ATL92LA072 · Cessna U206G
Buckner Aviation Cessna U206G · Accident: total loss of engine power (mechanical failure) en route
From Middle Georgia Regional Airport (MCN) to Bowling Green Warren County Regional Airport (BWG)
Event
- NTSB case
- ATL92LA072
- 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 U206G
- Aircraft type
- Cessna 206
- 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
- N9679G
- Operator
- Buckner Aviation
- Onboard fatalities
- Unknown
- Route
- From Middle Georgia Regional Airport (MCN), Macon, GATo Bowling Green Warren County Regional Airport (BWG), Bowling Green, KY
- 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 · descent
- 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 (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
- Fluid, oil › Starvation
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD RENTED THE AIRPLANE FOR SEVERAL DAYS. DURING THE ACCIDENT FLIGHT, WHILE DESCENDING TO LAND, THE ENGINE OVERSPED. IT WAS CONTROLLED BY REDUCING THE THROTTLE. SHORTLY AFTERWARDS SMOKE WAS NOTED OUTSIDE OF THE AIRPLANE AND IN THE CABIN. THE ENGINE THEN QUIT. A FORCED LANDING WAS MADE TO ROUGH TERRAIN WHICH RESULTED IN SUBSTANTIAL DAMAGE. ENGINE DISASSEMBLY REVEALED DAMAGE CONSISTENT WITH OIL STARVATION. 1.5 QTS OF THE NORMAL 13 QTS OF OIL WERE DRAINED FROM THE ENGINE. NO OIL WAS FOUND ON THE ENGINE NOR THE FUSELAGE, EXTERNALLY. DURING THE NINE DAYS AND 22 HOURS THE AIRPLANE WAS RENTED BY THE PILOT, THERE WAS NO EVIDENCE THAT ANY OIL WAS ADDED TO THE ENGINE.
Probable cause
THE PILOT'S INADEQUATE PREFLIGHT INSPECTIONS WHICH RESULTED IN OIL STARVATION AND EVENTUAL FAILURE OF THE ENGINE. A FACTOR WAS THE ROUGH TERRAIN WHERE THE AIRPLANE WAS FORCE LANDED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92LA072
- Event ID
- 20001211X14227
- Case number
- ATL92LA072
- 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: 0de00c3a06021df1e3ba16f51b14caa6392afbc565dfac40e13f060917a2fa1c; retrieved 2026-09-23T03:16:40.251Z.