The one place a drone is never a joke
A single multirotor near a runway can close an airport for hours. The architecture below is built around early wide-area detection, positive identification and evidence — with every mitigation step coordinated with aviation authority rules.
Design constraints
Airports impose an unusual pair of constraints: the protected volume is enormous and operationally unforgiving, and uncoordinated RF emission is itself a flight-safety hazard. The detection stack is therefore dominated by radar (wide, fast, all-weather) and passive EO/IR (identification without emissions), with spectrum monitoring in listening mode.
Response is procedural as much as technical: geofenced alert stages, ATC-coordinated holds, law enforcement dispatched on pilot-localization data, and every event recorded to evidential standards for prosecution and insurance.
Engagement flow
-
01
Detect
X-band LSS radar sweeps the approach volume; contacts beyond the airfield boundary enter the air picture with automatic threat grading by distance and trajectory.
-
02
Identify
Cued EO/IR classifies the contact (drone vs bird vs aircraft) with AI; spectrum monitoring classifies emissions and begins pilot localization.
-
03
Decide
Alert stages trigger on geofence penetration: observation, warning, operational response — each with defined authority and logging.
-
04
Resolve & record
Law enforcement acts on pilot coordinates where the aircraft lands; the full sensor record is archived for investigation and regulator reporting.
Reference configuration
| Wide-area LSS radar | 2–4 × (10 km on 0.01 m², 3 s refresh) |
|---|---|
| Panoramic high-speed EO | 2–4 × (360°/7 s, hands off to tracking EO) |
| Tracking EO with laser ranging | 4–8 × (3 km auto track, ±1 m ranging) |
| RF spectrum monitoring | 3–6 × (30 MHz–6 GHz, pilot localization) |
| Command & control | 1 × C2 integrated with airport security ops; RTSP/UDP to existing VMS |
Airport FAQ
Is jamming legal at airports?
Usually not for the airport operator itself — RF emission around active runways is tightly regulated and typically reserved for state authorities. That is precisely why this architecture is detection-led: it produces the evidence and localization that let the lawful responders act.
How does this integrate with existing airport systems?
Over open interfaces: RTSP video into the VMS, UDP tracks into the security operations platform, alarm stages over standard relay/API. No rip-and-replace.
What about beyond-perimeter threats on approach paths?
Radar range is sized to approach corridors; the 10 km envelope gives controllers minutes of warning rather than seconds.
Specifying airport low-altitude protection?
Send runway layout, approach corridors and regulatory jurisdiction for a reasoned design.
Discuss the architecture