{"id":3477,"date":"2026-09-16T12:02:37","date_gmt":"2026-09-16T04:02:37","guid":{"rendered":"https:\/\/midradar.com\/?post_type=news&p=3477"},"modified":"2026-09-16T12:02:37","modified_gmt":"2026-09-16T04:02:37","slug":"low-altitude-surveillance-radar-explained-range-use-cases","status":"publish","type":"news","link":"https:\/\/midradar.com\/es\/news\/low-altitude-surveillance-radar-explained-range-use-cases\/","title":{"rendered":"Radar de Vigilancia de Baja Altitud: Alcance y Casos de Uso"},"content":{"rendered":"

Wu Kang<\/strong> | Radar System Specialist | Published September 16, 2026<\/p>\n

A low-altitude surveillance radar tracks UAVs, small aircraft, birds, and \u2014 on several models \u2014 ground or water targets moving below roughly 600 to 3,000 meters, at ranges from about 1.5 km for small drones up to 20 km for larger aircraft, depending on the target’s radar cross-section.<\/p>\n

\"\"

Low-Altitude Surveillance Radar Explained: Range & Use Cases<\/p><\/div>\n

What a Low-Altitude Surveillance Radar Actually Watches For<\/b><\/strong><\/h2>\n

This is a narrower category than the primary surveillance radar an air traffic control tower relies on, and a different problem from a ground surveillance radar aimed purely at the horizon. A low-altitude unit covers the airspace band where most of the actual security work happens: drone incursions, low-flying aircraft near a perimeter, birds that trigger false alarms on other sensors, and \u2014 because several models in this line double as ground radars \u2014 vehicles and vessels moving on the surface underneath that airspace.<\/p>\n

Compared with camera-only or fixed thermal-line perimeter setups, this class of radar extends warning time because detection doesn’t depend on line-of-sight optics or ambient light. A camera has to already be pointed at a threat to see it. A radar sweeping 360 degrees finds the track first and hands a bearing to whatever sensor looks next.<\/p>\n

Why Doesn’t Every Radar List the Same Range?<\/b><\/strong><\/h2>\n

The common mistake in reading a radar spec sheet is treating “detection range” as one number that applies to everything the radar can see. It doesn’t. Range depends on the target’s radar cross-section (RCS) \u2014 roughly, how much radar energy a given target reflects back. A truck or a small boat reflects far more energy than a consumer drone, so the same radar publishes very different ranges for each.<\/p>\n

Take the MR-RDT20K. Its general-target range is 20 km, and that same 20 km figure applies to vehicles and helicopters. Point it at a small UAV instead, and the published range drops to 10 km \u2014 half the distance, same radar, because a small drone’s RCS is a fraction of the reference target used for the general figure. The MR-RDA10K-4R spec sheet goes a step further and adds a weather qualifier: its 10 km small-UAV figure is listed specifically for clear weather. Midradar’s literature describes adaptive clutter suppression for filtering rain, waves, and background motion, but that’s a mitigation for false tracks, not a guarantee that published range holds in a downpour.<\/p>\n

The practical takeaway for anyone comparing radars: ask which target class and which environmental condition a published range number assumes, not just what the number is.<\/p>\n

\"\"

Low-Altitude Surveillance Radar Explained: Range & Use Cases<\/p><\/div>\n

Eight Radars, One Spec Table<\/b><\/strong><\/h2>\n

The table below covers Midradar’s published low-altitude line as it currently appears on the company’s product pages. RCS and weather qualifiers are kept exactly as published rather than smoothed into a single “detects up to X km” claim.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Modelo<\/b><\/strong><\/td>\nScan architecture<\/b><\/strong><\/td>\nGeneral \/ large-target range<\/b><\/strong><\/td>\nMedium-class target<\/b><\/strong><\/td>\nSmall-UAV range<\/b><\/strong><\/td>\nMax altitude<\/b><\/strong><\/td>\nSimultaneous tracks<\/b><\/strong><\/td>\nAlimentaci\u00f3n<\/b><\/strong><\/td>\n<\/tr>\n
MR-RDT02K<\/a><\/td>\n3D Ku-band, mechanical + DBF<\/td>\n3.5 km<\/td>\nMedium UAV \u22653.5 km (RCS 1 m\u00b2)<\/td>\n\u22651.5 km (RCS 0.01 m\u00b2)<\/td>\n600 m<\/td>\n\u2265100<\/td>\n\u2264120 W<\/td>\n<\/tr>\n
MR-RDT05K<\/a><\/td>\n3D Ku-band, mechanical + DBF<\/td>\n5 km<\/td>\nMedium UAV \u22655 km (RCS 1 m\u00b2)<\/td>\n\u22653 km (RCS 0.01 m\u00b2)<\/td>\n600 m<\/td>\n\u2265200<\/td>\n\u2264180 W<\/td>\n<\/tr>\n
MR-RDT10K<\/a><\/td>\n3D X-band, mechanical + DBF<\/td>\n10 km<\/td>\nVehicle\/helicopter \u226510 km<\/td>\n\u22655 km<\/td>\n1.000 m<\/td>\n\u2265200<\/td>\n\u2264260 W<\/td>\n<\/tr>\n
MR-RDT12K<\/a><\/td>\nX-band 9.8\u201310 GHz, mechanical + DBF<\/td>\nVehicles\/ships\/helicopters \u226525 km<\/td>\nPersonnel \u226515 km<\/td>\nDJI Phantom 4-class UAV \u226512 km*<\/td>\n\u22643,000 m<\/td>\n\u2265500<\/td>\nNot published<\/td>\n<\/tr>\n
MR-RDT18K<\/a><\/td>\n3D X-band, mechanical + DBF<\/td>\n15 km<\/td>\nVehicle\/helicopter \u226515 km<\/td>\n\u22658 km<\/td>\n2.000 m<\/td>\n\u2265300<\/td>\n\u2264330 W<\/td>\n<\/tr>\n
MR-RDT20K<\/a><\/td>\n3D X-band, mechanical azimuth + DBF elevation<\/td>\n20 km<\/td>\nVehicle\/helicopter \u226520 km<\/td>\n\u226510 km<\/td>\n3.000 m<\/td>\n\u2265500<\/td>\n\u2264400 W<\/td>\n<\/tr>\n
MR-RDA10K-4R<\/a><\/td>\nX-band 2D phased array, monopulse<\/td>\nVehicles\/ships \u226515 km<\/td>\nPeople \u226512 km<\/td>\n\u226510 km, clear weather**<\/td>\nNot published<\/td>\n\u2265500<\/td>\nNot published<\/td>\n<\/tr>\n
MR-RDA15K-4R<\/a><\/td>\nFour-array 2D AESA<\/td>\nVehicle\/helicopter \u22658 km<\/td>\n\u2014<\/td>\n\u22655 km<\/td>\n1,500 m<\/td>\n\u2265500<\/td>\n\u22641.6 kW total<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

*MR-RDT12K’s small-target figure is published against a named consumer drone class rather than a stated RCS value, so it isn’t directly comparable to the RCS 0.01 m\u00b2 figures used elsewhere in this table.<\/p>\n

**A second published product page for the MR-RDA10K-4R lists materially different specifications under the same model name. Treat both pages as provisional and request the current signed datasheet before putting any RDA10K-4R figure into a tender document.<\/p>\n

Two Scanning Approaches Behind These Numbers<\/b><\/strong><\/h3>\n

The RDT-series units scan mechanically: a rotating antenna combined with digital beamforming (DBF) on elevation gives 360-degree coverage by physical rotation, which is why MR-RDT12K and MR-RDT20K both list a flat 360-degree azimuth figure. It’s a simpler, lower-power design, and it’s why this sub-line runs from 120 W up to 400 W rather than into the kilowatt range.<\/p>\n

The RDA-series units use a four-array phased design instead. Each face steers electronically and covers roughly 90 degrees on its own; stitched together, the four faces cover the full circle. MR-RDA10K-4R states this explicitly \u2014 90 degrees per face, 360 degrees as a system \u2014 which is useful precision, but it also means a buyer has to read the per-face number and the system number as two different things rather than assuming one radar head equals one coverage figure.<\/p>\n

How Radar Cues the Camera: Slew-to-Cue Integration<\/b><\/strong><\/h2>\n

A radar track by itself is a bearing, a range, a speed, and sometimes an altitude \u2014 not a picture. Midradar’s radar-EO fused products, such as the MR-RD02SE-DMS15-AU Radar-EO Detection System, pair one of the radar heads above with visible-light imaging, infrared thermal imaging, and a servo pan-tilt, run through the RGS2000 platform.<\/p>\n

The handoff between radar and camera works in roughly five steps:<\/p>\n

    \n
  1. The radar detects a track crossing a configured threshold \u2014 range, speed, or a defined zone.<\/li>\n
  2. Track data (bearing, elevation, speed) passes to the platform software in real time.<\/li>\n
  3. The platform commands the pan-tilt unit to slew the EO payload to that bearing automatically. Midradar’s own material calls this “radar-EO intelligent slew-to-cue.”<\/li>\n
  4. The camera zooms to the target’s range and an operator, or the platform’s AI target recognition where it’s deployed, confirms whether the track is a drone, a bird, a vehicle, or a false detection.<\/li>\n
  5. Confirmed threats get logged and can trigger an alarm, or an acoustic\/optical deterrent response, through the same platform.<\/li>\n<\/ol>\n

    Whether this integrates cleanly with an existing security stack usually comes down to protocol support before it comes down to radar range. Midradar’s platforms support GB\/T 28181, ONVIF, and RTSP for connecting to third-party video management or command-and-control systems, along with RESTful APIs and SDKs for tighter integration work. Checking that list against whatever VMS or C2 platform is already running is worth doing before a spec is finalized, not after.<\/p>\n

    \"\"

    Low-Altitude Surveillance Radar Explained: Range & Use Cases<\/p><\/div>\n

    Where This Gets Deployed<\/b><\/strong><\/h2>\n