Drone defense,without the acronyms.

Counter-UAS, or C-UAS, is the practice of detecting, identifying, tracking and stopping uncrewed aircraft that enter airspace where they do not belong. A counter-drone system is normally layered: sensors find and classify the aircraft, an electronic layer denies its control or navigation link, and a physical effector is held in reserve for the few threats that keep coming.

The terms counter-UAS, counter-drone and anti-drone are used interchangeably in the industry. So are UAS, UAV and drone.

Four sensing methods are used together, because none is sufficient alone.

• Radar detects any physical airframe whether or not it is transmitting, and gives range and altitude.
• Passive RF detection listens for the control and video links. It can often identify the model and locate the operator — while emitting nothing at all.
• Electro-optical and infrared cameras confirm what the radar found and answer the question radar cannot: what is it, and is it carrying anything.
• Acoustic sensing is occasionally added at very short range.

Fusing radar with passive RF and imaging is what keeps the false-alarm rate low enough for a security team to act on.

It depends on the sensor and on the target. A small quadcopter has a radar cross-section of a few hundredths of a square metre, so detection range is far shorter than for crewed aircraft. Representative figures for the sensors we field:

• Ku-band surveillance radar — roughly 5 km against a small UAS
• X-band FMCW radar — about 20 km against larger fixed-wing types
• Passive RF direction finding — about 5 km, across 300 MHz to 6 GHz
• EO/IR turret with laser rangefinder — recognition at about 2,500 m

Terrain, clutter and weather all reduce these numbers. Treat any range quoted without a stated target size as marketing.

It means the counter-UAS system is installed, monitored, maintained and upgraded by the vendor for a recurring fee, rather than bought outright as a capital purchase. The site avoids the capital cost, the hiring problem and the refresh cycle. The operator provides the trained staff who watch the airspace and run the response playbook.

It suits civilian infrastructure — airports, data centers, utilities, refineries, stadiums — which needs the capability continuously but has no reason to build a counter-drone team in-house.

Jamming floods the frequencies a drone uses for control and video with noise, so the aircraft loses its link and falls back to whatever its firmware does next — usually hovering, landing, or returning to its launch point.

Spoofing, also called navigation deception, transmits false satellite navigation signals so the aircraft believes it is somewhere it is not, and flies accordingly.

Both are reversible: nothing is destroyed, and a mistaken engagement costs nothing but the alert. Both are also regulated, because they affect the radio spectrum around them.

Detection is almost always permitted. Interference and physical defeat usually are not — at least not for private operators. In most jurisdictions, transmitting on another party's control frequencies, interfering with satellite navigation, or damaging an aircraft in flight are restricted to designated government agencies, and even then only over specified sites.

This is why serious deployments are designed around the authorization boundary: detection and identification run continuously, while denial and defeat layers are installed but enabled only under the legal authority that applies to that site.

This is general background, not legal advice. Confirm your own position with counsel and with your national aviation and spectrum regulators before assuming any capability is usable.

Yes, and it has to. A radar that alarms on every gull is worse than no radar, because the security team stops believing it.

Classification uses the micro-Doppler signature of spinning rotors, which birds do not produce, combined with flight behaviour — drones hold headings, altitudes and speeds that birds do not — and confirmed against the RF picture and the camera. Bird-aware classification is the single biggest factor in whether an airport will tolerate a system running during operations.

The honest answer is that it depends on the perimeter, the terrain, and how far up the response ladder the site is authorized to go.

The more useful comparison is unit economics. A single legacy interceptor missile can cost over a million dollars; the drones it is fired at cost under fifty thousand each, often far less. That exchange rate is what makes traditional air defense unusable against this threat. A layered approach is built so the response always costs less than the thing it protects — which in practice means detection and reversible denial handle almost every incursion, and expensive effectors are rarely fired.

A site survey and RF map take days rather than months. Sensor masts that combine radar, imaging, jamming and navigation deception on one coaxial mount go up in about five minutes each, and a full site is normally commissioned within a week.

The long pole is almost never the hardware. It is the authorization, the integration with existing site security, and drilling the response playbook with the people who will actually run it.

The pattern is high consequence and low airspace control.

• Refineries and petrochemical plants, where ignition risk is unacceptable
• Substations and generation sites — exposed, unstaffed, load-bearing for everything downstream
• Data centers, concentrating enormous value under an open sky
• Airports, where a single sighting halts operations for hours
• Stadiums and events, where crowds rule out most responses
• Ports, rail yards and borders, where the footprint is too large to fence
• Correctional facilities, where contraband arrives over the wall rather than through the gate