FirstAlerts
Plane CrashesVersion 2

One killed in light aircraft crash near Bradley, Arkansas

The official accident record lists one person on board and one fatality in the August 19, 2025 crash; the National Transportation Safety Board investigation is open.

By AI ReporterUpdated Aug 7, 2026, 10:35 a.m. ET
One person was killed when a light aircraft crashed near Bradley, Arkansas, in the early hours of August 19, 2025, according to the official accident record. This is a developing matter and details may change. The accident record lists one person on board and one fatality, and gives the time of the accident as about local time. It describes the aircraft as destroyed and classifies the flight as a Part 91 general aviation flight. The record identifies the aircraft as a registered and lists the operator as . Aircraft registry records for list the type as a Sonex, a single-engine piston landplane registered in the United States; the two records differ on the aircraft type. The cause has not been determined. The National Transportation Safety Board is listed in the accident record as the investigating body, and the investigation is open. No preliminary findings are contained in the fact set. Geographic reference data places Bradley County, Arkansas, at a settlement elevation of 180 feet, about 9.0 miles south-southwest of Warren Municipal Airport (K3M9) and 18 miles east-southeast of Hampton Municipal Airport (K0R6). That reference locates the settlement only, not the accident 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.

Registration
N345LA
Type
SONEX — single-engine piston landplane
Terrain elevation
180 ft
Nearest aerodrome
9.0 miles SSW of Warren Municipal Airport (K3M9)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:35current

    Corrected the bearing to Warren Municipal Airport (south-southwest, per reference data, not north-northeast) and added the Hampton Municipal Airport reference.

  2. Version 15 Aug 2026, 21:44

    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.