FirstAlerts
Plane CrashesVersion 3

Single-Engine Plane Crashes at Roseburg Regional Airport; No Injuries Reported

A single-engine passenger plane crashed in a field at Roseburg Regional Airport on Saturday, Aug. 15, 2026; no injuries were reported and the cause has not been determined.

By AI ReporterFirst reported Aug 17, 2026, 4:00 p.m. ETUpdated Aug 29, 2026, 7:56 a.m. ET
A crashed at Regional Airport in , Oregon, at about on Saturday, Aug. 15, 2026, according to kpic.com and nbc16.com. Both outlets reported no injuries. The cause has not been determined. Firefighters found the aircraft in a field at the airport and there was no fire, the two outlets reported. Officials said no fluids were released as a result of the crash. Air traffic was redirected for a short time and the Federal Aviation Administration was notified. The crash was one of three separate calls firefighters handled in 14 minutes, along with a natural cover fire and a structure fire, according to kpic.com and nbc16.com. Weather observations recorded at Regional Airport (KRBG), 1.7 miles away and 12 minutes from the reported time of the crash, show wind from 20 degrees at 10 knots, visibility 10 statute miles, clear skies and a temperature of 80°F. Those are instrument readings only and say nothing about what happened. The aircraft has not been identified in the available reporting, and no registration or operator has been given. No findings from the FAA have been reported.

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
492 ft
Nearest aerodrome
1.7 miles SSE of Roseburg Regional Airport (KRBG/RBG)

Sources

Revision history

  1. Version 329 Aug 2026, 11:56current

    Single-Engine Plane Crashes at Roseburg Regional Airport; No Injuries Reported

  2. Version 218 Aug 2026, 14:23

    Dropped the "still developing" line, added the calendar weekday and second outlet attribution (kpic.com) to the reported details.

  3. Version 118 Aug 2026, 10:56

    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.