GPS-Denied Drone Flight: What Jamming Does to Your Aircraft, and How to Respond

Losing GPS mid-flight is not rare, and it is not usually caused by an adversary. A nearby cell tower, a poorly shielded video transmitter, a passing car with an illegal personal GPS jammer, or simple obstruction from terrain and buildings can all pull satellite lock out from under a drone. What matters is knowing what your aircraft will do about it, because the automated response is not always the safe one.

The failure follows a predictable ladder, not a cliff

A drone loses navigation in stages, not all at once: first automatic position hold and braking go, then any secondary system like vision positioning takes over if it can, and only when every fallback is exhausted does the aircraft revert to raw attitude control with no automatic stabilization at all.

Compass and GPS faults are processed by the same navigation estimator on most flight stacks, so the symptoms overlap. A slow drift with the control sticks centered, a circular “toilet bowl” oscillation, or a sudden loss of position hold are all versions of the same underlying problem: the aircraft has stopped trusting its own position estimate. Treat any of them as the same emergency, because trying to diagnose the exact cause in the air wastes the time you need to respond.

DJI drones fall back to ATTI mode, and ATTI mode drifts

On DJI aircraft, losing a usable GPS signal while the vision system is also unavailable triggers Attitude, or ATTI, mode: the light on the aircraft blinks yellow, and the drone can no longer hover or brake on its own. It will drift with the wind at whatever speed the wind is blowing, and DJI’s guidance is to land as soon as possible rather than try to fight through it.

Two DJI behaviors surprise most pilots the first time they encounter them. The signal-loss trigger delay before ATTI engages varies by model, from about 3 seconds on some FPV-focused aircraft to 11 seconds on older Mini models, so two drones sitting side by side can react at different speeds to the same interference. And on enterprise aircraft like the Mavic 3E and 3T, altitude itself gets clamped under weak GNSS: the drone will not climb above roughly 10 feet (3 meters) in darkness or about 100 feet (30 meters) with adequate light, no matter what altitude the mission plan calls for. A survey flight planned at 200 feet will not fail loudly. It will simply refuse to climb, and the data will be wrong.

Vision positioning is the fallback that actually keeps a DJI drone stable through a GPS loss, and it has real limits worth knowing before you need them. DJI’s enterprise manuals put the working envelope at roughly 20 inches to 100 feet (0.5 to 30 meters) of altitude, over a surface with enough visual texture and at least 15 lux of light. Water, snow, and featureless pavement all defeat it. A dawn flight over a reservoir has no automated fallback at all if GPS drops.

Return-to-home is not the safety net most pilots assume

The instinct when something goes wrong is to hit return-to-home, and with GPS that instinct can backfire. RTH needs a working position fix to fly itself home, which is exactly what a GPS outage takes away. DJI’s own documentation states plainly that the aircraft may instead enter ATTI mode and land wherever it happens to be when RTH is triggered during degraded GPS.

The better sequence, drawn straight from DJI’s own troubleshooting guidance: keep the aircraft in visual line of sight, do not press RTH, expect drift and be ready to fly attitude mode manually, get the aircraft low over ground with good visual texture so vision positioning can re-engage, avoid Sport mode since it disables the vision system entirely on some models, and land as soon as it is safe to do so.

ArduPilot and PX4 give you real settings to check, not just defaults

Open-source flight stacks expose the failure behavior as configurable parameters, and most pilots never look at them until something has already gone wrong.

On ArduPilot, FS_EKF_ACTION controls what happens when the position estimator’s confidence collapses, and it defaults to landing the aircraft. A newer dead-reckoning failsafe, added in Copter 4.3, lets the aircraft coast on inertial data alone for a configurable window, but ArduPilot’s own documentation is honest that 10 to 30 seconds is the realistic ceiling for that kind of unaided flight. Anything longer is not something the parameter can promise you.

On PX4, the equivalent setting is COM_POS_FS_ACT, and it is worth knowing which value your aircraft is set to before you fly it commercially: one option descends the aircraft, the other terminates the flight outright. The geofence configuration matters here too, since GF_SOURCE decides whether the fence is evaluated against raw GPS or the flight computer’s best estimate, and a corrupted position reading can trigger a geofence action that never should have fired.

What to actually do when it happens

Maintain visual line of sight and fly the aircraft yourself rather than trusting an automated function that depends on the exact system that just failed. Get the drone low over textured, well-lit ground so any vision-based fallback can re-engage. Land as soon as it is practical, and do not switch to a performance mode that disables secondary positioning systems to save a few seconds of flight time.

Afterward, export the flight log before doing anything else. Note the time, your location, and how many satellites the aircraft was tracking when the problem started, since that is exactly the information the FAA’s GPS anomaly report asks for and the detail you will not reconstruct accurately from memory a day later.

For the regulatory backdrop, the FAA hub tracks the rules this sits inside, and our 400-foot altitude guide covers the airspace rules that apply regardless of what your GPS is doing. The counter-drone technology hub covers the other direction: what happens when the interference is deliberate.