LAX91LA188 · Enstrom F28C
Enstrom F28C · Accident: partial loss of engine power (mechanical failure) en route
From an unrecorded airport to L12 · Redlands, CA
Event
- NTSB case
- LAX91LA188
- 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
Enstrom F28C
- Aircraft type
- Enstrom F28
- Category
- Helicopter
- 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
- N214MM
- Operator
- Randy Testman
- Onboard fatalities
- Unknown
- Route
- From not recordedTo L12 · Redlands, 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 · 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 (mechanical failure)
- 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 starvation
- 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 › Starvation
- Fuel system, line › Leak
- Fuel system, line › Loose
- Other maintenance personnel › Maintenance, 100-hour inspection, inadequate
Approximate · Estimated position: the centre of Palm Springs, CA, the place the record names. Not the accident site.
NTSB narrative
DURING CLIMB THE PILOT NOTICED THAT THE ENG WAS NOT DEVELOPING FULL POWER. HE ALSO SMELLED FUEL WHEN THE HEATER VALVE WAS OPENED. THE ENG BEGAN TO RUN ROUGH, AND SMOKE CAME OUT OF THE BOTTOM OF THE HELICOPTER. A FORCED LANDING WAS MADE IN A CANYON BOTTOM COLLIDING WITH SMALL TREES. AFTER LANDING THE PILOT EXTINGUISHED A FIRE IN THE ENGINE COMPARTMENT. THE FUEL INLET LINE CONNECTOR TO THE ELECTRIC FUEL BOOST PUMP WAS FOUND LOOSE. IN ADDITION, A CONNECTOR ON THE UPPER DECK MANIFOLD PRESSURE LINE ATTACHED TO THE TURBOCHARGER INDUCTION TUBE WAS FOUND LOOSE. THE PILOT REPORTED THAT HE SMELLED FUEL ON 3/30, 4/12, AND 4/28, AND REPORTED THIS TO THE MAINTENANCE FACILITY FOR CORRECTION. A 100-HR INSPECTION WAS COMPLETED ON 4/11, 20.8 HOURS BEFORE THE ACCIDENT.
Probable cause
INADEQUATE INSPECTION OF THE FUEL SYSTEM RESULTING IN AN ENGINE POWER LOSS AND INFLIGHT FIRE DUE TO A LOOSE FUEL CONNECTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA188
- Event ID
- 20001212X16827
- Case number
- LAX91LA188
- 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: 371090525afd87b678b87fd042294db5e4045af1741d0302a5cad454433972d8; retrieved 2026-09-21T15:28:15.911Z.