FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA07FA137 · Beech A36

1 Sept 2007 · Elizabethton, TN, United States

Beech A36 · Accident: in flight collision with terrain/water en route

From Elizabethton Municipal Airport (0A9) to VJ1 · Abingdon, VA

Report a problem

Event

NTSB case
MIA07FA137
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
5 · 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
Visual 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
N326DK
Operator
Victor J. Osborne, Jr · private individual
Onboard fatalities
Unknown
Route
From Elizabethton Municipal Airport (0A9), Elizabethton, TNTo VJ1 · Abingdon, VA
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
En route · climb to cruise
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 terrain/water
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 › Clearance, inadequate
  • Pilot in command › In-flight planning/decision, poor

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The Beech A36 airplane was approximately 0.95 inch aft of the aft center of gravity (CG) limit at the start of the flight, which was destined for an airport approximately 20 nautical miles north-northeast of the departure airport. Mountainous terrain at an elevation of 4,321 feet mean sea level (msl) was noted between the departure and destination airports. The flight departed from runway 06, and by witness accounts the airplane became airborne 2/3 down the 4,529 foot-long runway, and was noted to be only 75 to 100 feet above ground level (agl) at a point approximately 1,500 feet past the departure end of the runway. Witnesses also reported the airplane was flying slow in a steep climb attitude with the landing gear retracted, and there was no unusual engine sounds heard. The flight continued on a northeasterly heading, where another witness located in mountainous terrain about 1 mile southwest of the crash site location noted the airplane flying only 2-3 times the height of the tree tops, or an estimated 200 to 250 feet agl. That witness reported the engine sounded like it was a larger engine, and he did not hear any missing or sputtering from it. The airplane impacted up sloping terrain during daylight hours at an elevation of 3,400 feet msl, approximately 5.38 miles northeast from the departure end of runway 06. There were no known witnesses to the crash. Impact and a postcrash fire destroyed the airplane. Examination of the airframe and flight controls revealed no evidence of preimpact failure or malfunction. Examination of the engine, engine systems, and propeller also revealed no evidence of preimpact failure or malfunction.

Probable cause

The poor in-flight planning by the pilot-in-command for flying towards rising terrain with inadequate clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA07FA137
Event ID
20070907X01326
Case number
MIA07FA137
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: f68a9c44ce1858c762c7df54aeefc2bb79788c7c7913b01b905f2088a9db85c9; retrieved 2026-09-20T16:19:25.279Z.