LAX99LA099 · Cessna 172N
Cessna 172N · Accident: total loss of engine power (non-mechanical) on approach
From Long Beach International Airport (LGB) to Monterey Regional Airport (MRY)
Event
- NTSB case
- LAX99LA099
- 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
- Instrument 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
- N7374D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, CATo Monterey Regional Airport (MRY), Monterey, 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
- Approach · IFR final approach
- 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 › Became lost/disoriented
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot attempted three ILS approaches, but reported that he was having problems with the navigation equipment during each approach. At the end of the third approach he advised ARTCC that he was low on fuel, with only about 30 minutes remaining. The pilot relayed through another aircraft that he had visual contact with the airport and was below the clouds. He canceled IFR and reported that landing was assured. He saw an airport beacon ahead, flew toward it, and attempted to activate the pilot-controlled lighting. The lights did not illuminate and the pilot realized he was about midfield of the runway and too high for a safe landing. He initiated a go-around and the engine quit. The aircraft crashed about 7 miles north of the pilot's intended destination airport and about 3/4 miles north of an uncontrolled airport. The aircraft was examined following recovery. No fuel was found in the fuel tanks or lines, and no evidence of leakage was observed. Comparison of the Hobbs meter readings between departure and the accident revealed that the pilot had flown 4.4 hours during the accident flight. The pilot reported that he had not experienced any mechanical problems with the engine or aircraft prior to the accident. The navigation radios in the aircraft were tested with no discrepancies found. A functional test of the ground navigational aids was performed following the accident with no noted discrepancies. The pilot did not provide evidence of instrument currency.
Probable cause
Fuel exhaustion due to the pilot's becoming lost and disoriented during multiple attempts at completing an ILS approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA099
- Event ID
- 20001205X00190
- Case number
- LAX99LA099
- 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: investigation status. 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: 7d121c22755d5f5e960cda1baff39f80ceecd110c7bead703a6a6c941876779d; retrieved 2026-09-22T15:52:57.390Z.