DRONEZONE
Counter-UAS

The Integration Tax: Why Base Defense Buys Chains, Not Sensors

DroneZone Desk · · 5 min read

We read the layered base-defense market as an integration market wearing a sensor market's clothes. Every protected site needs the same chain — detect, classify, confirm, decide, defeat — and every link in that chain is available from competent suppliers. What is scarce, and what buyers actually pay for, is the engineering that makes the handoffs work: cueing that slews a camera onto a radar track in seconds, command software that turns competing sensor feeds into one picture, and effector interfaces that hold custody through the engagement. Sensor hardware prices are converging downward; integration, installation, and sustainment are not. The durable margin in counter-drone base defense sits with whoever owns the command layer.

Ask an airport operator, a depot commander, or a forward-base engineer what counter-drone defense they bought, and the honest answer is never a product. It is a chain. A sensor must find the drone, a second sensor must confirm what it is, a command system must decide what to do about it, and an effector must be cued precisely enough to act within the seconds available. The chain is only as good as its weakest handoff, and the handoffs — not the sensors — are where most counter-drone projects succeed or fail. The Gatwick closure of December 2018, which grounded roughly a thousand flights and stranded well over a hundred thousand passengers, was not primarily a detection failure; it was the absence of an integrated chain that could turn uncertain reports into confident action. Every serious procurement since has been shaped by that lesson, whether the buyer articulates it or not.

The canonical layered architecture has settled into four functional tiers, and the supplier base has sorted accordingly. Wide-area detection comes from passive RF sensors — the class built by Dedrone, Aaronia, and the detection side of D-Fend Solutions — supplemented at larger sites by radar from the likes of Echodyne, Blighter, or RTX's KuRFS family. Confirmation comes from electro-optical and infrared cameras slewed onto the track. The decision layer is command-and-control software. Defeat, where it is legally permitted, runs from RF jamming through protocol-level systems to guns and interceptors. Each tier is competitively supplied, and each tier's products are, in isolation, increasingly interchangeable. The interoperability problem between them is not.

Cueing is the first place chains break, and the reason is that each layer wants a different quality of track. A passive RF sensor yields a bearing, a model identification, and often the operator's location, but no continuous custody. A camera needs the track handed off tightly enough to find a small airframe in its field of view within seconds, against sky, clutter, or an urban skyline. A jammer needs bearing and protocol; a gun needs fire-control-quality position and velocity; an interceptor needs uninterrupted custody from launch to terminal. A detection system that cannot deliver the track quality its effectors require is a very expensive alarm. Rules of engagement add a further constraint: almost every civilized use case demands visual confirmation before defeat, which makes the slew-to-cue loop between detection and camera the pacing step of the entire architecture.

Premium assessment

This forward assessment and the rest of the analysis belong to the Premium tier — available soon. Join the list on the Premium page and read it at launch.

In brief
Airports, depots, and forward bases procure counter-drone defense as a detection-to-defeat chain. The contract that matters is the one that makes the handoffs work.
DroneZone DeskDesk-original reporting and analysis
More from the Desk