GAA16CA473

NTSB accident investigation · Cessna 172 · Fulton, MO · August 14, 2016

Accident · No injuriesData collectionFinal report
Date
August 14, 2016, 11:00 local (16:00 UTC)
Place
Fulton, MO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N78242Cessna 172
Defining event
Landing: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report January 18, 2017
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160814014449A
Case key
93976

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 improper landing flare and subsequent improper recovery from a bounced landing, which resulted in the airplane porpoising.

Findings · 2

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 172K: 33 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationCessna 172K: 9 casesAll aircraft: 1,285 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 pilot reported that during the initial touchdown he "got a bad bounce." On the third bounce the nose wheel "gave way and the propeller impacted the ground." The airplane sustained substantial damage to the firewall. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3B (2016). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first initiating a series of motions that imitate the jumps and dives of a porpoise. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, miss-trimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again.

Factual narrative

The pilot reported that during the initial touchdown he "got a bad bounce". On the third bounce the nose wheel "gave way and the propeller impacted the ground". The airplane sustained substantial damage to the firewall. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3B (2016). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first initiating a series of motions that imitate the jumps and dives of a porpoise. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, miss-trimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again.

Aircraft

Registration
N78242
Reported as
Cessna 172 (K)
Category
Airplane
Serial number
17257543
Built
1968
Airframe hours
3,698
Engine
Lycoming O-320-E2D, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · May 1, 2016
Departed
VER · Boonville, MO
Destination
FTT · Fulton, MO
Airport
FTT · Elton Hensley Memorial, runway 18, 4,001 × 75 ft, concrete
Equipment
None

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
72
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
April 16, 2015
Seat
Left
Flight hours
413 total · 77 in this make and model · 413 as pilot in command

Weather

Conditions
Visual (VMC) · Day
Wind
150° at 8 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
81 °F, dew point 68 °F
Altimeter
30.10 inHg
Observed at
KCOU, 10 nm away

Docket · 2

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