FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12CA330 · Cessna 172R

11 May 2012 · Immokalee, FL, United States

Cessna 172R · Accident: loss of control on ground during takeoff

From Immokalee Regional Airport (IMM) to Immokalee Regional Airport (IMM)

Report a problem

Event

NTSB case
ERA12CA330
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
N5253B
Operator
Atp USA
Onboard fatalities
Unknown
Route
From Immokalee Regional Airport (IMM), Immokalee, FLTo Immokalee Regional Airport (IMM), Immokalee, FL
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
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
Loss of control on ground
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
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot demonstrated three successful touch-and-go landings. After the third touch-and-go landing, the flight instructor deplaned, and the student pilot successfully performed eight solo touch-and-go landings on the same runway. The student pilot reported that while he was on final approach for the ninth solo touch-and-go landing, he heard the pilot of a helicopter announce the intention to fly over the landing runway. The student pilot announced that he had the helicopter in sight and advised of his intention to perform a touch-and-go landing on the runway. The student pilot landed and said he then applied full throttle before retracting the flaps. The airplane started to drift to the left and the right wing lifted, so the student pilot reduced the power to idle and applied aft control yoke then waited for the airplane to come to rest. The flight instructor reported seeing the helicopter fly over the airplane while it was on the runway during the landing roll. The flight instructor also noted that the student pilot had not retracted the flaps and saw the airplane veer sharply to the left and then cart wheel, coming to rest upright. The operator reported there was no evidence of preimpact failure or malfunction of the airplane. Postaccident inspection of the airplane revealed damage to the firewall.

Probable cause

The student pilot’s failure to maintain directional control during a touch-and-go landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12CA330
Event ID
20120511X43758
Case number
ERA12CA330
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: 4f28e1fa13c68f4b61f6f1c539ac08f5663df5abba4aad4af3408e658cb88399; retrieved 2026-09-15T18:03:25.371Z.