FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX98FA154 · Mooney M20K

5 May 1998 · Bakersfield, CA, United States

Mooney M20K · Accident: airframe, component or system failure en route

From Sacramento Executive Airport (SAC) to Bakersfield International Airport (L45)

Report a problem

Event

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

Mooney M20K

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
N231BY
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sacramento Executive Airport (SAC), Sacramento, CATo Bakersfield International Airport (L45), 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 · descent
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
Airframe, component or system 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

  • Flight control, elevator › Flutter
  • Flight control, elevator › Separation
  • Pilot in command › Airspeed(vne), exceeded

Approximate · Estimated position: the centre of Bakersfield, CA, the place the record names. Not the accident site.

NTSB narrative

While descending for an instrument approach in instrument meteorological conditions, the airplane's airspeed exceeded its never exceed velocity (Vne) of 196 knots. The elevators fluttered and separated from the airplane. Thereafter, the stabilizers departed, the nose pitched downward, and both wings failed in a negative direction. A ground witness heard a 'pop' sound, and observed airplane parts falling from the low clouds; the surface winds were reported by the witness as gusty. Earlier during the flight, the pilot had been cruising about 19,000 feet, and tracking in a southerly direction at 191 knots (ground speed). The winds aloft were westerly. While communicating with flight watch and radar controllers, he indicated that his airplane was not equipped with deicing equipment. The pilot was advised that icing conditions existed between 13,000 and 15,000 feet, and the freezing level was 7,000 feet. Due to traffic, at 0923 the controller cleared the pilot to descend to 15,000 feet. The pilot accepted the clearance, and requested a clearance to divert to a nearby airport. The controller approved the request. During the last 24 seconds of radar-recorded flight, the airplane's rate of descent increased to 3,500 feet per minute, and over its southerly course its ground speed increased to 240 knots. Shortly after this at 0930:21, the sound of an emergency locator beacon was recorded in the radar control facility. Pilot reports covering the area of the accident around the time of the event reported light to moderate turbulence and light to moderate rime/clear icing conditions. Engineering analysis and testing by the airframe manufacturer predicted the onset of flutter to occur at 241 knots. The airplane was modified by the installation of a larger engine with 95 additional horsepower available.

Probable cause

The pilot's operation of the airplane at a speed well in excess of it's designed never exceed speed that resulted in elevator flutter and in-flight failure of the airplane. Turbulence and icing conditions were factors in the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX98FA154
Event ID
20001211X10119
Case number
LAX98FA154
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: 30ffcb727098c12c01c370c0ee7cc07bf79cf65d596ecba7962310c3c1c5815a; retrieved 2026-09-20T22:36:16.913Z.