Analysis · September 2026

Counter-UAS: the market and the kill chain


How militaries answer the drone threat — the detect-to-defeat kill chain, soft-kill versus hard-kill, the two axes every C-UAS buy is decided on, and where the counter-drone market is heading. A dated 2026 snapshot.

The kill chain: detect, track, identify, decide, defeat

Counter-UAS runs the classic targeting cycle — find, fix, track, identify, target, engage, assess (F2T2EA) — compressed in practice to detect → track → identify → decide → defeat. The architecture is consistent: sensor(s) → C2 / fire-control → effector. Sensors build the air picture; a command-and-control layer fuses it and decides; an effector executes the engagement. The launcher and its munition sit at the terminal engage node — cued by C2, not self-generating the wide-area picture.

The doctrinal consensus, stated repeatedly by the US Congressional Research Service and Congressional Budget Office, is that no single system protects you: layered defence of multiple detect and defeat systems is mandatory, and the C2 / sensor-fusion layer is named the most important investment, because no effector works without a coherent picture of what it is shooting at.

Soft-kill versus hard-kill

  • Soft-kill — non-kinetic effects: jamming the control link, spoofing satellite navigation, or high-power microwave. Cheap per shot and usually the first layer, but localised and temporary; it betrays the emitter's position, and it fails against autonomous "dark" drones and fibre-optic FPVs that carry no RF link to attack. Roughly 90 Russian jammers were reported destroyed in Ukraine after revealing their position (per press reporting).
  • Hard-kill — kinetic defeat: interceptor drones, guns, nets, or guided rockets and missiles. The definitive layer, especially where electronic warfare fails, but constrained by falling-debris and collateral risk, which tightens rules of engagement. Some effectors add abort authority to manage that risk — the Switchblade can be waved off and re-engaged up to about 4 seconds from impact, and the Coyote Block 2+ carries an electronic safe-and-arm fuze with return-to-readiness — though debris risk still favours net-capture and ramming at the low-collateral end; rocket and missile interceptors carry more reach and more debris risk.

The design goal every programme states is "any-sensor, best-effector" — C2 selects the layer (electronic warfare, kinetic, or directed energy) per threat and per rules of engagement.

The C2 and cue-in layer — a live contest

The command layer is where the market is contesting hardest, and as of 2026 there are two competing C2-of-record narratives rather than a settled record with a challenger. FAAD C2 (Northrop Grumman) has long been the US Department of Defense's designated C-UAS command-and-control system of record; it fuses heterogeneous sensor and datalink tracks into one air picture and was demonstrated driving eight sensors and six effectors simultaneously (a 2022 demonstration, per army-technology.com and vendor material).

Anduril Lattice has risen fast to challenge that status: the US Army selected it for a counter-drone fire-control replacement (October 2025), then awarded a ten-year enterprise contract vehicle worth up to $20 billion (March 2026) positioned to replace FAAD C2 as the Army's C2 backbone. The $20 billion figure is the Army-wide enterprise vehicle — a ceiling, not an obligated sum — under which the Pentagon's JIATF-401 counter-UAS effort placed a separate initial task order of about $87 million. Which system ends as the true system of record is not yet settled.

Raytheon's FS-LIDS is the canonical "launcher as one node" picture: a Ku-band radar (~15 km) cues FAAD C2, which tasks both an electronic-warfare soft-kill and a Coyote launcher for hard-kill against Groups 1–3 — and it inherits the same C2-transition caveat.

Procurement is also shifting toward pre-qualified marketplaces: JIATF-401 stood up a C-UAS Marketplace of 1,600-plus catalogued items (initial operating capability February 2026), and NATO's NSPA runs framework buying on the same logic — buy from a vetted catalogue rather than run a fresh competition each time.

Cost-per-engagement and magazine depth

Two axes now dominate C-UAS down-selects.

  • The first is cost-to-kill — the interceptor should cost less than what it shoots down. Illustrative press and vendor estimates put guided 70 mm rockets near $25k and some interceptor drones around $15k, against OWA targets estimated at $20k–$50k; these are unaudited figures, cited for order of magnitude only. Named, dated data points sharpen it: Ukrainian-built interceptors — SkyFall's P1-SUN, Wild Hornets' Sting, the Octopus — run roughly $1,000–$3,000, while the US-built Merops comes in around $15,000; after early-2026 Iranian drone strikes the US Army bought 13,000 Merops in eight days, which doubles as a live magazine-depth signal. As CSIS put it (March 2026), "using multimillion-dollar interceptors on low-cost UASs is neither efficient nor sustainable."
  • The second is magazine depth — a named US Army capability gap — because one-for-one interceptors are structurally vulnerable to swarm saturation.

The favoured paths are AI-driven C2, networked interceptors, high-power microwave for cheap mass, and deeper affordable magazines. NATO's Project Flytrap (Germany/Poland, 2025) is actively sorting which effector belongs at which echelon.

The market, in numbers

Counter-UAS is the fastest-growing segment of air defence. Forecasters cluster around ~25% annual growth (low-to-mid 20s); MarketsandMarkets, for example, puts the counter-UAS CAGR at 25.1%. Market-size estimates vary widely by house and vintage, so any single figure reflects one firm's view:

Counter-UAS market sizing — one house's view (MarketsandMarkets)
ForecastBaseHorizonCAGR
Earlier MnM forecast~$6.6B (2025)>$20.3B (2030)~25.1%
Newer MnM forecast (supersedes)~$9.17B~$29.70Blow-to-mid 20s

National spending

National spending reflects the same curve:

Selected national C-UAS spending (public figures, as of 2026)
BuyerFigureNote
United States (FY27 request)~$994Mnearly doubled; ~$414M for operational systems (platforms/sensors/batteries); expeditionary/mobile launchers a separate ~$24M line
Polandanti-drone "wall"SAN / PGZ-Kongsberg contract (Jan 2026), distinct from the separate ~€2B Eastern Shield border wall
Colombia$1.68B shieldfirst phase ~$260–271M (sources conflict)

Interoperability is being written into standards — SAPIENT (UK Dstl; ICD published as BSI Flex 335) for sensor fusion, the draft STANAG 4817 for multi-domain control of unmanned platforms, and the statutorily mandated Modular Open Systems Approach (MOSA) in the US.

For how the launcher itself is becoming a separate procurement item, see our launch-node analysis.

The offer

Silentis offers Umbra as the engage node in this kill chain — an any-sensor, best-effector launcher you cue from your own C2, not another closed shooter. See the Counter-UAS launcher →

Sources

SourcePublicationDate
Kill chain, layered defenceCongressional Research Service R48477; Congressional Budget Office 62563 (cbo.gov)—
FAAD C2army-technology.com; Northrop Grumman FAAD C2 datasheet—
Lattice / fire-control replacement (Oct 2025) and $20B enterprise vehicle (Mar 2026); JIATF-401 ~$87M task order; C-UAS Marketplace (IOC Feb 2026)insideunmannedsystems.com; anduril.com/counter-uas; defence press—
FS-LIDS / KuRFS; hard-kill abort authority (Switchblade wave-off; Coyote Block 2+ safe-and-arm fuze)rtx.com (LIDS); army-technology.com; uasvision.com2024-02-12
Interceptor unit costs (SkyFall P1-SUN, Wild Hornets Sting, Octopus, Merops) and 13,000-in-8-days Merops buyDefense News2026-05-05
Cost-to-kill doctrine quoteCSIS (Bergmann / Svendsen / Burchell)2026-03-23
FY27 operational vs expeditionary/mobile line splitExecutiveGov, FY27 Army C-UAS—
Market growth (CAGR ~25.1%)MarketsandMarkets (published forecasts); US budget request and Poland/Colombia figures via defence press—
Standards — SAPIENT / STANAGjanes.com; act.nato.int—
Standards — MOSAmilitaryembedded.com—
Standards — Project Flytrapbreakingdefense.com; army.mil—
Standards — NSPA frameworknspa.nato.int—