Here’s a sentence that should not be possible in 2026: a medical plane lost its GPS in mid-flight because the U.S. military was actively scrambling the signal across the area, and minutes later it flew straight into a mountain. Four people died. That’s not a conspiracy theory or a forum rumor. It’s the finding from federal investigators looking into the crash near Ruidoso, New Mexico, this past spring.
The National Transportation Safety Board put out its preliminary report on the May 14 crash, and the details are the kind that make you read the whole thing twice. The plane went down in the Capitan Mountains, killed everyone on board, and started a wildfire that burned for weeks. Investigators won’t name an official cause until the final report lands. But they laid out a timeline that’s hard to look away from.
Four People, One Mountain, No Signal
The aircraft was a Beechcraft King Air C90, a twin-turboprop used all over the country for air ambulance work. It left Roswell Air Center just before midnight on what’s called a repositioning flight, meaning it was on its way to pick up a patient at Sierra Blanca Regional Airport near Ruidoso. No patients were on board yet. The crew was four people: pilots Keelan Clark and Ali Kawsara with the company Generation Jets, and flight nurses Jamie Novick and Sarah Clark with Trans Aero MedEvac, an outfit that’s been flying southeastern New Mexico and west Texas since 1966.
According to the report, the crew reported losing GPS at midnight, just minutes after takeoff. They asked air traffic control for help. The flight ended when the plane hit the side of a mountain at roughly 9,950 feet, in terrain that rises above 10,000 feet. All four were killed.
The Jamming Came From White Sands
For the first time, the NTSB confirmed that scheduled military GPS jamming coming out of White Sands Missile Range was active during the flight. White Sands is a giant Army testing range in south-central New Mexico, and part of what they do there involves knocking out GPS to test equipment under realistic conditions.
If you’ve never heard of GPS jamming, the idea is simple. GPS signals coming down from satellites are incredibly weak by the time they reach you. Jamming means blasting radio noise on the same frequencies, which drowns out those faint signals so receivers on the ground or in the air can’t read them. There’s a nastier cousin called spoofing, where false data tricks the equipment into showing a wrong position. Both have been popping up more often around the world, especially near conflict zones.
Here’s the part that complicates the story: the military didn’t do this in secret. The FAA had already published a Notice to Airmen warning any pilot flying into the area that GPS would be jammed. The crew’s preflight briefing included that warning, and the jamming window covered both the time and the location of their flight. So the loss of GPS wasn’t a shock. It was expected.
They Asked the Military to Stop. It Worked, for a Minute.
This is where the timeline gets genuinely upsetting. When the crew told controllers they’d lost their primary navigation, the controllers actually got on the phone with the military installation and asked them to halt the jamming. And it worked. White Sands paused the operation for a brief window. The pilots got their bearings back.
Shortly after the pause, the pilots reported they could see the landing strip at Sierra Blanca and were cleared for a visual approach. Then, minutes after that clearance, the military jamming resumed. There were no more transmissions from the aircraft. Flight tracking data showed it descending toward the Capitan Mountains, and then it struck the slope. The crew wasn’t even the only flight having trouble that night. Other pilots in the region reported their own GPS problems at the same time.
Why Pilots Say Losing GPS Alone Shouldn’t Down a Plane
This is the question that keeps coming up among aviation people, and it’s a fair one. GPS is not the only way to fly. Pilots have been navigating by ground-based radio beacons and by simply looking out the window for decades. So why would a crew that knew the jamming was coming end up in the rocks?
Retired airline pilot John Cox, who now runs a safety consulting firm, put it bluntly: “The loss of GPS should not result in the loss of an airplane, so there’s got to be more to it than that.” Steve Arroyo, a longtime United Airlines pilot, explained the trade-off well. GPS can bring you down with the precision and safety margin required for a tricky approach. Without it, conventional navigation can leave you drifting outside those margins, especially when you’re threading around obstacles with little room for error.
That’s the catch. Pilots lean on GPS not because they’re lazy, but because it’s so accurate that it lets them fly safely through terrain where older methods get sloppy. Take it away in the wrong spot, and your wiggle room shrinks fast.
The Other Things That Went Wrong That Night
The GPS jamming wasn’t the only problem stacked against this crew, and the report makes that clear. The weather reporting system at Sierra Blanca Regional Airport, their destination, was already out of service that night. That matters more than it sounds. Without it, the crew had no approved instrument-guided way to land at that airport from the moment their wheels left Roswell. Their fallback was already shaky before the GPS dropped out.
Then there’s the sky itself. Weather was clear, but there was no moon. Investigators specifically noted that dark night skies with no moonlight can badly reduce a pilot’s ability to see terrain ahead. You can’t dodge a mountain you can’t see, even on a visual approach.
There’s also a data puzzle the NTSB flagged but hasn’t solved. Two separate systems tracking the plane’s altitude didn’t agree. The Spidertracks GPS altitude was running about 600 feet higher than the recorded ADS-B altitudes, and there were big gaps in the ADS-B data. Whether the jamming starting back up caused those gaps is still undetermined. That’s a 600-foot question mark hanging over a flight that ended on a mountainside.
This Wasn’t the First Time White Sands Caused Headaches
If you think this came out of nowhere, it didn’t. Air traffic controllers had been complaining about exactly this for months before the crash. Public records show that in March and April, controllers at the Albuquerque Air Route Traffic Control Center filed reports through a NASA-run anonymous safety system, and they were clearly fed up.
One report said aircraft were “greatly affected by the GPS jamming and it’s not taken seriously by management.” Another said controllers were told they “can’t ask to stop jamming, and to just put everyone on headings.” In aviation, there’s a request called a “stop buzzer,” where a controller asks the military to cut a test short over a safety concern. The complaints accused the FAA of denying controllers permission to make those calls.
One incident stands out. A private jet got jammed and made a wrong turn straight into restricted airspace over White Sands itself. The controller called a stop buzzer. A manager on duty later told that controller they couldn’t do that and to just keep putting aircraft on headings. On another morning, a commercial airliner approaching El Paso got a “GPS Position Lost” warning, and the airline traced it right back to White Sands. So civilian planes getting hit by this jamming was a known, documented thing well before May 14.
The Fire, and What Comes Next
The crash didn’t end with the impact. The post-crash fire ignited what became the Seven Cabins Fire in the Lincoln National Forest, which is heavily wooded and remote. It burned more than 30,000 acres, about 48.4 square miles, fed by dry, windy conditions in rugged country. It wasn’t declared 100% contained until June 12, nearly a month after the plane went down. Ruidoso, the town the crew was trying to reach, is a mountain community with a year-round population under 8,000 sitting at the base of the Sierra Blanca range.
As for answers, this is only the preliminary report, labeled WPR26FA186. The NTSB hasn’t assigned a probable cause, and it won’t until the final report, which is expected in 12 to 24 months. Everything in the preliminary findings is subject to change.
But the core facts are already on the record. The military was jamming GPS over a stretch of New Mexico. A medical crew flew into it, lost their primary navigation, briefly got it back when the jamming paused, then lost it again right as they lined up to land. Their backup airport had no working weather system, and there was no moon to light the terrain. Four people, two of them nurses who fly to save other people, didn’t make it home. The official cause is still a year or two out. The timeline is right here now.