# NTSB WPR10CA392: Cessna 172P, N64204, San Jose, CA, August 8, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 8, 2010, 14:00 local (21:00 UTC) - Place: San Jose, CA - Coordinates: 37.326389, -121.818611 - Nearby events: https://openairdocs.org/map.md?lat=37.3264&lon=-121.8186&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: 1 uninjured - Status: Completed, report March 16, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76903 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA392 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76903/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76903 - Page: https://openairdocs.org/ntsb/WPR10CA392 ## Probable cause The pilot’s improper flare and inadequate recovery from 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 · Incorrect use/operation (probable cause); cases with it: [Cessna 172P, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072436), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172P, 19 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072436), [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) (defining event); cases with it: [Cessna 172P, 16 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072436), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The pilot reported that after a cross-country flight, she maneuvered the airplane onto final approach while maintaining about 65 knots. The pilot flared too early and as a result, the airplane stalled and landed hard. The airplane bounced down the runway and the pilot continued to pull back on the control yoke. After the third bounce, the airplane touched down and came to a stop at the end of the runway. As the pilot was taxiing the airplane back to the parking area, she noticed that when the rudder was fully deflected to the right it made a clipping sound. When she exited the airplane, she examined the airplane and observed the propeller tips were bent. Postaccident examination of the airplane by a Federal Aviation Administration inspector revealed that the airplane sustained substantial damage to the firewall and fuselage. The pilot reported no mechanical failures or malfunctions prior to the accident. ## Factual narrative The pilot reported that after a cross country flight an airspeed of 65 knots was maintained while on final approach. When the airplane touched-down the pilot thought the landing was hard “where I flared a bit too early and stalled...But there was a total unexpected bounce.” The pilot stated she verified the throttle was idle when the airplane touched down again and bounced a second time. The pilot continued to pull back on the yoke and the airplane touched down and bounced for a third time. After the third bounce the airplane touched down and came to a stop at the end of the runway. As the pilot was taxiing the airplane back to the parking area, she noticed that when the rudder was fully deflected to the right it made a clipping sound. When she exited the airplane, she examined the airplane and observed the propeller tips were bent. Post examination of the airplane by a Federal Aviation Administration inspector revealed that the airplane sustained substantial damage to the firewall and fuselage. The pilot reported no mechanical failures or malfunctions prior to the accident. ## Aircraft - Registration: [N64204](https://openairdocs.org/deregistered/N64204-2019-06-12), registration cancelled 2019-06-12, S/N 17275534, built 1981 (OpenAirDocs) - Reported make and model: CESSNA 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17275534 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Ahart Aviation - Registered owner: Ahart Aviation - Airworthiness certificate: Standard, Normal - Departed: KLVK, Livemore, CA - Destination: KRHV, San Jose, CA - Airport: KRHV, Reid-Hillview Airport, runway 13L, 3,100 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 19; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review October 26, 2009; seat: left; flight hours: 284 total, 53 in this make and model, 168 as pilot in command, 18 in the last 90 days, 18 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 80° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 54 °F - Altimeter: 29.88 inHg - Observed at: KRHV ## 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 20100808042159A](https://openairdocs.org/incident/20100808042159A), Aug 8, 2010: Cessna 172P, San Jose, CA, Substantial damage. While landing at reid hillview airport runway 13L the pilot experienced a hard landing resulting in three to four bounces. Due to the hard landing the aircraft… ## Other investigations on N64204 (2) 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. - [NTSB WPR18CA072](https://openairdocs.org/ntsb/WPR18CA072), Jan 20, 2018: Cessna 172P (N64204), Cloverdale, CA, substantial damage. Probable cause: The pilot's failure to maintain airplane control during the approach and his delayed decision to go around. - [NTSB WPR09CA209](https://openairdocs.org/ntsb/WPR09CA209), Apr 20, 2009: Cessna 172P (N64204), Livermore, CA, substantial damage. Probable cause: The student pilot’s improper recovery from a bounced landing. ## Docket (2 files) The files NTSB released with the investigation on September 27, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76903. 719 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 604 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40336615&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Other Pertinent Forms and Reports (item 2, .PDF, 115 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40335891&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports-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.