FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04FA093 · Cessna 182S

12 Apr 2004 · North Augusta, SC, United States

Cessna 182S · Accident: in flight encounter with weather on approach

From Aiken Regional Airport (KAIK) to Mid Delta Regional Airport (KGLH)

Report a problem

Event

NTSB case
ATL04FA093
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
3 · 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 182S

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
N364ME
Operator
Unknown
Onboard fatalities
Unknown
Route
From Aiken Regional Airport (KAIK), Aiken, SCTo Mid Delta Regional Airport (KGLH), Greenville, MS
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
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
In flight encounter with weather
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
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
Substantial

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight departed on an IFR flight plan, did not proceed on its northwest course as directed, and did not maintain a consistent heading or altitude. The flight continued in a southwest direction, and the pilot elected to land the airplane. An air traffic controller provided altitude and heading assignments for a surveillance approach, and the pilot did not maintain the assigned headings and altitudes. The controller stated to the pilot the low altitude alert indicated 600 feet, and he instructed the pilot to climb. A witness on the ground saw the airplane flying erratically beneath the clouds at treetop height, then it dipped right then left and nosed down into trees and the ground. Examination of the airframe, engine, and components revealed no evidence of mechanical malfunction. A review of the pilot's log book revealed he logged 13.9 hours actual instrument time and 102.4 hours simulated instrument time. A witness at the departure airport stated the pilot checked the weather, and he overheard the pilot "talking about flying south to avoid rain, and then heading west from there." A review of WSR-88D Doppler Weather Radar Level III images revealed an area of precipitation was approximately 10 miles west of the departure airport and extended approximately 20 miles from north to south; the location of the accident site corresponded with the southeast edge of the precipitation area. An instrument-rated pilot who was monitoring the air traffic control frequencies as the accident flight was being vectored for the approach at Augusta Regional at Bush Field stated he heard the pilot state on the radio he was trying to fly through holes in the clouds.

Probable cause

The pilot's failure to maintain control of the airplane due to spatial disorientation, which resulted in an uncontrolled descent and subsequent in-flight collision with trees and the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04FA093
Event ID
20040415X00468
Case number
ATL04FA093
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, 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: 7aee9fe7c60e066f0f14c3a043c683f469ebc34241a981a5097efb4f4d12e7ef; retrieved 2026-09-20T18:30:15.987Z.