ERA15CA154 · Beech 58
Brick Street Mutual Insurance Beech 58 · Accident: landing area overshoot
From Yeager Airport (CRW) to Charlotte-Monroe Executive Airport (EQY)
Event
- NTSB case
- ERA15CA154
- 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
- Instrument 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
- N50NH
- Operator
- Brick Street Mutual Insurance
- Onboard fatalities
- Unknown
- Route
- From Yeager Airport (CRW), Charleston, WVTo Charlotte-Monroe Executive Airport (EQY), Monroe, NC
- Aircraft age
- About 36 years (built 1979)
- 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
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot had initially intended to perform a GPS approach to runway 23, into the wind; however, the weather was below minimums for that approach and he then elected to perform an instrument landing system (ILS) approach in the opposite direction to runway 5. While about 100 feet above decision height for the ILS approach to runway 5, the pilot did not have the runway environment in sight and started to make the motions to go-around, but did not increase engine power. He then observed the runway centerline markings and due to excess speed and a tailwind, the airplane floated and landed long. When asked about the touchdown point location and speed at touchdown, the pilot estimated it was about 1,000 feet before the departure end of the 7,001-foot-long runway, at a speed of 85 knots. He applied the brakes, but the runway was wet and he did not feel deceleration. He left the flaps fully extended as the airplane traveled off the end of the runway, coming to rest upright in a grass area. The pilot added that there were no preimpact mechanical malfunctions with the airplane. The recorded weather at the airport, about the time of the accident, included an 11-knot tailwind. Examination of the wreckage by a Federal Aviation Administration inspector revealed damage to the landing gear and lower fuselage.
Probable cause
The pilot's failure to maintain a proper glidepath and failure to perform a go-around once a safe landing could not accomplished, which resulted in a landing area overshoot and runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15CA154
- Event ID
- 20150313X90544
- Case number
- ERA15CA154
- 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, coordinates. 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: 67813090396d3ee130cecbce8aabbb111fa72d31bac617821ca4d24e21756185; retrieved 2026-09-16T02:09:08.846Z.