FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02LA180 · Cessna 172N

2 Jun 2002 · Alhambra, CA, United States

Cableair Cessna 172N · Accident: total loss of engine power (non-mechanical) en route

From Bermuda Dunes Airport (UDD) to Santa Monica Municipal Airport (SMO)

Report a problem

Event

NTSB case
LAX02LA180
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
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 172N

Aircraft type
Cessna 172
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
N6629E
Operator
Cableair
Onboard fatalities
Unknown
Route
From Bermuda Dunes Airport (UDD), Bermuda Dunes, CATo Santa Monica Municipal Airport (SMO), Santa Monica, CA
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
En route · cruise
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
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, incorrect
  • Pilot in command › Fuel supply, not verified
  • Pilot in command › Refueling, not performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted a sign located on the Interstate's divider during a forced landing following a loss of engine power while in cruise flight. The pilot had initially reserved a Cessna 172 equipped with 50-gallon fuel tanks and initially planned the trip with that airplane in mind. His passenger called to ask if his friend could accompany them. The pilot stated that he would have to get back with him after checking the weight and balance. He reworked his weight and balance calculations and determined that they would be 66 pounds over gross with full fuel, golf clubs, and an additional person. The pilot went to the airport to check on the airplane and see how much fuel was on board. When he got to the airport he saw that the accident airplane, which had 40-gallon fuel tanks, had just returned from a flight. He talked to the pilot about how the airplane handled and what the fuel level was. The pilot that had just returned in the airplane stated that it was running fine and he had flown about 1 hour 50 minutes. The pilot recalculated the weight and balance and found that the accident airplane would be within limits with his two passengers and their baggage. He estimated his trip time would be 3 hours with a fuel burn of 6 gallons per hour. The pilot subtracted the 2 hours of flight time from the previous flight, in addition to his trip time of 3 hours, and calculated he would have 1.6 hours of reserve fuel on board at the completion of his trip. The pilot determined that this would be plenty of fuel to make the trip. Prior to takeoff the pilot conducted a preflight inspection, which included visually checking the fuel level. The aircraft arrived at the destination after an 1 hour 15 minute flight, and the pilot did not have the airplane refueled. The next day when they returned to the airport for the return flight the pilot did not visually inspect the fuel tanks and departed. One hour and 12 minutes later the engine lost power and the pilot landed on an interstate highway. Post accident inspection of the airplane revealed that the fuel tanks were intact, but empty, with no other breeches or leakage in the fuel system lines found. Review of the Cessna 172N Pilot Operating Handbook revealed the fuel flow for 65 percent brake horsepower settings at the cruise altitudes would have been between 7.2 and 7.4 gallons per hour.

Probable cause

the pilot's miscalculated fuel consumption, failure to verify the fuel supply on board, and his failure to refuel the airplane prior to takeoff, which resulted in fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02LA180
Event ID
20020606X00814
Case number
LAX02LA180
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-06-03.
  • API snapshot SHA-256: 023fe3524d1309cc6e60ead1c5b89b0a897983ee06986037c49ff0ed24368a89; retrieved 2026-09-21T19:42:34.597Z.