GAA17CA540

NTSB accident investigation · Cessna 172 · Lynchburg, VA · September 16, 2017

Accident · No injuriesData collectionFinal report
Date
September 15, 2017, 20:00 local (Sep 16, 2017, 00:00 UTC)
Place
Lynchburg, VA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5396DCessna 172
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Night
Status
Completed · report September 10, 2018
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA/ FSDO
FAA report
20170915019399A
Case key
96033

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 172N: 150 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Incorrect use/operationCessna 172N: 16 casesAll aircraft: 809 casesProbable cause
Performance/control parameters: angle of attackAircraft › Aircraft oper/perf/capability · Capability exceededCessna 172N: 13 casesAll aircraft: 990 casesProbable cause
Performance/control parameters: airspeedAircraft › Aircraft oper/perf/capability · Incorrect use/operationCessna 172N: 19 casesAll aircraft: 1,681 casesProbable cause
Terrain: mountainous/hilly terrainEnvironmental issues › Physical environment · Contributed to outcomeCessna 172N: 8 casesAll aircraft: 329 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Cessna 172 (N)
Category
Airplane
Serial number
17272562
Built
1979
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
24
Injuries
None
Certificates
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

Docket · 4

The files NTSB released with the investigation on July 19, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 961 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N5396D · 1

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