We Put the Train in Training

Since I had a day off today, and neither of my usual local routes are great for morning runs right now, I headed down to the rail trail for the first time since mid-December. It was a cold, clear, beautiful morning for a run. Did I mention cold? Weather.com said it was in the 40s, which for me means short sleeves or sleeveless. (I never said I was smart.) It was fine, except for my hands. It took about 3 miles before my hands warmed up. I was sure I was going to lose some fingers. I still might. Except, I'm typing; so probably not. I've got to remember to keep a pair of running gloves in my car for mornings like this.

At any rate, it was a very nice run. 3.5 miles north toward York from Brillhart Station, and then back for a total of 7 miles in 1:04:19. Good pace, and I felt great...except for my frostbitten fingers. I really feel like I've got my strength back these last two weeks. I can't yet run the mileage I was running last year, but I'm feeling confident that I can get back to it.


I also saw for the first time, and was briefly impeded by, a train using the tracks along the rail trail. That train stops in York, but this train (I know you can't see me because it's a blog post, but pretend I'm pointing at myself) isn't stopping until it crosses the finish line in Virginia Beach.

The Shadow of the Past

It seems that I'm running out of blogging steam a bit here at the end of the year. Usually, that means I don't have anything to write about. This week, I feel like I have a lot to write about (even if none of it is really super interesting or funny), I just haven't found the time. So, this ends up being kind of a catch-all post for the last week.

Messing with Texas
My last entry was about (among other things) enduring 40 blisteringly hot minutes on the hotel treadmill in Dallas. Unfortunately, despite my grand plans to get two runs and a weight workout in while on my business trip, that treadmill run on Monday night would be the end of my Texas exercising (Texercising?).

I had not, however, seen the last of In-n-Out Burger. I'll leave it to my readers to decide if that's a good or bad thing, but it was just what my colleague and I were in the mood for again after a long day on Tuesday. I planned to work for while and then hit the gym. I hooked up my laptop, sat down on the bed...and woke up four hours later at 12:00am.

Wednesday morning's breakfast was probably the highlight of the whole trip. "Don't mess with Texas?" Well, what about covering the whole state with syrup and eating it? I really didn't think a big waffle was the best breakfast choice before a long day of meetings, but when I saw they were shaped like the state of Texas I knew I had to have one.

(Yee-haw!)

I had one last chance to get a workout in on my business trip on Wednesday evening, but I chose the path of laziness. These three days had been the culmination of two months of very hard work, late nights, and a lot of stress. To see it come to fruition was very rewarding, and now that I had reached a key milestone in the project, I wanted nothing more than a relaxing dinner and a cold beer. And therein was the problem...

My colleague had departed for another meeting while my flight home was not till the next morning. The hotel didn't have a bar, and so I set the GPS to find restaurants. The trouble is that I was staying in a suburban/business-park type part of Dallas, so I couldn't just walk outside and find a place, so I couldn't really see what I was getting into. The first place looked much fancier than I was prepared to deal with, and the second turned out to be an oyster house. Yes, in Texas. I lost my resolve to sit by myself at a chain-restaurant type place, which did abound, and ended up with Jack-in-the-Box take-out. I stopped at a convenience store to see if I could get a beer, and they (predictably) had only six-packs or 40s, either of which would have been a terrible since I was leaving for the airport at 5:00am. At least my sandwich was really good.

On the Road Again
It was great to be home, but it seems like the trip has taken its toll and that I'm still recovering. I went to the rail trail on Saturday for the first time since my last 20-miler in November. I didn't really have a strict mileage or time goal -- I was just going to run from Hanover Junction to Brillhart Station and back, which is between 12 and 13 miles. I started feeling really, really tired at mile 3, and thought about heading back. I bargained with myself that I would turn around at 5 miles, since 10 would have equaled the previous week's run. Unfortunately, I got a second wind just before the 5-mile point that made me decide to press on to Brillhart. When I stopped there for a stretch break, I had sharp pains in the muscles on the fronts of my shins, which I've now had a few times since the marathon. Stretching my ankles in different directions seemed to relieve the discomfort.

Though I felt a little wobbly as I started back, some Sports Beans and Gatorade seemed to help. I made it back to Hanover Junction for a total of 12.75 miles in 2:03, which is good enough, but I just felt like I was dragging for most of this run. It's ok. For once, I"m not going to overreact to a crummy long run. This is almost exactly where I was at this point last year, and once I get back into my routine after the holidays, I'll be fine. While I didn't do well in Texas, it does seem like in general that motivation to get out and run during the week is back, which bodes well for Virginia Beach.

(I'm a shadow of the runner I was just a few weeks ago.)

That theme continued on Sunday. On the plus side, I lifted in the morning, and seem to be getting back in the habit. Unfortunately, my back has been bothering me a little this week and it flared up yesterday. I woke up on Tuesday, Wednesday, and Thursday morning with stiffness in my lower back, but would loosen through the morning and really didn't bother me much. However, as I was lifting, while on my last set it just felt like all the muscles in my lower back were cramping up, and it still is aching today. Hopefully this isn't the beginning of something nagging.

Since it was a rare Sunday without plans, Chris and I decided to go for a bike ride, which would be our first since August. It was kind of a disaster. I found that the bike tires needed air, but I'd read that you shoudn't use a pump meant for cars to pump up bike tires. I had a foot pump, and grabbed it to take with us to our starting point at York. Well, first, it wouldn't inflate the tires and then the hose broke off, anyway. Off to Dick's to buy a new pump, and then off to Hanover Junction since Dick's is midway between it and York.

Finally, we were able to get underway, only to find that neither of us had any energy at all. It's totally understandable in light of the long biking layoff and tiring runs the day before, but was still frustrating. I will also say that while I like cold weather while running, cold weather for biking was not fun! It made it seem 20 degrees colder than it really was. I'll definitely be using the cold compression gear next time out.

Up Next
My plan this week was to do "regular" runs on Monday night and Thursday, my first speedwork session tomorrow, lift on Wednesday and Friday, and then run in the Celtic Solstice 5-Miler in Baltimore on Saturday. I'll see how my back feels, but I suspect either tonight or Tuesday will get skipped. I'm also not sure how much I'll race the 5-miler. In 2009, I ran the Al's Run 8K in Milwaukee in 42:45. That's probably not achievable these days, since I pushed myself on pace in all my long runs back then and I really haven't done that since spring of 2010. I'd be very surprised if I could come in under 45 minutes and I think somewhere around 50 is probably a more realistic goal. I suspect the course will be crowded, and I know it's at a very scenic location, so I think the best strategy is to just enjoy myself, run a comfortable pace, and worry about smashing some PRs in 2012.

Saturday Long Run: So You're Telling Me There's a Chance...

If you read this blog regularly, you know I'm having a crisis of confidence regarding the upcoming Philadelphia Marathon because I haven't done as good a job getting my base miles in as I should have.

If you don't read this blog regularly, I'm having a crisis of confidence regarding the upcoming Philadelphia Marathon because I haven't done as good a job getting my base miles in as I should have.

I'd been debating what do with my long run today. Taper? Or try to get one more 20-miler in? I asked for and got lots of advice here, on dailymile, and on the Runner's World Philadelphia Marathon forum, and opinions ranged from "do it -- there's plenty of time to rest" to "No, at this point you're not going to gain any fitness and you run the risk of injury by not being rested on race day." Thanks again to everyone who gave me advice.

I decided to try for 20 miles, but set up my route as an 8-mile out and back so that I could easily stop at 16 if I didn't feel like going on. I wanted 20, but I know at this late stage it wasn't worth killing myself for. The second I stepped on the trail, though, I had the feeling that this could be a great run. I felt light, I felt fast, I felt strong, I felt like a Kenyan, I felt like a marathoner again...I felt so distracted by how great I felt that I guess I forgot to hit "start" on my Garmin for (I'm guessing) about 3/4 of a mile. That's ok, I know where the 8-mile mark is, it just meant my time would be an estimate.

I felt great all the way up, and if I'd had my four-bottle hydration belt, I would have gone all the way to York and back. Of course, if I'd had my four-bottle hydration belt it would have annoyed the daylights out of me. I started to tire around mile 13, but I had been eating sports beans every two or three miles throughout the run and I think that really helped.

I got back to Hanover Junction with my GPS reading 15.83, which is weird since I'm certain I ran more than .2 miles before starting it. I'm a bad distance estimator but not THAT bad, and I know that at least two songs had played before I noticed it wasn't running. I refilled my bottles, stretched my calves and quads out, and headed south. My new plan was to run a mile down and a mile back, so I could stop at 18 if I needed to. I was tired, but still felt good, and so I kept on going for two miles, and circled back and ran a little past Hanover Junction till my Garmin actually read "20.00."

(I ran 20 and lived to tell the tale and look like a dork.)

It was definitely my best long training run ever. I ran the whole 20 miles without walk breaks, though I did make three quick stops: a restroom break at about mile 10, the refilling break at 16, and a quick stop to photograph some cute goats at about mile 18.5. It took me 3:29:39, two minutes faster than last time, which means I probably was going faster last time and burned myself out, forcing me to walk.

I had no leg cramps during the run and my post-run stretching, which was very surprising and very welcome. I don't think I could have run 26.2 today without some walking breaks, but I feel like this puts me in line to at least equal my performance at Shamrock. Given the bad base miles situation I've gotten myself in, I'll gladly take that at this point.

(This friendly goat came over to say "hi", or probably "Hey old man, let me out of my cage.")

Overall, I couldn't have asked for a more beautiful morning for this run, and I couldn't have hoped to feel any better during it. I may regret this 20-miler on 11/20, but right now I feel my confidence needed the boost more than my legs needed the third week of tapering.

(While I was stretching at Hanover Junction after the run,
the sky was the deepest blue I've ever seen.
My crappy cell phone camera doesn't do justice how beautiful it was.)

Saturday Long Run: To the Pain

Between an insane work schedule, bad weather, and some kind of minor respiratory bug, I've had a pretty uninspiring two weeks of running. Even during the week before, when I pulled off a 19-mile long run, I'd had a week where I just didn't get my midweek garbage miles in. I say all this not to make excuses, but as constructive criticism of myself because all my failings caught up with me yesterday on the trail.

With a goal of 20 miles, I set out from Hanover Junction, taking the trail north toward York, since I'm familiar with the rest stop locations and the elevation changes along this part of the trail. I look forward to seeing the sights on more southerly parts of the trail, but a 20-mile long run is not, in my opinion, the time to explore. It seemed like my perfect running weather, low 40s and overcast. The forecast called for the sun to come out, so I had my trusty visor, but the sun never showed up.

I made a key equipment-selection mistake that I suspect contributed to my undoing. Violating a common-sense rule that every runner -- including me -- has heard over and over, I set out on my long run with two untested pieces of gear. The first was a new long-sleeve Nike running shirt, which I purchased last week. Despite the cold temperatures, I was sweating profusely within two miles. There's nothing wrong with the shirt. It's very comfortable, in fact. I just forgot who I am. I love to be cool/cold while running. I run in shorts and a tank top when the temperature is the 40s. This shirt seems considerably warmer than the cotton long-sleeve shirts I wear for (or at least the start of) my colder weather runs. This shirt will be great in December, January, February, but it just wasn't cold enough, by my standards, yesterday. I took it off just past two miles. Despite my miscalculation, I would become very glad that I had brought it.

My second mistake was a new hydration belt. I know that on a cool morning I can go 15-16 miles with the two bottles on my old Nathan hydration belt, but I thought that I shouldn't push that to 20. Though I can refill bottles at Hanover Junction, I wanted to run 10 miles to York and back, thinking this would be psychologically easier than a loop course with a break at either Hanover Junction or my car, if I parked somewhere else, and had to stop and start again. So on Friday night, I purchased a new four-bottle Nathan hydration belt. And while a differently-mapped course with a refilling stop might have been a pain, it would have been less annoying than bouncing around of the two bottles on my back and the constant re-adjusting of the fit of the belt. I'm very unhappy with this product. I'm going to elaborate further in a product review later in the week. Luckily, with the long-sleeve shirt tied around my waist, I could get the belt to fit tightly over it, so one equipment problem solved another.

(Equipment Fail. Taking the giant cat along probably wasn't smart, either.)

Still, my main challenge was that my legs just didn't feel strong yesterday. On my 19-miler two weeks ago, I stepped onto the trail and felt like the wind. Yesterday, I stepped onto the trail and felt like I was made of lead. Still, I pressed forward at my usual pace, and by mile 4 or 5, felt looser and more comfortable. I ran 10 miles north, which was my worst tactical mistake of all, which brought me just past York College but not all the way to the trailhead in downtown York.

After turning back south at King's Mill Road, I quickly began to tire. I really feel like I bonked just as badly as I did on last week's 13-miler, but since I'd run 10-miles north in my infinite wisdom, I was now doing so with 7 miles to run to get back to my car. My quads were on fire. Though the York County Heritage Rail Trail is a straight north-south course with no branches, somewhere I took a wrong turn, because at about 15 miles, I realized I was no longer in south central York County. I was in Hell.



After 16.5 miles, I started mixing in walking breaks. I ended up taking three, three-minute walking breaks spaced out a little over a mile apart. Unlike my walking breaks during the marathon, though, these seemed to help. My last walking break ended with a little over a mile to go. Running hurt, but I also knew that the more I ran, the faster this misery would be over.

With a mile to go, I saw a familiar friend ahead. But why was Pooka, our big friendly black cat, on the trail? Was I hallucinating? Had I actually died, and this was my spirit animal? That's disappointing. I would have hoped for an eagle, wolf, or some other cool animal. I think, in a weakened voice, I think I actually called out "Poooooooooka help me!" Luckily, I was the only one on this part of the trail because, of course, it was just one of the billions of other cats in the world.

Half a mile to go. A quarter mile. A tenth. In a final indignity, Garmin made me run about a tenth of a mile past Hanover Junction to get meet my goal. I collapsed on the porch of the old train station (which is now a museum and rest stop on the trail) to do my IT band stretches. With Garmin reading "20.00", I felt exhausted, but exhilarated; relieved that I'd finished, but angry at myself because I know that I could have done better these past few weeks and that the race is 6 miles longer than this brutal run. I had nothing left. Dead, but in my pain and exhaustion, more alive than I've felt in weeks.

Lessons learned/Notes:

• No new gear on long run or race day (duh!)
• Don't set up a course where I'm 10-miles away from my car (duh!), especially on the trail where there's not really a good way to have someone pick me up if I need it.
  
• Walking the water stations during the marathon would probably be a good idea.
• I have one more long run next week, technically supposed to be the 20-miler that I took today, before tapering. Then the taper is 12, then 8 miles in the two weekend before race day.
• The focus from here on out really needs to be on getting good, consistent, short runs in during the middle of the week. My schedule is going to be brutal the next few weeks, but I think I need to get in three 4-6 mile runs between Monday and Thursday each week.
• I didn't feel like my 2:45am peanut butter sandwich helped me. As much as I dislike .eating before a run, maybe I can't that much earlier than my run. I also ate one pack of Sports Beans. I think, since I prefer them to GU or Clif Bars, that I probably want to eat at least two packs during the marathon if I want them to help.
• This is my second-longest run ever, but I feel like my 19-miler two weeks ago was definitely a better run. I could have gotten 17 or 18 today without the walk breaks, but there was no way I was getting to 19 or 20.
  

(The best part was when I got back to my car.)

Saturday Long Run: Brian Runs 19 Miles and Encounters the Wall

I felt it as soon as I took my first step -- an electricity that seemed to rise up from the trail itself, burning away my doubts. This run could be amazing.

After painful calf cramping on my last two long runs, and a week where I generally ignored my midweek running -- I limited myself to four miles on Tuesday not out of laziness but due to exhaustion from one of the busiest and most stressful work weeks I've had in the last five years -- I had been extremely doubtful that I could run the 19 miles that Hal Higdon had ordered me to run this weekend.

I'd driven south the Hanover Junction access point on the York County Heritage Rail Trail, knowing that I needed to choose a less hilly setting to have any chance at reaching my goal, but I was not optimistic until that moment when I stepped out on the trail. I felt light. I felt fast. I was Kenyan. An extremely slow, pale Kenyan, but a Kenyan nonetheless.

My plan was to turn around at mile 5, refill my bottles at Hanover Junction, and then head south 4.5 miles and back. However, I felt so good at mile 5 that I kept right on going. I contemplated going all the way to the trail head at York, but a quick assessment of my water and Gatorade supply made me think that was a bad idea. So, I turned around after about 8.2 miles.

I started to struggle a bit at about mile 15, but after a refilling stop at Hanover Junction, with 16.4 miles under my belt, I felt I could run a bit farther south and turn around to bring me back to my starting point with 20-mile mark. But then, I met an old friend from Shamrock: The Wall. I crashed pretty hard at just under 18 miles. I turned around and struggled northward and stopped at 19. I was sore but not injured, but my legs just couldn't go one more step and I felt like I would be risking injury to press on in pursuit of a (in this case) meaningless mile.


So, I probably fell a little short of the "amazing" I felt I could achieve at the beginning of this run. I'd have loved 20 and it would have been a huge confidence boost (probably to the point that I'd be unbearably cocky and everyone would hate me), but this was my second-farthest run ever, and I'm really happy with it. I think the cool conditions at the start made it a pretty good simulation of the marathon, and I think I repeated a key tactical mistake that I also made at the Shamrock Marathon.

A few brief lessons learned/confirmed:

• Try harder to put the "S" in LSD -- I ended up at 19 miles in 3:19:36, putting me at a 10:28 pace, which is not far off my usual long run pace. As slowly as I was shuffling those last 2-3 miles, this means I was probably going way too fast somewhere along the route. I don't think my lame-o Garmin keeps accurate speed on the trail, but I have to do a better job of making sure I feel like I'm going slow. This was my undoing at Shamrock, too.
  
• More midweek miles are needed -- I didn't really hit the wall until mile 22 at Shamrock. I think more midweek runs, including back-to-back days, which are not my SOP when not on a training plan, gave me more endurance even though my longest pre-race training run was 18 miles.
• That Reebok visor I bought in the summer? Awesome. This seems like it was the first really sunny long run day in at least a month. It warmed up toward the end of the run (It was in the low 50s when I started, but was probably around 65 by the end), but this was the sunny, cool dry run where I think the visor is perfect. I definitely need to bring it to Philly.
• EAT BEFORE YOU RUN 19 MILES, IDIOT. I hate feeling "full" when I run, but the 3:00am peanut-butter sandwich would have probably helped me get that last mile in.
• There's no such thing as too much BodyGlide.
  
• When starting from Hanover Junction, there's more shade running north toward York. If I do other long runs on the trail, and I plan to, I might get a belt with more water bottles, so that I can run all the way to the end of the trail and back without running out of fluids.
  

Overall, it was one of my best runs ever, and I'm glad I got to enjoy this gorgeous day. Of course, I'm also going to enjoy my step-back week next weekend.

More Trail, Less Fail

I spent the week silently seething with rage over my highly unsatisfactory -- No! -- disgraceful run on the York County Heritage Rail Trail last week.

So, desperate for revenge, I set out southward from Brillhart Station determined to avenge my death!

Well...ok, the above isn't really true. I was ok with my run last week, but was hoping to do a little both in terms of preparation and distance. And I didn't really die. If I did, you'd be spared further blog posts, obviously.

Anyway, the part about heading south from Brillhart Station is true. It was a relatively cool, overcast morning, and there was even a nice breeze -- which the tall trees around the trail completely blocked. It seemed much more humid on the trail than it did otherwise, and so I think on mornings like this, where clouds are keeping the sun from just beating down on me and the actual temperature isn't too bad, I should probably stay off the trail and just run on the roads here in Manchester.

My preparation was a little better than last week. I remembered to both bring and charge Garmin, which worked really well on this relatively straight course. Although it would lose signal quite often due to (I'm guessing here) weather and the thick vegatation (Geez, Brian, you're making it sound like you were running in the stinkin' Amazon Rain Forest.), it seemed like it would "catch up" when the signal came back. That doesn't work so well on my twisty neighborhood courses, since Garmin assumes a straight line from where it lost signal to where I am when it picks it back up.

Because running on the trail is A) safer than running on the road since I don't have to watch for cars and also B) more boring than running on the road since I don't have to watch for cars, I decided to bring my Shuffle. Here, I failed again. I'd forgotten to charge it, and even though I have a USB charger on my phone's power cord, apparently a Shuffle of this generation needs to be plugged into a computer to charge. D'oh.

Overall, though, this was a nice run. I ran for seven miles, going past Hanover Junction, last week's turnaround point, and turned around. This worked out nicely. Since I take a pit stop at this access point to refill my bottles and eat some Sports Beans before setting out again, it made the run back seem a little shorter than the run down.

Here's a picture of Hanover Junction. as seen from the south.
Abraham Lincoln's train changed tracks here on its way to Gettysburg for the Gettysburg Address.

Until about mile 12, when my legs started saying "Hey Brian, we don't want to do this any more." I had sweating buckets for the whole run, but I was drinking water and (at that point) watered-down gatorade, and I'd taken a salt tablet before the run and at my pit stop, so I didn't think I was dehydrated or in danger of heat-related injury. I told my whiny legs to shut the hell up, and made i back to Brillhart and the safety of my car. In doing so, I abandoned a crazy plan, hatched at mile 10 when I briefly felt like I could run forever, to head a bit past Brillhart and turn around to add a 15th mile.

(This is what the rail trail normally looks like.)

(And here's what it looked like after I sweated my way back to my car.)

I'm really happy with this run. 14.13 miles in 2 hours and 19 minutes, for a 9:50/mile pace. It's my longest run of the summer (by .13 miles), but my pace for my only other 14-mile run of the summer, on July 15, was 10:00/mile, so this is a pretty nice improvement.

Time to eat the donuts.

People are Still (sort of) Jerks
Like last week, I said "hi" to everyone I passed. However, for some reason I got more responses today. I have several theories:

1. People who were on the trail last Saturday read my blog entry and realized that they are, in fact, jerks.

2. I appeared less creepy than last week. I didn't wear the visor today. Maybe the visor is creepy.

3. People saw how much I was sweating and didn't want to make me angry.

Further testing is needed.

Fail Trail

I've christened today's run "The Fail on the Trail". It wasn't a bad run, it was just kind of a meltdown of preparation and mental sharpness on my part.

Like I've said in most of my recent entries, I'm not really starting my marathon training yet, since I'm shaving the first few weeks of Higdon's Novice II because I'm already ahead of the mileage, but I was still hoping to get a longer long run in this morning. 14 was my goal. I thought I'd run on the rail trail, because it would give me a change of scenery and, if I started at Brillhart, the opportunity to stop and refill my bottles at the turnaround point at Hanover Junction. Brilliant! Since I wanted to beat the heat and be on the trail around 6am, I laid all my clothes and paraphernalia out the night before. That's not just preparation, that's extraordinary preparation!

I checked the always reliable weather.com (please consider the italics to be the sarcasm font in this case), and noted that today's low was predicted to be 67 degrees. Awesome! Anything under 70 is a gift I'll gladly accept. But, when I scrolled through the hourly forecasts, none of them showed lower than 74. D'oh! That's not terrible, but a little warmer than most of my summer early morning runs. With that in mind, I considered lowering my distance goals a bit, but instead decided that the shade of the rail trail and the built-in refilling stop would be too much of an advantage to give up.

Alarm went off at 4:30, and I'm ready to be out the door at 5:20. Clockwork. Except for one little thing...I saw that I hadn't put the plug from the charger into my Garmin fully, and it had less than an hour of charge.

FAIL

I like to have Garmin, despite its inaccuracy, since it lets me monitor my pace without having to resort to math, but this wasn't a critical error -- I still have my trusty Timex Ironman Triathlon (no sarcasm here, I seriously love this watch). No problem, everything was still going smoothly. I got to Brillhart station at 6:00am, and headed southward on the trail. I was running along, everything was going fine, and I don't need Garmin when I have an awesome and reliable stopwatch... that I forgot to start.

FAIL

A bit discouraged, I started my watch. I'm estimating I was only 3-4 minutes into my run before starting it. Not the end of the world, but I bet Meb Keflezighi never forgets to start his watch.

I quickly noticed that the humidity was humiditating rather heavily, but luckily the trail has a great amount of shade and it was mostly overcast, anyway. Of course, I'd opted for the visor, even though under these conditions it's unnecessary and even a minor detriment.

mini-FAIL

Within the first mile, I was already sweating profusely. In fact, people following me on the trail probably had to swim for it. My route turned out to be not as well-thought as I'd planned. You see, Chris and I had biked this same section of the trail on Tuesday night. This had the unfortunate effect of making it seem like it was taking forever to get anywhere while running. On a bike, the Howard Tunnel seems just a few minutes past Brillhart Station. Today, it seemed light years away (Really, it's about 2 miles from where I started/finished.)

FAIL

(Isn't it pretty? Doesn't it look humid?)

Once past the tunnel, things seemed to take a turn for the better. Using my now-running chronometer and the mile markers on the trail, I could tell I was running about a 10-minute mile pace, and I started feeling better, or at least getting used to how gross I felt. There was one close call where I thought I saw a snake coiled on the trail ahead of me (EPIC FAIL), but fortunately it turned out to just be a branch with some leaves.

I reached Hanover Junction in approximately an hour. It turned out to be between and six and seven miles away from Brillhart. I took a short break to drink some water and refill both of my bottles, and then headed north (to FREEDOM!)

The way back didn't seem to take as long as the way down (In reality, it took the same time or a few minutes longer.) I was still laying down between 9 and 10 minute miles and, since the trail is picturesque but really just running in a straight line, was bored out of my mind. All I could focus on was watching for the next mile marker, just wanting to get this one over with. Finally, it seemed, I reached the cool relief of the tunnel, which was just a cooler but more humid spot on this humid run.

(Crap. Is it "Come into the light, Brian." or "Don't come into the light, Brian"?)

From there, though, it was easy. Just two miles to go. As I reached Brillhart Station, my watch read 2:03:10, so I'm estimating my full run at 2:07. It turned out, according to the distance reading from Tuesday's bike ride, to be 12.76 miles.

Good enough.

Also, People are Jerks
As I ran, I said "hi" to everyone who passed. Maybe 1 in 10 returned my hello. I don't expect to become best friends with people I meet on the trail, but I'm running, they're running, isn't the bond of shared suffering enough to warrant a friendly greeting?

Several people have told me that they've noticed that solo female runners usually won't say hi to a lone male runner. Do I look like a creepy stalker? I've never stalked anyone, and I really don't think I'm that creepy looking. So thank you to the two ladies who did return my hello, you reassured me a bit that perhaps I don't look like an axe murderer. And even if I were, where I would hide an axe while I'm running?

There was one guy in particular that I thought was a jerk. He was definitely a better runner than me, catching up to and passing me after starting at Brillhart a few minutes after me and then pulling way ahead of me. I said hello as he passed, and was greeted by a stony silence. At what I believe to be the 5-mile mark (based on a previous bike ride along this course), he turned and passed me going the other way. I said hello again, and this time was glared at for my troubles.

Well Mr. Cool, I'll have you know that while you may be (much) faster than me, I continued on to Hanover Junction and back again, and I believe that makes me the better man.

So, that's the end of today's rant. Am I off-base here? What's proper running etiquette in this situation -- hello or no?

Back on the Trail

(York County. We put the "rail" in Rail Trail.)

We hit the York County Heritage Rail Trail again on Monday morning. This time, we started at Brillhart Station, south of York and headed southward to Hanover Junction, which is south of Seven Valleys and back. (I know these names mean nothing to anyone outside York County -- and I admit I'd never heard of Hanover Junction and I've lived in York most of my life!)

(Oh, THAT Hanover Junction.)

Our ride totaled just over 14 miles in an hour and a half, so we improved on Saturday's ride in both pace and distance. It was a very warm, humid day -- it didn't feel bad on the bike but it would have been murder to run in. Thus, I felt kind of like I was cheating. Did the few runners few runners on the trail look at us and think "What a bunch of wimps?" Probably. Were other bikers laughing at our 20-year old Huffys? Probably.

Who cares?

(You won't find any carbon fiber on this bike!)

(This IS my "powering through the mountain stages" face.)

It was a nice way to spend the morning. I'm looking forward to more rides on the trail this summer and also doing some running there in the fall when cooler temperatures arrive. The trail offers more shade than the neighborhoods where I run in the mornings now, but since the closest access point is 20 minutes from my house, it's not a good option for trying to get out early and beat the heat on weekday mornings.

(No one knows how the ancient peoples of Seven Valleys erected these bicycle statues
2000 years before the time of Christ.)


(A good time was had by all.)

I'm taking Tuesday off, and then resuming running on Wednesday, so this will be a lighter week than last week, but like I said last post, I don't think that really matters. Right now my legs aren't sore, but they are tired. I'm hoping that mixing in some biking this summer will eventually make me feel stronger when I get into my deadly-serious, intense, Novice marathon training. Maybe cross-training can be right up there with packet pickup and carb-loading in the parts of the marathon that I'm good at.

And Time Doesn't Wait for Me, it Keeps on Rollin'

I'm undisciplined about a lot of things in my training. Speedwork, tempo runs, and cross-training among them. (I've got long, slow, distance down though!) But I think I've found my cross-training for the rest of the summer and fall, though.


Today, Chris (my wife for any newer readers) and I took a gorgeous 12-mile bike ride on the York County Heritage Rail Trail. Our ride took us an hour and a half, but we weren't looking to set any land-speed records. In fact, I am much more likely to set a speed record for flying over my handlebars and smashing into a tree. We just wanted to explore this new (to us) place to ride and make sure we left enough energy in the tank to get back to the trail head in downtown York, since the ride out seemed mostly downhill. The way back didn't seem as hilly as I thought it might, though, so next time we can push our pace a little bit more and or head further south -- the trail goes 20 miles down to the Maryland line.

(I'm not so confident on the bike, yet. Here I fell behind as we crossed the street.)

We didn't go quite as far as we'd planned, but it was gorgeous ride on a beautiful day, and I'm looking forward to more adventures on the rail trail this summer. Great idea, Chris. I'm glad I tagged along!

(We turned around just south of the Howard Tunnel, one of the many interesting sights along the trail.)