Wet Track, Silent Power Unit: The Sepang Software Failure and a Test of FIA Governance

What happened that Sunday morning at the Sepang International Circuit was a rare sight in recent Formula One history. On the formation lap, on a wet track, the cars almost came to a standstill. The news of that moment was not speed but stasis. Before the race had even begun, as spectators fixed their eyes on the grid, the machines moving across the track seemed to be losing control of themselves. Some lost speed for no apparent reason; some power units seemed to fall suddenly silent. A pre-race formality, normally not the stuff of headlines, became a technical and safety event. The lap meant to prepare the field turned into a stage for a test — where questions of trust between machine, software and regulator moved to the front.

At the centre of the incident is an unintended loss of power. Running at low engine speed, in wet and low-grip conditions, and in wet-weather energy-management settings, an interaction with the layout of specific circuit sectors produced an energy loss in the power unit that nobody had predicted. This was not a mechanical failure but a behavioural failure at the software layer. And here the story stops being purely technical; it becomes the story of a governance system, in which a regulator must decide mid-race how to intervene quickly.

Context: New-era cars, an old argument

The 'new era of cars and engines' Formula One was working with was by no means an easy season. Built around ground-effect aerodynamics and new energy-management systems, this generation of cars was technically ambitious, but that ambition exacted a price. From the opening race, drivers had been voicing dissatisfaction with the nature of energy management. This was not a one-off complaint; it was a sustained cycle of discontent affecting both race outcomes and the spectator experience.

Sepang itself is an important part of this discussion. The Malaysian circuit had been off the Formula One calendar for years, and its return meant a track of a different character, whose sector layout, long straights and technical corners place a different load on the power unit. In wet conditions this load becomes more complex, because low grip lowers car speed, engine revolutions stay low, and the balance between energy recovery and deployment becomes fragile.

Core analysis: A chain at the software layer

This is where the argument I like to return to repeatedly comes in — the incident is not merely a symptom but a chain of variables. First variable: low engine speed. On a formation lap the car does not run at full speed, so revolutions are low. Second variable: low grip. On a wet track the chance of wheelspin is higher, so the car must be driven more slowly. Third variable: an energy-management mode set for wet weather, which deploys and recovers electrical energy differently from a dry race. Fourth variable: the layout of specific circuit sectors, which in this particular combination creates a state in which the software misapplies its own limits.

In the combination of these four variables, the power unit loses power unexpectedly — this is not the failure of a single component but a system behaviour. To readers outside Formula One this may seem mysterious, but in engineering terms it is a familiar kind of problem: when software faces a state its designers never tested, the system behaves unpredictably.

The most notable element is the FIA's response. During the rain delay the body issued an over-the-air software update that removed the energy-limit constraint in the affected sectors. In other words, mid-race, in the middle of competition, the regulator applied a technical fix. This is a rare sight — a rule-maker appearing at once as legislator and emergency technical enabler.

From here a deeper question is born: if a software layer governing power deployment is configurable enough to be changed mid-race, then future disputes over consistency and equality between teams are inevitable. Today it is an emergency fix; tomorrow it may be the centre of a controversy.

The inversion: the problem is not in the software but in what went unseen

This is where my habit kicks in — when everyone looks at the software bug, I turn around and ask: where was the bug all this time? The answer is more uncomfortable. The issue was not caught in dry testing, because it manifests only in a specific combination of low speed, low grip and wet conditions. The FIA itself admitted a shortfall in wet-weather pre-season testing.

That is, the real failure is not in the software but in the scope of testing. If a system fails in a state nobody tested, that is not an accident — that is a systemic blind spot. This is why the incident cannot be dismissed as a mere technical glitch; it must be seen as a design-coverage failure.

This systemic strand has a real consequence. If the bug is not caught in dry testing, the same problem may return at another wet, low-grip circuit. This is not a one-race event; it is a possibility of recurrence.

In the same way, the drivers' reaction is an inseparable part of the story. The discontent that had accumulated since the start of the season over energy management here took the form of open ridicule. A sharp, mocking comment about the new-era cars — comparing the technology to a toy — is not just a joke; it exposes a fragility in the relationship between competitors and regulator.

Here I want to add a caveat, because in this kind of news the question of reliability is vital. The news report underpinning this analysis contains internal inconsistencies. In the title, the name of one Grand Prix and, in the dateline, the city of another country sit side by side — that is, 'Bahrain' and 'Malaysia' are conflated. Again, the same report places the Sepang race, the new-era cars, a driver's move to a particular team, and a four-time champion in the same text — timelines that are mutually incompatible. When these appear together, it suggests the text is probably garbled or composite. Any fact should therefore be checked against the original wire source before use.

Re-reading the context: governance and the economy of trust

In Formula One the regulator, the FIA, is not merely a rule-maker; it is also the guardian of the competitive environment. When cars almost stop mid-race, the question raised concerns not only safety but the regulator's capability. The FIA's technical side is fronted by Nikolas Tombazis, its single-seater director. In explaining the root cause, the body issued a detailed technical admission and pledged a full joint review with teams and power-unit manufacturers.

This is a deliberate posture of transparency — shifting attention from 'chaos' to 'root-caused and being fixed'. But even behind this transparency lies a strategic calculation. Fronting a technical director rather than institutional leadership sends a specific message: the problem is technical, and therefore so is its solution.

One more thing is notable in this context. Even before this incident, the season was being described as a 'difficult first season.' This suggests a deficit of trust had already accumulated, one that a single fix cannot erase. A mid-race software patch can pause the problem temporarily, but a season-long accumulation of discontent can only be eased by the report of a review.

Risk map: three layers

I prefer to see the risks of this incident in three layers. First, the safety risk, which is the most severe — cars almost came to a standstill on a wet formation lap. If speed drops suddenly and the car behind does not know in advance, the chance of a collision is created. Second, the regulatory risk — a condition-dependent bug that dry testing does not catch and that may return. Third, the reputational risk — elevated by drivers' public ridicule and season-long discontent.

Of these three, the least discussed but most enduring is the second. Reputation is repaired over time, a safety incident is confined to a single race, but an untested failure mode carries the possibility of returning at every wet weekend on the calendar.

A deeper chain of transmission

There is a subtle connection here that the media usually overlooks. The incident's origin is technical, but its effect reaches the broadcast product. When the start of a marquee race becomes chaotic and leading drivers are affected, the spectator experience is directly hit. That is, a problem at the software layer eventually becomes a problem of broadcasting and commercial product.

The chain can be seen this way: upstream sit the power-unit manufacturers and software; in the middle sit FIA regulations and race events; at the far end sit broadcasting and audience perception. A demand for intervention at the software layer produces a regulatory review in the middle, which determines the credibility of the 'new era' at the far end.

Formula One was never only a game of speed; it has always been a game of balance between rules, technology and entertainment. And that balance is now under test.

Takeaway: the next wet weekend will be the real answer

Any verdict now would be premature. The outcome of the joint review the FIA has pledged will determine whether the incident was an isolated glitch or a harbinger of a larger systemic crisis. If the review leads to a software fix and an expanded wet-condition testing protocol, the system will grow stronger. If the matter is simply covered with compensatory statements, the same incident will return at the next wet weekend.

Viewing this through a football-analytical lens, I find an analogy, though it is structural rather than substantive: a condition-dependent failure that manifests only in a specific combination — much as a team's tactic collapses in a specific match situation that nobody notices in normal conditions. The core lesson is the same: the failure you did not test for is the one that hurts you most.

So the question is no longer about software. It is now about the scope of testing — and how prepared the regulator is to widen that scope will determine whether that wet Sepang morning remains an isolated event in history, or stands as a warning.