Eleven miles at Bethpage, without fuel nor water

Today’s run (Bethpage State Park): 11.2 miles

I had plans to run with my buddy Dave today, but he had a scheduling issue and needed to postpone. The plan was for Dave to accompany me on his bike while I ran. Last February, I wrote a post about Dave’s racing nightmare when he suffered a heart attack during a 10 mile race. Since then he has responded well and has been cleared for runs in the 2-3 mile range. It shows that even if you suffer a heart attack, being otherwise fit will certainly accelerate your recovery.

The temperature was in the high 30’s when I went out at at 8:30 AM, and I’d purposely under dressed knowing I’d be generating heat over my long run. I wasn’t that uncomfortable, even at the beginning, and by mile two I was glad to be in running shorts.

I wore the Spiras thinking they would minimize the possibility of foot problems, but I detected the slight pain in my left foot that I’d assumed was specific to the Kinvara 3’s. After a few miles the pain decreased and I thought I had it licked. Turned out it wasn’t so simple. By the end my feet were very uncomfortable.

The only nutrition I took for the entirety of my run was a GU gel that I had prior to the start. I took along a GU Roctane for refueling later in the run, but I didn’t feel as though I needed it. I also brought a water bottle but didn’t take a sip during the run. I wasn’t being macho by denying myself nutrition and hydration, I just wanted to test whether I needed it. Did my body use fat as an energy source after glycogen depletion?

After many weeks running the Bethpage bike trail, I’ve become familiar enough with the route that I know how far I’ve gone without looking at my Garmin. I also separate the course into stages, based on landmarks. That helps me psychologically, especially as I increase my distance each week. Today I ventured within a mile of the bottom of the trail, located in Massapequa Preserve. I may end up doing an end to end run next time.

On my way back I was happily surprised that my energy level never fell too far and when it dropped a little, I quickly rebounded. I saw many runners, walkers and cyclists today and one sap who was walking along the trail, smoking a cigarette. Why do something healthy like that and smoke?

I did experience a drop in energy with about 2 miles to go. I knew I was facing the toughest part of the route and resigned myself to the work. Running the penultimate hill was easier than I thought it would be, but the final hill was a bear. Still, I finished 11.2 miles feeling in better shape than I did when I ran 9 miles a few weeks ago.

I’m on vacation this week and next weekend is the Marcie Mazzola 5K (on Sunday). Due to that, I’ll skip my base run as I taper. From now until then, speed will be my focus. I’m curious to see if all this base building will help me push the pace over a decidedly shorter distance.

The declining accuracy of my Garmin FR210

I’d add 3% just to be safe

Today’s run (street): 2.53 miles (Gmaps measured)

I’m not sure why, but my Garmin FR 210 has been under-performing lately. It was especially bad this morning. I generally run the same route every day at 4:00 AM and, after careful measurement, I know that the distance is exactly 2.53 miles. The Garmin’s margin of error is generally -3%, which means that it under-counts to that degree fairly consistently. Since it is consistant, I accept that variance and correct for it in my pace calculation.

It’s no mystery why this happens. Looking at my run captured in Garmin Connect, I can see that the watch will vectorize corners and straighten out curves. This is due to the capture time between GPS signals (approximately one sample per second). If the signal was captured continuously, the course would be displayed accurately, with no corners cut, etc. When it’s cloudy, the signal can get interrupted. When that happens, the watch interpolates the distance between signals as a straight line. Enough of those and your accuracy really suffers.

Lately my FR210 has been under-reporting by about 5% and this morning it came in at -7%. It was cloudy, but clear enough to see some stars. My run could only be described as slow, and with the under-counted distance, my watch recorded my pace as glacial. Correcting for the true distance, it was still the slowest 4:00 AM run in memory.

I’m puzzled as to why my Garmin’s GPS has become less accurate of late. Perhaps it’s just going through a bad spell. The GPS accuracy tends to be better when I run a mostly straight course like at Bethpage. I’ll see how it does tomorrow.

Base training has its benefits and so does peppermint oil

Today’s run (street): 4.8 miles

Happy feet guaranteed

One of the benefits of base training is that it redefines the scale of a challenging run. For instance, over the winter the average distance of my weekend runs dropped to about 3.75 miles. That meant that any run greater than four miles was an envelope pusher. It didn’t mean that I couldn’t run 6 miles or more, but it would have felt like a lot of work to do that.

My training plan has me covering one extra mile on my long weekend runs each week. I’m building up to a final base run of 12+ miles prior to the half marathon. Yesterday I ran 10 miles and today I covered 4.8. I went out with the intention of running between 3 and 4 but it felt so easy (I wasn’t really pushing the pace) that I extended my route to almost five miles.

While these longer Saturday runs are making my Sunday recovery workouts feel easier, my feet have begun to protest. It’s been a long while since I covered the equivalent of a half marathon over the period of a weekend. I’ve done just that over the past three weeks. Foot soaks with peppermint oil soap have helped a lot. I recommend it to anyone.

I’m feeling more prepared for the Half than I was last year. Eleven miles is on the schedule for next Saturday. Hope it doesn’t rain again.

Building character on the Bethpage trail

Today’s run (Bethpage State Park): 9.1 miles

Today is supposed to be the better weather day this weekend, so I headed to Bethpage this morning for my long base run. It was tough week in the office, and I addressed my sleep debt by getting eight full hours last night. I hoped the extra rest would carry me through what would be my longest run (so far) this year.

Although I have a brand new pair of Saucony Kinvara 3’s sitting in a box, I decided to do today’s run with the Spiras. I didn’t want to discover any fit problems with the Kinvaras that I’d need to endure throughout the bulk of my run. Still, I was concerned that I’d have a recurrence of chafing at the back, along the Achilles, that I’d experienced last weekend.

Bethpage’s lot had many more cars than usual, probably because it was the first weekend of Spring. I also arrived an hour later than I usually do, owing to my later wake-up time this morning. As I made my way through the initial hills, I saw numerous runners along the way, most of them heading north to the start of the bike trail. The Syosset Cross Country boys team were running hill repeats on the big hill and it reminded me of when I did that last year to prepare for the town of Oyster Bay Supervisor’s 5K.

There must have been forty high school age runners on the path today, I kept seeing them coming from the other direction at different points in my run. They all looked strong and fast and I was glad they weren’t going my way because it would have been humiliating to be passed dozens of times. Surprisingly, I was only passed a couple of times today.

I knew I was in for a better experience than last Saturday’s because I still felt plenty strong at the Southern State crossover that led into the Massapequa Preserve. I came up behind a couple of runners that I hoped would pace me a little, but I ended up passing them because they were running a little too slow. I U-turned after covering four and a half miles and prepared for the second half of my run.

I had no issues with the back of my heel today but I did have some chafing problems with my small toe on my right foot. It got fairly uncomfortable, but I didn’t stop because I knew there wasn’t any quick fix for it. As much as I like the Spira’s I’m noticing some small fit issues that come out on longer runs.

Despite the foot issue, I felt very strong throughout the run. It seemed to take little time to get to the seven mile mark today. I didn’t take any anything for an energy boost and only sipped on a little water late in the run. At Bethpage, the last two miles is what I call the “character-building” phase of the run. There are some smaller rises and some steep short sections, with a few downhills to balance it out. But, inevitably, the last hill awaits. There’s no escape.

Despite arriving at the 8.5 mile point, I still had good energy as I made my way uphill and I even passed another runner on that section. The best part of the bike trail is the short, steep downhill that leads to the parking lot. I embraced it fully today and carried my run an additional tenth mile back to my car.

So despite missing a couple of morning runs this week, I feel on track for my Half Marathon training. Next weekend I may need to do my long run on Sunday so I can get in some speed work on Saturday. Before the LI Half is the Marcie Mazzola 5K. I’m hoping that a good base and some fast twitch activation will yield a decent time for that race.

Test at Bethpage: Gatorade G Series FIT Perform 02

Today’s run (Bethpage State Park): 7.35 miles

Nice bottle, but no thanks

I had a mid morning appointment today and that forced me to get out for my run before 7:00 AM. My plan was to get to Bethpage and run the bike trail, covering at least seven miles. I’d rested on Friday because I wasn’t feeling great, and I hoped that would give me a performance boost today.

I brought along a bottle of sport drink with a very long name: Gatorade G Series FIT Perform 02. It’s an electrolyte mix that’s meant to be consumed during a workout. I was testing this mix to see if it’s something I should carry during my half marathon. I’ve learned that satisfaction with performance supplements, like gels and drinks, varies greatly from person to person.

Almost from the start, I could tell that I wouldn’t be burning up the trail today. I had none of the energy I usually expect for these long, early morning runs. I thought it would be a good test of the G Series mix, and a good gauge of my ability to cover 7+ miles when starting with an energy deficit. As I started my Garmin, it chirped and showed “Low Battery.” Like my watch, I hoped I had enough power to get through today’s run.

Considering my low energy, the first couple of miles went by fairly quickly. The temperature was hovering around 30 degrees, but the winds were strong, especially on the way back. I reached the point where I expected to hear a chirp signaling three miles and when I looked at the Garmin the screen was blank. Later, when I recharged the watch, I saw that the battery had given out after 2.61 miles.

Along the way I sipped from the G2 mix, hoping that it would restore my depleted energy levels. The “melon-pear” flavor tasted neither like melon nor pear. In fact it didn’t taste like much of anything. Since I didn’t have an easy way of knowing how far I’d run or how much time I’d been running, I decided to turn back at a place I could locate on Gmaps so I could measure total distance later.

There were many runners on the trail this morning, mostly running in pairs or in groups. I would have felt lonely except that they were all running faster than me. I wouldn’t have been able to keep up with any of them today. I suspect it was the early hour, when competitive club runners go out for long distances before they start their day.

I wasn’t hurting, exactly, but I never felt strong as ran along. I started taking sips of the G2 more frequently as I got closer to the end. The last 1.5 miles of the Bethpage bike trail has the most pronounced hills and I needed a boost, even if it turned out to be more psychological than real. As I approached the final long hill, I decided I’d just pace it fast enough so that I could call it running. At that moment, a group of sleek, fit, compression-clad men and women ran by on my left, chatting away as if this hill was a bump. How humiliating.

After I finished my run, I saw that the G2 mix contained nothing to help my energy stores. The whole 16 oz. bottle contained only 5g of carbs  and 4g of sugar. I’d consumed about half the bottle, so all I got was 110mg of sodium and 30mg of potassium. And it also made me a little queasy. So this mix will not be accompanying me on my half marathon in May.

I accomplished a good part of my weekend distance goal this morning. I need to cover almost 6 miles tomorrow to make my “weekend 13”. It’s not an unreasonable target, but I hope to feel more energized on Sunday.

When a run goes according to plan

How I spent my morning

Today’s run (street): 6.2 miles

My morning running plan was happily free of debate. No decisions to make about my route, gear or distance. I’d prepared to run 6 miles on the roads around my neighborhood and the cloudy and dry weather looked perfect.

I started by running the loop I use every morning to benchmark my first mile. After that I diverted my course by running towards the middle school. Once I got there, I ran across the field to a path that took me to the nearby business park. I continued in that direction and ran the hilly loop before exiting into neighborhood #3 at the three mile point.

I felt good as I moved along these neighborhood streets that led me out to Woodbury Road, a heavily trafficked street. Running along Woodbury Road’s sidewalk is always interesting. In the fall there’s often a thick covering of leaves that cushion each step. Today the sidewalk was bare and covered with packed dirt.  Except for the cars whizzing by on the street, I felt like I was doing a mini trail run.

I reached the easternmost point of my run and then switched directions back toward my house. I was on track to cover my intended six miles and ended up making it with a little distance to spare. I didn’t run this route particularly fast but I was satisfied with the effort and pleased to have run a dozen miles over this weekend.

The best part of finishing a couple of good weekend runs is knowing that Monday is my rest day. Another 20+ mile week is in the books. So far, so good for my half marathon training plan.

Seven hard miles at Bethpage

Today’s run (Bethpage State Park): 7.25 miles

It wasn’t exactly night and day, but today’s run went far better than yesterday’s struggle on the trails. I really wanted to stay in and skip my run, but my wife pushed me out the door saying that I’d complain all day if I didn’t get my run in.

I decided that a long run was in order, so I went out to Bethpage around 9:00 AM.Yesterday I’d confirmed that the park would be open this week. The last time I visited (admittedly many weeks ago), the gates were closed and locked with a sign saying “Park closed to winter sports.”

There were only a few cars parked in the big lot so I found a spot near the entrance to the bike trail. I was a little nervous when I started off, concerned that I’d be once again plagued with low energy and sore legs. By the time I reached the top of the first hill, I knew I had enough fuel to get me halfway through my intended seven miles. The question was whether I’d have enough to get me back.

The weather was very nice — mid 40’s, clear and sunny. Being that it was the middle of the week, there weren’t too many runners and cyclists, although there were some. I bounded down the big hill knowing that, when I returned later, it would not be so much fun. I always dread that last challenge, especially after many miles of hard running.

Bethpage’s bike trail is rolling, with very few flat sections. There are a couple of steep hills to deal with between miles one and two. At least on the way back you get nice downhills when you need them. It’s much easier for me to run long distances at Bethpage than almost anywhere else, because it’s a linear course and therefore easier to gauge progress.

I felt fine through the first three and a half miles so, after the turnaround, I picked up the pace to get past a group of walkers who had suddenly appeared ahead of me. Taking on seven miles today was a calculated risk because I have not run that distance in months. My current base is closer to four miles and by mile five I was starting to feel fatigued.

There’s a point about 1.5 miles from the trail head where the path rises steeply over a short distance. On the way out it’s not a problem on fresh legs, but on the way back it can be a struggle. I used my usual technique of pretending I was running downhill which works okay on 2% grades, but not so good on this monster.

I did manage to get over that hill and enjoy a mostly downhill run over the next quarter mile. Still, that final long hill loomed large and I just kept thinking about how good I’d feel once I finished. The hill was as hard as I thought it would be, and only the view of the top and the level road that followed, kept me going.

I finished my run and semi-collapsed in my car’s seat, guzzled 20 oz. of water and headed home. Tomorrow I’ll take it down a notch and do an elliptical session at an easy pace. Today’s run was my longest in months, and it felt very hard. Hopefully it will push my base a little further. The half marathon is in May and I have a long way to go before I’m ready.

Putting in the miles before putting in the rest

Today’s run (street): 4.6 miles

My energy level still hasn’t rebounded, and the only thing that got me out the door today was the promise of an easy run. Yesterday’s workout was surprisingly challenging, telling me that I’m due for some rest. But the lure of the open road was too tempting this morning, so I decided to go out for a run, regardless of the time it would take to cover my distance.

I followed a route by the nearby middle school where I ran by a bunch of guys playing a serious game of flag football. They had parked their cars along the road and I was amused to see both a Maserati and a Maybach among the numerous Honda’s and Jeeps. Sunday morning football is the great equalizer. I continued on with the intention of covering four or five miles.

Like last Sunday, I kept my pace easy and ran fairly well. There was an unexpectedly stiff wind coming from the east that made things uncomfortable when I faced it head-on. I’m looking forward to tomorrow’s rest day where I can (hopefully) recover enough to take on seven miles mid-week. So much for getting a long run in this weekend. But with a full week of vacation ahead, I should have plenty of opportunity to put in the miles.

Committing to the distance(s)

It was a good weekend for running. Two colleagues who always check in with me on their weekend running both reported great experiences. I had a decent long-ish run on Saturday and an invigorating trail run yesterday, on a course best described as nature’s roller coaster. This morning I was pleased to hear that my friend and colleague FS achieved a PR for a 10K race on Saturday. She wasn’t even trying to do that. It was the zen of the run.

My goal for this month was to exceed 70 running miles. After tomorrow’s run I’ll probably come in just at 69. I averaged 73 running miles per month in 2011, plus three miles per week on the elliptical machine. I think I made a critical mistake by under-training on distance in the three months preceding my half marathon. My training mileage peaked in March at 74 and plummeted to below 60 in April. No wonder I struggled in the last miles of that race in early May.

For the first time ever, I’m going to write out a training plan that will help ensure that I cover the distances I need to get my base up where it needs to be. It’s nice to head out the door with no plannned distance. I can cut it short anytime I feel like it. But if I go out knowing that I can’t come home until I’ve reached seven miles, I’ll make sure I do just that.

Today I ran like a Kenyan

As if

Today’s run (street): 5.4

Don’t be impressed by the headline of this post, I wasn’t channeling Geoffrey Mutai winning the ING NYC marathon this morning. Quite the opposite, actually. While Kenyan runners regularly hit five minute miles in competition, they tend to do their long recovery runs at an extremely slow pace. That was my plan today and I kept to it.

The training schedule that I’ve followed over the last few years has been to run five days a week, with additional cross training on a 6th day. I rest on Mondays unless I’m not feeling well or if I’m tapering for a race.

With a schedule like that, I shouldn’t have issues with running strength or stamina but I sometimes hit the wall around 30 minutes into a run. Since my policy has always been, “Once I start, no stopping” I run through these low points and will occasionally rebound strongly. People have said that even though my frequency is high, my base is fairly low. This is true. My weekday running distances average 2.5 miles due to time limitations. On weekends I’ll go longer, but the shorter runs play havoc on my base.

My monthly mileage numbers this past November and December were down about 10% from the prior year. I know it’s because I wasn’t consistently doing 7+ mile distances as I had in 2010. I’ve decided to work on my base with 5 miles being my lower limit for weekend runs. Last Sunday I ran the 5 mile Hangover Run and this morning I did a 5.4 mile neighborhood run.

Five miles isn’t particularly long but I needed to motivate myself to get out today after suffering three tough runs since Sunday. I figured that running slowly would make it easier — and it was —  until I hit 4 miles and started to suffer fatigue. I didn’t fully understand why, since I’d run over a minute/mile faster last Sunday. Unfortunately, running like a Kenyan didn’t yield the results that I’d hoped to attain.

A week of tough running has convinced me that I need to give myself a two-day break to restore my fitness to normal levels. Since I can’t resist running on weekends, I’ll target Monday (my usual rest day) and Tuesday as recovery days. I’ll see if that does any good when I get back to it on Wednesday.