Narrative:

I spoke to the airport and [they] said that they lifted the runway condition code to 2/2/2 and that a couple aircraft had used the runway earlier in the day with minimal issues. Airport representative stated the runway was in a lot better condition than the taxiways and aprons. Airport representative stated that the runway was deiced 25 feet wide on each side of the centerline (50 feet total).got onto the runway and slowly increased power slowly and evenly. The aircraft started rolling and at about 60-70 knots the aircraft started to veer aggressively to my left and I tried to correct with opposite rudder. Opposite rudder pressure didn't hardly help the yawing of the aircraft. I looked down and made sure the torques were matched and they were; the aircraft was still veering to my left. I tried to add a little more power on the left engine to counter balance the yaw; instantly found that wasn't going to work and brought both power levers to idle. At this point; I decided the aircraft wasn't going to be able to be recovered back towards centerline.the runway conditions were way; way worse that what was reported. I realized I wasn't going to be able to control the aircraft. At this point; I brought the power to idle; I feathered the propellers and cut off fuel; knowing I would end up on the left side of the runway in the snow due to the aircraft veering to the left of centerline.this was not an accident. After investigation and proper preflight planning; the runway was under advertised; as found out during this incident. The runway should have never even been open to any air traffic at any time of the day and should be remained closed until proper steps can be taken to improve the runway condition code.

Related reports:

Google
 

Original NASA ASRS Text

Title: King Air Captain reported runway conditions were poor during takeoff roll resulting in a runway excursion.

Narrative: I spoke to the airport and [they] said that they lifted the runway condition code to 2/2/2 and that a couple aircraft had used the runway earlier in the day with minimal issues. Airport representative stated the runway was in a lot better condition than the taxiways and aprons. Airport representative stated that the runway was deiced 25 feet wide on each side of the centerline (50 feet total).Got onto the runway and slowly increased power slowly and evenly. The aircraft started rolling and at about 60-70 knots the aircraft started to veer aggressively to my left and I tried to correct with opposite rudder. Opposite rudder pressure didn't hardly help the yawing of the aircraft. I looked down and made sure the torques were matched and they were; the aircraft was still veering to my left. I tried to add a little more power on the left engine to counter balance the yaw; instantly found that wasn't going to work and brought both power levers to idle. At this point; I decided the aircraft wasn't going to be able to be recovered back towards centerline.The runway conditions were way; way worse that what was reported. I realized I wasn't going to be able to control the aircraft. At this point; I brought the power to idle; I feathered the propellers and cut off fuel; knowing I would end up on the left side of the runway in the snow due to the aircraft veering to the left of centerline.This was not an accident. After investigation and proper preflight planning; the runway was under advertised; as found out during this incident. The runway should have never even been open to any air traffic at any time of the day and should be remained closed until proper steps can be taken to improve the runway condition code.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.