The Second ADUO Token Is Spent and Singapore Still Had Lag: Honda's Problem Isn't Hardware, It's Control

The complaint Fernando Alonso filed after Marina Bay was not about a crash, a puncture or a wrong strategy call. He said the car has the power, but the power is not arriving at the moment he needs it. In an Aston Martin garage, that is the most expensive sentence available. Driveability does not appear in any column of a timing sheet — not in best lap, not in sector time, not in top speed. I have been running the same Excel template since 2026: car number, session, best lap, delta to pole, tyre age. It has never had a column for driveability. That is precisely why something like turbo lag escapes the team's simulation tools and only surfaces as a question after the race. Aston Martin's Malaysian weekend had gone better than expected. The result at Sepang sat above the team's own forecast, and that forecast was carried into Singapore. On paper, the Marina Bay street circuit looked suited to the AMR26 — low-speed corners, traction zones, a demand for mechanical grip. A team that has just over-delivered tends to build the next race's budget on that over-delivery. Singapore did not pay out. Performance fell short of expectation, and after the race Alonso pointed directly at the power unit's driveability. Honda did not treat it lightly. Both the engineers and the power units went back to Sakura for deeper investigation. The finding was that there was no specific hardware fault. What there was, was turbo lag — the time the turbo takes to spool up, and therefore the gap between pressing the accelerator and feeling the turbo respond. That is not a new ailment. It was one of the factors that hurt driveability with the new power unit specification introduced at Zandvoort. And it was for exactly that reason that Honda spent its second ADUO token of the year in Madrid, fitting a new turbocharger whose only job was to eliminate the problem. Here is a commercial fact that never makes the race report. ADUO is not an engineering shortcut; it is a quota. Limited, non-renewable, usable only a handful of times in a season. When you spend your second token on a component designed to kill one specific problem, and that problem returns three races later, it is not merely a technical disappointment. It is expenditure on an asset whose return could have been measured and was not. I stopped reading lap times the day I started reading depreciation schedules, and that instinct applies here. The turbocharger is a cost, the token is the payment, and Singapore was the invoice. Honda's chief trackside engineer Shintaro Orihara, speaking to Motorsport.com, admitted the problem returned unexpectedly in Singapore. In his words, even with the new turbocharger fitted to manage lag, controlling that lag remained difficult because of the unique track layout and the energy-rich situation, which gave the driver unstable acceleration. This is where the story stops being technical and becomes commercial. The hardware was fine, and the car still did not behave. Which means the thing that failed was not the part — it was the operating window the part was run inside. Orihara was also asked whether MGU-K deployment in different places than usual could partly compensate. His answer was clear: it helps to a degree, but not enough to offset the lag, and the MGU-K had contributed to the problem in a different way. Read his explanation plainly and it is a supply-and-demand problem. On an energy-rich track, teams normally use MGU-K harvesting to compensate for turbo lag. With enough harvesting power, the engine can sit at a high operating point through off-throttle sections, the turbo keeps spinning, and the next throttle application does not feel delayed. But on a lap where energy demand outruns harvestable supply, gathering enough harvesting value becomes difficult. Then the engine's operating mode is insufficient to keep lag under control. According to Orihara, that is exactly what happened at Singapore. That raises the most uncomfortable question. Finding no specific fault during the Sakura checks is itself a concern, because it implies the same issue can return the next time Aston Martin visits an energy-rich circuit. Honda stressed that lessons have been learned and countermeasures are being prepared — not in hardware, but in how the power unit is operated through software and settings. Orihara said they have learned things from Singapore and are preparing countermeasures, that they understand turbo lag control must improve, that current control is not meeting driver demands, and that they still need to check how those measures behave on the power unit. That sentence deserves close reading. When a manufacturer says the fix lives in software and remains to be validated on the power unit, it is saying the solution is unproven. That is honesty, and it is the same honesty as last time — when lag appeared at Zandvoort, the answer was a new turbocharger. Now the answer is new control maps. The logic is identical both times: the problem is tied to a track characteristic, so the real test will come at the same track type. Which is why Honda's claim is currently correct on paper and untested on track. Mike Krack's contribution goes well beyond a technical note. He called it emotional dynamics. Sepang surprised the team in terms of outcome, and that raised the expectation level for Singapore beyond what was realistic. When you fail to deliver against it for various reasons, everyone becomes disappointed and the weekend itself gets harder. That is not psychology; it is risk management. A weekend should carry a list of risks — tyre degradation, traffic, setup window, power unit delivery. In Singapore that list was not built, and Krack admitted as much. He also conceded that simulation cannot produce a clear picture here. If there is lag, or what Orihara described about the MGU-K stopping, how much does that cost you in driveability — that goes beyond simple sensitivity simulations. In my experience, this is where the spreadsheet goes quiet. The spreadsheet never shouts; it just keeps the receipts until you ask. But anything that generates no receipt — like delay under the driver's foot — never shows up in the budget and then becomes the largest cost of the weekend. The least popular part comes now. The weakest link in this whole episode is not the turbocharger. It is that a team entered a weekend without a risk register, despite having three seasons of data on how this power unit behaves on street circuits. Second, treating the absence of a hardware fault at Sakura as proof that no hardware fault exists is a leap that is cheap on the dyno and expensive on track. A dyno cannot reproduce Marina Bay's lap-by-lap energy profile. So 'no fault found' does not mean 'no fault exists'; it means the fault is not where we looked. Third, spending a token is not a disaster if the lesson transfers. If the software-based measures Honda is now describing actually work, the token was not wasted — it was the price of expensive information, and in a regulatory era where upgrades are counted, information is the real currency. But if those measures also fail in Austin, the question stops being about turbo lag and becomes whether Honda's diagnostic process is pointed in the wrong direction entirely. One excuse is technique; two is process. That is where Aston Martin's real test sits. Krack said the team must regroup after such an event, understand where it lost out, take the right learning, and manage expectations better — or at least, when managing them, hold a set of risks that could affect the outcome, which they did not do in Singapore. That sentence sounds less like a race engineer and more like someone from a finance team. And perhaps that is why it will work. When the stands went empty, the spreadsheets got honest — true of gate receipts, and equally true of power unit delivery. The question ahead is not whether Honda's new turbocharger is good or bad. It is whether a manufacturer can adapt its power unit to a track layout thoroughly enough that the driver feels no delay at all. Austin gives the first clear answer, but the real answer will come at the next energy-rich circuit. Until then, one thing is worth recording: the gap opening up this season may not be created by components, but by the control maps that run them. And control maps have no balance sheet — which is why they are the last thing anyone notices.