FirstAlerts
Plane CrashesVersion 2

One dead in crash of homebuilt Montana Coyote near Fredericksburg, Virginia

The accident record lists a single person on board and one fatality; the National Transportation Safety Board's investigation is open and the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:26 a.m. ET
One person was killed when a homebuilt Montana Coyote aircraft crashed near Fredericksburg, Virginia, on July 14, 2026, at about 3:05 p.m. local time, according to the accident record. The record lists one person on board and one fatality. The aircraft is identified in the accident record as a registered as . Aircraft registry records list as a Montana Coyote registered in the United States. Geographic reference data places the settlement of Fredericksburg at an elevation of 46 feet, 2.3 miles north of Shannon Airport (KEZF), 4.1 miles south of Dogwood Airpark (VA42) and 6.8 miles south of Stafford Regional Airport (KRMN). That reference locates the city, not the accident site. No departure or destination airport is given in the accident record. The National Transportation Safety Board is investigating. The investigation is open and 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
N448VQ
Type
Montana Coyote
Terrain elevation
46 ft
Nearest aerodrome
2.3 miles N of Shannon Airport (KEZF)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:26current

    Corrected the compass directions between Fredericksburg and the three nearby aerodromes and clarified that the geographic reference locates 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.