Counter Drone Jamming: How RF and GNSS Jammers Work

A jammer does not “break” a drone. It raises the noise floor at the drone’s receiver until the wanted signal can no longer be demodulated. The quantity that decides the outcome is the jamming-to-signal ratio (J/S) at the victim receiver:

Free-space path loss is a good first approximation. The ITU-R P.525 recommendation gives the standard closed form:

A simple illustration at 2.4 GHz: the pilot is 1 km from the drone and transmits 20 dBm, so the wanted signal arrives at about −80 dBm. The jammer sits 3 km from the drone and radiates 47 dBm into a 10 dBi antenna, so the jamming signal arrives at about −53 dBm. That is a J/S of roughly 27 dB in free space.

Real deployments never look that clean. The drone’s receive antenna is rarely pointed at the jammer, terrain and buildings add loss and multipath, the drone’s link may use spreading or hopping, and the jammer’s duty cycle and thermal limits cap sustained output. This is why datasheet range figures are quoted at a stated J/S and a stated victim signal level, and why you should treat any range number without those conditions with suspicion.

Time to effect is the second variable. Once the link is lost, the drone does not react instantly; it waits for its link-loss timeout before triggering failsafe. A well-built jammer reaches effective J/S within seconds, and the drone’s own timeout does the rest.

Two things follow from this table. First, a drone flying a preprogrammed route with no link to jam is only vulnerable through GNSS. Second, a jammer that covers only 2.4 and 5.8 GHz misses a large share of long-range and non-standard platforms, which is why wide-band coverage matters in practice.

The academic literature groups jammers into four strategies: constant, random, deceptive and reactive. In counter-drone hardware these map to a handful of practical signal types:

A practical jammer rarely commits to one type. A software-defined radio (SDR) architecture lets the operator select a signal type per channel and per band, and change it as the threat library changes.

Constant jamming transmits whether or not the target is communicating. Reactive jamming works the other way around: the unit watches the RF spectrum continuously and transmits only after it detects a target link — a drone’s control signal, for example.

Look-through is the periodic pause in transmission during which the jammer re-senses the spectrum: is the target still there, has it changed frequency, has its signal strength moved.

Why pause at all? Because the jammer’s own transmit power is far above the target signal it is trying to receive, and with finite TX/RX isolation the receive chain saturates on its own transmission. Listening while transmitting therefore needs either enough isolation — a separate receive antenna with good physical separation — or time division. Most implementations take the time-division route, which makes the length and frequency of the look-through window a key design parameter:

Reactive jamming comes down to a timing problem: the combined latency of detection, processing and transmit ramp-up has to be shorter than the target’s dwell time on a frequency, or the duration of a single burst. A hypothetical number shows why. If the target link stays on each hop for about 1 ms and the system needs 2 ms from detection to transmission, every jamming attempt lands on a frequency the target has already left, and the effect is close to zero.

This is why reactive jamming usually implements detection on an FPGA: a wide-band ADC samples, and a hardware pipeline performs the spectrum transform and the energy or feature detection, at far lower latency than software on a general-purpose CPU. The typical hardware chain is wide-band ADC, RF front end and FPGA.

Pure reactive leaves blind spots and pure constant is too blunt, so in practice hybrid jamming is common: hold constant or scheduled jamming on the bands where the high-threat links are expected, and run reactive on the rest. The same balance is considered the more even-handed approach elsewhere in electronic warfare, for instance against the remote triggers of improvised explosive devices.

Reactive jamming is not stronger jamming; it is cheaper and quieter jamming. Against wide-band jamming it is a complement, not a replacement.

Some points worth understanding:

The following table summarizes a representative fixed-site wide-band jammer, to show how the numbers on a datasheet fit together.

When comparing products, check these in order: instantaneous bandwidth and channel count (can it cover the bands you care about at once), power per channel and antenna gain (what EIRP you actually get), range conditions (J/S and victim signal level), and time to effect. Then ask whether the unit supports reactive mode, and what its reaction time is.

These are vendor-published figures and should be read as indicative. Overall, a drone jammer system lands between roughly $1,500 and $50,000+ for the jammer itself, and cost is driven by output power, number of bands, thermal design, and whether it can be cued by other sensors. Cost per neutralized threat is where those figures pay off: why jamming is the most cost-effective anti-drone strategy.

The same transmit power through a different antenna gives very different range and very different collateral interference.

The usual arrangement is a layered approach: wide-area detection plus omni jamming for warning and initial disruption of anything whose approach direction is unknown, with directional antennas layered on top for targeted mitigation of confirmed targets. It is also why directional jamming has to be cued by a detection system rather than aimed blind by hand.

A jammer that transmits continuously across everything is the bluntest tool. A better approach is to let detection systems drive it. Radar finds the target, RF detection identifies which frequencies it is using, and an electro-optical sensor confirms. The jammer then concentrates power on the target’s bands only, and slews a directional antenna onto it.

The benefits are practical: lower collateral interference to your own communications, lower duty cycle and heat, and a smaller electromagnetic footprint that gives away less about where you are. This is also why a standard interface to a command platform matters more than a small gain in output power. The detection half of that pairing is a selection problem in its own right — see how to choose a drone detection radar.

GNSS signals are extremely weak at the receiver, on the order of −130 dBm for GPS L1 C/A, below the thermal noise floor. Receivers recover them using the despreading gain of the code (about 43 dB for GPS C/A). A jammer therefore only needs to raise the in-band noise enough to eat that margin, and a modest transmitter can deny GNSS over a wide area.

The effect on a drone depends on its design. Many consumer drones lose position hold and drift, or cannot execute return-to-home. Survey and mapping platforms that rely on RTK lose their fixed solution. Platforms with visual or inertial backup may keep flying with growing error.

GNSS jamming denies the signal. A different approach is to feed the receiver false but plausible signals and let the platform act on a position fix that was never real. That mechanism, and the directional-redirection and signal-takeover tactics built on top of it, is the subject of a companion article in this series: GNSS spoofing.

Fixed-site jammers are used around critical infrastructure and industrial facilities where drones must be kept out of a defined airspace. Portable and backpack units serve mobile protection tasks such as VIP movements and temporary event security. Handheld units give small teams a directional option for short-range response. Integrated systems pair jamming with radar and optics for sites that need automatic detection and response. One constraint runs through all of them: outside narrow authorized use, transmitting a jammer is not a power a private operator holds — the FCC’s jammer enforcement page is one plain statement of the US position — which is why authorization and procurement shape these systems as much as the hardware does.

These projects are useful for the analysis, simulation and measurement side of RF and GNSS work:

Counter drone jamming is a link-budget problem first and a hardware problem second. The parameters that decide effectiveness are J/S at the victim receiver, instantaneous bandwidth, EIRP and time to effect. Reactive and look-through jamming buy precision at much lower power and exposure, but only if detection and response latency stay short enough. Its limits are equally clear: fiber-optic and GNSS-independent drones are outside its reach, and the strongest systems pair a jammer with detection so that power goes only where it is needed.