# NTSB CHI08CA091: Cessna 172R, N53417, Batavia, OH, March 17, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 17, 2008, 12:30 local (16:30 UTC) - Place: Batavia, OH - Coordinates: 39.070388, -84.179054 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.0704&lon=-84.1791&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 30, 2008 - Report: Approved by Office Director - Parties: FAA-Cincinnati FSDO - NTSB case key (mKey): 67777 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI08CA091 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67777/pdf - Page: https://openairdocs.org/ntsb/CHI08CA091 ## Probable cause The pilot's misjudgment of the landing flare and her inadequate recovery from the 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 · Incorrect use/operation (probable cause); cases with it: [Cessna 172R, 37 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072401), [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 · Pilot (probable cause); cases with it: [Cessna 172R, 75 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072401), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172R, 8 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072401), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/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); cases with it: [Cessna 172R, 25 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072401), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172R, 40 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072401), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172R, 39 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072401), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172R, 10 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072401), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The student pilot stated that she was practicing touch-and-goes on runway 4 (3,568 feet by 75 feet, asphalt) as part of a solo instructional flight when the accident occurred. She noted that the winds were variable and gusty, and it was "choppy" in the pattern. The accident occurred on what was to be the final landing for the day. The pilot reported that the airplane was established on final approach about 65 knots. The airplane was slightly low, but she did not feel the need to correct the glide path. The airplane touched down and its nose suddenly turned to the left. As the nose went to the left, the airplane bounced. She "gently lowered the nose, but the plane bounced again and again." Her efforts to regain control were not successful and the airplane ultimately came to rest in a grass area to the left side of the runway. The nose landing gear collapsed during the accident sequence. A post accident inspection did not reveal any anomalies consistent with a pre-impact failure or malfunction. Archived weather information was not available for the accident airport. Winds recorded at an airport about 10 miles north of the accident airport were from 110 degrees at 9 knots. The pilot reported a total flight time of 97.5 hours. She had accumulated a total of 5.8 hours as pilot-in-command (PIC) and 2.3 hours as PIC in the same make and model aircraft. ## Factual narrative The student pilot stated that she was practicing touch-and-goes on runway 4 (3,568 feet by 75 feet, asphalt) as part of a solo instructional flight when the accident occurred. She noted that the winds were variable and gusty, and it was "choppy" in the pattern. The accident occurred on what was to be the final landing for the day. The pilot reported that the airplane was established on final approach about 65 knots. The airplane was slightly low, but she did not feel the need to correct the glide path. The airplane touched down and its nose suddenly turned to the left. As the nose went to the left, the airplane bounced. She "gently lowered the nose, but the plane bounced again and again." Her efforts to regain control were not successful and the airplane ultimately came to rest in a grass area to the left side of the runway. The nose landing gear collapsed during the accident sequence. A post accident inspection did not reveal any anomalies consistent with a pre-impact failure or malfunction. Archived weather information was not available for the accident airport. Winds recorded at an airport about 10 miles north of the accident airport were from 110 degrees at 9 knots. The pilot reported a total flight time of 97.5 hours. She had accumulated a total of 5.8 hours as pilot-in-command (PIC) and 2.3 hours as PIC in the same make and model aircraft. ## Aircraft - Registration: [N53417](https://openairdocs.org/aircraft/N53417), registered now, S/N 17281162, built 2003 (OpenAirDocs) - Reported make and model: Cessna 172R - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17281162 - Airframe hours: 3297 - Engines: Lycoming IO-360-L2A 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Eastern Cincinnati Aviation, Inc. - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Continuous airworthiness, March 1, 2008 - Departed: I69, Batavia, OH - Airport: runway 04, 3,658 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 62; injuries: none; student; medical: class 3, with waivers/limitations; last flight review March 1, 2008; seat: left; flight hours: 98 total, 95 in this make and model, 6 as pilot in command, 23 in the last 90 days, 14 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 110° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 43 °F, dew point 23 °F - Altimeter: 30.45 inHg - Observed at: LUK, 10 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 20080317833189A](https://openairdocs.org/incident/20080317833189A), Mar 17, 2008: Cessna 172R, Batavia, OH, Substantial damage. (-23) On landing, the aircraft started to porpoise, bounced on the runway three times. The propeller struck the runway on the second and third bounce. On the… 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.