Airport Security Radar: Detecting Drones, Birds & Intruders

Wu Kang | Radar System Specialist | Updated September 2026

Airport security radar rarely means one device. Runway approach paths, perimeter fence lines, and low-altitude airspace each need different detection coverage, so airports typically pair low-altitude 3D radar with a counter-UAV system layer rather than relying on a single sensor for all three threat types.

Why a Single Radar Doesn’t Cover an Airport’s Threat Picture

An airport security brief usually names three problems in one sentence: unauthorized drones near approach paths, bird activity that risks a strike, and people or vehicles crossing the perimeter. Each needs a different capability from the radar layer.

Low-altitude 3D radar (the MR-RDT and MR-RDA series) provides the wide-area detection and tracking, covering aircraft, UAVs, vehicles, and personnel across the airspace and ground picture in one sweep. It answers “is something there and where is it going,” not “what exactly is it.”

A counter-UAV system layer adds the classification and response piece: spectrum detection, protocol analysis, and electro-optical tracking to confirm what a radar track actually is and, where legally authorized, respond to it. Radar alone flags a track; the counter-UAV layer is what turns that track into an identified, actionable threat.

The Low-Altitude Radar Layer: Detection Ranges by Target Type

The MR-RDT series (3D continuous-wave, mechanical azimuth with DBF elevation) and the MR-RDA series (2-D AESA phased array) cover different points on the range/altitude spectrum. The figures below are published per model, with the target class each range applies to.

Model	Radar type	Small UAV range	Personnel / vehicle range	Max altitude	Azimuth	Power
MR-RDT02K	3D Ku-band CW, mechanical/DBF	≥1.5 km (RCS 0.01 m²)	—	600 m	—	≤120 W
MR-RDT05K	3D Ku-band CW, mechanical/DBF	≥3 km (RCS 0.01 m²)	—	600 m	—	≤180 W
MR-RDT10K	3D CW, mechanical/DBF	≥5 km	Vehicle/helicopter ≥10 km	1,000 m	—	≤260 W
MR-RDT12K	X-band, mechanical + DBF	DJI Phantom 4-class ≥12 km	Personnel ≥15 km, vehicles/ships/helicopters ≥25 km	3,000 m	360°, -5° to 60°	30 rpm antenna
MR-RDT18K	Extended-range 3D CW	≥8 km	Vehicle/helicopter ≥15 km	2,000 m	—	≤330 W
MR-RDT20K	3D CW, mechanical/DBF	≥10 km	Vehicle/helicopter ≥20 km	3,000 m	360°, -5° to 60°	≤400 W
MR-RDA10K-4R	X-band 2-D phased array, monopulse	≥10 km clear weather (RCS 0.01 m²)	Vehicles/ships ≥15 km, people ≥12 km	—	90°/face, 360° four-face	—
MR-RDA15K-4R	Four-array 2-D AESA 3D	≥5 km	Vehicle/helicopter ≥8 km	1,500 m	360°, -2° to 45°	≤1.6 kW

For runway-approach coverage, altitude ceiling matters as much as range: the MR-RDT12K and MR-RDT20K both reach 3,000 m, while the compact MR-RDT02K/05K units top out at 600 m, better suited to close-perimeter monitoring than approach-path airspace.

What “Detects Birds” Actually Means Here

The MR-RDA10K-4R’s published capability list names aircraft, UAVs, birds, and loitering munitions as detected target types. That’s a meaningful data point for an airport buyer, but it comes with a gap worth naming directly: no bird-specific detection range or classification methodology is published for this or any other model in the line. The dedicated bird-and-drone radar category that some airports already use (Schiphol and similar operations are documented publicly as running this kind of equipment) typically relies on micro-Doppler signature classification specifically tuned to tell a flock of birds from a quadcopter, and that level of classification detail isn’t part of Midradar’s published specifications.

The practical implication: MR-RDA10K-4R can be evaluated for bird presence in the general track picture, but a buyer whose primary driver is wildlife hazard management and strike-risk reporting should confirm classification accuracy and false-alarm rate directly with a current test report before specifying it for that specific use case, rather than assuming it performs the same job as radar built exclusively for avian detection.

Separately, this model has two published product pages with materially different specifications under the same name. Treat any MR-RDA10K-4R figure as provisional until confirmed against a current signed datasheet.

The Counter-UAV Layer: Where Classification and Response Live

Three integrated counter-UAV systems sit above the radar layer: MR-AUS20-RD02SE-RF03, MR-AUS70-RD05-RF05, and MR-AUS70-RD05-RF10. All three combine spectrum/RF detection, protocol analysis, radar detection, electro-optical tracking, and platform management through the RGS2000 low-altitude target control and identification platform; the RF10 and RF05 variants add higher-tier radar/sensor components for larger coverage areas.

None of the three have per-model numeric specifications (detection range, classification accuracy, response time) published on their product pages. This is a genuine gap for a Complete Guide to name rather than paper over: a buyer sizing a counter-UAV layer against a specific runway geometry needs those numbers from a technical datasheet or a pre-sales consultation, not from marketing copy.

One point applies regardless of model: any directional interference or countermeasure response module in a counter-UAV system operates under national and local spectrum/airspace law, which varies by jurisdiction and by whether the site is civil or military. Confirm local legal authorization for interference-based response before it’s included in a project scope — this isn’t a Midradar-specific caveat, it applies to counter-UAV interference technology generally.

Runway, Perimeter, and Ground Intrusion Coverage

The same low-altitude radar models that track airborne threats also carry personnel and vehicle detection ranges: the MR-RDT12K reaches personnel at 15 km and vehicles at 25 km, and the MR-RDA10K-4R reaches people at 12 km and vehicles/ships at 15 km. For most airport perimeters this ground-target range from the low-altitude layer is sufficient on its own; a dedicated ground/surface surveillance radar line exists for projects where fence-line intrusion detection needs to be specified independently of the airspace radar, which is a separate evaluation outside the scope of this guide.

A Framework for Specifying an Airport Radar Layer

1. Map the three zones separately: approach-path airspace, perimeter fence line, and apron/runway ground area. Each may need a different altitude ceiling and range.
2. Size altitude ceiling to actual approach geometry, not a generic “high enough” assumption. A 600 m-ceiling unit and a 3,000 m-ceiling unit solve different problems.
3. Decide whether classification is a hard requirement.If distinguishing a drone from a bird flock in real time is mission-critical (wildlife hazard reporting, strike-risk logging), confirm that capability directly rather than assuming general “detects birds” language covers it.
4. Confirm legal authorization for any interference-based responsebefore it enters the scope, since this varies by jurisdiction and airport classification (civil vs. military).
5. Request current signed datasheets for the counter-UAV system modelsand for MR-RDA10K-4R, given the published data gaps above, before finalizing a bid.
6. Plan the platform integration path(ATC/tower systems, existing C2, VMS) alongside the sensor selection, not after equipment is already on order.

Integration With Existing Airport Systems

Radar and counter-UAV data feeds into an airport’s existing security or operations platform through open protocols: GB/T 28181, ONVIF, and RTSP for video/track interoperability, plus RESTful APIs and SDKs for deeper platform-level integration with a command center or VMS. Confirming which system the airport already runs (VMS, C2 platform, or tower-adjacent operations system) before specifying hardware avoids a mismatch discovered during commissioning.

What This Costs

Neither the low-altitude radar line nor the counter-UAV system line has published pricing. Cost depends on coverage area, number of radar heads, whether a counter-UAV response module is included, and integration scope with existing airport systems — a quote is required for an accurate number.

Trade-offs Worth Weighing

Low-altitude radar gives continuous, all-weather airspace and ground coverage that a camera-only or acoustic-only system can’t match at range, and running the radar and counter-UAV layers together closes the gap between “something is there” and “here’s what it is and what to do about it.” The trade-off is real: the counter-UAV system’s classification and response capabilities aren’t backed by published per-model numbers, so a buyer evaluating strike-risk or classification-critical use cases has more homework to do before signing than the marketing language alone suggests. The MR-RDA15K-4R’s 1.6 kW draw is also a genuine planning constraint for sites without ready grid access near the radar mount point.

FAQ

Can this radar tell the difference between a drone and a bird?

The MR-RDA10K-4R lists birds alongside aircraft, UAVs, and loitering munitions as detected target types, but no classification methodology or bird-specific accuracy figure is published. Confirm this directly for any wildlife-hazard-critical use case.

What altitude does airport radar need to cover?

It depends on approach geometry. Published options in the MR-RDT/MR-RDA line range from a 600 m ceiling (MR-RDT02K/05K) up to 3,000 m (MR-RDT12K, MR-RDT20K).

Is drone jamming or interference legal at every airport?

No. Any directional interference or countermeasure response requires confirmed local legal authorization, which varies by jurisdiction and by whether the site is civil or military.

Does the radar itself identify the drone, or does something else do that?

The radar layer detects and tracks. Classification and identification are handled by the counter-UAV system layer, which adds spectrum detection, protocol analysis, and electro-optical tracking on top of the radar track.

Is pricing published for this equipment?

No. Both the low-altitude radar and counter-UAV system lines route to a quote request, since cost depends on coverage area and integration scope.

What's the biggest gap procurement teams should ask about before ordering?

The counter-UAV systems (MR-AUS series) don't have published per-model detection range or classification accuracy figures, and the MR-RDA10K-4R has two conflicting spec pages. Both should be confirmed with a current signed datasheet before a bid is finalized.