Audi’s Gabriel Bortoleto Disqualified from Miami Sprint Over Engine Pressure Breach
Bortoleto loses 11th‑place Miami Sprint finish after Audi engine pressure exceeds 4.8 barA limit; team admits breach, Hulkenberg loses car to fire.

TL;DR
Gabriel Bortoleto lost his 11th‑place finish in the Miami Sprint after his Audi’s engine intake air pressure reached 4.9 barA, exceeding the 4.8 barA limit. The team acknowledged the breach, adding to a difficult weekend for Audi that saw Nico Hulkenberg’s car burn during reconnaissance laps.
Context The Miami Sprint is a 100‑kilometre race that sets the grid for the main Grand Prix. Bortoleto crossed the line in 11th place on Saturday, but post‑race technical checks revealed his Audi’s intake air pressure was above the allowed maximum. FIA Technical Delegate Jo Bauer recorded the over‑pressure and referred the matter to the stewards, who applied the standard disqualification penalty for a technical infringement.
Key Facts - Bortoleto’s car measured 4.9 barA, 0.1 barA over the 4.8 barA ceiling set by Article C5.3.2 of the FIA F1 Technical Regulations. - The team told the stewards that the Technical Delegate’s finding was correct, noting the pressure spike occurred over a single lap as temperatures rose higher than expected. - Audi also lost Nico Hulkenberg before the Sprint began when his car caught fire during reconnaissance laps, compounding the team’s setbacks. - The regulations require the engine intake air pressure to stay below the limit “at all times”; corrective action after the breach does not negate the violation.
What It Means Audi now faces a points deficit in both the constructors’ and championships’ standings, with Bortoleto’s Sprint result erased and Hulkenberg missing the race entirely. The team will likely scrutinise its cooling and pressure‑control systems before the next event in Imola. Observers should watch whether Audi can avoid further technical issues and how the disqualification influences its upgrade path for the remainder of the season.
Continue reading
More in this thread
Conversation
Reader notes
Loading comments...