Turn One in Austin, a Battery in Sepang, a Tenth in Singapore: Red Bull's Real Weakness Begins at Lights Out

Turn One in Austin. Isack Hadjar started third — matching the best qualifying result of his career — and by the time I looked back at the lap-one timing screen, he was not third. There had been no crash, no puncture, no contact. Just a car that had been on the front row on Saturday drifting backwards inside the first two hundred metres on Sunday. Afterwards he said the start had not been “nice,” and that whatever could not be fixed “in the last couple of days” was not going to be fixed at all.

That sentence is the key to this whole story. Because the easy read is that Red Bull's second car is slow. It isn't. In his own words the raw pace was “just great” and the Sunday race pace was ahead of expectation. What is keeping a fast car away from points is not aerodynamics — it is the lights going out.

Context

It is worth spelling out what a launch actually is, because the broadcast calls it a “bad start” and moves on, and the real thing gets lost there. A launch is the sum of three things: the clutch bite point (where the clutch engages and engine torque reaches the wheels), the torque and ERS deployment mapping (how much electric boost arrives, and when), and the drive-by-wire throttle (the electronic link between the pedal and the engine). Miscalibrate any one of them and the rear tyres spin — and positions lost to wheelspin in the first two hundred metres do not come back over a race distance, least of all at a circuit where overtaking is limited.

For Red Bull this is an odd place to be. Their lead car is winning races — Sepang and Singapore both went their way — so the team's competence is not in question. The question is about the second car, and the size of that question is measured in points. Look at the last three rounds: third to sixth in Austin with a throttle fault attached. A battery/ERS problem in Sepang that cost a podium. Tenth in Singapore behind technical trouble.

My frame is simple: I am not weighing this car's speed, I am weighing its conversion rate. A car that starts on the front row and cannot convert it into points is not fast — it is incomplete. The difference is that the incompleteness is not being manufactured in the factory. It is being manufactured on the pit wall.

Core

First and most important: this is a launch-execution defect, not a performance deficit. Hadjar separates the two himself — raw pace excellent, start poor. A performance deficit is what you fix with floor, wing and aero package. An execution defect is what sits in the set-up sheet and the clutch procedure. The two repair at different speeds, and that is the team's real problem.

Second: the pattern of the fix is the biggest clue. Hadjar says there were times when the team believed the starts were under control and then it went back the other way. Eleven years in performance departments taught me that this is the signature of one specific thing — an under-modelled variable, a factor the simulation is not yet capturing properly. A broken component behaves the same way every time. The thing that changes week to week — track rubber, temperature, the clutch's thermal state, grip at the grid slot — is exactly what makes a problem oscillate. The team is probably tuning one bite-point number while the model is mapping that number to the wrong conditions.

Third, and in my view the least priced-in part of this discussion: the radio. Do not file this under comfort. Modern race execution stands on the pit-to-car link — Safety Car and VSC response, undercut timing, energy management, brake and tyre modes. If the link drops intermittently, the entire reactive half of strategy is left to guesswork. Hadjar saying it is “a bit difficult to do a race without it” is soft language; in everyday language it means calls were made from half-arrived data rather than from eyes on the screen.

Fourth: put the battery and the throttle on the same line as the radio. Three consecutive rounds, same car, failures in electronic subsystems adjacent to the power unit — battery/ERS on one side, a drive-by-wire throttle on the other. That is not noise, it is a pattern, and in the homologation era such a pattern is expensive, because a fresh solution cannot be brought every weekend.

Mexico sharpens the equation. Mexico City sits at roughly 2,240 metres, where air density is about a fifth lower. Lower density degrades cooling — brakes and electronics both — and the track surface is at the bottom end of the grip scale, which makes wheelspin maximally punitive. Hadjar himself described the surface as “so slippery that you are just sliding around so much.” And the long run to Turn One cuts both ways: the same tow that offers an attacking opportunity makes you an easier target for anyone behind. A front-row-class car with a known launch defect at that circuit is the worst available combination.

There is a second trap: practice time is zero-sum. If the team spends real track time on launch rehearsal, it is taking that time from race runs and tyre preparation — at a circuit where grip is unusually low and the track evolves fast.

And a small piece of arithmetic: if the second car surrenders six to ten points a weekend to reliability, that becomes a constructors'-deciding margin by the end of the season, while never once appearing in Verstappen's win column.

Contrarian

Now the part where I have to stand against my own argument.

The strongest counter-case is that this may not be a car defect at all but a driver release profile. Front-row pressure is new for a young second driver. If there are two tenths of difference in how quickly the clutch is released, the screen shows exactly the same outcome a broken clutch procedure produces — lost positions. I do not have the data that separates the two, and I will not invent what I do not have.

Second, and this matters: the material I was given places Hadjar as Verstappen's team-mate and includes a Sepang round in the recent calendar. Neither is consistent with the published 2026 season — Malaysia last hosted a world championship round in 2026. So I am treating every figure here as scenario data, and I have built the argument so it survives either reading: a fast Red Bull, a repeatable launch defect, and a second driver who cannot be relied upon.

Third possibility I cannot dismiss: the team is deliberately not fixing this fully. In a late rules cycle with a major reset ahead, redirecting engineering attention away from launch maps and radio hardware toward the next car is rational. If that is what is happening, then “nothing could be done” is not a technical constraint — it is a priority decision, and it should be described as one.

Takeaway

In Mexico, one number matters to me: Hadjar's position after lap one. Lose two or more places and this is a seasonal defect that will follow the team into next year. Hold position and I will accept that they finally caught the under-modelled variable.

And when you watch the race, trust the commentary less — listen to the team radio. The silence in there is the real story of this season.