F1 »

Liuzzi hit with grid penalty

Vitantonio Liuzzi has been penalised for blocking Nico Hulkenberg in qualifying for the British GP and drops five places on the Silverstone grid.
Vitantonio Liuzzi will start the British Grand Prix from the outside of row ten after being hit with a penalty for blocking Williams' rival Nico Hulkenberg in the second phase of qualifying at Silverstone.

The Force India driver had again reported a lack of top speed during day two of the event, and was caught on camera holding Hulkenberg up as both chased a spot in the top ten shoot-out for pole position. Liuzzi's fate was sealed, however, when he chopped across the bows of the young German rookie as Hulkenberg looked to pass and gain the advantage of a clear track.

"We need to work to understand why we were not so fast this session, as we believed a Q3 position was possible with both cars based on the performance in practice," Liuzzi opined, having enjoyed a stronger FP3 performance, "In Q1, it went okay and the balance in both the high and slow speed corners was quite good. Unfortunately, I only got one flying lap on my first run and, then, on the second, I couldn't improve. I think P12 or higher was there, but it can happen. We'll now start 20th because of the penalty.

"We thought that we had to keep Nico behind and I didn't realise he was on a hot lap. From 20th, it's not going to be easy, but there are overtaking spots here at least - plus the incentive of racing in front of our home crowd"

Liuzzi's penalty promotes Renault's Vitaly Petrov, Toro Rosso team mates Sebastien Buemi and Jaime Alguersuari, Lotus's Heikki Kovalainen and Virgin's Timo Glock, while Hulkenberg lines up 13th, sharing row seven with reigning world champion Jenson Button.

Force India came closest of all to getting a car into the top ten, with Adrian Sutil only being bumped from the shoot-out at the last moment. Having eased into Q2 on the basis of the fourth fastest lap in the opening phase of qualifying, the German struggled to find the necessary grip on Bridgestone's softer tyre compound and missed the cut by a couple of tenths.

"We have had a good car the whole weekend, but we struggled a bit with the tyre today, so the result is a little bit disappointing," Sutil confirmed, "In Q1, I could set a good time on the hard tyre, and it looked really good for a Q3 slot but, in Q2, I just couldn't get a good lap and couldn't go any quicker. We need to investigate why we couldn't go faster on the softer tyre, but it's not the end of the world and P11 is a good position to start. The top ten is, of course, the goal for the weekend, so it's important to finish the race, then anything is possible."



Related Pictures

Click on relevant pic to enlarge
Saturday Practice, Adrian Sutil (GER), Force India F1 Team, VJM03
Qualifying, Nico Hulkenberg (GER), Williams, FW32
Qualifying, Vitantonio Liuzzi (ITA), Force India F1 Team, VJM03
(L to R): Lewis Hamilton (GBR) Mercedes AMG F1 with Toto Wolff (GER) Mercedes AMG F1 Shareholder and Executive Director and Valtteri Bottas (FIN) Williams.
23.02.2017.
(L to R): Lewis Hamilton (GBR) Mercedes AMG F1; Toto Wolff (GER) Mercedes AMG F1 Shareholder and Executive Director; Valtteri Bottas (FIN) Williams, with the Mercedes AMG F1 W08.
23.02.2017.
(L to R): Lewis Hamilton (GBR) Mercedes AMG F1; Toto Wolff (GER) Mercedes AMG F1 Shareholder and Executive Director; Valtteri Bottas (FIN) Williams, with the Mercedes AMG F1 W08.
23.02.2017.
(L to R): Lewis Hamilton (GBR) Mercedes AMG F1 with Valtteri Bottas (FIN) Williams and the Mercedes AMG F1 W08.
23.02.2017.
Sahara Force India F1 VJM10 cockpit detail.
22.02.2017.
Sahara Force India F1 VJM10 rear wing and engine cover detail.
22.02.2017.
(L to R): Esteban Ocon (FRA) Sahara Force India F1 Team with team mate Sergio Perez (MEX) Sahara Force India F1 and the Sahara Force India F1 VJM10.
22.02.2017.
(L to R): Andrew Green (GBR) Sahara Force India F1 Team Technical Director; Sergio Perez (MEX) Sahara Force India F1; Dr. Vijay Mallya (IND) Sahara Force India F1 Team Owner; and the Sahara Force India F1 VJM10.
22.02.2017.
(L to R): Sergio Perez (MEX) Sahara Force India F1 with Alfonso Celis Jr (MEX) Sahara Force India F1 Development Driver and Esteban Ocon (FRA) Sahara Force India F1 Team.
22.02.2017.
(L to R): Andrew Green (GBR) Sahara Force India F1 Team Technical Director; Sergio Perez (MEX) Sahara Force India F1; Dr. Vijay Mallya (IND) Sahara Force India F1 Team Owner; Esteban Ocon (FRA) Sahara Force India F1 Team; Robert Fernley (GBR) Sahara Force India F1 Team Deputy Team Principal, and the Sahara Force India F1 VJM10.
22.02.2017.
(L to R): Dr. Vijay Mallya (IND) Sahara Force India F1 Team Owner with Sergio Perez (MEX) Sahara Force India F1 and Esteban Ocon (FRA) Sahara Force India F1 Team.
22.02.2017.
(L to R): David Croft (GBR) Sky Sports Commentator with Sergio Perez (MEX) Sahara Force India F1 and Esteban Ocon (FRA) Sahara Force India F1 Team.
22.02.2017.
(L to R): Alfonso Celis Jr (MEX) Sahara Force India F1 Development Driver; Sergio Perez (MEX) Sahara Force India F1; Dr. Vijay Mallya (IND) Sahara Force India F1 Team Owner; Alfonso Celis Jr (MEX) Sahara Force India F1 Development Driver, with the Sahara Force India F1 VJM10.
22.02.2017.
(L to R): Sergio Perez (MEX) Sahara Force India F1; Dr. Vijay Mallya (IND) Sahara Force India F1 Team Owner; Esteban Ocon (FRA) Sahara Force India F1 Team, with the Sahara Force India F1 VJM10.
22.02.2017.
(L to R): Sergio Perez (MEX) Sahara Force India F1 with team mate Esteban Ocon (FRA) Sahara Force India F1 Team and the Sahara Force India F1 VJM10.
22.02.2017.

Join the conversation - Add your comment

Please login or register before adding your comments.

Although the administrators and moderators of this website will attempt to keep all objectionable comments off these pages, it is impossible for us to review all messages. All messages express the views of the poster, and neither Crash Media Group nor Crash.Net will be held responsible for the content of any message. We do not vouch for or warrant the accuracy, completeness or usefulness of any message, and are not responsible for the contents of any message. If you find a message objectionable, please contact us and inform us of the problem or use the [report] function next to the offending post. Any message that does not conform with the policy of this service can be edited or removed with immediate effect.




© 1999 - 2017 Crash Media Group

The total or partial reproduction of text, photographs or illustrations is not permitted in any form.