Executive Airline & Charter Mitsubishi MU-2K incident
Mitsubishi MU-2K · Incident: airframe, component or system failure en route
From Cyril E. King Airport (STT) to an unrecorded destination
Event
- NTSB case
- MIA85IA203
- 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-2K
- 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
- N7DD
- Operator
- Executive Airline & Charter
- Onboard fatalities
- Unknown
- Route
- From Cyril E. King Airport (STT), ST.THOMASTo 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 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
- Door, landing gear › Movement restricted
- Landing gear, normal retraction/extension assembly › Overload
- Landing gear, nose gear › Binding(mechanical)
- Landing gear, nose gear › Disconnected
- Landing gear, nose gear › Movement restricted
Approximate · Estimated position: the centre of San Juan, the place the record names. Not the accident site.
NTSB narrative
AFTER DEPARTURE THE NOSE GEAR UNSAFE LIGHT REMAINED ILLUMINATED PETER GEAR RETRACTION. ATTEMPTS TO GET A SAFE LIGHT ON THE NOSE GEAR IN THE EXTENDED POSITION WAS UNSUCCESSFUL AND WHEN THE AIRCRAFT LANDED IT SETTLED ONTO A PARTIALLY RETRACTED NOSE GEAR. INSPECTION OF THE AIRCRAFT REVEALED THAT THE NOSE GEAR STRUT HAD NOT FULLY EXTENDED AND THAT WHEN THE GEAR WAS RETRACTED THE NOSE GEAR TIRES CAUGHT THE NOSE GEAR DOORS PREVENTING THEM FROM OPENING. THE GEAR RETRACTED AGAINST THE GEAR DOORS CAUSING FAILURE OFTHE RETRACT JACKSCREW. A MICROSWITCH WHICH CUTS THE GEAR MOTOR OFF WHEN THIS CONDITION OCCURRS WAS FOUND OUT OF ADJUSTMENT AND DID NOT OPERATE. ADDITIONALLY IT WAS FOUND THAT THE MECHANICS WHO DID THE LAST GEAR RETRACT TEST ON THE AIRCRAFT USED A MAINTENANCE MANUAL FOR AN EARLIER MODEL AIRCRAFT WHICH DID NOT HAVE THIS SAFETY SWITCH THUS FAILING TO CHECK IT FOR ADJUSTMENT. NO REASON AS TO WHY THE NOSE GEAR STRUT DID NOT FULLY EXTEND WAS FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA85IA203
- Event ID
- 20001214X36843
- Case number
- MIA85IA203
- 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: 286c66ff354e09f8f529a5627f5e7ddf1b0969b76bbe3305f90ed55ec849b39c; retrieved 2026-09-18T20:20:24.549Z.