FirstAlerts
Plane CrashesVersion 3

Four Crew Killed in Medevac King Air Crash Near Ruidoso, New Mexico

Dailymail.com reports a US military GPS-jamming exercise has been linked to the 14 May crash on a preliminary basis; the National Transportation Safety Board is named as investigating.

By AI ReporterFirst reported Aug 5, 2026, 9:11 a.m. ETUpdated Aug 7, 2026, 10:06 a.m. ET
crew members were killed when a medevac crashed on near , New Mexico, on 14 May 2026, according to dailymail.com, which reported the aircraft was down . The outlet reported people on board, all crew, and fatalities. The National Transportation Safety Board is named as an investigating body. This account rests on a single dailymail.com report, and nothing further has been reported into the story in the roughly two days since that report. The details below stand as that report left them. The cause has not been determined. On a basis, dailymail.com reported that a US military GPS-jamming exercise has been linked to the crash, and that the Air Force's 746th Test Squadron was testing GPS-jamming technology during its NAVFEST electronic warfare event. According to the same report, the Federal Aviation Administration had warned pilots that the exercises could disrupt GPS signals up to 400 miles away between 12 and 18 May. Dailymail.com described the crash as the first fatal civilian plane crash in the US known to be linked to electronic warfare; that characterisation is and is not supported by any investigative finding in the available reporting. Dailymail.com also reported that the Seven Cabins Fire has been burning in the Capitan Mountain Wilderness since 14 May. Geographic reference data places in Lincoln County, New Mexico, at a terrain elevation of 6,742 feet for the settlement itself. The same reference data puts the referenced point 12 miles southwest of Sierra Blanca Regional Airport (KSRR/RUI), 21 miles east of Three Rivers Ranch Airport (NM71) and 23 miles southwest of G Bar F Ranch Airport (NM84). That data describes the place only and says nothing about what happened. No registration for the aircraft appears in the available reporting, and the airframe has not been identified. No NTSB finding, or final, appears in the available reporting.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
6,742 ft
Nearest aerodrome
12 miles SW of Sierra Blanca Regional Airport (KSRR/RUI)

Sources

Revision history

  1. Version 37 Aug 2026, 14:06current

    Removed "The event is still developing" and the closing "The NTSB investigation is continuing." Added an explicit paragraph stating the story rests on one dailymail.com report and that nothing has been reported into it in roughly two days. Changed the dek and body from "investigation is open" to the NTSB being named as an investigating body, and closed on the absence of any NTSB finding in available reporting. All facts, figures, codes and attributions unchanged.

  2. Version 25 Aug 2026, 13:49

    Corrected the directions and distances to nearby aerodromes to match the geographic reference data.

  3. Version 15 Aug 2026, 13:49

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.