Summary
On January 16, 2010, a Cirrus SR22 (N155SR) was involved in an incident near Fredericksburg, TX. All 4 people aboard were uninjured. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this incident to be: The pilot's failure to maintain directional control during landing, and his failure to properly execute a go-around.
After completing a 167-mile cross country flight in dark night conditions, the pilot landed on a 5,000-foot long runway. The pilot stated that during the landing roll, the airplane encountered a gust of wind from the right, and he could not prevent the airplane from drifting to the left. He said that he applied full power and attempted a go around, but the airplane would not become airborne. The pilot said he reduced power before the airplane struck a fence on the left side. There was substantial damage to the wing, fuselage, and the landing gear, but no injuries to the four persons on-board.
This incident is documented in NTSB report CEN10CA104. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N155SR.
Accident Details
Probable Cause and Findings
The pilot's failure to maintain directional control during landing, and his failure to properly execute a go-around.
Aircraft Information
Registered Owner (Current)
Analysis
After completing a 167-mile cross country flight in dark night conditions, the pilot landed on a 5,000-foot long runway. The pilot stated that during the landing roll, the airplane encountered a gust of wind from the right, and he could not prevent the airplane from drifting to the left. He said that he applied full power and attempted a go around, but the airplane would not become airborne. The pilot said he reduced power before the airplane struck a fence on the left side. There was substantial damage to the wing, fuselage, and the landing gear, but no injuries to the four persons on-board.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# CEN10CA104