The Data Behind George Russell’s Engine Software Failure That Ruined His Hungarian GP Start

George Russell’s difficult Hungarian Grand Prix weekend was made even worse by a Mercedes engine software malfunction that caused an abnormal rev surge on the starting grid and ultimately led to his slow getaway.

The British driver had already endured a frustrating build-up to the race after Mercedes was forced to replace his engine following a technical failure on Saturday. A water leak caused by striking a kerb damaged the power unit beyond repair, meaning the team had to install a new engine before Sunday’s race.

However, despite the fresh hardware, Russell was hit by another problem when the lights went out. A launch system failure triggered the anti-stall mechanism, causing him to lose several positions immediately and adding another setback to what had already been a difficult weekend.

The incident perfectly summed up Russell’s disappointing first half of the season. After the race, the Mercedes driver admitted that he needed the summer break to reset mentally after a campaign where frustrating circumstances had often prevented him from achieving the results he believed were possible.

The Hungarian Grand Prix was a reflection of those struggles. Russell’s issue was not simply a lack of pace, as he acknowledged that even under normal circumstances a top-three qualifying position would have been difficult to achieve. Instead, his weekend was damaged by a combination of reliability problems, mistakes, and unfortunate situations that repeatedly worked against him.

What Caused Russell’s Slow Start?

The launch failure that triggered the anti-stall system became one of the defining moments of Russell’s race. Initially, Mercedes appeared to suspect that the problem may have been caused by driver input.

Team engineers noticed that Russell seemed to briefly reduce his throttle application while preparing for the start, at a moment when the engine was already running at high revs to create the necessary turbo boost.

However, further analysis showed that Russell’s throttle movement was not the cause of the problem. Instead, it was a reaction to an issue that had already developed inside the car.

Mercedes team principal Toto Wolff explained after the race that the engine behaviour was abnormal and outside Russell’s control.

“It looks like he gave about 10% throttle and the whole thing revved maximum, he went off the throttle and it popped down,” Wolff explained. He later added that the number of reliability problems and technical difficulties Mercedes had experienced during the opening part of the season was unacceptable.

The telemetry data supported Russell’s explanation. The driver confirmed that while preparing for the start, he noticed the engine revs suddenly increasing in a way that did not match his throttle input.

Russell explained that he was holding the engine at the required rev level when, approximately four seconds before the lights went out, the engine suddenly began revving unpredictably. He attempted to correct the situation through throttle adjustments, but the engine was no longer responding normally.

“The engine wasn’t reacting to the throttle,” Russell said, explaining that his actions were an attempt to control the malfunction rather than the reason it happened.

How the Launch System Was Supposed to Work

Formula 1 drivers must carefully manage their throttle position before the start of a race. The goal is to maintain the correct engine speed and build sufficient turbo boost without allowing the revs to become too high or too low.

Drivers receive information directly through their steering wheel displays, including indicators showing whether the engine speed is within the ideal range for launch.

A comparison between Russell and Mercedes teammate Kimi Antonelli showed just how different their situations were.

During the preparation phase before the start, both drivers followed the normal procedure and reached around 30 percent throttle. Antonelli’s engine remained stable, holding approximately 12,300rpm as the lights came on.

Russell’s car, however, behaved completely differently.

The engine speed began climbing beyond the expected level, rising above 12,700rpm and briefly reaching around 12,800rpm. This was unusually high and forced Russell to react by reducing his throttle input.

The telemetry showed that Russell attempted to calm the engine by lifting almost completely off the accelerator. His throttle position dropped from around 30 percent to below 10 percent while the lights were still red.

But the adjustment did not solve the issue.

For a brief moment, the engine speed dropped below 12,000rpm before rising again to approximately 12,600rpm, even though Russell was applying less than 10 percent throttle.

This left the driver in a difficult position when the race began. Unlike Antonelli, who was able to maintain around 30 percent throttle for the launch, Russell started with significantly less power available.

How the Anti-Stall System Was Triggered

When the lights went out, Russell attempted to launch the car while holding only around nine percent throttle. Because the engine was not producing enough power, the revs dropped sharply.

At clutch release, Antonelli’s engine speed remained around 5,800rpm, allowing him to make a clean getaway.

Russell’s engine, meanwhile, fell to approximately 4,500rpm.

With insufficient drive being produced, the Mercedes anti-stall system activated automatically. The system is designed to prevent the engine from shutting down completely during situations where the revs fall dangerously low.

Although the technology prevented a full stall, it severely compromised Russell’s start. He lost valuable positions immediately and was forced to recover throughout the rest of the race.

The incident was particularly frustrating because Mercedes had apparently encountered a similar issue during pre-season testing in Bahrain.

Russell acknowledged that the problem was not completely new, although he was unsure about the exact details.

“It was obviously a brand-new engine. I think it was something we had seen in pre-season at one point, but I have no idea,” he said.

Another Difficult Weekend for Russell

The Hungarian Grand Prix became another example of how small technical problems can have major consequences in Formula 1. While Russell’s pace was not enough to challenge the very front of the grid, the engine issue added unnecessary difficulty to an already challenging weekend.

Instead of focusing purely on performance, Mercedes was forced to deal with reliability concerns and operational problems.

For Russell, the summer break arrived at an important moment. The driver has shown strong pace throughout the season but has often found himself losing opportunities due to circumstances beyond his control.

The Hungarian GP highlighted those frustrations once again. A damaged engine, a launch failure, and lost track position combined to create another race where Russell was left wondering what could have been.

As Mercedes looks ahead to the second half of the season, resolving these reliability issues will be crucial. For Russell, the goal is simple: return from the break with a more competitive and dependable package that allows his ability behind the wheel to determine his results rather than unexpected technical failures.