# Incident 20180812010999I: Cessna 172S, Sanford, FL, August 12, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 12, 2018, 08:46 local time
- Place: Sanford, FL
- Damage: No damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: Pilot school (Part 141)
- Operator: CE8S
- Location: 28.7845° N, 81.2761° W: Placed by OpenAirDocs: center of Sanford, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=28.7845&lon=-81.2761&mi=10
- Aircraft: N563ND, registered now (https://openairdocs.org/aircraft/N563ND) (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: Commercial pilot, flight instructor
- Pilot flight hours: 750 total, 520 in this make and model, 159 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180812010999I

## Narrative

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

ON 8/12/18 CONN335 (N563ND), C172, ABORTED TAKEOFF RUNWAY 27L DUE TO A BIRD STRIKE. AIRCRAFT TAXIED TO THE RAMP. DAMAGE: NONE. VERIFIED WITH MAINTENANCE DEPARTMENT THERE WAS NO DAMAGE TO AIRCRAFT AS A RESULT OF THE BIRD STRIKE. CLOSED

## Other reports on N563ND (1)

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

- [Incident 20181217022179I](https://openairdocs.org/incident/20181217022179I), Dec 17, 2018: Cessna 172S (N563ND), Sanford, FL, Minor damage. A Cessna 172S, operated by L3 commercial training solutions in Sanford reported a bird strike on final to runway 27R. During approach, the crew noticed birds…

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.