# NTSB ERA20CA130: Cessna 172, N66046, West Palm Beach, FL, March 17, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 17, 2020, 15:35 local (19:35 UTC) - Place: West Palm Beach, FL - Coordinates: 26.593055, -80.084999 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.5931&lon=-80.0850&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 27, 2020 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 101084 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA20CA130 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101084/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101084 - Page: https://openairdocs.org/ntsb/ERA20CA130 ## Probable cause The failure of the nosewheel steerage linkage during takeoff, which resulted in a loss of directional control and impact with an obstacle during an attempted aborted landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Landing gear system: landing gear steering system](https://openairdocs.org/ntsb-findings/01023250): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01023250/cases.md?model=2072439), [All aircraft, 32 cases](https://openairdocs.org/ntsb-findings/01023250/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (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) - [Object/animal/substance](https://openairdocs.org/ntsb-findings/03022000): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-findings/03022000/cases.md?model=2072439), [All aircraft, 224 cases](https://openairdocs.org/ntsb-findings/03022000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Cessna 172S, 4 cases](https://openairdocs.org/ntsb-events/330/sequence.md?model=2072439), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md) - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230); 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) - [Takeoff: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172S, 22 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072439), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Takeoff-rejected takeoff: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Takeoff-rejected takeoff: 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 flight instructor, after a normal preflight inspection and engine run-up, the student pilot taxied to the runway for takeoff and began the takeoff roll. Everything seemed normal as the airplane accelerated; however, as the airplane rotated, it started to yaw left. The instructor attempted to assist the student correct the left yaw by applying right rudder. He was unable to correct the left yaw, so he took over the flight controls and aborted the takeoff. The airplane bounced to the left and impacted a retention pond bank. A Federal Aviation Administration inspector who examined the airplane reported that the forward fuselage and firewall were buckled, that the nosewheel steerage linkage was broken, and that rust was noted on the fractured surfaces. ## Factual narrative According to the flight instructor, after a normal pre-flight inspection of the airplane and engine run-up, the student pilot taxied to the runway for takeoff and began the takeoff roll. Everything seemed normal as the airplane accelerated; however, as the airplane rotated it started to yaw abnormally to the left. The flight instructor attempted to overcome the left yaw by pressing on the right rudder to assist the student pilot. He was unable to overcome the left yaw, took over the flight controls and aborted the takeoff. The airplane bounced to the left and collided with the bank of a retention pond.Examination of the airplane by a Federal Aviation Administration inspector revealed that the forward fuselage and firewall was buckled. Further examination revealed that the nose gear steering tube rod end failed and rust was noted on the threaded area of the fractured surfaces. ## Aircraft - Registration: [N66046](https://openairdocs.org/aircraft/N66046), registered now, S/N 172S9786, built 2005 (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: 172S9786 - Year built: 2005 - Airframe hours: 11025.8 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, February 16, 2020, 84 hours before - Departed: LNA, West Palm Beach, FL - Destination: LNA, West Palm Beach, FL - Airport: LNA, Palm Beach County Park, runway 10, 3,489 × 75 ft, asphalt - Equipment: ADS-B, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 32; injuries: none; commercial, flight instructor; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review December 11, 2019; seat: right; restraint: 3-point; flight hours: 318 total, 318 in this make and model, 249 as pilot in command, 81 in the last 90 days, 68 in the last 30 days, 2 in the last 24 hours - Student pilot; age 59; injuries: none; student; medical: class 3, with waivers/limitations; seat: right; restraint: 3-point; flight hours: 55 total, 55 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 70° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 64 °F - Altimeter: 30.19 inHg - Observed at: KPB, 5 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 20200317010219A](https://openairdocs.org/incident/20200317010219A), Mar 17, 2020: Cessna 172S, West Palm Beach, FL, Substantial damage. Student pilot, [privacy data omitted] and CFI [privacy data omitted], reported aircraft pulled to the left on takeoff roll. Aircraft ran off of the end of the… ## Docket (5 files) The files NTSB released with the investigation on July 24, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101084. 5.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485566&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot and Student statements (item 2, .PDF, 941 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485567&FileExtension=.PDF&FileName=Pilot%20and%20Student%20statements-Master.PDF - Memorandum Of Record FAA telephone correspondence (item 3, .PDF, 108 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485568&FileExtension=.PDF&FileName=Memorandum%20Of%20Record%20FAA%20telephone%20correspondence-Master.PDF - Maintenance Records (item 4, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485569&FileExtension=.PDF&FileName=Maintenance%20Records-Master.PDF - Photo Array (item 5, .PDF, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40485570&FileExtension=.PDF&FileName=Photo%20Array-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.