Advertisement
Advertisement
Kvyat takes pole for GP3 decider
By alley - Nov 1, 2013, 9:11 PM ET

Kvyat takes pole for GP3 decider

Toro Rosso Formula 1 signing Daniil Kvyat closed the gap on championship rival Facu Regalia by setting pole position for race one of GP3's 2013 title decider in Abu Dhabi.

MW Arden driver Kvyat lapped the Yas Marina circuit in 1m55.473s to take pole, while ART's Regalia struggled to find pace and will start 10th.

Kvyat is now just three points behind as a result of the four bonus points for pole. Regalia, whose struggle for grip was clear as he slid onto the run-off during one of his early runs, made a rear suspension change for his second effort on fresh tires but to little avail.

Carlin's Nick Yelloly will start alongside Kvyat on the front row, with another title contender, Kevin Korjus, in third. Korjus showed great pace through the opening two sectors, but appeared to struggle in the switchback section around the hotel.

Alexander Sims continued to perform well in his continued late-season cameo with Carlin and starts fourth, ahead of championship outsider Jack Harvey of ART.

Carlos Sainz Jr. qualified sixth, salvaging a decent starting position as his best time was disallowed for what video replays suggested was a very marginal track-limits call at the final corner.

Conor Daly, who is fourth in points, starts seventh, ahead of Patric Niederhauser and series debutant Dean Stoneman (LEFT), who qualified an impressive ninth for his international open-wheel return.

The last of the title contenders, Tio Ellinas, who led the series for the first part of the season, will start 12th.

None of the top six were eliminated from the title fight as a result of missing out on the four points for pole, but there will certainly be casualties in Saturday evening's race, the first-ever main series night race for either GP3 or GP2.

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.