# NTSB WPR11CA440: Cessna 172, N5275S, Phoenix, AZ, September 8, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: September 8, 2011, 13:50 local (20:50 UTC) - Place: Phoenix, AZ - Coordinates: 33.688056, -112.082496 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.6881&lon=-112.0825&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 27, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 81747 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11CA440 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81747/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81747 - Page: https://openairdocs.org/ntsb/WPR11CA440 ## 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. - [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 172S, 66 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072439), [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 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. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072439), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis According to the pilot, after landing he applied aileron input to compensate for the wind. During the landing roll, the airplane suddenly made a 90-degree turn and the pilot was not able to regain control of the airplane. The pilot stated that there were no mechanical problems with the airplane. A postaccident examination of the airplane revealed that it struck a runway sign and light, damaging the left elevator. ## Factual narrative According to the pilot, while in the traffic pattern he heard another pilot request a wind check and the control tower responded 190 degrees at 10 knots. The pilot reported that the airplane landed on all three landing gear and he input aileron for wind correction. On the landing roll out, the airplane suddenly made a 90-degree turn and the pilot stated that he was not able to regain control of the airplane. The pilot stated that there were no mechanical problems with the airplane. Federal Aviation Administration (FAA) inspectors responded to the site and reported that the airplane hit a runway sign and light damaging the left elevator. ## Aircraft - Registration: [N5275S](https://openairdocs.org/aircraft/N5275S), registered now, S/N 172S9203, built 2002 (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: 172S59203 - Airframe hours: 6094 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Westwind School of Aeronautics LLC - Registered owner: Lake Gateway LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Continuous airworthiness, August 31, 2011, 18 hours before - Departed: FFZ, Mesa, AZ - Destination: DVT, Phoenix, AZ - Airport: DVT, Phoenix Deer Valley Airport, runway 25L, 8,197 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; flight hours: 116 total, 116 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 102 °F, dew point 46 °F - Altimeter: 29.84 inHg - Observed at: DVT ## 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 20110908025169A](https://openairdocs.org/incident/20110908025169A), Sep 8, 2011: Cessna 172S, Phoenix, AZ, Substantial damage. Private pilot lost control of aircraft during touchdown and landing rollout. This resulted in substantial damage to the aircraft. No mechanical issues were… ## Other investigations on N5275S (1) 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 GAA16CA188](https://openairdocs.org/ntsb/GAA16CA188), Apr 6, 2016: Cessna 172 (N5275S), Payson, AZ, substantial damage. Probable cause: The student pilot's failure to maintain pitch control during the landing flare, resulting in the subsequent porpoise during landing and substantial damage to the firewall. ## Docket (1 files) The files NTSB released with the investigation on November 21, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81747. 581 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 581 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40354605&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.