Interlagos 2026: How the Rain Erased the Data Model, and Verstappen Walked Through the Gap

The rain at Interlagos does not fall on schedule. It came late on Friday, returned early on Sunday, and by the moment the organisers decided to postpone qualifying to the morning of 3 November 2026, every model I had built across the season had turned into scrap paper. I sat in front of a screen in Melbourne at three in the morning, and the first thing I looked at was not the leading car. I looked at the starting grid column. Max Verstappen was seventeenth.

Seventeenth. At a race where, for years, the winner had almost always started from the front of the field, that number is not a statistic. It is a question. And in this profession, a good question is always worth more than a readily available answer. Every race is a network; I simply look for the knot. That night, the knot was not in the fastest car. It was in the weather, in the moment a red flag was raised, and in the way one driver read a gap that our software could not compute.

Context: A season stretched to its limit

Round 21 of the 2026 Formula 1 season took place at the Autódromo José Carlos Pace, the circuit the industry still calls Interlagos. It was a sprint weekend, meaning only one official free practice session, and most of the car set-up data had to be locked in very early. For a team, this is a data nightmare: you enter a weekend with very little calibration time, and you must accept a margin of error.

What matters is the seasonal context. After several years of stability under one technical regulation set, the gaps between teams had been compressed. The leading group was no longer a full second per lap ahead of the chasing pack. The drivers' championship still leaned toward Verstappen, but the safety margin was far thinner than in the two previous seasons. Every point became more expensive, and every strategic mistake could flip an entire chapter of the season.

Interlagos is not a beautiful circuit in any aesthetic sense. It is a short, tilted, anti-clockwise loop, climbing through the Senna S before dropping down a long straight. Its geometry creates two characteristics I always note before a race. First, the gaps between cars tend to compress because the long straight is enough to generate a slipstream. Second, the braking zone at Turn 1 is where every mistake gets magnified. In the dry, this is a trade-off between downforce and top speed. In the wet, it becomes an entirely different problem.

I have spent many years watching races and have concluded that every strategic model carries a hidden assumption: that the track surface is a constant. When it rains, that constant disappears. And when the constant disappears, the entire reasoning structure above it collapses with it. This is why I always tell younger colleagues to learn dry-race analysis first, but to learn humility in wet races.

Core analysis: The red flag, the timing, and the geometry of a comeback

Qualifying was moved to Sunday morning. Verstappen was eliminated in Q2 and then received a grid penalty for taking a new internal combustion engine. He began the race from seventeenth. Under any model trained on dry data, his win probability at that moment was near zero. But the race did not begin on a dry surface.

The first knot was not Verstappen's speed, but the structure of the contest when the red flag appeared. When a race is stopped for a red flag, the entire order is reset. The gaps the leading drivers had built are erased. Cars that had pitted for tyres, for a new wing, or for repairs get a chance to rejoin the midfield. In the dry, a red flag is a rare event that usually benefits only a few. In the rain at Interlagos that year, it became a door thrown open for those who had chosen wrongly and needed another chance.

I watched the red-flag sequence several times. What stood out was not the chaos, but the order within the decision-making. Verstappen did not try to swim upstream in the early phase. He held position, held his tyres, and waited. On a slippery surface, passing five cars in three laps sounds great on paper, but in reality it is the fastest way to lose the car into a wall. So he did not pass. He waited for the structure of the race to open.

When a second red flag came out after another incident, the order was reset once more. And this is where the strategic geometry becomes clear. The cars ahead had pitted, changed tyres, and locked themselves into their order. The cars in the middle were pulled closer together in terms of distance. Verstappen was there, on relatively fresh tyres, in a group where he no longer had to pass each car one by one around the lap. He only had to exploit the gaps the reset created.

There is a detail few commentators noticed: in the wet, the optimal strategy is not the fastest strategy, but the least wrong one. Every time a driver runs off-line to overtake, they buy a probability of error. Every time a team calls a car into the pits a lap too early or too late, they buy a probability of losing position. In a dry race, both probabilities can be approximated by a model. In a wet race, they are almost impossible to estimate. Whoever understands this chooses to let the race open the way for them.

The second knot was the unusually symmetrical leading group: two Alpine cars finished second and third. To anyone who followed the season, this is a statistical anomaly. Alpine was not a team with the average pace to stand on a dry podium. But in a wet race, the finishing order no longer reflects pure pace. It reflects three things: the right pit call, the ability to keep the car on the road, and luck in avoiding collisions.

I recall pausing on this detail for a long time. In my dry-data model, the gap between Alpine and the leading group was a number large enough to exclude the team from any podium scenario. In wet data, that number loses most of its meaning. This is the lesson every data analyst must face at least once: the data is not wrong, but it only answers the question it was generated to answer. Dry data was never generated to describe a flooded Interlagos.

As for Verstappen, what he did after taking the lead was the hardest part. Holding the lead on a slippery track is a different problem from taking it. The leading driver is responsible for the water they touch, while those behind can benefit from the already-broken water trail. It is a reverse geometry: the leader's advantage becomes a burden when the surface is slippery. He managed a gap of nearly twenty seconds late in the race to avoid a mistake, and that was a decision of discipline rather than a display of speed.

A note on the technical baseline. The regulations in force in 2026 had been stable for some time, so teams no longer had much room for large aerodynamic leaps. During that period, technical advantage was mostly won through small details and through understanding tyres better. In a wet race, technical advantage is compressed almost to zero because every car runs below the limit of the wet tyre. When chassis performance is levelled, the decisive factor shifts to people and to the decision-making process. That is what happened.

Another angle I always note in the right-hand column of my notebook: the opportunity cost of each strategic decision. A team that pitted a car before the red flag spent a pit stop for nothing while exposing the cars behind. A team that waited too long lost position to those who gambled more. In the dry, these two decision groups can be balanced by a probability model. In the wet, waiting is itself a decision, and sometimes the best one.

I do not want to turn this piece into a dry table of numbers. But there is one number I still keep in mind: about twenty seconds. That was the final gap between a car that started seventeenth and one that started from the front of the field. That number does not tell a story about speed. It tells a story about a man who understood that in the rain, it is not speed that decides, but the order of decisions.

The human factor: What the data sheet does not record

There was a moment in the race I cannot compress into a chart. When Verstappen completed the decisive lap and took the lead, the grandstand at Interlagos rose to its feet. That roar is not in my telemetry data. But it tells me something about the atmosphere: that people were witnessing something they would retell years later.

This is why every analysis I write has its own section for the human factor. A driver's body language stepping out of the car, the silence in the pit lane, the way a strategist holds their headset after calling a pit stop wrongly. None of it appears in any data table, yet it explains most of what happens afterwards. On the tactical map, emotion is a coordinate people forget.

I once ignored this factor while advising on recruitment, and I had to write a long self-criticism to remind myself of the lesson. Since then, I never draw a tactical conclusion without reading back the human part of a race at least once.

The counter-intuitive angle: The hero and the shadow of randomness

The story told most often after this race is the story of a great driver. And he deserves it. But if I stop there, I have missed part of the truth. Most of the miracle at Interlagos came not from Verstappen going faster than everyone, but from the structure of the race being broken twice by red flags. Those two moments pulled him from seventeenth to near the leading group without a single head-to-head overtake.

This is the blind spot in how we tell sports stories. We look for a hero because a hero is easier to tell than a system. But the data at Interlagos that year shows something else: if the red flag had not appeared, or had appeared a few laps earlier, the result could have been entirely different. That does not diminish the performance. It merely places it correctly within the network.

If I must say what few want to hear: this victory is not proof that Verstappen can win from seventeenth in all conditions. It is proof that he best understood how a wet race gets restructured, and that he responded to that restructuring faster than anyone. That is a different skill, no less impressive, but not the skill the crowd's story is telling.

There is a counterfactual I always pose when analysing a race like this: if the red flag had not come, and if the track had been as slippery as forecast, where would Verstappen have finished? My answer, after reviewing the data, is: hard to say, and possibly not on the podium. That is not a way of belittling the performance. It is a way of honouring it with the truth. The diagram does not lie, but the person reading it does.

A forward-looking conclusion: What to verify at the next race

After Interlagos, the biggest question for me is not who wins the title, but how teams will adjust their decision models before weekends with uncertain weather. Will they accept that dry data cannot be extrapolated to wet data, and will they dare to keep the car on track instead of diving into the pit lane out of model reflex? Data is a shelter, but the story is home.

At the next race with similar weather, I will watch three things: when the leading group makes its pit calls, how the cars behind handle the water at Turn 1, and whether anyone dares to choose the least-wrong strategy instead of the fastest one. If they do, we will know that Interlagos taught the whole industry something.