# NTSB GAA16CA301: Cessna 172, N8324E, Urbana, OH, June 8, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: June 8, 2016, 16:57 local (20:57 UTC)
- Place: Urbana, OH
- Coordinates: 40.130279, -83.754447 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.1303&lon=-83.7544&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report September 12, 2016
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 93365
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA301
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93365/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93365
- Page: https://openairdocs.org/ntsb/GAA16CA301

## Probable cause

The pilot's abnormal runway contact during the landing flare, which resulted in a porpoise, hard landing, and runway excursion.

## 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: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172N, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072434), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Effect on equipment; cases with it: [Cessna 172N, 19 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072434), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172N, 26 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072434), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072434), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-flare/touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072434), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## 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](https://openairdocs.org/aircraft/N8324E), registered now, S/N 17272189, 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: 17272189
- Year built: 1979
- Engines: 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

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 56; injuries: none; 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

## 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 20160608013719A](https://openairdocs.org/incident/20160608013719A), Jun 8, 2016: Cessna 172N, Urbana, OH, Substantial damage. Making an approach to runway 22 during the flare a gust of wind caused the airplane lift and land hard

## Docket (3 files)

The files NTSB released with the investigation on August 24, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93365. 2.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443646&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Record of Phone Conversation (Pilot) (item 2, .PDF, 186 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443647&FileExtension=.PDF&FileName=Record%20of%20Phone%20Conversation%20(Pilot)-Master.PDF
- Accident Photo (Courtesy of FAA) (item 3, .PDF, 1 photo, 135 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40443648&FileExtension=.PDF&FileName=Accident%20Photo%20(Courtesy%20of%20FAA)-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.