Preparing for first marathon run was a challenge in itself
A person doesn't have to be crazy to attempt a marathon, but I have come to believe it probably helps to be at least a little bit loco.
Certainly most of the people who become aware of my plans to complete the 26.2-mile endeavor at Oklahoma City next Sunday express concerns about the state of my mental health.
Often, people say they couldn't run 26 feet, let alone 26 miles. And, quite honestly, the fact that I have prepared my 46-year-old body over a 16-week period for the biggest sporting challenge I have faced in my life, makes me feel pretty good about myself.
I remind people that more than several Hillsboro natives have completed marathons over the years. My story is anything but unique. I also inform skeptics that I didn't start out covering 20 miles or more at a time. I began with runs of four miles, three days a week. This has been a slow, steady progression.
I followed a plan outlined by Runners World magazine for a beginner. Having a plan on paper has been extremely helpful in sticking with the program.
I also feel obligated to point out that very few people actually run the full distance. Even Hillsboro's Todd Lehman, a Boston Marathon qualifier, likely takes a break or two during the race.
I expect to walk for one minute after each mile. It's a program developed by Jeff Galloway, who has completed more than 110 marathons in his lifetime. A former Olympian, Galloway bases his theory on the premise that if a person walks early and often, the short slowdown will give the body enough of a recovery break to allow the athlete to be going strong late in the race while those who run the whole time will be fading.
Glen Kliewer, a two-time finisher from Hillsboro, uses this method. That's good enough for me, and that's the way I have trained on my long runs.
So, what would possess a graying high school English teacher to embark on such an adventure? Galloway calls it a mid-life mission. He claims that the 40-plus age group is the fastest-growing marathon crowd.
Hey, it's cheaper than a new red Corvette and less stressful than a new redhead.
I plan to report on my marathon journey in my May column, assuming I finish. If I don't, I won't feel as motivated to chronicle the attempt.
I have been keeping a journal of sorts over the past 15 weeks. I'd like to share some excerpts as a way of either encouraging others to follow in my footsteps or explain the process to those who believe I am completely nuts.
Week 1: 20 miles. I'm used to running about 12-16 miles per week. My two runs, Wednesday and Saturday, were about six miles each. They were not a problem. The biggest change was running Friday and Saturday, rather than leaving a day in between. I was afraid of a tendonitis flair up. But, it didn't happen.
Week 2: 17.5 miles. I cheated a bit this week. I just couldn't find time to run Friday's four miles, and I couldn't see the point. So, I ran my seven on Saturday without the Friday run. The Saturday run was not a problem as I was entertained by the first half of the KU basketball game. So far, all my runs have taken place indoors on my treadmill.
Week 3: 18 miles. A good training week, though my lungs and chest have felt a bit tight at times. This was Trojan Classic week, an announce-athon for me with 18 games, including seven on Saturday. So, rather than get up super early, I ran my scheduled eight miles on Friday starting at 9:15 p.m.
I should have removed my shirt. I received an extremely sore area of my chest that protrudes, if you get my drift, as a result of my run. Otherwise, it went well.
Week 4: 19 miles. This week wrapped up the first month. I had a good outside run on Wednesday, three miles out to the north and three miles back. I ran into a bit of mud. The temperature was in the low 40s.
Saturday's 9-miler was kind of tough. I arose at 6:30 a.m. so I could get to Wichita and help son Jordan move from one apartment to another.
In Wichita, I visited the First Gear running store in Old Town and talked marathon with the staff. I bought some dri-fit shirts and shorts, designed to wick moisture away from the body. I hope they will solve the chafing issues by keeping me drier.
Week 5: 21 miles. I set up an impromptu 5-kilometer run with some high school students. We completed the city course in 23:30 on Friday. The temperature outside was in the low 60s.
I wore my new dri-fit shirt for my Wednesday six-mile run, and it seemed to help with the chafing. I also wore my new shorts for my 8-mile run on Saturday, and they seemed to help as well.
I had the opportunity to visit with Glen about his OKC marathon last year. He plans to run at Abilene the first weekend in April. At first, I thought he was nuts, but he explained that this would be a training run for him and would be simply a long, supported run.
It makes some sense, but I would have to kick up my mileage to be ready for a 26-miler at that point and kick in about $55. I'll have to think about it.
Week 6: 22 miles. I logged the most mileage ever in one week, culminating in a 10-mile run/walk on Saturday. Even though I wore the dri-fit shirt, I ended up with some serious chest chafing. So, for the first time since I started this adventure, I am doubting my capability to complete my training. My longest effort so far is not even half of what it will take to complete the 26.2 miles. Is this plan even realistic?
Week 16: 24 miles. The most challenging run so far was Saturday's 12-miler, all on the treadmill. With a little Vaseline, the leg chafing was solved. I didn't wear a shirt, so the torso chafing was not an issue.
I found out that my treadmill stops at 100 minutes. For a bit, I couldn't get it restarted until if figured out what had happened. I thought maybe I burned out the motor.
I covered the 12 miles in just over 107 minutes. I felt quite drained, possibly because I decided to switch to a different system. I walked one minute after completing each mile, rather than one minute after each five minutes run.
I'm hoping to match the way Glen plans to run at OKC.
Week 8: 25 miles. Several people told me during the week that my stamina will continue to build, that I shouldn't worry. Apparently, they were right. My long run of 12 miles on Saturday went much better than my first 12-miler the Saturday before.
I actually felt pretty good after completing the run. I had eaten a light breakfast at about 8 a.m., then began my run at 11 a.m. The Vaseline is doing the trick on my leg chafing problem. But, I still haven't tried to run this far with a shirt on since the last painful episode. Will I be able to solve that issue? The good news is I am still in the game as the calendar turns to March.
Week 9: 28 miles. Saturday's 14-mile run nearly did me in. Afterward, I ran a few errands, then took a hot shower. I nearly passed out. I felt sick for most of the day.
By evening, I had mostly recovered. But it scared me a bit and shook my confidence. Will I really be able to do this? My best effort so far has been just over the halfway point. I will try again next Saturday.
So far, the pattern has been that the first attempt at a long run sucks, and the second is not as rough. I hope that pattern continues.
Week 10: 25 miles. I originally thought I would cover 14 miles again on Saturday, but I didn't feel well Friday night, and I kind of chickened out. So, I stuck with the Runners World plan of running a 10-k two days in a row, Saturday and Sunday. I ran them outside with no walking, and that felt really good, especially getting back out into the open air.
As it turned out, this would also allow me to move my long run next week to Sunday. I will be busy Saturday. I also noted that when I ran outside, I had no chest chafing issues. Interesting.
Week 11: 29 miles. I made a mistake and only ran eight miles on Thursday. I was scheduled to run nine. But I ran it outside due to the warm, dry weather.
The forecast for Sunday was not looking good, so I completed my 16-miler on Saturday afternoon. It went really well. I was chased by a dog briefly, but he was just curious, not furious.
I zig-zagged all around the area north of Hillsboro for a time of 2:28. I felt no ill effects besides tight calves after the run. Very encouraging.
Week 12: 32 miles. Wow! I did it. I ran from Goessel to Hillsboro Sunday afternoon. Actually, I ran one mile west, 1/4 south, 1/4 north, and back to Goessel before heading for Hillsboro because it is only 15 miles from State Street in Goessel to Ash and D Street in Hillsboro.
My legs were burning, but the lungs held out, and chafing was not an issue in the cool, dry weather. I finished in 2:41, almost too fast.
But I don't think speed is so much an issue. I'm a little concerned about leg stamina. I was once again encouraged, however, as virtually all my mileage was on pavement and up and down some considerable hills. Next week: a 20-miler. Then I begin to taper.
Week 13: 39 miles. This was the big one, 10 miles Thursday, four miles Saturday and 20 miles Sunday in a time of 3:06. I survived, but just barely. I felt pretty sick when I stumbled into my yard.
I am still starting out way too fast. My first mile was 7:34. I'm thinking that's what nearly caused my downfall. I ran two 10-mile loops to the north of Hillsboro and back to town. From here on out until M-Day, my longest run is a mere 10 miles. That's the good news.
I also encountered a large white cow on the road Sunday. I wasn't really sure which way she was heading, so I opted to quietly go around her. Next time around, she was gone.
I have seen some wildlife in my treks around Hillsboro. Often I see turkey vultures. I'm not sure that is such a good sign for a long-distance runner. I'm also quite sure I saw an eagle one day. It was too big for a hawk.
Week 14: 25 miles. Let the tapering begin. It felt a bit strange backing off after that excruciating 20-miler on the previous Sunday.
I received a card confirming my registration in the OKC marathon. I'm getting stoked for the event. Is it too early to start praying about the weather?
I ran a few laps with Todd out at the track Saturday. He was very encouraging. An article in the Free Press about his upcoming Boston Marathon effort mentioned that I was planning to compete at OKC. So, I guess I have no choice but to follow through. I have said all along the more people I tell, the better chance that I will stick with it.
I strayed from the training schedule just a bit this week and ran 10 miles Thursday and 10 Saturday. My family needed to go furniture shopping Sunday since that is the only day wife Kathy has off. So, a 10-mile run would not fit the schedule.
Week 15: 16 miles (only). I came across an online article this week that pointed out the absolute necessity of tapering back on miles run in the final three weeks before the big day. It described exactly my feelings that I am not putting in the needed miles to stay in shape.
The article also nailed my continuing desire to devour any food within arms' reach. My metabolism is sky high as my body repairs the damage I have subjected it to the past few months, according to the article.
Next week calls for only three miles Tuesday, three miles Thursday and an optional two-mile jog Saturday.
Oh, yeah. Then there's the matter of that little race in Oklahoma City on Sunday. If you want to check the results to see how the Hillsboro contingent fared, log on to okcmarathon.com after the race is over about mid-afternoon. If you just want to pray for us, that would be acceptable as well.