What happened
While performing a GPS instrument approach, the pilot monitored automated weather reports and anticipated landing with a light quartering tailwind on an upslodging runway. Upon reaching the runway and transitioning to visual flight rules, the pilot received reports of approximately 1/4 inch of dry, unplowed snow on the surface.
During the landing roll on runway 22, the pilot engaged the brakes, spoilers, and thrust reversers. Although the aircraft type/model initially slowed, the antiskid system began functioning continuously, causing the rate of deceleration to drop significantly. The pilot attempted to cycle the thrust reversers but noted a lack of effective response. Realizing the aircraft was not slowing sufficiently, the pilot considered an aborted landing but determined it was too late to execute the maneuver. Consequently, the aircraft overran the end of the runway, traveling onto a grass area and into a deep ravine. The accident resulted in substantial damage to the fuselage and both wings, though there were 0 fatalities.
Findings
Investigations into the airport conditions revealed that the runway surface was covered in approximately one inch of snow. Reports indicated that snow removal efforts at the facility had been inconsistent, leaving behind significant windrows and ice chunks. The airport lacked a formal, documented snow and ice control plan, and runway assessments were conducted informally without official records.
Furthermore, there was no active Notice to Air Missions (NOTAM) regarding the runway conditions at the time of the accident. While the manufacturer provided estimated landing distances for various conditions, the presence of unplowed snow and a tailwind significantly increased the required stopping distance beyond the aircraft's operational capability on the available runway.