DoD Counter-UAS Strategy and Joint Doctrine

The Pentagon spent most of the 2010s treating small UAS as a niche force protection problem—something relevant to special operations and fixed forward operating bases, but not a priority for conventional force modernization. That assessment was wrong, and the cost of getting it wrong is now embedded in the force structure decisions, acquisition timelines, and doctrine gaps that define the current C-UAS enterprise.

Understanding where DoD is now requires understanding how it got here.

Origins: From Ad Hoc to Organized

The DoD C-UAS enterprise grew from operational necessity in Iraq and Afghanistan, where groups like ISIS weaponized commercial quadcopters with dropped grenades and modified fixed-wing drones as kamikaze systems. Early responses were organic—units deployed commercial jammers, adapted existing sensor systems, and developed local TTPs without institutional backing. The 2017 ISIS drone campaign against Kurdish forces in Mosul, which injured or killed dozens of soldiers, accelerated recognition that this was a systemic problem, not an anomaly.

The formal organizational response came in 2019 with the establishment of the Joint Counter-small UAS Office (JCO) under the Deputy Secretary of Defense. The JCO was chartered to synchronize DoD C-UAS efforts across components, accelerate capabilities to the field, and coordinate with interagency partners. Critically, the JCO was given a coordination mandate, not acquisition authority—it can recommend and synchronize, but the services retain acquisition decision-making. This has been a persistent source of friction.

The JCO's first major product was the DoD C-UAS Strategy, released in January 2021. The strategy established three lines of effort: developing and fielding capabilities, maturing the operational architecture, and engaging with allies and partners. It explicitly acknowledged that the threat had outpaced the response and that existing systems were inadequate for the emerging UAS environment.

The Integrated Fires-Low Architecture

DoD organizes its C-UAS requirements through the Integrated Fires-Low (IF-Low) construct, which tiers UAS threats by altitude and range and assigns defeat responsibilities to specific system families. The architecture mirrors the broader Integrated Air and Missile Defense (IAMD) layered approach but specifically addresses the low-altitude, small UAS domain that existing SHORAD and SHORAD-adjacent systems were not designed for.

The tiers generally map as:

• Tier 1: Group 1-2 UAS (small commercial-class, under 55 lbs, below 1,200 AGL)—countered by short-range electronic warfare, directed energy, and kinetic systems at the unit level
• Tier 2: Group 3 UAS (medium, under 1,320 lbs, below 18,000 AGL)—countered by extended-range EW and SHORAD-class kinetic systems
• Tier 3+: Group 4-5 UAS (large, military-grade)—countered by SHORAD, HIMAD, and air-to-air assets

The distinction matters for acquisition. Tier 1 threats require organic, platoon-level capabilities distributed across the force—cheap, easy to maintain, crew-operated systems. Tier 2 threats require more sophisticated systems with longer range and more capable seekers. Conflating the tiers drives poor requirements and misaligned procurement.

Service-Specific Programs

Each service has developed C-UAS programs reflecting their specific operational contexts and threat priorities.

Army: The Army's C-UAS investment is centered on the Indirect Fires Protection Capability (IFPC) program, the IM-SHORAD (Interim Maneuver-Short Range Air Defense) based on the Stryker platform, and organic unit solutions including the Coyote Block 2+ and Block 3 interceptors. The Army is also fielding the IVAS-integrated C-UAS detection capability and investing in Directed Energy M-SHORAD (DE M-SHORAD) as a lower cost-per-shot defeat option. The Army's challenge is scale—it needs C-UAS distributed to the brigade combat team level and below, which requires affordable, maintainable systems in numbers that current budgets struggle to support.

Marine Corps: The Marines have prioritized MADIS (Marine Air Defense Integrated System) for the expeditionary context, emphasizing lightweight, mobile solutions that can deploy with Marine Expeditionary Units. MADIS integrates detection and kinetic/electronic defeat on a JLTV platform. The Marine approach reflects their expeditionary mandate—every C-UAS system must be air-transportable and operable without fixed infrastructure.

Navy: The Navy's C-UAS priority is ship defense against the Group 1-3 UAS threat, which became acute as Iranian-backed groups demonstrated the ability to strike vessels with modified commercial drones. ODIN (Optical Dazzling Interdictor, Navy) provides a directed energy capability for ship-based C-UAS. The Navy has also accelerated integration of CIWS (Close-In Weapon System) for drone threats and is testing rail gun and high-energy laser solutions for future fleet defense.

Air Force: Air base defense is the Air Force's primary C-UAS concern. The THOR (Tactical High-power Operational Responder) high-power microwave system was developed by AFRL specifically for swarm defeat at fixed installations. The Air Force is also integrating C-UAS sensor networks into its base defense systems and evaluating integration with F-35 sensor data for base perimeter awareness.

The Replicator Initiative

In August 2023, Deputy Secretary of Defense Kathleen Hicks announced Replicator—an initiative to field thousands of attritable autonomous systems across multiple domains within 18-24 months. While framed broadly, the initial focus was explicitly on small UAS and counter-UAS applications, directly referencing lessons from Ukraine and the need to field mass at operationally relevant scale.

Replicator represents a significant shift in acquisition philosophy. Rather than developing exquisite, expensive systems in small numbers, Replicator sought to leverage commercial and dual-use technology to field large quantities of systems that could be expended in contested environments. For C-UAS specifically, the initiative targeted autonomous loitering munitions and counter-drone effectors that could impose costs on adversary UAS campaigns without the per-unit economics that make current kinetic intercepts unsustainable.

The initiative's execution has been more complicated than the announcement suggested. Classification restrictions, export control considerations for allied sharing, industrial base limitations on rapid production, and the inherent challenge of integrating autonomous systems with existing C2 architectures have all created friction. The 18-24 month timeline for "thousands of systems" proved optimistic. But the underlying logic—that cost-imposing solutions require mass, and mass requires affordable unit costs—has accelerated thinking across the services.

Ukraine: The Doctrine Reset

The conflict in Ukraine has been the most consequential operational laboratory for C-UAS doctrine in the modern era. Several specific lessons have directly influenced DoD thinking:

Cost-per-intercept economics are unsustainable at scale. Early Ukrainian air defense expenditures revealed that defending against mass drone attacks with expensive interceptors quickly depletes stockpiles and creates economic leverage for the attacker. A Shahed-136 costs roughly $20,000-50,000; intercepting it with a Patriot missile costs over $3 million. The math is untenable at operational scale.

Electronic warfare is essential but insufficient. GPS spoofing and RF jamming proved effective against commercially derived drones, but adversaries adapted—shifting to optical navigation, pre-programmed waypoints, and frequency-hopping communications. EW is a necessary component of the C-UAS architecture but not a sufficient one.

Layered defense with organic capabilities is critical. Ukraine's most effective C-UAS approach combined national-level systems (Patriot, NASAMS) with theater-level SHORAD, unit-level EW, and individual soldier adaptations including civilian quadcopters repurposed as spotters and modified firearms with optics for low-flying targets. No single layer worked; the combination did.

The sensor network must be distributed. Centralized detection creates single points of failure. Ukraine's most resilient detection came from distributed sensor networks including civilian observers, commercial radar systems, and integrated acoustic sensors—not from centralized air defense radar.

These lessons are being incorporated into JP 3-01 revisions, service-level C-UAS publications, and formal training programs at the Combined Arms Center and equivalent service schools. The adaptation is ongoing; doctrine is trailing operational learning by 12-24 months in most areas.

Rapid Acquisition: Compressing the Timeline

Traditional defense acquisition timelines are incompatible with the pace of UAS threat evolution. A system entering the acquisition process today under standard Major Defense Acquisition Program procedures would not reach the field for 7-10 years. The threat environment is evolving faster than that by an order of magnitude.

DoD has responded by aggressively using alternative acquisition pathways:

Middle Tier Acquisition (MTA) under Section 804 of the FY2016 NDAA allows programs to reach initial fielding within 5 years without a full Milestone A-B-C process. Multiple C-UAS programs have been structured as MTA efforts, trading acquisition rigor for speed.

Other Transaction Authority (OTA) under 10 U.S.C. § 4022 allows DoD to enter agreements with commercial and nontraditional defense contractors outside the Federal Acquisition Regulation (FAR) system. OTA has been used extensively for C-UAS prototype development and rapid commercial technology integration.

Emergency Fielding authorities have been used repeatedly since 2017 to get capability to combatant commanders facing immediate threats. These authorities allow bypassing standard testing and evaluation requirements, which creates sustainment and interoperability challenges downstream but delivers capability at operationally relevant timelines.

The JCO plays a coordination role in this rapid acquisition environment—attempting to ensure that service-level rapid acquisitions don't produce incompatible systems that fragment the joint C-UAS architecture. The degree to which that coordination is succeeding remains a subject of internal debate within the department.

Where Doctrine Stands and Where It's Going

The current joint doctrinal baseline for C-UAS is JP 3-01, Countering Air and Missile Threats. The 2023 revision incorporated small UAS more substantively than previous editions but remains primarily oriented toward traditional air and missile threats. Service-level publications—the Army's FM 3-01 (Air and Missile Defense Operations), the Marine Corps' MCTP 10-10E—have incorporated C-UAS more directly but vary in how they address Group 1-2 UAS at the tactical edge.

The doctrinal gap is most acute at the company and battalion level, where most encounters with weaponized commercial UAS actually occur. Unit-level TTPs are largely self-generated from operational experience, shared informally through the force, and variably integrated into pre-deployment training. The institutional training base—National Training Center, Joint Readiness Training Center, Marine Air-Ground Task Force Training Command—has accelerated incorporation of realistic C-UAS training scenarios, but the gap between operational experience in Ukraine or the Middle East and institutional training remains significant.

The trajectory is clear: C-UAS is transitioning from a force protection niche to a core warfighting function that every echelon must address. The organizational and doctrinal infrastructure is adapting, but the pace of adaptation is being tested by a threat environment that has no interest in waiting.