MIA96IA114 · Mitsubishi MU-2G-30
Mitsubishi MU-2G-30 · Incident: airframe, component or system failure en route
From Hartsfield Jackson Atlanta International Airport (ATL) to Birmingham-Shuttlesworth International Airport (BHM)
Event
- NTSB case
- MIA96IA114
- 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
- Charter & commuter
- 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-2G-30
- 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
- N920S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Birmingham-Shuttlesworth International Airport (BHM), Birmingham, AL
- 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 135: Air Taxi & Commuter
- 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 · climb to cruise
- 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
- Minor
Cause areas
- Landing gear › Failure
- Manufacturer › Inadequate quality control
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated the nose gear did not retract during the initial climb after takeoff. Emergency procedures were completed (but the nose gear would not retract and the main gear would not extend). The airplane was landed with the nose gear extended and the main gear retracted. A check of the landing gear system after landing revealed a faulty (nose gear) bearing. Examination of the bearing revealed evidence that it had not been properly assembled and staked when it was manufactured.
Probable cause
failure of the nose landing gear bearing due to improper assembly and staking (inadequate quality control) by the manufacturer; which prevented the nose gear from retracting and the main gear from extending, and resulted in a subsequent landing on the nose gear and tail assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96IA114
- Event ID
- 20001208X05633
- Case number
- MIA96IA114
- 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: 0eadaa56aff4ab059d9ea4cda71115438b68467859f98a65c8696cf90ba9e49d; retrieved 2026-09-18T17:51:58.869Z.