# NTSB WPR10CA062: Cessna 172, N8504B, Yucca Valley, CA, November 21, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 21, 2009, 09:30 local (17:30 UTC) - Place: Yucca Valley, CA - Coordinates: 34.337223, -116.579719 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.3372&lon=-116.5797&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: 2 uninjured - Status: Completed, report March 23, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 75081 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA062 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75081/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75081 - Page: https://openairdocs.org/ntsb/WPR10CA062 ## Probable cause The pilot's inadequate compensation for the crosswind gusts and failure to maintain directional control of the airplane. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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 172, 8 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072402), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Cessna 172, 3 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072402), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/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 172, 30 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072402), [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-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172, 14 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072402), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-flare/touchdown: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172, 11 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072402), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The pilot was landing in a crosswind when a gust of wind coming between hangars caused the airplane to veer away from the wind and off the runway. The pilot applied full power in an attempt to execute a go-around, but subsequently impacted terrain and nosed over. The pilot said there were no preimpact mechanical malfunctions or failures. ## Factual narrative The pilot stated in the Pilot/Operator Accident Report that he was landing in a crosswind, when a gust of wind coming between hangars caused the airplane to veer away from the wind and off the runway. The pilot applied full power in an attempt to execute a go-around but subsequently impacted terrain and nosed over. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. ## Aircraft - Registration: [N8504B](https://openairdocs.org/deregistered/N8504B-2018-01-26), registration cancelled 2018-01-26, S/N 36204, built 1957 (OpenAirDocs) - Reported make and model: CESSNA 172 - Registry model: [Cessna 172](https://openairdocs.org/model/cessna-172) (registry code 2072402) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 36204 - Engines: CONT MOTOR O-300 SER 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: KTNP, Twentynine Palm, CA - Destination: 6CA5, Yucca Valley, CA - Airport: 6CA5, Valley Vista Airport, runway 18, 3,000 × 60 ft, dirt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 29; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review December 4, 2008; seat: left; flight hours: 115 total, 115 in this make and model, 3 in the last 90 days, 2 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 240° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 48 °F, dew point 18 °F - Altimeter: 29.98 inHg - Observed at: KL35 ## 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 20091121024139A](https://openairdocs.org/incident/20091121024139A), Nov 21, 2009: Cessna 172, Yucca Valley, CA, Substantial damage. Contact with the pilot has been by voice mail, because of his work location. He is not able to receive calls during the normal work hours. This report will be… ## Docket (1 files) The files NTSB released with the investigation on December 22, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75081. 333 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 333 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40323254&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.