Austin's Throttle, Sepang's Battery, Mexico's Turn 1: The Car Took Hadjar's Points, Not the Driver

On Saturday evening at COTA the timing screen held Isack Hadjar in third — a career-best-equalling qualifying. On Sunday evening the same screen had him sixth, and the team radio kept returning one word: throttle. My ledger has three rows for that weekend — qualifying P3, race P6, fault: throttle. Above it sits the Sepang row, where a battery cost him a podium; above that, Singapore, where 'technical problems' left him tenth. Three consecutive rounds, three electronic failures, and in the same window the team's other car won at Sepang and Singapore. The broadcast had a story. My spreadsheet had a timestamp.

First, the caveat that will not be wearing a swimsuit in this report: the supplied notes place Hadjar as Max Verstappen's Red Bull team-mate and treat Sepang (Malaysia) as part of the recent calendar. Malaysia last hosted a World Championship round in 2026, and Hadjar's publicly documented 2026 seat was at Racing Bulls. I am therefore treating every quantitative specific below as scenario data, pending verification. The argument does not depend on it, because the entity under analysis is not a name — it is a package with front-row single-lap pace, a repeatable launch defect, and a second driver whose weekends keep getting cut by hardware. Label the assumption now, because if the calendar reading changes the dates change; the pattern does not.

The uncontested part of the picture: the car is quick over one lap and quick on Sunday. Hadjar called the raw pace 'just great' and the Sunday pace 'great'. The deficit is not in the performance curve. What falls between a P3 Saturday and podium-capable Sunday pace is procedure — clutch bite point, torque and ERS deployment mapping, drive-by-wire throttle behaviour, and the quality of the pit-to-car radio link. The team is not hiding it: the driver says the team is aware of the weakness and names two items, starts and radio quality.

Where F1 normally trades qualifying against race pace, here the loss is concentrated in the first 400 metres — an execution deficit, not a performance deficit. The lap-1 position drop at Austin is the cleanest proof. It is also where my data runs out: no launch times, no count of positions lost, no sector deltas, no lap-time set. What exists is driver description — the getaway 'was not nice', the car was sliding, the track had little rubber. I do not discount it; driver language usually agrees with telemetry. I will not call it a count.

The real clue is not the fault but the behaviour of the fix. Hadjar says there were times the team believed the starts were under control, and then it went the other way. In engineering terms that is not the signature of a broken component; it is the signature of an under-modelled variable — clutch thermal state, rubber level on the grid slot, track temperature, the driver's release profile. One of those changes at every circuit and breaks the correlation. When a team repeatedly 'solves' a launch and loses the solution, the root cause is usually a variable nobody controls. [Confidence: Medium]

Mexico City is the worst possible test, because 2,240 metres of altitude cuts air density by roughly a fifth and leaves the grid short of grip as well as downforce. Lower density means every torque overshoot at launch costs more wheelspin, and it also degrades brake and electronics cooling — a separate headache for the same car that has logged battery and throttle complaints in three straight rounds. The driver described the surface as so slippery 'you are just sliding around', and noted a good tow at the start. A tow cuts both ways: the slipstream that offers an attack makes the car easier to pass for anyone behind with a marginally better launch. Front-row pace plus a known launch defect is the worst combination this circuit can offer. [Confidence: High that altitude is the dominant Mexico variable; Low that the team has a specific countermeasure]

I keep reliability in a separate column, because the broadcast folds it into the same story. A start is an execution problem; a throttle and a battery are hardware problems. Battery/ERS, an unspecified technical failure and a drive-by-wire throttle across three consecutive rounds on one car are all power-unit-adjacent control electronics, and that is a narrow place to be under homologation. It is a pattern, not noise. My estimate — and it is an estimate, not a measurement — is that 6 to 10 points lost per weekend on the second car is title-deciding in a tight constructors' fight, and invisible in a win column.

Radio is not a comfort item. Safety Car and VSC response, undercut timing, brake-tyre-ERS management all run on real-time engineer input. A degraded link raises the probability of a reactive strategy error, and a late Safety Car call costs positions, not tenths. The driver framed it structurally: difficult to do a race without it. Mechanically, radio hardware sits largely in control electronics and spec-adjacent territory, so the fix is an operations task, not a development-allowance one.

There is a practical squeeze that gets under-reported: practice time is zero-sum. Mexico has low grip and large track evolution, so every useful Friday minute is expensive. Real launch work costs race-run and tyre-prep time. The driver has already conceded nothing could be done in the last couple of days and the team goes with what it has. That is rational under the constraint set, and it also means the team is deliberately arriving at the highest-start-risk circuit with a known start defect. His own framing is defensive — he will adapt, and he is happy if they can minimise the damage. Damage limitation from a front-row car inverts the usual Red Bull expectation. I have no hard basis to claim the internal target is points preservation rather than a podium, but the word choice points there. [Confidence: Medium]

Hadjar himself is being under-read by results. P3 to P6 with a throttle fault at Austin, a battery fault costing a podium at Sepang, P10 in Singapore behind technical trouble — that is a three-round pattern in which the car, not the driver, ate the points. On the evidence available his qualifying and Sunday pace are genuine. The sample of strong sessions is small, and I will not swap a full-season column for it.

One media-behaviour detail is unusual: the weakness is being named publicly by the junior driver, not by engineering or management. The language targets process, never people; praise is always redirected to the car's pace, and there is not a syllable of complaint about Verstappen. For a young second driver at a top team that is disciplined but pointed — and it suggests internal acknowledgement without an internal owner.

Now the audit against my own thesis. The easy story is 'Hadjar is inconsistent, the second Red Bull seat is cursed'. I hold that to the same standard. First, the lap-1 position loss at Austin is execution and belongs in the driver's ledger; because the count is not recorded I will not inflate it. Second, attributing the launch defect to the car may be premature: release profile and clutch feel are driver variables, and the team's other car starts normally — an inconvenient fact that speaks against my conclusion. If the fault is seat-specific, a large part of the problem becomes driver-in-the-loop calibration and the 'team weakness' report is only half true. [Confidence: Low-to-Medium — this is the joint with the least data]

What cannot be counted I file as input rather than noise: the political pressure on a second seat, whose name attaches to a fix that keeps failing, and the experience of a paying spectator watching the race change before the first corner. The numbers do not describe the mood on that grid.

The oldest habit in my archive: the eye test is a hypothesis; I keep the receipts. The receipt says this car's biggest risk is not its pace but its first 400 metres — and in Mexico those 400 metres will be the most expensive part of the weekend.

My interim ledger for Mexico watches three things and reports them separately: the number of launch runs in FP1 (I expect it unusually high, because real track time will go to testing rather than set-up), positions held to Turn 1 (two lost from P3 means a structural problem, one means execution), and radio-link continuity (a late call under Safety Car is the true measure). I am setting a date for that verdict — 72 hours after the race — and I will publish it whether it agrees with me or not. I publish weekly, errors included, because the archive is the argument.

The question is not whether the Red Bull is fast. It is. The question is why a team with front-row pace keeps finding itself in damage-limitation mode after lights-out. Mexico's first corner will answer it, and if it does not, next season's first launch will.