FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA331 · Cessna 172R

28 Apr 2011 · Fort Worth, TX, United States

Airline Transport Professionals Cessna 172R · Accident: loss of control in flight during landing

From Arlington Municipal Airport (GKY) to Fort Worth Spinks Airport (FWS)

Report a problem

Event

NTSB case
CEN11CA331
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 172R

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
N411ES
Onboard fatalities
Unknown
Route
From Arlington Municipal Airport (GKY), Arlington, TXTo Fort Worth Spinks Airport (FWS), Fort Worth, TX
Aircraft age
Not recorded
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
Landing · flare/touchdown
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
Loss of control in flight
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot was performing touch-and-go takeoffs and landings when the airplane touched down and bounced. During the attempted recovery, the airplane stalled, rolled left, and impacted the ground. According to the flight instructor, he attempted to take control of the airplane, but the student continued to pull back on the airplane's control yoke. The student pilot reported that when requested to relinquish the flight controls, he did so. The airplane's left wing and fuselage sustained substantial damage during the accident. The flight instructor reported that there were no mechanical malfunctions or failures with the airplane prior to the accident.

Probable cause

The student pilot's improper recovery from the bounced landing and the flight instructor's delayed remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA331
Event ID
20110511X93312
Case number
CEN11CA331
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: 7e4bc792157f7fb869e294a88e37977af73158425d4c8699531197eede658337; retrieved 2026-09-15T16:09:31.296Z.