# Accident 20170915019399A: Cessna 172N, Lynchburg, VA, September 15, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 15, 2017, 20:00 local time
- Place: Lynchburg, VA
- Airport: Falwell Airport
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.3781° N, 79.1222° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3781&lon=-79.1222&mi=10
- Aircraft: N5396D, a cancelled registration (https://openairdocs.org/deregistered/N5396D-2018-12-27) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 350 total, 7 in this make and model, 88 in the last 90 days
- NTSB investigation: [NTSB GAA17CA540](https://openairdocs.org/ntsb/GAA17CA540) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170915019399A

## Narrative

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

ACCORDING TO THE STATEMENT FROM THE PILOT: PILOT MADE A NORMAL APPROACH INTO FALWELL AIRPORT WITH EXTRA SPEED.  PILOT BALLOONED THE AIRCRAFT DURING TOUCHDOWN.  PILOT THEN EXECUTED A GO-AROUND BY ADDING FULL POWER WHILE MAINTATING POSITIVE CONTROL OF THE AIRCRAFT.  THE AIRCRAFT'S PERFORMANCE

COULD NOT MEET THE NEEDED CLIMB RATE BASED ON THE RUNWAY GRADIENT AND OBSTACLE REQUIREMENTS.  HE DECIDED HE WOULD NOT CONTINUE THE GO AROUND AND PULLED OUT THE POWER AND STALLED THE AIRCRAFT ONTO THE GROUND CAUSING DAMAGE TO THE WINGS, PROPELLER, ENGINE, AND LANDING GEAR.

## 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 GAA17CA540](https://openairdocs.org/ntsb/GAA17CA540), Sep 16, 2017: Cessna 172 (N5396D), Lynchburg, VA, substantial damage. Probable cause: The pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing.

## Other reports on N5396D (2)

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

- [Incident 20140112000549I](https://openairdocs.org/incident/20140112000549I), Jan 12, 2014: Cessna 172N (N5396D), Lynchburg, VA, Minor damage. Upon landing at W24, wind gust pushed the aircraft to the left. Landing gear on the grass broke a runway light and there was a small dent on the landing gear.…
- [Accident 19990713043079A](https://openairdocs.org/incident/19990713043079A), Jul 13, 1999: Cessna 172N (N5396D), Denver, CO, No damage. (-23) According to the flight instructor pilot, the student was on base leg and he, the instructor, pulled the power back to simulate an engine failure…

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.