NYC Marathon Course Guide: Five Bridges, 875 Feet¶
The 2026 TCS New York City Marathon on November 1 marks 50 years of the five-borough course, the one that runs through every corner of the city before it finishes in Central Park. That's the editorial fact. Here's the training fact: no other marathon in the world asks for the same crossing count, at the same mile locations, against the same accumulated fatigue profile.
Every course guide covers the Queensboro Bridge. Which means every runner who reads those guides trains for one obstacle and arrives at the start line knowing four are still unnamed. The Queensboro is not the problem. The five bridges together are the problem, and the way they compound across 26.2 miles is what this post addresses.
Training blocks for November 1 are running now. If yours started in late July, you have 13 to 14 weeks. That's enough time to build the specific adaptations this course demands, but only if you know what you're building for.
The Five Bridges: Elevation, Mile, Grade, and the Running Tab¶
NYC's five bridges are not distributed evenly across the course. Two arrive in the first 13 miles while the legs are fresh; one hits at mile 15 after the longest sustained flat stretch; two more arrive back-to-back at miles 20 and 21 when the legs are spent. The table below is organized by race order, not size.
| Bridge | Crossing | Race Mile | Gain (ft) | Approx. Grade | Cumulative Gain (ft) |
|---|---|---|---|---|---|
| Verrazano-Narrows | Staten Island to Brooklyn | 0-2 | ~130 | 3-4% | ~130 |
| Pulaski | Brooklyn to Queens | 12-13 | ~45 | 2% | ~175 |
| Queensboro (59th St) | Queens to Manhattan | 15-16 | ~120 | 3-4% | ~295 |
| Willis Avenue | Manhattan to Bronx | 20 | ~20 | 1% | ~315 |
| Madison Avenue | Bronx to Manhattan | 21 | ~20 | 1% | ~335 |
Elevation figures derived from NYRR published course maps and publicly available GPS profiles; total gain varies by measurement method. The 875-foot figure cited in training discussions typically includes approach roads and aggregate undulation beyond bridge summits.
The total across five bridges is around 335 feet of net gain, but that understates the cost. Each bridge is a climb followed by a descent, and descents have their own physiological price. The compounding effect runs in both directions.
The bottom-line number from this table: a runner who reaches the Queensboro at mile 15 has already paid for the Verrazano and the Pulaski. They arrive at the longest bridge of the day carrying two prior disruptions, with the longest climb still ahead of them.
Why Rhythm Breaks Before It Fades¶
On a flat course, a runner finds their pace in the opening miles and holds it. The body settles. Stride rate stabilizes. Heart rate finds a ceiling. That rhythm is the engine of an even-split marathon.
Every bridge breaks it. Not catastrophically, but structurally. The climb asks the body to shift effort upward. The descent invites a release, and most runners take it: they accelerate on the way down when the correct response is to hold. The body read "relief" and produces a surge it cannot sustain. This happens five times.
By mile 15, a runner has climbed twice and surged twice on descents. They arrive at the Queensboro not fresh but fragmented. The Queensboro is harder because of what preceded it, not because the grade itself is exceptional.
The result appears in finisher data. NYC has one of the lowest negative-split rates among major marathons. The analysis from RunRepeat's marathon database puts the rate near 5% for NYC finishers, compared to 15-20% on flat courses like Chicago and London. That gap is not a coincidence of field depth or weather. It is the course structure expressing itself in aggregate finishing patterns.
The second-half fade at NYC is a tab coming due.
The First Avenue Trap¶
The Queensboro ends with a right turn onto First Avenue at mile 16. The descent off the bridge is fast. The relief is real. Then First Avenue opens up: flat, straight, and lined with the loudest crowds on the course. Every physiological signal says go. Most runners go.
The cost is not avoided. It is deferred.
The surge on First Avenue at miles 16 to 18 draws on the same glycogen reserves that miles 23 to 25 depend on, and it does so before the body has recovered from the Queensboro climb. Published pacing analysis of NYC finishers consistently shows that runners who run miles 16 to 18 significantly faster than their prior-race average pay in the final 10K: the cost shows up as a 4 to 6 minute loss in the closing miles relative to runners who hold pace through the First Avenue segment.
The training fix for this is not willpower. Willpower does not survive 18 miles of accumulated fatigue and a roaring crowd. The fix is rehearsal: a runner who has practiced holding back in a simulated surge context has a different response available at mile 16 than a runner who has only ever trained to push when the body feels good. Section four addresses the specific drill.
Simulation Drills: One Per Bridge Phase¶
These drills are not standalone workouts. They are modifications to the long runs and mid-week runs already in your block. Each one targets the specific physiological demand that each bridge imposes, at the mile position in the race where the demand hits.
Verrazano-Narrows (miles 0-2): Cold-start climbing
The Verrazano asks a runner to climb 130 feet during the first two miles of the race. Most training plans never program a hill at the start of a run. Runners warm up for 15 to 20 minutes, then climb. That's backward for this course.
Drill: One long run per week with the hill in the first 15 minutes, not the middle. Find any 100 to 150-foot climb near the start of your route. Run it before your body has found its rhythm. The adaptation is teaching the system to settle on the climb itself, not before it. Belongs in weeks one through six of the block.
Pulaski Bridge (miles 12-13): Mid-run disruption control
The Pulaski is small, 45 feet, but it arrives after 12 miles of rhythm-building. Its risk is the same as the First Avenue surge on a smaller scale: the descent invites a reset, and most runners take it.
Drill: A 14-mile run with a deliberate hill at miles 10 to 12. The instruction is to hold effort on the descent, not recover it. One consistent output over the entire crossing, not two efforts separated by a pace dip. This builds the habit of not rewarding yourself on the downside. Belongs in weeks one through six.
Queensboro Bridge (miles 15-16): Sustained climbing after accumulated miles
Most training plans treat the Queensboro as a standalone problem: do hill repeats, problem solved. That's the wrong model. The Queensboro's difficulty is not the grade. It's the 15 miles that precede it. The hill training needs to happen at the end of the long run, not in a fresh-leg workout.
Drill: The final 2 miles of a 20-mile long run include a sustained climb. Not a separate hill session. The climb at the end of the long run is the simulation. Effort-based pacing only on the climb: don't look at pace. Run by breathing rate. If you can hold a steady breath cadence over the bridge, you've run it right, whatever the watch says. Belongs in weeks seven through twelve.
Willis Avenue and Madison Avenue (miles 20-21): Back-to-back late
Both bridges are small, under 25 feet each. Both arrive when the legs are spent. They are separated by approximately 1.3 miles through the Bronx, which means a runner has to climb, recover on flat ground for less than a mile, and climb again. The short recovery between them is the difficulty. A runner who handled each bridge individually in training has not practiced the back-to-back at late race fatigue.
Drill: At miles 18 to 19 of a 22-mile long run, two short climbs separated by 10 minutes of flat running. The first climb is hard because it's late. The second climb is harder because the legs expected flat. The adaptation is learning to climb twice in succession without losing form or surging on the descent between them. Belongs in weeks seven through twelve.
One note across all five drills: the goal is not to build climbing strength. Climbing strength helps, but it is not the gap. The gap is the descent reflex, the automatic acceleration that follows a climb, which costs rhythm and draws on reserves the final miles depend on. Every drill above is designed to separate the climbing effort from the descent response. Hold the effort constant. Let the pace float with the grade. Recover the pace on the flat, not on the bridge.
Where This Work Goes in a Block That's Already Running¶
Most runners reading this in late July have 13 to 14 weeks before November 1. Here is where the drills above fit in that window.
Now through early September (weeks 1-6, foundation phase): The Verrazano and Pulaski drills belong here. These are lower-intensity modifications to easy long runs and mid-week sessions. The physiological target is pattern-building: teaching the body to respond to early-run hills and mid-run disruptions without surging on the descent. No additional fatigue stimulus, just a change in where within the run the hills appear.
Mid-September through mid-October (weeks 7-12, specific phase): The Queensboro simulation and the Willis/Madison finisher drills belong here. These are harder, because they arrive at the end of long runs when the legs are already loaded. One per week is the right frequency. Not both in the same week. The First Avenue behavioral work also belongs in this phase: structured long runs where the explicit goal from miles 14 to 18 is holding pace rather than surging, simulating the First Avenue segment with a crowd you cannot hear and adrenaline you do not have.
Final 2 to 3 weeks (taper): No new stimulus. The bridge work is done. What you built in weeks seven through twelve is consolidating now.
One more thing: these drills are a filter, not a plan. Drop them into whatever block structure is already running. They do not require a new schedule.
Running by Effort on a Course That Punishes Pace¶
Most marathon training treats pace as the primary signal. Your GPS watch shows pace. Your training plan prescribes pace. Your goal time is expressed in pace.
On a course with five grade changes, pace is the wrong signal at every bridge. A 3% grade makes 8:30 pace look like 9:15 pace on the watch. A descent makes 8:30 pace look like 8:00 pace when the effort is identical. The watch is giving you the wrong information at exactly the moments that matter most.
Trail runners already solve this problem. Variable terrain demands effort-based pacing: hold the output constant, let the pace float with the grade, recover the pace on the flat. That instinct is exactly what NYC rewards at each bridge. It is not an ultra technique imported into a marathon context. It is what bridge management looks like from the inside.
The practical cue: on every bridge climb, put the watch face down. Run by breathing rate. If you're maintaining a steady, controlled breath cadence through the whole crossing, you've run it right. If you're blowing up your breathing to maintain pace on the climb or surging your pace on the descent, the watch is making the race harder, not easier.
Starting Where You Are¶
The block is running. These drills do not require starting over.
If your runs are coming in through Strava or Apple Health, NavRun reads your actual training history and builds a plan from what you've already done. Not a template from a training table. The plan starts with what you've proven. Generate it at navrun.app, one click once your runs are flowing in.
November 1 is 13 weeks out. The Verrazano drill starts this week.
Common Questions¶
Why does everyone talk about the Queensboro if the other bridges matter too?
Because the Queensboro is the loudest moment of the race. You come off 15 miles, hit the longest climb of the day with no crowd noise on the lower level of the bridge, and emerge onto First Avenue to the biggest crowd on the course. It's a dramatic sequence, and drama gets remembered. But the data says the Verrazano costs you earlier than you realize, and the First Avenue surge after the Queensboro is where the race is actually decided.
Can I use hill repeats instead of these bridge-specific drills?
Hill repeats build climbing strength, which helps. But the bridge-specific problem is not climbing strength. It is rhythm disruption at specific mile positions, and the descent reflex that follows each climb. A runner with strong hill-repeat training who has never practiced a late-run Queensboro simulation will still surge on the downside at mile 16. The drills address the specific habit, not the general fitness.
What if I don't have hills near where I train?
A treadmill incline works for the Verrazano and Queensboro simulations. Set 3 to 4% grade for 10 to 15 minutes. For the Pulaski and Willis/Madison drills, any overpass, parking garage ramp, or elevated trail section works. The grade precision matters less than the position in the run (early, mid, or late) and the descent response practice.
I've run NYC before and felt fine until mile 22. Is the early bridge work really necessary?
Yes. The reason miles 22 onward feel like a separate race is that the earlier bridges extracted a cost you didn't notice in the moment. The fragmentation is invisible until the tab comes due. Training the early bridges does not make miles 22 to 26 painless. It makes the tab smaller.