Bagging Croydon (#144) and Granthan (#145) in the quest to run 5K in all N.H. locations

Where I didn't want to leave my car.

If we ever have to do without cars, I know how long it would take to get from Croydon to Grantham, N.H.

I ran a "back-to-back" in those two towns this past Saturday, making them #144 and #145 in my quest to run a minimum of 5K in every city, town, and unincorporated place in New Hampshire.

And unlike a lot of these runs, this one worked out to be between the two actual villages rather than just out in the middle of nowhere, although there was certainly enough of that. Read on!

The date: Saturday, Oct. 15. Due in Brandon, Vt. that evening for a performance, my original plan was to veer further north and knock off two more-distance communities: Wentworth and Warren.

But a late start and then heavy traffic on Interstate 93 heading north prompted me to change plans before the I-93/I-89 split.

I didn't really have a Plan B, but realized en route that Croydon and Grantham were two towns I needed, and were just off I-89 on the way to Vermont.

So up I went, taking Exit 13 in Grantham and following Route 10 south towards Croydon.

Good old Route 10, which wanders through the western part of the Granite State from the Mass. line all the way up to Hanover and Dartmouth College.

I actually once wrote a travelogue about Route 10 for New Hampshire Magazine some time ago. It doesn't seem to be online anywhere—perhaps I'll fish it out of the archives and post it later.

Travelogue or not, here I was again on Route 10 as it wound its way along the shallow valley of the North Branch of the Sugar River, which was just beginning its long journey to the Connecticut River.

My usual method of a "back-to-back" is to find the boundary between two towns, then pace off 1.6 miles in each direction, noting the turn-around point at each end.

I then return to the border and head out in one direction as far as the turn-around point, then head back and cross the border in the other direction.

At the second turn-around point, I then head back the start, which is now the finish line.

As long as I've done the math right, that's a minimum of 3.2 miles in each community. And that exceeds my minimum distance of 5K, which is 3.1 miles.

One reason this works so well is that for some reason, New Hampshire communities are very good about marking the town lines.

Maybe it's due to road maintenance obligations. Maybe just a turf thing. But in New Hampshire, roads in and out of even the smallest, most remote towns invariably sport flashy green border markers.

The roads themselves may be crumbling to pieces, but the signs always seem look brand new.

Look at the size of that breakdown lane!

In this case, Route 10 wasn't falling to pieces. On the contrary: it was clean and dark and newly paved with a smooth surface and a gentle crown.

The speed limit was as high as 55 m.p.h. on long "straightaways" (as we call them), but a generous breakdown lane would keep a runner from feeling any danger.

The Grantham/Croydon line happened to be right in the middle of one of these straightaways, out in the open for all to see.

One disadvantage to this to this: there was no convenient place to stow my car. Not that anything would happen here, other than a bear coming by to ransack the vehicle.

I just don't like leaving it out in the open while I'm off jogging around.

I then hopped back in to measure off 1.6 miles into Croydon to find my turn-around point. To my surprise, the village of Croydon came up quite quickly: the historical society, the church, the school, the Coniston General Store.

That last one is a nod to the 1906 novel "Coniston" by New Hampshire author Winston Churchill, not be confused with the British politician of the same name.

"Coniston," a best-seller, was an historical tale set in the world of 19th century New Hampshire politics. Locations included the fictional town of Coniston, which was a stand-in for Croydon.

And the turnaround coincided exactly with Pat Sawyer Memorial Park, completely deserted but with a nice parking area.

And right across the highway: Milepost 60.0. So I immediately decided to base myself here: 1.6 miles from the town line. I would run back up the highway, over the town line into Grantham, and then as far as Milepost 63.2.

I'd then turn around and retrace my steps. Presto! Two towns, and a little more than 5K in each.

And so it came to pass. The afternoon was warm for October: temps in the high 50s, but with almost no wind.

High clouds were moving in from the south, filtering out the sun and muting the fall colors all around me. A pretty good day to be out for a run.

I'll meet you at the old barn. You know—the old barn!

I started at 1:32 p.m., heading north, accompanied mostly by the sound of my own feet on the pavement, the occasional passing vehicle, and occasional bursts of rifle fire from the woods.

One virtue of Route 10 following the valley of the North Branch of the Sugar River is that even though we were high in the hills, the course was almost completely flat!

The only grade at all was a short bump up into the town of Grantham proper, at the far end of my route.

The exact turn-around spot of Milepost 63.2 was at Grantham's Dunbar Library, across from the United Methodist Church. Village to village!

And I couldn't help but think I had covered the distance between both towns on foot in a way that must have been much more common say, a hundred years ago.

In case anyone wants to know: people can still do it, if they have to. I did, anyway.

I felt strong pretty much the whole way. No foot pains, no issues at all.

As I strode through Croydon on final approach, I was surprised to find Pat Sawyer Memorial Park now being used by three men at the lone basketball net, shooting hoop.

They left me alone, and I left them alone. But if they were curious about the guy in the orange shirt and black shorts running through their town last Saturday—well, he made it to Grantham and back in exactly 1 hour and 20 minutes.

The distance was 6.4 miles, meaning a pace of 12:30. That's somewhat better than what I've logged lately, probably because of the flatness of the course and the pleasantness of the weather.

Next up: Running in another state this week. More later!

Reaching the Halfway Point: New Jersey is #25 in the quest to run 10K all 50 states

The hand-drawn map I used to bag Bayonne, N.J. on Saturday, July 2.

While driving across the bridge to Bayonne, N.J., I began to detect an odor that was halfway between basil and a fire at a tire dump.

"Just great!" I thought, from behind the wheel of my new (to me) 2012 Subaru Forester, assuming it was the car burning coolant, or window washer fluid, or something. "Well, at least I found out while the dealer will still cover any fix."

But it wasn't my car, which was on its first extended road trip under new ownership. I found that the source of the odor was the Hackensack River, which forms Bayonne's western border. It really does smell like basil and a tire dump fire, with notes of spoiled ginger and rotting shellfish at low tide.

So it was with a sense of relief that I commenced what turned out to be a 7.1-mile loop around Bayonne, a community of about 65,000 people crowded onto a peninsula that juts into the heart of the New Jersey industrial docklands west of New York Harbor.

Ah, New Jersey, land where citizens are forbidden to pump their own gas. I came to keep alive my "once-a-month" state run streak, active since December of last year. If successful, the run would put me at the half-way point of completing this extended project.

Bayonne is a community of single-family homes crowded onto small lots. Streets are arranged in a grid pattern, with corner stores everywhere. And good public transit options. Example: Manhattan is within easy reach via New Jersey Transit Light Rail up to Hoboken, then PATH trains under the Hudson.

Bayonne's eastern flank remains the site of heavy-duty petrochemical industry, and the southern tip is dominated by the massive Bayonne Bridge, opened in 1931 and spanning the Kill Van Kull (one of the world's busiest shipping channels) to Staten Island.

The Bayonne Bridge, with Bayonne in the foreground.

The iconic span is currently being rebuilt to keep the graceful main arch intact, but to raise the roadway about 60 feet higher to accommodate larger cargo ships now passing through the Panama Canal. If that process is of interest, check out this thorough and informative article about the whole process.

But on this sunny, dry and windy Saturday, my route was entirely within the community's residential core. Starting on East 12th Street, I would run counter-clockwise, more or less, and mostly on the outer avenues, taking advantage of the lack of busy cross streets on the sides closest to the water.

The highlight would be an extended stretch of park fronting the Hackensack River, giving me a chance to really get that special odor into my lungs. Driving into town, with its incredible diversity of small residential and commercial buildings, and almost complete absence of national chain stores, I felt I was in a place with character.
Why Bayonne? (Now there's a question I bet I'm not the first to ask.)

Beautiful Bayonne, with New York City rising in the northeast.

Well, it was close to Staten Island, which is where I was heading afterwards to visit a friend and take a shower.

But also, one of my Fordham classmates, Richard Szemiot, grew up in Bayonne. Years later, for his first foreign trip, he joined a small group of us visiting Thailand. And everywhere we went in that exotic land, he found some way of comparing what he saw to Bayonne. Example:

"Richard, what do you think of that sunset?"

"It really takes me back—it looks like the sunsets you'd get from the Bayonne Bridge."

Since that trip, I've been eager to visit Bayonne and see how it reminded me of Thailand.

So I should not have been surprised when the first part of my route along Avenue E took me past this place:

I headed north up Avenue E as far as about 50th Street, then crossed over to the other side of town to run along the Hackensack River, planning to use what seemed to be a bucolic network of walking paths, at least when viewed using Google Earth.

One surprise: Bayonne has hills! Well, surprisingly steep inclines, anyway. It's not San Francisco, but there's a definite ridge running along the spine of most of the peninsula. (Guess that's way it's dry land and not part of the bay.)

Another surprise: the river paths aren't accessible from where I wound up. They're blocked by gates festooned with PRIVATE PROPERTY and NO TRESPASSING signs.

But still, I was glad I came to this corner of Bayonne, as it turned out to be the scene of some actual drama.

While jogging cluelessly along West 54th St., I saw people gathered on the sidewalk up ahead. A mild commotion was ensuing over...a new puppy! A young child was holding the dog's new leash as family members and neighbors made a fuss.

Well, how about that? The scenes you come across on the streets of Bayonne.

But before I could finish that thought, the puppy got loose and darted out into the street—directly into the path of an oncoming car!

This prompted screams from the sidewalk as adults held back the child (who'd dropped the leash) from chasing after the mutt, who was excitedly sniffing a bush across the street.

So I heroically veered out onto the pavement and motioned the driver to stop (which he'd already done) as a family member retrieved the dog.

I tried to think of the Spanish words for "My work here is done" but instead just waved to the family and went on my way.

I did finally reach the Hackensack River, but only through the semi-manicured grounds of Steven R. Gregg Park, a 100-acre spread laid out along the shoreline.

It's a pretty impressive urban greenspace, with roadways and walking paths looping through groves of mature shade trees, all of it leading down to the riverfront, which is laid out with Beaux-Arts flourishes. Think Greek temple on a minimalist budget, with a big helping of Atlantic City boardwalk along the riverfront itself.

Although the view is dominated by container ship unloading facilities on the opposite shore, it's a nice place, with a freshening breeze carrying the now-familiar odor ashore in great gusts.

However, you can't escape these alarming signs, which are posted simply everywhere, in English and Spanish:

I have to say, it's the first time I've seen signs warning of brain cancer from the use of recreational lands.

What's going on is that the whole areas of Newark Bay remains polluted from chemicals used in the production of Agent Orange during the Vietnam War. Turns out the dioxins can accumulate in shellfish to the point where they're poisonous.

Apparently people still go out "crabbing" in the area, and the results can be deadly. Hence the signs.

After exiting the park, I headed down shadeless Avenue A for the final push. Among the highlights of this area: Bayonne High School, done in the Gothic style popular for education buildings in a bygone area. They really don't make 'em like this any more:

Bayonne High: Built for the ages.

It was now mid-afternoon. With more sun than clouds, not even the basil-scented breeze could keep me from feeling like I was overheating. I was in fact acquring a good sunburn, but that wasn't apparent until later.

Glad to find my car parked where I'd left it, and unmolested. (Compare that to what happened to me in Boston last April.)

The final tally: 7.1 miles in 1 hour and 43 minutes, or a pace of 14:30. Good enough!

And now—anyone hungry for crabs?

Bagging Delaware (#24) on a soggy day and notes about other recent adventures

My all-weather map of Delaware. Note state's name spelled wrong.

Okay, it's been awhile so figured time for an update.

Amazing but true: I've kept up the one-per-month pace in my quest to run a minimum of 10K in all 50 states.

Just yesterday (Thursday, June 16), it was Delaware. In May, it was Nevada. In April, Massachusetts. The last day of March found me in unseasonably mild rural Rhode Island, while February brought me to Central City, Nebraska, which I discovered is anything but central.

So I'm now up to a total of 24, and running out of close-by states, which means it'll be more challenging to keep the once-a-month pace going.

The only states I have within driving distance are Maine and, sort of, New Jersey.

The remainder will involve at least some kind of trip away from home base to accomplish. Some can be done in one day if I find a cheap air fare.

But right now, I don't have any firm plans until when I go out to California November. That's when I might try to get either Oregon or Washington. Or both. :)

A planned visit to Sioux City, Iowa next February will give me a chance to bag that state and maybe a couple of others in the upper Midwest: South Dakota and Minnesota.

Among states in the "day-trip" category are a stretch in the deep south: South Carolina, Georgia, Tennessee Alabama, Mississippi and Louisiana. With JetBlue and Southwest out of Boston, they're all doable.

Same thing with a few in the Midwest: Indiana, Michigan, and Wisconsin.

Well, if I can somehow keep up a pace of one state per month, that means I'll be finished by...July 2018!

That's not allowing for recovery from knee surgery I'm sure I'll need at some point.

And as for Delaware: Dover is hands-down the flattest place I've ever run in. For the entire route, the biggest gains (or losse) in altitude were when I hopped on and off a curb!

I'll give the place high marks for sidewalks, though. Of the entire 6.6-mile course, which included some stretches of road far out in the suburbs, only one short section was without some kind of pedestrian way.

Lots of bike paths as well. Wish my own area of Manchester, N.H. and its surrounding suburbs could enjoy amenities like this.

In other news:

• Summited Mount Moosilauke with a small party on Saturday, June 11. Didn't add to my total of 4,000-footers, which still stands at 31. Still, it was enough to get me back on the trail.

A busy calendar, alas, means there aren't too many opportunities in the near future to conquer any more of the 48 peaks on the list.

A new wrinkle is our youngest dog, Inca. She likes to get out and did well on Mount Moosilauke, save for not appreciating rain on the way down.

For her, Mount Moosilauke was #6, so it's time to get moving if she's going to have a chance to complete the whole roster.

Alas, our older dog, Zahnna, is now too infirm to haul herself up (and down) a White Mountain summit. As a 13-year-old German Shepherd, she now has trouble with household stairs, so her total of peaks will have to stand at 31—the same as me.

• Haven't yet run in any official road races this year. Again, mostly a function of time and organization. I have these fantasies of getting up early on the weekends and hauling myself out to New Hampshire communities I've yet to run in. Ha!

But will make it a priority to make some progress in this area. Same with longer bike rides.

Bagging nearby Vermont (#19) in mid-winter

Bennington's picturesque train depot during greener months.

A mild winter (so far) recently gave me an opening to add to the "Running in All 50 States" project. So I took it!

The opening came on Sunday, Jan. 31, while driving back to New Hampshire from a silent film accompaniment performance in upstate New York.

As I followed Route 67 into Bennington, Vt., it was overcast but mild (above 40 degrees) and getting milder.

It being the final day of January, it was my last chance to get in a long run in a new state, thus extending my streak of consecutive months to a grand total of two.

The trouble was that time was running short. I was due in Wilton, N.H. (about two hours away) for a performance at 4:30 p.m. that very afternoon.

And as I pulled into Bennington, it was already 11:30 a.m.

Some quick in-my-head math convinced me I could still pull off a long run, although there was precious margin for error.

So I sat there in North Bennington and used Google Maps to eyeball a loop route out to Shaftsbury (following the old Rutland Railroad's main line) then down 7A into Bennington, then cutting back through local roads and around the Bennington College campus to back where I started.

The minimum distance for these state runs is 10K, or 6.2 miles. Just to be sure, I quickly drove the planned route, and was surprised to find it added up to 8.0 miles.

Too long! At my pace, I wouldn't finish in time to make it comfortably over to Wilton.

So, looking at the map, I quickly altered the end of the route to tighten the loop and shave off enough distance to shorten the run, but not below 6.2 miles.

Because then it wouldn't count!

With no time to drive this revised route and check the distance, I decided it was time to just do it.

I had dressed for cooler weather, but it was in the mid-40s. So I wound up bare-legged, with only black shorts and my lime green wicking moisture T-shirt. In January in Vermont!

But I really lucked out, not just in weather, but in location. The valley floor in this part of Vermont is studded with village centers and picturesque homes and even a real working railroad line!

So off I went, with North Bennington Village my starting point. Time was 11:47 a.m.

First I crossed over the railroad line while gawking at Bennington's handsome Victorian passenger depot. The depot sits unused but ready to host Amtrak trains from Burlington to NYC in the near future. The clock on the cupola is working and We'll see.

I then quickly found myself in open country, with the road paralleling the rail line in classic New England fashion.

After about two miles, I hit Route 7A in Shaftsbury, where I turned south. The rail line ducked under the road and curved out of sight on its way up to Rutland.

This was the busiest stretch of roadway, and the hilliest. But amazingly, parts of it had sidewalks! So other than dodging snowmelt puddles, it was pretty easy.

I then made the move to shorten the route: turning right on Overlea Road, which would send me right into Bennington College, which I'd skirt to the north on my way back to North Bennington.

The road—really a residential street—was so quiet, I could run in the middle of it for long stretches with no sign of any vehicles.

The grade drifted downwards until it crossed the disused rail spur running south into Bennington—the stub end of what I later learned was called the "Corkscrew Branch" to Albany, N.Y.

Today it dead-ends in Bennington. At the Overlea Road crossing, a clutch of at least two dozen tank cars (that's all I could see) were stored south of the crossing.

I then hauled myself upgrade to make a right on Matteson, which was necessary to have enough distance for this run to count.

My next turn was right on Harlan, but it seemed to be taking a long time to come. Meanwhile, I enjoyed views of the famous Battle of Bennington Monument, which was visible rising from the hills to the south.

Finally, a street on the right. But with a missing street sign! Should I take it or not?

A wrong turn could cost me precious minutes (not to mention foul up my distance), and I had to be in Wilton ready to do a three-hour movie at 4:30 p.m.

Dead reckoning told me to take it, so I did. I slogged upgrade for awhile (This better be the right road!), and was never so relieved to see HARLAN at the next intersection, which was with College Road, my next turn.

College Road skirted the northern boundary of property owned by Bennington College, long famous as the school with the highest tuition in the nation. (I just checked, and that's not true anymore. But still, it's about $50K a year.)

A flat well-paved surface, and complete absence of traffic, inspired me to do a series of "arm lifts" where I reach high, then move my wrists, all while keeping pace running. It really helps break the repetitive running pattern and adds to the aerobic workout.

I was closing in on where I started, but the maps weren't clear about the best road to take, and neither was I.

But a quick turn down a side street put me on Mechanic Street—exactly the right road to take me back to where I started. And it had sidewalks, too!

As I approached my car, I felt not quite sure that I'd completed 6.2 miles. So I kept going up the depot again, and then back, adding perhaps 2/10 of a mile just for insurance.

Stop time: 1:09. But what was the distance?

I drove the route, watching the miles add up. Turning onto Overlea, we still hadn't reached 5, so I began to worry. But we hit 6 while still on College Road, so I knew I'd be okay.

The final tally: 6.6 miles in 1 hour and 22 minutes, or a pace of 12:25 per mile.

I changed my clothes at a gas station along the way.

And yes, I made it to Wilton on time!

Adding Pennsylvania (#17) and Kentucky (#18)

Geez, look at those elevation lines to the south of downtown Coraopolis.

Okay, I admit there's been something of a gap in my quest to run a minimum of 10K in each of the 50 states.

With nothing to report since 2013! Really?

But the drought is over, as I chalked up two states in two days during a recent silent film accompaniment road trip from New Hampshire to the Midwest.

The pair are Pennsylvania (#17, on Thursday, Dec. 10) and Kentucky (#18, on Friday, Dec. 11).

I'm not sure what's more amazing: that the December weather allowed for two long pleasant morning runs (in shorts!), or that I was actually able to complete them back-to-back without any injury or problem or really any soreness.

In fact, after each run I felt energized and calm for the rest of the day, a large part of which was filled with driving to the next city.

It reminded me of what it felt like when I was running long distances while a student in Glasgow: early morning runs through unfamiliar territory in cool but not cold weather, followed by a day of classes.

I had originally planned to try for a third state on this trip: Michigan on Saturday, Dec. 12. But this would have required driving two hours each way from where I was staying in Cleveland.

And by then, after spending most of the past three days behind the wheel, I didn't want to give up my one without driving, driving, driving.

Plus, I had completed two long runs in the prior two days. I felt fine, but I knew piling on another long one was courting trouble, and I had miles to go before I slept, if you know what I mean.

The Pennsylvania run was in the town of Coraopolis, a community on the south bank of the Ohio River just downstream from downtown Pittsburgh.

I mapped out what seemed like an easy route to follow, from my Motel 6 at the airport along a Thorn Run Road all the way to the river and downtown Coraopolis, then looping back by Main Street and Maple Street to Coraopolis Heights Road, which ran through a rural area all the way back to the hotel.

Here's Part 1 of the Pennsylvania run, using Dairy Queen as a landmark.

What I didn't count on was the incredibly steep drop down to the river. I expected a downgrade, but not the kind of descent I found myself making from the ridgeline above the Ohio River.

I must have lost at least 700 feet in a very short distance, finally bottoming out on "Fifth Avenue," which would not be mistaken for the New York City thoroughfare of the same name.

What goes down must come up, and I steeled myself (local industry reference!) for the right-hand turn on Main Street that would start taking me back up.

Here's Part 2 of the Pennsylvania run.

Although the small downtown was on a narrow flat plain along the river, the streets to the right of me literally took off up the slope at such a rate that second floor could have a door onto the sidewalk.

Turning onto Main Street, it seemed like it was straight up. Cobblestones were an interesting touch, and block by block I huffed my way back up the ridge.

I then ran into one of those frustrating moments where Google Maps doesn't exactly mirror reality. Main Street went up and up, and so did I, until it reached a dead end!

What? It was supposed to connect with Maple Street Extension, which I believed was the road running far below us. A postman confirmed this, and so I hustled along the edge of a large cemetery (the symbolism was not lost) going down to meet Maple Street Extension, and start the climb back up all over again.

The rest of the run went smoothly. I found myself feeling strong even as Coraopolis Heights Road stretched out before me through rolling countryside, with no sign of the airport for what seemed like a very long time.

End result: 6.9 miles in 1 hour, 31 minutes, for a pace of 13:12. I'll take it, especially considering those long upgrades.

The next morning found me in Covington, Kentucky, the urban community just across the Ohio River from downtown Cincinnati. I plotted a looping route that would take me across the Licking River and back, assuming the bridges had pedestrian crossings.

Weather was the same as the day before: cool and damp, with just the hint of a spritz of rain in the air.

The route first took me across the Licking River into Newport, then back into Covington.

The first bridge did indeed accommodate pedestrians, and I soon found myself in a somewhat down-at-the-heel part of Newport, a place where the Pabst Blue Ribbon people still have a lock on all tavern promotional signs.

But still, the older housing stock had a lot of character, even if some of the brick buildings have been painted in alarming colors.

I then huffed my way back across another bridge and into Covington, where I went through some pretty spectacular neighborhoods, especially the Warren Avenue area.

After reacehing Meinken Park, I headed back, mostly along Madison Avenue almost the whole way back to the hotel.

Taking the direct route back to the hotel, for a total of 8 miles.

End result: 8.0 miles in 1 hour, 45 minutes, for a pace of 13:07. Not bad considering what I'd run the day before.

So I felt pretty good after what for me were two long back-to-back runs.

Back in New Hampshire, the weather continues unseasonably mild even as I write this. So perhaps I might get one more nearby state before the year ends. We'll see.

Bagging two more New Hampshire towns: Shelburne (#142) and Gorham (#143)

My turn-around point in Shelburne was this spot, exactly 1.6 miles from where I parked the car at the 27.0 mile marker. Late afternoon in December = looooong shadows.

I never thought I'd go running north of Mount Washington in December—in shorts!

But a spell of unseasonably mild weather in our part of the world allowed me to bag two towns "north of the notches," as they say: rural Shelburne and comparatively cosmopolitan Gorham. And I didn't have to bundle up.

The date: Saturday, Dec. 5. The occasion: on my way to an annual silent film screening in the even-further north community of Dixfield, Maine. The goal: to run a minimum of 5K in at least a couple of towns that I doubt will ever hold an official road race.

I don't often get to run in towns this far north. But in planning this gig, I figured that on my way it might be possible to fit in a run among the enormous snowbanks usually in place by now.

Well, Mother Nature had other plans. The higher summits of the surrounding White Mountains are indeed white, but winter hasn't quite reached the valleys just.

Thus I found myself pulling off Route 2 at the Gorham / Shelburne line onto a grassy patch that made for a perfect parking spot.

As it became clear that the weather would be unseasonably nice, I actually had plans to bag four towns. Before Gorham / Shelburne, I had hoped to do a similar two-town run in Jefferson and Randolph, through which Route 2 also runs.

But coming up through Franconia Notch, I noticed a light coating of snow on the shoulder. And heading further through Twin Mountain, I watched as the temperature dropped below 40 degrees. Anything lower requires extra gear, which I didn't bring.

So I wasn't sure about the Jefferson / Randolph stretch, and then ultimately bagged it because that section of the road is narrow, with very little shoulder, and has a lot of steep ups and downs. That, plus the slushy roadside snow and the at-times heavy traffic, made me push on to Gorham / Shelburne.

It turned out to be the right decision. They're at a lower elevation, so the temp had recovered to the mid-forties by the time I pulled in. Plus, the road follows the Androscoggin River, which at this point flows along a flat stretch of valley. And Route 2 is in pretty good shape in these parts, too.

After measuring off 1.6 miles in each direction, I returned to the town line and began the Shelburne stretch at 3:25 p.m.

A long straightaway and then some up-and-down curves took me through some of the dense groves of birch trees for which Shelburne is known. Fun fact: Shelburne's population was 480 in 1859, but only 372 now. So it's one of those upcountry towns that went into decline after the Civil War and still haven't recovered.

I came back to the car at 4:03 p.m. meaning 38 minutes to do 3.2 miles. Nothing to brag about there.

Heading into Gorham for the second part of the run, it was starting to get dark in the valley even though some of the peaks high above us were still catching the light. The wind picked up a bit, but running in shorts still felt fine.

Talk about scenery! The rocky, snow-capped summit of Mount Madison, the nearest Presidential Range peak and rising high above us to the south, looked more like the Matterhorn than it deserved to.

After the rural emptiness of Shelburne, the town center of Gorham seemed like Midtown Manhattan. Stores, restaurants—even sidewalks! (The town's population is about 3,000.)

After my turn-around point, I was headed east-bound, meaning I could better see the day's fading light still kissing the upper reaches of ridges hemming us in. The snow had probably melted a bit and was now refreezing, making the higher spots look like they were lightly dusted with powdered sugar. (Can you tell I was hungry?)

Funny: in Gorham I passed signed promoting the town's 5K run on Thanksgiving. Ooops, missed it!

Reached the car at 4:43 p.m., meaning about 40 minutes for the final 3.2 miles. By then it was completely dark, but the temperature had dropped just a bit: to 41 degrees.

And so I had just enough time to drive up the street to the town's Subway (housed in a former bank branch office), where I changed into my performing clothes and got a sandwich.

Next up: this coming week I'm on a road trip to Ohio and Toronto, Canada, and so have an opportunity to claim as many as three new states in my quest to run at least 10K in all 50.

Stay tuned!

Another month, another half-marathon!

In the least unflattering photo of several taken during the race, I'm about to cross the finish line.

It was a few days ago now. But this is to note that I ran in and finished the half-marathon version of this year's Manchester (N.H.) City Marathon.

The race, held Sunday, Nov. 1, 2015, attracted 344 entrants for the half-marathon of 13.1 miles, vs. about 200 for the full 26.2-mile marathon.

In a race this long, most of my effort goes into carefully pacing myself so as not to become hobbled prior to finishing.

The Manchester course contains quite a few ups and downs, and I have to be very careful not to overdo it on the downs, as this is where bodily stress accumulates fast.

Also, there's a short section of trail running in Livingston Park, which is beautiful to look at, but can trigger problems as my feet hit the rocky surface. So I take it especially slow during that stretch.

But I did manage to keep stride the whole time, not stopping once. I finished at 2 hours, 43 minutes, and 41 seconds, for an overall pace of 12:29 per mile.

That was good enough for 323rd place out of 344 finishers, which is a victory for me in the sense that avoided coming in dead last.

It was my slowest half-marathon yet, but the silver lining is that afterwards I felt only minimal soreness in my feet, ankles, and legs.

After two half-marathons in the last month, could I be building up my ability to run longer distances?

And could that possibly lead to trying to run a full 26.2-mile marathon one of these days?

Time will tell.

Next up: an attempt to add Nevada to the list of states in which I've run a minimum of 10K.

I was hoping October would allow me to add Vermont, but a flat tire and other misadventures during a swing through the Green Mountain State prevented that from happening.

And also, I find I've been missing races in N.H. towns that I could still use.

Just this past month, 5K races were run in Walpole and Holderness, two towns I've wanted to get for a long time. Grrrrrr.

I used to rely on www.coolrunning.com for race listings, but a recent "upgrade" to the site has rendered the "upcoming events" much harder to use and a lot less comprehensive, apparently.

However, the site still carries results of races, which is how I found out about the ones I missed.

So I'll have to reverse-engineer the process, reviewing results from this year and then searching to see if the race will be run next year.

No one said this was supposed to be easy. But sometimes it's harder to find out about races than actually run in them!