SUNPOO
Back to News

November 9, 2026

How to Specify Low-Altitude Surveillance Radar for Counter-UAV and Perimeter Airspace

A procurement-focused guide to specifying low-altitude surveillance radar for counter-UAV and perimeter airspace, covering detection physics, radar-video fusion, site geometry, verification, and supplier questions.

How to Specify Low-Altitude Surveillance Radar for Counter-UAV and Perimeter Airspace

Why Low-Altitude Surveillance Radar Is a Specification Problem, Not a Catalog Purchase

Low-altitude surveillance radar detects, identifies, and tracks slow, small targets such as micro-UAVs in the airspace above and around a protected site. It is the sensing layer of a counter-UAV or perimeter airspace system, not the whole system. The hard part is not choosing a radar; it is specifying one that fits the site's geometry, target profile, and operating environment, then verifying that fit before deployment.

This guide is written for procurement and security engineering teams moving from consideration to supplier evaluation. It focuses on the decisions you must make, the evidence to request, and the trade-offs that determine whether a radar deployment works in practice.

Start With the Threat and Site Model, Not the Hardware

Radar performance is meaningless without a defined target and a defined volume of airspace. Before comparing models, document the following.

  • Target class: Micro-UAVs, fixed-wing small UAVs, and birds differ in radar cross-section, speed, and flight profile. A radar tuned for slow small targets behaves differently from one optimized for faster, larger targets.
  • Approach corridors: Identify the directions from which a drone could realistically approach. A site surrounded by tall buildings or terrain has different blind-zone risks than an open perimeter.
  • Protected volume: Define the airspace you need to monitor in three dimensions: maximum range, minimum altitude, and elevation coverage. A 360° azimuth claim does not describe elevation coverage.
  • Clutter environment: Ground clutter, vegetation, water, and urban structures all generate returns. The radar's environmental adaptability and clutter-rejection design matter more than a single detection-range figure.
  • Response model: Decide what happens after detection. If the radar feeds an alarm, a camera slew, or a countermeasure system, the interface and latency requirements belong in the specification.

A useful discipline is to write a one-page site model before reading any datasheet. If a supplier's claims cannot be mapped to that model, the comparison is not yet meaningful.

Detection Physics: What LFMCW, FMCW, and Phased Array Actually Change

Radar architecture determines how the system handles small, slow targets in cluttered environments. Three terms appear repeatedly in counter-UAV radar specifications.

LFMCW and FMCW

LFMCW (linear frequency-modulated continuous wave) and FMCW (frequency-modulated continuous wave) radars transmit continuously and measure range from frequency differences. For low-altitude surveillance, the practical implications are short measurement cycles, low peak transmit power, and suitability for detecting slow small targets. Continuous-wave designs are commonly used in compact drone-detection radars because they can maintain track on low-speed targets without the blind ranges associated with some pulsed designs.

DBF and two-dimensional phased array

DBF (digital beamforming) and two-dimensional phased-array architectures shape and steer beams electronically. This affects how quickly the radar can revisit a sector, how it forms elevation coverage, and how it manages multiple targets. A two-dimensional phased array can support multi-face assembly for 360° coverage, which is relevant when a single radar face cannot cover the required airspace.

What the architecture does not tell you

Architecture labels do not by themselves establish detection range, false-alarm rate, or track quality. Those depend on antenna design, processing, installation height, and the environment. Treat architecture as a filter for shortlisting, not as proof of performance.

Single-Face, Multi-Face, and Radar-Video Fusion Configurations

Low-altitude surveillance deployments generally fall into three configuration patterns. The right choice depends on site geometry, response requirements, and how much confirmation the operator needs before acting.

Configuration Typical fit Key trade-off Evidence to request
Single-face radar Sector coverage, corridor monitoring, or sites where one approach direction dominates Limited azimuth coverage; blind sectors must be mapped Azimuth and elevation coverage pattern; installation height assumptions
Multi-face radar assembly Sites requiring 360° azimuth coverage with defined elevation limits More installation points, cabling, and synchronization complexity Face-to-face calibration method; coverage overlap and null zones
Radar-video fusion system Operators who need visual confirmation before escalation, or sites with high nuisance-alarm cost Higher integration and tuning effort; camera coverage must match radar coverage Fusion logic, alarm workflow, and how the system handles radar-only tracks

Radar-video fusion pairs radar tracks with electro-optical or multi-spectral cameras so that an operator sees both the track and the object. The value is confirmation and reduced nuisance alarms, not longer detection range. If camera coverage does not overlap the radar's detection volume, the fusion benefit is partial.

Site Geometry and Installation: Where Most Deployments Are Won or Lost

Radar coverage is shaped by installation height, nearby structures, and ground conditions. Two sites with identical radars can produce very different results.

  • Height: Mounting height affects minimum detectable altitude and the size of the ground-clutter region. A higher mount can improve low-altitude coverage but may expose the radar to more distant clutter.
  • Obstructions: Buildings, towers, and terrain create shadow zones. Ask the supplier to mark expected shadow zones on a site plan, not just quote a range.
  • Multi-face alignment: When using multiple radar faces for 360° coverage, alignment and synchronization determine whether the coverage is continuous or has seams.
  • Power and network: Confirm power availability, cable routing, and whether the radar processes tracks at the edge or sends raw data to a central system.
  • Environmental exposure: Wind loading, temperature range, and precipitation affect mounting and enclosure requirements. These are site-specific and should be confirmed with the supplier.

A supplier that cannot discuss installation geometry in concrete terms is a warning sign. Coverage claims that ignore mounting height and obstructions should be treated as marketing, not engineering.

Questions to Ask Before You Shortlist a Supplier

Use these questions to separate specification-grade suppliers from catalog resellers. The answers should be specific and testable.

  1. What is the detection range for a defined target class, and under what conditions was it measured?
  2. What is the azimuth and elevation coverage, and how does it change with mounting height?
  3. How does the radar handle ground clutter and slow-moving non-targets such as birds or vehicles?
  4. What is the false-alarm behavior in a representative environment, and how is it characterized?
  5. How does the radar integrate with cameras, alarm systems, or command-and-control software? What interfaces are supported?
  6. What does the installation and calibration process involve, and who performs it?
  7. What documentation is provided: coverage plots, interface specifications, installation drawings, and test reports?
  8. What are the environmental operating limits, and how are they verified?

Request written answers. Verbal assurances about performance are difficult to hold a supplier to during acceptance testing.

Verification: How to Test Before Full Deployment

Radar performance claims should be verified against the site model, not accepted from a datasheet. A staged verification approach reduces risk.

Documentation review

Ask for coverage plots, interface definitions, and any test data the supplier can share. Check whether the stated conditions match your site: target type, mounting height, and clutter environment.

Factory or bench demonstration

Where available, observe the radar tracking representative targets. Ask how the demonstration environment differs from your site.

On-site trial

An on-site trial with a representative target and realistic flight profiles is the most reliable evidence. Define pass/fail criteria in advance: detection probability in specified sectors, track continuity, and false-alarm count over a defined period.

Acceptance criteria

Write acceptance criteria into the procurement documents. Include the target class, approach profiles, sectors, and the measurement method. Without pre-agreed criteria, acceptance becomes a negotiation.

Warning Signs in Radar Procurement

  • Detection range quoted without target class, conditions, or measurement method.
  • 360° coverage claimed without elevation limits or installation assumptions.
  • No discussion of clutter, false alarms, or nuisance tracks.
  • Integration described only in general terms, with no interface specification.
  • Unwillingness to support an on-site trial or to define acceptance criteria.
  • Certifications or standards referenced without documentation.

None of these alone disqualifies a supplier, but a pattern of vague answers usually predicts a difficult deployment.

Where Low-Altitude Radar Fits Alongside Other Sensing

Low-altitude surveillance radar is one layer in a broader sensing architecture. Perimeter surveillance radar and ground penetrating radar address different problems and should not be conflated with counter-UAV airspace monitoring.

  • Counter-UAV radar: Detects and tracks small airborne targets. The focus is airspace intrusion detection and track continuity.
  • Perimeter surveillance radar: Detects ground-level intrusions along a boundary or fence line. The focus is ground clutter rejection and low false alarms.
  • Ground penetrating radar: Images subsurface features for survey, utility detection, or structural investigation. It is not an airspace or perimeter security sensor.

Some sites combine airspace and perimeter radar with a shared command interface. If that is your intent, specify the integration requirement early, because it affects interface choices and alarm logic.

Matching Radar Configuration to Site Type

The following patterns are common starting points. They are not prescriptions; each site still requires its own coverage analysis.

  • Critical site with a dominant approach corridor: A single-face radar covering the corridor, paired with cameras for confirmation, may be sufficient. Confirm elevation coverage for low-altitude approaches.
  • Site requiring full azimuth coverage: A multi-face assembly using two-dimensional phased-array radar faces can provide 360° azimuth coverage. Verify overlap and calibration.
  • Site with high nuisance-alarm cost: Radar-video fusion with multi-spectral electro-optics supports visual confirmation before escalation. Confirm that camera coverage matches radar coverage.
  • Border or linear perimeter: Coverage may follow the boundary rather than a circle. Ask for a coverage plan that reflects the actual geometry.

In each case, the specification should state the protected volume, the target class, the required response, and the evidence that will demonstrate performance.

Next Steps for a Radar Procurement

Move from reading to specifying. Build the site model, shortlist architectures against it, and ask suppliers for coverage plots, interface documentation, and a trial plan. Define acceptance criteria before you commit. If a supplier cannot answer the questions in this guide with specifics, that is useful information early in the process.