- Date
- July 12, 2024, 09:45 local (13:45 UTC)
- Place
- Pisgah Forest, NC · Off end of runway 9
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5VVBeech 58
- Defining event
- Landing: Landing area overshoot
- Weather
- Visual (VMC) · Day
- Status
- Completed
- Report
- Approved by Office Director
- Investigation class
- Class 4 - Basic report with no Prelim publish
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20240712009799A
- Case key
- 194755
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Aircraft
- Registration
- N5VV
- Reported as
- Beech 58
- Category
- Airplane
- Serial number
- TH1334
- Built
- 1982
- Airframe hours
- 4,400
- Engines
- Continental IO-520-CB, 280 horsepower, reciprocatingContinental IO-520-CB, 280 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · July 12, 2024 · 0 hours before
- Destination
- AVL · Asheville, NC
- Airport
- 3NR3 · Transylvania Community Airport, runway 9, 2,901 × 50 ft, asphalt
- Equipment
- Onboard weather, Handheld GPS, Electronic flight bag or handheld device, ADS-B, Stall warning system
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 77
- Injuries
- None
- Certificates
- Private, Airline transport
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- October 5, 2023
- Seat
- Left
- Restraint
- 3-point
- Flight hours
- 2,805 total · 1,493 in this make and model · 2,602 as pilot in command · 14 in the last 90 days · 5 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 350° at 5 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 81 °F, dew point 63 °F
- Altimeter
- 30.19 inHg
- Observed at
- KAVL, 11 nm away
- METAR
- METAR KAVL 121454Z 35005KT 10SM CLR 27/17 A3019 RMK AO2 SLP194 T02720167 51006
Docket · 3
The files NTSB released with the investigation on September 27, 2024, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.2 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.