ATL93LA019 · Beech 58
Kilo Hotel Beech 58 · Accident: in flight collision with object on approach
From Hartsfield Jackson Atlanta International Airport (ATL) to Everett-Stewart Regional Airport (UCY)
Event
- NTSB case
- ATL93LA019
- 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
- Instrument Meteorological Cond
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N101KH
- Operator
- Kilo Hotel
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Everett-Stewart Regional Airport (UCY), Union City, TN
- 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
- 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
- Substantial
Cause areas
- Pilot in command › IFR procedure, not followed
- Pilot in command › Minimum descent altitude, below
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT RECEIVED A WEATHER BRIEFING AND FILED AN INSTRUMENT FLIGHT PLAN TO THE DESTINATION AIRPORT WITHOUT LISTING AN ALTERNATE AIRPORT. UPON ARRIVING AT HIS PLANNED DESTINATION, HE EXECUTED TWO INSTRUMENT APPROACHES AND WAS UNABLE TO ESTABLISH VISUAL CONTACT WITH THE GROUND. HE REQUESTED A THIRD APPROACH FROM AIR TRAFFIC CONTROL AND COLLIDED WITH TREES ABOUT THREE MILES SHORT OF THE AIRPORT WHILE ON FINAL APPROACH. EXAMINATION OF THE AIRPLANE FAILED TO DISCLOSE A MECHANICAL MALFUNCTION OR A COMPONENT FAILURE. ACCORDING TO THE PUBLISHED APPROACH PROCEDURE THE MINIMUM DESCENT ALTITUDE IS 800 FEET MSL; THE PILOT DESCENDED BELOW THE PUBLISHED MINIMUMS. THE PILOT DID NOT REPORT A PROBLEM WITH THE AIRPLANE OR THE ONBOARD FLIGHT INSTRUMENTS.
Probable cause
THE PILOT'S FAILURE TO FOLLOW INSTRUMENT PROCEDURES WHILE CONDUCTING AN INSTRUMENT APPROACH WHICH RESULTED IN THE COLLISION WITH TREES; THE PILOT DESCENDED BELOW THE MINIMUM DESCENT ALTITUDE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA019
- Event ID
- 20001211X15820
- Case number
- ATL93LA019
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-10-31.
- API snapshot SHA-256: 89097cbfd2666d2e798ded057cc296e66c7564ab7a9b91ca3117831f2e104c7a; retrieved 2026-09-21T14:39:48.562Z.