Glenn Dunbar/Motorsport Images
Sainz misses Belgian GP due to exhaust failure
Carlos Sainz will not take part in the Belgian Grand Prix after suffering an exhaust failure on his way to the grid.
The Spaniard was on his reconnaissance laps when he radioed his team to report smoke coming from the rear of his car. On the run to Blanchimont towards the end of the lap, the smoke got heavier and Sainz said: “Box, box, something broke.”
https://twitter.com/ChrisMedlandF1/status/1300055582775414786
Once back in the garage, McLaren took the engine cover off but found an exhaust failure that could not be repaired in time for the start of the race, forcing Sainz to jump out of his car and not take part.
Sainz was due to start from seventh place at Spa-Francorchamps but his grid lot will now remain empty, with Sergio Perez remaining in eighth rather than moving up a position on the grid.
The incident marks the second time in a row that Sainz has suffered a powertrain-related problem and failed to start the Belgian Grand Prix, after a power unit issue left him stranded on the startline a year ago, limping round the first lap before retiring.
Chris Medland
While studying Sports Journalism at the University of Central Lancashire, Chris managed to talk his way into working at the British Grand Prix in 2008 and was retained for three years before joining ESPN F1 as Assistant Editor. After three further years at ESPN, a spell as F1 Editor at Crash Media Group was followed by the major task of launching F1i.com’s English-language website and running it as Editor. Present at every race since the start of 2014, he has continued building his freelance portfolio, working with international titles. As well as writing for RACER, his broadcast work includes television appearances on F1 TV and as a presenter and reporter on North America's live radio coverage on SiriusXM.
Read Chris Medland's articles
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.