# Accident 20161113018619A: Cessna 152, Ft. Lauderdale, FL, November 13, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 13, 2016, 14:32 local time
- Place: Ft. Lauderdale, FL
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 26.3369° N, 80.6253° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=26.3369&lon=-80.6253&mi=10
- Aircraft: N94292, registered now (https://openairdocs.org/aircraft/N94292) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYCOMING 0-235 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 212 total, 212 in this make and model, 122 in the last 90 days
- NTSB investigation: [NTSB ERA17LA044](https://openairdocs.org/ntsb/ERA17LA044) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20161113018619A

## Narrative

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

ON 11/13/2016 AT APPROXIMATELY 19:33Z A CESSNA 152, N94292, ENROUTE FROM KLAL TO KTMB CRASHED INTO THE EVERGLADES 30 MILES WNW OF KFLL. TWO SOULS ONBOARD ESCAPED WITHOUT INJURY.

## 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 ERA17LA044](https://openairdocs.org/ntsb/ERA17LA044), Nov 13, 2016: Cessna 152 (N94292), Miami, FL, substantial damage. Probable cause: The loss of torque on the No. 3 connecting rod’s nuts, which resulted in the failure of the No. 3 connecting rod’s bolts and a subsequent total loss of engine power due to the operator's maintenance…

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.