Counter-drone has been a junk drawer for a decade — a radar here, a jammer there, a laser on a truck that needs perfect weather. The story of the next 18 months is that the drawer is being emptied, and everything inside is being bolted to one command architecture.
Counter-drone has been a junk drawer for a decade — a radar here, a jammer there, a laser on a truck that needs perfect weather. The story of the next 18 months is that the drawer is being emptied, and everything inside is being bolted to one command architecture.
The Gadget Era Ends
The counter-UAS market spent the last decade producing point solutions. Handheld jammers. Acoustic arrays. High-power microwave demonstrators like Epirus Leonidas. Each works, some well, and none share a track picture. The result, in exercises and in Ukraine: an operator staring at three screens showing three versions of the same swarm.
Ukraine burned the lesson in. Kyiv's claimed trajectory — over 2 million FPV drones in 2024, with industry statements pointing toward 4 million units a year of capacity — put swarms against defenses built to stop one aircraft at a time. On the other side, Russia's Geran-2 (the license-built Shahed-136) arrived in waves of dozens, at unit costs Western analysts place between $20,000 and $50,000. A $4 million Patriot interceptor against a $35,000 drone is not a defense. It is a budget with a fuse.
The U.S. Army's response over 2024-2026 has been quietly structural. Rather than fielding another sensor, it started fielding the thing that connects sensors: a common command-and-control layer with real production money behind it.
A Spine, Not Another Sensor
The centerpiece is FAAD C2 — the Forward Area Air Defense Command and Control system built by Northrop Grumman, in service since the 1990s and now being rebuilt as the connective tissue for counter-drone. FAAD C2 takes tracks from radars, RF detectors, and electro-optical sensors, correlates them into a single air picture, and hands engagement-quality data to whatever effector is assigned — kinetic, electronic, or directed energy.
Around it sit the systems the Army has been buying at scale:
- LIDS (the Low, slow, small Integrated Defeat System), pairing the KuRFS radar with Coyote interceptors — the fixed-site and M-LIDS mobile variants are now the Army's system of record for counter-drone - APKWS II laser-guided rockets, at roughly $20,000-$35,000 per shot, increasingly the cheap air-to-air and ground-launched drone killer - IFPC Enduring Shield launchers for the cruise-missile and drone tier, first units fielded under a Dynetics production contract - A growing menu of third-party sensors — Anduril's Sentry Tower, RF geolocation kits, acoustic nets — all expected to plug into the same picture
The contracts tell the real story. Coyote interceptor production, LIDS sustainment awards to SRC running into the high hundreds of millions, and FAAD C2 modernization work are the unglamorous money. A new radar makes a press release. The middleware that lets twelve radars act like one makes a program of record.
Allies Are Wiring In
France's PARADE system — a Thales and CS Group program fielded after the Paris 2024 Olympics compressed its timeline — is built as a modular architecture, not a single weapon. The UK has moved the same way, with Project ORCUS evaluations feeding an architecture-first approach and the RapidDestroyer microwave demonstrator slotted as an effector, not a system. Germany's NNbS short-range air defense program follows the same logic: one C2 layer, many shooters.
NATO's counter-drone doctrine from 2024 onward reads like procurement guidance for integration — common track formats, common engagement authorities, shared data links. The alliance has stopped asking who has the best sensor and started asking whose sensors can talk.
The winning counter-drone system of 2027 will not be a weapon. It will be an interface control document that everyone else had to sign.
The Data-Standard Fight
Underneath the procurement headlines is the fight that actually decides the market: whose data model becomes the default. Every fusion engine needs a track format, an identification confidence scheme, and a rules-of-engagement message set. Whoever owns those standards owns the upgrade cycle for a generation.
FAAD C2 is the incumbent in the U.S. lane, and incumbency is its own argument — an installed base across Army and joint units that any new sensor must integrate with or sit outside the network. Anduril's Lattice is the challenger pitch: a software-first mesh that treats FAAD as one node among many. Helsing is making a parallel argument in Europe around AI-assisted sensor fusion. The Joint C-sUAS Office, before its functions were absorbed into the Army's rapid capabilities structure, spent its final years pushing common architectures and test standards at Yuma; its successors inherited the fight.
Expect the standards contest to be settled the usual way: not by a specification committee, but by whichever architecture holds the most fielded nodes when the next supplemental lands.
What It Means for the Buy
The shift changes who gets paid. A sensor company selling a $2 million radar now faces a compliance bar: publish the interface, meet the track standard, demonstrate a FAAD C2 integration at a live-fire event. Companies that treated their data format as a moat are discovering it is a wall keeping them out of the network.
It also bends the cost curve the right way. Integration lets a $30,000 APKWS or a Coyote-class interceptor get cued by whatever sensor saw the track first, instead of requiring a dedicated sensor per effector. The Shahed economics problem — defending against cheap mass without spending yourself broke — is an architecture problem before it is a weapons problem. A fused picture lets commanders match the cheapest adequate effector to each track. A stovepiped one forces the most expensive available answer.
The 2027 posture, on current trajectory: division-level units running a common air picture, Coyote and APKWS as the volume kinetic layer, electronic warfare and microwave systems cued by the same tracks, and one C2 spine — almost certainly FAAD C2 in U.S. formations — underneath all of it.
What to Watch
- FAAD C2 contract awards through mid-2027: follow the modernization and production dollars, not the demo videos. A stall means the stovepipes win another round. - Live-fire integration events: watch which non-traditional sensors — acoustic, passive RF, space-based cueing — demonstrate a working FAAD feed, and which only brief it. - Replicator follow-on tranches: whether C-UAS gets its own line or rides inside broader autonomy buys will signal priority. - NATO track-standard decisions: alliance-level adoption of a common counter-drone data model in 2026-2027 freezes the market for a decade. - PARADE, NNbS, and FAAD interoperability tests: the first exchange of engagement-quality tracks between a European architecture and a U.S. FAAD network in a live exercise is the moment "integrated" stops being a brochure word.
The gadget era produced some genuinely good gadgets. The architecture era will decide which of them anyone can still use.
Counter-drone has been a junk drawer for a decade — a radar here, a jammer there, a laser on a truck that needs perfect weather. The story of the next 18 months is that the drawer is being…