# Accident 20060508006809A: Cessna 421B, Marathon, FL, May 8, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 8, 2006, 08:00 local time
- Place: Marathon, FL
- Airport: Marathon Airport
- Damage: Destroyed
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 24.7322° N, 81.0364° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=24.7322&lon=-81.0364&mi=10
- Aircraft: N988GM, a cancelled registration (https://openairdocs.org/deregistered/N988GM-2009-11-16) (OpenAirDocs)
- Registry model: Cessna 421B (registry code 2076014, https://openairdocs.org/model/cessna-421b) (OpenAirDocs)
- Registry engine: Continental GTSIO-520-C (registry code 17035, https://openairdocs.org/engine/continental-gtsio-520-c) (OpenAirDocs)
- Reported make and model: CESSNA 421B
- Reported engine: CONT GTSIO520C
- Fatal injuries: 0
- Pilot flight hours: 1,500 total, 200 in this make and model
- NTSB investigation: [NTSB MIA06LA105](https://openairdocs.org/ntsb/MIA06LA105) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060508006809A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) GEAR WAS NOT EXTENDED. AIRCRAFT PROPELLERS CAME INTO CONTACT WITH THE RUNWAY AND PILOT INITIATED A GO-AROUND, BECAME AIRBORNE BUT WAS UNABLE TO GAIN SUFFICIENT ALTITUDE TO AVOID COLLIDING WITH TELEPHONE POLES AND TREE AND SUBSEQUENTLY CRASHED INTO CANAL IN RESIDENTIAL AREA.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB MIA06LA105](https://openairdocs.org/ntsb/MIA06LA105), May 8, 2006: Cessna 421B (N988GM), Marathon, FL, substantial damage. 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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.