ATL93FA059 · Cessna 172G
Cessna 172G · Accident: loss of control in flight during takeoff
From HIA Airport (03GA) to Tuscaloosa National Airport (TCL)
Event
- NTSB case
- ATL93FA059
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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 172G
- 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
- N5972R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From HIA Airport (03GA)To Tuscaloosa National Airport (TCL), Tuscaloosa, AL
- 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
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Compensation for wind conditions, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT WAS DEPARTING RUNWAY 10, WHICH WAS DOWNWIND, AT THE PRIVATE SOD AIRFIELD. THE WINDS AT THE TIME WERE FROM 230 DEGREES AT 14 KNOTS GUSTING TO 27 KNOTS. THE RUNWAY AT THE AIRFIELD CROSSES A STEEP HILL AT ABOUT THE MIDPOINT OF THE RUNWAY. THERE WERE TREES, APPROXIMATELY 100 FEET IN HEIGHT, LINING BOTH SIDES OF THE RUNWAY. WITNESSES STATED THAT, DURING THE TAKEOFF ROLL, THE AIRCRAFT WAS OBSERVED TO HAVE THE FLAPS IN THE EXTENDED POSITION. THE AIRCRAFT WRECKAGE WAS LOCATED ON THE NORTH SIDE OF THE DEPARTURE END OF THE RUNWAY. THE AIRCRAFT IMPACTED THE TERRAIN IN A NOSE DOWN, LEFT WING LOW ATTITUDE. THE AIRCRAFT FLAPS WERE FOUND TO BE IN THE RETRACTED POSITION.
Probable cause
The pilots inadequate preflight planning and his failure to properly compensate for the wind. A factor was the unfavorable wind condition at the time of take off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93FA059
- Event ID
- 20001211X11906
- Case number
- ATL93FA059
- 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: e2323789359f35a4d6f34ebdfdc29f6ac5e658534380f93c5db495301bd8055e; retrieved 2026-09-21T00:40:14.437Z.