ATL96LA109 · Beech 58P
Beech 58P · Accident: overrun during landing
From Raleigh Regional Airport at Person County (TDF) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL96LA109
- 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
- Visual Meteorological Cond
Beech 58P
- 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
- N6461U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Raleigh Regional Airport at Person County (TDF), Roxboro, NCTo not recorded
- 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
- Landing · landing roll
- 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
- Overrun
- 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 › Distance/speed, misjudged
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Upon arriving in the Banner Elk Airport area, the pilot established a traffic pattern for runway 12. He stated that, due to the high terrain features around the airport, runway 12 was the preferred runway for landings. The airplane touched down about 1,000 feet beyond the approach end of the 4,600 foot long runway. As the airplane rolled toward the end of the runway, the pilot applied heavy braking that resulted in a blown main landing gear tire. The airplane rolled off the departure end of the runway and down an embankment, and collided with a tree. No mechanical problems were reported with the airplane by the pilot.
Probable cause
the pilot's misjudgment of distance and speed during the approach to land, and his failure to attain the proper touchdown point on the runway for the landing, which resulted in an overrun and collision with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL96LA109
- Event ID
- 20001208X06157
- Case number
- ATL96LA109
- 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: bafbfda6d58150a5205dd2842c1852848078812a892975f4d0b02c741b5a5e46; retrieved 2026-09-22T21:47:38.489Z.