Ahead of Mexico, Red Bull's Real Weakness Exposed: Hadjar Says Both the Launch and the Radio Need Fixing

Mexico City (Sports Desk). In Formula One, having a fast car and converting it into a fast result are not the same thing — and this season that truth keeps leaking out of Red Bull's second cockpit. What Isack Hadjar said ahead of the Mexico City Grand Prix is not the grumble of a frustrated driver. It is a rare, disciplined public admission from a team whose car can win races but whose race starts keep stopping it from doing so. In Hadjar's own words, the car's raw pace was "just great" while the start "was not nice."

Inside the Red Bull engineering room, this is already on record. Hadjar said plainly that the team is aware of the weakness. But the gap between awareness and a solution is precisely Red Bull's problem right now. At Austin, a driver who qualified third dropped down the order on lap one and finished sixth. The car had speed. The qualifying lap was there. The Sunday race pace was there. Only the first 300 metres after lights-out went wrong.

"Nothing could have been done in a couple of days"

Between Austin and Mexico there was very little time. Hadjar admitted that "there was nothing that could be done in the last couple of days" that would cure the start at its root, and that the team would therefore "go with what we have." Journalistically that sentence says two things at once. First, the team is not hiding the problem. Second, it has accepted that the problem will not be solved in a single weekend.

There is an important nuance here. This is not procrastination; it is a pragmatic call made within a known constraint. A launch is the combined product of four things — the clutch bite point, torque delivery, ERS deployment mapping and the driver's release profile. Change any one and the other three react. And as soon as the circuit changes, so do grip level, track temperature and the state of the rubber. A solution that works at one circuit can invert itself at another.

Crucially, the team has not given up. Hadjar's stated intent was to reproduce the good starts it has had before. But that is exactly where the difficulty begins: you can only "reproduce" something if you know why it worked the first time. And in this car's case, that knowledge does not appear to exist.

Austin: third to sixth, and not only because of the throttle

Austin was two different stories stitched into one weekend. On Saturday, Hadjar matched his career-best qualifying position — third. That was a statement in itself, because when one Red Bull is winning races, the sight of the other on the front row tells you the car's single-lap pace is not theoretical. Hadjar said he was fighting for pole.

Sunday changed the picture. At lights-out he was shuffled backwards. Then a throttle problem struck during the race. Sixth at the flag. Look only at the result and it reads as an acceptable weekend — sixth scores points. Look at the sequence and the story is different: a car starting third finished sixth, and at least part of that was a failure the team already knew about.

It is essential to split this into two parts, because the team will split it too. The first part is the launch — a shared failure of driver and procedure, one that could have been addressed. The second is the throttle fault — a hardware or software failure the driver cannot prevent. Putting both into one account is wrong; but putting them into separate accounts and declaring the weekend fine is also wrong.

The launch is an operational defect, not a performance deficit

This is the single most important line of the entire analysis: Red Bull's problem is not how fast the car is, it is how the car is operated. Hadjar separated the two cleanly — raw pace was excellent, the start was not. Once that distinction is understood, everything else falls into place.

A car that can reach the front row on Saturday and run with strong race pace on Sunday is not a slow car. It is simply a car that cannot convert its pace into points at the start. In Formula One that gap is enormous. If the car were slow, the solution would be obvious — upgrades, wind tunnel time, a new floor, a new rear wing. But when the car is fast and the start is bad, the solution hides somewhere far more awkward: in procedure, in calibration, and in variables the team does not control.

So Hadjar saying the car's pace was excellent is not consolation. It is a diagnosis. And it should not comfort the team, because it means the deficit will not be closed with money — only with time and attention.

What gets fixed and then regresses — the biggest signal

The sharpest part of Hadjar's statement was not that the start was bad. It was that the team has repeatedly believed it had the starts under control, and then it went back the other direction. In engineering language that describes a calibration loop that is not yet correlated with the track.

When a team repeatedly improves one thing and the improvement repeatedly rolls back, it usually means the team is fixing a variable that is not the real variable. It is rarely a broken part. It is an uncontrolled variable — the amount of rubber laid down, track temperature, the clutch's thermal state, humidity, altitude, or the driver's own release profile. The team is applying a static solution to a moving surface.

The direct consequence is that in Mexico the team cannot trust a Friday practice start that looks good to stay good on Sunday. The surface in Mexico City will behave nothing like Austin's, and the data collected in Texas will not be comparable.

Reliability: three rounds, three different electronic wounds

If the launch is Red Bull's most visible problem, reliability is its most expensive one. Across the last three rounds Hadjar's car has broken in some way each time, and each time differently.

First, Sepang, where a battery problem took away a possible podium. Second, Singapore, where the race ended tenth amid technical problems. Third, Austin, where the throttle ruined the race. Treat these as three unrelated incidents and you will draw the wrong conclusion. Three consecutive rounds, the same car, and each time a failure close to the electronics or software is a pattern, not noise.

There is a technical subtlety here. A battery/ERS complaint and a drive-by-wire throttle complaint both sit in electronic subsystems adjacent to the power unit, where homologation rules limit what can be changed. Diagnosing the problem is one thing; fixing it mid-season is quite another. That makes this a rules-book problem as much as an engineering one.

The constructors' consequence is direct. If the second car keeps losing six to ten points a weekend to reliability, that is a title-deciding deficit in a tight fight — and, most dangerously, it is invisible in Verstappen's win column.

The radio: a strategy problem, not a comfort problem

Hadjar listed two weaknesses — the starts and the radio quality. The second can look trivial at first glance. It is not. He said himself that doing a race without it is "a bit difficult" — that is not a driver's comfort complaint, it is a structural limitation.

A large part of modern race execution happens over the radio: reacting to a Safety Car or VSC, undercut timing, tyre temperature management, brake temperature management, ERS mode usage, defending against cars behind. If that link intermittently degrades, the risk is not discomfort — the risk is that the team reacts late under a Safety Car and the strategy goes wrong.

Technically there is something interesting here. Radio hardware sits largely in control electronics and standard-parts territory, which means fixing it is an operations and infrastructure task, not a development-allowance task. Nobody needs to touch the aerodynamics. And that makes it more uncomfortable, not less: something that could have been fixed relatively easily has gone unfixed for three rounds.

Tyres and degradation: insufficient information

One honest caveat. The underlying analysis contains no meaningful tyre data. Compound choice, track temperature, stint length and degradation mode are all absent. The only signal is "great pace on Sunday" and "raw pace was just great."

That signal matters because it indicates the car's strength is not confined to qualifying — it is competitive over a long run too. But saying more than that without data would be speculation, and this report will not speculate.

The physics of Mexico: 2,240 metres

Now to the circuit where this story continues. The Autódromo Hermanos Rodríguez sits roughly 2,240 metres above sea level, where air density is about a fifth lower. That is not a trivia point; it rewrites the technical picture.

First effect: downforce. Thinner air means wings generate less force, so teams run bigger wings. Second: grip. The surface becomes slippery, and Hadjar described it exactly that way — so slippery the car is sliding around. Third: cooling. Thin air degrades brake and electronics cooling. Fourth: drag. Lower density cuts drag, which amplifies the tow.

Put those four together. On one side, a team brings a car whose launch is already weak. On the other, that team arrives at a circuit with low grip and high slip. On low grip, the smallest error in clutch and torque delivery magnifies wheelspin, and wheelspin means lost positions. Meanwhile degraded cooling in the electronics is an added risk for a car that has seen battery and throttle failures in three consecutive rounds.

Plainly: Mexico is the least favourable circuit on the calendar for Red Bull's two known weaknesses. Both get amplified at once.

The run to Turn 1: the weekend's single biggest exposure

Hadjar highlighted two Mexico-specific things — the long run to Turn 1 and the good tow available at the start. Both are true, and they are two sides of one coin.

The tow is an opportunity: pick up the slipstream from the car ahead and you arrive at the braking zone level with it. But the same tow is available to the car behind you. If your launch is weak and the car behind has even a marginally better one, the long run becomes a trap. You will be caught.

That is why starting third with a known launch defect is the worst possible combination at this circuit. Losing a position here is not just losing a position, because overtaking is limited. If what happened in Austin — losing places on lap one — repeats in Mexico, coming back will be far harder.

And this is where Hadjar's second sentence becomes significant. He said he would try to adapt and would be happy if the team could minimise the damage. That is not the language of a front-row driver. It is the language of a driver who already expects to lose places at the start and to have to recover. For a team like Red Bull that is an inversion of the objective — points preservation rather than a podium push.

The zero-sum practice problem

Here is an angle that often goes unnoticed. A Formula One weekend has limited track time. Across both Friday sessions a team must cover race set-up, tyre preparation, long-run data and qualifying simulation. If it also has to practise starts, it has to give something else up.

When the start is solved, two or three launch runs are enough. When the problem keeps returning, the team must run repeatedly — different clutch settings, different bite points, different release profiles — and that time comes directly out of race running. In Mexico that cut is the most expensive of all, because grip is low and track evolution is enormous: Friday's surface will differ sharply from Sunday's, and data collected early in a session can be obsolete by the end of it.

So every minute of Red Bull's Friday running in Mexico carries a price, and the team must choose between giving time to the start and giving it to race pace. It cannot have both.

Hadjar's performance is being under-read by results

Now the driver at the centre of the story. Read the results page: sixth in Austin, a lost podium at Sepang, tenth in Singapore. That looks like a driver under pressure. Read the reasons and the picture changes.

In Austin he started third and finished sixth with a throttle fault. In Sepang a battery failure cost him a podium. In Singapore technical problems left him tenth. Three rounds, three times the car pulled the driver back rather than the other way round.

One thing must be said clearly: losing places on lap one is a driver-and-procedure failure. A broken throttle is not. Lumping them together is unfair to Hadjar. On the other hand, the sample of strong sessions is still small, so the claim that his pace is genuine is a medium-confidence claim, not a settled conclusion.

What is clear is this: Red Bull's second cockpit currently holds a driver who can put the car on the front row and deliver race pace on Sunday, and whose results page understates him.

Verstappen's dominance and the internal balance

Max Verstappen's role in this picture is straightforward. He has won recent rounds, and that alone proves the car retains race-winning capability. When the number one driver is winning, there is no ambiguity about team orders. The risk on that front is low.

Interestingly, Hadjar did not say a single negative word about Verstappen. He consistently redirected praise to the car's pace. That is discipline, and it looks deliberate.

But there is a signal here worth noting. The person publicly naming the team's weakness is its most junior member — not engineering, not management, but the second driver. His words were that the team knows the weakness and that radio quality needs to improve. That statement points at process, never at people.

That is informative in itself. It implies the problem has been acknowledged internally but has no internal owner. A defect everyone knows about and nobody is solving is the defect that lasts longest.

The constructors' cost: a calculation nobody sees

In a constructors' fight, two cars matter. If one is winning and the other is losing six to ten points a weekend to reliability and starts, that gap can be decisive by the end of the season.

The most awkward part is that the loss is invisible. The wins column looks fine. The press release looks fine. But the gap in the standings stays there. And if the championship is lost by a handful of points, people will go back and ask where those points went — and the answer will be in Sepang's battery, Singapore's technical problems and Austin's throttle.

What to watch

Four things will matter in Mexico.

First, Friday practice. If Red Bull spends a large share of its programme on launch runs, the team is treating the problem seriously and betting on race pace. If it does not, the team has already conceded.

Second, the post-qualifying message. If Hadjar again reaches the front row and again talks about minimising damage, the internal target has shifted.

Third, radio quality. It is not visible on track, but the team's reaction under a Safety Car will reveal whether the link has been fixed.

Fourth, and most important, the first lap. If Hadjar holds his position to Turn 1, the entire weekend can change. If he does not, it becomes the next chapter of the longest-running technical story of the season.

Conclusion

Red Bull's car is fast. There is no doubt about that. Verstappen's wins prove it and so does Hadjar's qualifying pace. But the bridge between a fast car and a win is weak right now — and that bridge is the start.

The most important fact of this season is not how fast the Red Bull is. It is that the team recognises its biggest weakness, admits it, and still cannot fix it. A mistake once is an incident. A mistake that keeps returning is a system. And fixing a system requires changing priorities, not parts.

Mexico gives the team another chance to set that priority. The question is whether it will be used, or whether at the end of the season the line will be: nothing could be done in the last couple of days.

---

Data verification note: Two elements of the underlying analysis require verification. First, Isack Hadjar is presented as Max Verstappen's Red Bull team-mate, whereas in the publicly documented 2026 season his seat was at Racing Bulls. Second, a Sepang (Malaysia) round is presented as part of the recent calendar, whereas Malaysia last hosted a World Championship round in 2026. The cause is unclear — this may be an alternate or forward-looking season dataset, a composite article, or an entity-attribution error in the initial analysis. All quantitative specifics above should therefore be read as "scenario data — pending verification." The conclusions hold under either reading: a fast Red Bull with a repeatable launch defect, and a reliability-hit second driver.