LAX82FA255 · Mitsubishi MU-2B
Mitsubishi MU-2B · Accident: partial loss of engine power (mechanical failure) during takeoff
From Sonoma Valley Airport (0Q3) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX82FA255
- 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
Mitsubishi MU-2B
- Aircraft type
- Mitsubishi MU-2
- 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
- N27GP
- Operator
- Robert Marshall JR
- Onboard fatalities
- Unknown
- Route
- From Sonoma Valley Airport (0Q3), SCHELLVILLE, CATo Oakland San Francisco Bay Airport (OAK), Oakland, 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
- Takeoff · roll/run
- 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)
- 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
- Fuel system, fuel control › Failure, partial
- Fuel system, fuel control › Leak
- Pilot in command › Performance data, not identified
- Pilot in command › Propeller, improper use of
- Propeller system/accessories › Engaged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT APPROXIMATELY 800 FT DOWN THE LEFT SIDE OF THE RWY THE LEFT ENG EXPERIENCED A POWER LOSS. THE ACFT SWERVED OFF THE LEFT SIDE OF THE RWY COLLIDING WITH A DRAINAGE DITCH & COMING TO REST INVERTED. EXAMINATION OF THE FUEL CONTROL UNIT REVEALED THAT THE BELLOWS WITHIN THE ASSEMBLY WERE FOUND IN AN EXTENDED POSITION, INDICATING A LEAK INTO THE EVACUATED AREA. A FAILURE WAS NOTED AT THE SEAM IN THE BELLOWS. IN ADDITION, EXAMINATION OF THE PROPELLER REVEALED THAT THE START LOCKS WERE ENGAGED & THE BLADES WERE AT THE START LOCK POSITION AT IMPACT. IN ORDER TO ENGAGE THE START LOCKS, THE POWERLEVER HAS TO BE MOVED TO REVERSE DURING SHUTDOWN WITH THE ENG RPM BELOW 50%. AFTER ENG START THE PLT MUST AGAIN RETARD THE POWER LEVERS TO REVERSE TO DISENGAGE THE START LOCKS. THE LOCKS WILL NOT DISENGAGE AFTER THE POWER LEVER IS SET TO THE FLIGHT RANGE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FA255
- Event ID
- 20020917X03675
- Case number
- LAX82FA255
- 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 1982-07-14.
- API snapshot SHA-256: a1d579f7759c6bd37e54b74ae1c7828337a72ff3bf051be38e3ae8b4f61ca233; retrieved 2026-09-22T02:59:13.229Z.