N6684Z Beech 36 accident

NTSB WPR19LA138 · 2019-05-05 · Reno, NV · near RNO

Docket — crew, injuries and powerplant

Summary

The pilot was landing the airplane in gusty wind conditions when he lost directional control of the airplane. After touchdown, the airplane veered off the runway to the left, despite the pilot’s corrective inputs. Subsequently, the airplane exited the runway, struck two runway signs, and spun to the right before coming to a stop. An examination of the airplane revealed that the nosewheel would not center and that it pointed to the right. Impact damage was visible on the nosewheel strut assembly. Additionally, when the right rudder pedal was pushed to the full position, the right rudder was about 5° from full deflection. It could not be determined whether these anomalies were impact related. The airplane would have had right turning tendencies if the nosewheel condition existed during the landing. The pilot would have had less rudder authority available to counter the left turning tendencies if the rudder condition existed during landing. No other mechanical malfunctions or failures that would have precluded normal operation were observed. The circumstances of the accident are consistent with the pilot’s inability to maintain directional control during landing in strong, gusty wind conditions.

Full narrative

On May 4, 2019, about 1915 Pacific daylight time, a Beech A36 airplane N6684Z, was substantially damaged when it was involved in an accident at the Reno/Tahoe International Airport (RNO), Reno, Nevada. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. According to the pilot, he was landing on runway 25 when, despite his right rudder inputs, the airplane veered left off the runway. The airplane continued onto an intersecting runway, striking two runway signs and making a tight 360° turn to the right before stopping. The pilot stated that he was unaware of why he lost directional control of the airplane on the ground. About the time of the accident, the reported wind was from 310o at 15 knots, gusting to 29 knots. The airplane was examined by a certified airframe and powerplant (A&P) mechanic, under the supervision of a Federal Aviation Administration (FAA) inspector. No anomalies were noted with the brake system or tires. The airplane was lifted on jacks to facilitate a landing gear examination. During the examination, the rudder pedals moved freely and there was no binding or anything impeding their movement. The left rudder was noted to fully deflect. However, when the right rudder pedal was pushed to the full position, the right rudder was about 5° from full deflection. Additionally, the nosewheel strut assembly exhibited impact damage. The nosewheel would not center and pointed slightly to the right. The investigation could not determine if the nosewheel and rudder were out of alignment before the accident or if their misalignment was due to impact damage.

Probable cause

The pilot’s inability to maintain directional control during landing in gusty crosswind conditions for reasons that could not be determined based on available evidence. 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
Day
Sky condition
BKN
Ceiling (ft)
7000
Visibility (sm)
10
Wind direction
310
Wind speed (kt)
15
Temperature (F)
68
Nearest airport
Reno/Tahoe Intl
Distance from field
5062.0
Airport elevation
4415

Aircraft

RegistrationMakeModelDamageFAR part
N6684Z Beech 36 SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-landing roll Loss of control on ground defining Cruise
2 Landing-landing roll Runway excursion Cruise
3 Landing-landing roll Collision with terr/obj (non-CFIT) Cruise

Findings

Finding
Not determined-Not determined-(general)-(general)-Unknown/Not determined cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Attain/maintain not possible cause