LAX99LA122 · Aero Commander 500B
Aero Commander 500B · Accident: total loss of engine power (non-mechanical) during initial climb
From 0Q5 to 028 · Willits, CA
Event
- NTSB case
- LAX99LA122
- 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
Aero Commander 500B
- Aircraft type
- Aero Commander 500
- 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
- CFBCR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 0Q5To 028 · Willits, 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
- Initial climb
- 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
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, not verified
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to departure the pilot believed that his airplane contained between 30 and 40 gallons of fuel, adequate for a 15-minute-long flight to another airport where he could purchase additional fuel. The pilot reported the fuel gauge registered 40 gallons, so he departed. During initial climb upon reaching an altitude of about 400 feet above the ocean, both engines simultaneously lost power. The pilot rocked the airplane's wings and experienced a 'short surge of power.' However, it lasted only a brief moment and all engine power was again totally lost. The pilot turned toward the shoreline, reduced airspeed, and ditched about 0.25 miles off shore. The overnight tide/wave action subsequently beached most of the airplane. In the pilot's report, he did not indicate having experienced any mechanical malfunctions. The Federal Aviation Administration (FAA) coordinator examined recovered portions of the airframe and engines. In pertinent part, the FAA reported finding no physical evidence of any mechanical malfunction with the examined components. However, because of the airframe damage sustained during immersion in the salt water and the subsequent destruction to components, the Safety Board was unable to document the integrity of the fuel quantity indicator system.
Probable cause
Fuel exhaustion due to the pilot's failure to ensure that an adequate fuel supply was onboard. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA122
- Event ID
- 20001205X00346
- Case number
- LAX99LA122
- 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 1999-03-19.
- API snapshot SHA-256: 2046973abaa487b3c81b280d58d251a357fb487555a88f780d60e1da5dade05f; retrieved 2026-09-21T11:10:51.338Z.