ATL94LA177 · Cessna 172D
Cessna 172D · Accident: loss of engine power during takeoff
From 21A to 21A
Event
- NTSB case
- ATL94LA177
- 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 172D
- 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
- N2830U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 21ATo 21A
- 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 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
- Fuel contamination
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AS THE AIRPLANE CLIMBED THROUGH 100 FEET, THE PILOT WATCHED THE ENGINE RPM DROP FROM 2360 TO 1700. AFTER ATTEMPTS TO RESTORE FULL POWER FAILED, THE PILOT LOWERED FULL FLAPS AND ATTEMPTED A LANDING STRAIGHT AHEAD. THE NOSE WHEEL DUG INTO THE GROUND AND THE AIRPLANE FLIPPED INVERTED. DURING THE ENGINE EXAMINATION, WATER WAS DISCOVERED IN THE FUEL SYSTEM AND THE CARBURETOR. THE ENGINE OPERATED NORMALLY THROUGH ALL POWER RANGES DURING THE FUNCTIONAL CHECK. ACCORDING TO THE PILOT, THE POSITION OF THE AIRPLANE ON THE RAMP PREVENTED HIM FROM SUMPING THE FUEL SYSTEM PROPERLY.
Probable cause
THE PILOT'S FAILURE TO PROPERLY SUMP THE FUEL SYSTEM DURING THE PREFLIGHT INSPECTION THAT RESULTED IN LOSS OF POWER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL94LA177
- Event ID
- 20001206X02181
- Case number
- ATL94LA177
- 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: 307fadc53d44034107f9c28335d7afb4d0818079edaa30657cab99c482ce41da; retrieved 2026-09-23T00:36:16.605Z.