The U.S. military's drone problem has never been simply a procurement problem. Individual services have each stood up acquisition pipelines, developed doctrine in isolation, and delivered autonomous systems that arrive at combatant commanders without a unified force-generation framework behind them. The result is a capability that exists on paper — and in budget line items — more coherently than it does on the battlefield. The Biden-era Replicator initiative, which sought to field thousands of autonomous systems, was dissolved by the Pentagon in 2025 and replaced by the Defense Autonomous Warfare Group. The structural fragmentation it was meant to address never went away.

That diagnosis sits behind the most architecturally significant provision in the Senate Armed Services Committee's FY2027 National Defense Authorization Act: a clause permitting the establishment of a dedicated Robotic and Autonomous Systems Combatant Command, or RASCC, led by a four-star general and equipped with test and evaluation authority as well as limited acquisition authorities. The committee advanced the bill 18-9 on June 11, 2026, at the close of its markup in Washington. The bill totals $1.14 trillion — $1 trillion for DoD, $41 billion for the Department of Energy — broadly aligning with the administration's $1.15 trillion discretionary request.

The Stovepipe Diagnosis

The core argument for RASCC is organizational, not technical. Each military service presently manages drone acquisition on its own terms, optimizing for service-specific requirements rather than joint operational output. The outcome is predictable: systems that are procured in volume but cannot be coherently allocated, tasked, or sustained across the joint force. A Senate SASC staffer described the problem bluntly:

"The real issue from the Replicator days was [that] they were buying assets, but how do you actually force generate and deliver those in a coherent way to combatant commanders?"

Replicator's dissolution in 2025 removed the only cross-service coordination mechanism that had been operating at scale. DAWG, its successor, has not been defined in public with the same ambition. The RASCC provision is Congress's structural answer — not another program office, not an initiative, but a combatant command with the statutory weight that designation carries.

The fragmentation concern is not abstract. The Pentagon is simultaneously running the $1.1 billion Drone Dominance Program and Joint Interagency Task Force 401, two active drone efforts whose relationship to one another — and to service-owned programs — remains organizationally diffuse. Whether RASCC would subsume, coordinate with, or stand apart from those efforts is not specified in what the committee has passed.

What a Four-Star Drone Command Would Actually Change

Combatant commands carry authorities that program offices and task forces do not. A four-star RASCC commander would, under the provision as described, hold test and evaluation authority and limited acquisition powers — meaning the command could, in principle, drive requirements, validate systems, and influence procurement in a way no existing drone-focused body can. The "limited" qualifier on acquisition authority matters: it suggests Congress is not proposing to strip service acquisition executives of drone programs wholesale, but rather to insert a joint-force integrator with enough statutory authority to compel coherence.

The test and evaluation authority is arguably as significant. One persistent failure mode in autonomous systems fielding has been the absence of a joint T&E framework — services test to their own standards, which produces systems validated for service-specific environments that fail in joint or combined operations. A combatant command with T&E authority could establish common metrics and realistic operational conditions that no single service has incentive to mandate for the others.

What RASCC would not automatically resolve is the deeper question of requirements generation. If individual services retain control of what they ask autonomous systems to do, a new command with acquisition authority is downstream of the problem. The provision, as passed in committee, permits the establishment of RASCC — it does not mandate it, and it does not define the command's relationship to existing service acquisition structures in detail. That architecture would be worked out in implementation, if the provision survives to enactment.

The Bill's Path and the Dissents

The 18-9 committee vote is a meaningful margin but not a consensus. Sens. Tim Kaine (D-Va.) and Tammy Duckworth (D-Ill.) voted against the full bill, with Kaine citing concerns over Iran conflict policy — a dissent rooted in the broader national security posture of the legislation rather than the RASCC provision specifically. The bill now moves toward the full Senate; a final NDAA requires reconciliation with the House version and a floor vote in both chambers. Committee passage is the beginning of that process.

SASC Chairman Sen. Roger Wicker (R-Miss.) and Ranking Member Sen. Jack Reed (D-RI) presided over a markup producing a bill broadly aligned in topline with the administration's request, which limits the fiscal political surface area for opposition. The RASCC provision's durability through floor debate and House conference will depend in part on whether it attracts organized resistance from services protective of their acquisition prerogatives — a dynamic that has quietly killed less prominent reorganization efforts in prior NDAAs.

For now, the provision stands as committee language: a structural proposal, not an enacted command. Whether a four-star drone headquarters with acquisition authority actually materializes depends on a legislative process that has many more steps to run.

Sources