LAX89LA199 · Piper PA-31-350
Northern Aviation Piper PA-31-350 · Accident: total loss of engine power (non-mechanical) on approach
From King County International Airport - Boeing Field (BFI) to Murray Field (EKA)
Event
- NTSB case
- LAX89LA199
- 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
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N35479
- Operator
- Northern Aviation
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo Murray Field (EKA), Eureka, 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 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
- Pilot in command › Fuel consumption calculations, inaccurate
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ESTABLISHED ON AN INSTRUMENT APPROACH, THE RIGHT ENGINE LOST POWER. SHORTLY THEREAFTER, THE LEFT ENGINE LOST POWER. THE PILOT WAS UNABLE TO RESTART EITHER ENGINE AND A FORCED LANDING WAS MADE IN AN OPEN FIELD. DURING THE LANDING ROLL, THE AIRPLANE COLLIDED WITH THE TERRAIN. INSPECTION OF THE ENGINE REVEALED THAT THE AUX TANKS WERE EMPTY. THE MAIN FUEL TANKS CONTAINED AN UNKNOWN QUANTITY AND WERE RUPTURED IN THE CRASH SEQUENCE. THE AIRPLANE HAD BEEN OPERATING OFF OF THE AUX TANKS PRIOR TO THE LOSS OF POWER. THERE WERE NO MECHANICAL FAILURES OR MALFUNCTIONS REPORTED WITH THE AIRPLANE OR ENGINES.
Probable cause
THE PILOTS INACCURATE FUEL CONSUMPTION CALCULATIONS AND IMPROPER FUEL TANK SELECTOR POSITION. THESE RESULTED IN FUEL STARVATION TO BOTH ENGINES WHEN THE AUX TANKS RAN DRY AND THE MAINS HAD FUEL REMAINING IN THEM. A FACTOR IN THIS ACCIDENT WAS THE ROUGH TERRAIN ENCOUNTERED WHEN THE PILOT WAS FORCED TO LAND SHORT OF THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA199
- Event ID
- 20001213X28355
- Case number
- LAX89LA199
- 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: 20df4b6ff099cebba95abfc9b119ad28a2dd6fc55674ed9f739681ed07f08e8e; retrieved 2026-09-23T07:36:13.939Z.