# Accident 20161017018169A: Cessna 152, Miami, FL, October 17, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 17, 2016, 08:09 local time
- Place: Miami, FL
- Airport: Miami Executive Airport
- Damage: Substantial damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Operator: D4RS
- Location: 25.6539° N, 80.4328° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=25.6539&lon=-80.4328&mi=10
- Aircraft: N46953, registered now (https://openairdocs.org/aircraft/N46953) (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: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 54 total, 54 in this make and model, 54 in the last 90 days
- NTSB investigation: [NTSB GAA17CA042](https://openairdocs.org/ntsb/GAA17CA042) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20161017018169A

## Narrative

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

PILOT STATED THAT HE WAS ON TAKEOFF ROLL AND HE REACHED 50 KNOTS ON HIS AIRSPEED INDICATOR AND HE PULLED ON THE YOKE TO LIFT THE NOSE OF THE AIRCRAFT AND HE NOTICED NO RESPONSE TO THE YOKE INPUT, THEN HE REACHED 65 KNOTS AIRSPEED AND ONCE AGAIN HE WASN'T GETTING RESPONSE FROM THE YOKE. AT THAT POINT HE DECIDED TO ABORT THE TAKEOFF AND REDUCED POWER AND STARTED APPLYING BRAKING POWER TO CONTROL THE AIRCRAFT, SUBSEQUENTLY THE AIRCRAFT WENT LEFT OFF THE RUNWAY CAUSING THE AIRCRAFT TO JUMP OVER A SMALL DIRT MOUND AND MAKING THE AIRCRAFT TO JUMP UP IN THE AIR AND LAND ON THE ENTRANCE OF A WATER CANAL NEAR THE RUNWAY ON THE LEFT HAND SIDE.

## 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 GAA17CA042](https://openairdocs.org/ntsb/GAA17CA042), Oct 17, 2016: Cessna 152 (N46953), Miami, FL, substantial damage. Probable cause: The student pilot's failure to maintain directional control during the aborted takeoff, which resulted in a runway excursion.

## Other reports on N46953 (5)

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

- [Incident 20160911016369I](https://openairdocs.org/incident/20160911016369I), Sep 11, 2016: Cessna 152 (N46953), Homestead, FL, Minor damage. On 11 September 2016 at 1540, Cessna 152 N46953, operated under 14 CFR 141 conducting a first solo cross country flight made a hard landing at Homestead…
- [Incident 20160831009709I](https://openairdocs.org/incident/20160831009709I), Aug 31, 2016: Cessna 152 (N46953), Miami, FL, No damage. N46953 landed on runway 13 at tmb and exited on taxiway D1 where the airplane ground looped in the intersection causing the right main gear to enter the grass…
- [Incident 20160216020349I](https://openairdocs.org/incident/20160216020349I), Feb 16, 2016: Cessna 152 (N46953), Pembroke Pines, FL, No damage. Depart tamiami airport (ktmb) to palm beach Florida (kpbi) on a night dual cross country flight and after level of at 2500 ft. engine lost power and start…
- [Incident 20120719013539I](https://openairdocs.org/incident/20120719013539I), Jul 19, 2012: Cessna 152 (N46953), Lebelle, FL, Minor damage. The pilot stated while on a cross country flight the engine started to run rough. The pilot contacted miami center and advised that they were going to make a…
- [Incident 19810704045079I](https://openairdocs.org/incident/19810704045079I), Jul 4, 1981: Cessna 152 (N46953), Hamilton Afb, CA. Zg engine rough. Emergency landing. Found spark plugs fouled.

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.