# Accident 20100507034039A: Cessna 305A, Fort Pierce, FL, May 7, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 7, 2010, 19:00 local time
- Place: Fort Pierce, FL
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 27.4256° N, 80.3404° W: Placed by OpenAirDocs: center of Fort Pierce, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=27.4256&lon=-80.3404&mi=10
- Aircraft: N5312G, a cancelled registration (https://openairdocs.org/deregistered/N5312G-2018-05-10) (OpenAirDocs)
- Registry model: Cessna 305A (registry code 2074002, https://openairdocs.org/model/cessna-305a) (OpenAirDocs)
- Registry engine: Continental O-470 series (registry code 17026, https://openairdocs.org/engine/continental-o-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 305A
- Reported engine: CONT MOTOR O-470 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,233 total, 55 in this make and model, 29 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100507034039A

## Narrative

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

ON MAY 07, 2010, AT 1900 EASTERN DAYLIGHT TIME, A CESSNA CE-305 AIRCRAFT, N5312G, EXPERIENCED THE LOSS OF DIRECTIONAL CONTROL, IMMEDIATELY AFTER LANDING, AT TREASURE COAST AIRPARK, IN FORT PIERCE, FLORIDA.  AS A RESULT OF THE LOSS OF DIRECTIONAL CONTROL, THE AIRCRAFT VEERED TO THE LEFT, OFF THE RUNWAY, AND IMPACTED A LARGE PINE TREE WITH THE LEFT WING ON THE OUTBOARD SECTION OF THE WING.  THE FLIGHT WAS CONDUCTED AS A PERSONAL FLIGHT UNDER THE PROVISIONS OF TITLE 14 OF THE CODE OF FEDERAL REGULATIONS (14 CFR) PART 91 WITH NO FLIGHT PLAN FILED.  VISUAL WEATHER CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT.  THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE.  THE PILOT DID NOT RECEIVE ANY INJURIES.  THE FLIGHT DEPARTED TREASURE COAST AIRPARK, IN FORT PIERCE, FLORIDA, ON MAY 7, 2010, AT 1845 EASTERN DAYLIGHT TIME.  THE PILOT REPORTED THAT IMMEDIATELY AFTER LANDING, HE LOST DIRECTIONAL CONTROL OF THE AIRCRAFT AS IT VEERED TO THE LEFT AND IMPACTED A PINE TREE.  THE ON-SCENE INVESTIGATION REVEALED THAT AS A RESULT OF THE IMPACT, THERE WAS SUBSTANSTIAL DAMAGE TO THE LEFT WING, INCLUDING THE SPAR.  THERE WAS ADDITIONAL STRUCTURAL DAMAGE, CAUSED BY THE FORCE OF THE TREE IMPACT, THAT EXTENDED THROUGHOUT THE FUSELAGE AS EVIDENCED BY SKIN WRINKLING THROUGH THE ENTIRE AIRCRAFT.  THE HEAVIEST CONCENTRATION OF SKIN DAMAGE (WRINKLING) APPEARED ON THE TOP OF THE WING ABOVE THE FUSELAGE.

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

## Other reports on N5312G (4)

Matched to the same aircraft by N-number and date.

- [Accident 20151124019539A](https://openairdocs.org/incident/20151124019539A), Nov 24, 2015: Cessna 305A (N5312G), Sulphur, LA, Destroyed. Aircraft doing touch & goes on runway 15. After low turn to upwind, about 100 feet AGL and still over airport property, engine quit. Pilot planned to land on…
- [Accident 19860703029839A](https://openairdocs.org/incident/19860703029839A), Jul 3, 1986: Cessna 305A (N5312G), Figure Eight La, AK, Substantial damage. Crash occurred after power failure when emergency landing was attempted on a lake.
- [Accident 19840927056869A](https://openairdocs.org/incident/19840927056869A), Sep 27, 1984: Cessna 305A (N5312G), Anchorage, AK, Substantial damage. Ground looped on rollout. 4th incident with control problem. Tailwheel spring leaf oversized, not firmly fastened.
- [Accident 19730123002839A](https://openairdocs.org/incident/19730123002839A), Jan 23, 1973: Cessna 305A (N5312G), Anchorage, AK, Substantial damage. Plt planned to lnd within the 700FT threshold extension. Lndd 4FT short. Gr collapsed.

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.
