Army Returns 173rd Airborne’s 600-Soldier Drone Battalion to Infantry Duties

The U.S. Army is ending the dedicated drone-warfare mission of a roughly 600-soldier battalion in the 173rd Airborne Brigade, returning the Europe-based unit to traditional airborne infantry duties. The reversal removes a deployable formation built specifically to experiment with unmanned warfare, but the Army says the battalion’s findings will feed future force design and drone experimentation.

The battalion, based within a brigade stationed in Italy and Germany, will complete its final major exercises in Germany before submitting results from those events and nearly a year of previous work. Two anonymous U.S. officials attributed the refocusing order to acting Army Chief of Staff Gen. Christopher LaNeve. The available information does not establish that the leadership change preceding the decision caused it, or that the Army is ending drone development elsewhere.

That distinction is important. The Army is closing one organizational experiment, not walking away from unmanned aircraft. Regular formations continue to test and integrate small drones, including through the service’s broader transformation initiatives. The unresolved issue is whether distributing that work across conventional units can preserve the speed, technical focus and institutional memory concentrated in a dedicated battalion.

A year of concentrated drone experimentation

Formed last November, the specialized battalion was intended to deploy wherever additional drone capability was required. Its soldiers worked with first-person-view drones, artificial intelligence and aircraft designs intended to remain useful amid electronic jamming. The unit also studied dedicated unmanned formations developed by Ukraine’s armed forces and translated those observations into feedback for the Army.

The work extended beyond flying aircraft. In May 2025, the Army highlighted a first-person-view drone laboratory at Caserma Del Din in Italy where brigade soldiers designed and built systems. That type of soldier-level experimentation gives engineers and acquisition officials direct information about usability, reliability and the gap between a prototype that functions in a demonstration and equipment that a formation can repeatedly train with and maintain.

The Army’s challenge is turning that rapid feedback into equipment decisions without creating incompatible fleets or fragmented support arrangements. An Army University Press analysis of unit-driven drone development describes the institutional tradeoff: operational units can identify needed changes quickly, while acquisition specialists still have to manage contracting, testing, cybersecurity, airworthiness and sustainment requirements.

Small drones evolve faster than traditional military platforms, but rapid hardware turnover carries costs. Frequent design changes complicate training, spare-parts inventories, software support and configuration control. A dedicated experimental unit can contain some of that complexity while producing repeatable findings. Distributing experimentation across multiple formations creates a broader user base, but it also raises the risk that lessons arrive in different formats or that units test equipment under inconsistent conditions.

The findings survive, but the organization does not

The Army said the battalion will “deliver what it learned” during its final exercises, together with findings from the past year, to guide force design and future experimentation. A third anonymous official described the exercises as a planned culminating event after which the unit’s future would be reviewed. That official also said many participants had expected the specialized mission to continue under former Army Chief of Staff Gen. Randy George.

The handoff will therefore matter as much as the final exercises. Useful experimental data must identify not only whether a drone completed a task, but also what training, maintenance, communications, software and logistical support were required to keep the system available. Without a dedicated organization, the Army will need another mechanism to retain experienced personnel, compare results between units and convert field observations into requirements that manufacturers can build against.

The service has not publicly detailed that replacement mechanism. It also has not specified whether another formation will inherit the battalion’s role as a deployable center of drone expertise. That leaves a difference between preserving reports and preserving a functioning team: documents can inform planning, but an established unit also carries practical knowledge through its operators, maintainers and leaders.

Congressional concern has added a near-term accountability point. A group of lawmakers requested an Army briefing by Sept. 21 on how the service intends to continue applying lessons from Ukraine and advancing drone integration after the specialized mission ends. The Army’s response could clarify whether this is a transition to a broader model or simply the conclusion of a limited experiment.

For now, the confirmed outcome is unusually concrete: approximately 600 soldiers will return to airborne infantry duties, while their drone work moves into the Army’s planning system. The next test is whether those findings become fielded capabilities and whether the service can reproduce the battalion’s concentrated learning without retaining the battalion built to produce it.

By Stephen Wallace — Editor for AMI’s aerospace integration and unmanned mobility coverage, focused on drone manufacturing, VTOL systems, autonomous networks, and air-ground mobility links.