- Date
- June 12, 2026, 15:08 local (22:08 UTC)
- Place
- Hillsboro, OR
- Injuries
- 1 fatal
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N10CFLancair 235
- Defining event
- Takeoff-rejected takeoff: Unknown or undetermined
- Weather
- Visual (VMC) · Day
- Status
- Investigation ongoing
- Investigation class
- Class 3
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20260612006799A
- Case key
- 203169
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Preliminary report
What NTSB knew early in the investigation. It may change in the final report.
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 wasobserved 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.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Aircraft
- Registration
- N10CF
- Reported as
- Lancair 235 (NO SERIES EXISTS)
- Category
- Airplane, amateur-built
- Serial number
- 203
- Built
- 2014
- Damage
- Substantial damage
- Fire
- On-Ground
- Flight
- Personal · Part 91
- Airworthiness certificate
- Special, Experimental (Special)
- Airport
- 7S3 · Stark's Twin Oaks Airpark, runway 02, 2,465 × 48 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Weather
- Conditions
- Visual (VMC) · Day
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 75 °F, dew point 46 °F
- Altimeter
- 30.10 inHg
- Observed at
- KUAO, 13 nm away
- METAR
- METAR KUAO 122153Z VRB03KT 10SM CLR 24/08 A3010 RMK AO2 SLP191 T02440083
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.