FirstAlerts
Plane CrashesVersion 2

One Dead in Lancair 235 Accident Near Hillsboro, Oregon

The accident record lists one person aboard and one fatality; the National Transportation Safety Board investigation is open and the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 9:17 a.m. ET
One person was killed when a was substantially damaged near Hillsboro, Oregon, on June 12, 2026, at about 10:08 p.m. local time, according to the accident record. The event is still developing and details may change. The accident record lists one person aboard and one fatality, notes that the aircraft sustained substantial damage, and classifies the flight as a Part 91 general aviation flight. The aircraft is identified in the record as a registered . The National Transportation Safety Board is listed as the investigating body, and the cause has not been determined. Aircraft registry records list as a Cooper John H , a single-engine piston landplane with a Lycoming O-290-D2 engine, serial number 203, registered in the United States. The registry lists the registered owner as Cooper John H; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. Registry information describes the airframe only and says nothing about what happened. Geographic reference data places Hillsboro in Washington County, Oregon, at a settlement terrain elevation of 213 ft, about 2.3 miles WSW of Portland Hillsboro Airport (KHIO), 2.6 miles SE of Olinger Airpark (OR81) and 4.8 miles SSE of Sunset Air Strip (1OR3). That data locates the city, not the accident site. The NTSB investigation remains open.

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
N10CF
Type
Cooper John H LANCAIR 235 — single-engine piston landplane
Engines
LYCOMING O-290-D2
Registered owner
Cooper John HThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
213 ft
Nearest aerodrome
2.3 miles WSW of Portland Hillsboro Airport (KHIO/HIO)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 13:17current

    Added the accident record's substantial-damage listing to the second paragraph and clarified that the geographic reference data locates the city rather than the accident site.

  2. Version 15 Aug 2026, 15: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.