# NTSB GAA17CA556: Cessna 172, N5146R, Gallatin, TN, September 16, 2017

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 16, 2017, 13:20 local (18:20 UTC)
- Place: Gallatin, TN
- Coordinates: 36.374168, -86.408332 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=36.3742&lon=-86.4083&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 15, 2017
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 96093
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA556
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96093/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96093
- Page: https://openairdocs.org/ntsb/GAA17CA556

## Probable cause

The student pilot’s improper landing flare, which resulted in a bounced landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [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 172M, 37 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072418), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

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

- [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172M, 30 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072418), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Cessna 172M, 47 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072418), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Landing: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172M, 19 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072418), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172M, 51 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072418), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The student pilot reported that, while attempting a touch-and-go landing, the airplane bounced. He added that he "worked the yoke" to stabilize the airplane, but the airplane bounced a second time and veered off the runway to the left. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Factual narrative

The student pilot reported that, while attempting a touch-and-go landing, the airplane bounced. He added that, he "worked the yoke" to stabilize the airplane, but the airplane bounced a second time and veered off the runway to the left. Subsequently, the airplane sustained substantial damage to the firewall. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N5146R](https://openairdocs.org/deregistered/N5146R-2021-01-09), registration cancelled 2021-01-09, S/N 17263363, built 1974 (OpenAirDocs)
- Reported make and model: CESSNA 172 (M)
- Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17263383
- Year built: 1974
- Airframe hours: 8953.5
- Engines: LYCOMING O-320-E2D 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Airworthiness certificate: Standard, Normal; Standard, Utility
- Last inspection: 100 hour, July 23, 2017
- Departed: BNA, NASHVILLE, TN
- Destination: M33, Gallatin, TN
- Flight plan: VFR
- Airport: M33, Sumner County Rgnl, runway 17, 6,300 × 100 ft, asphalt
- Equipment: ADS-B

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 55; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 142 total, 141 in this make and model, 15 as pilot in command, 15 in the last 90 days, 8 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 70° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: 5,500 ft broken
- Temperature: 82 °F, dew point 66 °F
- Altimeter: 30.13 inHg
- Observed at: KBNA, 20 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 20170916019489A](https://openairdocs.org/incident/20170916019489A), Sep 16, 2017: Cessna 172M, Gallitin, TN, Substantial damage. Entered downwind pattern for runway 17 for touch and go. Completed first touch and go reported his position turned crosswind for runway 17 entered downwind, on…

## Docket (2 files)

The files NTSB released with the investigation on November 16, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96093. 4.2 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458036&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Accident Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 395 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458037&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.