FirstAlerts
Plane CrashesVersion 2

One dead in experimental airplane crash near Yuba City, California

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

By AI ReporterUpdated Aug 7, 2026, 10:02 a.m. ET
One person was killed when an experimental amateur-built airplane crashed near Yuba City, California, on July 16, 2026, at about 2:01 p.m. local time, according to the official accident record. The record lists one person on board and one fatality. The accident record identifies the aircraft as a , registration . Aircraft registry records list as a Van's, a single-engine piston landplane registered in the United States. Geographic reference data places Yuba City in Sutter County, California, at a settlement elevation of 59 feet, and records the location as 1.3 miles NNW of Sutter County Airport (KO52), 3.9 miles NW of Yuba County Airport (KMYV/MYV) and 6.1 miles ENE of Vanderford Ranch Company Airport (CA73). That reference data locates the city, not the accident site. The National Transportation Safety Board is investigating, according to the accident record. The investigation remains 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
N98GB
Type
VAN''S β€” single-engine piston landplane
Terrain elevation
59 ft
Nearest aerodrome
1.3 miles NNW of Sutter County Airport (KO52)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:02current

    Clarified that the geographic reference data locates the settlement rather than the accident site, and attributed the NTSB investigation to the accident record.

  2. Version 15 Aug 2026, 15:03

    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.