
Vilander to run Nurburgring as Bird opts for FE
AF Corse driver Sam Bird will sit out the FIA WEC's 6 Hours of Nürburgring event next month, due to a clash with the Formula E round in New York. IMSA regular Toni Vilander will replace him in the GTE Pro class No. 71 AF Corse Ferrari 488 GTE.
In Formula E, Bird will drive with his regular team DS Virgin Racing. It's a move that effectively ends his chances of winning the 2017 GTE drivers' world championship. He and teammate Davide Rigon currently sit third in the points standings, just 14 points off the lead.
"With the first-ever FIA-sanctioned motorsport event to be held in New York, Formula E is continuing to push the boundaries and break new ground, and it's exciting to be part of that," said Bird (pictured). "I know we'll put on a great show for the people of New York and I'm expecting big crowds to turn up on both days. Being a double race event, there's a huge amount at stake for all the teams and the drivers so it's definitely one to watch."
For Vilander, it's his first race in the WEC since the 6 Hours of Bahrain in 2015, also with AF Corse. The Finn raced with the Italian team in the WEC from 2012-2015 in GTE Pro, winning the title in 2014. Since then he's been driving with Risi Competizione in IMSA's GTLM class.
"I'm happy to be able to return to the FIA WEC with the 488 GTE of AF Corse," Vilander stated. "This is my chance to cancel the disappointment of the 24 Hours of Le Mans. The No. 71 is in the top places of the championship standings, and I will give all I have to achieve the best possible result at Nürburgring, to help Ferrari in the Manufacturers' Championship and help Davide Rigon in the Drivers' ranking."
Meanwhile, Bird's DS Virgin Racing teammate Jose Maria Lopez will not make the trip to New York for Formula E,; the Argentinian will instead race with Toyota Gazoo Racing in LMP1.
Latest News
Comments
Comments are disabled until you accept Social Networking Cookies. Update cookie preferences
If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.




