FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10FA471 · Cessna 182T

8 Sept 2010 · Helena, GA, United States

Air Dandy Cessna 182T · Accident: controlled flight into terrain/object (CFIT) on approach

From West Georgia Regional Airport / O V Gray Field (CTJ) to Telfair Wheeler Airport (MQW)

Report a problem

Event

NTSB case
ERA10FA471
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
1 · 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
Instrument Meteorological Cond

Cessna 182T

Aircraft type
Cessna 182
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
N804GK
Operator
Air Dandy
Onboard fatalities
Unknown
Route
From West Georgia Regional Airport / O V Gray Field (CTJ), Carrollton, GATo Telfair Wheeler Airport (MQW), McRae, GA
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 · IFR final approach
Defining eventThe 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
Controlled flight into terrain/object (CFIT)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot was en route to an airport that did not have a control tower or weather reporting facilities. He checked weather at surrounding airports and informed the air traffic controller that he would need to fly the global positioning system (GPS) approach. Once cleared for the approach, no subsequent communication was received from the pilot. Radar data showed that the airplane intercepted the final approach segment and descended without leveling off at the minimum descent altitude. The airplane impacted trees and terrain about 2.74 miles from the runway, on a heading and course that were aligned with the runway. Although a pilot-rated passenger survived, he had no recollection of the accident flight. Witnesses reported that it was foggy at the time of the accident. Weather at nearby airports indicated that low ceilings and visibilities were prevalent in the area, with the weather gradually improving at the time of the accident. An examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures. Postmortem toxicology testing on the fatally injured pilot noted elevated glucose levels in the vitreous fluid and urine, and an elevated hemoglobin A1c level in the blood, indicating that the pilot was likely diabetic with poorly-controlled blood sugar. While the investigation was unable to determine that the pilot was impaired, he had recently eaten and his blood sugar may have been high enough to impair his cognitive performance. Though there were no indications that the pilot was aware of his diabetes, a Federal Aviation Administration medical examination nearly 4 years before the accident had noted elevated urine and blood sugar without any additional follow-up required.

Probable cause

The pilot’s continuance of the GPS approach below the minimum descent altitude while landing in instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10FA471
Event ID
20100908X05150
Case number
ERA10FA471
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: a134d97915bf08c69326483232030529c3b3bf6d1ce6989504671c516b3bcc73; retrieved 2026-09-13T21:03:05.585Z.