In December 2018, repeated drone sightings shut down London's Gatwick Airport for more than a day. Around 1,000 flights were canceled or diverted and roughly 140,000 passengers were affected. The airport knew drones were present. What it could not do was track them: nobody could say with confidence whether it was one drone or several, where they were at any given moment, or where the operator was standing. That gap between knowing a drone exists and knowing exactly where it is and where it is going is the difference between detection and tracking, and closing it is the entire job of drone tracking radar.
Detection is the easy half. A radar return that flags an object in the airspace is a starting point, not an answer. Tracking is the hard half: holding a continuous, updating line on that object as it moves, predicting where it goes next, and keeping it in custody long enough to make a decision and respond. This guide explains what separates a radar that merely detects from one that truly tracks, how tracking radar hands a target to a camera for identification, why tracking many drones at once is harder than tracking one, and where the limits are. We build multi-sensor systems where radar tracking is the backbone of situational awareness.
The clearest way to frame the distinction comes from the counter-UAS field itself. As one systems integrator puts it, detection answers the question is there a drone here, while tracking answers the harder question of where is it going and whether you can keep it in custody long enough to respond. A single detection is a dot on a screen that appears and vanishes. A track is a continuous line that shows the drone's path, its current position, its heading, and its speed, updated many times per second.
That continuity is what converts data into intelligence. A drone detected once tells you almost nothing actionable. A drone tracked over time tells you its intent: whether it is loitering over a fuel farm, circling a stadium, transiting straight through your airspace, or climbing into an approach corridor. Two drones at the same location look identical as isolated detections. As tracks, one might be a hobbyist passing through while the other makes repeated passes over a restricted zone. Only tracking reveals the difference, and the difference is the whole basis for a response.
The single most important factor separating a detection radar from a tracking radar is update rate, also called revisit time: how often the radar refreshes its picture of a given point in the sky. A mechanically rotating radar sweeps its antenna in a circle and sees any given target only once per rotation. Between sweeps, a fast, erratic drone moves unseen, and the track can break. This is why the highest-performing drone tracking radars use electronically scanned or staring designs that revisit targets far more frequently.
Purpose-built tracking radars are engineered around this. Active electronically scanned array (AESA) radars steer their beam electronically with no moving parts, providing simultaneous multi-target track-while-scan across the full coverage volume. Staring radars illuminate their entire coverage area continuously for the fastest possible update rate. The most widely deployed military C-UAS radars now track hundreds of simultaneous targets with update rates sufficient for engagement-quality tracking. Beyond the hardware, tracking depends on the algorithm: software that associates each new return with the correct existing track and predicts where the target will appear next, so the system maintains a coherent path rather than a scatter of unconnected dots.
A radar that can hold a single track is not enough, because real incidents rarely involve a single drone. A swarm, or even two or three coordinated aircraft, will defeat a system that can only follow one target at a time. This is where multi-target track-while-scan matters: the radar maintains dozens or hundreds of independent tracks in parallel, each one updated continuously. Commercially available staring radars purpose-built for drones can track more than 100 targets at once while distinguishing drones from birds with AI-assisted classification.
There is an honest limit here worth stating plainly. Every radar has a finite tracking capacity, and a large enough swarm can saturate it. Counter-UAS analysis notes that overwhelming defenses with numbers exploits the fixed capacity of any radar to track and engage, and that decoys can force a system to spend attention on non-threats. Multi-target tracking dramatically raises the ceiling, but no radar is infinite. This is one more reason tracking radar is deployed as part of a layered system rather than as a lone sensor.
A tracking radar answers where the drone is, but not what it is. Radar provides wide-area volume search and a precise position, yet it cannot tell an operator whether the tracked object is a quadcopter carrying a payload or a large bird. A camera can make that identification, but a camera has a narrow field of view, the so-called soda-straw problem, and cannot scan the whole sky to find the target on its own. The mechanism that marries the two is called slew-to-cue.
The process is elegant. The radar detects a track and passes its three-dimensional coordinates, azimuth, elevation, and range, to an electro-optical and infrared camera on a pan-tilt gimbal, which automatically rotates to those coordinates to visually acquire the target. The operator does not search the sky manually. They are handed a verified visual track that the radar initiated. Once the camera has the drone in frame, it can auto-track and confirm identity, read a payload, and support a response decision. This radar-to-camera handoff is now the standard integration pattern across serious deployments, and it only works if the radar track is accurate and the positioner holding the camera can slew fast and precisely. A gimbal that loses a fraction of a degree of pointing accuracy during a high-speed slew can lose a small drone entirely, which is why tracking quality and mechanical precision matter as much as raw detection range.
In a complete system, the drone is being watched by more than one sensor at once, and each produces its own track. The radar has a track. If the drone is emitting, an RF sensor has one too. The camera has a third. The challenge, and the real work of a command-and-control platform, is correlating these into a single track. As fusion analysis explains, the system must correlate tracks across sensors with different update rates, coordinate frames, and error characteristics, determining that a radar track at one position and a camera track at a slightly different position represent the same physical object.
Done well, this delivers what operators actually need: one drone shown as one track, carrying its live radar position, its RF identity where available, and its camera confirmation, with the noise of overlapping alarms stripped away. That fused, continuous track is the difference between an operator managing a coherent airspace picture and one drowning in disconnected alerts. It is also what makes tracking useful for handoff, because a single clean track with a full history is what law enforcement and security teams can act on.
Radar tracking is powerful, but it is not flawless, and understanding where it struggles is part of designing around it. A drone flying tangentially to the radar, neither approaching nor receding, produces little radial velocity and can fall into what engineers call the Doppler notch, a blind zone where the target's motion is filtered out as if it were stationary clutter. Small radar cross-section, low-altitude clutter, and the saturation problem all apply to tracking as much as to detection.
None of these limits makes radar tracking optional. They make it one essential layer among several. The US Government Accountability Office has cautioned that some counter-drone technologies have a limited ability to detect and track small UAS under 55 pounds, and that clutter and birds can generate false detections. The answer is the same one that runs through every honest counter-drone discussion: layer radar with RF, cameras, and a fusion platform so that each sensor covers the others' blind spots. Our guide to how drone detectors work details how those layers combine.
The operational payoff of tracking is that it turns an alarm into a decision. A detection says something is out there. A track says this specific drone entered the northeast sector two minutes ago, has made three passes over the storage yard, is currently at 200 feet and 400 meters out, and is holding position. That is a picture a security team can act on. It supports intent assessment from the drone's own behavior, it enables a real-time drone track that can be handed to responders, and it produces a documented flight history that becomes evidence after the fact.
For cooperative drones, a fused track can also point toward the operator by combining radar position with RF direction finding, as covered in our RF detection guide. For the drones that emit nothing, the radar track and camera confirmation are the response, which is why continuous tracking is the connective tissue of the entire detect, track, identify, and respond sequence.
Any facility where a drone's flight path determines the threat needs tracking, not just detection.
Airports: Gatwick is the cautionary tale. Tracking across approach corridors and terminal airspace tells controllers whether a drone is a fleeting overflight or a sustained threat to operations.
Critical infrastructure and large events: Substations, refineries, and stadiums need to know a drone's trajectory to assess intent and coordinate a response. During the Paris 2024 Olympics, authorities using radar, cameras, and jamming intercepted 53 unauthorized drones near venues, a posture built on continuous tracking. Critical infrastructure sites increasingly require the same capability.
Detection equipment, including tracking radar, is covered at 100 percent federal funding for eligible agencies through the FEMA Counter-UAS Grant Program. For a view of the vendors building these systems, see our counter-drone vendor landscape, and for the military lineage of this technology, our guide to military drone detection.
Tracking a drone with radar is a passive sensing activity and is lawful for any organization in the United States. Actively defeating a tracked drone by jamming or interception remains restricted under federal law to the Departments of Defense, Energy, Justice, and Homeland Security, with narrow authorities extended to certain law enforcement agencies under the SAFER SKIES Act. For nearly every operator, a continuous track handed to the agencies that can act is both the lawful posture and the effective one.
Detection tells you a drone is somewhere in your airspace. That was never enough, as Gatwick proved when sightings alone shut an airport for a day and a half. What security teams need is custody: a continuous, updating track that shows where a drone is, where it has been, and where it is heading, held long enough to make a decision. Drone tracking radar, with a fast update rate, multi-target capacity, and a slew-to-cue handoff to cameras, is what delivers that custody for the physical airframe regardless of whether the drone is transmitting.
We believe the organizations that handle drones well stop asking whether they detected something and start asking whether they can track it well enough to respond. Radar provides the track. RF and Remote ID add identity. Cameras confirm it. A fusion platform merges the three into one clean picture. That is what continuous airspace awareness looks like, and tracking is the capability that makes all of it actionable.
Want to see how continuous radar tracking would cover your airspace? Talk to our team about a site survey for your facility.
Related reading:
Drone Detection Radar: How It Works, What It Costs, and Which Type You Need
How a Drone Detection System Works: Sensors, Software, and Coverage
How Drone Detectors Work: RF, Radar, Acoustic, and Camera Sensors Explained