A US military GPS jamming exercise brought down a medical evacuation flight in New Mexico in May 2026, killing all four people aboard, and the military is responsible for their deaths
By The Conspiratory EditorsAugust 8, 2026
That a United States military GPS jamming exercise conducted at White Sands Missile Range caused the 14 May 2026 crash of a medical evacuation flight into the Capitan Mountains in New Mexico, that the military therefore killed the two pilots and two flight nurses aboard, and that this has been effectively established by the National Transportation Safety Board's preliminary report.
This is an open federal investigation and the account here will change. What is documented is unusual for a story of this kind, because the official record confirms rather than denies the suspicious part. According to the National Transportation Safety Board's preliminary findings, reported by Stars and Stripes, a Beechcraft King Air C90 air ambulance flew into the Capitan Mountains near Ruidoso, New Mexico, around midnight on 14 May 2026, twenty-three minutes after leaving Roswell, killing both pilots and both flight nurses. The pilots had told an air traffic controller they had lost GPS signal. An operations supervisor contacted the military, which was running a GPS jamming exercise at White Sands Missile Range, and asked it to stop. As the aircraft approached Ruidoso the supervisor called back to say jamming could resume. Five minutes later the aircraft struck the mountain. Three other aircraft reported losing GPS to controllers that night. What is not established is the thing the claim asserts. The NTSB says plainly that it has not determined the probable cause or any contributing factors, and Snopes, examining the claim on 6 August, declined to rate it because no evidence yet confirms or disproves that the jamming caused or contributed to the crash. So the rating here is unproven, and it is unproven in a specific direction: the sequence is real and documented, and the causal link is the part no one has established. We make no accusation against the military, any service member or any official, and none has been made by any investigating body.
Believed by: A wide and largely non-partisan audience, including pilots and aviation professionals following GPS interference as a safety issue, alongside a general readership encountering the story through headlines that state the causal conclusion the investigation has not reached
Opening entry, and the file is marked developing because the investigation is genuinely unfinished rather than because the sourcing is thin. The reason for building now is that the claim reached the US search trends feed this week while the NTSB's position, that it has determined no cause and no contributing factors, is absent from most of the coverage carrying it. This file will be updated as the investigation proceeds, and the entry that matters will be the final report. If it finds the jamming caused or contributed to the crash, the verdict here changes accordingly; if it identifies other factors, that will be recorded with the same prominence. source →
The full story
Twenty-three minutes
Shortly after midnight on 14 May 2026, a Beechcraft King Air C90 lifted off from Roswell, New Mexico. It was an air ambulance, flying to collect a patient. Aboard were two pilots and two flight nurses.
Twenty-three minutes later it flew into the side of the Capitan Mountains near Ruidoso. Nobody survived.
For nearly three months that was, publicly, a night-time crash in mountainous terrain. Then the National Transportation Safety Board's preliminary findings became public, Stars and Stripes reported them on 5 August, and the story became something else entirely.
What the findings describe is this. During the flight the crew told an air traffic controller they had lost GPS. The United States military was at that moment running a GPS jamming exercise at White Sands Missile Range, covering the airspace the flight was in. An operations supervisor contacted the military and asked it to stop. As the aircraft approached Ruidoso, the supervisor called back and told the military it could resume. Five minutes after that, the aircraft hit the mountain. Three other aircraft reported losing GPS to controllers the same night.
The official record is the source of the suspicion
It is worth being precise about why this story is harder than most of what this site covers, because the difficulty is structural.
The ordinary shape of a claim like this is an allegation running against an official account: something terrible happened, the authorities say one thing, and a counter-narrative says the real cause is being hidden. The evidence for the counter-narrative is usually thin, circumstantial or fabricated, and the work of a file like this one is to say so.
Here it is inverted. Nobody had to leak anything. The jamming exercise, the crew's report of GPS loss, the request to stop, the permission to resume and the five-minute interval all come from the investigators themselves, published in a preliminary report and relayed by a defence newspaper. The suspicious material is the official material.
That means the sceptical position here cannot be, and is not, that the circumstances are innocent or invented. They are documented and they are grim. The narrower question, and the only one actually open, is whether the jamming caused or contributed to the crash. And on that, the body doing the investigating has said something plain that almost none of the coverage repeats.
What the NTSB has not determined
The NTSB has stated that it has not yet determined the probable cause or any contributing factors to the accident.
That is not bureaucratic hedging, and it is not a refusal to say what everyone knows. A preliminary report is a factual record assembled in the weeks after an accident: what was recovered, what was recorded, what the sequence appears to have been. Probable cause comes later, after the wreckage, the recorders, the systems, the weather, the training records and the procedures have all been worked through. The final report in this case does not exist yet.
The things an inquiry will have to establish are not incidental. What were the aircraft's other navigation systems doing once GPS was lost? What terrain-awareness warnings sounded, and when? What was the visibility, at night, against unlit high ground? What did the crew understand about their position, and what were they told? Any of those could turn out to be a contributing factor alongside the GPS loss, or instead of it.
There is also the awkward fact of the other three aircraft. They reported losing GPS to controllers that same night and they did not crash. That does not clear the exercise of anything, and the difference may lie in terrain, altitude or phase of flight. It does mean that GPS loss on its own was survivable for other crews on the same night, which is precisely the sort of discrepancy an investigation exists to resolve.
Snopes reached the same place on 6 August. It examined the claim that the military was responsible for the four deaths and declined to rate it, confirming the jamming exercise was real and current, and stating that no evidence yet confirms or disproves that it was the sole or partial cause.
Where the coverage overshot
Between 5 and 8 August the story travelled a long way, and it changed shape as it went.
Technology and general-interest aggregators picked it up with headlines asserting that the jamming likely caused the crash, and in at least one case that the military had accidentally killed everybody on board. Those are conclusions. The NTSB has not reached them. A reader meeting the story through one of those headlines encounters the verdict before the facts, and there is no particular reason they would go looking for the agency's statement afterwards.
This is the mechanism worth naming, because it is not lying and it is not fabrication. Every individual fact in those pieces is real. What has been added is the join between them, and the join is the part nobody has established. It is a more respectable failure than the fabricated videos this site usually rates, and it does the same job: it hands the audience a settled answer to a question that is still open.
The congressional letter sits in a similar position. Representative Gabe Vasquez, having been briefed by the NTSB chair and regional officials, wrote to the NTSB and the Defense Department asking for a joint briefing and said that military technology “definitely had a role to play in the flight path of this tragic crash”. That is a real development and it means officials are being pressed. It is a legislator characterising a briefing, not an investigator publishing a finding, and the two get quoted interchangeably.
Why the inference feels irresistible
Almost everyone who reads the sequence draws the same conclusion, and it would be dishonest to pretend that is a failure of reasoning. A crew said they had lost navigation. Someone asked the military to stop interfering. The interference was allowed to restart. Five minutes later four people were dead on a mountainside. The inference is the natural one.
It is reinforced by a real grievance. GPS interference has been a growing aviation safety problem for years, driven by electronic warfare exercises and by deliberate jamming in conflict regions, and pilots have been raising it for a long time without much sense of being heard. A story that looks like the bill finally coming due lands on that frustration and confirms it.
And the human weight of it presses in one direction. This was an air ambulance crew, flying at night, to fetch someone who needed help. An unfinished investigation offers nothing to hold on to. A documented military exercise offers something.
None of which makes the causal claim true. It makes it understandable, which is a different thing, and it explains why the careful version of this story has almost no chance against the confident one.
The document that will settle it
There is a specific thing that will answer this, and it does not exist yet: the NTSB's final report, with its probable cause and any contributing factors.
If it finds that the jamming caused or contributed to the crash, the rating on this page changes and this file will say so as plainly as it says the opposite now. If it identifies other factors, or several acting together, that will be recorded with the same prominence. The point of holding the question open is not scepticism for its own sake. It is that the answer is coming from people who are actually able to determine it.
In the meantime the useful distinction is between two sentences that look almost identical. “The military was jamming GPS when this aircraft lost navigation and crashed” is documented, and it is serious enough on its own to warrant every question being asked of it. “The military caused this crash” is not documented, and saying it now does not make the four people aboard any less dead or the eventual finding any more likely to be honest.
One question deserves an answer whichever way causation falls, and it is the one this file would most like to see addressed. The jamming was paused because an aircraft in that airspace had reported losing navigation. It was then allowed to resume while that same aircraft was still airborne, at night, approaching mountains. Who judged that safe, on what information, and under what procedure, is not in the public record. That is a question about how the exercise was run rather than about what caused the impact, and it does not need a probable-cause finding to be worth asking.
What's still unexplained
- What does the final NTSB report conclude? The preliminary findings establish the sequence; probable cause and contributing factors are determined later, and until that document exists the central question of this file is formally open. Nothing here should be read as anticipating it.
- Why was the exercise permitted to resume while the aircraft was still airborne and approaching mountainous terrain at night? The pause and the resumption are documented, but who assessed that it was safe to restart, on what information, and under what procedure is not something the public record currently answers.
- What happened aboard the aircraft after the GPS loss? Terrain-awareness alerts, the state of other navigation systems, crew workload and what the pilots were told all bear directly on causation, and none of it has been published.
- Does the joint briefing requested by Representative Vasquez produce anything on the record? A congressional request is not an investigation, and whether it yields documents, testimony or only a private meeting will determine if it adds to the public account or not.
Point by point
The claim: The NTSB report shows the military jamming caused the crash.
What the record shows: It shows a sequence, and the NTSB says explicitly that it has not concluded what caused the accident. A preliminary report is a record of facts gathered so far; assigning probable cause and contributing factors is what the final report does, and that has not been issued. The agency's own statement is that it has 'not yet determined the probable cause or any contributing factors to the accident'. Reading a preliminary report as a verdict misunderstands what the document is for, and in this case the misreading is doing the work in almost every viral version of the story.
The claim: The timing settles it: jamming resumed and five minutes later the aircraft hit a mountain.
What the record shows: The interval is documented and it is the strongest fact the claim has. It is still not a causal finding. An accident investigation has to establish what the crew could see, what the aircraft's other navigation systems were doing, what terrain-awareness warnings sounded and when, what the weather and visibility were at night in mountainous terrain, and what the crew were told and understood. Any of those could be a contributing factor alongside GPS loss, or instead of it. Sequence establishes opportunity; investigations establish cause, and this one is unfinished.
The claim: Three other aircraft lost GPS the same night, which proves the jamming was dangerous.
What the record shows: It establishes that the interference was real and widespread, which is a genuine and serious finding, and it is one of the reasons the story matters beyond this single flight. It also cuts against the narrowest version of the claim in one respect: three other aircraft encountered the same conditions that night and did not crash. That does not exonerate the exercise, and the difference may lie in terrain, altitude or phase of flight. It does mean GPS loss alone was survivable for other crews, which is exactly the sort of thing an investigation exists to unpick.
The claim: A member of Congress has said military technology played a role, so the question is settled.
What the record shows: Representative Gabe Vasquez said that military technology 'definitely had a role to play in the flight path', after being briefed by the NTSB chair and regional officials, and he has requested a joint briefing from the NTSB and the Defense Department. That is a significant development and it is why the story has an official track beyond the accident inquiry. It is not a determination. Legislators receive briefings and characterise them; investigators publish findings. The letter is evidence that officials are being pressed, not evidence of what caused the crash.
The claim: The military would never admit it, so the absence of a finding proves a cover-up.
What the record shows: The record runs against this. The jamming exercise is not hidden: it appears in the NTSB's preliminary findings and in FAA communications from the day, which is how the public learned about it. An operations supervisor's request to pause it, and the call permitting it to resume, are both documented. If an institution were concealing its role, publishing the exercise, the pause, the resumption and the interval before impact would be a strange way to go about it. What is missing is a causal determination, and the ordinary reason for that is that the investigation has not finished.
Timeline
- 2020 to 2026Interference with satellite navigation becomes a recognised and growing aviation safety concern worldwide, driven by both military electronic-warfare exercises and deliberate jamming and spoofing in conflict regions. Pilot reporting of GPS loss rises substantially over the period, and regulators and industry bodies treat it as an unresolved systemic risk rather than an isolated problem.
- 2026-05-14Shortly after midnight, a Beechcraft King Air C90 operating as an air ambulance departs Roswell, New Mexico, to collect a patient. Twenty-three minutes into the flight it collides with terrain in the Capitan Mountains near Ruidoso. Both pilots and both flight nurses aboard are killed.
- 2026-05-14According to the NTSB's preliminary findings, the crew radio an air traffic controller during the flight to report that they have lost GPS navigation capability. The United States military is conducting a GPS jamming exercise at White Sands Missile Range at the time, covering the area the flight is operating in.
- 2026-05-14An operations supervisor contacts the military and asks it to stop the jamming. As the aircraft approaches Ruidoso, the supervisor calls back and informs the military that jamming may resume. Five minutes later the aircraft strikes the side of the mountain range. Three other aircraft also report losing GPS signal to air traffic control that night.
- 2026-08-05Stars and Stripes reports the NTSB's preliminary investigative findings, including the pause-and-resume sequence and the five-minute interval before impact, and publishes the NTSB figure showing the aircraft's flight path. The story reaches a far wider audience than the crash itself had, and aviation trade outlets follow.
- 2026-08-05Representative Gabe Vasquez of New Mexico announces that he has written to the NTSB and the Department of Defense requesting a joint briefing, saying he has been briefed by the NTSB chair and regional officials and that 'military technology definitely had a role to play in the flight path of this tragic crash'. That is a statement by a legislator, not a finding by an investigator, and this file records it as such.
- 2026-08-06Snopes examines the claim that the military was responsible for the four deaths and does not rate it. It confirms that the military was testing GPS jamming technology at the time, citing FAA communications from the day and the NTSB preliminary report, and states that no evidence has come to light definitively confirming or disproving that the jamming was the sole or partial cause.
- 2026-08The framing hardens as it travels. Technology and general-interest aggregators publish headlines asserting that jamming 'likely caused' the crash or that the military 'accidentally killed everybody on board', conclusions the NTSB has expressly not reached. The claim reaches the US search trends feed in the week beginning 3 August.
This is an open federal investigation and the account here will change. What is documented is unusual for a story of this kind, because the official record confirms rather than denies the suspicious part. According to the National Transportation Safety Board's preliminary findings, reported by Stars and Stripes, a Beechcraft King Air C90 air ambulance flew into the Capitan Mountains near Ruidoso, New Mexico, around midnight on 14 May 2026, twenty-three minutes after leaving Roswell, killing both pilots and both flight nurses. The pilots had told an air traffic controller they had lost GPS signal. An operations supervisor contacted the military, which was running a GPS jamming exercise at White Sands Missile Range, and asked it to stop. As the aircraft approached Ruidoso the supervisor called back to say jamming could resume. Five minutes later the aircraft struck the mountain. Three other aircraft reported losing GPS to controllers that night. What is not established is the thing the claim asserts. The NTSB says plainly that it has not determined the probable cause or any contributing factors, and Snopes, examining the claim on 6 August, declined to rate it because no evidence yet confirms or disproves that the jamming caused or contributed to the crash. So the rating here is unproven, and it is unproven in a specific direction: the sequence is real and documented, and the causal link is the part no one has established. We make no accusation against the military, any service member or any official, and none has been made by any investigating body.
Reviewed by The Conspiratory Editors · Last reviewed August 8, 2026 · How we rate
Common questions
Is The medevac GPS jamming crash true?
This is an open federal investigation and the account here will change. What is documented is unusual for a story of this kind, because the official record confirms rather than denies the suspicious part. According to the National Transportation Safety Board's preliminary findings, reported by Stars and Stripes, a Beechcraft King Air C90 air ambulance flew into the Capitan Mountains near Ruidoso, New Mexico, around midnight on 14 May 2026, twenty-three minutes after leaving Roswell, killing both pilots and both flight nurses. The pilots had told an air traffic controller they had lost GPS signal. An operations supervisor contacted the military, which was running a GPS jamming exercise at White Sands Missile Range, and asked it to stop. As the aircraft approached Ruidoso the supervisor called back to say jamming could resume. Five minutes later the aircraft struck the mountain. Three other aircraft reported losing GPS to controllers that night. What is not established is the thing the claim asserts. The NTSB says plainly that it has not determined the probable cause or any contributing factors, and Snopes, examining the claim on 6 August, declined to rate it because no evidence yet confirms or disproves that the jamming caused or contributed to the crash. So the rating here is unproven, and it is unproven in a specific direction: the sequence is real and documented, and the causal link is the part no one has established. We make no accusation against the military, any service member or any official, and none has been made by any investigating body.
What is The medevac GPS jamming crash?
Shortly after midnight on 14 May 2026, a Beechcraft King Air C90 air ambulance left Roswell, New Mexico, to collect a patient. Twenty-three minutes later it flew into the side of the Capitan Mountains near Ruidoso. Both pilots and both flight nurses were killed. What emerged in the NTSB's preliminary findings, and reached a wide audience…
What does the evidence show?
It shows a sequence, and the NTSB says explicitly that it has not concluded what caused the accident. A preliminary report is a record of facts gathered so far; assigning probable cause and contributing factors is what the final report does, and that has not been issued. The agency's own statement is that it has 'not yet determined the p…
Why do people believe it?
The documented sequence is genuinely disturbing, and no amount of care about causation changes that. A crew reported losing navigation, someone asked the military to stop interfering, the interference was allowed to restart, and five minutes later four people died against a mountainside. Anyone reading that will feel the pull of the obvi…
What is still unresolved?
What does the final NTSB report conclude? The preliminary findings establish the sequence; probable cause and contributing factors are determined later, and until that document exists the central question of this file is formally open. Nothing here should be read as anticipating it.
Sources
- 1.NTSB investigates medevac crash that occurred during military GPS jamming exercise, Stars and Stripes (2026)
- 2.Did US military's GPS signal jamming cause fatal plane crash? What we know, Snopes (2026)
- 3.Military GPS Jamming Under Scrutiny In Fatal New Mexico Medevac Accident, AVweb (2026)
- 4.NM delegation demands answers from Pentagon over GPS jamming linked to fatal medevac crash, Albuquerque Journal (2026)
- 5.NTSB investigations, National Transportation Safety Board (2026)
Embed this case file on your site
Paste this snippet to show this case file as a small card, with a link back to the full write-up. Free to use.
<iframe src="https://theconspiratory.com/embed/medevac-gps-jamming-crash-2026" title="The Conspiratory verdict" width="520" height="190" style="border:0;max-width:100%" loading="lazy"></iframe>Help us investigate
This is a living case file. If you spot an error or know evidence we missed, tell us, and weigh in on where you land.
Where do you land?
Cast your read on this one.
Comments
Add your take. Comments are read and approved by a human before they appear, so keep it on topic and civil. Please do not accuse named, living people of crimes.