140 miles per hour

Before my ride today I was going to title this post "Sore calves, slow leaks". I had sore calves, not from cycling, but from painting. At least that's the only exercise I had this week. Mrs. MTBMan1 and I journeyed to Baltimore to visit our son and meet up with our daughter who bussed down from NYC. Our original plan was to travel from Baltimore to Hancock in northwestern Maryland to rent bikes and ride the Western Maryland Rail Trail as a family but son had plans to work on his house so we pitched in to paint his study. I did the cutting in and it was up and down the step stool innumerable times and crouching on my knees on the floor. That's the only thing I could conceivably believe could have made me sore. We never got to the Rail Trail. It was very hot and humid anyway so I'm not sure how much fun it would have been.

As to the slow leaks ... I mentioned in a previous post about my mysterious leaking tire which rode fine one day and was flat in the garage the next and I could not find a leak to save my life. In fact, I reinflated the tube and left it out for days and it never lost any air. So I packed it up for a spare.

But on my ride today, first in 6 days, I used my GPS as usual and when I got back it reported that I rode 69.4 miles from someplace south of Boston, MA to near Durham, NH in about a half and hour. Basically a straight line as the crow flies at an average speed of 140.3 mph. Pretty good for a bike, eh? Must have flown. Perhaps I went into a trance and did a bi-location like superman did in one episode. Cause I thought I was sloggin' it in upstate NY. Who knew?

Or maybe the trip to Baltimore confused the GPS. It got disoriented.

Now my cycle 'puter says I did 21 miles in about 1-1/2 hours. But it doesn't know about bi-location!

Posted in |