Australian GP: Formula 1: The final 2 laps of the Australian Grand Prix had all the drama, which saw multiple car collisions and red flags, and a race restart. The Australian Grand Prix has become the subject of controversy following the decision of Haas to protest the provisional results of the race. Follow Formula 1 LIVE Updates with InsideSport.IN.
Haas driver Nico Hulkenberg had been running in fourth place before the red flags were thrown, denying him the opportunity to retain his position. However, if the pre-red flag running order is somehow reinstated, Hulkenberg could potentially move up to a podium finish. This is because Carlos Sainz was ahead of Hulkenberg when the red flags were shown.
Following the red flags, the running order was reset to final grid restart positions, sending Hulkenberg back down to P8. He was later promoted to P7 after Sainz received a five-second time penalty. However, Haas believes that Hulkenberg should have been allowed to maintain his position.
As a result, Haas has submitted a protest to the stewards of the race. A team representative will visit the stewards at 19:30 local time to review the matter. The protest adds another layer of drama to what was already an eventful race in Melbourne.
For the first time since 2013, @alo_oficial has THREE consecutive podium finishes in the bag! 💪
We think El Padre enjoyed this one 😉#AusGP #F1 @AstonMartinF1 pic.twitter.com/H4ugAYqHjF
— Formula 1 (@F1) April 2, 2023
Reasons for Red Flags
Sunday’s Grand Prix at Melbourne saw a late red flag deployed as Haas’s Kevin Magnussen crashed into the Turn 2 barriers, ripping the right-rear wheel off his VF-23. That led to a standing restart in which Carlos Sainz tapped Fernando Alonso into a spin, both Alpines crashed out, and Williams’ Logan Sargeant also collected AlphaTauri’s Nyck de Vries.
Also Read: Australian GP: Christian Horner acknowledges Sergio Perez’s ‘horrible day’ in Qualifying – Check Out
The race was red-flagged again and restarted under caution on Lap 58 of 58 – but the order of classification for the restart was reverted to before the previous accident-filled restart had begun, which irked the Hass team.
Editors pick
