The Night the Military's GPS Jamming Brought Down a Medevac Plane — And What We Should Learn From It

This is one of those stories that makes you stop and think about all the invisible systems we trust with our lives every single day.

On May 14, 2026, a Beechcraft King Air medevac plane took off from Roswell, New Mexico, carrying two pilots, two nurses, and a patient waiting at the other end of their journey. They never made it.

What happened that night is a perfect storm of military secrecy, outdated aviation infrastructure, and a catastrophic miscommunication — and honestly, it should make all of us ask some pretty serious questions.

It Started as a Routine Flight

The crew was flying to Sierra Blanca Regional Airport near Ruidoso to pick up a patient who needed transport to a hospital in Albuquerque. Nothing unusual about that. These medevac pilots do this kind of work all the time, often flying through darkness and tricky conditions to save lives.

But this particular night was different. The moon wasn't out, visibility was nearly zero, and just off their flight path, the U.S. military was running GPS jamming exercises at White Sands Missile Range.

Now, these exercises are supposed to be announced in advance. The FAA publishes notices warning pilots when and where GPS might become unreliable. But here's the thing — GPS signals from satellites 12,000 miles up are incredibly weak. When the military cranks up a ground transmitter powerful enough to defeat drones and other threats, those signals don't exactly respect the neat boundaries drawn on aviation charts.

The Moment Everything Went Wrong

About eight minutes after takeoff, pilots Keelan Clark and Ali Kawsara reported to air traffic control that they'd lost their GPS signal entirely. No navigation, no reliable positioning. In a dark sky over mountainous terrain, that's like asking someone to find their way through a forest blindfolded.

The crew had to fall back on older technology — manual heading vectors from air traffic control, radio-based navigation systems. Their aircraft's ADS-B tracking, which normally sends position updates every few seconds, slowed to once per minute. The data was spotty, unreliable, and frankly, terrifying to work with.

You have to imagine what was going through those pilots' minds. They had patients depending on them. They had a job to do. But every instrument they relied on was essentially lying to them or going silent.

The Decision That Haunts This Story

Here's where things get really heartbreaking.

The air traffic control operation supervisor recognized the danger. These weren't amateur pilots flying for fun — they were medical professionals trying to navigate rugged mountains without their primary navigation tools. The supervisor reached out to the military and requested a temporary pause in the jamming.

The military obliged. And for a brief moment, the plane's tracking systems came back online.

At around 12:08 a.m., the crew reported they had Ruidoso in sight. They requested a visual approach — they could see their destination with their own eyes now. Air traffic control cleared them for landing. Everything seemed like it was going to be okay.

But someone in the chain of communication made a critical assumption: if the plane could see the airport, the crew was safe. The jamming could resume.

So it did.

And the plane's ADS-B tracking disappeared again.

A Preventable Tragedy

Minutes later, the King Air slammed into a mountain. There were no survivors.

Let that sink in for a moment. Four people lost their lives because of a series of decisions that, individually, might have seemed reasonable — but collectively, created a disaster.

The military needed to test jamming capabilities. Air traffic control wanted to protect an aircraft in distress. The pilots were trying to complete their mission. Nobody set out to kill anyone that night.

But here's what I keep coming back to: the moment the jamming resumed, the plane lost its tracking capabilities again. The pilots had spotted the airport, sure, but they were still flying through darkness, over terrain that offered zero margin for error. Without working instruments, without reliable positioning data, they were flying essentially blind.

A visual approach means you can see where you're going — but it doesn't mean you have perfect awareness of exactly where you are relative to terrain, obstacles, and your descent path. That requires instrumentation. And that instrumentation was being deliberately disabled.

A History of Secrets in the New Mexico Desert

There's something almost poetically tragic about this happening in New Mexico. That desert has been the site of America's most closely guarded experiments for nearly a century.

It was here, at White Sands Missile Range, that the first atomic bomb was detonated in 1945 — Trinity, they called it. Just two years later, debris from a classified spy balloon turned up on a ranch near Roswell and launched one of the most enduring UFO stories in American history.

Those experiments were secrets. What's different about this crash is that it wasn't classified. The jamming exercise was known. The danger was foreseeable. And people died anyway.

This Has Happened Before

Here's what really concerns me: this isn't even the first time GPS jamming has endangered civilian aircraft near White Sands. According to the reporting on this crash, there have been multiple incidents where planes either went down or came dangerously close because of these exercises.

We're not talking about isolated incidents anymore. We're talking about a pattern.

The aviation system is built on trust — trust that navigation systems will work, trust that critical information will be shared between agencies, trust that the military's activities won't create unacceptable risks for civilian aircraft. That trust was broken.

What Needs to Change

I don't pretend to have all the answers, but a few things seem obvious to me:

First, the military needs better coordination with civilian aviation authorities — not just notifications, but real-time communication during exercises. If an aircraft is in the air and in distress, maybe that isn't the moment to resume jamming.

Second, pilots need redundant systems that can't be knocked out by a single source of interference. GPS is incredibly useful, but we've built a system that depends on it almost entirely. That concentration of risk is dangerous.

Third, the assumption that "visual contact with destination = safe" needs to be questioned. These pilots weren't landing in a clear field with a straight shot. They were descending into mountainous terrain in the dark. One glimpse of lights on the horizon doesn't mean the hard part is over.

Finally, we need transparency about these exercises. This happened in 2026, and it's being reported publicly. That's good. But how many near-misses have occurred that we'll never hear about?

This crash didn't have to happen. There were at least three moments where a different decision could have saved those four lives. The supervisor who asked for the pause. The controllers who assumed visual contact meant safety. The military who resumed jamming without understanding the full picture.

Aviation is safe because of layers of protection — multiple checks, redundant systems, clear communication. When those layers fail, tragedies follow. But the terrifying thing about this story is that none of the failures were technical. They were human. They were assumptions. They were gaps in understanding.

And that means they're fixable — if we're willing to learn.

Source: Popular Mechanics