US Army autonomous launcher nears development awards

The US Army is approaching development awards for its Common Autonomous Multi-Domain Launcher programme, which will create optionally crewed vehicles capable of carrying several offensive and defensive missile types.

The programme covers medium and heavy variants rather than a single universal vehicle. CAML-H uses a 15-ton-class chassis and is being considered for larger weapons including Tomahawk and PAC-3 Missile Segment Enhancement, while CAML-M is based on the Family of Medium Tactical Vehicles.

The medium platform could carry Multiple Launch Rocket System munitions or an Integrated Fires Protection Capability arrangement using AIM-9X. Autonomous reloading also forms part of the programme, reducing the number of personnel required around launch and replenishment operations.

Earlier work demonstrated that a High Mobility Artillery Rocket System could be adapted for robotic operation without extensive structural modification. The prototype later participated in military exercises, providing experience in autonomous movement and remote control.

CAML extends that work into a family of launchers designed for several weapon categories. The concept offers logistical and procurement advantages, although Tomahawk, PAC-3 MSE, MLRS rockets, and AIM-9X do not arrive as mechanically or electronically interchangeable payloads.

Each weapon requires its own canister, data connection, electrical supply, alignment, safety procedures, fire-control sequence, and clearance envelope. Commonality must absorb those differences without producing a vehicle more complex and expensive than several specialised launchers.

A common architecture carries uncommon weapons

Mechanical interfaces need to secure missile modules against road vibration, cross-country loads, shock, and launch forces. Alignment must remain accurate after transport, while the vehicle needs sufficient stability to fire from uneven or lightly prepared ground.

Larger missiles raise the centre of gravity and may introduce transport restrictions. Levelling equipment, stabilisers, and module-handling systems add weight and require regular maintenance.

Electrical and software architecture carries equal importance. The launcher must receive engagement data, communicate with command networks, confirm the weapon’s status, complete pre-launch checks, and execute the correct sequence for each missile.

Open interfaces can shorten the integration of new payloads, but they do not remove qualification. Every weapon still needs environmental, transport, electromagnetic, safety, and live-firing trials.

Autonomy adds perception sensors, route planning, obstacle detection, remote supervision, and defined responses to communications failure. The vehicle must identify whether ground conditions, overhead obstructions, and nearby structures make a location suitable for firing.

Cybersecurity becomes critical when a networked autonomous vehicle carries long-range weapons. Authentication, command authority, update mechanisms, and degraded-mode behaviour have to prevent interference without making the launcher unusable when links are disrupted.

Industrial vehicle technology is already entering other dangerous Army tasks, including Caterpillar’s participation in the autonomous breaching competition. CAML adds the tighter control requirements associated with missile movement and launch.

Growing electrical demand across military vehicles provides another connection. Qualification of 600V Army vehicle electronics reflects the power required by sensors, actuators, communications, and mission equipment aboard increasingly automated platforms.

Reloading may exceed the driving challenge

Autonomous movement receives much of the attention, although robotic replenishment could prove harder to execute reliably.

Missile canisters are heavy, awkward, and hazardous. Handling equipment must locate the launcher and module accurately, move the load without damaging connectors or structures, and verify that the canister is locked in place.

Field conditions complicate every step. Reloading may occur at night, under camouflage, on uneven ground, or after equipment has been exposed to dust, mud, shock, and weather.

Sensors and mechanical interfaces that operate consistently in a factory can become unreliable when markings are obscured or alignment surfaces are damaged. Manual intervention may still be needed, reducing some of the expected personnel saving.

A common handling architecture could simplify support across several missiles, although existing canisters were not necessarily designed for robotic transfer. Standardising future modules may require changes to weapon programmes outside CAML.

Supplier selection will show how far the Army intends to use mature commercial vehicle technology. Automotive manufacturers can provide chassis, powertrains, and production capacity, while missile companies control launch systems, energetic safety, and fire-control interfaces.

The eventual fleet mix will determine whether the medium and heavy variants provide genuine economies. Separate chassis, payloads, and support equipment could create two production lines despite the shared architecture.

Dispersed autonomous launchers could make missile units harder to locate and reduce the number of personnel exposed during movement and firing. Those advantages depend on affordable vehicles that can operate for extended periods without constant technical intervention.

Development awards will begin the process of turning the architecture into prototypes, modules, and controlled software. Testing will need to include payload changes, difficult terrain, communications loss, robotic reloading, and connection to wider command networks.

CAML promises to place several weapon families on common autonomous platforms. Its production case rests on whether commonality reduces complexity across the force rather than concentrating it inside each vehicle.