WPR22FA021 · Cessna 150L
Cessna 150L · Accident: VFR encounter with IMC en route
From Ashland Municipal Airport Sumner Parker Field (S03) to Haigh Field (O37)
Event
- NTSB case
- WPR22FA021
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna 150L
- Aircraft type
- Cessna 150
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5268Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ashland Municipal Airport Sumner Parker Field (S03), Ashland, ORTo Haigh Field (O37), Orland, CA
- Aircraft age
- About 49 years (built 1972)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- VFR encounter with IMC
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The non-certificated pilot departed on a cross-country flight that required multiple fuel stops. The weather forecast called for clouds near the accident site. During the fuel stops, the pilot recharged the battery and, at one instance, refused assistance from witnesses to find and replace his alternator. Witnesses stated that he sparingly used the battery power for takeoff and landing and continued his cross-country flight with a known inoperable alternator. Postaccident examination of the cockpit revealed that the master switch was in the OFF position. With the master switch in the OFF position, the electrical system was not powered, and the airplane was not able to transmit its aircraft positions over its automatic dependent surveillance-broadcast (ADS-B) system. The field examination of the airplane wreckage did not reveal any mechanical malfunctions or failures that would have precluded normal operation. A witness near the top of the mountain reported that clouds and fog were present and provided a visibility of about 200 ft. He added that, about the time of the accident, he heard a low-flying airplane and was able to distinguish noise consistent with a running engine but did not hear the airplane’s impact with terrain. He further reported that the fog was present for most of the morning, lasting through the early afternoon. The pilot was likely flying the airplane low over the interstate to stay out of the clouds. He then likely entered instrument meteorological conditions as the airplane approached the mountain valley and turned back towards the departure airport before impacting trees in a wings-level attitude. No record was found indicating that the pilot received a preflight weather briefing; however, it could not be determined if the pilot obtained weather information using other sources. The pilot’s toxicology results indicate that he may have been experiencing impairing effects of diphenhydramine, such as sedation, at the time of the crash, and may also have been experiencing mild symptoms of uncontrolled diabetes, such as fatigue or blurry vision. However, the pilot’s decision to attempt the risky flight is unlikely to have been directly affected by these medical factors. Thus, given that the airplane was in controlled flight at the time of its collision with visually obscured terrain, there is low likelihood that the pilot’s diphenhydramine use or uncontrolled diabetes contributed to the crash.
Probable cause
The non-certificated pilot’s improper decision to continue the flight under visual flight rules into instrument meteorological conditions which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA021
- Event ID
- 20211022104148
- Case number
- WPR22FA021
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 879eac29a8e3cc55f31ee397d2cbbbf71a516ec53fdf92960e1a3f2d3fe9f804; retrieved 2026-09-15T07:35:56.280Z.