ERA13CA315 · Beech A23-19
Beech A23-19 · Accident: runway excursion during landing
From Braden Airpark (N43) to Braden Airpark (N43)
Event
- NTSB case
- ERA13CA315
- 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 A23-19
- 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
- N4785J
- Operator
- Aliosman Bilukbash
- Onboard fatalities
- Unknown
- Route
- From Braden Airpark (N43), Easton, PATo Braden Airpark (N43), Easton, PA
- Aircraft age
- About 46 years (built 1967)
- 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
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he had not flown for over two years prior to the accident flight. On the day of the accident, he took off and made two uneventful landings to runway 18. He then departed runway 36 and entered the airpark traffic pattern. The pilot reported his turn to final approach placed the airplane in position to land long and fast. He landed long on runway 36 and was unable to stop before the airplane departed the left side of the runway. The airplane dropped six feet down a steep embankment, crossed a road, and came to rest about 70 feet past the departure end of runway 36. Postaccident examination by a Federal Aviation Administration inspector revealed substantial damage to the right wing spar. At the time of the accident, the wind in the area was reported from 210 degrees at 12 knots, gusting to 17 knots. The pilot reported no preaccident mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot's improper touchdown point during landing, which resulted in a runway overrun. Contributing to the accident was the pilot’s decision to land with a tailwind condition and his lack of recent experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA315
- Event ID
- 20130708X51520
- Case number
- ERA13CA315
- 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. 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: 16374173b245fae34e339b52f780ec9ccc7d34c262cd681be49f074257d67254; retrieved 2026-09-15T22:08:31.669Z.