FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04FA045 · Beech B200

4 Dec 2003 · Morlan, GA, United States

Southeastern Air Charter Beech B200 · Accident: in flight collision with object on approach

From Douglas Municipal Gene Chambers Airport (DQH) to Newnan Coweta County Airport (CCO)

Report a problem

Event

NTSB case
ATL04FA045
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
2 · 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

Beech B200

Aircraft type
Beechcraft 200
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
N85BK
Onboard fatalities
Unknown
Route
From Douglas Municipal Gene Chambers Airport (DQH), Douglas, GATo Newnan Coweta County Airport (CCO), Newnan, 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
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 collision with object
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
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Decision height, continued below
  • Pilot in command › In-flight planning/decision, inadequate

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

NTSB narrative

Upon arriving at the destination airport, the controller cleared the flight for localizer 32 approach and informed the pilot that radar service was terminated and a frequency change was approved, report canceling IFR this frequency. The pilot acknowledged the clearance. A review of radar data revealed that the airplane was on course and lined up with the runway when the airplane collided with trees and the ground one mile south of runway 32. A review of information on file with Southeastern Air Charter, Inc., the operator of the accident airplane, found that the pilot's most recent Airman Competency/Proficiency Check was conducted in a Cessna 210. There were no records to indicate the pilot had under gone a flight-check in the Beech 200, as outlined in the Corporations FAA Approved Operational Specifications. Examination of the airframe and engines found no pre-existing discrepancies that would have precluded the airplane from operating properly prior to impact. Surface Weather Observations reported near the time of the accident. was visibility 1 to 1¼ miles; ceiling 200 feet overcast. A review of the approach plate found the minimum descent altitude for the approach to be 325 AGL and visibility 1 mile.

Probable cause

The pilot's inadequate in-flight planning/decision when he continued the flight below the decision height and collided with trees. A related factor was the low ceiling.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04FA045
Event ID
20031209X02012
Case number
ATL04FA045
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 2003-12-05.
  • API snapshot SHA-256: 19097a24e787a29c36994456dc69c98d5ab74ec8ace05b44e91c3b883ff87957; retrieved 2026-09-20T18:44:45.554Z.