It’s all about timing … or is it?

About two weeks ago, I did my 16th half marathon as a walker. My finish time was my second-best ever, which came as a bit of a surprise, and I soon learned why.

The course was in a beach town (Wildwood, NJ), which is my favorite place for a race course, so it was fast and flat with great scenery.

The temperature was about just right, although there were ferocious winds, with gusts up to about 20 mph. Somehow they seemed to be headwinds the majority of the time, which made it tough going.

I didn’t see a mile marker until mile 3, so I wasn’t sure of my pace in the beginning. But as the race went on, I felt steady and strong, and my RunKeeper app gave me a sense of my timing.

Beautiful day for a race! Headed toward Stone Harbor from North Wildwood.

Beautiful day for a race! Headed toward Stone Harbor (and the halfway-point turnaround) from North Wildwood.

At one point, too, I kept a mental count of how many runners I passed … I stopped after 6. I praise anyone who undertakes the goal of doing a race, no matter their pace, but it does give me a thrill to walk faster than some people run.

Feeling strong in mile 12, on the Wildwood boardwalk (photo by Chris M. Junior)!

Feeling strong in mile 12, on the Wildwood boardwalk!

As I neared the home stretch, I realized (based on the updates my app was announcing) that I might break the 3-hour mark. (My PR is 2:54 and change, which occurred in 2012, and I haven’t managed to break 3 hours since. I’ve come within about 30 seconds of it, to no avail.)

The finish line approached and its clock was under 3 hours — which meant that, even factoring in the small amount of time after the race start that I crossed the finish line, I had indeed broken 3 hours.

Soon thereafter I got a text from the race tracking system with my finish time: 2:57:49.

I was surprised! Sure, I had done my mileage work during training. But I’m up several pounds over my normal weight, I haven’t been working out as regularly otherwise as I’d like, and I haven’t been eating the most balanced, healthy diet lately. Plus, factoring in the wind … again, I was surprised. On top of that, my RunKeeper app tally was about 12.7 miles, which was slightly puzzling. But I did feel really good during the race — I felt like my pace was consistent, as was my stride, and so I thought maybe the pieces had come together.

IMG_2641I was really pleased that I had finally broken the 3-hour mark again.

And then … it was negated.

“Before and during the race, we believed our course measurement of 13.11 miles was correct,” explained an email from the race organizers a few days later. “However, from the information we have since gathered, we realize the published course was in fact short by approximately .15 to .20 of a mile….” Add in some discrepancy with the course turnaround point (which I believe was corrected before I reached it, based on the description), and “this would have resulted in approximately .2 to .3 of a mile less distance on top of the already .15/.20 of a mile shortage.”

So … I didn’t have my second best time ever. And I didn’t break the 3-hour mark again, yet. My minor disappointment faded as I realized a few things about the race:

Happy finisher!

Happy finisher!

  • I felt strong through the race, with a consistent pace and good form
  • I didn’t hit a wall
  • I powered through the crazy wind
  • I finished strong
  • I am proud of myself!

Which tells me that although a brag-worthy finish time is great and all, accomplishing the goal in the first place is just as worthy of crowing about. Keep it in perspective and don’t let numbers get you down.

Happy walking!

2 thoughts on “It’s all about timing … or is it?

  1. Indeed you are correct Joelle. The time is one thing but all you cite above is more important and as always I am so very proud of you! Mom


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s