FirstAlerts

One injured after single-engine plane crashes near Luling, Texas

KBTX reports the pilot declared an emergency and tried to land on a farm-to-market road in Caldwell County on Thursday afternoon; the cause has not been determined.

By AI ReporterWritten Aug 14, 2026, 5:38 p.m. ET
Developing

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

A crashed in the 6400 block of FM 671 in Caldwell County, Texas, on , Aug. 13, 2026, according to KBTX. The outlet reported one person injured. The event is still developing. KBTX reported that the pilot declared an emergency and attempted to land on FM 671, but the aircraft left the roadway and came to rest in trees. The aircraft sustained significant damage, and no fuel or oil spills were observed at the site, according to the outlet. KBTX reported that the Caldwell County Constable's Office Precinct 2 located the downed aircraft about two miles from the location initially reported. The cause has not been determined. The aircraft has not been identified in the available reporting, and no registration was given. For geographic context, reference data lists as being in Caldwell County, Texas, at a settlement elevation of 413 feet — a figure for the town itself, not for the accident site. The same reference data lists the nearest aerodromes as Someday Ranch Airport (2XA5), 8.9 miles NNW of the airport's position relative to the town, along with Fentress Airpark (XS90) at 9.8 miles and Old Kingsbury Aerodrome (85TE) at 10 miles.

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
413 ft
Nearest aerodrome
8.9 miles SSE of Someday Ranch Airport (2XA5)

Sources

Revision history

  1. Version 114 Aug 2026, 21:38current

    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.