(I’m a member of the Running Fools board over on The Motley Fool, and when I started running again they were the ones I went to to talk about it. I’ve made it a point to do race reports after my events … and I’m going to be posting those throwback reports here to get us up-to-date. This was my second 5K, in Queens, New York. This report was written in April, 2013.)
Summary: I’ll take it.
The JFK Runway Run is one of (if not the) oldest runway runs around – they’ve been doing it continuously since 1972. They shut down the main runway at JFK Airport in Queens and the race happens right there. From the starting line, you run about 200 yards, then take a hard right and it is a perfectly straight, perfectly flat shot down to a turnaround into a (duh) perfectly straight, perfectly flat 2nd half.
After packet pickup at an administration building, they loaded us onto a bus for a 15 minute shuttle out to the runway, including a pretty serious looking security stop. We sat out there waiting in the wind (and, holy crap the wind) for all of the runners to be delivered for a 9am start – which they are supposedly pretty strict about, because any delay could screw up the airport for the rest of the day. The biggest problem was wind – about 5 minutes before the scheduled start time, a gust of wind blew the entire start / finish line setup down … the clocks, the pace signs, everything. We wound up starting 15 minutes late.
I was concerned about this race because I’ve done very little real training since my last race three weeks ago. It turns out that the injury to my ankle that I sustained at the finish line of that one was more severe than expected – even my toes turned purple. So between that and travel for work (and I got lazy – there, I said it – I got lazy) I wound up doing less than half of my planned miles over that time period, and many of those were not quality miles. Knowing how my mind works, the worst possible thing for me would have been to beat my previous time … that kind of positive reinforcement encourages my laziness. I finished about 45 seconds slower than my previous race, which is still significantly farther along than I expected to be at this point when I started running. Also, I’m pissed off that I let myself get lazy and go backwards on a perfectly flat course. All in all, though, given how poorly I’ve trained over the last three weeks – I’ll take it.
1. Several people in this one didn’t follow the board’s collective wisdom. There was a pink tutu, a guy running with boxing gloves on, race t-shirts everywhere, etc. Plus, this is Queens – you can imagine the humanity. Lots to see.
2. Which is a good thing, because … perfectly flat and perfectly straight is not all it is cracked up to be. I’m used to running on hills and mixing up muscles. And scenery that changes. It was tougher than expected.
3. Because it was an out and back, I got to see the leaders coming the other way – holy crap, I cannot imagine ever running that fast. Holy crap.
4. The FAQ on the website said something like “it tends to be windy – don’t wear loose fitting caps”. Biggest understatement ever. I have no idea how they land airplanes in that kind of wind. Also – in an out-and-back, tailwinds will eventually be headwinds. Yeah.
5. Wings and beer on race day are AWESOME.
Next race: Phillips 10k Trail Race, June 9th
One thought on “Throwback Thursday Race Report – RR #2, JFK Runway Run”