Gonna Fly Now

Seeing as how I haven't run since 1972 I thought I did pretty well on my first attempt to get back into some semblance of running shape. I think that bike commuting has kept me fairly fit, but my endurance leaves something to be desired -- although somehow my third mile was my fastest mile this morning, it must have been mostly downhill.

Splits:

• Mile 1:   8:00
• Mile 2:   7:34
• Mile 3:   7:04 
• Total:   22:42

I'll include a link to my GPS output once I figure out this new Garmin Connect thingy.

Aha!

http://connect.garmin.com/activity/10538043

Well, the GPS actually says 2.98 miles, but I'm saying that's close enough to 3.0 to make no difference. We're rounding up, people!

 I surprised myself by actually getting out of bed to go running this morning. I wasn't particulary sore from yesterday's run and bike rides, but my right hip is a bit achey. I think that's more bike-related than running-related, but I was a little concerned when I first hit the street. Half a block into the run I suddenly remembered that I do, in fact, have hamstrings. But, after a good half-mile or so into the run they loosened up and didn't give me any cause for concern. (Note to self: get into a yoga class).

 I ran the Underpass Loop course that I've run many times before, so everything was familiar territory, from the long slightly uphill stretch on Parley's Canyon Blvd, to the grind running up the hill under I-80, to the long flat 1700 East. No surprises, no drama, just a good run.

No splits today because I accidentally left my GPS in bike mode, which doesn't do automatic mile splits. (Which is lame). My total time was 22:25, which matches yesterday's pace.

http://connect.garmin.com/activity/10648697

I meant to go for 3.0 miles, but just missed. I mapped out the route last night, but I turned a little too early, and cut some distance of the total. I left my GPS at the office the previous night, so I didn't have it to chastise me for changing the route.

Total time: 20:30.5

Here's the route:

http://www.gmap-pedometer.com/?r=3072635

The Pipeline kicked my butt this morning. As I was running staggering along in the first mile I was thinking to myself "I used to run ultras, how can I not be able to run the Pipeline?" But, then the trail leveled out, I found my pace, and I ground out another five miles.

Amazingly, I've never been on the section of the Pipeline Trail from Burch Hollow to Elbow Fork, so I didn't know what I was getting myself into. I figured it would be like the rest of the trail, but it turns out the only significant elevation change on the trail takes place on the first mile of that segment. A few years ago I would have just tucked my chin down and charged the switchbacks. This morning, yeah, not so much.

This section of the trail is different from the rest of the Pipeline. The trees are thicker and the trail is narrower. For about a mile I ran through thin single track, with long grasses whipping against my shins. It was spectacular. After turning around at Elbow Fork I had an awe-inspiring view of the clouds swirling around Mt. Raymond as the sun broke through the clouds behind me.

The trail marker says that from Burch Hollow to Elbow Fork is only 2.0 miles, but my GPS tracked it as just over 3 miles. (6 miles R/T). I'm leaning towards the GPS distance being closer to correct because I don't want to believe that me close to an hour to run 4 miles.

Splits:

• Mile 1:  13:06
• Mile 2:  11:04
• Mile 3:    8:37
• Mile 4:    8:15
• Mile 5:    8:33
• Mile 6:    8:30
• Total:    58:38

GPS output:

http://connect.garmin.com/activity/10735785

This morning I decided to run the 1500 East out-n-back. This is the first run I did when I moved to my home in Sugar House, and since then I've decided it's about my least favorite run from my house. It's not particularly difficult -- just a little over a mile of rolling city streets -- but for whatever reason it's hard to get into a good pace on this run.

I'm pleasantly surprised to see that I'm running negative splits lately. Typically I go out to too fast, and consequently run out of steam on the last half of the run. This is particularly a problem for me in races, so seeing these negative splits makes me feel I'm starting to figure out proper pacing.

Splits:

• Mile 1:      7:55
• Mile 2:      7:50
• Mile 3:      7:09
• Mile 3.5:   3:49
• Total:      26:44

GPS Output:

http://connect.garmin.com/activity/10933335

I'm not sure I should be writing about this morning's trail run. To call it fast, or running, would be an exaggeration at best, an outright lie at worst. But, I did it, so I'll write about it.

Since I didn't have to work today I figured I would get in a mid-week trail run, and decided to run one of my old favorites: the Pipeline Trail in City Creek Canyon. (I just found out today that it's called the Pipeline Trial - I always thought it was the Bonneville Shoreline Trail, but it turns out that runs below the mouth of the canyon). I used to run this one with my buddy Chris Pope, but I had completely forgotten how much elevation gain there is on this trail -- almost 1400 feet over the course of four miles. So, repeating last Saturday's performance, I found myself walking almost all of the uphill sections, and made up time on the downhill. I know my "up muscles" will come back with time, but it's frustrating to have to walk hills that I used to run.

Here's the splits:

• Mile 1:    8:40
• Mile 2:  13:15
• Mile 3:    9:46
• Mile 4:    7:40
• Total:    39:23

GPS output:

http://connect.garmin.com/activity/11029979

This morning I ran the Downington Ave Loop course that I first ran last week. I choose that particular course for today because I woke up a bit sore from yesterday's trail staggering, and figured I didn't want to do something with too much uphill (like the I-80 Underpass Loop). I started out fairly slow this morning, but ran a super fast third mile -- 6:39. I'm starting to wonder if my GPS might be a tad inaccurate, because I don't feel like I was running that fast.

Splits:

• Mile 1:   7:57
• Mile 2:   7:20
• Mile 3:   6:39
• Total:   21:57 

GPS Output:

http://connect.garmin.com/activity/11105545