E-HEL Moves Toward Production: The Next Test Is Sustained Field Capability
Back to Signal
DefenseInnovationAutonomy

E-HEL Moves Toward Production: The Next Test Is Sustained Field Capability

September 4, 2026Jess Loban

What the award announcement establishes

In its September 2, 2026 announcement, AeroVironment describes an Army other-transaction agreement for dozens of LOCUST X3 systems over the next few years. It identifies a 30-kilowatt, platform-agnostic system, with JLTV integration and palletized options, and includes support and training. The company describes the award as the first U.S. production contract for high-energy laser weapons.

That milestone should be attributed to the announcing supplier. It is narrower than claiming the first production contract for every kind of directed-energy weapon, and it does not by itself establish every acquisition-status detail or acceptance milestone. The release supports a transition toward production; it does not mean prototyping, integration or operational evaluation is finished.

The announcement also links the program to AMP-HEL prototypes and White Sands testing that informed coordination with the FAA. Those are relevant steps in the transition. They should not be replaced with an unsupported account of a particular border engagement or treated as blanket authorization for every domestic use.

Production must close the transition gap

GAO's April 2023 review of directed-energy transition planning found that successful demonstrations had not consistently led to acquisition programs with clear transition arrangements. The report distinguished the Army, which had a detailed transition plan, from planning weaknesses in the Navy and Air Force. Its follow-up record lists the Air Force recommendations as implemented, citing evidence reported in October 2025. That dated history explains why a production commitment matters: responsibility must move beyond demonstrating a physical effect to delivering, maintaining and improving a usable capability.

The handoff includes manufacturing quality, configuration control, training, repair and acceptance evidence. A prototype may rely on specialist support that cannot accompany every fielded unit. The production plan has to identify that dependency and either remove it or fund a practical support model.

Low marginal shot cost is not zero logistics

Lasers can reduce reliance on an interceptor for each engagement. Their economic attraction is strongest where a low-cost threat would otherwise consume an expensive munition. But a defensible comparison must include the whole capability rather than electricity alone.

Power generation, fuel, batteries where used, cooling, optics care, spares, maintainers and downtime remain part of the bill. The energy delivered in a beam is not the system's entire electrical demand. A nominally deep magazine can still be constrained by available power, heat rejection, target dwell time and the pace of successive engagements.

The GAO technology overview highlights atmospheric conditions, range and cooling among directed-energy limitations. Buyers should therefore compare cost per successful engagement within a defined environment, alongside availability and support burden. A single unqualified dollars-per-shot number cannot answer that question.

Match the effector to the operating conditions

The vendor announcement describes a role against Group 1–3 UAS; it does not support a categorical claim that the system is only for Groups 1–2. Even within a group, target characteristics and conditions matter. Power rating alone is not a complete performance specification.

A mobile installation can bring protection closer to a maneuver element, but the vehicle choice does not prove that every mobility, endurance or maintenance requirement has been met. Integration must account for the effect on the host platform and its support arrangements.

Layered defense remains the right planning question. A laser's role should be evaluated with other sensors and effectors, including what happens when weather, geometry or system availability makes a different response necessary. Production of one option does not eliminate the need for alternatives.

Accept the support arrangement with the hardware

For an illustrative fielding review, assume a delivered system completes its prescribed acceptance test but requires specialist assistance for a recurring maintenance task. The procurement question is whether that support is part of the planned operating model and available where the unit will use it. A successful test does not answer who performs the task, how the support is requested or what happens while the system is unavailable.

The receiving organization should identify the operator, maintainer, supplier and program-office responsibilities. Confirm the required training, approved maintenance information, support equipment and repair route. Where a task must remain with the supplier, include realistic access and turnaround assumptions in the availability plan. Do not present a field-maintainable capability when the actual configuration depends on support that has not been arranged.

This is a sustainment example, not a finding about the delivered E-HEL configuration. It illustrates why support evidence belongs in the same decision as production acceptance. The program should know which obligations transfer at delivery and which remain open, with resources assigned to both.

Compare availability and cost over a useful period

The acquisition price and the marginal cost of an individual engagement answer different budget questions. To assess a serviceable capability, identify the time horizon, included support and conditions under which the system is expected to be available. Keep supplier estimates distinct from observed operating results.

Separate scheduled maintenance, unexpected repair, unavailable support and environmental limitations in reporting. Combining every unavailable period into one figure can hide the action needed to improve support; excluding inconvenient periods can overstate usable availability. The definitions should be agreed before comparing alternatives.

The program may choose to address a support bottleneck, adjust the deployment plan or rely on another approved layer when the capability is unavailable. Those decisions do not require claiming that one technology is universally superior. They require a clear account of what the accepted configuration can support and what resources make that support dependable.

As production grows, check whether earlier support assumptions still hold across the additional units. More delivered systems increase demand for training, repair and configuration management. A supplier's ability to build hardware and the customer's ability to sustain it are related but distinct capacities. Fund the constraint demonstrated by the evidence rather than assuming that production volume alone resolves the transition problem.

What a fielding review should require

  1. Define the tested envelope. Document the conditions, target set and limitations demonstrated by the accepted configuration.
  2. Measure sustained availability. Include maintenance, cooling and power constraints, not just a successful shot sequence.
  3. Verify the support model. Establish operator training, repair responsibilities, spares and the logistics footprint at the intended unit.
  4. Test system integration. Confirm that detection, identification, authorization and effect assessment work with the wider defense arrangement.
  5. Track production evidence. Monitor acceptance results, configuration changes and supplier constraints as quantities increase.

For competing suppliers, the meaningful benchmark is a supported field capability under stated conditions. A new evaluation can still reveal a better fit for a mission; one production award does not settle the market. Industry should prepare evidence that connects performance to availability and sustainment, rather than rely on demonstration footage alone.

Sources and further reading

Spartan X's engineering, logistics and program-execution work joins these concerns into one fielding plan: performance that is understood, support that is resourced and delivery milestones that demonstrate an enduring capability.

Share this article
LinkedIn

BUILD WITH US

Ready to Solve Hard Problems?

Spartan X builds AI systems, autonomous platforms, and cybersecurity solutions for defense and national security.