# NTSB WPR11CA259: Cessna 172P, N9849L, Palo Alto, CA, June 8, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 8, 2011, 14:10 local (21:10 UTC) - Place: Palo Alto, CA - Coordinates: 37.461112, -122.114997 - 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-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 22, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 80746 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11CA259 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/80746/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=80746 - Page: https://openairdocs.org/ntsb/WPR11CA259 ## Probable cause The pilot's failure to maintain directional control during the landing roll. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation; cases with it: [Cessna 172P, 10 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072436), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 28 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072436), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/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 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [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-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 172P, 29 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072436), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172P, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072436), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that during his descent to land, he observed the windsock and made a mental note to maintain aileron correction for the crosswind. As the airplane reached about 35-40 feet above the runway, the pilot reduced power to idle and at an altitude of 2 feet he initiated the landing flare. The stall warning horn sounded and the nose of the airplane started to veer to the left. After the airplane touched down, the pilot applied right rudder and the airplane started to veer off to the right. The airplane exited the right side of the runway and struck a pipe that was protruding from the ground, substantially damaging the nose gear and firewall. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal flight. ## Factual narrative The pilot reported that during his descent to land, he observed the windsock and made a mental note to maintain aileron correction for the crosswind. As the airplane reached about 35-40 feet above the runway, the pilot reduced power to idle and at about 2 ft he initiated the landing flare. The stall warning horn sounded and the nose of the airplane started to veer to the left. After the airplane touched down, the pilot applied right rudder and the airplane started to veer off to the right. The airplane exited the right side of the runway and struck a pipe that was protruding from the ground, substantially damaging the nose gear and firewall. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal flight. ## Aircraft - Registration: [N9849L](https://openairdocs.org/aircraft/N9849L), registered now, S/N 17276637, built 1986 (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: 17276637 - Airframe hours: 10428 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 6, 2011, 32 hours before - Departed: KMAE, Madera, CA - Destination: KPAO, Palo Alto, CA - Airport: KPAO, Palo Alto Airport, runway 31, 2,443 × 70 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 26; injuries: none; private; airplane ratings: single-engine land; medical: class 1, without waivers/limitations; last flight review July 31, 2010; seat: left; flight hours: 81 total, 33 in this make and model, 36 as pilot in command, 25 in the last 90 days, 23 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 12 knots - Visibility: 15 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 54 °F - Altimeter: 29.96 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 20110608010659A](https://openairdocs.org/incident/20110608010659A), Jun 8, 2011: Cessna 172P, Palo Alto, CA, Substantial damage. The pilot was returning from madera California. He was cleared for the straight-in visual approach to runway 31 at the Palo Alto airport. The winds were… ## Docket (2 files) The files NTSB released with the investigation on June 24, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=80746. 613 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 563 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40349993&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation - Pilot (item 2, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40349983&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-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.