FirstAlerts
Plane CrashesVersion 4

New Mexico delegation seeks Pentagon answers on medevac crash near Ruidoso that killed four

Two outlets report a Beechcraft King Air went down on approach with four crew aboard; the National Transportation Safety Board's investigation is open and the cause has not been determined.

By AI ReporterFirst reported Aug 5, 2026, 9:11 a.m. ETUpdated Aug 17, 2026, 8:55 a.m. ET
crew members were killed when a medevac crashed on near , New Mexico, according to reporting by ladailypost.com and dailymail.com. The two outlets give different dates and times: ladailypost.com reported the crash occurred on 13 May 2026, , while dailymail.com reported 14 May 2026 and said the aircraft was down . Both outlets reported people on board, all crew; dailymail.com put the death toll at . Ladailypost.com reported the crew of consisted of two pilots and two flight nurses, and that the aircraft had taken off from Roswell for Sierra Blanca Regional Airport in to pick up a patient. The cause has not been determined. Ladailypost.com reported that the National Transportation Safety Board's investigation into the crash is ongoing, and that there would be full cooperation with it. Dailymail.com reported on a basis 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; the same outlet reported that the Federal Aviation Administration had warned pilots 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. No NTSB finding, or final, appears in the available reporting. According to ladailypost.com, the New Mexico Congressional Delegation has sent a letter to Defense Secretary Pete Hegseth demanding answers about the Department of Defense's involvement. The outlet reported that lawmakers said this is reportedly the first time US military GPS jamming contributed to a civilian plane crash. Both outlets reported that the crash sparked a wildfire that took three weeks to contain and burned 31,860 acres, with suppression costs estimated at $37.7 million. Evacuation orders remained in place for several weeks and no structures were lost, the outlets reported. Dailymail.com reported that the Seven Cabins Fire has been burning in the Capitan Mountain Wilderness since 14 May. No registration for the aircraft appears in the available reporting, and the airframe has not been identified.

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 417 Aug 2026, 12:55current

    Added second source (ladailypost.com): congressional letter to Defense Secretary Pete Hegseth, Roswell-to-Ruidoso patient pickup, crew composition, wildfire acreage and suppression cost, open NTSB investigation; noted date/time conflicts and dropped the geographic reference paragraph.

  2. Version 37 Aug 2026, 14:06

    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.

  3. Version 25 Aug 2026, 13:49

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

  4. 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.