GAA20CA023

NTSB accident investigation · Cessna 172 · Louisville, KY · October 15, 2019

Accident · No injuriesData collectionFinal report
Date
October 15, 2019, 14:47 local (18:47 UTC)
Place
Louisville, KY
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6097GCessna 172
Defining event
Landing: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report May 21, 2020
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20191015017379A
Case key
100430

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 student pilot's improper landing flare, which resulted in a porpoised landing, a subsequent hard landing on grass left of the runway, and a nose-over. Contributing to the accident was the student’s self-imposed pressure to land the airplane

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.

Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172S: 99 casesAll aircraft: 1,285 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · Student/instructed pilotCessna 172S: 206 casesAll aircraft: 9,295 casesProbable cause
Runway/land/takeoff/taxi surface: soft surfaceEnvironmental issues › Physical environment · Effect on operationCessna 172S: 5 casesAll aircraft: 264 casesProbable cause
Wind: crosswindEnvironmental issues › Conditions/weather/phenomena · Effect on operationCessna 172S: 18 casesAll aircraft: 1,008 casesProbable cause
Personality/attitude: motivation/respond to pressurePersonnel issues › Psychological · Student/instructed pilotCessna 172S: 2 casesAll aircraft: 53 casesProbable cause

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 solo student pilot reported that, while in the traffic pattern to land, the flaps would not lower, and he had to move the flap lever up and down several times to troubleshoot. Once on the base leg, he realized that the airplane was faster than normal. On final, he extended the flaps to 30° but felt the airplane was too high and fast. He reduced power to correct, and over the threshold, the airplane encountered a crosswind which pushed the airplane to the left of the runway centerline. He reduced power to idle and pushed the nose down "too quickly." The nose landing gear hit the runway first, the airplane porpoised, and he attempted to pitch the nose up to decrease airspeed. He was then worried that the airplane would aerodynamically stall "too high in the air," so he pitched the nose down. The airplane landed hard in the grass left of the runway, the nose dug into the ground, and the airplane came to rest inverted. The airplane sustained substantial damage to the right wing. The student reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation and that he should have added full power and performed a go-around. He added that he felt pressured to land the airplane to "get out of everyone's way."

Factual narrative

The solo student pilot reported that, during the traffic pattern to land, the flaps would not lower and he had to move the flap lever up and down several times to troubleshoot. On base, he realized that he was faster than normal. On final, he extended the flaps to 30°, but felt he was too high and fast. He reduced power to correct and over the threshold, a crosswind drifted the airplane to the left. He reduced power to idle and pushed the nose down "too quickly." The airplane porpoised and he attempted to pitch the nose up to decrease airspeed. He was then worried that the airplane would aerodynamically stall, so he pitched the nose down. The airplane landed hard in the grass left of the runway, the nose dug into the ground, and the airplane came to rest inverted. The airplane sustained substantial damage to the right wing. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airport's automated weather observation station reported that, about 6 minutes after the accident, the wind was from 200° at 11 knots. The student pilot was landing the airplane on runway 15. The student pilot reported that he should have added full power and performed a go around. He added that he felt pressured to land the airplane to "get out of everyone's way."

Aircraft

Registration
N6097G
Reported as
Cessna 172 (S)
Category
Airplane
Serial number
172S9673
Built
2004
Airframe hours
7,736.8
Engine
Lycoming IO-360-L2A, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Cardinal Wings Aviation LLC
Registered owner
Bccm Aircraft Holdings Llc
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
100 hour · September 17, 2019
Departed
27K · Georgetown, KY
Destination
LOU · Louisville, KY
Airport
LOU · Bowman Field, runway 15, 3,580 × 75 ft, asphalt
Equipment
ADS-B, Auto-pilot

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
Student pilot
Age
47
Injuries
None
Certificate
Student
Medical
Class 3, With waivers/limitations
Seat
Left
Flight hours
52 total · 52 in this make and model · 1 as pilot in command · 20 in the last 90 days · 5 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
200° at 11 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
73 °F, dew point 54 °F
Altimeter
29.90 inHg
Observed at
KLOU

Docket · 3

The files NTSB released with the investigation on December 12, 2019, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.0 MB 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.