Advertisement
Aston Martin protests qualifying results over Sainz crash

Zak Mauger/Motorsport Images

By Chris Medland - Apr 20, 2024, 7:15 AM ET

Aston Martin protests qualifying results over Sainz crash

Aston Martin has protested the results of qualifying at the Chinese Grand Prix due to the crash suffered by Carlos Sainz.

Sainz lost control out of the final corner during Q2 and spun to the inside of the track, hitting the barrier and stopping with a broken front wing. The red flag was brought out to interrupt the session, but Sainz was then able to restart his car without external help, and returned to the pits under his own power.

Ferrari was then able to replace the front wing and check the car for other damage before Sainz rejoined the session and advanced to Q3, while Lance Stroll was knocked out in 11th place for Aston Martin.

The protest from Aston Martin is against a breach of Article 39.6 of the Sporting Regulations, that states: “Any driver whose car stops on the track during the qualifying session or the Sprint shootout will not be permitted to take any further part in that session.”

Chris Medland
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

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.