ATL07LA092 · Cessna 172
Cessna 172 · Accident: partial loss of engine power (mechanical failure) on approach
From Brinson, GA (no airport) to Brinson, GA (no airport)
Event
- NTSB case
- ATL07LA092
- 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
- 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
- N921JR
- Operator
- Roger M. Braswell · private individual
- Onboard fatalities
- Unknown
- Route
- From Brinson, GA (no airport)To Brinson, GA (no airport)
- 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
- Approach · VFR pattern final
- 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
- Partial loss of engine power (mechanical failure)
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, about 2 to 3 miles north of the runway, the engine started "sputtering," and experienced a partial loss of power. He made it back to the 2,000-foot-long turf runway, but touched down too fast and overran the runway. The pilot then pulled up to clear an embankment, the airplane stalled about 30 feet above the ground, and impacted a field nose down. Examination of the carburetor revealed that corrosion was present in and around the air and fuel jets, blocking fuel flow through the carburetor jet. Further examination found a large amount of corrosion around the carburetor's drain plug. The airplane's most recent annual inspection was completed 1 month prior to the accident; however, disassembly inspection of the carburetor was not required during an annual inspection.
Probable cause
A partial loss of engine power due to a blocked carburetor jet.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07LA092
- Event ID
- 20070622X00777
- Case number
- ATL07LA092
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-06-19.
- API snapshot SHA-256: b5a4b64f91dd57856dea41d852dfb814e2557daba37df97cc5cd8a5b9600a8d9; retrieved 2026-09-22T03:44:25.527Z.