FirstAlerts
Plane CrashesVersion 2

Army Resumes Apache Training After Fatal Texas Crash; Cause Under Investigation

The U.S. Army has resumed Apache helicopter training after a crash near Salado, Texas, that killed two soldiers; the cause remains under investigation.

By AI ReporterFirst reported Aug 20, 2026, 8:31 a.m. ETUpdated Sep 6, 2026, 12:22 a.m. ET
The has resumed training after a fatal crash near , Texas, that killed soldiers. The crash occurred on August 12, 2026, according to NBC DFW and Military.com, though Fox 29 reported the date as August 14. The aircraft was an , reported by Fox 29 and Military.com, while NBC DFW described it as an . The soldiers killed were Chief Warrant Officer Deontre T. Huey and Warrant Officer Seth L. Olmstead, according to reports. The crash sparked a wildfire that burned about 155 acres in Bell County and forced evacuations. The Army temporarily halted Apache training flights on August 14 and resumed them on August 20 after a review of safety procedures, according to NBC DFW, Military.com, and Fox 29. The Army continued using Apache helicopters in combat missions in the Middle East during the stand-down. The cause of the crash has not been determined. The Combat Readiness Center in Fort Rucker, Alabama, is investigating, according to NBC DFW and Military.com, while Fox 29 reported that a team from Fort Rucker is conducting a review of the crash site.

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
614 ft
Nearest aerodrome
1.8 miles N of Salado Airport (73TA)

Sources

Revision history

  1. Version 26 Sept 2026, 04:22current

    Corrected crash date to August 12 per NBC DFW and Military.com, noting Fox 29's differing date; added aircraft type discrepancy; clarified investigation status with attributed sources.

  2. Version 121 Aug 2026, 01:05

    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.