A course can show 18 miles of singletrack and still offer only 11 miles you can truly run at race effort. Knowing how to estimate runnable sections before the start keeps you from building a road-runner pacing plan for a mountain race. It changes your effort targets, aid-station timing, fueling schedule, and expectations when the clock starts moving.
Runnable does not mean flat. It means you can move with a repeatable running gait at an effort that makes sense for your race distance. A 7% dirt climb may be runnable for 20 minutes early in a 25K. That same climb may be a hike in mile 42 of a 100K, after heat, altitude, and 8,000 feet of climbing have done their work.
Your job is not to label every segment run or hike with false precision. Your job is to identify where running is efficient, where power hiking is faster for the cost, and where terrain will control the pace regardless of fitness.
Start With the Course Profile, Not Total Distance
Total distance hides the decisions that matter. A 50K with 5,000 feet of climbing on smooth forest roads can be far more runnable than a 30K with 6,000 feet of loose, steep, technical mountain trail. Begin by breaking the route into logical sections: climb, ridge, descent, rolling traverse, and road or trail connector.
Use aid stations as the first set of boundaries. They are practical planning points because they determine water, calories, crew access, cutoff pressure, and the reset points you will remember when tired. Then split any long aid-station leg when the terrain changes sharply. A 10-mile leg with a 2,500-foot climb followed by a fast descent is not one pacing problem. It is two.
For each section, record the distance, elevation gain and loss, average grade, maximum sustained grade, surface, altitude, and exposure. Average grade is useful, but it can lie. A 5% average may include a flat mile, a 20% wall, and a descent. The sustained grade and terrain distribution tell you whether the section actually runs.
How to Estimate Runnable Sections by Grade
Grade is the quickest first filter. It is not the final answer.
On firm, smooth terrain at moderate altitude, most trained trail runners can usually sustain an efficient run on climbs under roughly 5%. Between 5% and 8%, runnability depends heavily on fitness, race duration, traction, and whether the climb is continuous. Between 8% and 12%, many athletes alternate running and hiking. Above 12%, deliberate power hiking is often the smarter choice, especially in an ultra.
Those ranges are planning cues, not rules. A 10% climb on compact dirt can be more runnable than a 6% climb covered in roots, wet rock, or deep sand. A short 15% pitch may be worth running over the top if it leads into a fast downhill. A 40-minute 9% climb near your aerobic threshold is a different decision entirely.
Think in terms of energy cost. If running changes your pace only slightly but spikes breathing, heart rate, and quad load, you are not gaining meaningful time. You are borrowing from the next section. Power hiking with purpose can preserve enough control to run the ridge, descent, or runnable valley that follows.
Measure sustained climbs separately
A climb that averages 8% over four miles may contain several runnable benches. Mark those benches. They are opportunities to shift gait, lower muscular strain, and make time without forcing the steepest terrain.
Likewise, do not call a descent runnable just because it loses elevation. A steep, technical downhill may demand short steps, braking, and constant line choice. Your watch may show a fast overall grade while your actual movement is closer to controlled hiking.
Surface and Technicality Decide the Real Answer
Grade tells you what the map sees. Surface tells you what your feet will feel.
Smooth dirt, packed gravel, forest road, and open buffed singletrack are generally high-confidence runnable terrain. Loose talus, off-camber tread, mud, deep sand, snow, roots, wet slabs, stream crossings, and tight switchbacks reduce runnable speed quickly. Even if you are moving fast, technical terrain may require enough concentration that it carries a high fatigue cost.
Use race photos, route descriptions, 3D mapping, previous-year reports, and GPX inspection to find transitions. Look for exposed ridgelines where wind may change footing, north-facing slopes that can hold snow or mud, and descents that compress large elevation loss into short distance. If the event provides a course video, treat it as terrain intelligence, not entertainment.
Technicality also changes by runner. A confident mountain descender may classify a rocky downhill as fully runnable. An athlete with limited technical experience may need to treat the same section as controlled movement. Build the plan around your own skills, not the lead runner's highlight reel.
Add Altitude, Weather, and Race Position
A runnable section on a cool training day can become a hike when it starts above 9,000 feet in full sun. Altitude lowers the output you can sustain. Heat raises fluid needs and makes steep climbs more expensive. Rain can turn benign dirt into a traction problem. Wind can make an exposed ridge slow even when the profile looks gentle.
Race position matters just as much. Early sections deserve a conservative runnability estimate because your restraint determines what remains later. A climb you can run at mile 4 may still be a bad choice if the course has another 10,000 feet of gain waiting.
For long races, classify each section twice: fresh and fatigued. A rolling ridge might be 90% runnable in the first third of the course, 60% runnable in the middle, and a run-hike section late. This is more useful than pretending one pace will hold from start to finish.
If you expect night running, downgrade technical terrain again. Darkness slows foot placement, makes route finding harder, and adds a mental cost that does not appear in the elevation chart.
Build a Run-Hike Plan Instead of a Guess
Once you identify likely runnable terrain, assign an effort and gait strategy to each section. Keep it simple enough to execute under stress.
For a runnable climb, your instruction may be: run the shallow grade, hike every steep pitch, and cap effort below redline. For a steep climb, it may be: power hike from the base, use hands when needed, eat halfway up, and run only the crest. For a technical descent: stay controlled through the rocks, then open stride when the trail smooths.
Avoid rigid intervals unless they match the terrain. Running nine minutes and hiking one minute can work on a steady fire road climb. It falls apart on terrain that switches from 4% to 18% every few hundred yards. Terrain-based cues are usually more durable: run the flats, hike the steep corners, run after the creek crossing, reset at the saddle.
A useful test is whether you can fuel while moving. If a section is truly runnable but easy enough to eat and drink, it is often a valuable place to bank efficient time. If running prevents fueling or makes your stomach bounce, the section may be harder than its profile suggests.
Turn Runnable Terrain Into Realistic Splits
Do not calculate an aid-station split from a single average pace. Estimate time by terrain type, then add transition costs. Your running pace on smooth trail, hiking vertical speed on sustained climbs, and descending pace on technical ground should each have separate assumptions.
For example, a six-mile aid-station leg might include two miles of runnable trail, one mile climbing 1,200 feet, two technical downhill miles, and one rolling mile. Give each piece a realistic estimate based on training data and comparable terrain. Add time for filling bottles, eating, bathroom stops, navigation hesitation, and the inevitable slowdown after a hard climb.
If you have recorded training on similar grades and surfaces, use that data first. Race effort, altitude, and accumulated fatigue still require a buffer, but your own history beats a generic pace chart. When course data is organized by aid station, elevation segment, and terrain transition, TrailSight can help turn those route details into a plan you can actually carry onto the start line.
Check your estimates against cutoffs, but do not chase cutoffs by running terrain that should be hiked. Instead, find the high-confidence runnable sections where you can move efficiently. Those are the places to protect time.
Rehearse the Decisions Before Race Day
The best runnability estimate is tested, not admired on a screen. During long runs, practice switching from run to hike before you are forced to. Find a sustained climb, compare running versus power hiking at the same perceived effort, and watch what happens to your breathing and leg fatigue afterward.
Practice downhills when your quads are already tired. Train fueling on rolling terrain. If your race has altitude, heat, poles, night sections, or slick rock, include those conditions where possible. You are training the judgment behind the plan, not just your aerobic engine.
On race day, treat your estimates as a framework. Conditions may improve them or tear them apart. The prepared runner recognizes the terrain, adjusts early, and saves their strongest running for the sections where it will actually hold.