F1 »

F1 Australian GP: Mark Smith leaves Sauber on eve of Australian GP

Sauber's technical director Mark Smith has split from the team on the eve of the 2016 F1 season opener in Australia for family reasons.
Sauber's technical director Mark Smith has split from the team on the eve of the 2016 F1 season opener in Australia for family reasons.

Smith had only been appointed at the start of July 2015 having previously held roles at Caterham, Jordan, Force India and Red Bull and a short statement from the Swiss team confirmed the Brit “has decided to go back to the UK for family reasons. He has already left the company.”

Sauber has also thanked Smith for his efforts over the past nine months and heads into the Australian Grand Prix without a technical director. It is not yet known who will cover the position for Sauber in Melbourne.




Related Pictures

Click on relevant pic to enlarge
Mark Smith, Caterham [Credit: XPB]
Sauber C36-Ferrari, [Credit: Sauber]
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.
Sergio Perez (MEX) Sahara Force India F1 and Esteban Ocon (FRA) Sahara Force India F1 Team unveil the Sahara Force India F1 VJM10.
22.02.2017.
Sergio Perez (MEX) Sahara Force India F1 and Esteban Ocon (FRA) Sahara Force India F1 Team unveil the Sahara Force India F1 VJM10.
22.02.2017.
Otmar Szafnauer (USA) Sahara Force India F1 Chief Operating Officer.
22.02.2017.
(L to R): Esteban Ocon (FRA) Sahara Force India F1 Team with Otmar Szafnauer (USA) Sahara Force India F1 Chief Operating Officer.
22.02.2017.
Esteban Ocon (FRA) Sahara Force India F1 Team.
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.