Grid penalties for engine changes have produced some genuinely absurd starting orders, and the fix is obvious

SMSofia Marchetti· posted 3w

A grid penalty is what a driver gets for exceeding their season's allowance of power-unit components, ten places per extra part, stacking if they change several at once. The system exists for a real reason: without it, teams with bigger budgets would simply fit a fresh engine every weekend and treat the whole allocation rule as a joke. In principle it's a reasonable way to force teams to manage reliability across a season instead of buying their way around it. In practice it has produced results nobody designed on purpose. At one recent Grand Prix, the fastest qualifier in the whole session started fifteenth because of a ten-place drop, while a driver who was genuinely the slowest car on the grid that weekend started ahead of him, because his own penalty happened to be large enough that it didn't trigger the same relative drop under the stacking rules. That's not a driver being punished for going over his allocation, that's a driver being punished more than a driver who went over his allocation by even more. The fix other paddock voices have floated is simple: cap every penalty at a flat ten places regardless of how many components were changed, and require anything beyond one swap to just start from the back outright. No more stacking math that can accidentally reward the bigger offender. The Race's proposed fix lays out exactly how the current system produces these upside-down results.

2 2

Replies2

MLMathis Leclerc· 3w

Cycling doesn't have anything this specific, but every sport with a stacking-penalty system eventually finds the same loophole, because whoever wrote the rule wasn't thinking about the edge case where two penalties interact badly. The fix's always the same too: flatten it, stop trying to be precise about degree and just pick a blunt, predictable number.

BDBram de Vries· 3w

Genuine question though, doesn't flattening it just create the opposite unfairness, where a driver who changed one component gets treated identically to a driver who changed four? The current system is trying to be proportional, it's just failing at it in this one specific stacking scenario. Maybe the fix is fixing the stacking math specifically rather than throwing out proportionality altogether.