What happened
During an instrument GPS approach, the pilot monitored automated weather reports and determined that the landing would involve a light quartering tailwind on an upslating runway. Upon reaching visual conditions, the pilot transitioned to visual flight rules and contacted the airport frequency. At that time, reports indicated approximately 1/4 inch of dry, unplowed snow covered the runway surface.
As the aircraft type landed on runway 22, the pilot engaged brakes, spoilers, and thrust reversers. While the aircraft initially decelerated, the rate of slowing decreased midway down the runway due to the antiskid system functioning continuously. The pilot attempted to cycle the thrust reversers but noted a lack of effective deceleration. Although an abort was considered, the pilot determined it was too late to execute a go-around. Consequently, the airplane overran the end of the runway, crossed onto a grass area, and entered a deep ravine. The incident resulted in substantial damage to the fuselage and both wings, though there were no fatalities or injuries reported.
Findings
Investigation into the airport conditions revealed that the runway surface had approximately one inch of snow. Local reports indicated that snow removal efforts at the facility had been inadequate, leaving significant windrows and ice chunks on the airfield. The airport lacked a formal, documented process for runway assessments or a structured snow and ice removal plan. Furthermore, there was no active Notice to Air Mission (NOTAM) regarding the runway conditions at the time of the accident. The failure to plow the runway contributed significantly to the loss of directional control and the subsequent excursion.