Understanding Split Strategy for Ohio Ultrarunning
Most people walking into their first 100-mile race in Ohio have no real plan for pace distribution. They run the first half too hard because the course is flat and the crowds are supportive. Then they pay for it somewhere around mile 50 when the hills show up and nobody told them about them. I learned this the hard way at the Old Bedlam 100 back in 2019. I hit mile 20 in under my target pace by forty-five seconds per mile, felt great, and then started dying by mile 42. Finished 3 hours slower than I should have. This is why breaking down your mileage by sections matters more than almost anything else when you are racing in Ohio. The terrain changes fast here. You can go from smooth farmland gravel to technical limestone ridges in less than three miles, and your heart rate response is completely different on each surface even when your perceived effort feels the same.
Unveiling The Magic Of Ohiomilesplit A Comprehensive Guide To Breaking Down The World Of Ultrarunning
The core idea is simple but most runners botch the execution. You break the entire course into individual mile segments and assign a realistic pace target to each one based on actual elevation gain and surface type, not your average fitness level. I use a spreadsheet with columns for mile number, cumulative elevation gain in feet, surface classification, target pace, and expected cumulative time at that mile marker. When you do this properly, you end up with a pace chart that looks almost boring because there are no dramatic jumps between sections. The mistake beginners make is treating every mile equally. A mile with 120 feet of climb is not the same as a flat mile, period. In Ohio ultrarunning specifically, you are dealing with what I call the glacial till problem. After spring rain, those compacted glacial deposits turn into slick clay surfaces that slow you down by 20 to 30 seconds per mile compared to dry conditions. You need to factor that in if your race is during April or May, which is most of the spring ultras in this state. I built my split strategy around a tool system that takes elevation profiles and pace targets and converts them into a mile-by-mile guide. The basic workflow is: export the course GPX file, load it into elevation profiling software, segment it by mile, calculate net elevation per mile, cross reference with surface notes from recent race reports, and build your pace cards. This whole process takes me about 45 minutes for a new course. Once you have done it three or four times you can knock it down to 20 minutes because you stop second guessing the surface classifications.
Here is a concrete example. Let me walk through how I handled a recent race with a 7,200 foot total climb over 100 miles. The first 20 miles averaged 45 feet per mile and I set my target at 10:30 per mile. Miles 20 through 45 climbed at an average of 180 feet per mile and I dropped to 12:15. Miles 45 through 75 dropped back to 60 feet per mile and I moved back up to 11:00. The final stretch from mile 75 to 100 was brutal with 240 feet per mile average and I targeted 13:00. When I stuck to this plan, I ran every mile within eight seconds of target and finished with zero bonking. When I deviated early, everything fell apart later. There are real limitations to this approach that nobody talks about enough. Your split targets become useless if the weather turns extreme. I had a race where thunderstorms dumped two inches of rain in 40 minutes and every single one of my paved and gravel sections turned into mud runs. My pace targets from the spreadsheet were completely irrelevant after that point. I just had to abandon the plan and run by feel, which most runners are terrible at doing because they have never practiced it. If you are going to use a split-based strategy, also practice running by feel on your long training runs so you are not completely lost when the course conditions diverge from your assumptions. Another limitation is that Ohio races tend to have aid stations that are irregularly spaced. Some courses have stations every 3 miles, others every 7 or 8. If you build your splits around fixed mileage intervals but your nutrition needs are tied to time or distance between stations, you will miss feeding windows. I started overlaying aid station locations on my mileage grid and marking my planned nutrition intake at each station. This is an extra 10 minutes of prep but it prevents the kind of gut crisis that ends races more often than pace errors do.
Get the Full Details
The technical side of building these splits has gotten easier over the years. I use Garmin Connect for the elevation profile export, Riegel formula adjustments for fatigue modeling across different distances, and a simple custom script that auto-calculates pace targets based on your recent training data and the course profile. You do not need fancy software. A spreadsheet and a GPX viewer are enough. What matters is being honest with your numbers instead of optimistically inflating your pace targets by 15 percent like almost everyone does. My final piece of advice is to keep a race journal with your actual splits versus your planned splits for every Ohio race you do. After five or six races you will start seeing patterns in how your body responds to certain types of climbs or surfaces. That personal data is worth infinitely more than any generic pacing chart you find online because it reflects your actual physiology on Ohio terrain, not someone else's. I have found that most people who treat ultrarunning as a guessing game end up with inconsistent results. The runners who show up year after year with solid finishes usually have some version of split planning in place. It is not magic. It is just deliberate preparation instead of hoping for the best on race morning.
