FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90LA011 · Beech 58P

12 Oct 1989 · Jackson, MS, United States

Beech 58P · Accident: airframe, component or system failure on approach

From an unrecorded airport to Lakeland Linder International Airport (LAL)

Report a problem

Event

NTSB case
MIA90LA011
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 58P

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
N94JP
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Lakeland Linder International Airport (LAL), Lakeland, 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

  • Pilot in command › Emergency procedure, not understood
  • Pilot in command › Gear down and locked, not maintained
  • Pilot in command › Gear retraction, inadvertent

Approximate · Estimated position: the centre of Jackson, MS, the place the record names. Not the accident site.

NTSB narrative

AFTER BECOMING AIRBORNE, THE PLT REALIZED HE HAD FORGOTTEN A BRIEF CASE & ELECTED TO RTRN TO THE ARPT. HE EXTENDED THE GEAR TO LAND & NOTICED THERE WERE 3 SAFE INDCNS. HOWEVER, AS HE EXTENDED THE FLAPS, THERE WAS A TOTAL LOSS OF ELECTRICALPOWER. HE MADE A GO-AROUND & TURNED THE MANUAL LANDING GEAR EXTENSION HANDLE TO VERIFY THAT THE GEAR WAS EXTENDED. HOW- EVER, HE TURNED THE EXTENSION HANDLE TO THE RIGHT, INSTEAD OF COUNTERCLOCKWISE, AS WAS STATED IN THE OPERATOR'S MANUAL. CLOCKWISE MOVEMENT OF THE EXTENSION HANDLE WOULD HAVE STARTED RETRACTION OF THE GEAR. WITNESSES NOTED THE GEAR WAS ONLY PARTLY EXTENDED BEFORE THE FINAL APCH TO LAND. DURING THE LANDING, THE GEAR COLLAPSED & THE ACFT WAS DAMAGED. NO REASON WAS FOUND FOR THE LOSS OF ELECTRICAL POWER.

Probable cause

THE PILOT'S MISUNDERSTANDING OF THE LANDING GEAR EMERGENCY EXTENSION PROCEDURE, WHICH RESULTED IN HIS INADVERTENT PARTIAL RETRACTION OF THE GEAR AND FAILURE TO LAND WITH THE GEAR IN THE DOWN AND LOCKED POSITION. LOSS OF ELECTRICAL POWER WAS A FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90LA011
Event ID
20001213X29656
Case number
MIA90LA011
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: b8e0bddee7b15e20f515bfed263cb10605a01b9c821cf9245f9900b7584e9a1c; retrieved 2026-09-23T07:04:46.909Z.