The counter-UAS landscape, honestly mapped.

The four layers of a counter-UAS system

A useful counter-UAS (C-UAS) programme has four distinct layers, and confusion about which layer a product belongs to is the single largest driver of bad procurement outcomes.

Detection. RF detection, radar, acoustic, or electro-optical. Different physics, different detection envelopes, different false-alarm profiles. No single sensor is adequate; fusion of at least two is a baseline requirement.

Classification. Distinguishing drone from bird, drone-type from drone-type, and friendly from hostile. This is where a surprising amount of real-world engagement failure occurs — a detection that cannot be classified confidently is a detection that cannot be acted on.

Tracking. Continuous track through clutter, weather, and adversarial masking. Track continuity is where sensor fusion becomes essential, not optional.

Engagement. Jamming, spoofing, kinetic, or capture. Each has legal, airspace, and collateral-damage implications that differ by site and by jurisdiction. The right engagement for a power plant is not the right engagement for a border post.

What actually works, under real conditions

In realistic Indian conditions — monsoon, heat, urban RF noise, VIP-convoy escort scenarios — three capabilities are genuinely mature today. Passive RF detection and classification for commercial-controller-based drones (DJI and similar). Doppler-gated staring radar for drones below the altitude ceiling of civilian ATC radar. Protocol-level RF takeover for a narrow set of drone models, legal only under specific authorisation.

Three capabilities are marketed as mature and are not. Acoustic detection at range, outside quiet rural sites. Single-sensor EO classification under glare and partial cloud. Broad-spectrum jamming in civilian airspace, where the collateral spectrum effects are regulatory non-starters.

Where the procurement conversation goes wrong

Two common failure patterns. First, buying detection without classification — the system alerts constantly and is silenced within weeks. Second, buying engagement without classification — the system is legally forbidden from firing because the track cannot be confidently classified as hostile. In both cases the procurement line looks complete on paper and is non-functional in the field.

A third pattern, specific to Indian procurement, is buying imported systems without field trials in the specific monsoon and RF environment of the deployment site. Detection envelopes collapse in monsoon. RF environments in Indian cities are unique. Field trial data from a European test range does not transfer.

The defensive-geospatial adjacency

C-UAS is operationally adjacent to geospatial intelligence, which is Flybi’s domain. A C-UAS programme is only as useful as its understanding of the airspace and terrain it defends. Current air picture, terrain masking, RF shadow mapping, and historical incursion pattern analysis are all geospatial problems. Buying C-UAS hardware without the geospatial layer is buying a rifle without a range card.

The honest recommendation

For most Indian critical-infrastructure operators, the right first investment is a detection-and-classification layer (passive RF + radar fusion) integrated with the site’s geospatial picture. Engagement should follow, under formal authorisation, once the site has operational familiarity with the detection layer and the legal framework has been established. Buying engagement first is common; it is also the pattern that produces silent systems.

Flybi operates in the geospatial layer of this stack — the air-picture and terrain analysis that makes C-UAS engagements defensible. We do not sell jammers or effectors. For partnership discussions, route via keshav@flybi.in with “[Restricted]” in the subject.

---

Related reading