Twenty Armies, Twenty Ways to Kill a Drone

A Russian reconnaissance drone crossing the Suwałki Gap in 2027 will be tracked by Polish radars, Lithuanian jammers, and a German battery on rotation — and each will describe it in a format the others cannot read. NATO's counter-drone problem is not a shortage of weapons. It is thirty-plus national C-UAS programs with no common command-and-control standard, buying faster than they integrate. The alliance has solved this before. It took twenty years.

The Fratricide Built Into the Architecture

Counter-drone defense fails upward. The kinetic problem — hitting a quadcopter — is largely solved: guns, jammers, interceptors, and net systems all work within their envelopes. The unsolved problem is identification at alliance scale. Every national system defines "hostile" differently, thresholds its confidence differently, and publishes its tracks differently. Put twenty of them on one border and the false-alarm rate does not add; it compounds.

The fratricide scenario writes itself. An allied sensor flags a track as hostile under national rules of engagement. A neighboring nation's system, running different classification logic, flags the same track as friendly — correctly, because it is a friendly drone that never got deconflicted. Both are right by their own standards. Both are wrong in the only sense that matters. Ukraine can run a single national air picture because it answers to a single command. NATO cannot, and every exercise since 2023 has demonstrated the seam.

Twenty National Solutions to One Problem

The procurement map explains the architecture. France bought PARADE, its modular counter-drone system, developed on a national timeline for national requirements. Germany runs layered national programs tied to its own air-defense modernization. Poland is building indigenous C-UAS layers alongside American and Korean purchases. The Baltic states buy what they can field fastest — commercially derived systems, Israeli interceptors, whatever ships soonest.

Each choice is individually rational. Collectively they produce an eastern flank where a drone crossing three borders in fifteen minutes generates three incompatible track files, three separate engagement decisions, and zero shared custody of the engagement. Exercises have surfaced this repeatedly: allied sensors see the same drone and report it in formats that require manual translation at the very moment the timeline permits none.

The real world delivered the same lesson louder. When Russian drones violated Polish airspace in September 2025 — roughly twenty airspace breaches in a single night, met by NATO fighters under the alliance's first live engagement over its own territory — the response worked because Polish and allied aircraft happened to be airborne and talking on established air-defense links. The follow-on Eastern Sentry deployment hardened the posture. What the episode exposed was the floor: slow, low, small tracks handled case-by-case by national chains of command, with the alliance's counter-drone layer still a patchwork of national systems stitched together by liaison officers. It worked at small scale. Scale is precisely what the threat is designed to deny.

Procurement Moves Faster Than Standards

NATO knows. C-UAS working groups have met for years; technical interoperability standards circulate in draft; the alliance's integrated air and missile defense architecture — the IAMD framework and its ACCS command system — is the natural home for a common counter-drone air picture. The machinery of standardization exists and is staffed.

The machinery is also slow, and the threat is not. Nations facing drone incursions in 2025 and 2026 bought nationally and planned to standardize later, which in procurement practice means never — retrofitting a fielded national system to a STANAG that did not exist at purchase time costs money nobody budgets. The result is a ratchet: every year of national buying deepens the installed base that any future standard must accommodate, which makes the standard blander, which makes it less worth adopting. Link 16 succeeded because it preceded the fleet. C-UAS standards are arriving after it.

The drone threat is networked and crosses borders in minutes. The defense is national and files its tracks in triplicate. That is not a gap — it is a structural mismatch.

The Precedent and the Timeline Problem

The alliance has closed exactly this gap before, and the precedents are sobering. Link 16 took roughly two decades from requirement to universal tactical adoption. ACCS spent over €1 billion and the better part of fifteen years achieving an integrated air picture — for manned aircraft, at the speed of bureaucracy, against a threat that was not evolving monthly. Both succeeded. Neither timeline is available now, because small drones iterate on commercial electronics cycles measured in quarters.

The plausible 2027–2030 path is not a single standard but a federation: a thin common track-exchange layer — essentially a translation protocol at the C2 boundary — imposed on national systems rather than replacing them. NATO's air-policing integration work and its nascent counter-UAS doctrine point this way. It is less elegant than Link 16 and more achievable, provided a STANAG emerges before the installed base becomes unmovable. Whether working groups can move at exercise tempo rather than conference tempo is the open question, and it deserves an honest answer: the evidence so far says no.

What to Watch

- C-UAS STANAG progress. A ratified track-exchange standard is the single highest-value document in allied air defense; its absence after 2027 is a verdict. - Exercise reporting on track-sharing. When allied sensors report a common drone in a common format without manual re-entry, the problem is actually being solved. - Common C2 procurement consortia. Any three-plus-nation group buying shared counter-drone command software creates de facto standards faster than committees do. - Air-policing C-UAS integration. Folding counter-drone tracks into NATO's standing air-policing picture is the cheapest interoperability win available. - Rules-of-engagement harmonization. Convergent national definitions of "hostile" matter more than convergent hardware; watch for a common engagement matrix.

The alliance that standardized artillery calibers and data links can standardize a drone track. The question is whether it does so in the years the threat allows — or in the decades its institutions prefer. The September night over Poland bought the alliance a warning; what it buys with the warning is the test.