.jpg?environment=live)
F3: Ocon takes dominant Moscow pole
Esteban Ocon took a crushing pole position for the first Formula 3 European Championship race at Moscow Raceway by six tenths of a second.
The championship-leading Lotus F1 Junior lapped the Russian track in 1m26.530s just after the midway point of the session. Nobody else cracked the 1m27s barrier, and after a further lap in 1m26.6s the Frenchman returned his Prema Powerteam Dallara-Mercedes to the pitlane.
Ocon completed fewer laps than any other competitor so therefore likely has more life in his tires for the races. His pole position margin was the biggest in a dry-weather qualifying session since the F3 European Championship was revived in 2012.
Jordan King was a distant best of the rest, the Briton taking his Carlin Dallara-Volkswagen to his first European F3 front-row slot for more than a year.
Tom Blomqvist, from the Jagonya Ayam side of the Carlin stable, took third on the grid, with the series' recent form man Max Verstappen -- who has taken six wins in a row -- in fourth place with his Van Amersfoort Racing Dallara-VW.
The third-row grid positions were taken by Lucas Auer (Mucke Motorsport Dallara-Mercedes) and Racing Steps-backed Carlin rookie Jake Dennis. Ferrari protege Antonio Fuoco starts seventh in his Prema car, alongside Van Amersfoort's ever-improving Dutchman Jules Szymkowiak.
Nicholas Latifi (Prema) and Felix Serralles (West-Tec) round out the top 10, with Felix Rosenqvist surprisingly down in 11th.
The field is down to 20 cars this weekend, with British teams Fortec Motorsport, T-Sport and Double R Racing skipping the event along with Swiss privateer Sandro Zeller.
T-Sport elected to go testing at Pembrey instead, while Double R found more monocoque damage than expected to Felipe Guimaraes's car after a run of five successive non-finishes.
Originally on Autosport.com
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.





