What happened
During the departure phase, air traffic control originally instructed the pilot to utilize runway 28L, which provided a 7-knot headwind. Due to an approaching storm moving from west to east, the controller suggested an alternative departure via runway 10R. The pilot agreed to the change, expressing a desire to depart before the weather arrived. Shortly after the aircraft began its takeoff roll, the controller issued a wind shear alert indicating a 20-knot increase at one mile final for runway 28L, which the pilot acknowledged.
As the aircraft reached a ground roll of approximately 4,000 feet, the pilot experienced a malfunction where the left rudder appeared to be non-functional. In response to this loss of control, the pilot initiated a rejected takeoff. While attempting to decelerate, the pilot noted that applying full braking caused the aircraft to veer toward the right, leading to the decision to use only enough braking necessary to maintain directional stability. The aircraft subsequently exited the runway, struck the airport perimeter fence, and entered a ditch. A fire broke out following the impact, resulting in significant damage to the fuselage. There were no fatalities among the four occupants, all of whom evacuated the aircraft safely.
Findings
- The pilot attempted to manage the aircraft using minimal braking to prevent a rightward veer during the aborted takeoff.
- The aircraft encountered a rudder malfunction during the takeoff roll.
- The incident occurred amidst active weather changes and a wind shear alert.