MIA92LA063 · Beech 58
Beco Aviation Beech 58 · Accident: airframe, component or system failure on approach
From Leonard M. Thompson International Airport (MYAM) to Treasure Coast International Airport (FPR)
Event
- NTSB case
- MIA92LA063
- 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
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N4188S
- Operator
- Beco Aviation
- Onboard fatalities
- Unknown
- Route
- From Leonard M. Thompson International Airport (MYAM), Marsh HarbourTo Treasure Coast International Airport (FPR), Fort Pierce, FL
- 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
- Approach
- 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
- Substantial
Cause areas
- Landing gear, normal retraction/extension assembly › Failure, partial
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER ARRIVING IN THE TRAFFIC PATTERN OF THE DESTINATION ARPT, THE PLT LOWERED THE LANDING GEAR SELECTOR HANDLE BUT THE GEAR DID NOT EXTEND. THE FLT DEPARTED THE PATTERN & ATTEMPTS TO LOWER THE GEAR VIA THE EMERGENCY METHOD WERE UNSUCCESSFUL. THE FLT DIVERTED TO A LARGER ARPT WHERE A GEAR UP LANDING OCCURRED. THE LANDING GEAR RETRACT MOTOR & GEARBOX ASSY WAS REMOVED FROM THE ACFT & DISASSEMBLY REVEALED THAT THE WORM SECTOR GEAR REPEATEDLY CONTACTED THE SECTOR GEAR STOP. ALSO, TWO HALF RINGS WHICH SECURE THE BEARING TO THE WORM ACTUATING SHAFT SHEARED. THIS ALLOWED THE WORM GEAR ACTUATOR TO TRAVEL TOWARD THE MOTOR. AS A RESULT, THE HAND CRANK ENGAGING SHAFT WOULD NOT CONTACT THE WORM GEAR ACTUATOR. ACCORDING TO A MECHANIC, THIS WAS DUE TO A WORN LANDING GEAR MOTOR WHICH WOULD DRIVE THE GEAR BUT WOULD RENDER THE DYNAMIC BRAKING ACTION INOPERATIVE. THE UP-LIMIT SWITCH WAS TESTED & FOUND TO OPERATE NORMALLY.
Probable cause
PARTIAL FAILURE OF THE LANDING GEAR MOTOR WHICH CAUSED INTERNAL DAMAGE TO THE LANDING GEAR RETRACT MOTOR AND GEARBOX ASSY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA92LA063
- Event ID
- 20001211X14035
- Case number
- MIA92LA063
- 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: 4ec2da73966d036f644a8bd07e9bdb63f1d32b7430c7ddeb0be0b5bd09e31996; retrieved 2026-09-23T03:26:10.619Z.