AINEWS
NTSB says GPS jamming contributed to the May 13, 2026 crash of a King Air air ambulance flight near White Sands. The military's only notice to pilots was a PDF on a portal.
On the night of May 13, 2026, a twin-engine Beechcraft King Air took off from Roswell on a 60-mile medevac (medical-evacuation / air-ambulance) hop to Ruidoso. Two pilots, two flight nurses, a half hour in the air, 69°F and clear sky. The crew lost GPS, reverted to older navigation equipment they rarely used, and flew into the Capitan Mountains. No one survived.
The cause the NTSB identified in its preliminary report is not weather. It is a US military GPS-jamming exercise out of White Sands Missile Range, a vast US military testing range in southern New Mexico where DoD units train against simulated electronic-warfare threats. The AP, AOPA, and KOB ran the same finding. The NTSB's language matters: the interference "contributed to" the crash, not "caused" it. The disorientation is documented; the cascading sequence of decisions is still being built. Per the Wired feature that walked the NTSB file and the exercise footprint together, this is the first time GPS jamming has contributed to a US civilian plane crash, and the first fatal US civil aviation accident linked to electronic warfare.
Exercises like the one on May 13 are not new. The US military ran at least 10 GPS-jamming exercises in the past year. The gap is the deconfliction: no one is required to keep those training windows away from the medevac network, the one corner of civil aviation least able to absorb a GPS loss.
The FAA Safety Team did publish an advisory for the May 13 window at White Sands, notice WSMRNM 26-13. It lives on a Safety Team portal, not in a cockpit feed. There is no mechanism that ties an exercise notice to a medevac dispatch desk, or to the Part 135 air-ambulance operators that fly the rural Southwest on short notice into unfamiliar strips, often in marginal weather, often at night. The crew on the King Air was carrying a patient when they departed Roswell. They could not have queried the FAA Safety Team portal mid-dispatch.
Kreindler, a law firm that specializes in air-crash litigation, describes medevac accident rates as "more similar to combat flying than to civil aviation." That framing is an attributed claim, not an independent benchmark, and the firm's clients are plaintiff medevac families. But the structural point holds: short-notice dispatch, unfamiliar strips, marginal weather tolerances, and a workload profile that does not allow for routine navigation backup drills. Losing GPS in that flight profile is not the same as losing GPS in a Part 121 airliner, where the crew flies the same routes daily, has dispatch coordination, and operates under a different regulatory frame.
Earlier in 2026, New Mexico and Texas briefly closed airspace over the same region when Customs and Border Protection used anti-drone lasers that interfered with aircraft systems. The pattern is the same: a national-security asset generates a navigation hazard, and the response is a notice on a portal, a temporary airspace closure, or a finding after the crash. There is no real-time channel from a DoD training schedule to a medevac dispatch desk.
The electronic-warfare side is already aware of the bleed. Eliran Almog, CEO of the cybersecurity firm Cyviation, told Wired: "As drone warfare and electronic warfare expand, airlines are increasingly encountering navigation disruptions hundreds of miles beyond the actual conflict zone." The Capitan Mountains are hundreds of miles from any conflict zone. They are 60 miles from Roswell.
The NTSB finding points at a deconfliction pipeline that ends at a PDF. The FAA Safety Team advisory is the public-facing version. The DoD schedules the exercise. The medevac operator never gets the notice. The crew flies. The jamming is on. The crew loses GPS. The crew disorients. The crew flies into a mountain.
A real fix is a pipeline: an exercise schedule that flows from DoD scheduling into FAA airspace management, that triggers a NOTAM (FAA Notice to Air Missions) or a temporary flight restriction when the affected radius overlaps with a known medevac corridor, and that requires dispatch acknowledgement. That pipeline does not exist today. The FAA Safety Team advisory is the closest thing, and it sits behind a portal login that no medevac crew queries on dispatch.
The NTSB will issue a final report. The "contributed to" language will get litigated. The four people on the King Air will not fly again. The next medevac into Ruidoso, or into any other rural corridor under an exercise footprint, will still be dispatched on short notice into a GPS-denied environment with no real-time notification and no regulatory channel to demand one.