Counter-UAS & Base Air Defence · clarifiers
Counter-drone procurement turns on one question more than any other: are you allowed to defeat the drone, or only see it? Detection-and-tracking is something almost every airport, base or critical site can buy and operate. Mitigation — jamming, cyber-takeover, kinetic or directed-energy effectors — is an act against an aircraft in flight, and in nearly every jurisdiction the authority to do that is reserved to police, military or a national security agency, not the site operator. Tell us that, the threat picture you're protecting against, and the sensor/effector mix you can lawfully field, and a supplier can scope a real system instead of a brochure. The questions below are the ones a C-UAS systems engineer asks before quoting.
What does this system need to do — detect and track only, or also defeat the drone?— unblocks quoting This is the single biggest fork in counter-UAS. Detection-and-tracking is widely procurable and operable by a site operator; mitigation (jamming, cyber-takeover, kinetic, directed-energy) acts against an aircraft in flight and in most jurisdictions the authority to do it is reserved to police/military/national-security forces — not the airport or site. It decides the entire supplier shortlist, the legal pathway, and whether you're buying sensors, effectors, or a layered system with both. Get this wrong and the rest of the quote is meaningless.
Select… Detection, tracking and identification only — no defeat capability Detect + mitigate (soft-kill: RF jamming / GNSS denial / cyber-takeover) Detect + mitigate including hard-kill (kinetic / net / directed-energy) Detection now, mitigation-ready architecture to add later once authorised Not sure — need help scoping what we're legally allowed to field Who holds the authority to operate mitigation (jam / defeat) at your site, and is it secured? For counter-UAS this is THE gate, not a tick-box. Operating an effector against a drone is tightly controlled everywhere: jamming needs a spectrum exemption, defeating an aircraft in flight is often reserved to a designated state authority, and at an operating airport it must be coordinated with ATC, the spectrum regulator and the security agency (GCAA / GACA / QCAA in the Gulf). A supplier needs to know whether mitigation will be operated by you, by a co-located state force, or not at all — that changes the system architecture, the rules-of-engagement integration, and what can lawfully ship to your country (export control: ECCN 6A008.e / EU Dual-Use 2021/821).
Select… Site operator is authorised to mitigate (exemption / licence held) Mitigation operated by co-located police / military / national-security force Authorisation in progress — not yet granted Detection-only deployment — no mitigation authorisation needed Unknown — need guidance on the authorisation pathway in our jurisdiction Which detection layers do you need — and is a single sensor enough or a fused multi-sensor picture? No single sensor catches every drone in every condition: radar sees the physical object but can clutter on birds, passive RF locates the drone and operator but is blind to autonomous/no-link drones, EO/IR confirms and identifies but needs line-of-sight and struggles in dust, acoustic is short-range only. The biggest operational problem at airports is false positives — so mature systems fuse layers (a radar/RF cue confirmed by camera). Telling us whether you need one modality or a fused, C2-integrated suite sets the price class and which suppliers are even in the conversation.
Select… Passive RF detection only (no emission licence, locates operator) Radar-led (detects autonomous / no-RF-link drones) EO/IR camera for visual ID / confirmation Fused multi-sensor (radar + RF + EO/IR, false-alarm reduction) Layered system integrated to an external C2 / air-picture network Not sure — recommend the right layering for our threat What standoff / detection range does the protected airspace require? Range drives the sensor class and cost more than any other spec: short-range handheld/RF kits detect at roughly 0.75–2 km, fixed-site C-UAS radars typically reach 3.5–14 km, and long-range or military-grade radar pushes to 40–80 km. The right answer comes from your protected footprint and threat warning-time, not from picking the biggest number — over-ranging a small perimeter wastes budget and floods operators with clutter, while under-ranging a large base leaves no reaction time.
Select… Short range — point / asset protection (up to ~2 km) Medium — perimeter / single airfield (~3.5–8 km) Extended — large base or multi-site (~10–15 km) Long / military-grade (40 km+) Not sure — size it from our protected footprint How does it need to deploy — fixed site, mobile/vehicle-mounted, or man-portable? Form factor reshapes the whole solution. A permanent fixed-site installation supports large mast-mounted radar, mains power and C2 integration; a vehicle-mounted or relocatable system trades range for on-the-move (OTM) coverage and rapid emplacement; man-portable/backpack kits are battery-run and short-range for dismounted teams. In the Gulf, fixed and vehicle systems also need the -32 to +65°C, IP66/67, MIL-STD-810 ruggedisation that desert heat and dust demand. This decides the product line within a given supplier's catalogue.
Select… Fixed site — permanent perimeter / base installation Mobile / vehicle-mounted (on-the-move coverage) Relocatable / rapid-deploy (set up and tear down in hours) Man-portable / backpack for dismounted teams Mix across several sites / configurations What drone threat are you defending against, and must it integrate into an existing C2 / air-defence network? The target class sizes the sensors and effectors: a single Group-1 hobbyist quadcopter is a very different problem from Group-2/3 tactical UAS or coordinated swarms, and loitering-munition/larger threats pull the system toward wider base air-defence. Equally load-bearing is whether this is a standalone island or has to plug into an existing C2 / IAMD picture via open interfaces (SAPIENT, ASTERIX, TAK/CoT, FAAD C2) — that determines whether a self-contained kit will do or whether the supplier must deliver an integration, not just a box.
Select… Group-1 small/hobbyist drones (low, slow, small) Group-1/2/3 tactical UAS up to ~25 kg Swarms / multiple simultaneous threats Larger UAS / loitering munitions (wider base air defence) Standalone system — no external C2 integration needed Must integrate into our existing C2 / air-picture network Optional — these help the supplier quote accurately first time (condition, certification and delivery especially).
