Since I finished the Prairie Fire Marathon last month, I've been in a bit of a running funk, and that has led to a blogging funk. Since I don't just like to write about my latest 5 mile recovery run, I've been at a loss for a topic that might be a little more interesting than watching mildew accumulate in the shower. That all changed a week ago Saturday when my stupid-ass went out for my morning run packing my cellphone and got back home not packing my cellphone. Now I have something to write about that's about as interesting as listening to Kim Kardashian talk about morals.
On Saturdays, I usually head out my front door to do my long runs consisting of a combination of 5, 7, or 9 mile loops, out in the country on little 2 lane highways or dirt roads. Because I'm out for so long, I'll wear a fuel belt and bring along some water, gels, and whatever else my intuition tells me I can't do without. Sometimes, like Saturday, that includes bringing my cell phone. After all, who doesn't like texting their BFF while attempting 8 minute miles into a headwind?
After mile four I looked down and noticed the wide open space in my belt's pouch where my phone hangs out. I started to panic. That phone isn't just my personal phone, but my work's too. I told myself there was a possibility that I forgot to insert said phone in said pouch before heading out, so I decided to wait till I got home to chalk that weekend up to being ruined. In a foreshadowing of things to come, about a mile and a half from getting home, the battery in my Garmin went out to lunch.
I mentioned my running funk above, and this was not helping. By the time I finished my 7 miles, my body was telling it had enough for the day. I was still not 100% recovered from the marathon, and I probably overdid a workout leading up to the weekend. I was starting to feel some twinges in my knee like I was coming down with Runner's Knee. Oh well, because after not being able to find the phone at home or by retracing my route in the car (and not having a bicycle), I knew I had to go back out on foot to find it.
As I feared, I got to mile 4 using a walk/jog combination without seeing any sign of it. So, I turned back around to retrace my steps again without any luck. In case you're keeping score, my 7 miles has now turned into 15 - 16 miles, and I have retraced my footsteps 4 times. I was pretty much dejected at this point. My legs and knees were pissed at me, and I was hungry from all the calories I burned.
Back home, I had pretty much given up, but it dawned on me the bluetooth on my phone was turned on and I might be able to locate it with another bluetooth device. It was a brilliant idea that has worked for others, but (spoiler alert) it didn't have a chance to work this time. While my wife and I were out looking for the bluetooth signal (Search and Rescue Mission Retrace #5): I was driving, she was scanning, and our 3 kids were in the back seat bored as hell, trying to understand what their parent's were doing driving along the highway at 5 mph. About a half mile from home my wife said she got a feeling to look across the street, and there it was.
As it turned out, the reason it took so long to find was my cell didn't just land on the gravel shoulder, but as it was falling out of it's pouch, the 35 mph crosswind blew it back onto the highway where an untold number of vehicles drove over it until it wound up on the opposite side of the road. By the time we got to it, the Ziploc bag I placed it in was tore up, the battery and battery cover were scattered, the battery was ruined, and the touch screen was toast.
Well, I went ahead and included a picture below, although it's hard to make out much detail.
So, consider this a public service announcement to all my running peers out there. Secure you stuff, or you might end up running an extra 10k or half marathon. Lucky for me, the phone's SIM chip was intact and I placed it in a borrowed phone from a buddy so I was only off the grid for the weekend.
Tuesday, November 20, 2012
Have You Ever Lost Something On A Run?
Posted by: Jon
2 Slow 4 Boston, Updated at: 7:30 AM
Labels:
General Musings,
Humor
Friday, October 26, 2012
Prairie Fire Marathon Race Review
Last week I wrote about my performance in the Wichita Prairie Fire Marathon, but I intentionally left out many details of the race logistics or course information so that I could write this post. Actually, I've blogged about this race in previous years, but in looking back, I don't think I did a good enough job describing the event. Plus, the Prairie Fire has evolved and changed. Full disclosure, this is my hometown marathon, and I want to see it do well. However, I'm planning on stating all the facts both good and bad.
The Prairie Fire Wichita Marathon has been in existence for 3 years now replacing the Wichita Marathon which was a point to point course. The Wichita Marathon was taken over by the Kansas Sports Commission and renamed after the sponsor, the Prairie Fire coffee roasters. One of the first changes was to the course. It became a dual loop course, with shared start and finish lines, all within the Wichita city limits.
Prairie Fire Wichita Marathon course as mapped by my Garmin. |
Prairie Fire Wichita Marathon elevation as measured by Garmin. |
Another change was the addition of an expo the day before. I can't say that there is anything that really stands out about the expo, but it's better than nothing, and you can find some deals there. Most of the deals might be difficult to take advantage of if you're from out of town since a lot of the vendors are local. Actually, one nice thing about the expo is that it's only a block from the starting line, so if you're coming in from out of town, you can stay at a hotel within walking distance of both like the Hyatt, Drury, or Fairfield Inn.
Prairie Fire "Fit For Life" Expo |
Prairie Fire "Fit For Life" Expo Packet Pickup |
Arriving to the starting area 45 minutes before the race, one thing became obvious right away that can also be an issue at large races. A shortage of port-a-potties. Not that there weren't a lot of them, it's just that everyone tries to use them at the same time before a race. I found some public bathrooms in a nearby parking garage that most runners didn't know about, and I still had to wait in line over 10 minutes. The bottom line is, don't show up to the starting line at the last minute. Despite bathroom lines, and thousands of people at the start, it's still not as congested as a big city marathon, and therefore not as hard to get around or find a parking spot.
While running the marathon, I was pleased with how much shade there was going through the neighborhoods to help keep me cool on a sunny morning. The bad thing about the shaded streets was there were some turns to navigate. The turns honestly didn't bother me at all, but I hear other runners complain there are too many of them. Another thing related to the turns, the course transitions between roads and sidewalks in a few places. Some transitions happen in a way to slow you down, but they are later in the race where you aren't competing with other runners for position.
The Prairie Fire Marathon uses the Bib Chip timing system which are disposable stickers on the back of your bib to track you. It's nice not to have to deal with chips on your shoes. As of this year they expanded the timing equipment to register your 10k, half, and 20 mile splits. They also allowed you to register your number with social media like Twitter and Facebook to automatically post updates as you crossed the mats. On the down side, they have yet to post those splits all in one place as part of the final results.
One of the unique aspects of Prairie Fire for my family is that they can park along the course almost anywhere and cheer me on, then along some roads, drive beside me until another car comes up behind them and forces them to speed up. While in the downtown areas of the course, there are a variety of bands playing tunes to add some energy along the way. And about mile 25, the runners are taken over a trendy foot bridge that passes the 44 foot tall Keeper Of The Plains statue where the Big and Little Arkansas rivers merge.
Keeper of the Plains |
2010 Commemorative T-Shirt |
2010 Finisher Technical T-Shirt |
2010 Finisher Medal |
2011 Commemorative T-Shirt |
2011 Finisher Technical T-Shirt |
2011 Finisher Medal |
2012 Commemorative T-Shirt |
2012 Finisher Technical T-Shirt |
2012 Finisher Medal |
2012 Finisher Medal |
Posted by: Jon
2 Slow 4 Boston, Updated at: 5:30 AM
Wednesday, October 17, 2012
Prairie Fire Wichita Marathon Report
My 20th marathon is in the books. Sunday I ran the Wichita Prairie Fire Marathon. I'm pleased to say this turned out to be one of my good performances despite not setting any personal records.
Before I talk about the race, let me first mention the PF Expo the day before. I was scheduled to work the last couple hours of the expo in the RunWichita running club's booth. Before that however, I got to meetup with running bloggers Jim (50 after 40) and Michael (Slowly Tri-ing) who were in town from Missouri to tackle the full and half marathons respectively. I had met Jim before at the Austin marathon in 2011, but this was my first time getting to meet his wife. Michael was a bit under the weatherly, but we had a great conversion for probably 20 to 30 minutes about all things running.
Before I talk about the race, let me first mention the PF Expo the day before. I was scheduled to work the last couple hours of the expo in the RunWichita running club's booth. Before that however, I got to meetup with running bloggers Jim (50 after 40) and Michael (Slowly Tri-ing) who were in town from Missouri to tackle the full and half marathons respectively. I had met Jim before at the Austin marathon in 2011, but this was my first time getting to meet his wife. Michael was a bit under the weather
As we were saying our goodbyes, the PF race director walk by and asked me if I'd do an interview for the local news. I spent about 10 minutes in front of the camera, and thankfully he did lots of nice editing so that when it appeared on the ten o'clock news, I sounded halfway intelligent.
Now, on to the race.
My mindset heading in was to shoot for a 3:30 (8:00 pace) if everything was perfect. If not, I felt setting a new PR was still in the cards, I just needed to maintain an 8:10 average pace, which my long runs told me was possible. With the injuries I've had this year, my mileage base was low. I have literally done one 16 mile, one 17 mile, one 18 mile, and one 20 mile run all year, so I wasn't sure how I would handle the last 10k of the marathon. With that in mind, my 'C' goal was to average about an 8:20 pace, or finish sub 3:40.
My pace wasn't all I was thinking about. I had a marathon fail last year when I focused too much on pace when there were early warning signs pointing to it being too fast, I mostly ignored them and I paid the price. Since then I've dedicated myself to paying attention to my heart rate and not allowing it to go over certain levels.
This time around, my marathon would be based off of my heart rate. For the first half dozen miles, I planned on a HR around 165 bpm. For miles 7 - 12, I was prepared for my HR to gradually increase up into the low 170s, and make sure it stayed under 175. For miles 13 - 20, I was hoping to keep HR between 175 and 180. If I hit 181 before mile 20, it would be time to slow down. If those heart rates sound high to you, it might help to know that my max heart rate is over 200, and my lactate threshold heart rate was tested to be 183 over the Summer. By mile 20, it should be pretty obvious how my race is shaping up, and I can go back to running by feel for the last 10k.
Here is my Wichita Prairie Fire Marathon 2012 race breakdown, courtesy of Garmin:
Here is my Wichita Prairie Fire Marathon 2012 race breakdown, courtesy of Garmin:
Split | Time | Distance | Elevation Gain | Elevation Loss | Avg Pace | Avg HR | Max HR |
1 | 08:18.2 | 1.00 | 39 | 0 | 8:18 | 159 | 168 |
2 | 08:12.5 | 1.00 | 0 | 47 | 8:12 | 165 | 170 |
3 | 08:20.1 | 1.00 | 14 | 14 | 8:20 | 165 | 173 |
4 | 08:17.9 | 1.00 | 50 | 0 | 8:18 | 172 | 177 |
5 | 08:13.8 | 1.00 | 6 | 9 | 8:14 | 171 | 176 |
6 | 08:14.6 | 1.00 | 17 | 0 | 8:15 | 170 | 177 |
7 | 08:20.2 | 1.00 | 0 | 16 | 8:20 | 170 | 176 |
8 | 08:07.5 | 1.00 | 0 | 38 | 8:07 | 170 | 177 |
9 | 08:29.4 | 1.00 | 49 | 0 | 8:29 | 171 | 175 |
10 | 08:12.8 | 1.00 | 16 | 22 | 8:13 | 174 | 180 |
11 | 08:16.7 | 1.00 | 52 | 63 | 8:17 | 174 | 178 |
12 | 08:14.5 | 1.00 | 55 | 44 | 8:14 | 171 | 176 |
13 | 08:13.2 | 1.00 | 54 | 104 | 8:13 | 173 | 179 |
14 | 08:15.3 | 1.00 | 33 | 6 | 8:15 | 178 | 183 |
15 | 08:11.2 | 1.00 | 0 | 52 | 8:11 | 177 | 181 |
16 | 08:26.3 | 1.00 | 46 | 36 | 8:26 | 178 | 180 |
17 | 08:22.0 | 1.00 | 16 | 0 | 8:22 | 177 | 181 |
18 | 08:35.0 | 1.00 | 14 | 16 | 8:35 | 177 | 180 |
19 | 08:40.5 | 1.00 | 43 | 39 | 8:40 | 179 | 182 |
20 | 08:32.9 | 1.00 | 74 | 55 | 8:33 | 178 | 181 |
21 | 08:35.8 | 1.00 | 0 | 43 | 8:36 | 180 | 184 |
22 | 08:24.1 | 1.00 | 39 | 32 | 8:24 | 181 | 185 |
23 | 08:27.8 | 1.00 | 69 | 27 | 8:28 | 183 | 186 |
24 | 08:37.7 | 1.00 | 32 | 41 | 8:38 | 183 | 186 |
25 | 08:56.3 | 1.00 | 33 | 47 | 8:56 | 183 | 186 |
26 | 08:26.0 | 1.00 | 25 | 0 | 8:26 | 185 | 190 |
27 | 01:44.7 | 0.22 | 0 | 30 | 7:55 | 193 | 197 |
Summary | 3:39:46.6 | 26.22 | 777 | 782 | 8:23 | 175 | 197 |
If you take the time to go over my splits above, you'll notice that I ran a pretty controlled race with my heart rates slowly increasing, and my paces staying fairly consistent as the wind or inclines would allow.
Speaking of wind. That was the main enemy of this race. The official wind data reports showed 12.3 mph average wind speeds with sustained winds at 23 mph, and maximum gusts of 31 mph. That coupled with 58º starting temps, and finishing temps in the mid 60s with sunny skies. It seemed no matter which direction we ran there was a headwind. Of course there were some tailwinds to help out including most of the last two or three miles, but the damage was already done.
My official chip time was 3:39:46. I missed my first two goals, but scored on my third. When all the above factors are combined with finishing only 5 minutes over my PR, I felt really good about this race. I'm honestly not sure what I could have done differently that would have given me a faster time. This might have been my smartest marathon to date. Compared to the rest of the field, only 13.4% of the runners finished ahead of me whereas last year that percentage was 0.5% higher.
Marathon Pics:
Marathon Pics:
High five for my 8 year old who's now inspired to run a half marathon. Is my hair on fire? |
Crossing the finish line in 3:39:46 chip time. |
Finisher shirt. Check. Finisher medal. Check. Time to find the beer garden. |
It's really hard to smile looking into the sun. My wife and kids come out to support me at all my marathons. Note: Wife behind camera. She's a great race photographer. |
My 4 year old daughter had a long morning. She fell asleep on the car ride home. But that doesn't stop us from taking her picture when she pouts. |
Update: If you would like to read more about the race itself and less about me, visit my next post where I review the Prairie Fire Marathon.
Posted by: Jon
2 Slow 4 Boston, Updated at: 5:00 AM
Labels:
Marathon,
Race Report
Subscribe to:
Posts (Atom)