The NTSB preliminary report on the Aerovac King Air 90 crash near Ruidoso, New Mexico on May 14, 2026 reveals a compounding series of regulatory and operational barriers that collectively rendered the flight undispatchable under any reasonable risk standard. Four crew members — two pilots employed by Generations Jets and two flight nurses from Trans-Aero Medical Services — were killed when the aircraft impacted terrain during a nighttime medevac mission to Sierra Blanca Regional Airport. The flight departed Roswell at approximately 23:54 local time and impacted terrain within 21 minutes. The crew had received their NOTAMs through ForeFlight prior to departure and was aware of ongoing U.S. military GPS jamming operations emanating from White Sands Missile Range, which covered an area up to 326 nautical miles and directly encompassed the route and destination. What the crew appears not to have fully processed was the cascading effect those two NOTAMs — GPS jamming and the AWOS at Sierra Blanca NOTAMed unserviceable — had on every available instrument approach at the destination airport.
Sierra Blanca Regional Airport published two instrument approaches: the RNAV GPS Runway 24 and the ILS/LOC Runway 24. The GPS jamming environment eliminated the RNAV approach as a reliable option. The ILS/LOC Runway 24 approach contains a procedural note that explicitly prohibits its use when a local altimeter setting cannot be received — a requirement fulfilled solely by the airport's AWOS, which was NOTAMed out of service for the duration of the flight. With both instrument approaches legally and practically unusable, the crew was committed to a visual approach at night with zero lunar illumination into mountainous terrain, with the Capitan Mountains peaking at 10,201 feet in the immediate vicinity of the approach path. Standard Part 135 operations specifications, and universally accepted industry practice in mountainous terrain operations, require an available instrument backup when conducting a nighttime visual approach. No such backup existed. The flight should not have been dispatched.
The accident highlights a systemic vulnerability in lower-tier Part 135 medevac operations: the gap between NOTAM awareness and operational decision-making. The crew accessed both NOTAMs through ForeFlight — the GPS jamming volume and the AWOS outage — but apparently did not work through the logical chain by which those two conditions together eliminated all authorized approach procedures at the destination. This analytical failure is not unique to inexperienced crews, but experience in structured operational environments like Part 121 or larger Part 135 carriers tends to instill a dispatch discipline that demands affirmative answers to the question of what approach will be used on arrival, not merely whether conditions appear flyable at departure. Crews without that institutional background may evaluate individual NOTAMs in isolation rather than recognizing when their combination forecloses a legal and safe arrival. The medivac environment compounds this by introducing mission pressure — a patient awaiting transport — that can subtly shift the internal calculus toward accepting marginal conditions.
The role of GPS jamming as an operational hazard deserves specific attention from crews flying in the American Southwest and other military exercise corridors. White Sands and adjacent ranges produce some of the most frequently NOTAMed GPS interference in the continental United States, and the interference envelopes are large. For any flight into or through these areas, crews and dispatchers should treat GPS jamming NOTAMs not merely as an avionics advisory but as a trigger requiring a systematic review of all approach procedures at origin, destination, and alternate airports. If the primary or sole instrument approach at any of those airports is GPS-dependent, and jamming is active or probable, the operational picture must be rebuilt from scratch using only ground-based navaids. In this case, the ILS/LOC existed as a theoretical ground-based alternative, but the secondary NOTAM condition removed it from the legal table entirely. Dispatch software and crew briefing checklists in Part 135 operations rarely automate this cross-NOTAM dependency analysis, leaving it to individual pilot judgment at the point of highest time pressure.
The broader implication for business aviation and charter operators is that Part 135 medevac missions concentrate multiple risk factors that, in any other operational context, would trigger a no-go decision at the dispatch level. Night, mountainous terrain, limited airport infrastructure, time pressure, and a high-stakes mission profile all converge simultaneously and routinely. The Ruidoso accident is a case study in what the industry calls the "normalization of deviance" — conditions that individually appear manageable and have been tolerated before, but whose joint presence crosses a threshold of unacceptable risk that should be embedded in operations specifications and dispatch authority rather than left to individual crew assessment in the early hours of the morning. The four lives lost on this flight represent a foreseeable outcome of a systemic failure that begins not at rotation but at the dispatch desk, and operators across the medevac sector should treat this preliminary report as a direct prompt to review their no-go criteria for compounding NOTAM environments.