FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA154 · Cessna 172 M

22 Apr 2020 · Ft Worth, TX, United States

Cessna 172 M · Accident on approach

From Parker County Airport (WEA) to Parker County Airport (WEA)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN20CA154
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 M

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
N13005
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Parker County Airport (WEA), Fort Worth, TXTo Parker County Airport (WEA), Fort Worth, TX
Aircraft age
About 47 years (built 1973)
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
Approach · VFR pattern final
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
Miscellaneous/other
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
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that he and the student pilot were prepared to land on runway 14 with partial flaps and reported wind from 190° at 17 knots. When they turned onto final approach, the instructor noticed that the airplane was too high and not aligned with the runway and that the airspeed was high. As the airplane approached the touchdown point, it encountered turbulence. The instructor took control of the airplane and executed a right-wing-low partial slip. The airplane touched down halfway down the 3,740-ft-long runway with a high ground speed. The instructor applied the brakes, and the wheels immediately locked, so he released the brakes and then tried reapplying them; however, the airplane did not decelerate. The airplane overran the runway and struck several airport lights and then traveled through two barbed-wire fences. The right main landing gear separated, the left main landing gear collapsed, and the fuselage and horizontal stabilizer sustained substantial damage. After the instructor and student exited the airplane, they noticed that the windsock indicated that they had landed with a strong quartering tailwind. The instructor said that the accident was due to the "undetected shift in wind direction - from a quartering headwind to a quartering/direct tailwind" and he and the student's incorrect decision to continue the approach and landing when the airplane was not stabilized.

Probable cause

The student pilot’s failure to maintain a stabilized approach and the flight instructor's delayed remedial action to initiate a go-around, which resulted in a runway overrun and impact with runway lights and fences.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA154
Event ID
20200423X91852
Case number
CEN20CA154
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: c2181f916abcf00e2286061dd32c7a59d73dcd9e5aff76b03800f87c6262f124; retrieved 2026-09-16T11:30:45.124Z.