When Congress reaches for a new combatant command, it usually means the department is struggling to integrate something that cuts across the services and existing geographic theaters. That was true for cyber. It was true, in different ways, for Special Operations and Space. Recent proposals for a drone‑focused combatant command fall squarely in that pattern, but may misdiagnose the underlying problem.
Uncrewed systems are tools, not a theater or a domain. Standing up a new four‑star headquarters to manage a class of hardware adds bureaucracy where what is really needed is clarity: of policy, of authorities, of concepts of operation, and of acquisition priorities. Before the Pentagon builds another flag‑officer ecosystem, it is worth asking what combatant commands are for, how they evolved, and whether a “drone COCOM” actually aligns with that logic.
How We Got COCOMs: Goldwater–Nichols And After
The unified combatant command system predates the 1980s, but the Goldwater–Nichols Department of Defense Reorganization Act of 1986 actually locked today’s COCOM model into place. Goldwater–Nichols clarified that operational command runs from the President to the Secretary of Defense directly to the combatant commanders, bypassing the service chiefs in the operational chain. The services organize, train, and equip. The COCOMs plan and fight.
In doing so, Congress empowered COCOMs as joint, theater‑level warfighters and made them the central nodes for campaign planning and execution. The law did not create commands for particular weapons. It strengthened joint commanders responsible for missions and theaters, supported by the services’ force‑providing role. That distinction matters in the current drone debate.
Geographic Versus Functional: Missions, Not Widgets
Over time, unified commands have been sorted into two basic types: geographic and functional.
- Geographic COCOMs (EUCOM, INDOPACOM, CENTCOM, AFRICOM, etc.): these plan and conduct operations in their regions.
- Functional COCOMs (SOCOM, STRATCOM, TRANSCOM, CYBERCOM, SPACECOM) provide globally oriented capabilities—special operations, nuclear deterrence, strategic transport, cyberspace ops, space support—across all theaters.
When functional COCOMs have been created, they have typically reflected either a global mission that no single theater can own (strategic deterrence, mobility) or a domain that pervades all theaters (space, cyber). In every case, they are aligned to enduring mission sets, not to specific hardware. There is no “Artillery Command,” “Missile Command” (in the joint sense), or “Unmanned Aerial Vehicle Command.”
Uncrewed systems, by contrast, are already embedded across every domain and mission: ISR, strike, logistics, EW, deception, and more. They are cross‑cutting enablers that should be wielded by geographic and functional commands as part of their toolkits, not cordoned off into a bespoke organizational silo.
What COCOMs Actually Do As Force Employers
Goldwater–Nichols also sharpened the division between force providers and force employers. The military departments and services recruit, train, and equip forces. The combatant commanders employ those forces in campaigns and operations. Over time, this has grown into a well‑understood workflow:
- Services build and present ready forces to joint force providers (e.g., Joint Staff, TRANSCOM, SOCOM).
- COCOMs plan, integrate, and employ those forces to meet theater or functional objectives.
- Functional COCOMs often act as global integrators for their mission set (STRATCOM for nuclear, TRANSCOM for mobility, CYBERCOM for cyber operations).
In that system, drones are already part of force packages that services present and COCOMs employ: MQ‑9s flying out of theater bases, small UAS in every brigade combat team, maritime uncrewed systems under fleet commanders, loitering munitions at the tactical edge. Creating a drone‑specific COCOM risks confusing the force‑provider/force‑employer split by building a structure around a technology category rather than a mission or domain.
Cyber Command’s Evolution: The Domain Logic
If proponents look for a precedent, U.S. Cyber Command provides an obvious reference point. USCYBERCOM was established as a sub‑unified command in 2010 and elevated to a unified combatant command in 2018. Its charter is to direct, synchronize, and coordinate cyberspace operations to defend DoD information networks, support joint force commanders, and defend the nation from significant cyberattacks.
Crucially, cyberspace is a recognized warfighting domain, alongside air, land, sea, and space. Cyber operations are inherently trans-regional. Malicious actors route through global infrastructure and ignore combatant command boundaries. The organizational “problem” CYBERCOM was designed to solve was not a hardware problem (servers, routers, tools) but a domain problem. No single geographic commander could own cyberspace, yet campaigns in that domain demanded consolidated responsibility and authority.
Even then, the path was incremental and painful. CYBERCOM emerged from earlier task forces and joint elements (JTF‑CND, JTF‑CNO, JTF‑GNO, JFCC‑NW) built over decades in response to mounting threats and real operational experience. Services had to reorganize around service cyber components. The Cyber Mission Force took years to build to full operational capability. Authorities—Title 10, Title 50, the relationship with NSA—required continual refinement. In other words, standing up a new COCOM was the end of a long evolution, not the starting point.
Lessons From CYBERCOM: Cross‑Cutting Without Centralizing Everything
There are at least three lessons from the cyber experience that should give pause before creating a drone command.
Cross‑cutting Doesn’t Mean Centralizing Everything.
Even after CYBERCOM’s elevation, most cyberspace operations are executed by service cyber components and mission teams aligned to support other combatant commands. CYBERCOM integrates and choreographs. It does not “own” all things cyber. A drone COCOM would face an even more acute version of this. Uncrewed systems are embedded in every service, every theater, and every mission set. Trying to centralize them risks cutting across service authorities and theater responsibilities in unhelpful ways.
Domains Justify COCOMS; Tools Do Not.
CYBERCOM exists because cyber is a domain of conflict with unique operational characteristics and global scope. Space Command exists because space is a domain. Uncrewed systems are platforms operating in those domains. If every major class of tool or weapon that proliferated across the joint force drove its own COCOM, the joint structure would quickly become unmanageable. Guns, tanks, munitions, sensors, and AI all cut across COCOMs; none of them gets its own COCOM.
New Headquarters Are Costly, In People And Focus.
Standing up CYBERCOM required reallocation of billets, creation of new staff structures, and persistent friction in roles and responsibilities with other commands and agencies. At a time when DoD is under pressure to reduce general and flag officer billets and streamline headquarters, adding another four‑star command for a class of hardware runs counter to that trend. The opportunity cost in terms of talent, attention, and time would be significant.
What Problem Is A Drone COCOM Trying To Solve?
When I worked for General James Mattis in the U.S. Central Command, he would always tell his staff (paraphrased), “Spend 2 weeks formulating the problem statement. Once you do, you can usually determine the solution in 2 hours.” So what problem or problem sets would a drone COCOM solve?
The proposal appears to respond to several real concerns: the explosive growth in uncrewed systems, adversary use of drones and loitering munitions, the need for coherent concepts of operation, and the desire for a single senior advocate in the building. Those are valid problems. But a new COCOM may be the wrong instrument for solving them.
If the issue is fragmented policy on unmanned export controls, authorities for cross‑border ISR, counter‑UAS rules of engagement, or manned–unmanned teaming, those are quintessentially Office of the Secretary of Defense (OSD) and Joint Staff problems. The joint requirements process, the Joint Capabilities Integration and Development System (JCIDS), and existing governance structures are meant to harmonize doctrine, organization, training, materiel, leadership, personnel, facilities, and policy around emerging capabilities.
If the issue is a lack of coherent operational concepts, then doctrine development and experimentation (through organizations like the Joint Staff J7, service warfighting labs, and cross‑functional teams) is the right place to focus. Exercises, wargames, and live experimentation can, and should, drive rapid learning about how to employ uncrewed systems at scale. None of that requires a new combatant command.
If the issue is advocacy and resource prioritization, there are other precedents. Functional components, cross‑functional teams, or designated executive agents can give drones a strong voice without creating an entirely new COCOM structure. SOCOM, for example, has service‑like authorities for SOF procurement but remains tightly integrated with the rest of the joint force.
The General Officer Experts Speak
I reached out to several of my general officer colleagues to get their take on this proposal. All agreed that a drone COCOM is a bad call.
According to Houston R. Cantwell, Brig Gen, USAF (Ret), a Senior Resident Fellow for Airpower Studies at the Mitchell Institute for Aerospace Studies who served a 30-year career in various roles including combat pilot, commander, and strategist, flying the F-16, MQ-9, and RQ-4 aircraft:
A new COCOM dedicated to drones and unmanned systems is absolutely the wrong approach. These new systems need to integrate with manned systems within very dynamic domains and this approach only complicates the issue. The Air Force’s new Collaborative Combat Aircraft bring cutting edge new capabilities that must seamlessly integrate into existing Air Force fighter and bomber aircraft. New underwater unmanned systems must closely coordinate with the Navy’s subsurface fleet. The introduction of a COCOM to govern these new systems introduces unnecessary risk to the warfighter and is counterproductive.
Mark Loeben, Maj Gen USAF (Ret.) also takes a skeptical view of the suggestion of another COCOM. He believes that, instead, we should be reducing permanent functional commands (and their expensive staff requirements) and streamlining command and control as new technologies dilute the effectiveness of regional and mission-specific command structures.
“Creating another COCOM might be putting the horse before the doctrine,” Loeben said. “As a former deployed commander of a ‘drone’ unit, I experienced the cross-cutting nature of the rapidly developing RPA mission first-hand. The high demand for MQ-9 capabilities in the early 2010s often required my team to coordinate with three COCOMs (2 geographic and one functional) and the Joint Staff before seeking commander’s intent through our ‘train and equip’ Air Force chain.”
Finally, Maj Gen USAF (Ret.) James Poss, who retired as the Air Force’s Assistant Deputy Chief of Staff for Intelligence, Surveillance and Reconnaissance, where he was responsible to the Secretary and Chief of Staff of the Air Force for policy formulation, planning, evaluation, oversight, and leadership of Air Force ISR capabilities. opined as follows:
“The notion of a Drone COCOM shows a fundamental misunderstanding of how the Department of Defense, and warfare, works. Getting more drones is an organize, train and equip problem the services must solve. Using them in combat is a job for the existing geographical combatant commanders, not a specialized command. This isn’t a stand-alone issue like ensuring special operations are equipped and employed correctly that Special Operations Command addresses. To win the autonomy war drone autonomy must be part of every weapon system and every operation , not something that yet another Combatant Commander must approve before buying or employing a drone.”
Slippery Slope: An AI Command Next?
Creating a drone COCOM because uncrewed systems are ubiquitous and important would set a powerful precedent that when a technology matures and spreads across the joint force, it deserves its own four‑star headquarters. That opens the door to an “AI Command,” a “Robotics Command,” or other technology‑defined structures such as autonomy, data, and algorithmic warfare that permeate every mission.
That direction risks confusing categories. Autonomy and AI are characteristics of systems and processes. They are not missions or domains. Drones are platforms. They are not theaters of war or functions. COCOMs are designed to command operations in a place or across a mission set, not to be stewards of a particular tech stack. Once that conceptual line is blurred, every emerging technology becomes a candidate for its own organizational empire.
Fix The Policy, Not The Org Chart
A better approach would focus on using the structures created since Goldwater–Nichols as they were intended.
- Leverage OSD and the Joint Staff. OSD policy, acquisition, and research elements, combined with joint requirements and doctrine development, are built to tackle cross‑cutting issues like drones. They can clarify authorities, streamline acquisition paths, and ensure coherent rules of engagement across COCOMs.
- Empower existing COCOMs. Geographic and functional commanders already integrate uncrewed systems into their plans and operations. Strengthening their ability to experiment, share lessons learned, and rapidly field new capabilities is more consistent with the Goldwater–Nichols logic than creating a hardware‑focused peer.
- Use functional organizing constructs short of a COCOM. Joint task forces, global integration frameworks, and cross‑functional teams can give uncrewed systems a focal point without standing up a new permanent command. These can be disbanded or reshaped as the technology and threat environment evolve.
- Align with officer drawdown and reform. Reducing general and flag officer billets and trimming headquarters has become a recurring theme in defense reform debates. Creating a new drone COCOM pulls in the opposite direction: more overhead, more staff, more turf battles, and more inertia.
Goldwater–Nichols was ultimately about making joint warfighting more effective by clarifying roles, strengthening combatant commanders, and pushing jointness down into the force. A technology‑specific “drone command” risks moving away from that vision by fragmenting responsibility, multiplying bureaucracies, and confusing who is responsible for employing what in which theater.
The United States absolutely needs to get serious about uncrewed systems: their integration across domains, their industrial base, the policies that govern their use, and the defenses against them. Those are urgent problems. But they are policy, doctrine, and capability problems, not organizational ones that can be solved by adding one more box at the top of the org chart.