How to Choose a drone detection radar

A counter-UAS radar isn’t a matter of “just buy the one with the longest detection range.” The core tension in selection is really a trade-off between three things — coverage angle, deployment speed, and budget. A fixed phased-array radar with 360° coverage can handle fast targets (up to 220 km/h), but its weight and power draw both climb. A man-portable folding radar can be set up in three minutes and run on battery for 4+ hours, at the cost of typically covering only a single 90° sector and focusing more on low-and-slow drones under 130 km/h. On price, a single-panel FMCW radar sits in the $30,000–$80,000 range, a single-sector phased array runs $80,000–$200,000, and a multi-panel array with full 360° coverage costs more still — and that’s just the radar unit itself, not system integration, C2 software, or mitigation equipment. The point that’s easiest to miss: a radar only “detects” — it can’t determine on its own who the operator is, whether they’re authorized, or what the payload is. That’s exactly why authoritative guidance such as the US military’s JIATF-401 stresses multi-sensor fusion rather than worshiping a single radar’s spec sheet.

A few years ago we deployed a system for an overseas client. The radar’s spec sheet looked great — detection range, update rate, and target speed coverage all met the mark. But once the gear was up on site, we discovered the client’s tower could only carry 5 kg-class equipment and no power line had been provisioned; in the end we had to fall back on a low-power directional array radar and just barely strap it on.

That episode taught us something: radar selection is never “pick the best one off the spec sheet” — it’s about first working out how the deployment environment will constrain your choices. This article follows that logic: principles and categories first, then how to read the specs, and finally “which type should your scenario pick.”

A radar works in a very direct way: it actively transmits electromagnetic waves, receives the echoes reflected back by a target, and uses the echo’s time delay and Doppler shift to calculate range, speed, and bearing.

When buyers compare different radars, the first numbers they usually look at are these: detection range, operating frequency band, update rate, azimuth coverage, target speed coverage, minimum detectable RCS, false alarm rate (CFAR configuration capability), simultaneous target tracking count, data interface, power consumption, and operating temperature range.

On frequency band there’s a common trade-off: 24 GHz has a shorter range but performs better in complex clutter; 10 GHz reaches farther but has slightly weaker clutter rejection. Choosing 10 GHz or 24 GHz is essentially a question of “range” versus “environmental adaptability” — there’s no absolute right answer.

The measured specs below come from one vendor’s public datasheet (model information withheld; given only as a reference for parameter ranges, not an endorsement). They make the typical differences between the “fixed/integrated” and “portable folding” forms of the same type easy to see at a glance:

You can see that the fixed radar trades a wider operating temperature range and a 220 km/h speed ceiling for the ability to “watch year-round”; the portable one trades “single-panel ≥90° coverage + minute-level setup + battery power” for mobility, with its speed ceiling correspondingly narrowed to low-and-slow scenarios under 130 km/h. When selecting, don’t fixate on a single number like detection range — coverage angle and deployment speed are often a see-saw trade-off.

As a rough reference, detection ranges break down like this: portable/short-range radar about 300 m–1.5 km, mid-range 3D micro-Doppler radar about 3 km-class, and long-range pulse Doppler radar about 5–20 km (some vendors claim up to 20 km; the model datasheet is authoritative in practice).

Rather than listing specs, clients more often show up with a specific scenario and ask “which one should I buy?” Below are the four typical scenarios we’ve summarized, with the corresponding recommendations:

One reminder: the fourth scenario is no longer purely a “radar selection” question — it’s an integrated system bundling radar + EO + jamming. Before purchasing, be clear about whether you want detection capability or a complete closed-loop mitigation capability; the two have completely different procurement logic.

The prices here are for the radar hardware itself, excluding system integration, installation, and training; the actual figure is subject to quotation:

⚠️ One important point: this is only the price of the radar unit — it does not equal the total budget for a complete detect-and-mitigate system. A full system (including software integration, a C2 platform, and possibly mitigation equipment) has a very wide total cost span, from entry-level solutions in the tens of thousands of dollars to full-spectrum military solutions in the millions, plus the additional costs of system integration, installation and commissioning, and personnel training.

One market phenomenon worth noting: not every vendor follows the “sell the radar as a standalone unit” model common in Europe and the US. A considerable share of solutions on the market bundle radar, EO, jamming, and spoofing directly into an integrated directional counter system, with a standard configuration that often includes radar + EO channel + jamming module + spoofing module + control software, and detection range, jamming range, and spoofing range each labeled separately. These products answer a client’s “turnkey” procurement need, which isn’t entirely the same logic as the “standalone radar selection” discussed in this article — before purchasing, it’s best to be clear about whether you’re buying a “radar” or an “integrated system.” They are two different decision paths.

The conclusion is straightforward: high-security scenarios usually deploy radar and RF together — the two are complementary, not substitutes for each other. For a broader look at where this fits, see our overview of what types of drone detectors exist.

Most radar vendors provide UDP/TCP interfaces that push target plots/tracks, and the vast majority of teams take the route of secondary development on the vendor SDK. On the software side there are mainly three things to do: protocol parsing, coordinate transformation, and multi-radar fusion and deduplication.

Commonly used Python libraries include: numpy/scipy (for processing raw echoes, mostly in self-developed scenarios), filterpy (Kalman filtering for target tracking), and scikit-learn/pandas (track data processing and micro-Doppler feature classification). More detail on multi-sensor fusion and system deployment will be covered in a later article on device integration.

Once more, the distinction raised at the start of this article: radar “detection” of drones is unrestricted in most countries and regions, but “mitigation” based on detection results (jamming, protocol hijacking, etc.) is strictly limited by law, usually reserved for authorized agencies only — these two lines must be kept clearly separate, both in this article and in procurement conversations, to avoid clients conflating them.

Separately, a radar is itself an active RF-transmitting device, so its own spectrum-use license / type approval is another independent compliance line, distinct from the authorization to use mitigation equipment. Before purchasing, you need to verify the specific requirements of the local radio regulatory authority.