# Accident 20031108029299A: Cessna 172K, Sunbury, OH, November 8, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 8, 2003, 15:45 local time
- Place: Sunbury, OH
- Airport: Private
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 40.3294° N, 82.9591° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.3294&lon=-82.9591&mi=10
- Aircraft: N78203, a cancelled registration (https://openairdocs.org/deregistered/N78203-2013-08-20) (OpenAirDocs)
- Registry model: Cessna 172K (registry code 2072430, https://openairdocs.org/model/cessna-172k) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172K
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 315 total, 190 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB NYC04CA028](https://openairdocs.org/ntsb/NYC04CA028) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031108029299A

## Narrative

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

(-23) PILOT WAS LANDING TO THE SOUTHWEST ON A 2700' PRIVATE RUNWAY. AIRCRAFT TOUCHED DOWN APPROXIMATELY HALFWAY DOWN THE RUNWAY AND COULD NOT STOP BEFORE OVER RUNNING RUNWAY. AIRCRAFT ENTERED PLOWED FIELD AND OVERTURNED.

## 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 NYC04CA028](https://openairdocs.org/ntsb/NYC04CA028), Nov 8, 2003: Cessna 172K (N78203), Kilbourne, OH, substantial damage. Probable cause: The pilot's failure to obtain the proper touchdown point which resulted in an overrun and subsequent nose over.

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.