ATL99LA059 · Cessna 172
Cessna 172 · Accident: loss of engine power en route
From Florala Municipal Airport (0J4) to Peter Prince Field (2R4)
Event
- NTSB case
- ATL99LA059
- 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
- 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 172
- 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
- N8968B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florala Municipal Airport (0J4), ALTo Peter Prince Field (2R4), Milton, 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
- En route · climb to cruise
- 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 engine power
- 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
- Fuel system, tank › Contamination, water
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane had been parked on the ramp for several days, and it had rained the day before the accident. During the preflight inspection the pilot stated he had taken fuel samples from both fuel tanks and found no water or other contamination. After the preflight examination, the flight departed on runway 04. The pilot turned downwind, and had started a turn to left base when the engine lost power and sputtered. The pilot activated the carburetor heat and switched fuel tanks before returning the fuel selector to both. The engine continued to sputter. While attempting to return to runway 04, the airplane collided with trees approximately 50 feet south of the airport. Examination of the airplane disclosed the presence of water in the fuel tanks.
Probable cause
THE PILOT'S INADEQUATE PREFLIGHT INSPECTION, WHICH RESULTED IN A LOSS OF ENGINE POWER DUE TO FUEL SYSTEM CONTAMINATION WITH WATER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA059
- Event ID
- 20001205X00263
- Case number
- ATL99LA059
- 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: da0f91099178183d8165e05da3f908e0e3722e6ffb50f9c3478edb128909d9f1; retrieved 2026-09-21T20:34:52.796Z.