GP-News.net

  • F1 News
  • F1 races
    • Formula 1 Australian GP
    • Formula 1 Chinese GP
    • Formula 1 Japanese GP
    • Formula 1 Bahrain GP
    • Formula 1 Saudi Arabian GP
  • F1 teams
    • McLaren
    • Red Bull
    • Ferrari
    • Mercedes
    • Aston Martin
    • Alpine
    • Audi
    • Haas
    • RB
    • Williams
    • Cadillac
  • F1 drivers
    • Arvid Lindblad
    • Max Verstappen
    • Lewis Hamilton
    • George Russell
    • Lando Norris
    • Oscar Piastri
    • Charles Leclerc
    • Carlos Sainz
    • Sergio Perez
    • Fernando Alonso
    • Lance Stroll
    • Alex Albon
    • Franco Colapinto
    • Nico Hulkenberg
    • Esteban Ocon
    • Pierre Gasly
    • Valtteri Bottas
    • Zhou Guanyu
    • Oliver Bearman
    • Kimi Antonelli
    • Gabriel Bortoleto
    • Isack Hadjar
  • F1 legends
    • Ayrton Senna
    • Michael Schumacher
    • Alain Prost
    • Niki Lauda
    • Sebastian Vettel
    • Jackie Stewart
  • F1 interviews
  • F1 videos
  • F1 history
  • Advertise
  • F1 store
  • Home
  • Formula 1 results and calendar
  • Formula 1 Driver Standings
  • Formula 1 Constructor Standings
Home » Max Verstappen blames Red Bull software limit for lost Madrid pole chance

Max Verstappen blames Red Bull software limit for lost Madrid pole chance

Max Verstappen, Red Bull RB22, 2026 F1

Max Verstappen believes a Red Bull software limitation prevented him from mounting an even stronger challenge for pole position in Madrid, after the four-time Formula 1 world champion qualified third for the Spanish Grand Prix. The Dutchman was fastest through the middle sector but lost decisive time in the final part of the lap, where he said the RB22 could not deploy electrical energy in the way he wanted.

Lando Norris ultimately produced the fastest time in his McLaren MCL40 despite making an error at the final corner, while Max Verstappen finished 0.140 seconds away from pole. The Red Bull driver made no attempt to hide his frustration afterwards, insisting the deficit was not caused by tyre performance but by the way the car’s energy deployment was being controlled.

Max Verstappen loses ground in Madrid’s final sector

The 2026 qualifying trend continued at the Madring, with Mercedes-powered machinery once again at the front as Lando Norris delivered an exceptional final lap. Max Verstappen could only manage the third-fastest time overall, despite producing the quickest sector of anyone through the middle part of the circuit.

The final sector proved decisive. Red Bull had already shown signs of losing performance there during practice, with Madrid telemetry highlighting Max Verstappen’s substantial loss towards the end of the lap before qualifying.

In Q3, Max Verstappen again gained strongly through the middle sector before surrendering time over the closing sequence. According to the Red Bull driver, however, this was not simply a balance issue or the result of running out of tyre performance.

Red Bull software prevents energy deployment change

“Our software is limited and that holds us back a little,” Max Verstappen said. “We don’t have the correct energy deployment in the third sector. I wanted to change it, but we can’t.”

The problem underlines how important electrical energy management has become under Formula 1’s 2026 technical regulations. At the Madring in particular, the interaction between corners taken at or near full throttle and the deployment strategy around the rest of the lap has emerged as a major technical factor.

Ferrari faced a similar need to understand how driver inputs affected energy usage during practice, with the team even encouraging Lewis Hamilton to take Madrid’s Turn 12 flat-out as part of its deployment work.

For Max Verstappen, the frustration was that he believed the tyres still had enough performance to complete the lap strongly. The limitation instead came from the amount and distribution of electrical energy available in the RB22.

“It’s not because of the tyres that we’re losing in the third sector,” Max Verstappen explained. “The tyres could push all the way to the end, but we don’t have the right energy deployment.”

Max Verstappen left frustrated after qualifying third

Asked whether the situation had left him disappointed, Max Verstappen again returned to the same technical limitation.

“Am I frustrated? As I said, I would have liked a different energy deployment, but it wasn’t possible to have it.”

Red Bull’s deployment limitations have already emerged as a recurring theme during the 2026 season, adding another difficulty to an RB22 that has not always allowed Max Verstappen to extract his usual advantage. A wider look at the weaknesses Max Verstappen has faced with the RB22 shows how the Dutchman’s season has increasingly been shaped by the technical characteristics of the car.

Madrid provided another example. Max Verstappen had enough performance to be a genuine factor in the fight for pole and was particularly strong through the middle sector, but without the energy deployment he wanted over the final part of the lap, Red Bull could not convert that pace into the fastest qualifying time.

Sep 12, 2026John Matthews
Kimi Antonelli narrowly misses Madrid pole as Lando Norris snatches top spot by 0.011sLando Norris stuns himself with ‘one of my best-ever laps’ to claim Madrid pole
You Might Also Like
 
Aston Martin’s back-of-the-grid derby: Lance Stroll and Fernando Alonso’s “private” battle in Japan
 
Isack Hadjar quietly solves Red Bull’s second-driver problem alongside Max Verstappen

Leave a Reply Cancel reply

John Matthews

John Matthews is a seasoned motorsport journalist with over a decade of experience covering Formula 1

2 months ago F1 News, Formula 1 Spanish GP, Max Verstappen, Red Bull2026 Formula 1 season, Madring, RB223

Ferrari F1 latest news and updates

Recent Posts

  • George Russell’s painful 2026 F1 season: How bad luck, mistakes and Kimi Antonelli shattered his title dream
  • Honda admits it cannot identify Aston Martin battery failure cause as 2027 F1 concerns grow
  • Max Verstappen reveals 2027 Nürburgring and Spa 24 Hours plans but rules out Le Mans for now
  • Carlos Sainz slams Pirelli’s F1 wet tyres after Brazilian GP aquaplaning problems
  • Ralf Schumacher delivers brutal George Russell verdict with Kimi Antonelli and Barrichello comparison

Mercedes F1 news

Partners

ScuderiaFans - Ferrari news and updates

Contact us

About us

Our writers

Privacy Policy

Advertise with us

Terms and Conditions

© 2024 GP-News Ltd. All Rights Reserved
GP-News Ltd, 199 Republicii Street, 5A
Ploiesti, Romania, 100392

@ Copyright 2024 GP-News.net | All Right Reserved
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}