How far can you run in 80 minutes?

Today’s workout (elliptical): 24 minutes

Back in the early ’90’s I was running three or four days a week on average. My runs took place primarily on the streets of NYC and, with no technologies to track my distance, I never really knew how much ground I covered. After tracing my typical route in Gmaps I now know that it wasn’t much. My average run was probably two miles (if that) and progress was frequently interrupted by stops at crosswalks.

I remember once having dinner with my running partner and another couple who were also runners. The guy told me that he ran about 25 miles a week and that amazed me. I’d responded by saying that was practically like running a marathon every week. I recall wondering how he found routes that were long enough to compile that distance. Today I typically run 20 miles per week but my average distance per run is only about 3.75 miles. I do more distance on weekends with my longest run (to date) being 8.15 miles. I ran that in 74 minutes.

I’d like to push my distance further and have decided to see how far I can run in 80 minutes. I just need to find some place where I can do that without traveling the same ground over and over. I can get about seven miles out of running within my neighborhood and the two others that border it but breaking out further requires crossing some major roads which I’m loathe to do. It would be fun to run with some destination in mind but that will take some planning and coordination. With the three day weekend coming up I’m hoping to find an hour and a half to try the 80 minute plan. Even after almost two years I haven’t run nine miles straight. My run-against-time plan could help me reach that goal.

Energy drinks. Really?

 Today’s run (street): 5.5 miles at 9:30 per mile

We’re celebrating my daughter’s 12th birthday today. Among other activities we made a visit to the local bowling lanes this morning. I’m not a fan of bowling, and no offense to those who are, but I have trouble viewing it as a sport. That’s why I was so amused when we took a break so the kids could play some arcade games and saw this display of energy drinks in the vending machine.

An impressive display of energy drinks

Do you really need a 16 ounce can of Amp or RockStar to get you through the rigor of rolling a ball down a lane twenty times? Maybe so. My daughter and son wanted to bowl and I was expected to participate so I did my best. My wife is a good athlete and has no problems with the game but I have little skill with it. I quickly noticed that each time you take a turn the scoreboard displays the speed of the ball, presumably when it hits the pins. Now the game was interesting for me. We bowled two games and though I barely broke 100 each game I managed to improve my average speed from about 16 MPH to close to 20. I never did reach 20 but I came close – 19.86 MPH was my best of the day. With that, a good time was had by all.

Next time I break 20!

 Earlier today I went out for my first weekend run. I didn’t have a great night’s sleep and started with less energy than I normally have at 7:00 AM. I had no allusions of speed but I wanted to get some mileage in. I hadn’t run more than four miles since last week’s race so I figured today would be a day to do that. It was cool when I went out and I watched my heart rate to maintain a pace that kept me about 70% of max. No heroics for me, especially since the humidity was about to climb. I made my way over to neighborhood #2 where I did most of this morning’s run. By 7:30 there were lots of people out, preparing for the day’s activities, washing cars, walking dogs and running. I followed a different direction just for the change of scenery although it really just amounted to looking at different cars and houses. By the time I re-entered my neighborhood I had about 4 miles done and my heart rate had risen to over 80% of max. I covered another 1.5 miles before finishing with a total of five and a half. I then made a beeline to the pool for a cool-off dip. Perfect.

I’m not sure how much I’ll run tomorrow. I’m thinking that a visit to Stillwell may be a nice change from the road and I’ll see how I feel when I get up. In the meantime I’ll enjoy the activities still to come as we continue the celebration of our daughter’s birthday.

Walking for a cause and running just because

The Emerging Runner family walks for a good cause

Yesterday’s activities: 1.5 mile walk-a-thon plus  2.6 miles (street run) at 9:37/mile

Today’s run (street): 4.4 miles at 9:10/mile

It’s been an active weekend that started yesterday morning with the start of the Nassau County Red Cross Walk-a-Thon at Eisenhower Park. My wife works at the Red Cross as a volunteer so the Emerging Runner family spent from 8:00 – 11:00 AM helping to set up and manage participants who had come for the 1.5 mile walk. After Friday’s 6+ mile run in Central Park I was feeling the residual effects of the hills but I thought the walk would be easy and fast. It turned out that 1.5 miles seemed a lot longer than I’d imagined but I enjoyed every step. It was a strange morning for weather, alternating between overcast skies, bright sun and a 15 minute downpour that had crowds of people running for cover under makeshift tents.

My wife, son and daughter and I set out on the walk at a good pace and I enjoyed seeing the park from a different perspective. There were lots of runners out in the morning and I wished that I had worn running clothes but this was really about walking and family time. We had a lot of fun and the turnout was excellent considering all the bad weather that had been expected. Later on that day I decided to do an easy run around the neighborhood. The sun had stayed out and it had grown a little warmer but the winds grew increasingly stronger throughout my 25 minutes of running, I didn’t run fast but I wasn’t concerned about pace. It was nice to get a run in on Saturday, however short.

This morning I headed out early because it’s Mother’s Day and I wanted to be as available as I could for the rest of the day. My kids set up breakfast for my wife downstairs while she did her daily workout upstairs. I slipped out and did a neighborhood run going in the opposite direction of my usual loop so that I could fold in the longish hill on Jericho Turnpike. I still felt some residual tiredness from Friday but I decided to maintain a faster clip than yesterday and completed 4.4 miles at 9:10 per mile. I was very pleased with the pace because my effort level was low while my enjoyment level was high. It was still early when I returned home. So far, we’ve had a full day with plenty of time left to celebrate Mother’s Day.

Lengthening my long runs

Today’s workout: Rest day

A “long run” has different definitions based upon who is doing the running. For some, it’s runs over 13 miles with the half marathon length serving as the demarcation point. For others (like me less than two years ago) a 5K can be considered an aspirational length. I have been thinking about yesterday’s run and how it felt to break a personal distance record. Could I have gone on longer than the eight miles that I’d covered on Sunday? As a practical matter the answer is yes. I stopped when I did because I’d met my goal of eight miles – four out and four back. If my distance goal was nine or ten miles I probably could have accomplished that as well. I finished my run at eight because I had nothing more to prove on Sunday.

I have a goal of doing a 10 mile run this year. It’s a distance considered by some to be a nice training run while others view it as an impossibility. I’m happy that it is at least a possible distance for me at this point.. Looking at my splits for yesterday’s run, I noticed that my pace dropped measurably after an hour’s running. I ran the first 6.2 miles averaging 8:57 per mile but miles seven and eight were far slower, closer to 9:30. I really liked running for longer than an hour. It surprised me that I had enough energy to pass other runners even near the end. Perhaps I’ll look at increasing distance as my next focus point and worry less about pace. Well, maybe just a little less.

1,000 calorie run at Bethpage State Park

Today’s workout (Bethpage bike trail): 8.15 miles at 9:10 per mile

Not counting last year’s Cape Cod marathon relay in Falmouth where I ran 9 miles across two non-consecutive legs, I established a personal distance record on today’s run. Unlike Falmouth, today was an uninterrupted run that covered over eight miles in an hour and fourteen minutes. I’d made the decision not to run this morning’s RXR 10K and, perhaps out of guilt for not racing, I decided to do a long distance run on my own. In order to break out of my usual 5-6 mile doldrums that have been standing in as my long weekend runs over the last couple of months, I knew that needed to leave the neighborhood to help frame out a longer run.

I headed to Bethpage State Park and paid my fee at the gate. I tried to buy an Empire Passport on the spot but they only accepted a check or cash and I only had a little cash and some credit cards. I began my run at the end of the bike trail and immediately met the sharp but mercifully short initial hill. Once level I knew that I’d enjoy a long downhill at the half mile mark. The enjoyment was bittersweet because I knew I’d need to climb that long hill upon my return when I would be depleted from an hour-plus of running. I followed the trail for four miles and passed a number of runners and walkers and winced each time a cyclist whizzed by from behind a little too close for comfort. At one point two cyclists, who were riding side by side, came toward me and would have run me off the path but I stood my ground. Unfortunately for the closer rider, the end of my elbow struck his arm and produced a yelp. I apologized by yelling “share the road!” I think they learned their lesson. At least they didn’t come after me.

A funny thing about the Bethpage bike trail is that it often gives the illusion that you are running uphill even when you’re not. As I made my way for the 4 mile out segment I kept thinking how I’d enjoy the downhill side of the hills I was encountering. I turned around shortly after crossing the overpass to the Southern State Parkway and was dismayed as I headed back for the second 4 miles that the path seemed to run uphill. I still had plenty of energy at the midpoint so the hills were easily met but in the back of my mind I was dreading the long uphill stretch I’d encounter between miles 7 and 8. I caught and passed a few more runners and walkers and monitored my Garmin to make sure my heart rate was staying within range. I managed to keep my pace around 9:00 per mile for most of my run but by mile seven I slowed down to the mid-9:00 range, especially on the run-ending hills. The only time I questioned whether I could finish what would be a personal best for distance was leading up the big final hill. When I got there I just dug in, took smaller steps and hoped it would soon be over.

In the end I covered 8.15 miles and when I looked at the run summary on the Garmin I saw that I’d expended exactly 1,000 calories over the course of my run. I’m pleased that I’ve broken the 8 mile single run barrier and I feel better than I thought I would after all that work. Some day I’ll run 9 but for today, the record stands at 8.15.

Two good runs: one fast, one slow, both hot.

Yesterday’s workout (Central Park): 3.25 miles at 8:52 per mile

Today’s workout (street): 5.48 miles at 9:21 per mile

In terms of effort I’d say both today’s and yesterday’s runs were about even. It’s hot today and it was hot in NYC yesterday when I trekked over to Central Park. I much prefer the cooler seasons for running but I also appreciate the way the trees and plants bloom in late spring and summer. The Park was filled with runners, cyclists and walkers when I arrived and I made my way over to the bike path on the lower loop to start my planned 3 mile run. My friend Steve had a conflict so he couldn’t join me today so I decided to go it alone for a run that followed the lower and upper loops below the reservoir. I knew that the hardest part of the run would happen in the first half because a good part of that route is uphill.

Surprisingly, it took me about a mile to break a sweat but once I did I got REALLY hot. I cut across the Great Lawn and headed back down, hugging the shade and happy to know that a few downhills awaited me. I’d maintained a decent pace even with the uphill challenges and I passed a number of runners although I also got passed a couple of times near the end. By the time I returned to my starting point I was glad to finish, cool down and head back to the office. A meeting had spilled into my planned running window that caused my run+lunch timing to be very tight. I quickly changed, grabbed a fast bite and finished a minute before my 2:00 meeting. I was glad that I’d run an 8:52 pace or I might have ended up being late!

This morning I headed out for a neighborhood run with no planned route in mind. I intentionally ignored the Garmin because I didn’t want to influence my pace in any way. Although it was hot and sunny I figured that I could a cover some good distance as long as I didn’t push too hard. I did check my heart rate throughout the run to ensure I was keeping to around 80% of max. I traveled through my neighborhood roads and cut across to neighborhood #2 at the 2.5 mile mark. I chose some different streets that I hadn’t run before, just for a change. I wound up covering 5.5 miles and finished feeling like I’d done a lot of work this morning. I need to work more on distance so I’m considering heading to Bethpage tomorrow to run the bike path where I can cover 8 to 10 miles out and back. Either that or a return to Stillwell to begin training for the next XTERRA race.

A tale of two 3.5 mile runs

Yesterday’s run (Central Park): 3.5 miles at 9:12/mile

Today’s Run (street): 3.5 miles at 8:45/mile

Yesterday I was excited for the chance to do another run in Central Park. It was a busy Friday and I managed to wrap up morning meetings in time to change and meet up with my friend Steve for the jog up to the park. The skies were bright and the sun was out but the 57 degree temperatures felt cold on the building-shaded streets. We started our run at the 6th Ave. entrance on Central Park South and made our way to the lower loop to run counterclockwise to the north. Steve admitted to really feeling last Friday’s workout for a couple of days after our run but he said he could do six today. I told him that he may feel differently once he started to encounter the hills. We set off at a decent pace, low 9’s, and enjoyed watching all the activity in the park. At one point we were set upon by a group of tourists on bicycles who didn’t seem to understand the concept of sharing the road with pedestrians. We also saw a person running around wearing Kangoo Jumps that look like in-line skates with elliptically shaped spring devices on the bottom. He certainly got some energy response from the shoes. Looked like fun but I’ll stick to my Brooks for now.

Once we reached the reservoir we followed the path on the southern edge and then headed south. Steve was very glad at the 2 mile point that we weren’t really going to run six. He did a great job keeping up with me and I told him his reward would be downhill running to balance all the hills we’d hit on the way up. We ended up covering 3.5 miles and felt fresh, even at the end. Good thing too because we both had long afternoons ahead. We walked south back to our offices, energized for the rest of the work day.

I woke up this morning with a headache that I attributed to sinus pressure. Rather than hoping it would just go away on its own I took a Sudafed and ibuprofen and chased them with a strong cup of coffee. I headed out around 8:00 AM for my run. I warmed up after about a mile and covered a route that took me first around and then through the neighborhood. I was concerned that the effects of the Sudafed would impact my running and while I felt tired I still managed to keep a decent pace. I originally thought I’d go 40 minutes but I cut it short to ensure I’d be ready in time for this morning’s activity, an Arbor Day festival at a local preserve. I was pleased with today’s run. I’ve programed the Garmin to automatically roll through the various metrics as I run such as pace, distance, time and heart rate. I used the heart rate numbers rather than speed to guide me in terms of effort to expend. It paid off with a decent pace, close to what I achieved recently in a 5K race.

Tomorrow I have plans to meet my friend KWL at a local park for a run at 6:30 AM. The weather is supposed to be pretty bad so chances are we’ll need to postpone. That would be too bad but I can’t complain about all the great running weather (and great runs) I’ve enjoyed this week.

Central Park: once around for good measure

Central Park Reservoir (1.58 miles around)

Yesterday’s run (Central Park): 4.8 miles at 9:18/mile

Today’s run (street): 2.16 miles at 9:37/mile

Yesterday  afternoon I ran in Central Park for the second time in less than a week. I met my friend CK at the statue of the Maine in Columbus Circle and we set off with a vague plan to cover the distance to the reservoir and back. CK is still dealing with a foot injury that has forced him to scale back on his running in favor of other sports and activities. Like the last time we ran, he said he’d need to take it easy due to the foot injury. This time I knew not to believe him. CK laughed at me as I prepared the Garmin for the start. He’s more old school, relying on time from his stopwatch rather than using an over-engineered running watch that captured distance, pace, etc. However, I noticed that he asked me more than once how far we’d gone during the run.

The sun was high in the sky but the heat was moderate. By the midway point I did find myself gravitating to the side of the road that had the most shade. By the time we reached the reservoir I began to feel the effort. CK managed to subtly push the pace past my default comfort zone. I wasn’t exactly hurting but I felt like I was running at race pace although the Garmin’s display did not reflect that. By the time we’d circled the reservoir and headed toward the east side of the upper loop I was ready to slow down. We ended our 4.8 mile run near the outlet to Central Park South and then grabbed some water to cool down. Once again I had a great Central Park run and CK pushed me hard, as always.

I tossed and turned last night and I believe that related to being so wired from the midday run. My plan for this morning was to cover two miles at an easy pace to balance the hard work from yesterday. I was suspicious that my recent recalibration of the Garmin led to under-counting my distance so I used this morning’s run as a benchmark, comparing the Garmin numbers to Gmaps. Both came out exactly the same: 2.16 miles. I was hoping the Garmin was off which would explain why I felt I worked so hard yesterday and only managed a 9:18 pace. I guess I need to work a little more on speed. The hills didn’t help but I can’t blame them. What goes up one also comes down and it probably evened out in the end..

Time to calibrate the FR60

Today’s workout (street): 4.17 miles at 8:57/mile

Yesterday’s run felt so effortless that I wasn’t ready to stop when we reached the end. Business took priority over pleasure but I did feel great for the remainder of the work day. The run itself was work and I felt the effect of all those hills this morning when I woke up. Still, I was anxious to get out for another run. My wife and kids were volunteering at my son’s elementary school all morning. I had nothing on the calendar until after lunch so I headed out for my run around 9:00 AM with temperatures in the the high 30’s under overcast skies. My Garmin was fairly quiet so I knew I was within pace range although a check of the display showed my pace to be a little slower than it seemed. I stepped it up after the first mile and would periodically surge for 30 seconds to a minute before falling back to my default pace. I was running faster than yesterday’s city excursion and I felt the difference. All the same I didn’t feel that I was working that hard and the data from my heart rate monitor confirmed it. I felt like I had covered a lot of ground but I ended up only going a little more than four miles. It was just far enough to count as a good workout.

When I finished the run I checked my Garmin and saw it displayed 4.07 miles, averaging 9:10. 9:10 isn’t a bad pace and I figured that yesterday’s run had wore me out more than I’d thought. I then mapped the exact route using Gmaps and saw that the Garmin under-counted the distance by 2.3%. Adjusting my pace for that variance, my overall average was under 9:00 (8:57) and my splits were 8:54, 8:57, 9:03 and 8:59. Love the FR60! I’m going to try to calibrate it a little closer so I don’t have to do so much math. I haven’t messed with the calibration adjustment on the FR60 yet. The default accuracy is +/- 3%. It wasn’t all that easy to adjust the 50 so I’m hoping the 60’s controls are better. My problem with calibration is that I switch my foot pod often between my pairs of street and trail running shoes and every change affects the calibration accuracy. Overall, I’m happy with my recent runs and glad that I’ve made my way down to the low 9:00’s that I was running prior to my pneumonia disruption. I don’t know what I’ll run tomorrow. The skies are looking ominous but I’m hoping that this passes and that the trails are in good shape by Sunday.

Your mileage may vary

Today’s workout: Rest day

Despite my meticulous efforts to capture my running metrics, I’m realizing that my perception of my overall performance differs from the hard facts. When people ask me about it I usually say I run 9:00 miles. I can run faster than that, but I don’t. In truth, I only hit 8:00-something paces a few times a month and most of the time I average between 9:10-9:30/mile. Yesterday, after uploading my latest run into Garmin Connect, I noticed that my average monthly distance is 65 miles. This confused me because, when asked, I usually say I run 20 miles a week. I think part of that delusion comes from when I used MapMyRun to record my metrics and included the distance measurement from my elliptical sessions. In fact, I ran less monthly distance a year ago than today because I was limiting my morning weekday runs to no more than 20 minutes.

In order to really reach the 20 mile per week level I will need to average closer to 3 miles per day during the week (less one rest day and one cross training day) and 10 miles over the weekend. The gating factor is time, not conditioning. However, if I really could average 9:00 per mile I would definitely compile more distance in the same amount of time.