# NTSB CEN09CA509: Cessna 172S, N6186T, Bluffton, OH, August 6, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 6, 2009, 18:00 local (22:00 UTC)
- Place: Bluffton, OH
- Coordinates: 40.885276, -83.868614 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.8853&lon=-83.8686&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report October 19, 2009
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 74486
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA509
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74486/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74486
- Page: https://openairdocs.org/ntsb/CEN09CA509

## Probable cause

The student pilot's failure to compensate for wind conditions and maintain aircraft control during the landing.

## Findings

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

- [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072439), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/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 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2072439), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [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: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172S, 49 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072439), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)

## Analysis

The airplane experienced a hard landing when it encountered a gust of wind just prior to the landing flare during a student solo flight. The student pilot reported that during the touchdown, the left main landing gear and nose landing gear impacted the runway. Unknown that the airplane was damaged, the student pilot executed a touch-and-go and flew the airplane back to his home airport. Examination of the airplane revealed the firewall was buckled.

## Factual narrative

The airplane experienced a hard landing after encountering a gust of wind just prior to the landing flare during a student solo flight. The student pilot reported that during the touchdown, the left main landing gear and nose landing gear impacted the runway. Unknown that the airplane was damaged, the student pilot executed a touch-and-go and flew the airplane back to his home airport. Examination of the airplane revealed the firewall was buckled, resulting in substantial damage to the airplane.

## Aircraft

- Registration: [N6186T](https://openairdocs.org/aircraft/N6186T), registered now, S/N 172S10729, built 2008 (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S10729
- Airframe hours: 263
- Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, August 4, 2009
- Departed: 5G7, Bluffton, OH
- Destination: FDY, Findlay, OH
- Airport: 5G7, Bluffton Airport, runway 05, 4,126 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 53; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 36 total, 36 in this make and model, 11 as pilot in command, 27 in the last 90 days, 11 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 330° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 81 °F
- Altimeter: 30.02 inHg

## 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 20090806048429A](https://openairdocs.org/incident/20090806048429A), Aug 6, 2009: Cessna 172S, Bluffton, OH, Substantial damage. Student departed fdy for solo practice. While practicing touch and go landings at 5G7, on runway 5, the pilot reported the left main touched down first,…

## Docket (1 files)

The files NTSB released with the investigation on August 19, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74486. 430 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 430 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40317510&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.