ERA20CA130 · Cessna 172 S
Cessna 172 S · Accident: system/component malfunction/failure (non-power) during takeoff
From Palm Beach County Park Airport (LNA) to Palm Beach County Park Airport (LNA)
Event
- NTSB case
- ERA20CA130
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172 S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N66046
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Palm Beach County Park Airport (LNA), West Palm Beach, FLTo Palm Beach County Park Airport (LNA), West Palm Beach, FL
- Aircraft age
- About 15 years (built 2005)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA130
- Event ID
- 20200317X62852
- Case number
- ERA20CA130
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 07f10a7ec20523765fc9b7ad455f65c4b68ffedce7c9854fa21e0fd9a0d58a4b; retrieved 2026-09-16T11:19:14.754Z.