# NTSB GAA17CA540: Cessna 172, N5396D, Lynchburg, VA, September 16, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: September 15, 2017, 20:00 local (Sep 16, 2017, 00:00 UTC) - Place: Lynchburg, VA - Coordinates: 37.378055, -79.122222 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.3781&lon=-79.1222&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 10, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA/ FSDO - NTSB case key (mKey): 96033 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA540 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96033/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96033 - Page: https://openairdocs.org/ntsb/GAA17CA540 ## Probable cause The pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172N, 150 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072434), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172N, 16 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072434), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 172N, 13 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=2072434), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172N, 19 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072434), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Terrain: mountainous/hilly terrain](https://openairdocs.org/ntsb-findings/03021010): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172N, 8 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md?model=2072434), [All aircraft, 329 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241); cases with it: [Cessna 172N, 21 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=2072434), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Cessna 172N, 45 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072434), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172N, 46 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072434), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The pilot reported that, during landing, the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered he could not go around when landing in this direction, at this airport, due to terrain and obstacles. He further added that he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about ¼ nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east)." The pilot reported that the landing was on runway 28. ## Factual narrative The pilot reported that, during landing the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered you "cannot go around" when landing in this direction, at this airport, due to terrain and obstacles. He further added that, he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about one 1/4 nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east). The pilot reported that the landing was on runway 28. ## Aircraft - Registration: [N5396D](https://openairdocs.org/deregistered/N5396D-2018-12-27), registration cancelled 2018-12-27, S/N 17272562, built 1979 (OpenAirDocs) - Reported make and model: CESSNA 172 (N) - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17272562 - Year built: 1979 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: OFP, Hanover, VA - Destination: W24, Lynchburg, VA - Airport: W24, Falwell, runway 28, 2,932 × 50 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 24; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review April 20, 2017; seat: left; restraint: lap only; flight hours: 351 total, 7 in this make and model, 194 as pilot in command, 88 in the last 90 days, 31 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: 350° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: 9,000 ft overcast - Temperature: 72 °F, dew point 63 °F - Altimeter: 30.11 inHg - Observed at: KLYH, 5 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20170915019399A](https://openairdocs.org/incident/20170915019399A), Sep 15, 2017: Cessna 172N, Lynchburg, VA, Substantial damage. According to the statement from the pilot: pilot made a normal approach into Falwell Airport with extra speed. Pilot ballooned the aircraft during touchdown.… ## Other investigations on N5396D (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 DEN99LA121](https://openairdocs.org/ntsb/DEN99LA121), Jul 14, 1999: Cessna 172N (N5396D), Englewood, CO, substantial damage. Probable cause: The flight instructor's failure maintain aircraft control. A factor was the inadequate supervision by the flight instructor. ## Docket (4 files) The files NTSB released with the investigation on July 19, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96033. 961 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 648 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465349&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation (Pilot in Command) (item 2, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465350&FileExtension=.PDF&FileName=Record%20of%20Conversation%20(Pilot%20in%20Command)-Master.PDF - FAA Chart Supplement W24 Airport (item 3, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465351&FileExtension=.PDF&FileName=FAA%20Chart%20Supplement%20W24%20Airport-Master.PDF - Accident Photos (item 4, .PDF, 2 photos, 183 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465352&FileExtension=.PDF&FileName=Accident%20Photos-Master.PDF 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. --- 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.