dns

I was reading this post about having a DNS -- do not start -- day. It's one thing to have one DNS, but another to have multiple.

And this year has been the Year of the DNS for me.

First, there was the sprained ankle, which resulted in a DNS at Kaiser, a race I had hoped would be a PR attempt.

The plus side to this: I discovered I am a really good spectator.

Then: New York. My heart still hurts thinking about it. I had high hopes for this marathon. Everything was lined up: The hotel was booked, I was on the VIP bus to the starting line, the ramen research was done, I had made plans to meet up with friends. But then my stupid hip had to protest. (Of course, my physical therapist thinks the hip injury may stem from the ankle sprain throwing everything out of alignment and causing my muscles to fire wrong. Curse you, left leg.)

Ultimately, deferring was the right decision. Only 10 percent of all lottery entrants actually get into the race, and since I'm not fast enough to enter with a qualifying time, this one entry is probably the only shot at New York I'll ever have. So rather than stumble through a once-in-a-lifetime experience in pain and risk a DNF (perhaps even worse than a DNS), I backed out. Hopefully next year I'll be 100 percent and can experience New York at its fullest.

But wait. The DNS action doesn't stop there.

I am actually debating yet another DNS this weekend. I'm signed up for the Healdsburg Half Marathon on Sunday, and there's absolutely no way I can run 13.1 miles. The farthest I've run recently has been a little more than 5 miles. My options: (a) Start the race, only run 7-8 miles and then call someone to come get me from wherever I drop out (my first DNF!), (b) Bring my bike to the race, ride the course and cheer for my friends who are running it or (c) Scrap the whole thing altogether and do something completely different, like maybe hot yoga or a long ride (have I mentioned I'm obsessed with my bike?) or even swimming.

Overall, this year hasn't turned out at all as planned.