FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX86LA147 · Mooney M20F

19 Mar 1986 · Burbank, CA, United States

Mooney M20F · Accident: loss of control in flight during initial climb

From Hollywood Burbank/Bob Hope Airport (BUR) to Tehachapi Municipal Airport (TSP)

Report a problem

Event

NTSB case
LAX86LA147
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

Mooney M20F

Aircraft type
Mooney M20
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
N9591M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CATo Tehachapi Municipal Airport (TSP), Tehachapi, 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
Loss of control in flight
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

  • Flight control, elevator › Binding(mechanical)
  • Flight control, elevator › Inoperative
  • Flight control, elevator › Movement restricted
  • Flt control syst, elevator control › Fatigue
  • Other maintenance personnel › Maintenance, annual inspection, inadequate
  • Other maintenance personnel › Maintenance, compliance with ad, not followed
  • Other maintenance personnel › Maintenance, lubrication, not performed
  • Pilot in command › Flare, not possible

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE ACFT WAS LANDED NOSE LOW AFTER FLYING THE PATTERN WITH A FLT CONTROL PROBLEM. THE PLT SAID HE NOTICED THE LACK OF ELEVATOR CONTROL DURING INITIAL CLIMB AND CAME BACK IN FOR A PRECAUTIONARY LANDING. THE ELEVATOR WAS FOUND TO BE INOPERATIVE DUE TO A BROKEN BEARING (PART #914012-015) THE SUBJECT OF AN AD 73-21-01 EFF 10/73, CONCERNING LUBRICATION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX86LA147
Event ID
20001213X33103
Case number
LAX86LA147
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: 50078973df6fb8993dba75dcc24b0cec33aaf68fc0e02c665b1dad9aabc76712; retrieved 2026-09-23T14:56:51.277Z.