# NTSB CEN11CA261: Cessna 172N, N3484E, Colorado Springs, CO, April 3, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 3, 2011, 12:00 local (18:00 UTC) - Place: Colorado Springs, CO - Coordinates: 38.805831, -104.700836 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.8058&lon=-104.7008&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 June 20, 2011 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 78746 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11CA261 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78746/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78746 - Page: https://openairdocs.org/ntsb/CEN11CA261 ## Probable cause The pilot loss of directional control during landing in gusty crosswind conditions. ## 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 172N, 82 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072434), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cessna 172N, 28 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072434), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Cessna 172N, 18 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=2072434), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072434), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072434), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis As the pilot returned to the local airport, the airport tower controller informed him of a storm cell approaching the airfield, issued a clearance to land, and reported wind from 70 degrees left of runway heading at 25 knots gusting to 34 knots. The pilot estimated the wind at 18 knots of crosswind, and landed using 40 degrees of flaps. While on the landing roll, the wind shifted to a tailwind at which time the airplane began to drift to the right side of the runway. The pilot attempted to go-around, but could not regain control of the airplane. He then elected to abort the go-around and attempted to bring the airplane to a stop. The airplane departed the right side of the runway and continued into a field. The airplane encountered uneven terrain and the airplane nosed over. Substantial damage was sustained to the airplane's wings and vertical stabilizer. The pilot reported no preimpact malfunctions with the airplane. A review of air traffic control transmissions revealed the pilot was aware of alerts for low-level windshear and microbursts during this local flight. The airplane's pilot operating handbook directs pilots to utilize the minimum flap setting required for field length while operating in strong crosswind conditions. In addition, the handbook does not state a maximum allowable crosswind velocity, but states that average pilot technique should be able to handle 15 knots of crosswind. ## Factual narrative As the pilot returned to the local airport, the airport tower controller informed him of a storm cell approaching the airfield, issued a clearance to land, and reported winds from 70 degrees left of runway heading at 25 knots gusting to 34 knots. The pilot estimated the winds at 18 knots of crosswind, and landed using 40 degrees of flaps. While on landing roll, the airplane experienced a shift in winds to a tailwind at which time the airplane began to drift to the right side of the 150-foot wide runway. The pilot attempted to go-around, but could not regain control of the airplane. He then elected to abort the go-around and attempted to bring the airplane to a stop. The airplane departed the right side of the runway and continued into a field. The airplane encountered uneven terrain and the airplane nosed over. Substantial damage was sustained to the airplane's wings and vertical stabilizer. The pilot reported no preimpact malfunctions with the airplane. A review of Air Traffic Control transmissions revealed the pilot was aware of alerts for low-level windshear and microbursts during the his local flight. The airplane's pilot operating handbook directs pilots to utilize the minimum flap setting required for field length while operating in strong crosswinds. In addition, the handbook does not state a maximum allowable crosswind velocity, but states that average pilot technique should be able to handle 15 knots of crosswind. Winds at the times of the pilot's landing were between 23 knots and 32 knots of crosswind. ## Aircraft - Registration: [N3484E](https://openairdocs.org/deregistered/N3484E-2012-06-04), registration cancelled 2012-06-04, S/N 17271566, built 1978 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17271566 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Peak Aviation Center Inc - Registered owner: Peak Aviation Center Inc - Airworthiness certificate: Standard, Normal - Departed: KCOS, Colorado Springs, CO - Destination: KCOS, Colorado Springs, CO - Airport: KCOS, Colorado Springs Municipal, runway 35R, 13,501 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; medical: class 3; last flight review October 29, 2010; seat: left; flight hours: 86 total, 5 in this make and model, 31 as pilot in command, 0 in the last 90 days, 0 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 28 knots, gusting 39 - Visibility: 8 statute miles - Lowest ceiling: 6,000 ft broken - Temperature: 55 °F, dew point 34 °F - Altimeter: 29.55 inHg - Observed at: KCOS ## 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 20110403004839A](https://openairdocs.org/incident/20110403004839A), Apr 3, 2011: Cessna 172N, Colorado Spring, CO, Substantial damage. On 4/3/2011, aircraft N3484E, a CE-172N, piloted by ryan t nelson, pilot [privacy data omitted] sustained substantial damage. Pilot landed at kcos, on 35R.… ## Docket (2 files) The files NTSB released with the investigation on May 2, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78746. 1.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40346727&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Photo: Accident overview (item 2, .PDF, 395 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40347036&FileExtension=.PDF&FileName=Photo%3A%20Accident%20overview-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.