The Ledecky-McIntosh Rematch Is a Pacing Story, Not a Speed Story

The Pan Pacific Championships run August 12 to 15 in Irvine, and the race with the most eyes on it is Friday's women's 400 freestyle: Katie Ledecky against Summer McIntosh, the two swimmers who have traded the world record and Olympic hardware in this event for the better part of a decade (NBC Sports).

The history is worth a sentence, because it explains why this particular 400 is a rivalry rather than just a fast heat. Ledecky set the world record at 3:56.46 at Rio in 2016 and held it for six years. Ariarne Titmus took it in 2022. McIntosh briefly improved on it at Canadian trials in 2023, and Titmus took it back three weeks later at that year's World Championships. At Paris 2024, Titmus won Olympic gold with McIntosh second and Ledecky third (Olympics.com). Then last July, McIntosh reclaimed the world record outright at 3:54.18 and backed it up with gold at the 2025 World Championships in Singapore, with Ledecky taking bronze (Team Canada). Whatever happens Friday, this is not two swimmers meeting for the first time. It's the latest round of a race that's been getting faster and closer for years.

None of that tells you who wins, and this post isn't going to guess. What's more useful, and what holds up whether Friday goes to Ledecky, McIntosh, or someone else entirely, is a question that has nothing to do with the final time: how do you spend four minutes of effort without running out of the ability to hold pace before the race is over?

The Story Everyone Tells, and the One That's Actually Useful

The easy narrative around a rematch like this is raw speed, who's faster right now, who trained better this cycle. That's a fine story for a highlight reel. It's a bad one to learn anything from, because "be faster" isn't a skill you can take into your own training on Tuesday.

Pacing is. Ledecky is one of the most studied pacers in the sport specifically because her splits in the 400 and longer freestyle events are unusually even for someone racing at that speed, distance analysts have broken down her race files for years trying to explain how she holds a pace most swimmers can only sustain for half the distance (MySwimPro). The physiology behind that isn't mysterious. A pace that surges and settles costs more oxygen and produces more lactate than the same average pace held steady, because your body has to keep re-adjusting to a moving target instead of settling into one metabolic state and staying there. Even pacing isn't a stylistic preference. It's the cheaper way to cover the same distance.

That's the part of this race worth stealing, and it has nothing to do with being an Olympic-level swimmer.

What "Threshold" Means When It's Not a Watts Number

Cyclists have FTP and get comfortable with the idea that there's a sustainable output they can hold for roughly an hour, and that racing or training above it borrows against a debt that comes due. Swimmers have the same ceiling, it's just measured differently: critical swim speed, the pace you could theoretically hold indefinitely before fatigue forces you to slow down, tested the same unglamorous way FTP is, over a set distance, at maximum sustainable effort.

The 400 free is raced right around that line, closer to it than a sprint, further from it than an Ironman swim leg. Which means the entire race is a threshold-pacing problem: go out faster than your sustainable pace and you're borrowing time you'll pay back, expensively, in the last 100. Go out too conservatively and you've left time on the table you can never fully recover. The skill isn't swimming fast. It's knowing, cold, what your sustainable number actually is, and having the discipline to hold it when the swimmer next to you surges.

Age-group swimmers get this wrong constantly, and so does everyone doing their own version of it in a different sport. It shows up as the runner who blows through mile one of a 10K ten seconds under their sustainable pace because the field feels slow, and pays for it in the last two miles. It shows up as the cyclist who matches every early attack in a group ride instead of racing their own number. The mistake has one shape across every endurance sport: you find out what "too fast" costs after you've already spent it, not before.

This is part of why threshold pace and critical swim speed get their own zones in the app now, worked out the same way FTP is, rather than a runner or swimmer's intensity getting borrowed from bike math built for a completely different muscle system and energy cost. A number like that only earns its keep if you actually know it before race day, not while you're three hundred meters into finding out the hard way.

Race Week Isn't When You Find Out If the Plan Works

Both swimmers arriving in Irvine this week are almost certainly tapered, and that's worth naming because it's a decision made weeks ago, not something that happens Friday morning. The whole discipline of a taper is that it protects the fitness you already built rather than chasing more of it, and the pacing plan for the race itself gets decided in practice, at a controlled effort, long before the starting gun. Race week is for readiness and execution, not experimentation. You don't discover your sustainable pace mid-race any more than you'd try a new pair of shoes on marathon morning.

This is the piece self-coached athletes skip most often. The plan for how hard to go out gets made in the car on the way to the pool, or the start corral of a race, based on adrenaline and how the field looks that morning, instead of being decided ahead of time from a number you actually tested. When the coach flags that a hard effort is coming up, the useful version of that isn't a vague warning, it's tying the session back to a real pace or power number you can hold, the same way "why this workout" explains what a session is actually asking of you rather than leaving you to guess and find out the hard way.

Why This Matters Even If You'll Never Race a 400

Most of us aren't racing anyone Friday. Plenty of people reading this aren't racing anything at all this season, and that's fine, sustainable pacing isn't a race-day-only skill. It's the same principle behind not going out too hard on a training ride you're doing purely to stay consistent, or not turning an easy recovery swim into an accidental time trial because someone pulled up next to you in the next lane. The instinct to match whatever pace is nearby, rather than the one that's actually sustainable for you, doesn't wait for a start line to show up.

The uncomfortable truth is that most of us get this wrong in the same direction every time: too fast early, because going out conservatively feels like leaving something on the table before you've even found out if you need it. Ledecky's race file is instructive precisely because it's the opposite instinct, trust the number, hold it, and let the field come back to you rather than chasing it early.

The Honest Limits Here

An elite swimmer's pacing data is not a training plan for the rest of us, and it would be dishonest to pretend otherwise. Ledecky and McIntosh have physiologies, training volumes, and years of race-specific feedback that don't transfer by watching a splits chart. This post also can't tell you how Friday's race actually goes, because it's being written before the start, and guessing at that isn't the point. What does transfer is the underlying principle, tested in exercise physiology well beyond this one event: an even, sustainable pace covers a given distance more efficiently than a surging one, and knowing your own sustainable number ahead of time is what makes holding it possible. That's worth taking into your next hard session regardless of what happens in Irvine.