FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA06LA105 · Cessna 421B

8 May 2006 · Marathon, FL, United States

Cessna 421B · Accident: wheels up landing

From Pompano Beach Airpark (KPMP) to Florida Keys Marathon International Airport (KMTH)

Report a problem

Event

NTSB case
MIA06LA105
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
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

Cessna 421B

Aircraft type
Cessna 421
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
N988GM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pompano Beach Airpark (KPMP), Pompano Beach, FLTo Florida Keys Marathon International Airport (KMTH), Marathon, 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
Substantial

Cause areas

  • Pilot in command › Wheels up landing, inadvertent

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

NTSB narrative

The commercial certificated pilot was positioning the multi-engine, retractable landing gear airplane for a corporate passenger flight under Title 14, CFR Part 91, when the accident occurred. Upon landing at the destination, the pilot aborted the landing, and after climbing to about 100 feet agl descended, impacting in a canal. A witness who was not looking towards the runway, reported hearing the sound of a twin engine airplane approaching with the engines at reduced power, and then heard a scraping noise similar to the recent gear-up landing he had witnessed. Looking toward the runway, he said the airplane was midfield, left of the runway centerline, about 20 feet in the air with the landing gear retracted, and that he saw a cloud of dust, and heard what he thought was full engine power being applied. He said the airplane climbed to about 100 feet agl, and disappeared from view. Another witness with a portable VHF radio tuned to the unicom frequency, reported hearing the pilot say he was "doing an emergency go-around." The airplane descended striking utility poles, and impacted in a saltwater canal. An examination of the airport runway revealed a set of parallel propeller strike marks. The left and right sets of marks were 109 and 113 feet long, and the mark's center-to-center measurement is consistent with the engine centerline-to-centerline measurement for the accident airplane. No landing gear marks were observed. The airplane's six propeller blades had extensive torsional twisting and bending, as-well-as extensive chord wise scratching and abrasion. Several of the blades had fractured or missing tips. An examination of the cockpit showed the landing gear retraction/extension handle was in the up/retracted position, and the landing gear extension warning horn circuit breaker was in the pulled/tripped position. The landing gear emergency extension handle was in the stowed position. The nose landing gear was damaged during final impact, and was not functional. During the postimpact examination, both the left and right main landing gear were stowed in the up-and-locked/retracted position. The landing gear were released/unlocked and operated appropriately using the emergency extension handle. An examination of the left and right main landing gear showed no damage to the wheel doors, leg doors, wheels, or tires. All linkages and locking devices were undamaged, and appeared to function normally.

Probable cause

The pilot's failure to extend the landing gear prior to landing, which resulted in the propellers striking the runway, an aborted landing, and an in-flight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA06LA105
Event ID
20060511X00547
Case number
MIA06LA105
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: 68b227ded6646424af0dd8dadab6fdcdbe3bff2eda346b2e5817eb4a93d141ff; retrieved 2026-09-21T08:58:22.623Z.