Software Glitch, Not Driver Error: How a Rogue Engine Map Sabotaged George Russell’s Hungarian GP Start

George Russell’s Hungarian Grand Prix ended in frustration before it had truly begun, as a technical glitch left the Mercedes driver almost stationary on the grid. The incident, which triggered the car’s anti-stall system and cost him several positions, was initially suspected to be a driver error but has since been confirmed as a software issue with his brand-new power unit. This mishap capped off a difficult first half of the 2026 season for Russell, who admitted he needs a break to recharge after a series of setbacks.

The Chain of Events: From Kerb Strike to Grid Stall
Russell’s troubles began on Saturday when he struck a kerb, causing a water leak that destroyed his engine. This forced Mercedes to install a new power unit ahead of Sunday’s race, meaning Russell started from the back of the grid due to penalty charges. However, the new engine brought its own set of problems.

On the grid, during the critical launch sequence, Russell’s engine began to rev erratically. Over the team radio, engineers initially suggested that Russell may have lifted off the throttle prematurely, a common mistake that can disrupt the build-up of turbo boost. However, post-race analysis of telemetry data tells a different story.

Telemetry Reveals the Truth
Team Principal Toto Wolff clarified that the issue was technical, not human. "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 expressed dissatisfaction with the frequency of such errors, labeling the reliability issues in the first part of the season as "unacceptable."

Russell corroborated this, stating, "I was on the throttle holding the revs, and then all of a sudden, about four seconds before the lights went out, the engine just started revving all over the place. And I was reacting with my throttle, and it wasn't doing anything. So, the engine wasn't reacting to the throttle."

A comparison with his teammate, Kimi Antonelli, highlights the severity of the glitch. During the five-second preparation phase, both drivers applied approximately 30% throttle. Antonelli’s engine held steady at around 12,300 rpm. In contrast, Russell’s engine surged past 12,700 rpm, peaking at 12,800 rpm. In an attempt to correct this, Russell lifted his foot, dropping his throttle input to below 10%. Despite this, the engine continued to behave unpredictably, dipping below 12,000 rpm before surging again to 12,600 rpm, completely unresponsive to his inputs.

The Anti-Stall Trigger
When the lights went out, Russell was left with only 9% throttle, far less than the 30% required for a proper launch. As he attempted to release the clutch, his engine speed plummeted to 4,500 rpm, compared to Antonelli’s stable 5,800 rpm. Lacking sufficient torque and revs, the car’s safety systems intervened, triggering the anti-stall mechanism and leaving Russell stranded momentarily as the rest of the field sped away.

A Recurring Nightmare
Russell noted that this specific issue was not entirely new, recalling a similar occurrence during pre-season testing in Bahrain. "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 admitted.

For Russell, the Hungarian GP was a microcosm of his recent struggles. Even without the engine failure, he acknowledged that a top-three qualifying spot was unlikely given the car’s pace. However, the accumulation of bad luck and technical failures has made the first half of the season particularly taxing. As F1 heads into its summer break, Russell will be hoping that Mercedes can resolve these software gremlins, allowing him to return for the second half of the season with a reliable car and a renewed sense of confidence.