This is part thirteen of a series of posts discussing various aspects of a bike trip I did across the United States in 2012. Part one discussed the start of the trip and choosing a route. Part two discussed my daily routine and nightly shelter. Part three discussed general mileage, elevation encountered, and state-by-state scenery. Part four discussed mileage extremes and water. Part five discussed food. Part six discussed elevation extremes, particularly crossing the Continental Divide at Monarch Pass. Part seven discussed how I used down time and how I kept electronics charged. Part eight discussed mechanical problems and other surprises. Part nine discussed health on an aggressively-paced cross-country bike trip. Part ten discussed how I managed to get home afterward. Part eleven lists all the gear and equipment I took with me. Part twelve discussed the cost of the trip. This post is a catch-all for other random observations I haven’t made yet.
I hit my maximum speed in a place you probably wouldn’t expect: not amidst the Rockies or similar, but on a gradual descent from Carson City to Dayton in Nevada. I’d leaned my bike up too close to an electronic sensor earlier in the day, so my “maximum speed” read as 100+ mi/h, so I don’t know my actual maximum. But in glancing down at my speedometer very briefly (and thinking I probably shouldn’t be looking at it too much ), the highest number I observed was 48.0 mi/h. None too shabby! The big thing that road had going for it (presumably besides a tail wind) was its straightness. Most mountain descents had too many curves in them for me to reach those speeds.
One mildly exciting moment was that time I came kind of close to hitting a deer. I was descending from Lizard Head Pass in Colorado, probably in the mid-thirties speedwise. A few hundred feet off I saw several deer (mother and fawns) on left and right sides of the road, clearly looking to cross to the right. So I slowed down a bit, and they kept standing and waiting for me.
Now, the smart thing to do here is to remember that deer are dumb. Just because they see you coming, they’re not going to necessarily wait for you to pass. So you want to keep that same slow speed, and remain capable of stopping if necessary.
I, on the other hand, promptly assumed moderate intelligence, or at least intelligence commensurate with self-preservation, and assumed the deer were giving (or at least allowing) me an opening to go through. So I stopped braking and sped up again. At which point a fawn on the left side decided to run in front of me across the road. It realized its mistake too late, its hooves scrabbling on the pavement as it tried to run downhill away from me, rather than in front of me. Meanwhile, I swerved slightly to avoid it, avoiding it by a few feet or so. Closer than desirable, but good enough, and good for a story. Next time I’ll remember that 1) deer are stupid, and 2) fawns are even more stupid.
Towns and size
My route took me through a large number of fairly small towns, with populations well under 1000. I don’t really understand how these towns survive. Sure, they might be nice places for the right kind of person to retire. But for anyone who needs to make a living (at least, outside of industries where telecommuting is possible), it’s hard to see that there’s enough work needing to be done to support all those people.
The smallest, most out-of-the-way town I visited was probably Seward, KS, to which the 2010 census ascribed a population of 64. Seward was 18 miles from the previous town, a mile off a county road (so if you’re there, you had to have chosen to go there), and 33 miles from the next town (itself off the county road, albeit on a slightly larger north-south road). Yet somehow it managed to support an entire restaurant in Mom’s Bar and Grill. (With its own website!) Truly surreal. (Although they had a sense of humor about it: one of the staff wore a T-shirt that said, “Where in the hell is Seward, Kansas?” Too true!)
And with that, at least going from a last skim of the route, I might be out of particular things to note. Next time, retrospective and wrapup.