- A software bug triggered during slow wet-weather running halted multiple cars on the formation lap, prompting a red flag ahead of the race in Sepang.
- FIA single-seater chief Nikolas Tombazis confirmed the glitch prevented power unit redeployment after an extreme concertina effect caused cars to almost stop completely.
- Governing officials developed and distributed a software patch to teams within 20 minutes, restarting the event following a 53-minute overall delay.
Formation Lap Glitch Triggers Red Flag at Sepang
The FIA has clarified the technical breakdown that paralyzed multiple Formula 1 machines ahead of Sunday’s Bahrain Grand Prix in Malaysia. After an initial 40-minute weather delay caused by heavy rainfall at the Sepang circuit, the field embarked on a formation lap that quickly descended into chaos. Front-row starters Max Verstappen and Lewis Hamilton, alongside several other competitors, suffered an electronic failure that neutralized throttle inputs, bringing numerous cars to a dead stop on track and forcing race control to display the red flag.
The sudden stoppage drew sharp criticism across the paddock. Sergio Perez branded the incident “unacceptable,” while McLaren’s Lando Norris called the situation “just horrible.” Norris pointed to the sport’s current technical regulations—where cars rely on power units delivering 47% electrical power—arguing that “we shouldn’t have any of that stuff, the electronic side.”
Software Vulnerability Exposed by Slow Wet-Weather Pace
Addressing the technical breakdown, FIA single-seater director Nikolas Tombazis explained that the governing body was caught out due to a lack of competitive wet-weather running under the prevailing engine formula. The unique operational demands of extremely low speeds in wet conditions exposed an unforeseen software flaw, requiring an emergency software patch that resulted in a 53-minute delay before the race could officially get underway.
Chelsea Told Squad May Hold Future Ballon d’Or Winner Other Than Cole Palmer or Estevao
“We didn’t manage to test the software as extensively as we would have liked, because there’s been very little wet running this year, and there was a bit of a combination of circumstances which caused this bug to kick in,” Tombazis said.
“Basically, the formation lap, some cars went very slowly, almost came to a standstill. There was a bit of a concertina effect between cars, and some cars almost stopped completely. And that bug prevented the power to be redeployed and for the cars to start again. I think if we had had a bit more testing, we probably would have managed to catch it in time and not to have such a situation.”
Rapid FIA Intervention and Paddock Reactions
Despite the disruption, Nikolas Tombazis defended the speed of the technical response once officials identified the root cause of the system failure.
“Once the problem happened, our guys realised very quickly what was happening and had to work under a lot of time pressure for an update to the software, which was issued to the teams, and the teams had to install it on their cars,” Tombazis stated. “So all of that took about 20 minutes. It may have felt like five hours for spectators waiting [for] a race and for everybody else, which is understandable, and we are sorry about that. But I think it was quite a fast reaction given the problem.”
While frontrunners faced high-stress moments on the grid, other drivers took the dramatic disruption in stride. Aston Martin-Honda driver Fernando Alonso, who went on to finish eighth in a strong outing for his team, quipped after the grand prix: “I had 50% DNFs this year, they never stopped the race for us.”
Why This Matters
Modern Formula 1 powertrains rely heavily on intricate electronic systems and hybrid deployment, with electrical output making up 47% of total power. The incident at Sepang demonstrates how vulnerable modern machinery remains to corner-case scenarios that cannot easily be replicated in dry testing conditions or simulated environments. Because race safety depends on precise electronic control, sudden sensor or deployment lockouts can freeze competitive fields simultaneously. Moving forward, the FIA and engine manufacturers face increased urgency to stress-test powertrain software against low-speed concertina effects and adverse weather to avoid costly delays and potential safety hazards at race starts.
Frequently Asked Questions
What caused the cars to lose throttle input during the formation lap?
A software bug was triggered when cars drove at extremely low speeds and encountered a concertina effect during the wet formation lap. The glitch prevented the powertrain from redeploying electrical energy, leaving drivers unable to get throttle response.
How long did it take the FIA to fix the problem?
FIA technical personnel diagnosed the bug and deployed a software patch to all teams in approximately 20 minutes, though the total delay before the race restart lasted 53 minutes.
Which drivers were impacted by the software glitch?
Front-row starters Max Verstappen and Lewis Hamilton were among the notable drivers who experienced the loss of throttle response, alongside several other competitors throughout the field.
