# Accident 20200108010292A: Cessna 172S, Palm Coast, FL, January 8, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 8, 2020, 07:47 local time
- Place: Palm Coast, FL
- Airport: Flagler Executive
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Run-Up Area
- Operating rules: General operating rules (Part 91)
- Operator: IHMS
- Location: 29.4653° N, 81.2078° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=29.4653&lon=-81.2078&mi=10
- Aircraft: N536ND, registered now (https://openairdocs.org/aircraft/N536ND) (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: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 53 total, 53 in this make and model, 53 in the last 90 days
- NTSB investigation: [NTSB ERA20CA140](https://openairdocs.org/ntsb/ERA20CA140) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200108010292A

## Narrative

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

A STUDENT PILOT WAS TAXIING HIS AIRPLANE INTO THE RUNUP AREA AT WHAT HE THOUGHT WAS A SAFE DISTANCE FROM ANOTHER AIRPLANE THAT WAS PERFORMING A RUNUP. THE MOVING AIRPLANE'S LEFT WING CONTACTED THE STATIONARY AIRPLANE'S PROPELLER, RESULTING IN SUBSTANTIAL DAMAGE TO THE MOVING AIRPLANE'S LEFT WING. NEITHER PILOT REPORTED ANY PREACCIDENT MECHANICAL FAILURES OR MALFUNCTIONS WITH THEIR RESPECTIVE AIRPLANES THAT WOULD HAVE PRECLUDED NORMAL OPERATION.

## Other aircraft in the event

- N550ND, Cessna 172S: no report for this aircraft; [N550ND](https://openairdocs.org/aircraft/N550ND) is registered now

## 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 ERA20CA140](https://openairdocs.org/ntsb/ERA20CA140), Jan 8, 2020: Cessna 172 (N536ND), Palm Coast, FL, substantial damage. Probable cause: The student pilot's failure to allow adequate separation when passing the parked airplane, which resulted in a ground collision.

## Other reports on N536ND (1)

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

- [Incident 20100509005049I](https://openairdocs.org/incident/20100509005049I), May 9, 2010: Cessna 172S (N536ND), Mayville, ND, Minor damage. While conducting a dual flight lesson the aircraft sustained minor damage due to a tail strike. The CFI failed to initiate coorective action of excessive sink…

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.