Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 12, 2026 · Lancair 235 NO Series · N10CF

Hillsboro, OR

Overview

Report Status
Factual report
Event Type
Accident
Date
June 12, 2026
Injury Outcomes
1 injury (1 fatality)
Location
Hillsboro, OR
Aircraft
Lancair 235 NO Series (2014)
Tail Number
N10CF
Injuries
Fatal
Aircraft Damage
Substantial
NTSB Number
WPR26FA217

On June 12, 2026, at about 1508 Pacific daylight time, a Lancair 235, N10CF, was destroyed when it was involved in an accident near Hillsboro, Oregon. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A pilot-rated witness located near the runway, just south of midfield, observed the accident sequence. During the airplane’s takeoff roll on runway 02, he reported the airplane’s nosewheel lifted off the runway surface within the first third of the runway and subsequently settled back to the runway. He observed the nosewheel rise off the runway a second time, followed by a reduction of engine noise. He also noted that the airplane appeared to decelerate. As the airplane crossed about the runway midpoint, he heard the engine noise increase. He lost sight of the airplane as it passed behind a rise in the terrain. He then heard sounds that he associated with the airplane impacting terrain. A second pilot-rated witness stated he observed the airplane start its takeoff roll and observed the nose lift off about halfway down the runway, though the airplane was not yet airborne. The airplane briefly passed behind a building, obscuring his view, at which time he heard a reduction in engine noise. He then heard a sound he associated with heavy braking, followed by the application of engine power. About two seconds later, he heard a second reduction in power and a sound of “locked up brakes.” The airplane came back into his field of view, and he observed white smoke from the tires. Another witness, who was located about 500 ft northeast of the departure end of runway 02, stated that he heard tires “chirping” followed by the sound of an engine “rev.” He then saw an airplane come off the end of the runway at a low altitude. He stated that the nose of the airplane pitched up and then the airplane rolled left. He observed the left wing impact terrain and the airplane cart-wheel before coming to rest and catching fire. Dashcam footage obtained from the driver of a privately owned vehicle traveling eastbound on SW River Road depicted the accident airplane exiting the departure end of runway 02 in a nose-high attitude. The camera’s view of the airplane was temporarily obstructed by vegetation; it then reappeared in a left-bank attitude as the left wing impacted terrain. Figure 1 Map depicting location of witness's, skid marks and main wreckage. The red lines represent skid marks. Examination of the runway surface revealed parallel, dark skid marks consistent with the accident airplane’s main landing gear tire tread and track width. The skid marks began about 1,000 ft from the start of runway 02, beginning with an intermittent mark from the right tire about 90 ft long, then continuing with marks from both tires for about 160 additional feet. A second set of skid marks was identified, beginning about 1,800 ft from the start of runway 02 and continuing for about 660 ft. A 66-inch-long gouge was observed in the pavement, extending off the departure end of runway 02. The gouge contained abraded material consistent with composite rudder material from the accident airplane. The wreckage was located in an area of uneven terrain in tall vegetation. All major structures were accounted for at the accident site. The airplane came to rest about 350 feet north of the runway on a magnetic heading of 195°. The first identified point of contact was disturbed soil located about 33 feet south of the main wreckage, where a single propeller blade was embedded. The fuselage and cabin area were mostly consumed by fire. The left wing was also consumed by fire. The right wing was thermally damaged and mostly intact, and the right-wing fuel tank was thermally damaged and breached. The empennage was separated from the fuselage and located adjacent to and north of the main wreckage; it sustained thermal damage, but was largely intact. The engine and firewall structure were thermally damaged, separated from the fuselage and located alongside and north of the main wreckage. The lower edge of the rudder exhibited abraded material consistent with the pavement gouge observed at the departure end of runway 02. The wreckage was retained for further examination.

Full Narrative

On June 12, 2026, at about 1508 Pacific daylight time, a Lancair 235, N10CF, was destroyed when it was involved in an accident near Hillsboro, Oregon. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A pilot-rated witness located near the runway, just south of midfield, observed the accident sequence. During the airplane’s takeoff roll on runway 02, he reported the airplane’s nosewheel lifted off the runway surface within the first third of the runway and subsequently settled back to the runway. He observed the nosewheel rise off the runway a second time, followed by a reduction of engine noise. He also noted that the airplane appeared to decelerate. As the airplane crossed about the runway midpoint, he heard the engine noise increase. He lost sight of the airplane as it passed behind a rise in the terrain. He then heard sounds that he associated with the airplane impacting terrain. A second pilot-rated witness stated he observed the airplane start its takeoff roll and observed the nose lift off about halfway down the runway, though the airplane was not yet airborne. The airplane briefly passed behind a building, obscuring his view, at which time he heard a reduction in engine noise. He then heard a sound he associated with heavy braking, followed by the application of engine power. About two seconds later, he heard a second reduction in power and a sound of “locked up brakes.” The airplane came back into his field of view, and he observed white smoke from the tires. Another witness, who was located about 500 ft northeast of the departure end of runway 02, stated that he heard tires “chirping” followed by the sound of an engine “rev.” He then saw an airplane come off the end of the runway at a low altitude. He stated that the nose of the airplane pitched up and then the airplane rolled left. He observed the left wing impact terrain and the airplane cart-wheel before coming to rest and catching fire. Dashcam footage obtained from the driver of a privately owned vehicle traveling eastbound on SW River Road depicted the accident airplane exiting the departure end of runway 02 in a nose-high attitude. The camera’s view of the airplane was temporarily obstructed by vegetation; it then reappeared in a left-bank attitude as the left wing impacted terrain. Figure 1 Map depicting location of witness's, skid marks and main wreckage. The red lines represent skid marks. Examination of the runway surface revealed parallel, dark skid marks consistent with the accident airplane’s main landing gear tire tread and track width. The skid marks began about 1,000 ft from the start of runway 02, beginning with an intermittent mark from the right tire about 90 ft long, then continuing with marks from both tires for about 160 additional feet. A second set of skid marks was identified, beginning about 1,800 ft from the start of runway 02 and continuing for about 660 ft. A 66-inch-long gouge was observed in the pavement, extending off the departure end of runway 02. The gouge contained abraded material consistent with composite rudder material from the accident airplane. The wreckage was located in an area of uneven terrain in tall vegetation. All major structures were accounted for at the accident site. The airplane came to rest about 350 feet north of the runway on a magnetic heading of 195°. The first identified point of contact was disturbed soil located about 33 feet south of the main wreckage, where a single propeller blade was embedded. The fuselage and cabin area were mostly consumed by fire. The left wing was also consumed by fire. The right wing was thermally damaged and mostly intact, and the right-wing fuel tank was thermally damaged and breached. The empennage was separated from the fuselage and located adjacent to and north of the main wreckage; it sustained thermal damage, but was largely intact. The engine and firewall structure were thermally damaged, separated from the fuselage and located alongside and north of the main wreckage. The lower edge of the rudder exhibited abraded material consistent with the pavement gouge observed at the departure end of runway 02. The wreckage was retained for further examination.

Flight

Event TypeAccident
Event Time15:08 PDT
Nearest AirportStark'S Twin Oaks Airpark (0.5nm NNE)
Runway02
Runway Length2465 ft
Runway Width48 ft
Aircraft FireGrd
Aircraft ExplosionUnknown

Aircraft

AircraftLancair 235 NO Series
Tail NumberN10CF
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Seats2

People & Injuries

Injury Summary1 injury (1 fatality)
Fatal1
Serious0
Minor0
Uninjured0
Total1

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point46 F
Altimeter30.10 inHg
Observation Time15:00
Weather SourceWFAC

Appendix: Source Data