The US Army announced on 2 October that Acting Secretary Adam Telle had directed the establishment of a Futures and Autonomous Systems Command (FASCOM). The same memorandum calls for changes to force structure, acquisition and specialist personnel. It follows the defence secretary's 30 September announcement of a separate department-wide Autonomous Warfare Command. The Army describes FASCOM as its means to bring autonomy into regular formations and acquisition decisions.
The directive identifies at least six formation areas: aviation, armour, fires, sustainment, engineering and training. It also calls for a Portfolio Acquisition Executive for Autonomy. Army Public Affairs says the service will prioritise acquisition and fielding of autonomous fires, combat vehicles, watercraft resupply, breaching, reconnaissance, surveillance and target-acquisition systems, as well as teaming between crewed and uncrewed platforms, no later than fiscal year 2028. The Army also plans more authorisations for 15X tactical UAS specialists and 390A robotics technicians near tactical formations.
Why the organisation matters
A command, acquisition portfolio and trained operators can connect prototype work to budgets, doctrine, sustainment and units. The Army already has a Capability Program Executive Office for Mission Autonomy; the new directive is an additional organisational step, not proof that a specific drone or robot has completed qualification. The announcement gives no FASCOM activation date, equipment quantities, individual system awards or operational acceptance records.
Future evidence to watch is the command's actual activation, published portfolio decisions, unit allocations and system-specific deliveries. Until those appear, the fiscal 2028 priorities should be read as direction for acquisition and fielding rather than a list of deployed capabilities.
Publication history
- — Added Army autonomy-command directive while separating organisational priorities from accepted systems.
Suggest a correction to this entry
Follow the evidence
Source types identify who makes the claim. Programme milestones and supplier statements should be read in context.
