# Accident 20060819018429A: Cessna 172P, Chester, SC, August 19, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 19, 2006, 18:30 local time
- Place: Chester, SC
- Airport: Chester Municipal Airport
- Damage: Substantial damage
- Phase of flight: Sfl Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 34.7869° N, 81.1906° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.7869&lon=-81.1906&mi=10
- Aircraft: N51887, a cancelled registration (https://openairdocs.org/deregistered/N51887-2014-08-22) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 500 total, 400 in this make and model, 300 in the last 90 days
- NTSB investigation: [NTSB ATL06CA123](https://openairdocs.org/ntsb/ATL06CA123) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060819018429A

## Narrative

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

(-23) WHILE GIVING FLIGHT INSTRUCTION THE PILOT LANDED LONG. AIRCRAFT RAN OFF END OF RUNWAY AND HIT TREES. AIRCRAFT RECEIVED SUBSTANTIAL DAMAGE WITH NO INJURIES TO PILOT OR STUDENT.

## 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 ATL06CA123](https://openairdocs.org/ntsb/ATL06CA123), Aug 19, 2006: Cessna 172P (N51887), Chester, SC, substantial damage. Probable cause: The CFI's failure to initiate a go-around when he noticed the flight was high and fast during the approach resulting in the flight landing long, overrunning the runway, and colliding with trees.…

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.