CEN13CA489 · Beech 58P
Beech 58P · Accident: landing area overshoot
From Owensboro Daviess County Airport (OWB) to Mount Hawley Auxiliary Airport (3MY)
Event
- NTSB case
- CEN13CA489
- 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 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
- N3858P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Owensboro Daviess County Airport (OWB), Owensboro, KYTo Mount Hawley Auxiliary Airport (3MY), Peoria, 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
- 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
- Landing area overshoot
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses reported the airplane landed midfield on runway 36 (4,000 feet long by 60 feet wide) and the approach airspeed was very fast. The airplane veered to the left, exited the runway surface, went down a berm, and impacted the airport perimeter fence. No tire skid marks were noted on the runway surface. The pilot stated that the airplane encountered a gust of wind during touchdown which caused a loss of control. Due to some residential buildings near the end of the runway, the pilot elected not to abort the landing. The wind was reported from 040 degrees at 10 knots and gusting to 18 knots. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Postaccident examination of the airplane revealed substantial damage to the left wing and fuselage.
Probable cause
The pilot did not attain the proper touchdown point during landing, which resulted in a runway excursion and impact with a perimeter fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA489
- Event ID
- 20130814X10932
- Case number
- CEN13CA489
- 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: a88be71405f80e9de09db21665bfc4487af0ea893d65ed94fddeac18a82e909d; retrieved 2026-09-15T22:31:00.888Z.