# 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 **No verdict.** 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. Category: Government & Intelligence · Era: 2020s · First circulated: From early August 2026, after the NTSB's preliminary report became public and Stars and Stripes reported it on 5 August; the framing that the military killed the crew spread rapidly through aggregators and technology and defence trade sites over the following days · 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 · Status: developing (details unconfirmed and may change) URL: https://theconspiratory.com/theory/medevac-gps-jamming-crash-2026 ## Summary 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 when Stars and Stripes reported it on 5 August, is a sequence that reads badly for the United States military. The crew told air traffic control they had lost GPS. A supervisor called the military, which was conducting a jamming exercise at White Sands Missile Range, and asked it to stop. As the aircraft neared Ruidoso the supervisor called back and said jamming could resume. Five minutes after that, the aircraft hit the mountain. Three other aircraft reported GPS problems to controllers the same night. This file rates the claim that the jamming caused the crash and that the military is therefore responsible for four deaths. That claim is unproven, and the NTSB has said in terms that it has not determined a probable cause or any contributing factor. The documented sequence and the causal conclusion are two different things, and most of the coverage has collapsed them. ## The claim 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. ## Origin and timeline - 2020 to 2026: Interference 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-14: Shortly 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-14: According 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-14: An 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-05: Stars 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-05: Representative 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-06: Snopes 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-08: The 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. ## The evidence, claim by claim - Claim: The NTSB report shows the military jamming caused the crash. Evidence: 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. - Claim: The timing settles it: jamming resumed and five minutes later the aircraft hit a mountain. Evidence: 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. - Claim: Three other aircraft lost GPS the same night, which proves the jamming was dangerous. Evidence: 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. - Claim: A member of Congress has said military technology played a role, so the question is settled. Evidence: 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. - Claim: The military would never admit it, so the absence of a finding proves a cover-up. Evidence: 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. ## Why 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 obvious inference, and the feeling is not irrational. - This is the rare case where the official record supplies the suspicious element rather than denying it. Most claims of this shape have to allege a hidden cause against official silence. Here the jamming, the GPS loss and the timing all come from the investigators themselves, which makes the remaining scepticism about causation feel like hair-splitting rather than rigour. - There is a real and growing problem underneath. GPS interference is a documented and rising aviation safety issue worldwide, and pilots have been raising it for years. A story that appears to show the cost of it lands on a grievance the aviation community already holds and considers under-addressed. - The victims were an air ambulance crew flying at night to collect a patient, which makes the loss particularly hard to sit with, and hard stories generate a demand for someone to be responsible. An unfinished investigation offers nothing to hold, and a documented military exercise offers something. - The headlines did the rest. Once outlets began writing that the military 'likely caused' the crash or 'accidentally killed everybody on board', readers encountering the story second-hand met the conclusion before the caveat, and most never saw the NTSB's statement that it has determined nothing. ## Open questions - 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. ## Latest developments - 2026-08-08T09:20Z: 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: https://www.stripes.com/theaters/us/2026-08-05/ntsb-medevac-crash-gps-jamming-22466131.html) ## Sources - NTSB investigates medevac crash that occurred during military GPS jamming exercise, Stars and Stripes (2026): https://www.stripes.com/theaters/us/2026-08-05/ntsb-medevac-crash-gps-jamming-22466131.html - Did US military's GPS signal jamming cause fatal plane crash? What we know, Snopes (2026): https://www.snopes.com/news/2026/08/06/us-military-medical-plane-crash/ - Military GPS Jamming Under Scrutiny In Fatal New Mexico Medevac Accident, AVweb (2026): https://avweb.com/aviation-news/military-gps-jamming-medevac-crash/ - NM delegation demands answers from Pentagon over GPS jamming linked to fatal medevac crash, Albuquerque Journal (2026): https://www.abqjournal.com/news/nm-delegation-demands-answers-over-military-potentially-causing-fatal-medevac-crash/3097938 - NTSB investigations, National Transportation Safety Board (2026): https://www.ntsb.gov/investigations/Pages/default.aspx Rated by The Conspiratory, a neutral, sourced encyclopedia of conspiracy theories. Full page: https://theconspiratory.com/theory/medevac-gps-jamming-crash-2026