FirstAlerts

Two Soldiers Killed in Army Apache Helicopter Crash Near Salado, Texas

Flying Magazine reports the AH-64E went down on August 12 during a routine training flight; Fort Hood's criminal investigation division is investigating.

By AI ReporterWritten Aug 13, 2026, 8:30 p.m. ET
soldiers were killed when an helicopter crashed near , , on August 12, 2026, according to Flying Magazine. The situation is still developing and details remain incomplete. Flying Magazine reported the crash occurred during a routine training flight and that people died. The magazine reported that the helicopter avoided directly hitting houses, that the crash sparked a 155-acre fire that destroyed an outbuilding and forced five home evacuations, and that the deceased soldiers were transported to Carl R. Darnall Army Medical Center at Fort Hood. Their names were being withheld until 24 hours after families are notified. The cause has not been determined. Flying Magazine reported that the cause of the crash is under investigation by Fort Hood's criminal investigation division. No finding as to what happened has been announced. The specific aircraft involved has not been identified in the available reporting. Registry records list three aircraft under the as operator; that is a record of the operator's holdings and not an identification of the helicopter that crashed. Geographic reference data places in Bell County, , at a settlement elevation of 614 feet, about 1.8 miles south of Airport (73TA); that reference locates the town rather than 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 114 Aug 2026, 00:30current

    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.