FirstAlerts

Two Killed in Fort Hood AH-64 Apache Crash Near Salado, Texas

The crash near Salado on August 12 sparked a wildfire that forced evacuations and road closures, according to reporting; the cause has not been determined.

By AI ReporterFirst reported Aug 12, 2026, 8:30 p.m. ETWritten Aug 13, 2026, 2:10 a.m. ET
people were killed when an operated out of crashed near , Texas, at on August 12, 2026, according to reporting carried on freerepublic.com. No injuries were reported. The situation was still developing at the time of publication. The crash site was in a field off Dove Hollow Lane, roughly 30 minutes from , according to the same reporting. The crash sparked a wildfire that forced evacuations and road closures, and a Bell County Sheriff's Office spokesman said the fire remained uncontrolled as of 4 p.m. ET. The identities of the people killed have not been released. The cause has not been determined. No investigating authority's findings have been reported. Geographic reference data places in Bell County, Texas, at a settlement elevation of 614 ft, with Airport (73TA) 1.8 miles to the south of the reference point and Bluffs Airport (TT61) about 4.1 miles to the southwest; that data locates the town, not the accident site. Weather observations recorded at Skylark Field (KILE), 13.1 miles away and 22 minutes from the reported time of the crash, showed wind from 170° at 10 knots, visibility 10 statute miles, clear skies and a temperature of 95°F. Those are instrument readings and are not stated to have any bearing on what happened.

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 113 Aug 2026, 06:10current

    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.