GNSS interference and the low-altitude economy
Delivery drones, air taxis and survey platforms now share airspace with interference that used to be a military-only concern. Civil certification is catching up.
What changed
GNSS interference used to be a military planning problem. The equipment that dealt with it was heavy, expensive and export-restricted, and civil operators never had to think about it.
Low-altitude commercial aviation changed the exposure. Delivery drones, inspection platforms, survey aircraft and now air taxis operate at altitudes and in places where interference is common — and they operate there continuously, on schedules, carrying value.
Where the interference comes from
Most of it is not aimed at you. Personal privacy jammers in vehicles, illegal repeaters, poorly filtered transmitters and industrial emitters all raise the local noise floor without anyone intending to attack an aircraft.
The deliberate part is growing too, and it concentrates in predictable places: borders, ports, large public events, and any area where drone activity is itself a security concern. If your routes touch those, you are not planning for a rare event.
Urban terrain makes it worse
Cities are hostile to GNSS before anyone jams anything. Buildings block satellites, reduce the visible constellation and reflect signals into multipath. Start from a degraded fix and it takes far less interference to push the receiver past the point of useful navigation.
This is exactly the environment air taxis and delivery platforms are being certified into, which is why anti-jamming is moving from an option to a design assumption.
What operators are doing about it
The practical answer is to stop treating GNSS as a single point of trust. Inertial and visual navigation cover short gaps, but they drift, and they cannot tell you that your position is wrong — only that you have lost the reference.
A controlled-reception-pattern antenna attacks the problem earlier, at the antenna, by refusing to receive the interference in the first place. It keeps the fix rather than replacing it, which is why it integrates without changing anything downstream in the autopilot.