©WRI2
Some things you just can't make up. Fernando Alonso's deployment issue in qualifying on Saturday was caused by the McLaren driver literally driving too fast for his Honda engine!
Honda's power unit deployment system is based on a throttle input algorithm which guesses where the car is located on the track, and deploys extra power accordingly.
When Alonso raced flat out for the very first time through Pouhon - a sweeping ultra fast double-left bend - on a hot qualifying lap in Q2, Honda's electronics were suddenly confused.
The deployment processors believed the car was still on the Liège downhill section, and therefore did not deploy the expected extra power as the McLaren exited Pouhon and sped towards Turn 12, the Fagnes chicane.
Alonso immediately reacted on the radio, furiously yelling he had 'no power', and subsequently aborted the lap and failed to make the Q3 cut in the process.
Honda F1 boss Yusuke Hasegawa later confirmed that the deployment issue was indeed linked to the engine's control system.
"We set a segment to when we have the deployment, and normally that segment is divided by the throttle," he told Motorsport.com.
"Sometimes a driver is making a different operation, so that makes the system confused and we didn't have deployment at some certain area."
Honda said it will change the system's procedures in order to avoid a repeat of the problem. And to keep Fernando Alonso from driving faster than his engine can think!
Gallery: The beautiful wives and girlfriends of F1
Keep up to date with all the F1 news via Facebook and Twitter
Max Verstappen’s racing curiosity has never been confined to Formula 1 – and now, one…
When F1’s radically redesigned 2026 cars finally roll out in Barcelona at the end of…
Max Verstappen has never been one to sugar-coat reality – and as Formula 1 braces…
Ferrari have survived decades of criticism about strategy calls, driver politics and pit stops that…
While the paddock has been whispering for months that Mercedes might be holding the winning…
Dan Gurney passed away on this day in 2018, and here at F1i we'll never…