# NTSB WPR15CA004: Cessna 172S, N2179L, Sedona, AZ, October 5, 2014 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: October 5, 2014, 10:30 local (17:30 UTC) - Place: Sedona, AZ - Coordinates: 34.848609, -111.78833 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.8486&lon=-111.7883&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: Minor injuries - Injuries: 1 minor - Status: Completed, report December 5, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - NTSB case key (mKey): 90221 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15CA004 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90221/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90221 - Page: https://openairdocs.org/ntsb/WPR15CA004 ## Probable cause The pilot's failure to maintain airplane control during the landing roll out. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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) - [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) - [Terrain: sloped/uneven terrain](https://openairdocs.org/ntsb-findings/03021017): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172S, 3 cases](https://openairdocs.org/ntsb-findings/03021017/cases.md?model=2072439), [All aircraft, 270 cases](https://openairdocs.org/ntsb-findings/03021017/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) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072439), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The pilot stated that he was on an extended final for landing. As he got closer to the runway, he noted that he was right of centerline, and made corrections to return to the runway centerline for landing. The pilot indicated that he was still making corrections as he initiated the flare to land. The flare was too high, and as a result, the airplane developed a greater than desired sink rate, which he corrected by adding power. The pilot stated that the landing was firmer than normal, and the airplane bounced before it settled back to the runway. The pilot looked inside the cockpit to retract the flaps and reduce the power to idle. When he looked back outside, the airplane was pointed off the runway. The pilot added right rudder to correct back to the runway. He did not want to add too much rudder and lose airplane control, and when he went to apply the brakes, he noted that his feet were too far down the rudder pedals, so there was no braking action. The airplane departed the runway surface, and traveled onto the grass, toward a ditch. As the airplane traversed through the ditch, the nose landing gear collapsed, the propeller struck the ground, and then the airplane came to rest inverted. The airplane sustained substantial damage to right wing, rudder, and vertical stabilizer. The pilot reported that there were no mechanical malfunctions with the airplane that would have precluded normal operation. In the Recommendation (how could this accident/incident have been prevented) section of the accident report, the pilot reported that the flight school has changed their policy, and no longer allows solo students to fly to the accident airport. He further reported that if he had ensured positive aircraft control prior to retracting the flaps, or taking his attention away from the landing, the airplane would not have yawed to the side of the runway. ## Factual narrative The pilot stated that he was on an extended final for landing. As he got closer to the runway, he noted that he was right of centerline, and made corrections to return to the runway centerline for landing. The pilot indicated that he was still making corrections as he initiated the flare to land. The flare was too high, and as a result, the airplane developed a greater than desired sink rate, which he corrected by adding power. The pilot stated that the landing was firmer than normal, and the airplane bounced before it settled back to the runway. The pilot looked inside the cockpit to retract the flaps and reduce the power to idle. When he looked back outside, the airplane was pointed off the runway. The pilot added right rudder to correct back to the runway. He did not want to add too much rudder and lose airplane control, and when he went to apply the brakes, he noted that his feet were too far down the rudder pedals, so there was no braking action. The airplane departed the runway surface, and traveled onto the grass, toward a ditch. As the airplane traversed through the ditch, the nose landing gear collapsed, the propeller struck the ground, and then the airplane came to rest inverted. The airplane sustained substantial damage to right wing, rudder, and vertical stabilizer. The pilot reported that there were no mechanical malfunctions with the airplane that would have precluded normal operation. In the Recommendation (how could this accident/incident have been prevented) section of the accident report, the pilot reported that the flight school has changed their policy, and no longer allows solo students to fly to the accident airport. He further reported that if he had ensured positive aircraft control prior to retracting the flaps, or taking his attention away from the landing, the airplane would not have yawed to the side of the runway. ## Aircraft - Registration: [N2179L](https://openairdocs.org/deregistered/N2179L-2019-04-24), registration cancelled 2019-04-24, S/N 172S9633, built 2004 (OpenAirDocs) - Reported make and model: CESSNA 172S - 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: 172S9633 - Year built: 2004 - Airframe hours: 7558 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Northern Arizona Investment Group LLC - Registered owner: Northern Arizona Investment Group LLC - Airworthiness certificate: Certificate of authorization or waiver (COA) - Last inspection: 100 hour, September 15, 2014, 50 hours before - Departed: PRC, PRESCOTT, AZ - Destination: SEZ, Sedona, AZ - Airport: SEZ, Sedona, runway 03, 5,132 × 100 ft, asphalt - Equipment: Electronic flight bag or handheld device, Data recorder, Auto-pilot, Angle of attack indicator, Airframe parachute, ADS-B, Video recording device, Stall warning system, Onboard weather, Heads up display, Electronic primary flight display, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 29; injuries: minor; flight instructor, commercial; instrument ratings: helicopter; medical: class 2, without waivers/limitations; last flight review April 15, 2014; seat: left; restraint: 3-point; flight hours: 403 total, 22 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 27 °F - Altimeter: 30.29 inHg - Observed at: KFLG, 19 nm away ## 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 20141005019399A](https://openairdocs.org/incident/20141005019399A), Oct 5, 2014: Cessna 172S, Sedona, AZ, Substantial damage. When he arrived at the Sedona airport he thought he was a little high and fast. He touched down hard and bounced the airplane; at this time directional control… ## Other investigations on N2179L (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 WPR17FA063](https://openairdocs.org/ntsb/WPR17FA063), Feb 12, 2017: Cessna 172 (N2179L), Ramona, CA, substantial damage, 1 fatal. Probable cause: The flight instructor's failure to ensure that adequate clearance from terrain was maintained after performance of a simulated engine failure maneuver, which resulted in controlled flight into… ## Docket (2 files) The files NTSB released with the investigation on November 20, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90221. 4.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - Pilot (item 1, .PDF, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419245&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20Pilot-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - Operator (item 2, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40419247&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20Operator-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.