RF APEX · AIRPORT SOLUTION
Protect Runways, Aprons and Approach Paths Without Disrupting Flight Operations
Airports are among the most sensitive low-altitude environments. RF Apex detection systems continuously monitor runways, aprons and surrounding airspace for unauthorized drones, identifying and tracking them in real time. When an intruding drone is confirmed, jamming and spoofing systems neutralize it before it can threaten flight safety. Integrated with airport security, the system delivers real-time alerts to support fire, rescue and security decision-making.
Send an Enquiry
Executive Decision Summary
A mature airport project usually needs to get the following decisions right at the same time:
Threat and Operating Model
System requirements should distinguish safety-critical airspace events from nuisance reports, authorized drone activity and false alarms.
| Operating Concern | Why It Matters | What the Buyer Should Define |
|---|---|---|
| Drone near an approach or departure path | Short warning time and severe consequences; fast correlation and notification are essential | Approach sectors, minimum useful warning time, altitude bands, ATC coordination procedure |
| Drone in the runway or taxiway area | Ground and flight operations need immediate situational awareness | Runway geometry, airside access limits, obstacle clearance, operator response procedure |
| Launch from landside or outside the perimeter | The launch point may be outside the airport and different every time | Public viewing areas, direction-finding needs, evidence retention, law-enforcement handover |
| Authorized airport or contractor drones | The system must not treat approved flights as threats | Approval data, flight plans, identification procedure, whitelist management and audit |
| Autonomous or non-cooperative targets | With no RF link present, RF detection alone may not be enough | Whether a radar or electro-optical layer is required, target size, acceptable detection uncertainty |
Airport detection data should support a shared operational picture, but an alert alone cannot determine pilot intent — and it cannot authorize a countermeasure.
Layered Counter-UAS Architecture
A reliable programme is designed as a sequence of functions, not as a single device. Each layer should have defined inputs, outputs, interfaces and operator responsibilities.
| Layer | Functional Requirement | Procurement Evidence |
|---|---|---|
| 1. Detect | Find targets using RF, radar or other approved sensors | Supported target types, frequency coverage, update rate, coverage assumptions and known limitations |
| 2. Verify | Corroborate alerts with EO/IR, track history and operator observation | Day/night performance, cueing workflow, recording format, false-alarm handling |
| 3. Command | Present tracks, alerts, health status and evidence on a controlled operator interface | Map layers, user roles, audit logs, API/SDK documentation, cybersecurity |
| 4. Decide | Act under an approved concept of operations and escalation rules | Alert prioritization, operator authority, decision records, notification paths, response-time targets |
| 5. Respond | Use approved non-kinetic, security or law-enforcement action | Legal authority, spectrum permission, safety interlocks, human authorization, post-incident reporting |
Important: Detection, identification and countermeasures are three separate decisions. A sensor alert alone does not prove intent, and any active response must stay within the authorization and spectrum rules that apply at the destination and for the end user.
Coverage Zones and Sensor Placement
Model coverage by operational zone. Precise geometry is more useful than a marketing radius, because terrain, terminals, hangars, towers and electromagnetic conditions affect every site differently.
| Zone | Coverage Objective | Typical Design Considerations |
|---|---|---|
| Approach and departure sectors | Early warning along priority flight paths | Long sight lines, target altitude, off-airport siting, aeronautical coordination, clutter |
| Runway and taxiway area | Continuous awareness close to aircraft movements | Obstacle limits, maintenance access, multipath, vehicle clutter, zero-downtime requirement |
| Terminal and apron | Detection and verification near passengers, stands and buildings | Dense structures, congested RF, privacy rules, camera field of view, alert prioritization |
| Airport perimeter | Detect crossings or launches before a drone reaches the core airside area | Fencing, terrain changes, adjacent roads, patrol access, power and networking |
| Command and evidence zone | Correlate alerts, notify stakeholders and preserve incident records | Network redundancy, time synchronization, user roles, retention policy, integration with airport systems |
System Priorities
Every part of the airport configuration is ordered around one principle: a drone incident must never turn into a flight-safety incident.
Continuous monitoring of runways, aprons and approach paths, detecting unauthorized drones in real time.
Near runways, navigation spoofing is preferred over broadband jamming, so aircraft communications and navigation are never affected.
RF detection combined with radar and visual confirmation verifies the threat before any response, reducing false alarms.
Alerts, tracks and incident records are delivered to airport security and operations through a clear command workflow.
Project Architecture
Every airport project follows the same process, so coverage, verification and response authority are all fixed before the system goes live.
Map runways, approach paths, blind spots, the RF environment and regulatory boundaries.
Deploy fixed wideband detection (APX-D02 / APX-DF-10G) and equip patrol teams with the F13M handheld detector.
Correlate RF, radar and visual evidence at the command layer and confirm the threat before responding.
Spoof the drone away from the protected area (APX-DSF-GNSS) or jam under orders; mobile teams respond with the APX-DJSB-8B backpack unit.
Typical Applications
One system architecture, applied to the areas where a drone incident costs the most.
Fixed detection covers the movement area, so an intruding drone is flagged before it can force a runway closure
Detection extends into the approach and departure corridors — where aircraft fly lowest and have the least room to manoeuvre
Covers terminals, stands and cargo aprons against surveillance, smuggling and disruption
Live tracks and incident records go straight to fire, rescue and security teams, so everyone responds from the same picture
Information to Prepare
With these six items ready, RF Apex can fix the detection positions and response methods and prepare a tailored proposal — no second round of questions needed.
Related Equipment and Systems
Fixed detection for the movement area, handheld units for patrol teams, and an aviation-safe response layer.
Technical Requirements for the RFQ
A useful RFQ describes operational outcomes and acceptance methods, not just a product name. Ask bidders to respond against the same requirement matrix.
| Requirement Group | Buyer Input | Evidence Required from the Supplier |
|---|---|---|
| Threat definition | Drone types, links, likely routes, altitudes, speeds, autonomy | Compliance matrix stating detectable, conditionally detectable or out of scope |
| Coverage | Protected boundary, alert zones, terrain, buildings, line of sight, required warning time | Coverage map, siting assumptions, blind-spot analysis, expansion options |
| Environment | Temperature, rain, dust, wind, salt fog, vibration, lightning, power quality | Environmental ratings, installation limits, thermal design, maintenance requirements |
| Performance | Alert latency, track continuity, direction finding, classification, evidence retention | Test methods, representative evidence, confidence conditions, documented limitations |
| Integration | VMS, PSIM, GIS, command platform, networks, time sources, third-party interfaces | Protocol list, API documentation, data ownership, cybersecurity architecture, version policy |
| Lifecycle | Operating hours, support response, spares, training, warranty, expected service life | Maintenance plan, remote diagnostics, spares list, upgrade policy, support SLA |
| Compliance | Destination, end user, import requirements, spectrum rules, operating authorization | Export screening, certificates, authorization dependencies, division of responsibilities |
Deployment and Integration Plan
Airport deployment should be treated as an aviation change project, with controlled surveys, approvals and test windows.
Form a stakeholder group covering airport operations, aviation safety, security, IT, spectrum, legal, law enforcement and the relevant ATC parties.
Document authorized drone operations, historical incidents, likely launch areas, protected assets and required warning time.
Complete RF, line-of-sight, structural, power, network and cybersecurity surveys at candidate positions.
Produce the coverage and integration design, defining sensor roles, blind spots, alert routing and failure behaviour.
Run a pilot in controlled windows with approved targets and representative routes, without interfering with airport systems.
Tune thresholds, classification rules, the operator interface and escalation procedures based on pilot evidence.
Install, complete FAT/SAT, train operators and maintainers, and schedule recurring scenario exercises.
Any change to runway use, buildings, perimeter access, radio systems or the authorized drone programme should trigger a review of coverage and procedures.
FAT and SAT Acceptance Framework
Acceptance criteria should be agreed before manufacture and installation. The project team should separate factory verification from performance testing at the real site.
| Test Item | Factory Acceptance Test (FAT) | Site Acceptance Test (SAT) |
|---|---|---|
| Configuration | Verify models, quantities, interfaces, firmware, accessories and documentation before shipment | Confirm installed assets, coordinates, calibration, network configuration and as-built drawings |
| Detection workflow | Demonstrate sensor output and alert handling with controlled inputs or representative targets | Run agreed routes and scenarios in priority zones, including repeat passes and edge conditions |
| Operator workflow | Verify user roles, alert acknowledgement, evidence export and escalation logic | Measure operator actions, notification timeliness, handovers and incident reporting in practice |
| Integration | Test documented APIs, data fields, time synchronization, health reporting and fault states | Verify end-to-end exchange with the buyer's operational systems and network policies |
| Reliability | Burn-in, restart, power-loss recovery and component health checks | Observe the specified continuous operation, communications recovery and environmental behaviour |
| Training and handover | Check manuals, maintenance tools, spares and training materials | Complete operator and maintainer training, competency checks and signed handover records |
Record test geometry, target type, route, altitude, weather, RF conditions, software version and operator actions. A single maximum-range demonstration is not a complete acceptance test.
Common Procurement Mistakes
Frequently Asked Questions
No. Near runways our primary response is navigation spoofing, which draws the drone away without broadband jamming. Jamming is used only under orders and avoids critical aviation bands.
Fixed detection reaches up to 10 km; the F13M handheld reaches up to 5 km and identifies more than 100 drone types.
Yes. Detection alerts, tracks and incident records are delivered to the airport security operations centre through a standard command workflow.
Usually not. Line of sight, buildings, RF conditions and operational zones differ across an airport, so effective warning and verification need a purpose-built layered design.
Only where the responsible authority holds the required legal and spectrum authorization and an approved safety procedure is in place. Rules differ by country, destination and end user.
Use repeated, approved scenarios across representative routes, altitudes, zones and conditions, recording detection, track continuity, alert latency, verification, operator actions and system recovery.
Official Planning References
For projects involving civil aviation or US operations, consult the official sources below. They do not replace local legal, spectrum, aviation, import or operational review.
Tell us your runway layout, protected areas and operating requirements, and RF Apex will prepare a tailored proposal for your airport.
Send an Enquiry