Advertisement
Spengler grabs pole for Hockenheim DTM finale
By alley - Oct 19, 2013, 5:10 AM ET

Spengler grabs pole for Hockenheim DTM finale

Bruno Spengler took pole position for the final round of the DTM at Hockenheim as BMWs filled the top four positions.

The 2012 champion moved progressively closer to the front during the four sections of qualifying and took the top spot in 1m33.443s during his single-lap run in Q4.

Practice pacesetter Dirk Werner made it an all-Schnitzer Motorsport front row for the first time since the team returned to the DTM in 2012. His lap was 0.303s slower than Spengler's.

Briton Andy Priaulx will start third, the RMG driver taking a career-best qualifying spot. Priaulx's lap was only the fourth quickest in Q4, but he was promoted a spot when Timo Glock's time was deleted for the German failing to keep all four wheels on the track at Turn 1. Fourth still marked a career-best start for the MTEK driver.

Miguel Molina continued the excellent qualifying form he's shown in the second half of the season. The Phoenix Audi driver made Q3 for the fourth weekend in a row and will start a spot ahead of his Zandvoort polesitter Marco Wittmann.

Mattias Ekstrom, Adrien Tambay, new champion Mike Rockenfeller and Augusto Farfus completed the top 10 while Martin Tomczyk was knocked back to 11th " and out of the Q3 reckoning, thanks to a stunning late effort from team-mate Priaulx at the end of Q2. Tomczyk will start two places ahead of Robert Wickens, who recovered from his practice off to start 13th and best of the Mercedes drivers.

A final-minute flyer from Pascal Wehrlein was enough to eliminate RSC Mucke team-mate Daniel Juncadella from contention in Q1.

The Spaniard, who starts 17th, had just a minute earlier knocked Jamie Green's Abt Audi out of contention. Christian Vietoris, third in the championship, will start behind him in 20th.

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.