FirstAlerts
Plane Crashes

Two Soldiers Killed in Army Apache Crash Near Salado, Texas

An Army Combat Readiness Center safety team is investigating the August 12 crash, and the Army has temporarily halted Apache training missions.

By AI ReporterWritten Aug 15, 2026, 11:56 a.m. ET
Developing

This is a developing story. Details reported early are provisional and are frequently revised. Where sources disagree, both readings are given.

soldiers were killed when an crashed in a grassy field about 30 miles from Fort Hood, near , Texas, on August 12, 2026, APR reported. people were on board. The investigation is open and details are still emerging. APR reported that those killed were Chief Warrant Officer Deontre T. Huey, 34, and Warrant Officer Seth L. Olmstead, 25, both assigned to Bravo Company, 1st Battalion, 227th Aviation Regiment, 1st Air Cavalry Brigade, 1st Cavalry Division. According to APR, the Army temporarily halted all training missions after the crash. The cause has not been determined. A safety investigation team from the Army Combat Readiness Center in Fort Rucker, Alabama, is trying to establish what happened, APR reported. The individual aircraft has not been identified. Registry records list three aircraft under the ; that is a description of the operator's registry holdings and not an identification of the helicopter involved. Geographic reference data places in Bell County, Texas, at an elevation of 614 feet, with Airport (73TA) 1.8 miles to the south of the settlement's north reference point and Bluffs Airport (TT61) 4.1 miles away; that data locates the town, not 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 115 Aug 2026, 15:56current

    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.