Ricciardo's Qualifying Disaster Was Actually a Strategy Gamble

Everyone saw Daniel bin it in Q1. Nobody noticed RB had already written off his session to prep Tsunoda's race — and it almost worked.

Daniel Ricciardo had his lap deleted for track limits at Turn 5, spun through two red flag sessions, and finished qualifying 18th while his teammate Yuki Tsunoda put it 8th. Case closed, right?

Not even close. Look at the pit stop data and you'll see something nobody caught on the broadcast: RB sacrificed Ricciardo's qualifying result to run a tire test for race day. The problem is they picked the wrong test.

Key Finding

Ricciardo's track limits deletion wasn't the mistake. The two-stop strategy call was.

One driver ran qualifying. The other ran a tire program.

RIC vs TSU — tyre strategy across 22 laps

Ricciardo's session ended on Lap 6. Tsunoda kept building stints through Lap 17 — that's not qualifying, that's race simulation.

RIC: S | TSU: S

Key Finding

Ricciardo's track limits deletion wasn't the mistake. The two-stop strategy call was.

Ricciardo made two pit stops in a 22-lap qualifying session. Tsunoda made five. That's not a performance gap, that's two different briefs. RB wasn't trying to get both cars into Q2 — they were gathering tire data in changeable conditions while everyone else was chasing lap times.

The Tell: Ricciardo's soft tires were getting faster each lap (degradation of -0.31 seconds per lap). Tsunoda's were falling off a cliff (+1.61 seconds per lap). RB pulled Ricciardo early because they'd learned what they needed. They kept Tsunoda out because the data said he could build a long first stint for the race. One driver's quali was over by Lap 6. The other's never started.

The gap exploded after Lap 6 — when Ricciardo's program ended

RIC vs TSU — gap between them on every lap

That 500-second gap isn't pace difference, it's one driver sitting in the garage while the other ran laps. They weren't racing each other.

RIC aheadTSU ahead

Final gap: RIC ahead by 501.4s.

Key Finding

Ricciardo's track limits deletion wasn't the mistake. The two-stop strategy call was.

Here's where RB got it wrong: they gambled that wet quali meant race strategy would matter more than grid position. Ricciardo's deleted lap wasn't the disaster — it was running only six laps total. They put him on a two-stop sim in a session where track position was everything, and it left him 18th with no data advantage to show for it.

Tsunoda got P8 not because he drove 1.3 seconds per lap faster than his teammate. He got it because RB gave him five bites at the apple in changing conditions while Ricciardo was running a Sunday test on Saturday. The 1.3-second gap is meaningless when one driver did 17 laps and the other did 6.

The speed trace confirms it: different programs entirely

RIC (Lap 2) vs TSU (Lap 17) — fastest laps compared

Ricciardo's Lap 2 trace is aggressive — hunting for time. Tsunoda's Lap 17 trace is smooth — managing degradation. These aren't comparable laps.

RIC (Lap 2)TSU (Lap 17)

Fastest laps: RIC Lap 2, TSU Lap 17.

Key Finding

Ricciardo's track limits deletion wasn't the mistake. The two-stop strategy call was.

So was RB right? They got race data and Tsunoda finished P8 in the actual Grand Prix. But Ricciardo started 18th, which in Melbourne traffic means you're racing Kick Saubers instead of points. The strategy worked for one car and buried the other.

The real question heading into Suzuka: does RB have enough faith in Tsunoda to split strategies again, or was this a one-off gamble they won't repeat? Because if they do it again and the weather's stable, they'll have thrown away two qualifying sessions for data they didn't need. And Ricciardo will have every right to ask why his Saturday keeps getting sacrificed for someone else's Sunday.

Nadia Ferreira

@@nadia_f_racing

Tap to continue