NTSB Preliminary Report on Fatal New Mexico Air Ambulance Crash: A Night Medevac Lost in Military GPS Jamming

Published: September 9, 2026  |  Category: Industry

According to the aviation accident preliminary report WPR26FA186 released by the U.S. National Transportation Safety Board (NTSB), at 00:15 Mountain Daylight Time on May 14, 2026, a Beech C90 (King Air series, registration N249CP) was destroyed when it collided with terrain near Lincoln, New Mexico; both pilots and both passengers were fatally injured. The aircraft was operating an air medical transport mission from Roswell Air Center to Sierra Blanca Regional Airport (SRR) in Ruidoso, to pick up a patient for transport to Albuquerque. The airplane was operated by Generation Jets under FAR Part 135; the two passengers were flight nurses employed by Trans Aero Medical Services. The post-impact fire grew into a wildfire that, per the Aircraft Owners and Pilots Association (AOPA) report of June 18, 2026, took more than 1,000 firefighters nearly a month to extinguish and burned 31,860 acres (about 129 square kilometers). This is one of the deadliest accidents in U.S. air medical transport in recent years — and a keyword recurring throughout the preliminary report, GPS jamming, is now directing the industry's attention to a new class of risk.

1. The Accident Timeline: What Happened After GPS Was Lost

The NTSB preliminary report reconstructs the key moments of the night flight. At 23:01 on May 13, the crew received notification of the mission; the night was dark (0% moon illumination) with visual meteorological conditions. The airplane departed Roswell at 23:52 and was cleared "as filed" to SRR at 12,000 feet. Shortly after departure, ADS-B data recording degraded from its normal 2–3 second intervals to roughly one-minute intervals — a classic signature of GPS interference. At 00:00:26, the controller advised the crew that the airplane was at 13,000 feet, 1,000 feet above the assigned altitude; the pilot responded that they were correcting and that the airplane had "lost GPS capability," requesting a heading. The controller provided an initial heading of 275° toward SRR, and the crew requested the RNAV (GPS) approach to Runway 24. At 00:01:17, the controller telephoned the operations supervisor to request that the military "stop jamming." At 00:01:46 the flight was cleared to the REYOK intersection with a heading of 350° — but during the turn, and due to the loss of GPS navigation capability, the pilot requested the ILS approach instead. The airplane then continued on a northerly heading for about 20 nautical miles at a GPS altitude of about 12,600 feet; during this segment the controller was also serving three additional aircraft that reported loss of GPS, one of which had difficulty identifying a directed ground-based navigation aid and required extra assistance. Around 00:05 the operations supervisor contacted the military to stop jamming, and at 00:07:34 ADS-B recording returned to normal 2–3 second intervals. At 00:08:06 the crew reported "a visual on Ruidoso," was cleared for the visual approach, and said they would cancel IFR "in just a couple of minutes" — their final transmissions. Between the airplane and the airport lay the Capitan Mountains, rising to 10,201 feet, about 14 miles northeast of the airfield. Around 00:10, the operations supervisor informed the military that the airplane was on a visual approach and that jamming could resume; ADS-B again dropped to one-minute intervals. The airplane continued descending, made a slight right turn at 00:13:26 at 9,820 feet GPS altitude, and the last data point (00:15:26) recorded 9,823 feet and 150 knots groundspeed. The airplane impacted terrain at about 9,950 feet — roughly 730 feet east of and 230 feet below the Capitan Mountains Summit Radio Facility (elevation about 10,180 feet). AOPA's coverage adds a chilling detail: the crew was dispatched just after 23:00, leaving less than an hour for all preflight planning and inspection before launch; meanwhile the automated weather broadcast system (AWOS) at SRR was out of service, which disallowed use of either the GPS or the ILS approach to the airport — conditions under which the crew was nevertheless cleared for a visual approach.

2. GPS Jamming: How White Sands Missile Range Testing Spilled into Civil Aviation

The NTSB report states plainly: GPS jamming activities encompassing the area around the accident flight were being conducted by the United States military during the time of the flight. The crew's preflight briefing contained two critical NOTAMs: first, that the AWOS at SRR was out of service; second, that GPS (including WAAS, GBAS and ADS-B) "may not be available" within a 240-nautical-mile radius (below 10,000 feet) centered on coordinates within the White Sands Missile Range, extending up to 366 nautical miles at higher altitudes, with the interference window running from 03:00 on May 13 to 06:29 on May 14. The accident flight's destination airport lies less than 70 nm from the center of that advisory area. AOPA notes that GPS interference from military jamming operations has been a concern for years, with inconsistent NOTAM dissemination; since 2019 AOPA has pressed the FAA to improve awareness and mitigation, advising pilots as a stopgap to ask ATC to "stop buzzer" when navigation systems are affected. In this accident, ATC made exactly that request at 00:01 — but roughly seven minutes later told the military that jamming could resume, at the moment the crew was in the final phase of a visual descent toward the airport. According to multiple U.S. media reports in August, the NTSB has yet to determine the significance of GPS jamming in the terrain collision, and New Mexico's congressional delegation has demanded information from the military on the jamming activity before the fatal crash; a KOB investigative report of August 10 said GPS jamming near White Sands returned following the deadly accident. As of this writing, the NTSB has not released a final report; the probable cause remains subject to the Board's final determination.

3. Three Safety Lessons for the Air Medical Transport Industry

This accident has drawn sustained attention inside and outside the industry because it stacks several risks specific to air medical transport: night operations, mountainous terrain, urgent dispatch, rapid launch — and a new variable that neither the crew nor the ATC system fully handled: regional GPS jamming. The first lesson concerns mission assessment. The "urgent" nature of air medical transport inherently compresses decision time — in this case the crew had less than an hour between tasking and takeoff, and whether the two NOTAMs capable of changing the approach decision (weather broadcast out of service, wide-area GPS interference) were fully digested is a key question of the investigation. AOPA's safety takeaways are highly operational: during preflight planning, carefully assess how the loss of GPS navigation would affect the flight — including the knock-on effect on terrain awareness and obstacle warning systems — and decide in advance how to navigate, approach and land without it; when flying at night over high terrain, stay on an IFR clearance and fly the published instrument approach all the way to landing, and terminate any visual approach if unable to keep the airport in sight. The second lesson concerns airspace risk management. GPS jamming has evolved from a wartime threat into a peacetime risk for civil aviation, and the overlap between military testing areas and medical transport routes is now on the table. For transport coordinators, this means route planning cannot stop at weather and overflight permits: NOTAMs on GPS interference and military activity areas must be actively checked, and "loss of GPS" should be a standard contingency scenario for night flights over high terrain. The third lesson concerns industry standards. For reference, China's civil aviation authority issued industry standard MH/T 1065-2018 Specification for Air Medical Rescue Flight Services and the advisory circular Helicopter Medical Rescue Operations (AC-135-FS-015) in 2018, and in June 2026 launched development of the national standard Emergency Rescue — General Requirements for Air Medical Rescue (see our September 8 article), which will set unified requirements across institutional qualifications, staffing, equipment, service processes and safety management — with operational risk management (including navigation-failure contingency and operating limits for night and complex-terrain missions) at the core of the safety-management dimension. The findings of this U.S. investigation may well become a safety case cited in air medical rescue standard-setting worldwide.

Disclaimer: This article is compiled from public sources: the U.S. National Transportation Safety Board (NTSB) Aviation Investigation Preliminary Report WPR26FA186 (accident of May 14, 2026; preliminary report issued June 2026, reviewed via the version published by KOB), the Aircraft Owners and Pilots Association (AOPA) report of June 18, 2026 "GPS jamming active when King Air struck mountain" (by Jim Moore), NBC News of May 15, 2026, the Associated Press of June 18, 2026, and KOB's investigative report of August 10, 2026, among other media coverage; all sources accessed and verified on September 9, 2026. The investigation is ongoing; information in the NTSB preliminary report is preliminary and subject to change, and the probable cause is subject to the NTSB's final report. Operator and organization names are rendered as in the source report. This article is industry news commentary and does not constitute medical advice; the feasibility and specifics of any air medical transfer must be assessed by qualified medical institutions.