MIA88LA113 · Piper PA-30
Piper PA-30 · Accident: airframe, component or system failure on approach
From Orlando International Airport (MCO) to Tailwinds Airport (FD15)
Event
- NTSB case
- MIA88LA113
- 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
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N7377Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando International Airport (MCO), Orlando, FLTo Tailwinds Airport (FD15), Jupiter, 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 · VFR pattern downwind
- 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
- Pilot in command › Emergency procedure, not performed
- Pilot in command › Gear down and locked, not obtained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT STATED THAT HE HAD COMPLETED A LDG AWAY FROM HIS HOME BASE WITHOUT THE GEAR DOWN & LOCKED LIGHTS BEING ILLUMINATED. HE STATED THAT HE HAD ASSUMED THE LIGHTS WERE 'BURNED OUT'. UPON DEPARTURE, HE RETRACTED THE GEAR & FLEW TO HIS HOME AIRPORT. UPON ARRIVAL, HE AGAIN FAILED TO GET ANY GEAR DOWN & LOCKED LIGHT BUT CONTINUED HIS LDG APRCH. THE GEAR COLLAPSED ON TOUCH DOWN & THE ACFT SLID TO A STOP ON ITS BELLY. THE PLT STATED THAT THE LDG GEAR DRIVE MOTOR HAD BEEN BLOWING FUSES WHEN HE ATTEMPTED TO LOWER THE GEAR, BUT IT NEVER OCCURRED TO HIM TO EXTEND THE GEAR BY THE EMERG SYSTEM. THE ACFT WAS LATER RAISED FROM THE RWY & THE GEAR WAS EXTENDED BY THE EMERGENCY SYSTEM. AN EXAM OF THE GEAR MOTOR REVEALED THAT IT HAD BURNED OUT. THE ACFT WAS MANUFG IN 1964 & HAD FLOWN 2376 HRS SINCE THAT TIME. THE LDG MOTOR WAS AN ORIGINAL COMPONENT & HAD NEVER BEEN OVERHAULED. THE PLT STATED THAT IT WAS DUE TO HIS OVERSIGHT THAT HE FAILED TO EXTEND THE GEAR BY THE EMERGENCY SYSTEM.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88LA113
- Event ID
- 20001213X25122
- Case number
- MIA88LA113
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-02-25.
- API snapshot SHA-256: 6985b81b6182d2204146dc6040810fc81baa420da0f819d760593f04d5ad2794; retrieved 2026-09-23T10:57:27.310Z.