ATL00LA074 · Beech A36
Beech A36 · Accident: in flight collision with object on approach
From DeKalb Peachtree Airport (PDK) to Clarksville–Montgomery County Regional Airport (CKV)
Event
- NTSB case
- ATL00LA074
- 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 A36
- Aircraft type
- Beechcraft 36
- 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
- N86BC
- Operator
- David A. Ordner · private individual
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Chamblee, GATo Clarksville–Montgomery County Regional Airport (CKV)
- 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 missed 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane collided with a tree during a climb-out from a missed approach. The pilot declared an emergency, and the controller provided the pilot with vectors to another airport 4.4 nautical miles southwest; however, prior to reaching the second airport, the airplane's engine lost power. The airplane collided with the ground and nosed over during an off-airport forced landing.
Probable cause
The pilot's failure to follow published instrument approach procedures, and collided with a tree while executing a missed approach. Factors were low clouds, fog and a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL00LA074
- Event ID
- 20001212X21648
- Case number
- ATL00LA074
- 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: ddf2949269f3769a8f3b014c39c38b430697f94f2cc3f0a2df3abce147ee18c3; retrieved 2026-09-21T10:31:49.261Z.