Skip to content

What Really Happened in Philadelphia 2026?

By Arich Knaub

Track conditions created more lapped traffic than usual. With only a few viable racing lines, if you can even call them that, it’s no surprise both front runners pointed to traffic as a major factor. And it’s not our first time posting about the subject this season.

Together, Ken Roczen and Cooper Webb lapped up to 5th place. Eight riders were lapped multiple times. That’s a significant number of extra passes in the shortened 17 minutes +1 lap Main Event. So, how did the extra traffic impact the race pace? And did Webb catch Roczen because of it?

First, establish the baseline, what each rider was capable of in the main event? Using lap time percentage, we can see the pace spread across the field. Unsurprisingly, the pace gap is massive.

Philadelphia 450SX: Lap Time Percents

One standout: Roczen’s fastest lap was the quickest of the race, set on Lap 8, about 44% into the main. Notably, it came on a lap that he lapped a rider on. Webb’s fastest lap came even later, on Lap 15, and required getting through two lapped riders.

The simple takeaway: Webb was strong late. That was obvious. What wasn’t obvious is how traffic shaped that outcome.

To quantify it, I reconstructed the race sector by sector using live timing. I tracked positions on a per sector basis, identified where the leaders encountered lapped riders, and counted passes per lap. From there, I grouped lap times by the number of lapped riders each leader faced.

Lap Time Averages per Number of Lapped Riders

On a clean track, both riders averaged in the 62s range, with Webb holding a slight edge. With one lapped rider, the advantage flipped. Roczen was, on average, 1.2 seconds faster than Webb. But in heavier traffic (2-4 lapped riders), it flipped again: Webb was quicker by more than 0.3 seconds per lap.

This aligns with what we’ve heard repeatedly by other racers: Webb’s racecraft is truly alien. He processes the track differently, and here, that translated into maintaining pace in denser traffic.

But does that explain the outcome? Was Roczen significantly delayed late, allowing Webb to close?

The next graph compares lap time to the number of lapped riders per lap.

Roczen vs. Webb Lappers & Lap Times

What stands out is Webb’s consistency. From Lap 6 onward, his pace barely fluctuated, outside of Lap 14. Roczen, however, saw a noticeable drop in performance from Laps 15–17, well off his earlier pace and average. During those 3 laps, he encountered and passed 7 lapped riders.

But Webb dealt with even more traffic in the same window: 9 lapped riders.

So how does that happen?

By that stage of the race, they weren’t just lapping the typical backmarkers, they were deep into the top 10. Guys like Dylan Ferrandis, Justin Barcia, and company are all riders who are fast enough to end up sandwiched between Roczen and Webb for multiple laps. So while both riders recorded 28 total passes on lapped traffic, the timing and context of those passes were completely different.

Ultimately, this level of analysis shows when traffic occurred and how much there was, but not exactly how it impacted each rider in the moment.

Its time to go deeper…

Ken Roczen in the Philadelphia mud. Photo: Garth Milan

The key question in this is where exactly did Roczen lose so much time on Laps 15-17 compared to Webb? Roczen, himself, blamed the lapped traffic.

To answer it, I broke each lap down by sector and compared every segment against each rider’s clean-lap average pace, a reliable baseline for potential speed without interference. What emerges is very clear.

Roczen: Time Loss Due to Traffic on Laps 15-17
Webb: Time Loss Due to Traffic on Laps 15-17

Two things stand out immediately for Roczen.

First, Lap 16 was the true time killer for Roczen. He lost 4.1 seconds total on that lap alone, with 4.4 seconds of that directly tied to traffic. Breaking it down further, he lost 2.5s to Cade Clason in S1 and another 2.0s to Scott Meshey in S4. As context, Meshey was lapped 5 times in this race, with a 126% lap time.

Outside of Lap 16, however, Roczen’s time loss due to traffic was minimal. Across Laps 15 and 17 combined, he lost just 0.3 seconds to lapped riders. The rest of the deficit through this span comes from self-inflicted pace loss, nearly 4 seconds tied to mistakes and execution rather than traffic.

So while lapped riders did play a role late, Roczen also gave back significant time on his own.

Webb’s story, in the most Webb way possible, is counterintuitive. Despite navigating more lapped traffic over the same window, he actually gained time (+0.4s) relative to his clean-lap baseline through Laps 15-17. Overall, he lost just 2.1s total, with 2.5s due to self-inflicted pace loss.

The takeaway is pretty clear. Roczen lost 4.8 seconds late in the race due to lapped traffic, but 3.8s on his own. Webb gained time through traffic, while losing 2.5 seconds on his own.

Webb began Lap 15 trailing Roczen by 8.2 seconds. By the end of Lap 17, that gap had shrunk to just 1.7 seconds. The rest was what we all saw on TV. Roczen kicked it into gear the final lap to secure the win.