# NTSB WPR10CA475: Cessna 172S, N172CY, Santa Maria, CA, July 25, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 25, 2010, 13:00 local (20:00 UTC) - Place: Santa Maria, CA - Coordinates: 34.898887, -120.457496 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.8989&lon=-120.4575&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Van Nuys FSDO - NTSB case key (mKey): 77432 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA475 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77432/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77432 - Page: https://openairdocs.org/ntsb/WPR10CA475 ## Probable cause The pilot's inadequate flare which resulted in a bounce and hard landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fuselage: frames (main fuselage)](https://openairdocs.org/ntsb-findings/01035311): Aircraft › Aircraft structures · Damaged/degraded; cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01035311/cases.md?model=2072439), [All aircraft, 8 cases](https://openairdocs.org/ntsb-findings/01035311/cases.md) - [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 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) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The solo student pilot reported that he made a 40 minute flight to the destination airport in order to meet a family member for lunch. In order to initiate the landing flare, he pulled back on the control yoke, but the airplane's nose pitched up more than he expected. The pilot stated that he corrected for the higher than expected pitch attitude by pushing forward on the yoke, resulting in the airplane's nose wheel being "dropped" onto the runway surface. After contacting the runway surface, the nose wheel porpoised (bounced) one time before contacting the surface a final time. The pilot was ultimately able to stabilize the airplane by applying back pressure to the control yoke. Although he did not become aware of it until he returned to his initial point of departure, the airplane's nose wheel had struck the runway surface with sufficient force to buckle the lower part of the firewall and the forward portion of the floorboard. The propeller had also come in contact with the runway surface. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident. ## Factual narrative The solo student pilot reported that he made a 40 minute flight to the destination airport in order to meet a family member for lunch. In order to initiate the landing flare, he pulled back on the control yoke, but the airplane's nose pitched up more than he expected. The pilot stated that he corrected for the higher than expected pitch attitude by pushing forward on the yoke, resulting in the airplane's nose wheel being "dropped" onto the runway surface. After contacting the runway surface, the nose wheel porpoised (bounced) one time before contacting the surface a final time. The pilot was ultimately able to stabilize the airplane by applying back pressure to the control yoke. Although he did not become aware of it until he returned to his initial point of departure, the airplane's nose wheel had struck the runway surface with sufficient force to buckle the lower part of the firewall and the forward portion of the floorboard. The propeller had also come in contact with the runway surface. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident. ## Aircraft - Registration: [N172CY](https://openairdocs.org/aircraft/N172CY), registered now, S/N 172S8729, built 2001 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8729 - Engines: LYCOMING IO360 SER A&C 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Pacific Aerocademy - Registered owner: Donald P Alderman Md Inc - Airworthiness certificate: Standard, Normal - Departed: KSBP, San Luis Obispo, CA - Destination: Santa Maria, CA - Airport: KSMX, Santa Maria Public, runway 30, 6,304 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 61; injuries: none; student; medical: class 3, with waivers/limitations; flight hours: 35 total, 29 in this make and model ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none ## 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 20100725055579A](https://openairdocs.org/incident/20100725055579A), Jul 25, 2010: Cessna 172S, Santa Maria, CA, Substantial damage. NTSB did not notify FAA of accident. FAA unaware of accident until 2/9/2011.NTSB report states, "the solo student pilot reported that he made a 40 minute… ## Docket (1 files) The files NTSB released with the investigation on November 5, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77432. 794 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 794 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338117&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.