WPR26LA065 · Cessna 150F
Cessna 150F · Accident: fuel exhaustion en route
From Lake Havasu City Airport (HII) to French Valley Airport (F70)
Event
- NTSB case
- WPR26LA065
- 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
- Event fatalities
- Unknown
- 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
- Visual Meteorological Cond
Cessna 150F
- 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
- N8155S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Havasu City Airport (HII), Lake Havasu, AZTo French Valley Airport (F70), Temecula, CA
- Aircraft age
- About 59 years (built 1966)
- 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 · cruise
- 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
- Fuel exhaustion
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the airplane reported that he was conducting a round-trip cross-country flight from his home airport to another airport. The pilot departed his home airport with full fuel tanks (26 gallons of fuel, of which 3.5 gallons were unusable) and he estimated it would have provided about 4.5 hours of flight time for the flight. Upon arrival at the destination airport, the pilot observed both fuel gauges at about 3/4 of a tank, he however, did not visually verify or measure the fuel levels in either tank. The pilot initially stated that his flight time on the outbound leg was approximately 2 hours, 10 minutes. However, he later reported that it was about 1.5 hours. He added that during the return portion of the flight at an altitude of about 8,500 ft mean sea level, the airplane encountered stronger-than-anticipated headwinds, that resulted in a reduced ground speed. He added that he also encountered up and down drafts, which resulted in him adding power and enriching the mixture to maintain altitude and airspeed. As the airplane approached the destination airport, the engine began to lose power and subsequently experienced a total loss of engine power. The pilot reported that he was unable to restore engine power and initiated a forced landing on an unlit road. During the landing flare, he realized that the road had turned, and he subsequently landed in a vineyard. The airplane struck multiple metal ground stakes, which resulted in substantial damage to both wing struts and horizontal stabilizers. The pilot added that for fuel planning purposes, he used his prior experience operating the accident airplane to estimate fuel consumption. Recorded ADS-B data for the initial flight spanned about 1 hour, 20 minutes, and started about 1.5 nm south of the departure airport and ended about 9.5 nm west of the destination airport. ADS-B data for the return flight spanned about 2 hours, 10 minutes, and began about 12 nm west of the departure airport and ended about 6 nm east of the accident site. According to the airplane’s cruise performance chart, at a cruise altitude of 7,500 ft and a power setting of 2,700 RPM, and a lean mixture, the airplane’s cruise endurance was approximately 4.1 hours. The chart also noted that the endurance and range calculations did not include allowances for takeoff or fuel reserve. Additionally, the cruise performance chart did not include fuel burn calculations for a climb from takeoff to a cruise altitude, which is however provided in the maximum rate of climb data chart. Postaccident examination of the airplane revealed no evidence of any pre-accident mechanical malfunctions or failures that would have precluded normal operation. The fuel tanks or fuel lines were not breached. The left fuel tank contained about 4 ounces of fuel and the right fuel tank contained about 1/4 gallon of fuel.
Probable cause
The pilot’s inadequate preflight inspection and fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR26LA065
- Event ID
- 20251222202192
- Case number
- WPR26LA065
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-12-20.
- API snapshot SHA-256: e67cd62d4d6fc7e561224a1190819f06c08b93ed463356e55d3030d1137721d6; retrieved 2026-09-16T20:37:16.699Z.