ERA21LA012 · Beech 23
Beech 23 · Accident: runway excursion during landing
From Gene Snyder Airport (K62) to an unrecorded destination
Event
- NTSB case
- ERA21LA012
- 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
- 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 23
- Aircraft type
- Beechcraft 23
- 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
- N8783M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gene Snyder Airport (K62), Falmouth, KYTo not recorded
- Aircraft age
- About 56 years (built 1964)
- 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 · flare/touchdown
- Defining eventThe 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
- Runway excursion
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before attempting to land on the 3,001-ft-long, asphalt runway, the pilot had been advised by personnel at the destination airport that landing toward the upsloping direction of the runway was preferred. The pilot did not check the wind direction prior to landing, and during the landing flare, the airplane did not slow down or descend. The pilot added full flaps, but the airplane continued to float and touched down with about 200 ft of remaining runway. Subsequently, the airplane overran the runway end, proceeded through the airport perimeter fence, traveled down an embankment, and came to rest on a road. The airplane sustained substantial damage to the fuselage. Following the accident, the pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and stated that he believed that a tailwind was likely present during the landing attempt.
Probable cause
The pilot's failure to familiarize himself with the wind conditions at the destination airport and his failure to attain the proper touchdown point during landing, which resulted in a long, tailwind landing and subsequent runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA012
- Event ID
- 20201009102119
- Case number
- ERA21LA012
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 71b8aeb05ab32ac48bd17e576aa588fdce20580081b578ae521d1c3f46c3cdf9; retrieved 2026-09-16T13:12:53.687Z.