After I ate a quick banana for breakfast, my family piled into our minivan and drove to Castlewood State Park this morning so that I could run 6.2 miles. See, I’m doing a 10K at Castlewood on November 8th, and I’ve never done a trail run OR a 10K before. I thought it might be wise to do a trial run by myself, so I don’t make a complete fool of myself on race day. Especially considering the farthest I’ve managed to run in my training is 4 miles, and the farthest I’ve walked is 5 miles.
I found the route on MapMyRun and sent it to my phone. I also printed the route from the Skippo site.
After we arrived at the park, I grabbed my phone and my earbuds, some water, and a couple of chia bars – which I planned to eat at miles 2 and 4- and left Hubs to spend some quality time with the kidlets.
Once on the path, I cranked my Boost 101.9 app and ran. Around mile 3, I looked down at the map and my gps point and realized I’d made a wrong turn and had to retrace my steps.
Between mile 3 and 4 I was supposed to take the creek crossing (yes, I said creek) and launch up another trail. My gps was pinging me off course again, so I did a circle (or three) across and through the creek until it picked me up and put me at the trail I’d already passed several times. UGH.
Shortly after the 5.2 mile point, my phone died. Completely died. No tunes. No gps. No way to call my husband if I fell on the trail. Apparently, I can’t stream 4G that long. Hrumph.
A bit later, I stumbled on a hidden rock , so i stopped running and walked until I hit even ground again.
I went further than I’d planned to go, and my pace much slower than I wanted, but it was a beautiful morning and I FINISHED it.
Fortunately for me, there is an an informal course preview next weekend, so I’ll be going out and trying it again. Perhaps with pace runners to help guide and provide directions along the official route, I’ll be able to stick to 6.2.
Whatever the case, I am just glad I took my Catalyst this morning before I left for the run! No sore muscles for me!