Army Grounds Apache Training Flights After Fatal Crash Near Fort Hood, Texas
Two aviators were killed in the August 12 crash of an AH-64 Apache during a training flight; the Army Combat Readiness Center is leading an open investigation.
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
- 741 ft
- Nearest aerodrome
- 5.7 miles ESE of Fort Hood Landing Strip 50 (US-6498)
Sources
- US Army grounds all Apache helicopter training missions after deadly crash in Texaskesq.com
- US Army grounds all Apache helicopter training missions after deadly crash in Texaskeyt.com
- US Army grounds all Apache helicopter training missions after deadly crash in Texaskrdo.com
- US Army grounds all Apache helicopter training missions after deadly crash in Texasktvz.com
- US Army grounds all Apache helicopter training missions after deadly crash in Texas - Local News 8localnews8.com
- US Army grounds all Apache helicopter training missions after deadly crash in Texascbs58.com
Revision history
- Version 515 Aug 2026, 04:24current
Added kesq.com to the attribution for the crash, crew fatalities and the Fort Rucker investigators' arrival.
- Version 415 Aug 2026, 04:09
Added cbs58.com reporting (including its account of the stand-down and investigators' arrival), the two-seat crew configuration detail, and corrected the registry fleet figures to 47 aircraft with 39 matching the type.
- Version 315 Aug 2026, 03:27
Added headline and dek; added keyt.com and ktvz.com attribution including the Fort Rucker location and crew fatality count; corrected the Army registry fleet figure from 85 to 54.
- Version 215 Aug 2026, 01:35
Added krdo.com reporting on the stand-down's duration as a sourced conflict with localnews8.com's account of the investigation, and corrected the operator fleet figure to the 85 aircraft in the registry records, removing unsupported type and airframe breakdowns.
- Version 115 Aug 2026, 01:29
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.