FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90IA005 · Mooney M20F

6 Oct 1989 · Pensacola, FL, United States

Mooney M20F · Incident: complete gear collapsed during landing

From Venice Municipal Airport (VNC) to an unrecorded destination

Report a problem

Event

NTSB case
MIA90IA005
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
Incident
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
N52DB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Venice Municipal Airport (VNC), Venice, FLTo not recorded
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
Landing · landing roll
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
Complete gear collapsed
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Other maintenance personnel › Maintenance, installation, improper

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

NTSB narrative

TWO DAYS BEFORE THE INCIDENT, THE LANDING GEAR ACTUATOR & COMPONENTS OF THE LANDING GEAR WERE REPLACED & THE GEAR RIGGING WAS CHECKED. THE ACFT WAS FLOWN ON SEVERAL LEGS. AFTER GEAR EXTENSION, THE OWNER HEARD A POPPING NOISE, THOUGH THE GEAR EXTENDED NORMALLY. MAINT FACILITY PRESIDENT ADVISED IT WAS NORMAL. THE FLT DEPARTED & EN ROUTE WAS UNEVENTFUL, BUT AFTER EXTENDING THE LANDING GEAR, THE SAME NOISE WAS HEARD. AFTER TOUCHDOWN DURING THE LANDING ROLL, THE LANDING GEAR COLLAPSED. ACFT WAS FERRIED TO A FACILITY FOR REPAIRS. EXAM OF THE LANDING GEAR REVEALED THAT THE LANDING GEAR ACTUATOR SUPPORT BRACKET FAILED IN TENSION OVERLOAD.

Probable cause

IMPROPER RIGGING OF THE LANDING GEAR WHICH RESULTED IN AN OVERLOAD FAILURE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90IA005
Event ID
20001213X29647
Case number
MIA90IA005
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: 8e8474e7167700be7d7b22d88e066e0bf54456ae60b92e44f811445e939a0132; retrieved 2026-09-23T07:05:48.685Z.