N5396D accident

NTSB GAA17CA540 · 2017-09-16 · Lynchburg, VA · near W24

Docket — crew, injuries and powerplant

Summary

The pilot reported that, during landing, the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered he could not go around when landing in this direction, at this airport, due to terrain and obstacles. He further added that he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about ¼ nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east)." The pilot reported that the landing was on runway 28.

Full narrative

The pilot reported that, during landing the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered you "cannot go around" when landing in this direction, at this airport, due to terrain and obstacles. He further added that, he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident.

The ailerons, wings, and firewall sustained substantial damage.

During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about one 1/4 nautical miles from the runway threshold.

The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east). The pilot reported that the landing was on runway 28.

Probable cause

The pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Night
Sky condition
OVC
Ceiling (ft)
9000
Visibility (sm)
10
Wind direction
350
Wind speed (kt)
3
Temperature (F)
72
Nearest airport
FALWELL
Distance from field
0.0
Airport elevation
939

Aircraft

RegistrationMakeModelDamageFAR part
N5396D — — SUBS 091

Sequence of events

#OccurrencePhase
1 Approach-VFR go-around Aerodynamic stall/spin Cruise
2 Approach-VFR go-around Loss of control in flight Cruise
3 Landing-flare/touchdown Hard landing defining Cruise

Findings

Finding
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Incorrect use/operation cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Incorrect use/operation cause
Environmental issues-Physical environment-Terrain-Mountainous/hilly terrain-Contributed to outcome factor