# Accident 20171130022239A: Cessna 172R, Miami, FL, November 30, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 30, 2017, 23:00 local time
- Place: Miami, FL
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 25.6514° N, 80.4394° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=25.6514&lon=-80.4394&mi=10
- Aircraft: N537HF, registered now (https://openairdocs.org/aircraft/N537HF) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING I0360 SER A&C
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 193 total, 120 in this make and model, 8 in the last 90 days
- NTSB investigation: [NTSB ANC18LA014](https://openairdocs.org/ntsb/ANC18LA014) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20171130022239A

## Narrative

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

ON NOVEMBER 30, 2017 AROUND 2215 LOCAL TIME PILOT AND A PASSENGER DEPART TAMIAMI AIRPORT(KTMB) ON A LOCAL FLIGHT FOR ABOUT 35 MINUTES.

ON HIS RETURNED BACK TO TAMIAMI AIRPORT HE REPORT AT 2250 LOCAL 10 MILES EAST INBOUND FOR LANDING TO THE CONTROL TOWER. TOWER ADVISED HIM TO ENTER LEFT DOWNWIND FOR RUNWAY 9L AND ALSO CLEAR TO LAND. PILOT ON HIS STATEMENT REPORT HE LOST SITE OF RUNWAY 9L BUT CONTINUE THE APPROACH TOWARD THE RUNWAY BUT INSTEAD LANDED OF THE RUNWAY IN THE GRASS AREA BETWEEN RUNWAY AND TAXIWAY ALPHA. THE PILOT LANDED PARALLEL TOTHE RUNWAY AND CAME ACROSS TAXIWAY ALPHA ONE AND OVER THE AIRPORT SIGN CAUSING DAMAGE TO THE PROPELLER AND LEFT-SIDE WIND BEFORE CAME TO A COMPLETE STOP.

## 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 ANC18LA014](https://openairdocs.org/ntsb/ANC18LA014), Dec 1, 2017: Cessna 172 (N537HF), Miami, FL, substantial damage. Probable cause: The pilot's decision to continue the landing after a loss of visual cues during a night landing.

## Other reports on N537HF (2)

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

- [Incident 20240507019739I](https://openairdocs.org/incident/20240507019739I), May 7, 2024: Cessna 172R (N537HF), Van Nuys, CA, Minor damage. PIC maneuvered aircraft into a congested run-up area misjudged the space between another aircraft and the blast fence area resulting in a "left-wing" collision…
- [Incident 20221022016402I](https://openairdocs.org/incident/20221022016402I), Oct 22, 2022: Cessna 172R (N537HF), Van Nuys, CA, Minor damage. Returning from an instruction flight, the student pilot of [privacy data omitted], was manuevering the aircraft to parking spot. In doing so, the left-hand…

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.