How to Find Your Course's Net Elevation Drop

Published September 13, 2026 · Estimates, updated each registration cycle

Short answer: net elevation drop is the elevation at the start line minus the elevation at the finish line, and nothing else. That is the Boston Athletic Association's own definition, word for word: the difference in elevation between the start and finish points of an event. It is not the total descent on your watch file, not the sum of every downhill mile, and not how hard the race felt. Qualifier registration for the 2027 Boston Marathon opens tomorrow, Monday, September 14, 2026, and this is the first cycle in which that single number can add minutes to the time you submit.

Why the number matters this week

The index has three bands. A net drop of 1,500 to 2,999 feet adds five minutes to your submitted qualifying time, 3,000 to 5,999 feet adds ten minutes, and a course dropping 6,000 feet or more cannot be used to qualify at all. Below 1,500 feet nothing happens and your clock time is your application time. The BAA applies the adjustment itself, after a qualifying time is submitted for review, so there is no box to tick and no way to opt out. You are not looking up the number in order to declare it. You are looking it up so you know what your application really says before you send it. The mechanics are in the downhill rule explainer.

Where to actually look, in order

1. The race's own course page. Most point to point races publish start and finish elevations, often in the first paragraph, because a big drop is the selling point. Subtract one from the other. If the race quotes a single headline figure, check whether it says net drop or total descent, because those two numbers can differ by thousands of feet on a canyon course.

2. The USATF course certification record. Every certified American course has a certification code and a measurement document behind it, and that document records the start and finish elevations in meters along with a drop figure in meters per kilometer. The BAA points athletes to USATF and World Athletics for exactly this. Drop in meters per kilometer is the cleanest version of the number you need, because it is measured rather than estimated. To convert, multiply by 42.195 for the net drop in meters, then by 3.28084 for feet.

3. Do the threshold math once and reuse it. Boston's 1,500 foot line is 457.2 meters, which over 42.195 kilometers is a drop of about 10.8 meters per kilometer. The 3,000 foot line is about 21.7 meters per kilometer, and the 6,000 foot cutoff for ineligibility is about 43.3. So if a USATF record shows a drop under roughly 10.8 meters per kilometer, your time counts at full value. A useful sanity check sits inside the same system: for a performance to be eligible for an American record the course may drop no more than one meter per kilometer, which is about 138 feet over a marathon. Any record eligible course is nowhere near Boston's threshold.

4. Last resort, look up the coordinates. If the race publishes neither, find the start and finish locations on a topographic map or elevation lookup and take the difference. Do not use the elevation gain and loss totals from your GPS watch or from a run tracking site. Barometric and satellite altitude data drift over 26.2 miles, and those totals measure cumulative change, which is a different quantity from the one the BAA uses.

What five minutes does to a real application

Take a 42 year old man, whose standard is 3:05:00. He runs 2:57:30, a buffer of 7:30, and the predictor puts him at roughly 90 percent against our central estimate for 2027. Now suppose that race dropped 1,800 feet, so the smallest of the three bands applies. His submitted time becomes 3:02:30, his buffer becomes 2:30, and the same estimate puts him near 6 percent. He ran the same race and trained the same year. The only thing that changed is a number he could have looked up in five minutes. For reference, the 2026 race cut at 4:34 under the standard and our central guess for 2027 is about 5:15, give or take roughly 1:45. Those are estimates, not BAA figures.

If you are near a line, assume the worse band

Published elevations disagree. A race page, a certification document and a mapping tool can each give a slightly different figure for the same course, and the gap is often a hundred feet or more. Courses genuinely sit that close: Tucson comes in around 1,493 feet, seven feet under the first threshold. If your course lands within a hundred feet of 1,500, 3,000 or 6,000, plan as though the harsher band applies, and if you hold a second qualifier from a flat course, compare the two before choosing. That comparison is the whole point of deciding which qualifying time to submit, and the named courses on both sides of the line are listed in which marathons are too downhill for Boston 2027.

Do it before the window closes

Applications run from Monday, September 14 to 5:00 p.m. ET on Friday, September 18, and acceptance is not first come, first served, so there is no penalty for spending an hour on this first. Write down your course's start elevation, finish elevation, the difference, and which band it falls in, then put the indexed time rather than the clock time into the cutoff predictor. It will show that buffer against the estimated 2027 cutoff and against every real Boston cutoff since 2014, which is a far more honest answer than the number on your medal. The rest of the week's preparation is in the registration week checklist.