Trail
Running Paradox #1: The 2.8 Factor
Missing from this page are some photos. For now it is just some dry
text about estimating necessary time.
Part A: Running T minutes takes
2.8 x T minutes of clock time.
This seems like an awfully expensive exchange rate, having to lose an
extra 1.8 minutes for every minute spent running. I've found that with
one thing and another it's a good way to approximate how long it will
take, really.
Part B: One can always throw in an extra
mile or two.
Keeping Part A and Part B in mind is my method of planning enough time
for
the run, not stressing out over the process, enjoying the experience,
not getting discouraged, and kicking in a little extra mileage, thereby
staying consistent on the way to hitting mileage goals.
By way of example, the Hessie Continental-Divide
"Ice
Cream Cone Route" is one of my favorite runs in the Rockies west of
Boulder in the summertime. It's about 15 miles and elevation from 9000
up to 11,500 feet and back down again. Here are some of the time
consuming necessary things to make the run happen:
Plan
details of run, make time: 30 minutes.
Gear prep: 30 minutes.
Get gas, get out of Boulder: 30
minutes.
Drive up to the trailhead and park:
60
minutes.
Get myself and Maia ready to go:
15 minutes.
Actual running/hiking time: 5 hours.
Breaks for lunch and snacks: 1 hour
Load up: 15 minutes
Drive back to Boulder: 1 hour.
Take a really slow dinner, hydrate,
stretch, rest, stow gear: 3
hours.
In other words 5 hours of running and 8 hours of support time. So ok,
maybe it's a factor of 2.6.
Trail Running
Home