Wired's reporting frames the crash as the predictable outcome of an institutional failure: the DoD jams GPS across thousands of square miles while the FAA leaves GPS-based instrument approaches published and active into affected airports. The gap between what pilots are told to expect via NOTAM and what actually happens to the electromagnetic spectrum overhead is presented as the direct causal link to at least one fatal crash and hundreds of anomaly reports.
By submitting the Wired investigation to HN with the framing 'crash tied to military GPS blocking,' dzdt endorses the causal link between the DoD's jamming exercises and the civilian fatality. The submission amplifies the argument that the current coordination regime is unsafe.
The editorial argues that two decades of decommissioning VORs, NDBs, and ILS localizers in favor of WAAS/LPV approaches was built on the unspoken assumption that GPS is an always-on utility that degrades gracefully. That assumption is now demonstrably false over large portions of the continental US, meaning the safety win of GPS-based approaches has quietly introduced a systemic vulnerability the FAA has not reckoned with.
On a clear afternoon last year, a Cessna 210 went down near the edge of the White Sands Missile Range in New Mexico. The pilot, a 71-year-old with thousands of hours logged, was killed on impact. Wired's investigation, published this week, connects the crash to something the FAA and DoD have been doing quietly for years: deliberately jamming GPS signals across huge swaths of US airspace as part of routine military exercises.
The specific test window that day covered thousands of square miles and reached tens of thousands of feet — a volume of sky large enough to encompass entire commercial flight corridors, not just the range perimeter. The NOTAM (Notice to Air Missions) was on file. The pilot may or may not have seen it. What the FAA does not do, and this is the crux of the story, is disable the GPS-based instrument approaches into affected airports during these windows. The approaches remain published. The avionics still try to fly them. When the signal degrades or vanishes mid-approach, the autopilot's behavior depends on the box, the software version, and how the pilot has it configured.
Wired's reporting cites an escalating pattern: hundreds of pilot reports of GPS anomalies in the American Southwest, at least one previous fatal crash with a similar profile, and a growing gap between what the FAA tells pilots to expect and what the DoD is actually doing to the electromagnetic spectrum overhead.
The civilian aviation stack has spent two decades migrating away from ground-based navigation aids — VORs, NDBs, ILS localizers — toward GPS-derived procedures. WAAS-enabled LPV approaches now exist at thousands of small airports that could never justify an ILS install. This was, correctly, treated as a huge safety win. The unspoken assumption underneath it: GPS is a utility, always on, degrading gracefully.
That assumption is now demonstrably false over large portions of the continental United States, on a schedule the FAA publishes but does not enforce against. The DoD's testing tempo has increased sharply since 2022, driven by the very real need to prepare US forces for a battlefield where Russia and China jam and spoof GPS as a matter of course. Ukraine has been the loudest wake-up call — commercial drones, guided munitions, and even Starlink terminals have all been degraded by electronic warfare in ways that surprised Western militaries. The Pentagon's response has been to train harder at home. The side effect is that Cessnas fall out of the sky in New Mexico.
The cognitive dissonance here is worth naming. If a private tech company deliberately degraded a public safety-of-life signal on a published schedule and a fatal accident resulted, we would call it negligence and the executives would be deposed. When the DoD does it, the paperwork is in order, the NOTAM was filed, and the burden shifts to the dead pilot. The regulatory posture treats GPS jamming like weather — a hazard to be routed around — rather than like a controllable variable, which it obviously is.
The response from the receiver-manufacturer side is instructive. Garmin, uAvionix, and others have quietly been shipping firmware that handles jamming events more gracefully: annunciating loss of integrity faster, falling back to inertial dead-reckoning where hardware allows, refusing to arm approaches when signal quality is marginal. But there is no fleet-wide standard, no requirement, and no way for a pilot to know from the panel whether their specific box will tell them they've lost GPS or will silently coast on stale data for another 30 seconds.
This is a Wired story about aviation, but the second-order implications reach anyone building on GNSS. If you're shipping fleet telematics, autonomous vehicles, precision agriculture, drone delivery, high-precision surveying, or any timing-sensitive infrastructure that trusts GPS, the operating envelope you were designing against no longer matches the country you're operating in.
A few concrete implications. First, if your product's failure mode under GPS loss is "drift silently until the operator notices," that's now a defect, not a design choice. Cellular timing, network time protocol, and inertial fallbacks are not optional add-ons anymore. Second, if you're doing anything with RTK or PPP-derived centimeter positioning, model the jamming NOTAMs as scheduled downtime for your affected regions and set customer expectations accordingly — because pretending it's not happening is going to cost you a support ticket the first time a $400k combine wanders off a section line during a White Sands window. Third, if you're in the eVTOL, air-taxi, or BVLOS drone space, the FAA's current regulatory posture on GPS jamming is a material risk that belongs in your deck. The certification story for these vehicles leans heavily on GNSS-based navigation and detect-and-avoid. That story gets harder when the government itself is the jammer.
For security and infra folks: this is also a reminder that PNT (positioning, navigation, timing) is critical infrastructure with no meaningful redundancy in the US. eLORAN was funded, defunded, and refunded so many times over the last twenty years that no operational system exists. The rest of the world — China with BeiDou, Russia with GLONASS, Europe with Galileo — has been diversifying. American receivers can technically use those constellations, but our regulatory and procurement stance is still overwhelmingly GPS-first.
The short-term fix is boring and available: the FAA can and should suspend GPS-based approaches in the specific airspace and time windows the DoD is jamming, forcing avionics onto conventional navigation aids or grounding the flights. The medium-term fix is a receiver-integrity standard with teeth. The long-term fix is admitting that a single-constellation, single-frequency, unencrypted broadcast from thirty-year-old satellites is not a foundation you want under a modern economy — and building actual redundancy. None of that will move until enough of the wrong people die. The pilot in New Mexico was, apparently, not enough.
When I used to fly in Florida in the 2005-2015ish timeframe, NOTAMs for GPS interference (it didn't say that exactly but that's what it meant) were an everyday occurrence along my path, it became boilerplate. I experienced it a few times. One moment the GPS thinks you're plodding alon
Airline captain here... A visual approach to an airport in mountainous terrain on a moonless night is very risky.In our operation, departing to an airport with missing weather reports would not be permitted, so in a Part 121 scheduled service this flight may not have been able to dispatch legally.Ai
GPS is not essential to air navigation. It’s nice to have, and there are some approaches that legally require it to be operational in order to fly them (IFR procedures) but aviation has other systems in place to guide aircraft under conditions where visual flight navigation is impossible.In this cas
Missing from the article is that, once the pilots reported to ATC that GPS was inoperable, ATC was going to have them circle to the right and guide them along the ILS approach, which would've avoided the worst of the mountains. ATC also asked the military to stop GPS jamming, which they did for
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
I run GPSJAM.org, have been studying and tracking the effects of GPS interference on aviation for the past 5 years, and I was a source for this article. I'm not a pilot and I don't work for any aviation agency.I'm very curious to see what the final NTSB report says, but their prelimin