How a Bizarre Throttle Glitch Derailed Yuki Tsunoda's Dutch GP Race

Why it matters: Yuki Tsunoda's strong performance at the Dutch Grand Prix was unexpectedly compromised by a technical glitch, highlighting the critical nature of software settings in modern F1. Despite the setback, he managed to secure points, showcasing his resilience.

The details:

• Tsunoda's car got stuck in an incorrect "launch mode" throttle map after his final pit stop, a scenario prohibited from being changed on track by FIA rules implemented in 2020 to prevent 'party modes'.
• Team Principal Laurent Mekies confirmed the car was "locked into the wrong map," forcing Tsunoda to drive with a "not friendly throttle map."
• This specific map meant throttle response between 15% and 40% pedal travel was severely flattened, optimizing for a launch rather than sustained racing performance.
• Tsunoda radioed "I don't have power," and was instructed to try and adapt during a safety car period, as the issue could not be fixed outside the pit lane.

The big picture:

• F1 regulations since 2020 limit engine modes to one from qualifying onwards, with exceptions only for stationary cars (engine off), wet races, or in the pitlane.
• Drivers typically switch to 'launch mode' in the pitlane and back to standard mode after their stop; Tsunoda's failure to execute the switch immediately locked him into the wrong map.
• Despite the significant disadvantage, Tsunoda finished ninth, only 4.1 seconds behind Lance Stroll, whom he had pitted ahead of.

What's next:

• Mekies estimates Tsunoda could have finished seventh under normal circumstances, stating, "Honestly, there is not much you can say on the pace, because he was probably glued in traffic for most of the race."
• While frustrated, Tsunoda acknowledged the team minimized damage and found some confidence in scoring points under such difficult conditions.
• The incident underscores the tiny margins and complex systems that can make or break a race result in Formula 1.