LAX96LA205 · Cessna 150M
Candace Larned Enterprises Cessna 150M · Accident: total loss of engine power (non-mechanical) on approach
From Long Beach International Airport (LGB) to Los Banos Municipal Airport (LSN)
Event
- NTSB case
- LAX96LA205
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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 150M
- 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
- N66392
- Operator
- Candace Larned Enterprises
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, CATo Los Banos Municipal Airport (LSN)
- Aircraft age
- Not recorded
- 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
- Approach · VFR pattern final
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion; 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel consumption calculations, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had performed a preflight inspection and observed that the fuel tanks appeared full, and departed for the cross-country flight. After flying for about 3.4 hours, the engine sputtered followed by the propeller stopping. During the forced landing the airplane collided with a pole. The FAA reported finding no evidence of any mechanical malfunctions relating to the engine. The pilot subsequently reported that when he initiated the flight the fuel gages registered 3/4 full. Approaching the destination airport, the gages registered 1/4 full. During the flight the pilot had cruised between 4,500 and 6,500 feet msl. According to the Cessna, the engine can develop over 75 percent power when below 7,000 feet, during which time the fuel consumption rate can exceed 6 gallons per hour.
Probable cause
fuel exhaustion due to the pilot's improper in-flight decision to utilize a high engine power setting which reduced the airplane's endurance, and the pilot's inadequate fuel consumption calculations.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA205
- Event ID
- 20001208X05817
- Case number
- LAX96LA205
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-05-26.
- API snapshot SHA-256: ea408f199380b7750d8d388ca7c15eaa8dee9c554baa49ec4070ca3c0ab91f15; retrieved 2026-09-21T21:48:22.059Z.