FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL01LA111 · Cessna 172N

14 Sept 2001 · Sarasota, FL, United States

Cessna 172N · Accident: on ground/water encounter with weather while taxiing

From DeKalb Peachtree Airport (PDK) to Sarasota Bradenton International Airport (SRQ)

Report a problem

Event

NTSB case
ATL01LA111
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
Instrument Meteorological Cond

Cessna 172N

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
N19SC
Operator
Unknown
Onboard fatalities
Unknown
Route
From DeKalb Peachtree Airport (PDK), Atlanta, GATo Sarasota Bradenton International Airport (SRQ), Sarasota, 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
Taxi · from runway
First occurrenceThe 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
On ground/water encounter with weather
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

  • Pilot in command › In-flight planning/decision, improper

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

NTSB narrative

After landing on runway 32 and taxiing clear of the runway, the airplane nosed over inverted during gusty, high winds.The airplane was positioned on a taxiway oriented 040 degrees magnetic when the event occurred. Winds were reported from 320 degrees magnetic at 34 knots gusting to 46 knots at 0932. The maximum demonstrated crosswind velocity for the airplane, according to its Information Manual, is 15 knots. Examination of the airplane revealed damage to the propeller, wings, and wing struts.

Probable cause

The pilot's improper in-flight decision to land at an airport with high wind conditions, which resulted in a loss of control on the ground during taxi operations and subsequent nose over of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL01LA111
Event ID
20010920X01971
Case number
ATL01LA111
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 3936757f94708e32fa167470ba79d22a1ccc00b70ee0e3822f5cc90fb979e38e; retrieved 2026-09-22T11:34:16.991Z.