F1 »

POLL: Who should get second Force India seat?

Paul di Resta unveiled the new Force India VJM06 alone, but there are plenty of names in the frame to partner him in 2013....
Just as we were being led to believe that the second Force India ride for 2013 was boiling down to a head-to-head between Jules Bianchi and Adrian Sutil, the delayed announcement allowed several other candidates to pop into the frame.

According to the F1 rumour mill, Narain Karthikeyan has managed to squeeze extra funding from his backers and could be a contender to partner Paul di Resta, while others are calling for the likes of Kamui Kobayashi and Heikki Kovalainen to be given a chance to continue their F1 careers after better-funded drivers pushed them out of seats at Sauber and Caterham respectively.

With Vijay Mallya's widely-reported business problems, it may be that Force India is entirely dependent on a 'pay driver' linking up with di Resta, but who do you think should get the seat?

This is your chance to have your say, so cast your vote HERE, and feel free to explain your decision in the comments section below....



Related Pictures

Click on relevant pic to enlarge
Jaime Alguersuari tries his hand at tyre fitting
22.11.2012- Heikki Kovalainen (FIN) Caterham F1 Team CT01
22.11.2012- Kamui Kobayashi (JAP) Sauber F1 Team C31
25.10.2012- Press conference, Narain Karthikeyan (IND) HRT Formula 1 Team F112
Free Practice 1: Jules Bianchi (FRA), Test Driver, Sahara Force India Formula One Team VJM05
11.05.2012- Adrian Sutil (GER) and Nico Hulkenberg (GER) Sahara Force India F1 Team VJM05
Paul di Resta (GBR) Sahara Force India VJM06. 06.02.2013.
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.