Lansing-Capital Region

The pilot reported that after a normal start and taxi, the airplane was cleared for takeoff. During the takeoff roll, the airplane drifted right and the pilot corrected with the left rudder. When the airplane reached 100 knots, he rotated the airplane, and about 30 feet in altitude, the airplane experienced a roll to the right. The pilot tried to correct the roll with left rudder but was unable to provide sufficient left rudder. At this point, the airplane had drifted to the right of the runway and over the adjacent parallel taxiway. He was able to regain partial control by reducing engine power and banking the airplane to the left. The pilot attempted to land on the taxiway but was unable to judge his height above ground due to the low visibility, and subsequently impacted terrain to the right of the taxiway. Both wings and the fuselage sustained substantial damage. Prior to exiting the airplane, the pilot noted that the rudder trim was set to the full nose-right position. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Prior to the accident, maintenance was completed that consisted of an “Event II & Routine” inspection. The inspection procedure required the rudder trim system to be lubricated, a trim tab free play inspection, and an operational check prior to returning the airplane to service. Review of the maintenance procedures revealed there was no guidance on returning the rudder trim control system back to a neutral position at completion of the inspection.

The airport tower controller initially assigned the pilot to take off from runway 28L, which presented a 7-knot headwind. Shortly afterward, the controller informed the pilot of “a storm rolling in . . . from west to east,” and offered runway 10R. The pilot accepted the opposite direction runway for departure and added, “we’re ready to go when we get to the end . . . before the storm comes.” About 4 seconds after the airplane began accelerating during takeoff, the controller advised the pilot of a wind shear alert of plus 20 knots (kts) at a 1-mile final for runway 28L, and the pilot acknowledged the alert. In a postaccident statement, the pilot stated that departing with a 7-kt tailwind was within the operating and performance limitations of the airplane. The pilot reported that after a takeoff ground roll of about 4,000 ft “the left rudder didn’t seem to be functioning properly” and he decided to reject the takeoff. However, when he applied full braking, the airplane tended to turn to the right. He used minimal braking consistent with maintaining directional control of the airplane. The airplane ultimately overran the runway, impacted the airport perimeter fence, and encountered a ditch before it came to a rest. A postimpact fire ensued and consumed a majority of the fuselage. All four occupants evacuated safely.

The pilot was conducting an instrument approach at the conclusion of a cross-country flight when the airplane entered a shallow climb and left turn away from the runway heading about 0.5-mile from the intended runway. According to airspeeds calculated from automatic dependent surveillance-broadcast position data, the airplane’s calibrated airspeed was 166 knots when it crossed over the final approach fix inbound toward the runway and was about 84 knots when it was on a 0.5-mile final approach. The airplane continued to decelerate to 74 knots while it was in a shallow climb and left turn away from the runway heading. At no point during the approach did the pilot maintain the airframe manufacturer’s specified approach speed of 85 knots. The airplane impacted the ground in an open grass field located to the left of the extended runway centerline. The airplane was substantially damaged when it impacted terrain in a wings level attitude. The postaccident examination did not reveal any anomalies that would have precluded normal operation of the airplane. The altitude and airspeed trends during the final moments of the flight were consistent with the airplane entering an aerodynamic stall at a low altitude. Based on the configuration of the airplane at the accident site, the pilot likely was retracting the landing gear and flaps for a go around when the airplane entered the aerodynamic stall. The airplane was operating above the maximum landing weight, and past the aft center-of-gravity limit at the time of the accident which can render the airplane unstable and difficult to recover from an aerodynamic stall. Additionally, without a timely corrective rudder input, the airplane tends to roll left after a rapid application of thrust at airspeeds less than 70 knots, including during aerodynamic stalls. Although an increase in thrust is required for a go around, the investigation was unable to determine how rapidly the pilot increased thrust, or if a torque-roll occurred during the aerodynamic stall.

The airplane departed in IMC conditions on an IFR flight plan. Shortly after takeoff the pilot told the departure controller he had '...a problem.' The airplane's flight path was a series of left hand turns while performing descents and ascents. Reports of engine sounds varied from high rpm to low rpm. Many witnesses reported the airplane descending out of, and climbing into, clouds. The airplane was observed in a 45° angle descent, right wing low, as it collided with trees and the ground. The on-scene investigation found an intermittent electric gyro system inverter, a broken filament on the inverter power 'out' light bulb, electrically powered gyro's rotors did not have rotational damage, and a vacuum powered attitude indicator rotor with rotational damage. The pilot's toxicology report stated 45 mg/dl of ethanol detected in his muscle tissue.