# NTSB ERA20CA102: Cessna 172, N1126U, Rochester, NY, February 16, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 16, 2020, 11:30 local (16:30 UTC) - Place: Rochester, NY - Coordinates: 43.119167, -77.671943 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=43.1192&lon=-77.6719&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 25, 2020 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA FSDO - NTSB case key (mKey): 100951 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA20CA102 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100951/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100951 - Page: https://openairdocs.org/ntsb/ERA20CA102 ## Probable cause The pilot's failure to maintain airplane control during a go-around. Contributing to the accident was the pilot’s decision to take off after perceiving a rudder issue during taxi operations. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172M, 10 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2072418), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/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 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172M, 36 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072418), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Aircraft inspection event](https://openairdocs.org/ntsb-events/050); cases with it: [Cessna 172M, 3 cases](https://openairdocs.org/ntsb-events/050/sequence.md?model=2072418), [All aircraft, 229 cases](https://openairdocs.org/ntsb-events/050/sequence.md) - [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172M, 47 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072418), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis The pilot reported that, during his preflight inspection, he noted several anomalies. He added that the right rudder pedal was not functioning properly before the flight during taxi; however, he decided to go ahead with the flight. After takeoff, he reconsidered the flight and returned to the airport. While on approach to landing, the airplane was hard to control, so he chose to troubleshoot the control issue in the air and initiated a go-around. The airplane lifted off the runway and began to climb but then rapidly rolled right and then left and then impacted terrain. In addition, the pilot stated he lost directional control due to a rudder anomaly during a flight in the airplane several weeks earlier. A Federal Aviation Administration inspector who examined the airplane reported that the wings had sustained substantial damage. Postaccident examination of the rudder control system revealed no evidence of any preaccident mechanical failures or malfunctions that would have precluded normal operation. ## Factual narrative The pilot reported that, while on approach to landing, the airplane was hard to control, so he elected to troubleshoot the control issue in the air and initiated a go-around. The airplane lifted off the runway and began a climb, but rapidly rolled to the right, then left and impacted terrain. The pilot further described that the right rudder pedal was not functioning properly prior to the flight during taxi and that he had difficulty maintaining directional control during the approach. In addition, the pilot stated he lost directional control due to a rudder anomaly during a flight in the airplane that occurred several weeks prior. A Federal Aviation Administrator inspector examined the airplane after the accident and confirmed that the airplane's wings had been substantially damaged during the accident. A postaccident examination of the rudder control system revealed no evidence of a pre accident mechanical failure or malfunction that would have precluded normal operation. ## Aircraft - Registration: [N1126U](https://openairdocs.org/deregistered/N1126U-2020-12-05), registration cancelled 2020-12-05, S/N 17266855, built 1976 (OpenAirDocs) - Reported make and model: Cessna 172 (M) - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17266855 - Year built: 1976 - Airframe hours: 14958 - Engines: Lycoming O-320 -E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Schubert Brothers Aviation Inc, doing business as Rochester Air Center - Registered owner: Schubert Brothers Aviation Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 14, 2020, 58 hours before - Departed: ROC, Rochester, NY - Destination: ROC, Rochester, NY - Airport: ROC, Greater Rochester Intl, runway 25, 4,000 × 100 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: none; private; airplane ratings: multi-engine land, single-engine land; medical: class 2, with waivers/limitations; last flight review January 14, 2020; seat: left; restraint: 3-point; flight hours: 3,307 total, 250 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: 1,500 ft overcast - Temperature: 36 °F, dew point 28 °F - Altimeter: 30.04 inHg - Observed at: ROC, 1 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 20200216004899A](https://openairdocs.org/incident/20200216004899A), Feb 16, 2020: Cessna 172M, Rochester, NY, Substantial damage. On the takeoff roll while conducting touch and go's, the aircraft drifted right of center line. The pilot attempted to correct the drift by lifting off. During… ## Other investigations on N1126U (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 LAX05LA199](https://openairdocs.org/ntsb/LAX05LA199), Jun 10, 2005: Cessna 172M (N1126U), Carlsbad, CA, minor damage. Probable cause: the other pilot's inadequate visual lookout and failure to maintain separation while taxiing. ## Docket (4 files) The files NTSB released with the investigation on May 28, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100951. 4.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483979&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot Logbook Excerpt (item 2, .PDF, 847 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483980&FileExtension=.PDF&FileName=Pilot%20Logbook%20Excerpt-Master.PDF - Maintenance Record Excerpt (item 3, .PDF, 530 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483981&FileExtension=.PDF&FileName=Maintenance%20Record%20Excerpt-Master.PDF - FAA Inspectors Examination Statements (item 4, .PDF, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40483982&FileExtension=.PDF&FileName=FAA%20Inspectors%20Examination%20Statements-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.