# Accident 20130829018649A: Cessna 172S, Fort Lauderdale, FL, August 29, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 29, 2013, 19:08 local time
- Place: Fort Lauderdale, FL
- Airport: Fort Lauderdale Executive
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: Pilot school (Part 141)
- Location: 26.1972° N, 80.1717° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=26.1972&lon=-80.1717&mi=10
- Aircraft: N6065P, registered now (https://openairdocs.org/aircraft/N6065P) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 74 total, 74 in this make and model, 74 in the last 90 days
- NTSB investigation: [NTSB ERA13CA395](https://openairdocs.org/ntsb/ERA13CA395) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130829018649A

## Narrative

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

AIRCRAFT DID BOUNCE ON THE RUNWAY DURING LANDING, AFTER THE 3RD BOUNCE THE NOSE WAS FIRST TO TOUCH AND DID COLAPSE.

## 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 ERA13CA395](https://openairdocs.org/ntsb/ERA13CA395), Aug 29, 2013: Cessna 172S (N6065P), Fort Lauderdale, FL, substantial damage. Probable cause: The student pilot’s failure to apply power to go-around following a bounced landing resulting in abnormal runway contact and collapse of the nose landing gear.

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.