ATL83FKG10 · Cessna 177
Cessna 177 · Accident: total loss of engine power (non-mechanical) during initial climb
From 3J7 · Greensboro, GA to an unrecorded destination
Event
- NTSB case
- ATL83FKG10
- 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 177
- Aircraft type
- Cessna 177
- 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
- N3493T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3J7 · Greensboro, GATo not recorded
- 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
- Initial climb
- 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
- Total loss of engine power (non-mechanical)
- 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 exhaustion; 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
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Fuel supply, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT-IN-COMMAND REPORTED THAT THE ACFT WAS VERY LOW ON FUEL & HE HAD 10 GALLONS ADDED TO EACH WING TANK BEFORE DEPARTING MADISON, GA. FROM MADISON, HE FLEW TO GREENSBORO, GA FOR SALES DEMONSTRTION FLTS. DURING THE 1ST DEMONSTRATION FLT, THE ACFT PERFORMED WELL, EXCEPT THE CARBURETOR HEAT CONTROL BECAME JAMMED AT THE 'ON' POSITION DURING THE LANDING. THE CARBURETOR HEAT CONTROL WAS FINALLY MOVED TO THE 'OFF' POSITION & A 2ND DEMONSTRATION FLT WAS BEGUN. DURING TAKEOFF ON THE 2ND FLT, THE ENG LOST POWER AT APRX 100 TO 150 FT AGL. SUBSEQUENTLY, THE ACFT HIT TREES DURING AN EMERGENCY LANDING. DURING AN INVESTIGATION, VIRTUALLY NO FUEL WAS FOUND IN THE ENG DRIVEN FUEL PUMP, CARBURETOR, ELECTRIC BOOST PUMP, MAIN FUEL STRAINER, FUSELAGE HEADER TANK OR ASSOCIATED LINES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FKG10
- Event ID
- 20001214X43591
- Case number
- ATL83FKG10
- 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: 7b18b0e4dcb46813510a2a308a419d9b2e4f59a0c997ab020513b43ea61c7081; retrieved 2026-09-21T17:52:12.513Z.