ERA11CA096 · Cessna 172S
Sundowners Cessna 172S · Accident: runway excursion during takeoff
From Page Field (FMY) to Page Field (FMY)
Event
- NTSB case
- ERA11CA096
- 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 172S
- 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
- N385ME
- Operator
- Sundowners
- Onboard fatalities
- Unknown
- Route
- From Page Field (FMY), Fort Myers, FLTo Page Field (FMY), Fort Myers, 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
- Runway excursion
- 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
According to the pilot, he was practicing touch-and-go takeoffs and landings. During the takeoff roll following his eighth landing, he said he felt a gust of wind push the plane to the left. He applied full right aileron, but could not arrest the turn. He then applied the brakes, but the airplane departed the left side of the runway, impacted a ditch, and came to rest inverted, resulting in substantial damage to the firewall, wings, and vertical stabilizer. During a subsequent examination of the wreckage, a Federal Aviation Administration inspector found the flaps in the FULL, 30-degree position. The inspector also reported that there were no anomalies with the airplane. The reported wind at the airport about the time of the accident was from 350 degrees at 7 knots.
Probable cause
The pilot's failure to maintain directional control during the takeoff roll. Contributing to the accident was the pilot’s attempt to take off with full flaps.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA096
- Event ID
- 20101227X21121
- Case number
- ERA11CA096
- 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: 6dc96ff6492836acde65756bfe363e14c553affb2c11d8eabb2837ae4a4d8cbf; retrieved 2026-09-15T15:38:48.909Z.