# NTSB GAA18CA294: Cessna 172, N254EK, Palo Alto, CA, April 30, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 29, 2018, 19:40 local (Apr 30, 2018, 02:40 UTC) - Place: Palo Alto, CA - Coordinates: 37.461112, -122.114997 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.4611&lon=-122.1150&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: 4 uninjured - Status: Completed, report October 24, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 97313 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA294 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97313/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97313 - Page: https://openairdocs.org/ntsb/GAA18CA294 ## Probable cause The pilot’s improper landing flare, which resulted in a hard 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 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) - [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. - [Approach: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Cessna 172S, 11 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=2072439), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The pilot reported that, during short final, he noticed "a sudden lack of wind," and the airplane began to descend. He added that the airplane landed hard and bounced multiple times. He taxied back to the parking ramp without further incident. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airplane rental company owner reported that the pilot did not notify any personnel of the hard, bounded landing. He added that, during a later flight, the airplane owner noticed a vibration and landed to examine the airplane. Postflight examination revealed propeller damage and substantial damage to the fuselage. ## Factual narrative The pilot reported that, during short final, he noticed "a sudden lack of wind" and the airplane began to descend. He added that the airplane landed hard and bounced multiple times. He taxied back to the parking ramp without further incident. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The owner of the airplane rental company reported that the pilot did not notify any personnel of the hard, bounded landing. He added that, during a later flight, the owner of the airplane noticed a vibration and landed to examine the airplane. Postflight examination revealed propeller damage and substantial damage to the fuselage. ## Aircraft - Registration: [N254EK](https://openairdocs.org/aircraft/N254EK), registered now, S/N 172S11119, built 2011 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - 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: 172S11119 - Year built: 2011 - Engines: LYCOMING IO-360-L2A reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: PAO, Palo Alto, CA - Destination: PAO, Palo Alto, CA - Airport: PAO, Palo Alto, runway 31, 2,443 × 70 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 32; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review May 17, 2017; seat: left; restraint: 3-point; flight hours: 136 total, 136 in this make and model, 25 as pilot in command, 3 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 10 knots - Visibility: 10 statute miles - Altimeter: 30.06 inHg - Observed at: KPAO ## 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 20180429010699A](https://openairdocs.org/incident/20180429010699A), Apr 29, 2018: Cessna 172S, Palo Alto, CA, Substantial damage. Livermore, CA (lvk): N254EK, C172, aircraft porpoised on landing and sustained a prop strike with possible fire wall damage. Note: this is a late report and it… ## Docket (3 files) The files NTSB released with the investigation on August 28, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97313. 4.9 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40466104&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation - Rental Owner (item 2, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40466105&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Rental%20Owner-Master.PDF - Accident Photos (item 3, .PDF, 2 photos, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40466106&FileExtension=.PDF&FileName=Accident%20Photos-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.