As the Army's lasers enter production, who will repair them in the field?

The US Army announced in September that AeroVironment of Albuquerque had won an other-transaction agreement for production under the Enduring High Energy Laser (E-HEL) programme, the first time the service has placed a production contract for a high-energy laser weapon.² Laser Wars puts the award at $464.8 million and reports that the 2024 solicitation asked bidders to identify tasks soldiers could perform themselves and to support several line-replaceable units under Army Regulation 750-1.¹

E-HEL is meant to defeat drones at a lower cost per shot than missiles, with shots drawn from the power supply rather than a finite magazine.² Its design follows a modular open systems approach with 11 major interfaces, which the Army says frees it from any single platform or vehicle and lets it be mounted at fixed bases, at semi-fixed tactical sites or on mobile combat vehicles.²

Writing in Laser Wars on 27 October, Jared Keller argues that the real test for the Army's lasers is whether junior enlisted troops can keep them running in the field, rather than relying on clean rooms, specialist engineers or the companies that built them.¹ His starting point is a photograph from 31 August 2026 of a 20 kW Army Multi-Purpose High Energy Laser (AMP-HEL) on a JLTV near Rio Grande City, Texas, operating under NORTHCOM's Joint Task Force-Southern Border; a second AMP-HEL, on an Infantry Squad Vehicle, was photographed at Fort Bliss on 16 September.¹

The recent record is uneven. In February 2024 four 50 kW DE M-SHORAD prototypes on Strykers went to CENTCOM, where the Army's acquisition chief cited trouble with heat dissipation, electronics and wear on the vehicles, and the Army later dropped the effort in favour of E-HEL.¹ According to the DOT&E report for fiscal year 2024, the deployment kept the Army's Rapid Capabilities and Critical Technologies Office from starting its planned technical testing, and because the in-theatre assessment followed no test plan and had no independent observers, there was too little data to judge effectiveness, lethality, suitability or survivability.¹ DOT&E counts reliability, availability, maintainability, logistics and manpower supportability, and training as parts of operational suitability.¹

Earlier laser fieldings leaned on industry. When the Air Force bought an additional Raytheon High Energy Laser Weapon System for an overseas field assessment in December 2019, the deal bundled six months of maintenance training in theatre with the collection of reliability, availability, maintainability and supportability data; the Palletized High Energy Laser, a BlueHalo (now AV) system in CENTCOM since 2022, was given a four-year logistics support contract in April 2024 covering preventive and corrective maintenance and training.¹ Keller expects contractors to carry most of the upkeep for now, though he suggests the border deployment could yield data that earlier efforts failed to gather.¹

GAO flagged the same problem in April 2023. Reviewing a portfolio on which DOD spends about $1 billion a year, it listed maintainability among the longer-term challenges for directed energy weapons, next to battle management, tactics, techniques and procedures, and user safety.³ Availability suffered when one deployed system, troubled by cooling and by problems holding a battery charge, had to be shipped home to its maker; GAO offered the case as an illustration of a broader issue, that these weapons have delicate internals whose repair usually needs a dedicated clean room.³ Keller adds that debris on an optic can absorb heat and damage the lens, and he recalls Lt. Gen. Robert Rasch saying in August 2025 that the Army cannot rely on clean rooms in combat, and Maj. Gen. Sean Gainey saying in 2023 that keeping one system working took three.¹

GAO also looked at how the services listen to users. Each military department told GAO it heard from warfighters, whether by letting them try prototypes, through simulation exercises, in field conversations with operators or simply in passing, but only the Army tracked that input formally, through soldier touch points that log hours of soldier use; for one system it recorded 179 such hours on training tools alone.³ Some of what came back was practical: a controller modelled on video-game hardware made the weapons easier to operate, and a touch screen suits a weapon badly when the person at it may have food in hand.³

The maintainer is also a user

Human-factors work usually starts at the operator's console. The maintainability chapter of MIL-STD-1472H moves the starting point: whoever does a maintenance-type task, crew member or not, falls under the maintainer requirements.⁴ The standard then asks for designs that keep the skill and training burden low, that swap out as modular packages, that one person can remove and refit where weight and structure permit, and that can be serviced where they are fielded by people wearing whatever protective kit the mission demands.⁴

Read against the E-HEL solicitation, this makes the line-replaceable unit a human-factors decision as much as a logistics one.¹ Where the boundary of each unit falls decides what a soldier is trusted to touch and what goes back to the factory. The standard also wants anything easily harmed by rough handling or contamination to be flagged as such, with both hardware and procedure standing between it and careless treatment.⁴ A laser optic that heat and debris can ruin is exactly such an item.¹

Diagnosis before repair

Swapping a unit only helps if the soldier knows which one has failed. MIL-STD-1472H asks for automatic fault detection and isolation where possible, for built-in test or other plain evidence of status at the level of the replaceable unit, for self-test messages, and for troubleshooting that does not mean pulling subassemblies apart.⁴ It adds error-proofing: guides, alignment pins and shape differences that prevent wrong mounting, and parts that differ in function should not fit in each other's place.⁴ The battery-charge and cooling faults that sent a fielded weapon home are the kind of condition this asks the system to surface, so that the maintainer can tell a unit swap apart from a return to the manufacturer.³

KEY IDEAKnow which unit failed — then swap it in the field, or send it back.

Procedures that survive the field

The FAA's operator's manual for maintenance human factors treats compliance with procedures as the product of four things together: the maintenance system, the person doing the work, the document and the surrounding environment.⁵ It asks for a feedback route from the technician to the people who write the procedures and on to the manufacturer, for procedures to be checked with the people who will actually perform them in an operational setting, and, when a technician departs from the written steps, for the inquiry to look for the reason the departure made sense to them rather than for someone to blame.⁵ Procedures also need to stay reliable in the dark and in the open air, where the manual notes a good share of maintenance and inspection is carried out.⁵ AMP-HEL units have already been photographed on vehicles at the southern border and at Fort Bliss, settings with no clean room to hand.¹

Counting hours or learning lessons

The Army's soldier touch points give GAO a figure that can be audited.³ Hours, though, measure exposure rather than findings. The touch-screen example shows the value of seeing how a weapon is really used, mealtimes included; the FAA manual's point is that such findings only matter if a route exists to carry them back into the design and the written procedure.³⁵

• Which tasks inside each E-HEL replaceable unit has the Army assigned to soldiers, and was that split tested with soldiers in protective equipment, at night, in the field?
• Can the built-in test tell a soldier, in plain terms, whether a fault calls for a unit swap or for a return to the manufacturer?
• How are contaminated or damaged optics marked and guarded during field handling?
• Do touch-point records capture what maintainers found and what was changed, or only how many hours were logged?
• What will the border deployment record about maintenance time, errors and repeat faults, and who reads that record?