FirstAlerts
Plane CrashesVersion 2

NTSB Investigating Fatal Luscombe 8A Crash Near Canton, Texas

One person aboard was killed in the July 14, 2026 accident, according to the National Transportation Safety Board accident record; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:59 a.m. ET
A single-engine crashed near Canton, Texas, on July 14, 2026, at about 1:56 p.m. local time, according to the National Transportation Safety Board accident record. The record lists one person aboard and one fatality. The aircraft is identified in the accident record as . Federal aircraft registry records list as a , a single-engine piston landplane, serial number 3891, with a Continental Motors A&C65 series engine, registered in the United States. The registry lists the registered owner as Allan William B; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. Geographic reference data places Canton in Van Zandt County, Texas, giving a terrain elevation for the settlement itself — not the accident site — of 509 ft, and listing the location as 3.4 miles S of Canton Hackney Airport (K7F5), 5.0 miles E of Vogt's Vista Airport (TT73) and 5.4 miles S of Thompson Field (1TA7). Reference data of this kind describes the place only and says nothing about what happened. As a matter of record, the NTSB database, which begins in 2008, contains 52 other cases involving the , of which 6 involved a fatality. That count is a record of past cases and says nothing about the cause of this accident. The NTSB is investigating. The cause has not been determined.

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.

Registration
N1164K
Type
Luscombe 8A — single-engine piston landplane
Engines
CONT MOTOR A&C65 SERIES
Registered owner
Allan William BThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
509 ft
Nearest aerodrome
3.4 miles S of Canton Hackney Airport (K7F5)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:59current

    Corrected the aerodrome bearings to match the geographic reference data as given and clarified that the 509 ft elevation is for the settlement, not the accident site.

  2. Version 15 Aug 2026, 15:02

    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.