The Token Was Spent, the Lag Wasn't: What Honda's Singapore Weekend Actually Cost Aston Martin

At Turn 13 of the Marina Bay Street Circuit, Fernando Alonso's right foot was already flat on the throttle before the car answered. The response came — a fraction late. On television it reads as half a second of hesitation. Inside the cockpit it is the gap in which the car says “wait” and the wall says “no”.

That delay is not a driving error. It is the spool-up time of a turbocharger, and it is the least interesting part of this story.

The interesting part is this: Honda spent its second ADUO token of the 2026 season in Madrid specifically to delete that delay. A new turbocharger went on, with a clearly stated purpose. Two races later, in Singapore, the lag was back. On paper the fix was filed. On track it wasn't.

I followed the token until it turned into a turbocharger, and what I found at Sakura was not a broken part. That is the headline.

Context: what a token buys, and what it doesn't

Under the 2026 power unit regulations, ADUO — Additional Development and Upgrade Opportunities — is a parity instrument, not a prize. A manufacturer sitting below a defined performance threshold receives a limited number of extra upgrade allowances in a season. It is easy, and wrong, to read it as a fix budget. It is the same logic as wind tunnel and CFD allocations under the cost cap: the resource is finite, the count is public, and every spend carries an opportunity cost.

Honda put its first token into the new specification introduced at Zandvoort. That same specification began the driveability complaints — the gap between the driver's foot and the car's response, a gap that does not show cleanly in telemetry. The second token went in Madrid, aimed squarely at the same problem: a new turbocharger intended to eliminate the lag.

Sepang produced a better result than expected. Aston Martin's chief trackside officer Mike Krack calls these “emotional dynamics”, and the word is chosen carefully. Sepang raised the expectation level. Singapore looked, on paper, like a fit for the AMR26 — street circuit, traction, mechanical grip, few high-speed sections. What happened was the reverse.

Singapore's importance was never only sporting. Street rounds are the calendar's most expensive events: hosting fee, city contract and ticket price all point upward. Bringing a car that answers late out of slow corners to a round like that is commercially costly too, because the deficit shows in every session from Friday's time sheet to Sunday's race.

Core: no broken part at Sakura — which is the bad news

Honda sent both its engineers and its power units back to Sakura after the race. The checks revealed no specific hardware fault. What emerged instead was that the manufacturer was primarily struggling with turbo lag — the time it takes for the turbo to spool up, and therefore the delay between pressing the accelerator and feeling the turbo bite.

The problem is not new in itself. It was one of the factors that hampered driveability with the specification introduced at Zandvoort. That is precisely why Honda used its second token of the year in Madrid. Asked by Motorsport.com, Honda's chief trackside engineer Shintaro Orihara conceded the issue had returned unexpectedly in Singapore.

“Even though we introduced a new turbocharger to manage turbo lag, we still struggled to manage that lag in Singapore because of the unique track layout and also the energy-rich situation. That has given some unstable acceleration to the driver,” Orihara said.

The technical detail here is not decoration; it is the engine of the story. Asked whether MGU-K deployment in different places than usual could partly compensate, Orihara said it works only to a certain extent.

“MGU-K deployment can help [against] turbo lag, but not enough to compensate for it,” he said. “If we go to energy-rich tracks, we normally use the MGU-K harvesting to compensate for turbo lag. If we have enough MGU-K harvesting power, then the engine can run at a high operation point in the off-throttle sections. That helps turbo lag and is nice, but if we go to energy-rich circuits, sometimes it's difficult to get enough MGU-K harvesting value because of the energy-rich situation. In that case, the operation mode of the engine is not enough to control turbo lag and that's why we struggled at Singapore.”

Read plainly, that means an energy-rich lap is one whose electrical demand outruns what harvesting returns. When the MGU-K itself is drained, it stops being the tool that masks lag. Singapore's layout problem and Singapore's energy problem were not separate failures; they were two faces of one calculation.

Finding no fault at Sakura is not reassurance. A broken part has a part number, a lead time and a return date. A control problem has none of those. That is why Honda's remedy sits in software and settings rather than hardware — and why it will have to be re-proven at the next energy-rich circuit, because it cannot be proven on a dyno.

“Yes, we have learned some things from Singapore, so we are preparing countermeasures for the future,” Orihara said. “We understand that we need to improve our control of the turbo lag. At the moment, our control is not meeting the driver demands, so we apply some countermeasures. But again, we need to check how those work on our power unit.”

Where simulation ends, the race begins

Krack's contribution is managerial rather than technical, but the effect is the same. He attributes the Singapore disappointment partly to expectations that had climbed beyond what was realistic.

“I always call them the emotional dynamics,” he said. “I think Sepang probably surprised us in terms of outcome and it raised the expectation level [for Singapore] maybe even beyond what was realistic. And when you do not deliver it for various reasons, then everybody becomes disappointed and it gets more difficult over the weekend.”

The sharper admission is that driveability cannot be fully captured by simulation tools. “It is something that in simulations you cannot really have this clear picture,” Krack said. “How much will this cost you, for example? If you have lag or what Orihara was mentioning about the MGU-K stopping, and how it affects the drivability. This goes beyond simple sensitivity simulations.”

This is where a technical story becomes a ledger story. Under the cost cap, every team has a fixed pool of wind tunnel and CFD hours, and those hours go into aerodynamics — because aerodynamics can be measured. Driveability cannot be measured, so it lives in the part of development no spreadsheet fully captures.

And where does the damage land? Precisely at the circuits that create the energy-rich condition — the street rounds, which carry the calendar's most expensive tickets and largest hosting fees. Every constructors' championship position feeds directly into F1's prize money distribution, where Column 1 pays on historical performance and Column 2 on current standing. Points lost in Singapore are not merely points; they are a line in next year's budget. All of this inside a partnership whose entire commercial logic rests on Aston Martin having a works power unit.

Contrarian: a token is a permit, not a cure

Reading ADUO as “Honda gets to fix its engine” is the easiest mistake available. The rule was written to hold a parity line, not to generate performance. Parity instruments do not produce speed; they produce permission. Once the token is spent, the question is no longer whether Honda tried — the new turbocharger in Madrid is the proof of effort. The question is whether a token can ever buy the thing tokens cannot buy: track time.

In an era of testing restrictions, the real currency of calibration is not money but calendar. This problem is cheap in cash and expensive in weeks. Honda can fix it in software, but proving the software requires race weekends, and race weekends do not refund points. A development allowance is really a story about who can afford to be patient; here the manufacturer can, and the team cannot.

The second mistake is assuming that because no part broke, Honda is simply behind. Keep the two claims apart: the performance deficit is real, and the method of correcting it — tokens, simulation, calibration — is a separate argument. What failed in Singapore was not an engine but a control loop.

The third mistake is the European lens. We pass judgement on a power unit at Zandvoort, Barcelona and Madrid, while the calendar's energy-rich rounds — Singapore, and several street venues to come — sit outside that frame. Honda's real examination will not take place in Europe. It will take place where harvesting runs short.

Takeaway

Austin is next, and Honda arrives with countermeasures it has not yet fully validated on its own power unit. The most honest line Orihara offered was the simplest: “we need to check how those work.”

The question is not whether Honda spent its Madrid token in the right place. The question is whether a regulation that hands out upgrades but not proving time merely moves failure from the dyno to Sunday. In Singapore that failure passed close to the wall. Whose name does it get filed under next?