A military GPS-denial exercise was active when a medevac plane lost navigation over New Mexico on May 14. The air traffic controller asked the military to stop jamming. Several aircraft needed help. The signal returned, the crew reported the lights of Ruidoso in sight, and the controller cleared a visual approach. The military resumed jamming. Five minutes after that visual report, the Beechcraft C90 hit the Capitan Mountains. Pilots Keelan Clark and Ali Kawsara and flight nurses Jamie Novick and Sarah Clark died.
The National Transportation Safety Board has not assigned probable cause. Its preliminary report establishes the operational chain: scheduled interference, loss of GPS, controller vectors, a temporary stop request, a visual approach over moonless terrain, resumed jamming, descent below the surrounding ridge, impact, and a wildfire.
Recent coverage here followed a telecom timing defect into emergency calls, trains, and payments. This case adds a materially different failure. The GPS signal was deliberately denied by one public authority while another public system had to absorb the consequences in real time. New reporting from IEEE Spectrum and WIRED exposes the control boundary behind the NTSB sequence: electronic-warfare training can project hundreds of miles beyond a military range, yet civilian crews and controllers carry the degraded-navigation workload.
the warning covered half a region
The flight left Roswell Air Center at 11:52 p.m. for Sierra Blanca Regional Airport near Ruidoso. It was a short Part 135 mission to collect a patient. The night was clear and completely moonless. The destination airport’s automated weather system was out of service.
The crew’s ForeFlight briefing contained both conditions. It also contained the GPS interference notice. The NOTAM warned that GPS, WAAS, GBAS, and ADS-B might be unavailable inside a radius of 366 nautical miles at high altitude, 240 nautical miles at 10,000 feet, and 210 nautical miles even at 50 feet above ground. The scheduled window covered the accident flight.
A warning that broad is evidence of a known blast radius. It does not make the airspace safe. It transfers interpretation to every pilot and dispatcher crossing the region, including short-notice medical crews flying at night into mountain airports.
At midnight, the crew reported that it had lost GPS and asked Albuquerque Center for a heading. The plane had climbed 1,000 feet above its assigned altitude. ADS-B reporting, normally arriving every two or three seconds, had fallen to roughly one-minute intervals. The controller supplied headings and began arranging an ILS approach that did not depend on GPS.
Three other aircraft reported GPS loss during the same period. One had trouble identifying a ground-based navigation aid. The controller was now doing two jobs: separating traffic and substituting for navigation systems disabled by a military test.
a stop button without ownership
The stop request deserves more attention than the jammer. A controller could ask for interference to stop, and the military complied. That sounds like a safety mechanism. The sequence shows its limits.
The NTSB report does not say whether the pilots were told that jamming had stopped or resumed. The controller told the military that the flight had gone visual, then authorized the test to restart. A visual approach removed the aircraft from the instrument-approach procedure. It did not remove the surrounding 10,000-foot mountains, the moonless night, the pilots’ recent navigation disruption, or the controller’s reduced ability to watch the plane through normal ADS-B intervals.
The airplane began descending toward the airport lights. The Capitan Mountains stood between the aircraft and Sierra Blanca. Tracking data recorded a descent to about 9,400 feet, followed by a climb. The aircraft struck rising terrain near 9,950 feet, roughly 230 feet below the summit radio facility.
Responsibility will be divided in the final investigation. Pilot decisions, training, crew experience, air traffic control, the unavailable destination weather system, terrain awareness, company procedures, and the interference exercise all belong in the analysis. The preliminary evidence does not support pinning the crash on one switch or one person.
It does support a systems claim. The agency creating the degraded environment did not own the degraded operation. Controllers became the human fallback. Pilots had to change approach systems under pressure. Civilian surveillance quality fell. The military received a stop request, then a restart message, while the aircraft was still airborne in the affected terrain.
the backup system was people
The FAA’s Aeronautical Information Manual tells operators to preserve navigation independent of GPS for many IFR operations because interference and test events have become more common. The New Mexico flight had alternatives. It requested an ILS approach. The controller could provide radar vectors. The crew later chose a visual approach.
Each backup carried hidden requirements. Ground-based navigation demands current proficiency and functioning local facilities. Radar vectors consume controller attention. Visual flight at night over sparsely lit mountains requires a usable horizon and reliable terrain awareness. A NOTAM can list these dependencies. It cannot manufacture spare cognition in a cockpit or control center after the primary system disappears.
IEEE Spectrum reports that White Sands interference has affected aircraft more than 500 kilometers from the range. Its earlier investigations found reports of aircraft drifting off course, entering military airspace, losing navigation, and increasing controller workload. Anonymous safety reports from 2021 and 2024 warned that stop requests could be delayed or refused. One controller wrote that someone would get hurt if managers kept deciding how much equipment could fail before jamming stopped.
Those reports describe institutional normalization. When interference is routine, the exceptional condition becomes another item in a briefing package. Controllers learn to route around it. Pilots learn that satellite navigation may vanish. Managers learn that halting a test is expensive. The system appears resilient because people keep catching the fault.
Then the fault arrives during a moonless medevac flight with an unavailable weather station, several affected aircraft, young pilots, mountain terrain, and a controller splitting attention. Resilience assembled from warnings and heroics has no reserve when the conditions stack.
electronic warfare needs a civilian safety case
GPS denial is now a normal military requirement. Cheap drones use satellite navigation. Jamming and spoofing are basic countermeasures. White Sands exists to test weapons and navigation in contested environments. Civilian aviation cannot wish that mission away.
The answer begins with forcing the test owner to carry the external risk. A credible civilian safety case would define interruption thresholds before a test starts, use live monitoring for the actual interference footprint, prevent restart until affected aircraft are on the ground or clear of terrain-critical phases, and give controllers direct authority to sustain a stop without negotiating test cost. It would treat degraded ADS-B, multiple GPS-loss reports, unavailable destination systems, medevac status, and night mountain operations as cumulative risk inputs.
Airspace restrictions may also need to match the physical field. A jammer whose effects reach hundreds of miles creates a regional condition. Publishing a notice while leaving normal operations in place pushes a military test’s cost onto dispatchers, crews, patients, controllers, and passengers who gain nothing from the exercise.
The NTSB will eventually decide what caused this crash. The public does not need to wait for that finding to see the governance defect. One agency intentionally removed a navigation layer from shared airspace. Another agency and every aircraft inside the footprint were expected to degrade gracefully. The stop path existed. Ownership of the degraded system did not.