CEN09LA446 · Beech S35
Beech S35 · Accident: runway excursion during landing
From Pike County Airport Hatcher Field (PBX) to Tuscola Airport (K96)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN09LA446
- 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 S35
- Aircraft type
- Beechcraft 35
- 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
- N13W
- Operator
- David Hrupsa
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Pike County Airport Hatcher Field (PBX), Pikesville, KYTo Tuscola Airport (K96), Tuscola, IL
- 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
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot’s first attempt to land resulted in a go-around because he was too high and fast. During the second landing attempt, the airplane bounced and the pilot did another go-around. Witnesses reported that during the third landing attempt, the airplane touched down about mid-field with too much airspeed. The pilot applied the brakes, but the airplane went off the end of the runway. The pilot made a sharp left turn to avoid hitting a ditch head-on. The right main landing gear and nose gear collapsed, and the right wing came to rest on the road. The pilot reported that he took his hand off the throttle during the flare so that he could have both hands on the yoke. He reported that when he removed his hand from the throttle, it advanced about 200 rpm. An inspection of the airplane revealed that the throttle linkage was hitting the stops. The throttle control was examined and no discrepancies were noted.
Probable cause
The pilot failure to maintain proper speed and distance during approach to land which resulted in landing long and subsequent runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09LA446
- Event ID
- 20090720X03313
- Case number
- CEN09LA446
- 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: bbc6b10ce4548e7d840cf351b111f6c3440bf339dbada16a9beb28c899dc8e32; retrieved 2026-09-15T11:55:35.336Z.