GAA16CA301

NTSB accident investigation · Cessna 172 · Urbana, OH · June 8, 2016

Accident · No injuriesData collectionFinal report
Date
June 8, 2016, 16:57 local (20:57 UTC)
Place
Urbana, OH
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8324ECessna 172
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report September 12, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160608013719A
Case key
93365

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 abnormal runway contact during the landing flare, which resulted in a porpoise, hard landing, and runway excursion.

Findings · 3

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: landing flareAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172N: 38 casesAll aircraft: 1,285 casesProbable cause
Wind: crosswindEnvironmental issues › Conditions/weather/phenomena · Effect on equipmentCessna 172N: 19 casesAll aircraft: 1,008 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

In a telephone interview with the NTSB Investigator-in-charge (IIC), the pilot stated that the airplane porpoised during landing, then veered left off the runway and onto an intersecting runway. A postaccident examination revealed substantial damage to the firewall. According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. A review of recorded data from the automated weather observation station located about 14 miles northwest of the airport, revealed that, about 7 minutes before the accident the wind was 310 degrees true at 8 knots, and wind gusts 16 knots. The airplane landed on runway 02. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first setting off a series of motions that imitate the jumps and dives of a porpoise—hence the name. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, mistrimming 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. The corrective action for a porpoise is the same as for a bounce and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane's pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude.

Factual narrative

In a telephone interview with the NTSB Investigator-in-charge (IIC), the pilot stated that the airplane porpoised during landing, then veered left off the runway and onto an intersecting runway. A postaccident examination revealed substantial damage to the firewall. According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. A review of recorded data from the automated weather observation station located about 14 miles northwest of the airport, revealed that, about 7 minutes before the accident the wind was 310 degrees true at 8 knots, and wind gusts 16 knots. The airplane landed on runway 02. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first setting off a series of motions that imitate the jumps and dives of a porpoise—hence the name. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, mistrimming 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. The corrective action for a porpoise is the same as for a bounce and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane's pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude.

Aircraft

Registration
N8324E
Reported as
Cessna 172 (N)
Category
Airplane
Serial number
17272189
Built
1979
Engine
Lycoming O-320 SERIES, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Aviation Sales Inc.
Registered owner
Aviation Sales Inc.
Airworthiness certificate
Standard, Utility; Standard, Normal
Departed
MGY · Dayton, OH
Destination
I74 · Urbana, OH
Airport
I74 · Grimes Field, runway 02, 4,400 × 100 ft, asphalt
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
56
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
142.5 total · 95.9 in this make and model · 22.1 as pilot in command · 5.4 in the last 90 days · 2 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
310° at 8 knots, gusting 16
Visibility
10 statute miles
Temperature
68 °F, dew point 43 °F
Altimeter
29.97 inHg
Observed at
KEDJ, 14 nm away

Docket · 3

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