HEAT has arrived

On Sunday I ran in the Backside Trail Marathon.  When I signed up, the forecast was for low to mid-70's for the high on race day.  Of course, Sunday would turn out to be the warmest (hottest) day of the year so far with temps in the low 80's & humidity higher than normal.  A night & day difference from my previous race at McNaughton Park in Illinois earlier this month where the temps were mostly in the 40's and windchills were in the 20's & 30's.

I could have chose pacing at the Indiana Trail 100 which would have been cooler at night, but felt I really needed to work on my speed (especially after the slow miles at Potawatomi).  The course for the Backside Trail Marathon seemed like it would fit that need.   It consists mainly of winding bike trails in 2 interconnected city parks within Louisville.  When I ran this race in 2012, it had several road sections & was a fast course as far as trail races are concerned.  There aren't any big hills in the parks, but there are countless "small" hills (in comparison to the LLTH training course I use).  This race would let me see what kind of speed I had, if any.

I arrived an hour early & my car thermometer already read 60 degrees.  I came prepared with a hydration & S-cap plan with hopes that I could finish the race before it reached 80.  The 2 loop format helped as you don't always have access to a drop bag in a marathon.

I started at the back & though there was a timing mat at the start/finish, I believe the gun time was used (according to my watch).  Starting at the back I knew I would run my pace & not get caught up with someone else's.  With the 1st mile or so in a field or on the road, it would not be difficult to get by anyone.

Felt good at the start & began to slowly pass other runners.  I always feel better to be passing than being passed -- only 2 runners would pass me that I wouldn't pass back this race.  The majority of the runners were in the half marathon (1 loop), so the pace was pretty fast & I didn't pass all that many runners either.

My so-called "speed" seemed to be 10:30 to 11 minutes/mile.  This included jogging up the hills.  I felt comfortable with the pace, though it was much faster than usual for me.  It was exactly what I was looking for from this race.
 
This is how to maximize your trail mileage in a limited area -- there might be 2 miles of trails in this maze:

There were several changes to the course since I ran it a couple years ago.  Some road sections were removed & technical trail was added in parts of the park I had not seen before -- I thought it was a major improvement.  I went down once on the hard packed dirt trail in a rooty section.  The way my elbow is skinned up, you would think I fell on pavement!

I was able to maintain my "speed" for the 1st half or so.  Then I started to get hot.  Though I was taking lots of S-caps, my legs kept trying to cramp.  At times I would break open the capsules to get faster relief.  At about 18 miles, the legs became heavy & my pace dropped off.  I couldn't recover, especially with the heat.  From there on in, I just tried not to walk the flats.  I was covered w/salt at the finish.

Next up:

Looking forward to a new & scenic venue in Tennessee next month at the Thunder Rock 100.  I'm hoping for cool temps, though I'm sure that's not likely to happen with my luck.  Based on what I've heard though, course marking in this remote wilderness area will be my biggest concern at this point to point race.  With a 30 hr time limit & lots of elevation gain, I'll need everything to go my way.

Muddy McNutty - 2014 Spring edition

It's been 3 weeks since Potawatomi 100 in Pekin, Illinois & I'm just now getting this report out!

I went into the race with a mission this year.  My registration for Massanutten 100 earlier this year was rejected as I didn't have a qualifier.  I was surprised with that, but they were correct.  With gut & back issues the past few years, I needed to get back on track.  I've finished many loops at McNaughton Park, so I felt this was the time & course to get that qualifying race.

I figured I had to have these in my favor to complete 100 miles:

Temps - were great:
Nice & cool - mostly 40's.  It was blustery (20 mph winds w/40 mph gusts) for the 1st half day.

Trail conditions -  were manageable:
There was a record rainfall (according to the NWS) of 2"+ the day before.  No rain on race day (that's the key) so the wind was able to provide some drying.  Still muddy in the usual low areas -- hills were ok.  The 2 creek crossings each loop were maybe 18" deep at the most -- heavy, soaked socks & shoes always add to the challenge.

Major physical issues - had none:
I had no back issues -- short downhills are much easier on the back than long downhills.  Kept the brace tight.  I did have a queasy stomach after the 1st lap or so -- pretty sure it was the Heed, which I avoided subsequent loops.  No other gut issues -- special diet & therapy seem to be working.

my staging area:

 
After my mental collapse at Massanutten at 75-80 miles last year, I felt I had gotten over that problem as I've not forgiven myself for that -- however, I had mental issues AGAIN after 80 miles in Pekin.  It was very difficult to continue.  Had I not dropped to the 100 from the 150 at the start of the race, I would have certainly quit again right then.  It was halfway thru the final loop before I "smelled the barn" & knew I could finish.

a 150 mile finisher Sunday afternoon:

My lap times showed a progressive & fairly even loss of leg lift & I'm happy with the results (finished 12th out of 56 starters):

Next up:

I contemplated pacing at the Indiana Trail 100 this weekend, but finally decided on the Backside Trail Marathon -- a race in a Louisville city park.  I guess marathons have become my speed works since I can't get myself to the track.

Beersheba !

 "The toughest trail run in the country" -- that's what it says on the race logo for the Savage Gulf Marathon in Beersheba, TN where I ran last weekend.  Don't think that rings exactly true, though the race is pretty tough for a marathon.

The race is put on by and for the Tennessee Park Rangers (TPRA).  They really bent over backwards to be sure everyone had a safe & fun time.  I love new venues & this was no exception.

From the TPRA race website:

 

This was my 7th different trail marathon, but really the only other race I've run that's comparable to this one, as far as trail type, is Massanutten 100.  ROCKY!  I thought it had more rocky-technical trail per race mile than Massanutten, but it was distinctly different in one way:  the trails at this race were very well manicured -- even with the sometimes constant rock piles & boulder fields!

You could tell the hardcore people who built this trail made a super-human effort to rearrange some of the massive rocks & also bring in some flat rocks & place them amongst all the ones on edge or pointed.  Even so, it wasn't very easy jumping from rock to rock all day -- but it made a big difference.

As for the scenery, I would rate that near the top in comparison to other venues.  Plenty of overlooks, very abundant/beautiful waterfalls & lots of neat rock formations.  The course did not swing by everything the area had to offer -- it would be nice to come back & take the time to visit them.

Checking out the accommodations before heading south, it appeared the closest motel was almost an hour drive from the race.  Dry weather was forecast so I decided to take advantage of the free camping near the start line.  I arrived early so I could take in some sights.  This was at the Stone Door overlook:

I've seen pics where someone is on that thin 15' overhang over a 150' sheer vertical drop (crazy!): 

In the Stone Door (there are 2 people in this photo): 

There's only about a quarter mile of road (paved or gravel) running on the course & that's on the park road & parking lot at the start/finish.  I was still chilled by the cool, windy night in my tent so I wore a shirt to the pre-race instructions at the start.  As we ran past the cars in the parking lot during the start, I dropped off my shirt at my car.  That made me dead last heading onto the trails.

To me it seems the marathon pace is so much faster than a 50k.  I bided my time on the 1st couple miles on the easy, non-technical trails which led to the Stone Door steps & entrance to the rocky gorge below.  I knew I would catch up to the tail end of the group as they would still be backed up at those steep & narrow steps by the time I got there -- and they were.

Photos by Jessica Phillips Photography:

the leaders:

The trails were GREAT.  I always prefer narrow, technical single track over anything else.  No mud or sleet like last week at LBL -- I got the bottom of my shoes wet a few times here.  What I wasn't prepared for this race were all the suspension bridges!  Some of them were pretty long.

One of the crossings:

The 1st bridge was only a few miles into the gorge while everyone was still bunched up.  I was a third of the way across the bridge before I knew it.  It was going up & down quite a bit, but I held on.  Then it started swinging sideways at the same time!  I stopped dead in my tracks.  This was not a place for someone who gets motion sickness easy & has a fear of heights!

2 runners were stuck behind me on the bridge when I froze, so when the sideways motion slowed down, I let them squeeze by me.  Only when they got off & the bridge stopped moving did I get across -- one down, 7 more crossings to go!  I did not (nor did others I suspect) read the sign that said only 2 persons on the bridge at a time.  I got better as the day went on as I also made sure I was the only one crossing on each bridge.

 

One bridge was made up of strung out aluminum pic boards -- that was nice as it restricted the up & down movement.  It reminded me of how ice climbers go across crevasses in glaciers on ladders.  I did stop on a few of the bridges to admire the scenery.  The crossing over the Collins River with the huge boulders was the highlight of the course to me.

Surprisingly my back gave me problems at only one location the entire race:  the "Stagecoach Rd historic trail" about mile 16.  I imagine passengers on a stagecoach on this rough road in the old days got back problems here too!  It was a 1.5 mile section all on a steady downhill.  By the time I reached the bottom, I was ready to crawl.  Luckily there was an aid station right there.  I took time for a little rest & recovery & even more surprisingly, I had no ill effects afterwards!

Despite the marathon PW in terms of the finish time, I thought it was one of my better efforts in the past year.  It also had to be one of my most enjoyable races - highly recommended.

Next up is Potawatomi in Pekin, Illinois in about 2 weeks.  I'm attempting 10 loops of the course -- last year I was injured on the 5th loop.

short again at LBL

I came to LBL needing everything to be just right in order to make the cutoff at 36 miles (13'/mile) to be able to continue to a 50 mile finish.  However, Mother Nature had other thoughts. 

It started with the sleet & snow on Sunday night the week of the race.  I was out shoveling & scraping the ice & snow off the driveway the next day in near zero degree windchill conditions.  I did not catch a full fledged cold, but I did come down with some kind of bug -- sneezing, a constant dripping nose & worst of all was the fatigue.  For several days I thought the race was not a possibility.  However, after lots & lots of bed rest & vitamin C, I felt better by Friday afternoon.  The race was on.

My next hurdle came when I arrived at the race -- the snow had melted at Grand Rivers, but there was sleet & ice everywhere.  Despite 50's the day before & above freezing temps overnight, the trails had a thick layer of sleet on them.  I needed shoes w/aggressive tread -- I had none.

The temp was nice & cool & I started the race with a slow controlled pace.  After the 1st mile, I looked back & out of nearly 700 runners, there were only 75 or 100 behind me.  Starting in this position, I knew there would be backups once we hit the trails & a restrained pace the 1st loop.

Despite the stop'n'go running with the crowd on the 1st loop, I was ahead of the pace that I set last week during my test run on the course.  Near the midway point of the 2nd loop (18 miles), I was at the pace I needed to be to make the cutoff.  I could even run a little less than 14 minute miles & still make it -- I felt I could do it.

But, it was like a switch was thrown & the course instantly deteriorated!  Instead of the semi-solid sleet base, it became sleet, mud & mucho water.  The water could not drain off the trails as the sides had built up with splashed out sleet.  It was hard to believe it could get that deep on a usually well-drained course.

When the trail conditions changed, my chances of making the cutoff went out the window.   I was disappointed, yet I continued enjoying the run with the adverse conditions.

The temps felt like they rose to the 70's (actually only 50's) & the 3rd loop was mostly run in cold water.  Some of the small streams that you could jump over the 1st loop were now 15' wide & you had to be careful of dropoffs when wading thru them.  Where the trails were flat, the water just stood in the trails several inches deep.  On the hills there was always a steady stream running down the middle of the trail.  Splish - splash - what a gas!            

next up:

I have some soreness in the arch of my right foot (where I ran with too much mud in that shoe) -- other than that I feel pretty good.   I did not push & extend myself this race so I've decided to go back down to Tennessee for the Savage Gulf Marathon in what promises to be a most scenic & challenging run. 

pre-run at LBL

After the back to back long runs in TN, I thought I'd go down to LBL & run a lap or two on the course since I'm having concerns about the 50 miler.  I was planning on a good rest, then on Thursday or Friday I'd get the run in. 

BUT, I got a new toy during the week:  a GoPro 3+ Black version camera:

At this years LLTH race, I took my handheld video camera with me on the 1st loop -- it was extremely shaky.  That's when I seriously looked into the GoPro.  I'm still playing with it & trying to figure it out -- one thing it says is that battery power is limited in cold weather.  Since the temps were in the teens/low twenties, I decided to wait & head to LBL on a warmer Saturday.   A bit close to the 50 miler next weekend, but I knew to take it easy.

It turns out the Western Kentucky Running Club (WKRC), the people who put on LBL, lets their race day volunteers make an official run the weekend before the actual race.  I thought it an ideal time to join them so I could try out my new toy AND get in a confidence builder over the course.

I believe most of the volunteers were running 1 loop (23k).  I would do 1 loop & if I felt like it, I would continue on with 2 loops (marathon).  For the race this weekend, if my back doesn't give me problems, I don't think I would have trouble with finishing 50 miles.  The problem is the cutoff at 36 miles, which is at 2:15 pm (a 13' pace).  Pacing is critical -- I'm so worried that I won't make that cutoff that I usually start too fast.

Course was in great condition -- it was cool & breezy along the lake.

Well I started the run too fast on the road (I do this about every year) -- got caught up talking about the GoPro & whatnot.  Even so, I fell increasingly further & further behind the main group of WKRC runners.

 I concentrated on my pace -- I wanted to see how long I could maintain the 13'/mile average.  After the quick start I slowed down & by the end of the loop my average was down to the 13'/mile.  Since I felt OK I continued with the 2nd loop.  I averaged around 14'/mile on the 2nd loop -- I think I could have averaged 13'/mile, but I didn't want to push it this close to the race.  I don't know if I could have made it to 36 miles at that pace, but at least I know now I do have a chance -- it was good run.

Got a problem with the GoPro.  I'm getting a thumping noise when I'm running but it goes away when I turn my head to the side.  I believe it has to do with the strapping, but haven't figured it out yet.  A bit disappointed the rechargeable battery only lasted about 110'.  I have some more batteries on order.  Here's a 19 sec clip:


 https://drive.google.com/file/d/0Byd8JwCSMpVCRDJ1c0RBZVdfUzQ/edit?usp=sharing

Thunder Rock pre-run

Despite my back problems & level of fitness, I'm signed up for several long races this year.  The first one, Potawatomi 150 next month (signed up early last yr) appears physically out of reach at this time so I'm looking at dropping down the distance.

The 2nd one, Thunder Rock 100 in 2 months is a brand new & very scenic race in Tennessee & I jumped on it at registration opening (filled in 48 hrs) as there aren't very many races like this that are within driving distance of Louisville.  Last weekend the Race Director, Randy Whorton, had a pre-run on the first 40+/- miles of the course over a 2 day period.  I had never done back to back long runs before as I've always been too tired after the 1st day.  But I really wanted to see what I had gotten into plus I could quit after the 1st day if needed.

There would be a couple other challenges, other than having back to back long runs:  1. the course was basically unmarked & you had to follow an EVERYTRAIL map that the RD had posted.  I did not have the recommended EVERYTRAIL app to use while on the trail, but I did try to memorize what I could by following a GPS track on Google Earth.   It appeared most trails would have trail blazes, however the old forest roads looked troublesome.  2. With several thousand feet of elevation, it would be tough.

Day 1:

I knew it was going to be a long day in the 1st mile of the run.  About a dozen or so of us runners began on a wide gravelly trail on a slight downhill grade.  Trying to keep up with the group I still fell behind -- problem was they were running an 8:30 pace.  I was expecting a more leisurely pace.  Just before entering single track at 2 miles, I could see over a 1/4 mile ahead & they weren't in sight!

I ran alone, did alot of walking & did some wandering.  The 1st trails had old blazes on the trees, but they were few & far between.  Some intersections were a big guess & I ended up having to run down several trails/roads to try to determine which way to go.  One place in particular was bad & if it hadn't been for someone placing sticks in the road for a makeshift directional arrow pointing off the road, I would have never found my way!  It turns out one runner didn't see those sticks, got lost & had to be tracked down. 

Day 2:

The RD had a different plan the 2nd day since there were several others who had trouble the 1st day.  This day would have more turns & some totally unmarked trails so he would be running sweep.

Surprisingly, I felt OK the 2nd morning as I slept long & well (pretty tired!).  My back (w/brace) would not be an issue either day.  The biggest challenge I could foresee this day was not getting lost!

 bringing up the rear again:                                                     

The 1st day was scenic, but this day took the cake.  If you like running with the view & sound of water rushing by for miles, this is the race for you.  Lots of whitewater rapids too.  One view from about 250 feet straight above a creek was one of those WOW moments.  The trail was so narrow here too & since I have a fear of heights, I had to lean up against the hill on the other side thru this section.

This is a video of the runs:  https://www.youtube.com/watch?v=3o5VVIowQ0k

Again I was running behind the group this day (with the RD running sweep a few minutes behind me this time taking pics & video) but a couple times I would catch the group when they didn't know which way to go & had stopped to wait for the RD.  At one intersection I stopped & waited for the RD because I heard the group ahead up on a hillside where they shouldn't have been.  Turns out they did go the wrong way -- the RD ran after them.  I didn't go so I inherited the lead . . . until I got off course!

One of the new directions (RD changed them from the posted course) I heard just before we started was:  after about a couple miles after the right turn at the 1st intersection on the gravel road, turn left at the orange gate.  Well, I did that.  Turns out there was ANOTHER orange gate (the correct one) just a little further down!   No trail blazes this end of the course, so I was on my own.  After a half mile & down a 300' hill, the forest road became increasingly overgrown & difficult to traverse.  I had also passed a "50/50 guess" intersection down the hill -- should I have turned?  Well, I decided to turn around & go all the way back to the orange gate. 

Luckily, the RD (who had ran down the off course group earlier) was passing by on the gravel road!  So I was able to run to the finish with the RD.  When I got home & checked my GPS with the final miles WITH the RD, we did NOT run on the course we were directed to!  Wo!

Oh yes, I get motion sickness easily & on the very hilly/curvy van trips to the start & finish on these point to point runs, I got sick!  We even had to stop once for me to recover . . .

a memorable day

Last weekend I finished my 9th Louisville's Lovin' The Hills 50k (LLTH).  It has to have been the most fun time I've had on the same trails that are my regular training grounds.  The ice covered trees & snowy hills were AWESOME!   Some races may advertise of their most scenic courses, but this was the best one I've ever run.
 
All photos on the blog today courtesy of Terry Fletcher w/SPORTZbizz:

Race blog recap here.  More pics here & here.

I also love narrow single track -- most of the course on the Siltstone Trail (about 13 miles) was only as wide as my shoe turned sideways -- I checked!  Runners avoided the unpacked snow & kept true to the skinny path or risked discovering the hidden edge/dropoff of the already narrow trail below.

Ryan & Russ w/ice beards:

 

It was my slowest time for LLTH, but I knew that would occur going in.  Marking & then re-marking (because of the ice storm) on the snowy, obstacle-ridden course completely wore me out.  Also, I just can't hike up & down these hills during the week of any race & expect a good time.  But time was not a concern this day-- I was out to have a memorable run -- and I succeeded!



I took a hand held video camera with me on the 1st 6m loop.  This camera was NOT meant to be used while on the run like a GoPro.   Also, looking at the short & shaky results after the race, it was obvious I didn't always know when the camera was on or off!  In very small letters on the screen it signals red for pause/stop, green for on -- not easy to see when running.  Anyway, here is a short shaky segment -- trying to keep from tripping while avoiding icy branches & trees from knocking the camera from my hands:  video  The video is in High Definition (HD) although the default on Google Drive is 480p.

Next race is LBL 50M in 3 weeks.  Such a contrast between LLTH & LBL!  I'll need to avg 13 min/mile for the 1st 36 miles in order to be able to continue with the 4th lap.  Based on my recent efforts, that pace will be an extraordinary task!  My back seemed to tolerate the much slower pace better at LLTH last weekend too.

Last year I had one of my worst efforts ever at LBL & I still don't know exactly what happened.  Maybe I need to put in a speed work or two before then?  Will see . . . .

still running

Last weekend I travelled down to Huntsville, AL for my 4th Mountain Mist 50k.  Last year I set a satisfying PB for the course, but based on my recent races, I knew I wasn't going to be anywhere close to that -- if I finished at all.

The RD altered the course this year to try to minimize the congestion that always occurs very early in the race when 300 - 400 runners are funneled down the 1st big hill that's on single track.  The 1st 2 years I ran this I used a quick early pace to avoid the heaviest traffic but ended up running a forced pace afterwards just to keep from getting run over!  This year the course was re-routed so that a couple miles of fairly flat road/trail were shifted to just after the start to help spread out the field.

Well, the field had indeed spread out after 3 miles, but a new problem arose.  As soon as everyone headed down the 1st hill of years past, everyone came to a standstill.  Why?  Because Alabama has had its' share of cold weather --  one of the streams crossing the trail had turned into ice.  It took almost 4 minutes to go inch by inch just to get to the ice.  Had I known I would be standing around that long, I would've ran the 1st 3 miles alot slower (the line behind me was not near as long as the one in front).  One fellow couldn't wait & took a butt slide down the steep hillside to bypass everyone.

The course was the driest I've seen it, so other than the ice crossings, the course was fast.  Surprisingly though, this year the winning time was 27 minutes slower than last year when a record was set in the mud.  Besides the course alteration at the start, there was one other change at mile 24 -- the course felt longer but my Garmin said it was about the same. This years' winner, Scott Breeden, had won Louisville's Lovin' the Hills 50k in record fashion in 2013 after finishing 2nd at Mountain Mist a few weeks earlier.

2014:                                                     2013:

 

The 1st half of the course is the fastest & least technical.  I always use the 17 mile aid station as the halfway point of this race timewise.  Last year I averaged 12 min/mile to this point.  This year it was 13 min/mile -- it was slower, but felt good & was really enjoying myself.  I had used the same race prep (diet & belt tightening) as before at Tecumseh & up to that point it was working great.  However, the long rocky technical downhills at miles 19 & 27 were tough.  The large step downs on the boulders about did me in.  Most runners jump down them, but for me it was an awkward ballet with the stiff back brace.

After the last tortuous downhill, it was a struggle to continue.  I was hurting and had no energy.  There was Powerade at all the aid stations but it was watered down quite a bit -- I missed my sweet Gatorade.  I ate some pb&j quarters & potato chips - my favorites, but apparently I did not eat near enough.  After I dragged myself across the finish line, I headed straight for the hot pizza.  They have pizza delivered regularly & it's kept in ovens til needed -- it's great!  What Christmas turkey I was able to burn off during the race, I gained back & more with pizza (I think I ate a whole pizza!).  I believe I've found the limit to the special pre-race diet I'm using & need to make some adjustments (eat more) for longer races.

Next up on Saturday is Louisville's Lovin' the Hills 50k.  This race is about as local as it gets -- I can see the course from my front porch.  Earlier today I flagged the 1st leg for the race, about 6 miles.  I had planned on more but wasn't expecting the 5" of snow last night.  Felt like I needed snowshoes in the deeper areas.  Looking ahead at the forecast for the rest of the week, it doesn't look like the snow will be going away anytime soon.  If anything, any melting will freeze over & the course will be solid ice!  Looking forward to the challenge.

a couple changes

Hats off to Brian & all the others who made the 2013 Tecumseh Marathon happen in 2014!

After quickly encountering disabling back pain at the Otter Creek Marathon, I did a couple things differently for the re-scheduled Tecumseh Marathon:

First thing was to tighten up the back brace as tight as I could make it -- I was stiff as a board!  Since I've learned from experience that this causes digestive issues & unexpected pit stops, I made sure I had NO food in my system other than a couple gels & gatorade at the start (no breakfast either).  This was no simple task as it required a special diet 2 days before the race . . . . eating food that I knew would pass thru my digestive system for sure before the start of the race.  This makes it tough the day before the race with only liquids that have no solids.  I don't know if I would have enough energy reserves if I tried this for an ultra.

Second thing was to use a measured pace (much slower than at Otter Creek) the first couple miles.  It was tempting to open it up as the 1st mile was on gravel road & mostly downhill.   I settled in towards the back, but when we approached a wide flooded stream crossing the road, there was a major backup.  I think there were some rocks you could use to jump across, but with what seemed like 30 or 40 people standing around, I wasn't going to wait.  The water was about thigh deep & I passed a bunch of faster paced runners I had not planned on passing.  Best part of this move though was when I reached the "squeeze down" to single track right afterwards, there wasn't any backup.  It was single file running the next mile and luckily it was not at a forced pace.

Because of these changes, I believe I was able to finish this marathon (this time).

new course:

This year the RD used an alternate course using an out'n'back section around the lake with 3 laps of a 6 mile loop.  Although more than half of it was on frozen gravel roads, I thought this a much better design than the previous alternate course that was an out'n'back starting at the finish line.  With that pure out'n'back, you had to pass everyone running in the other direction at some point in the race.  When that was done in 2010 in the snow, it made it difficult to get by everyone on the single track. 

The reason for the move off the Tecumseh Trail was because of all the snow, ice & mud.  Less than half of the alternate course was on actual trail.  The trails took a real beating with the repeated loops in the mud.  Some of the trail was on the old course but was so wallowed out I could hardly recognize it.  Most of the mud was the "splashy" type and small parts of the trail were under water (much like at the Otter Creek Marathon that was in the rain).  There was only one hill that was encountered on each lap.  Had it been a hilly course with that mud, it would have been tough. 

I ran into alot fewer people that I knew this year since the field was practically cut in half.  I can remember:  Bob S., Terry F., Mike F., Russ G., Brian H. and Cassie R.  I recognized several others, but didn't get a word in with them.  At one point in the race I told Bob S. (who I seem to meet at every Indiana race either running or volunteering) that this was my LAST race!  My back was giving me fits at the time as I had just run down the one hill on the loop (downhills are the worst on my back).  I even told him my thanks & good-byes . . . this after 10 years since our first encounter at OPSF!

Well, I've got a short memory and 2 days later, with my back having recovered somewhat, I went & signed up for a bunch of races!!!  Duh. With entry limits nowadays, a decision has to made early.   All I can say is I'll take them one at a time -- if I don't make it to the race(s), I'll know I donated my entry fee to a good cause. 

This year I was going to make a big donation to the Jefferson Memorial Forest as I have done in the past, but since they keep closing miles & miles of scenic single track trail for no good reason, I've decided against it.  It was an easy decision for me.

couch potato

I've been spending alot of time off my feet lately & feeding my face seemingly nonstop (gained 10 pounds in 2 weeks) -- haven't gotten out of the holiday habit yet.  I've justified it by saying to myself:  I'm resting my back.  It's been almost 3 weeks since the Otter Creek Marathon.  It would've been my only marathon finish of 2013, but I ended up with my first ever marathon DNF -- my back shut me down, even with the brace.   Not sure what brought the pain on so fast other than my pace was a little quicker at the start than at the ultras I'd been running (I'm not going to do that again).  It didn't help that I fell awkwardly on my left hip early in the race.  I'm also beginning to think that the posture therapy I go thru for my gut problem is messing with the back -- if it's not one thing, it's another!

Got word today from the Massanutten lottery people that I did not meet the qualifications for the race in May this year.  After my mental shutdown there last year, in what would've been my best ever finish, I was hoping to redeem myself this year.  The way my back is now, I guess it's best that I didn't get to sign up.  Things are going to have to get much better just to get in a qualifying race for 2015.

Still going to try the re-scheduled Tecumseh Marathon Saturday after this holiday rest break.  It's been ages ago the last time my goal was to just finish a marathon.  I'm hoping to have more fun than pain this time . . .

4 races - too ambitious

Needless to say, I've been quite negligent on the blog scene these past couple months or so.  Guess I'm just getting "lazier", but it's also my "fatigued" feeling (mentally & physically) lately.  Of course I have no one to blame for this except myself . . .

At Massanutten in late Spring, I felt better physically than I ever had the previous 2 years when I was plagued with unpredictable abdominal pain.  After Massanutten, & with my new posture therapy, it was great to know I could run so far without the fear of that pain!  With that in mind, I made ambitious plans for the rest of the year . . .

However, I acquired a new pain in my back to replace those abdominal problems!  I thought it was temporary, but it's only gotten worse.  My running has been on a downward spiral since.  My back doesn't present a problem when I'm doing chores around the house -- only running & heavy lifting (which I avoid).  Unless I wear my brace (girdle) when running, my backbone can slip out of place.  When that happens, running & sometimes just walking are out of the question.  The brace is quite restrictive & also helps me endure back pain (it doesn't stop the pain).  I also learned that the brace itself can cause abdominal issues!  Wearing the brace too tight causes "unscheduled pitstops".  Wearing the brace too loose just makes it useless.


Results of that ambitious plan I made up back in May:

Jun 1    Music City Ultra 50k  -- in prep for Mohican, finished in the heat in 8:08
Jun 15  Mohican 100m -- DNF w/major back problems at mile 73, took month off from running
Sep 6    Hallucination 100m - DNF - back problems from the very start

all w/back brace:
Sep 28  Not Yo Momma's 100k - used brace for the 1st time, finished in 21:38 (18:35 in 2012)
Oct 12   Cumberland Trail 50k - finished in 7:34 (7:05 in 2012)
Oct 19  Big Backyard Ultra - new venue, novelty race, completed 29 miles in 7 laps(hours)
Oct 27  Stone Steps 50k - finished in 6:59
Nov 9   Georgia Sky to Summit 50k - new venue, finished in 8:18
Nov 23 Duncan Ridge 50k - finished in 9:26 (8:35 in 2012)
Dec 7   Tecumseh Marathon
Dec 21 Otter Creek Marathon

I'm too lazy to post a full race report for the past 4 races, so I'll just post somewhat shortened versions of each:

Big Backyard Ultra:

GREAT company -- got to meet & share stories with some top runners from across the country!

I learned that unlike the past, I need at least 2 weeks to recover from an ultra.  I had squeezed this in between 2 other ultras that were 2 weeks apart as I was curious about this race -- I won't do that again.

Had a worse night of sleep than usual:  Early in the night, BIG (Laz' dog) was barking incessantly (every 2 to 3 seconds) for hours (unbelievable) -- I wasn't the only one that dealt with that; the wind shifted about 4 a.m. and the smoke from the smoldering race campfire went directly (in)to my tent (what luck)!  The wind finally shifted again 30 minutes later, but it was too late then.

A quote about the course:  "while not easy, is not particularly difficult" -- I agree.  Completing the 4.167 mile lap in 1 hour is not that difficult.  There were many strategies abound.  Mine was to complete each lap in 58 to 59 minutes & have just enough time to go to my drop bag for drink & nourishment with maybe 15-30 seconds of sit (rest) time.  This worked well for 1 lap!  Apparently due to my girdle/back brace too tight, I had to sprint to the port-o-let at the end of the 2nd lap (no defecating allowed in Laz' backyard course) & barely made it back in time for the start of the 3rd lap (disqualified if you're not at the start).  I was out of breath, didn't get any rest & never really recovered from that.  It seemed the strategy for most was to finish each lap in 50 to 55 minutes (mostly because it was so easy for them to do so) & have 5 to 10 minutes rest.


Stone Steps 50k :

I scheduled this race as my Brother was visiting from Virginia during this time & it would be a good opportunity to introduce him to my sport!  We had a GREAT time together.

Fall colors were not prominent as in some previous years, but Mt Airy Forest in Cincinnati is still a nice place to run.

I completely forgot my salt pills this race.  I had my salt pill holder in my pocket but forgot to reload it after my last race.  I even forgot to take any salt during the race!  I can hardly believe I made it all the way to mile 24 before my right leg started to cramp.  A few minutes later & about 100 yards before the aid station, my leg completely locked up (very painful!).  Each time the muscles released themselves, I took a step & the leg would lock up again!  Several runners passed me & no one had any salt . . . so I resorted to licking my arm!  It was as salty as opening up a S-CAP & pouring in on my tongue.  This worked & I was soon able to walk & load up on pretzels at the aid station.

Georgia Sky to Summit 50k :

I wanted to do this race on the GA/NC border as I love new venues & the website promised "the 50k course is the most scenic on the east coast".  I doubt it was THE most scenic, but I wasn't disappointed.  Although I didn't see all the scenic views & waterfalls advertised, I was most impressed by Holcomb Falls:

It was hazy the 1st summit of the mountain.  The 2nd time up it had cleared up & the view was great!

The RD said if you like "inclines" you'll like this race.  My idea of an incline is a "tweener" -- a hill where you can't decide 'tween running it or hiking it.  This course seemed full of these -- even on the 2000' climbs up the mountain. 

Had a hard time at the start.  It was like I had a "burnt out" feeling, like I'd overdone it the past month or so -- too many races -- this was not good.  Within a half mile, I looked & there were only 10 people behind me.  The next couple miles was mostly a hike up the mountain, so I settled in -- repeating to myself I was here to enjoy myself!  I started talking with some of the other runners -- I felt better mentally after that, but physically, I felt I needed an "unscheduled pitstop".

After relieving myself, I also loosened my girdle a tad & felt 100% better.   I passed at least a dozen runners in the next few miles.  The only people I had passed previously were ones who had fallen or were injured.  Leaves were unusually deep in places & hid all the hazards - I lost 2 toenails.  Other than a quarter mile section on the 2nd descent that was very steep & technical, the hills weren't as steep or as technical as other races I've run in the Appalachians.  Still, over 7000' of elevation gain.

Late in the race you had to run on some freshly re-graded gravel roads.  Some had just had new rock put on them.  This was the least favorite part of the race for me.  My feet had been wet since the water crossings early in the race and were very tender by the time I reached the gravel.  It was like I was walking barefooted.  It was here I aggravated the previous injury to the joint in my left foot where I had jammed the toe back into my foot.  It hurt enough that I could only walk these runable sections & even then I had to carefully guide each step into the smoothest area.

Duncan Ridge 50k :

This was one of my better races last year & thought I would return as I also had alot of fun.  There were some nice scenic views all along the course, but this year almost all of the race was in the clouds (fog).  Total elevation gain (10,000') is the most for any 50k race I run all year.

With the way I felt about burnout at my last race, I had 2nd thoughts about running this race that I had signed up for several months ago.  Plus, it was also going to be a 6 hour drive in the rain & the forecast was rain for the race.  Well, I decided to go anyway & take a slow & cautious 7 hours for the drive.  I was also slow in the race (not by choice) & tried to enjoy it the best I could.  It was drizzly, foggy & cool (low 30's) at the start.

My Garmin 310 started on all zeroes but when I checked it in the 1st mile, I was getting all sorts of mixed up numbers (moisture problem?).  However, I didn't need my watch to tell me that I was starting very slow, just like at my last race.  About a quarter mile of the course was changed from last year (faster) as we ran in the park a little longer -- this helped the backup that occurred last year.

I restarted my Garmin at the 1st aid station & it surprisingly picked up GPS fairly quick at the base of a mountain & worked fine the rest of the day.  Based on the time of day, I was running 1 to 2 minutes slower per mile than last year to this point.  Within a few miles of the 16 mile turnaround on this out'n'back course, it looked to be a possibility I wouldn't make the cutoff of 4:45.  The only time (so far) that I worry about cutoffs is when I get lost or in 100 mile races.  With 10 hours the official time limit, this cutoff was reasonable & I could live with that.  I wasn't worried if I didn't make it -- I was feeling pretty rough then.  Well, I made it out of the aid station in 4:35 and on the way back I had a couple "unscheduled pit stops".  Once again, I felt much, much better afterwards.  I finished 50 minutes slower than last year even though I did run the last 10 miles faster than my 1st 10 miles this year.


Next up:  Tecumseh Marathon

I've been resting since my races in Georgia, but feel unprepared for the Tecumseh challenge this year.  I've run only ultras all year & with it being a marathon, the pace is naturally faster . . . yet my recent running indicates I'm heading in the other direction!  Going to experiment more with my pre-race diet (just Gatorade now?).  Weather will be a factor for me this race (being able to drive to the race in icy conditions).  My anti-lock brakes were the only thing which kept me from the ditch the last time there were bad driving conditions at the event -- hope the forecast changes . . .

Cumberland Trail

First of all, if you're an ultra runner, this may be good for a laugh or two (found this link on the Ultralist):  http://whatisultra.tumblr.com/   I like "YOUR FIRST 100 MILER".

Went down to Caryville, TN, last Saturday for the Cumberland Trail 50k.  I really loved the trail & scenery last year & I also had one of my better races.  I would have to deal with 2 handicaps this year though:   the back brace for my still aching back; and the 5 to 10 degree warmer (hotter) temps.

At 55 degrees at the start, I didn't think I would have a problem, but with the early 2000 foot climb with my "deluxe heater belt" in place and warm headlamp (1st hour in the dark), I was sweating like crazy!  It felt like the afternoon high of 81 had already arrived (only 71 last year).  Like Not Yo Momma's race last time out, I was caked with salt at the finish.

The trees weren't nearly as colorful as last year, but still a beautiful area to run in.  The leaves were just starting to turn & most leaves were still on the trees -- the trail had some leaves on it, but generally it was fairly clear.  With fewer leaves, it seemed as though the trail was much more technical this time, but less dangerous as you could see most all the hazards.  Anyway, I just couldn't run the same pace as I did last year (finished almost exactly 30 minutes slower).  Also going down technical, steep grades was very tough on my back -- on a one mile section down the mountain it took 20:25 to gingerly climb down.

Next up on my ambitious Fall schedule is the Big Backyard Ultra in Bell Buckle, TN, next Saturday. This is the infamous "last runner standing" race -- a guaranteed DNF for everyone but the winner.  This is from the UR magazine:

"BACK" again

A couple races since my last report:

Hallucination 100 (Sept 6) at Woodstock - another DNF:

After recovering from the disabling back pain at Mohican, my summer training went very well.  It was a cooler than normal Summer, with a very cool 1st half of August.   I had several good runs over 25 miles (no back pain).  I felt like in the best shape ever this time of year since I normally run very little during the summer.  No signs of back pain . . . until 2 days before the race!!  Actually it was just tightness & it's the feeling I get when my back is about to go out.  I have no idea what I did to bring it on . . . .

In the very 1st mile, I realized that I was not going to finish the race.  Pretty depressing since I thought there was a possibility I could PR the distance based on my training runs.  The course is the flattest that I run on all year & if one wanted to run their best time, this was the course to do it on. 

The back pain progressed slowly until eventually my back gave out altogether a few miles from the end of the 2nd lap (of 6 laps).  From there I walked it (staggered) in.

Best part of the event was seeing all the local runners who also made the trip.  Cynthia Heady, RD for Louisville's Lovin' The Hills (LLTH) was leading the women's race until having stomach issues.

getting ready for Not Yo Momma's:

Last year this race was the only long race that I didn't have any gut issues.  I realize now what I did -- it was a cool night camping & I remember curling up on my LEFT side on a slight hill.  If I had only realized it then that this would prevent the pain, it would have saved me a lot of trouble.

So this year, with my gut issues under control (knock on wood) and no back pain after Mohican, I signed up for this race & many others this summer for a very ambitious fall/winter schedule.  The last time I set up such a schedule, I caught the swine flu & that destroyed me for several months.  This time, my fickle back has thrown a wrench into my plans.

With back pain my no. 1 concern this year, I made several changes since the DNF at the Hallucination 100:  Increased my fish oil supplements; started back on glucosamine chondroitin; and started training with a back brace.  I was going to start a series of pilates sessions, but after the 1st class, I realized I did not have the coordination & dedication to keep at for the time I needed to.  What would probably help the most is to lose 20 pounds -- but that's much easier said than done.  I even seriously thought about seeing a chiropractor, though I'm still a little fearful of that yet.

During that good spell over the Summer, I signed up for the 100 mile version of the races at Not Yo Momma's .  Since my back was acting up the night before the race, I switched to the 100k on race morning.  First time I've ever worn a back brace in a race & for an extended period.  Advantages of the brace:

Sucks in my gut like a girdle -- keeps it from overhanging & there's less strain to keep upright.
Holds in heat at the back & fits firmly (does not move causing raw areas).
So far has kept my back from going out (does not stop all the pain though).

Disadvantages:
Bulky & weighs in at 2 pounds -- more when wet w/sweat. The weight is very noticeable.
Makes it feel like it's 10-15 degrees warmer during the race than it actually is.  Most definitely makes me sweat even more.
Had to modify it by adding bubble wrap to provide more lumbar support -- haven't found a solution to keep it exactly where it needs to be & it slips alot.
May interfere with digestion.


Not Yo Momma's 100 (9-28) - close to DNF:

The race went very well for the 1st 3 laps (16 miles each) - the back brace did its job.  It got hot & I sweat so much the brace almost turned all white w/salt!  However, I made a critical error.  For some reason, I completely forgot to take my Ensure -- I think when I changed from the 100m to 100k at the last second, I just didn't use any nutrition plan as I hadn't planned on running the 100k.  Anyway, I get sick of just gels after 50 miles & that's just what happened.  I don't know if the brace restricting my gut had anything to do with it, but at 52 miles, I got very sick.  I sat down for 2 hours & took off the brace -- with the 32 hour time limit, I had time to spare.   Finally, after heaving up everything (I think I emptied my small intestine), I was able to limp in the last 12 miles.

At 50 miles, I was on pace to finish in less than 18 hours (last year was 18:45), but I'm happy just to have finished.  This course is an exact opposite of the Hallucination 100 with its' profile.  I believe this course is as difficult as, or more difficult than Massanutten & that's saying alot.  Not rocky technical, but the very steep hills are relentless & incomparable to any others I've encountered.  There are only a few technical areas on the well groomed trail -- however I did manage to bust the nail on my big toe and that's just another added pain to deal with now.

Next up:

My ambitious schedule continues.  I have 3 races in the next 16 days!  Starts with the Cumberland Trail 50k tomorrow morning . . .

caught up

Last report of 3.


Mohican - 3rd attempt

2013 had been an odd year weather-wise and I have no complaints about this summer.  Even with a cooler than normal August last year, there have been 30+ fewer days this year where the temps have reached 90 here in Louisville.  It's been (so far) the coolest summer in recent memory.

So, back in June, I had several major factors in my favor entering Mohican:  normal temps (rare) on race day, a gut somewhat under control, injury free, mentally re-focused (from Massanutten) and some rare training days in June when it's usually too hot to even think about it.  I felt really good about my chances.

However, stupid me couldn't sit still taper week & decided to do some Spring cleaning & moved some heavy boxes around.  I didn't even realize what I was doing till my back went out -- just what I didn't need before a race where I DNF'd twice because of severe back pain!  Dumb! Dumb! Dumb!  So that's my race & report in a nutshell -- DNF with back problems -- again.



 
A couple notes about the recorded time above:

At the 50 mile mark, I was feeling good with a time of 12:43 and had over 19 hours to finish the 2nd half.  But my back started shutting me down around the 100k mark & by the time I got to the aid station at mile 73, even baby steps were painful & I called it quits.  Since they were the last aid station before the end of the loop, I believe the aid station captain was reluctant to take anyone back (this was about 1:30 a.m.) -- so I had to join the other disabled runner who was lying on the ground on a blanket.

About an hour later, another runner in really bad shape came into the aid station.  Since I tried & was able to stand without pain, I told them I would give that runner my blanket spot & try to walk it in (it turned out to be a slow & painful trek w/many breaks & wished I hadn't tried it!).  I had shut off my timer when I stopped at the aid station & for some reason (hoping for a miracle?) restarted it when I left, so that's why there's a discrepancy in the times.

Next up:

I've postponed all my construction projects around the house this summer due to my back & have been getting alot of back rest.  I used to call my running nemesis the "fickle" back -- I never knew when it was going to flare up.  I've dealt with it most of my running years and now, after a short absence, it has returned.   Since I no longer perform heavy lifting on a regular basis (using wood as a primary source of heat), I feel (& hope) this is just temporary.  Maybe I'll find out when I try Woodstock next month . . .

catch up - continued

After the mental disaster at Massanutten, I could hardly think about anything else.  I figured the best medicine to help get over it was to run another race as soon as possible.  I looked at the calendar & saw a familiar race in Mohican in June, so I set my sights on that race, although twice before (2008 & 2009) it was too hot for me & I also had major back problems.  I mostly don't consider Mohican each year because of that heat (mid 80's to low 90's).  So for it to be a possibility this year, I figured I needed to cram in some heat training. 

I looked for a shorter race in the heat that wasn't too far to drive to and found a 50k in Tennessee: the inaugural Music City Trail Ultra just outside Nashville.  As the date for this race approached, it was clear it was going to be what I was looking for:  forecast was for 89 degrees w/partly cloudy skies, humid and a chance of thundershowers.  I've NEVER finished an ultra where the temps have reached the mid 80's, so I knew it would be a challenge just to finish! 

I camped right at the start/finish line.  It was a hot & muggy night.  There were over 200 that signed up for the 50k, 25k & 10k -- a pretty good turnout for a first time running.  The RD had carved out a rugged course in what seemed to be a rarely frequented nature preserve & consisted of gravel roads, fire breaks and ancient logging roads, with a small amount of seldom used single track & a little bushwacking.  I heard it took months to knock down the brush & weeds to fashion out the trails.

Early in the race on a firebreak, pic courtesy of Chris Bosh:

The ticks & flies were the worst.  The flies weren't the usual deer flies I'm used to.  They didn't seem to bite as much but I've never encountered so many flies (kept the mouth closed). These were like huge houseflies (small horseflies?) that you could knock 2 or 3 down with every swing.  Aid station workers were pulling ticks off my legs even though I had soaked myself with repellent (probably lost it with sweat & going thru the streams).  I also ran over a long black snake before I knew it, as I thought it was just a stick.

I could hardly make heads or tails of the course from the small map on the website.  I couldn't tell which direction the race proceeded and on which trails -- turns out this would affect my race.  I came across 2 confusing intersections.  The 1st one I lucked out as a group of runners came up on me & after a consensus, decided the way to go (I would have went the wrong way otherwise).  At the 2nd intersection, I was by myself & with another 50/50 chance, I took the wrong way.  Ended up with about 1 bonus mile after double tracking twice.  I think if the people who marked the course went in both directions on the out'n'back sections, they would notice the markings can look alot different going in the other direction.

The skies were mostly cloudy with periods of sun thruout the day.  This kept the temps down (only 85!).  The sun only seemed to come out when I was out in open & then it felt like 110.  But what helped the most was the unexpected breeze.  Occasionally there would be a hint of rain in that humid breeze -- I finished the last mile in a downpour.  Had it reached 89 with partly cloudy skies & no wind, I would NOT have finished this race.  This was the hottest ultra I've ever finished.  I survived the challenge (w/the lucky break in the weather) & felt I was ready for an attempt at Mohican.

1 more catch up report to follow . . .