The U.S. aircraft register, updated daily
Accidents · NTSB WPR27LA008 · Preliminary: the investigation is not finished

Hakala John Charles LANCAIR IV-P-T accident near Ontario, Oregon, October 5, 2026

On October 5, 2026, a 2004 Hakala John Charles LANCAIR IV-P-T, registered N5UC, was substantially damaged in an accident during initial climb near Ontario, Oregon. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 5, 2026 · cases in 2026
Place
Ontario, Oregon · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
not recorded
Aircraft
Hakala John Charles LANCAIR IV-P-T, built 2004
Registration
N5UC · registry record · serial LIV-524
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

On October 4, 2026, about 1822 mountain daylight time, a Lancair IV-P-T airplane, N5UC, was substantially damaged when it was involved in an accident near Ontario, Oregon. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the airplane departed Ontario Municipal Airport (ONO), Ontario, Oregon, destined for Provo Municipal Airport (PVU), Provo, Utah. During the initial climb, the airplane experienced a loss of engine power at an altitude of about 3,325 ft mean sea level. The pilot turned the airplane toward the departure airport, but then determined that he would be unable to reach the runway. He subsequently performed a forced landing in a field. While maneuvering to avoid a tree, the airplane’s left wing contacted the ground. The airplane sustained substantial damage to the fuselage and left wing. The wreckage was retained for further examination. Figure 1 Accident site (Courtesy of Malheur County Sheriff's Office)

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (partial) during initial climb defining event

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Operator: R V Stich Construction INC

The flight

  • Destination: PVU Provo UT

Weather at the time

  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR27LA008.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.