There were no shortages of extreme weather conditions sweeping through the peloton during the 2015 season. So much so that the UCI tested out a new Extreme Weather Protocol during several races, and then decided to add it the UCI Regulations at a two-day Management Committee meeting during the World Championships in Richmond, Virginia.
Some of the drastic weather conditions that the peloton faced during races this year began in February at the Tour of Oman, where stage 5 ended in an argument between riders and organisers over security concerns regarding the extreme heat, with riders claiming that their SRM showed readings of 50 degrees Celsius.
High winds blew through the field during Driedaagse De Panne-Koksijde and Gent-Wevelgem, which were partially neutralized. The team time trial course at Tirreno-Adriatico was affected by rain and high winds that apparently damaged some of the roads, and the stage was altered to a shorter individual time trial instead. Later in that same race, Nairo Quintana won the queen stage 5 under snowfall on the summit to Terminillo.
Snowy conditions have affected races before with the 2014 Giro d'Itala, where snow dumped on the Gavira and Stelvio stage. And the 2013 Milan-San Remo was shortened due to snow and bad weather that ended up ruling out racing over the Turchino climb.
At the end of the 2015 season, extreme weather hit the peloton again with heat at the Abu Dhabi Tour, with riders claiming it was upwards of 50 Celsius during the opening stage. The stage was eventually shorted by only 14.5km and the riders still raced the 159km, some four hours in the heat.
Check out the gallery of extreme weather that the peloton faced during the 2015 season.
Thank you for reading 5 articles this month* Join now for unlimited access
Enjoy your first month for just £1 / $1 / €1
*Read 5 free articles per month without a subscription
Join now for unlimited access
Try your first month for just £1 / $1 / €1
Thank you for signing up to Cycling News. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.