# Accident 20120803016809A: Cessna 172R, Leesville, LA, August 3, 2012

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 3, 2012, 16:52 local time
- Place: Leesville, LA
- Airport: Leesville
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 31.1683° N, 93.3425° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=31.1683&lon=-93.3425&mi=10
- Aircraft: N989BT, a cancelled registration (https://openairdocs.org/deregistered/N989BT-2012-11-13) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- Reported engine: LYCOMING I0360 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 63 total, 63 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB CEN12CA526](https://openairdocs.org/ntsb/CEN12CA526) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120803016809A

## Narrative

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

PILOT WAS IN LANDING PHASE FOR RUNWAY 36, HE NOTICED THE AIRCRAFT WASN'T DESCENDING AS QUICKLY AS HE WOULD HAVE LIKED AND RECOGNIZED HE WAS GOING TO LAND LONG. PILOT INITIATED A GO AROUND, WITH FULL FLAPS.  HE STATED AIRCRAFT DIDN'T RESPOND AS HE THOUGHT IT SHOULD HAVE AND QUESTIONED HIMSELF IF HE WOULD HAVE ENOUGH ALTITUDE IN TIME TO CLEAR THE TREES OFF THE END OF THE RUNWAY. HE THEN DECIDED TO FORCE THE LANDING, LANDED LONG AND WENT OFF THE END OF THE RUNWAY INTO A DITCH AND THE AIRCRAFT FLIPPED OVER. INVESTIGATION SHOWED HOT DAY INCREASING DENSITY ALTITUDE AND TAILWIND FOR RWY 36.

## 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 CEN12CA526](https://openairdocs.org/ntsb/CEN12CA526), Aug 3, 2012: Cessna 172R (N989BT), Leesville, LA, substantial damage. Probable cause: The student pilot's failure to properly re-configure the airplane for a go-around, which resulted in a runway excursion when he decided to land on the remaining runway.

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.