ATL93LA063 · Beech 58
Vca Beech 58 · Accident: overrun during landing
From Smith Reynolds Airport (INT) to Tri-Cities Regional TN/VA Airport (TRI)
Event
- NTSB case
- ATL93LA063
- 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 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
- N8555R
- Operator
- Vca
- Onboard fatalities
- Unknown
- Route
- From Smith Reynolds Airport (INT), Winston-Salem, NCTo Tri-Cities Regional TN/VA Airport (TRI)
- 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 › Operation with known deficiencies in equipment, intentional
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT DURING THE ENGINE RUN UP PRIOR TO THE FLIGHT, THE AIRCRAFT BRAKES WOULD NOT HOLD THE AIRCRAFT FROM ROLLING. HE STATED THAT DURING THE VISUAL APPROACH, THE SUN BLINDED HIM MOMENTARILY AND HE LOST SIGHT OF THE RUNWAY. WHEN HE REGAINED SIGHT OF THE RUNWAY, HE WAS HIGH AND FAST FOR THE LANDING. HE ELECTED TO ATTEMPT TO LAND THE AIRCRAFT BEYOND THE NORMAL TOUCHDOWN POINT AND THE AIRCRAFT RAN OFF THE END OF THE RUNWAY.
Probable cause
THE INTENTIONAL OPERATION OF THE AIRCRAFT WITH A PARTIAL FAILURE OF THE BRAKE SYSTEM AND THE FAILURE OF THE PILOT TO ATTAIN THE PROPER TOUCHDOWN POINT. FACTORS IN THE ACCIDENT WERE THE SUNGLARE AND THE PARTIAL LOSS OF THE AIRCRAFT BRAKE SYSTEM.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA063
- Event ID
- 20001211X11909
- Case number
- ATL93LA063
- 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: 26cbdbfd17ecd9344039ef6653b3ec7a65d3282fc0273536b88ed9b846d5d5ba; retrieved 2026-09-23T02:14:10.384Z.