FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02IA072 · Piper PA-31-325

23 Mar 2002 · Fort Laudedale, FL, United States

Twin Air Piper PA-31-325 · Incident: wheels up landing

From Leonard M. Thompson International Airport (MYAM) to Fort Lauderdale Hollywood International Airport (KFLL)

Report a problem

Event

NTSB case
MIA02IA072
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
Unknown
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-31-325

Aircraft type
Piper PA-31
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
N49RB
Operator
Twin Air
Onboard fatalities
Unknown
Route
From Leonard M. Thompson International Airport (MYAM), Marsh Harbor, CBTo Fort Lauderdale Hollywood International Airport (KFLL), Ft. Lauderdale, 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
Landing · flare/touchdown
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
Wheels up landing
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

  • Pilot in command › Checklist, not complied with

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, due to radio traffic congestion at his landing airport, he missed the tower's call for his landing clearance, and his attempts to confirm his clearance were continually blocked. He completed all items on his before landing checklist except the landing gear, and by the time he got confirmation to land, he was on short final approach, and he forgot to lower the landing gear. Postcrash examination of the wheels up warning circuit revealed an operable warning horn.

Probable cause

The failure of the pilot to assure all items of the before landing checklist were complied with before landing, resulting in the wheels up landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02IA072
Event ID
20020327X00408
Case number
MIA02IA072
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, coordinates. 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: 5d5b4c67df02f65ed248326f81bc27028880f3df9bbfb765baef2ad573e80a9b; retrieved 2026-09-22T11:03:55.398Z.