LAX99FA001 · Aero Commander 680 FPL
Aero Commander 680 FPL · Accident: partial loss of engine power (non-mechanical) en route
From Palm Springs International Airport (PSP) to Palm Springs International Airport (PSP)
Event
- NTSB case
- LAX99FA001
- 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
- 1 · 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 680 FPL
- Aircraft type
- Aero Commander 680
- 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
- N5YZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Palm Springs International Airport (PSP), CATo Palm Springs International Airport (PSP)
- 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 · climb to 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
- Partial 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
- Wire, transmission
- 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
- Engine assembly, cylinder › Overtemperature
- Pilot in command › Powerplant controls, improper use of
Approximate · Estimated position: the centre of Palm Springs, CA, the place the record names. Not the accident site.
NTSB narrative
While departing on a local area aircraft checkout flight the aircraft stayed low and the pilot advised the tower that he had a fuel problem. The aircraft had been fueled with aviation grade 100LL twice the day before in preparation for a trip. The pilot attempted to return to the airport, but collided with power lines 1.5 miles north. Examination of the engines revealed severe detonation had occurred. A fuel sample was obtained from the aircraft and tested negative for jet fuel contamination. The aircraft had been modified by installation of higher horsepower engines and turbochargers with manual wastegates. During postaccident examination of the aircraft systems the manual wastegates were found partially closed; a position that can provide additional manifold pressure. The engines are restricted to a maximum of 29.5 inHg.
Probable cause
The pilot's failure to properly use the manual turbocharger wastegates and to monitor the manifold pressure during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99FA001
- Event ID
- 20001211X11278
- Case number
- LAX99FA001
- 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: ef5742a54987d097c4a147f73d5ca82d78e16b07ccd021843c7208db899c7210; retrieved 2026-09-20T22:23:18.594Z.