Two U.S. Army soldiers killed in Apache helicopter crash near Fort Hood, Texas
The crash occurred August 12, 2026, and the cause remains under investigation.
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
- Army temporarily halts Apache helicopter training missions after Texas crash that killed 2chicagotribune.com
- Army Halts Apache Training Flights After Fatal Fort Hood Crashdallasexpress.com
- Two US Army soldiers killed in Texas helicopter crash | Dunya Newsdunyanews.tv
- Two killed as US Army Apache helicopter crashes near Fort Hood base in Texastimesofindia.indiatimes.com
- Two soldiers dead after Apache helicopter crashes in Texasindependent.co.uk
- 2 people died in a military helicopter crash near Fort Hood, officials saykrgv.com
- 2 people died in a military helicopter crash near Fort Hood, officials say - KTSAktsa.com
- Army resumes Apache helicopter training missions after Texas crash that killed 2news4jax.com
Revision history
- Version 42 Sept 2026, 15:26current
Updated to reflect the latest reporting, including the identification of the soldiers and the conflicting accounts of the investigation lead.
- Version 318 Aug 2026, 23:52
Added crash date and time, victims' names and unit, the Army-wide Apache training halt, the 155-acre Dove Hollow Fire, the conflicting maintenance-test-flight account, competing investigating bodies and location names, and Brig. Gen. Diven's statement; removed the 'developing' framing.
- Version 213 Aug 2026, 08:13
Added Times of India as a second source, identified Coleman as Bell County Sheriff's Office spokesman and his "violent crash" description, added the wildfire evacuation of several homes, and noted the sourced variations in operator naming and investigation wording.
- Version 113 Aug 2026, 08:07
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.