Mark Sutton/Motorsport Images
Schumacher to miss qualifying
Mick Schumacher will not take part in qualifying for the Monaco Grand Prix after crashing in final practice.
The Haas rookie lost control at Casino Square, with the rear of the car getting away from him through the right-hander. Schumacher tried to catch the slide but failed to do so before hitting the barrier hard on the outside of the circuit, bringing out the red flags that meant the session ended a few minutes early.
The car was heavily damaged and Haas has now confirmed that the damage is too great for the team to be able to repair in time for qualifying.
https://twitter.com/F1/status/1396077364505944066
“Schumacher will not participate in qualifying,” a team spokesperson confirmed. “Chassis damage evaluation on his VF-21 on-going.”
Schumacher had been 14th quickest in FP3, raising hopes of a first Q2 appearance for Haas this season. The team’s hopes now rest with Nikita Mazepin, who was 16th in the final session and has enjoyed a clean weekend so far, following warnings from Guenther Steiner to both drivers to keep their cars out of the barriers.
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.