Army Grounds Apache Training Flights After Texas Crash That Killed Two Pilots
Two Fort Hood crew members died in a crash near Salado, Texas, and the Army says a Combat Readiness Center team is investigating; the cause has not been determined.
This is a developing story. Details reported early are provisional and are frequently revised. Where sources disagree, both readings are given.
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
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2mymotherlode.com
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2panow.com
- U.S. Army halts all Apache helicopter training flights after 2 soldiers died in crashfirstalert4.com
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2krgv.com
- Army halts Apache training flights after fatal Fort Hood helicopter crash kills 2 soldierskwtx.com
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2local10.com
- The Army ordered an Apache training stand-down after this week’s crashnbcdfw.com
- Army temporarily grounds training flights of Apache helicopters after Fort Hood crashstripes.com
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2wral.com
Revision history
- Version 715 Aug 2026, 09:27current
Added Local 10 to the outlets attributed for the aircraft type, operator, date, casualty figures and the Army's investigation statement.
- Version 615 Aug 2026, 05:27
Added KWTX and mymotherlode.com reporting, the conflicting time accounts (1:34 p.m. vs Tuesday afternoon), the record that this is the fourth Army Apache crash of 2026 and the only fatal one, and corrected the operator registry count to four.
- Version 515 Aug 2026, 02:19
Added First Alert 4 reporting (including its competing Aug. 11 date and "Apache attack helicopter" description) and corrected the operator fleet count on the registry from one to three.
- Version 415 Aug 2026, 01:58
Corrected operator fleet figure to one aircraft on the registry, added panow.com's differing cause characterization and the operator-name variant, and tightened the closing reference-data paragraphs.
- Version 315 Aug 2026, 01:55
Introduced the U.S. Army explicitly in the lead as the operating service and as the institutional source of all quoted statements, with a note that no individual official was named. Restructured the investigation section so the Army is identified as the speaker before each "said" attribution, replacing bare trailing "the Army said" constructions with clearly sourced institutional attribution. Added the named investigating bodies from the fact set and restored WRAL's "Wednesday crash" wording. Aircraft-type disagreement, both investigation-status accounts, figures, names, ranks, ages and all reference-data caveats retained unchanged; nothing added beyond the fact set.
- Version 215 Aug 2026, 01:43
Added victims' ages, hometowns and unit, the crash site's distance from Fort Hood, the Fort Rucker safety investigation team, the sourced disagreement over aircraft type, and a note that the individual aircraft is unidentified; corrected the direction to Salado Airport.
- Version 115 Aug 2026, 01:20
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.