ERA24LA321 · Beech 58
Beech 58 · Accident: landing area overshoot
From an unrecorded airport to Asheville Regional Airport (AVL)
Event
- NTSB case
- ERA24LA321
- 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 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
- N5VV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Asheville Regional Airport (AVL), Asheville, NC
- Aircraft age
- About 42 years (built 1982)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was flying his airplane to his home airport following an annual inspection. Ground operations and the preflight inspection were routine, and the weather was “clear and calm.” During the takeoff roll and shortly after takeoff, he noticed that the engines were not running smoothly. Rather than continue over the mountains to his destination, he elected to return to the departure airport. As he set up for landing, he was anxious and “high and a little fast” on the approach. After touchdown, the airplane bounced and veered slightly left as he applied the brakes and retarded the throttles. The airplane departed the end of the runway, the nose landing gear collapsed, and the airplane nosed down in the grass. A Federal Aviation Administration inspector reported that the propellers contacted the ground and the lower fuselage and right wing root were substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot further stated that he did not fly a stabilized final approach.
Probable cause
The pilot’s failure to maintain proper altitude and airspeed on final approach, resulting in a runway excursion and substantial damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA321
- Event ID
- 20240723194755
- Case number
- ERA24LA321
- 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: ae0260277d4ebfc17f39210c8025e69a45440d5bc8852c4c1014d4a5d3c8e130; retrieved 2026-09-16T19:04:48.944Z.