Not a Lego Race, an Untested One: How the FIA Software Failure Exposed a Governance Blind Spot

On a wet formation lap, when the cars came close to a standstill on the track, a single phrase rising from the paddock took over every channel on social media: "Lego race." The mockery spread at the speed of lightning. But when I sat down to arrange the race tape, the FIA technical statements and the teams' radio messages one after another, I understood that the mockery was not the story. The story was a governing body that forgot to test a condition. The scoreline said chaos; the tape said something stranger.

I have been watching sport and writing for many years—from the football pitch to the motorsport paddock, I carry one habit in both places: if there is no number, I do not write an opinion. And the number that troubled me most this race weekend was not a lap time. It was zero—the number of relevant faults caught in dry testing.

The Heavy Burden of a New Era

Since the 2026 ground-effect regulations, the phrase "new era of cars and engines" has become one of the heaviest burdens in sports journalism. Every season begins with a promise: closer racing, more overtaking, more entertainment. But the gap between promise and reality is filled by technical consequences—and this season has been labelled a "difficult first season" from the start.

The power unit—the hybrid engine, where a fuel-driven engine and electrical components work together—has drawn public driver dissatisfaction over its energy management since the season opener. This is not a one-day event; it is an ongoing cycle. When names like Lewis Hamilton and Max Verstappen publicly criticise the new rules, it is not merely a reaction to one race; it is a crisis in the relationship between an entire generation of cars and its drivers.

And standing in the middle of that crisis is the FIA—motorsport's global governing body. In its hands lie the technical regulations, the race director's decisions, and the ultimate responsibility for safety. What FIFA or UEFA is to football, the FIA is to motorsport. The difference is one thing—here the question is not breaking or obeying a rule, but the boundary lines of software and sensors.

How the Software Failed

Now to the story of the tape. The incident happened on a wet formation lap—that pre-race lap where cars move slowly to take their grid positions. At that very moment the cars suffered an "unintended loss of power." The cars came close to stopping.

The FIA's initial explanation was unusually specific. Behind the problem lay the interaction of four variables: low engine speed, low-grip conditions, energy-management settings configured for wet weather, and the specific sector layout of the circuit.

Looked at separately, none of these is a problem. But together they create a combination in which the software restricts the engine's energy distribution in a way no one predicted. The problem is not the failure of any single component; it is the failure of the combination of components. And this kind of failure is caught only when all the relevant conditions occur together.

There is a technical subtlety here worth noting. The energy management of a modern power unit is a software-controlled layer—where energy recovered under braking is allocated for use in later acceleration. That allocation depends on the car's speed, the track's grip, and which sector of the circuit the car occupies. On a wet track, grip falls, speed falls, and the calculation of energy recovery changes. If the software cannot correctly estimate this altered equation, a shortfall appears in the distribution—and that shortfall is exactly what the driver feels as a loss of power.

A Fix in the Middle of the Race

When the race was suspended due to rain, the FIA took an extraordinary step. It removed the energy-limit constraint in the affected sectors via software—an over-the-air update that reached every team's car during the race itself.

Structurally, this is an "in-race fix"—it has a structural resemblance to a coach changing the system mid-match in a field sport. But the resemblance is only structural, not substantive. Here the decision was taken by a race director who applied the authority of the technical regulations to intervene in a live competition. In football, a referee cannot change the rules mid-match; here the governing body itself suspended a technical parameter temporarily.

That intervention is the biggest signal. Because it proves that there is a configurable software layer governing power deployment—one that can be changed at any time, in any sector. On one hand, this capability opens a path to a solution; on the other, it raises a new question: if the parameter can be changed, then who controls which team is running which setting?

Where the Real Gap Lies

But here is the real question. If the problem was so specific, why was it not caught in pre-season?

According to the FIA's own admission, the bug could not be identified in dry testing. In other words, the testing programme did not adequately simulate wet conditions. The institution itself has admitted there was a shortfall in wet-condition testing in pre-season. This is a rare self-criticism by an institution—and at the same time the most important information.

The bigger failure than a caught failure is a system in which the failure is not caught. It is normal for software to have bugs. But a condition-specific bug escaping the testing process is a failure of the process, not of the technology.

I want to add a number here, because without a number this claim does not stand. Wet-condition testing is a hard constraint—the track can be artificially wetted, but the combination of real rainwater, temperature and grip is almost impossible to fully replicate. So many teams naturally prioritise dry testing. But this constraint is not the cause of the problem; it is the excuse for the problem. Because a wet race is a familiar reality in the terminal—it is inevitable, not conditional.

The Safety Risk

The most serious consequence of this process failure is safety. When cars are nearly stationary on a wet formation lap, the risk of collision with cars coming from behind is real. On a formation lap, speed is low, visibility is low, and the track is wet—when these three coincide, a small fault can turn into a major accident.

In my assessment, this risk is the most deserving of attention—more than financial loss or reputational damage. Because reputation returns, but a safety incident does not.

The Pressure of Reputation

But the reputational side is not to be ignored either. The drivers' public mockery—"battery-powered cars," "Lego race"—is a signal that reveals the fragility of the relationship between regulator and competitor. When players publicly mock the product, it is not just dissatisfaction; it is a crisis of trust.

The FIA answered this pressure in a specific way. It pledged a joint review with teams and power-unit manufacturers. And this message was delivered by a named technical authority—Nikolas Tombazis, the FIA's single-seater director.

Fronting a technical director to explain the failure is a deliberate message-management move. It shields the institution, and at the same time places the responsibility for the decision on a technologist's shoulders.

I went back to the Croatia call expecting noise; I found architecture. Here too. I went back to the paddock expecting mockery; I found a process gap, its every brick laid out for future risk.

How I Could Be Wrong

Now to the part where I must stand against my own argument.

First possibility: perhaps the problem is not the process but the car's design. If the new energy-management system is structurally weak, then no matter how much testing is done, the problem will return. In that case the FIA's software patch is a temporary fix, not a permanent one. My argument would then be proven wrong—because I blamed the process when the problem was in the technology.

Second possibility: perhaps the drivers' mockery is the real signal, and I underweighted it. If the new-regulation cars are fundamentally uncompetitive, then the reputational damage is not temporary; it is structural. Then the "testing gap" explanation becomes a convenient excuse—one the institution is using to protect itself.

Third possibility: reporting confusion. The description of this incident contains geographic and chronological inconsistencies—here the Bahrain Grand Prix, there Sepang, and at the same time hints of multiple time periods. If this confusion is a sign of the weakness of the original source, then the basis of my every conclusion is also in question.

I take all three possibilities seriously. Because every hot take is a hypothesis wearing a deadline—and a hypothesis's dignity depends on how much risk of being proven wrong it is willing to take.

The Road Ahead

So what comes next?

I am making a dated prediction, because a prediction without a date is not a prediction. If the FIA's joint review cannot update the software and the wet-testing protocol before the next wet race, then a similar power-loss event will return at the next wet event. And if that happens, the drivers' mockery will turn from a joke into a permanent element of long-term criticism.

The second thing I am watching is whether the joint review exposes divergence in team-level software configurations. If each team's setup is different, a new kind of debate will arise in the future—a debate about consistency.

And third: driver-regulator relations. If public criticism escalates, it will become a crisis of trust in the product. And once trust in the product is lost, no software patch can bring it back.

An empty stadium does not silence football; it amplifies what we ignored. Here too. If the mockery is noise, then beneath it lies a question—one that the next wet race will answer.