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

Cessna 150L accident near Glen Avon, Oregon, December 4, 2024

On December 4, 2024 at about 10:20 pm local time, a 1972 Cessna 150L, registered N5330Q, was substantially damaged in an accident during enroute (cruise) near Glen Avon, Oregon. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

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 October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 4, 2024 · about 10:20 pm local time
Place
Glen Avon, Oregon · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 150L, built 1972 · all 150Ls on the register
Registration
N5330Q · registry record · serial 15073230
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On December 4, 2024, about 1420 Pacific standard time, a Cessna 150L, N5330Q, sustained substantial damage when it was involved in an accident near Glen Avon, Oregon. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he was on the return leg of a cross-country flight to Bend Municipal Airport (KBDN), Bend, Oregon. About 20 miles into the trip, at an altitude of about 8,000 feet mean sea level (msl), the engine started to run rough. The pilot applied carburetor heat, but the engine continued to run rough. The pilot then verified that the magnetos were on BOTH, that the mixture was full RICH, and closed carburetor heat. The engine continued to run rough, and the pilot declared an emergency as the airplane was unable to maintain altitude in mountainous terrain. The pilot initiated a forced landing to a logging road. Subsequently, the airplane struck trees and sustained damage to both wings. The airplane was recovered to a secure facility for further examination.

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 enroute (cruise) defining event

The aircraft

  • Seats: 2
  • Landing gear: fixed
  • Operator: Bend Aircraft Mechanics LLC

The flight

  • Departed from: 7S3 Hillsboro OR
  • Destination: KBDN Bend OR

Weather at the time

  • Light: daylight
  • Wind: from 110° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 41°F (5°C), dew point 34°F (1°C)
  • Altimeter: 30.27 inHg
  • Observation at 1:53 pm from KUAO, 19 miles away

Weather report (METAR): KUAO 042153Z 11005KT 10SM CLR 05/01 A3027 RMK AO2 SLP252 T00500011

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.