Thursday, May 20, 2021

Quick Guide: Backcountry Resupply Caches

I walked into Hot Springs, NC on Day 17 of my 2013 Appalachian Trail hike. I found a cozy hostel, a welcoming populace (Wednesday night potluck at the community center!) and a great greasy-spoon diner that didn't skimp on the portion sizes. I ended up staying in Hot Springs for a day and a half, eating pizza, sampling a few local brews, and hanging out with hikers at the hostel. I don't generally hang out in town on thru-hikes. But I certainly enjoyed Hot Springs.

Not all trail towns are as idyllic as Hot Springs, though. Some towns (Kent, CT) have plenty of services but a terrible attitude. Other towns (Leadore, ID) have a great attitude, but very limited services. And once you get away from established hiking routes and trails, towns are frequently both unfriendly and inconvenient.

One section of the Hayduke Trail, for example, goes more than 300 miles between paved road crossings. Getting to town involves either a lengthy detour or a tough hitch down a dead-end dirt road. At the end of a similarly-sized roadless section of the Idaho Centennial Trail, the nearest "real" town is 80 miles away. Eighty miles! The Hayduke and the ICT are both admittedly fringey hiking routes. But we can push the envelope further. How about a thousand-mile loop of the empty spaces and looming ranges of Nevada, or an 800-mile ramble through the Mojave and Sonoran deserts? What if the best route - as far as scenic values and hiker experience is concerned - goes nowhere near anything that resembles a decent town or a plausible hitch?

The point is this: the need to stop into town once a week can, in some cases, be a major impediment to our enjoyment of a particular environment. But there's good news: we don't actually need to go into town in order to resupply. We can cache supplies in the backcountry instead.

Normally, caching is probably the least desirable way of resupplying. After all, it involves a whole bunch of driving to and from your cache site, before and after your hike. It involves having enough foresight to pack absolutely everything you'll need, weeks or months in advance. And it does involve leaving food unattended in the backcountry, which necessitates strict food-storage practices, as well as compliance with local regulations. All in all, it's a headache. But sometimes, it can be the best way, and allow you to hike a route that would otherwise be logistically impossible.

Prepping maildrops and caches. When appropriate, the latter make for a more pleasant resupply experience (IMO).

What is a cache?

Simply put, a resupply cache is a sturdy container filled with all the supplies a hiker needs, hidden in the backcountry. It requires extra work before and after the hike - you've got to place it before you begin the hike, and retrieve it after you finish. But in exchange, it's enormously convenient while on-trail - there's no need to get off route or go into town in order to resupply. To break it down into steps:

  1. Research your cache. Decide whether or not a cache is actually the best option for your particular resupply needs. Look up whether caching is legal in the area you’re planning to visit - and if so, what the applicable regulations say.
  2. Pack your cache. In addition to backpacking food, you'll want to include first aid supplies, extra gear,and more.
  3. Stash your cache. Drive to a convenient point along your backpacking route, and bury your odor-proof, bear-proof container in an inconspicuous & Leave-No-Trace compliant site
  4. Enjoy your cache. When you get to your cache site, take the afternoon off, eat your "town food", play Angry Birds on your phone while it's charging, wash your socks, and swap out gear. Pack up your backpacking food for the next section and re-bury your cache.
  5. Retrieve your cache. After you complete your hike, drive back to your cache site, pick up your box, and restore the area to a natural look. 

1. Research your cache

It’s the first principle of Leave No Trace outdoor ethics - prepare and plan ahead. Caches require far more forethought than any other method of backpacking resupply. You really do have to think of everything - headlamp batteries, new socks, Leukotape, medications, SD cards for your camera - if you didn’t think of it beforehand, you’ll have to live without it for a couple weeks at a minimum. This may sound intimidating - and to be fair, cache-based wilderness expeditions require a greater skill set than traditional town-based thru-hiking, all else being equal. But that need not scare us off. After all, thru-hiking requires a greater skill set than backpacking, which in turn requires a greater skill set than day hiking. Cache-based expeditions are merely one logical step in our development as outdoorsmen or outdoorswomen, and just about anybody willing and able to put in the time/effort should be able to achieve mastery.

When to cache

In addition to the obvious (town is impossible or inconvenient to get to), there are a few other reasons one might want to cache in the backcountry:

  • It's not safe to go into town. Many hikers aren't particularly comfortable with hitchhiking, especially when they're outside the cozy confines of a well-established trail corridor. And, of course, the Covid-19 pandemic introduced a wrinkle in the "hiker visits town" dynamic. Even though the threat is gradually receding as vaccination rates continue to improve, many hikers prefer to avoid town during the 2021 hiking season - and I certainly can't criticize that decision.
  • You don't have time to go into town. Town stops are the single biggest time-suck on a long-distance hike. It can often take an hour or two to get a ride. And once you get into town, you've got to visit a restaurant, post office, outfitter, grocery store, and laundromat. And by that time, the sun's going down, and you decide to spend the night at a motel. By the time you get back on trail the next morning, the better part of a day has elapsed - and that's if you make your town stop quick! By contrast, with a cache, I can eat my "town food" leisurely, pack up my resupply, launder my clothes, and repair gear - all in about three hours and without feeling rushed. 
  • You don't want to go into town. The founders of the Hayduke Trail designed their route around the cache system - not because towns didn't exist, but because they believed strongly that the best Hayduke experience would be found in two months of uninterrupted wilderness. It turns out that not too many hikers have followed in their footsteps, opting instead for a more traditional hitch-to-town resupply strategy. Nonetheless, their impetus was well-intentioned: spending weeks or months in the wilderness, without going into town, can be a tremendously powerful and rewarding experience.

When not to cache

Caches can be very useful, but they're not always appropriate. Here are a few instances where I would not cache:

  • Whenever it's illegal. You're generally prohibited from caching inside state or national parks. Exceptions exist of course, but generally the more protections that land has, the less likely that it's going to be appropriate/legal to cache on it. Land managers often distinguish between attended food storage (i.e. hanging your food bag near camp) vs unattended food storage (i.e. a cache). There are often different regulations for each. In many jurisdictions, unattended food storage is banned outright. Check the regulations for the park/forest/monument in advance.
  • On/near established long-distance hiking routes. Caching can be a great solution to logistical issues, but it also comes with its fair share of ecological impacts - digging a hole, for one. It's not too big of a problem if one hiker does it on a DIY route in the middle of nowhere - but we probably don't need a couple dozen people all digging holes near the same trailhead. Thankfully, there's generally no need to cache on an established trail. Even the most hardscrabble of CDT trail towns, Leadore ID, has a few people who run shuttles for hikers to and from the trail crossing. That's very much welcome, since there's not too much traffic on that dirt road! 
  • In ecologically sensitive areas. It's completely inappropriate to cache in the high alpine or cryptobiotic desert environments. Areas with lush vegetation and high soil moisture are generally best - these areas will heal quickly once you've removed your cache.

2. Pack your Cache

I used to be pretty skeptical of caches. After all, they shared a lot of similarities with maildrops - similarities that I didn't particularly like. I was forced to plan my resupplies weeks or months in advance, without knowing exactly how my nutritional needs and tastes would change on trail. I couldn't bring string cheese - keeping it unrefrigerated for a week in your pack is no problem, but two months in a cache sounded like a recipe for food poisoning. And finally, I wasn't looking forward to not eating in a restaurant, not being able to wash my clothes, or missing out on any other town niceties.

In preparation for a 2020 Greater Yellowstone Loop hike, I started to research food cache strategies. One of the most insightful tips I got was from serial thru-hiker Buck-30, who'd done some water caching on a hike of the Desert Trail a few years ago. Along with the water caches, Buck packed himself heavy, but yummy food - fruit cocktail and a Diet Coke, in his case. This got the gears turning, and eventually morphed into my "Town-in-a-Box" concept.

Town-in-a-Box

The idea is this: when hikers visit town, we do a lot more than just buy six more days of backpacking food. We pig out at the buffet, compensating for the calorie deficit we've been running. We wash our clothes. We charge our phones. We swap out gear, sip a beer, and relax with some trashy daytime TV. If I'm going to opt for a resupply cache in lieu of a town-stop, then my cache has to serve most, if not all of those functions.

Let's take a walking tour of an imaginary trail town, stopping at each business.

  • Restaurant. You may not be able to get a hot/fresh meal in the woods, but you certainly can pack yourself a bunch of obscenely heavy, bulky items that you'd never take backpacking. A couple cans of chili make a great snack. Ditto with snack-pack pudding cups, fruit cocktail, a 2-liter bottle of pop, or whatever else you crave. Depending on how long you're leaving your cache, and how deep it'll be buried, you can even get away with putting a few fresh fruits or veggies in your cache. How about burritos - tortillas, a can of chicken, a can of chili, a bag of shredded cheddar, fresh tomato, avocado, and onion? I bet that'll keep just fine for a week, buried underground at a constant 55F.
    • Go big! The first time I tried caching town food, I didn't leave myself nearly enough and ended up hungry and miserable. The second time? I left myself a feast.
    • Pack some luxuries. Hikers who typically go stoveless can leave a pot/stove/fuel inside their cache, so they can make a hot meal. Even hot/cooked ramen is a treat when you're used to biting it off the block. And of course, you can leave yourself a glass jar of spaghetti sauce and a container of parmesan with no care in the world for weight. 
  • Grocery store. It's possible to "go shopping" inside your cache - just leave yourself a little extra food so you can pick and choose what you want to carry. That way, if you're sick and tired of the Doritos after a month of eating them, you can pack out the BBQ Lays instead. And if you've been ravenously hungry and running out of food, you have the option to bring both - more food than you originally thought you needed.
    • Don't forget those non-food items that you typically buy at the store - toothpaste, headlamp batteries, ibuprofen, or athletic tape. You might not need all of it at any given resupply, but it's hard to say what you will and won't need. Anything you don't need can just be left in the cache. None of it will go to waste - you'll use it all eventually on future trips, just like with the extra food. 
  • Motel room. In addition to a soft bed, motel rooms offer hikers the chance to take a shower, charge their electronics, and veg out with House M.D. reruns.
    • Consider leaving a sponge in your box so you can wipe yourself down/freshen up. It'll eliminate the worst of the grime. Same thing goes with any other personal care items (say, a hairbrush) that are too heavy or annoying to carry in your backpack.
    • Bring a big battery bank. In addition to taking your phone from zero to 100%, you'll want extra juice so you can take care of the stuff you normally do in town - uploading photos to the cloud, paying your credit card bill, yakking with Great Aunt Edna for 45 minutes, or watching some bad TV. 
    • Before leaving home, check cell coverage maps (Gaia GPS offers layers for most major US carriers) to see if your cache location has cell service. Otherwise you'll have to bring a larger capacity battery on-trail (or a solar charger) so you can take care of all of your electronic entanglements atop a mountain where you actually have service. 
  • Tavern. Slip a couple delicious beverages of choice into your resupply cache. They won't be ice-cold, of course, but they do stay surprisingly cool if they're buried underground. This is particularly true in fairly cold climates, where soil temperature is fairly low. Fortunately, mountainous areas fit the bill. 
  • Post office/outfitter. This is your opportunity to swap out gear and to replenish supplies. Need new shoes or trekking pole tips? Leave yourself a pair. No longer need those microspikes? Leave them in your cache. In this way, with a little forethought, you can swap out your gear, always bringing the right tools for the season and environment.
    • Socks, trekking pole tips, shoes, and bottles of Aquamira all have pretty well-defined lifespans. Plan conservatively, just in case conditions are a bit more rugged than you expected. If your shoes usually last 700 miles, consider replacing them around the 450-500 mile mark. If they fall apart earlier than expected, and you're not within striking distance of a town, you'll be very glad you planned to replace them as soon as you did!
    • Consider leaving a sewing kit in your resupply cache (if you're not already carrying one in your backpack).
  • Laundromat. For the vast majority of human history, washing machines didn't exist. Yet, we've usually avoided living in total squalor. I won't claim that "some soap and a sturdy plastic bag" gets your clothes quite as clean as an Electrolux, but it certainly does the job. At the bare minimum, it gets rid of the uncomfortable sweat crust that builds up on your socks - and let's be honest, that's the biggest reason you want to do laundry in the first place. Two caveats apply here though:
    • Use biodegradable soap, and using as little of it as possible. My first attempt at trail laundry involved Dr. Bronners, and wasn't particularly successful in getting my clothes clean. My second attempt involved beefier soap, but it turned out to be really concentrated and probably wasn't the greatest for God's creation. The search continues for the perfect backcountry laundry soap. If you use one and are happy with it, shout it out in the comments so the rest of us can learn!
    • Don't do your laundry next to a stream. Instead, get water from a water source (either a large jug in your cache, or a nearby stream), and do your laundry "Dundo-style", as Ray Jardine would say, far away from the water source itself. We don't want to contaminate a stream with a mixture of soap scum and foot funk. If there's no nearby natural source and you need to cache water, I'd expect to use about 2.5 gallons to pre-rinse, thoroughly wash, and rinse a typical hiker's load of socks/underwear/bandana.

The overriding message is this: a little extravagance goes a long way. There's no need to go ultralight or minimalist when it comes to caching supplies. It's okay to have a little more than you need. You need a little flexibility to account for unknowns on trail, and you need a mental break for the austerity that wilderness backpacking demands. Treat yourself. It's okay. And you're still using a lot fewer resources (and money!) than you would be on an in-town resupply stop.

We can't completely emulate the comforts and conveniences of town with a resupply cache. But with a little creativity, we can get pretty close. And it's certainly a far cry from the "barely enough food, crammed into a USPS flat rate box" sadness of an isolated post office in the middle of nowhere. Unlike that sad, pathetic maildrop, Town-in-a-Box is designed to be sustainable indefinitely. It's possible to hike for weeks or even months at a time without ever visiting a town, using the Town-in-a-Box strategy.

One final tip: trying to organize many caches at once can be daunting. Spreadsheets are essential to keep it all organized. And, unless you’re buying in bulk, you might find it easier to go shopping for just one or two caches/resupply legs at a time. That will help you increase the variety of foods that you put in your cache (different foods will look good to you on different days) and avoid the dreaded “aw-screw-it” apathy when you’ve been at the grocery store for two hours already and your cart is overflowing.

3. Stash your cache

Critter Safety

The most important consideration when caching supplies in the backcountry is keeping your food absolutely 100% safe from critters. It's your only way of staying fed for the next week. And, given that your food will be stored unsupervised, it needs to be very, very critter-proof to keep a fed bear from becoming a dead bear, or to stop determined squirrels from gnawing their way inside.

I use a three-part safety system to ensure that my food will be absolutely secure:

  1. Store all food and smellable items in odor-proof bags
  2. Put everything inside a hard-sided, IGBC-certified bear-proof container
  3. Bury the whole business 8-12 inches underground

The idea is this: if a critter can't smell my food, it won't have any reason to try and dig up my box. And if it does randomly dig up my box, it'll find it completely impenetrable. And the fact that it's well-buried means that a curious animal won't randomly stumble upon it, swat it around a bit, or run off with it. Put simply, with this method I can be 100% certain that my cache will be waiting for me when I get there, completely undisturbed.

Let's dig into each of these elements:

1. Odor-proof bags. The name of the game here is a fleet of OPsaks - heavy-duty, resealable plastic bags designed to be 100% air and odor-proof. In the past, I’ve been a little skeptical of OPsaks. They don't hold up very well to the rigors of backpacking. Backpackers tend to abuse OPsaks - opening them and closing them constantly, crumpling them up, jamming them to the brim with food. After a week or two of this harsh treatment, the seals start to break, seams begin leaking, and suddenly your odor-proof bags aren’t very odorproof anymore.

On the other hand, OPsaks excel at keeping things fully air and odor-proof in static environments like a cache. Just buy fresh bags, put everything with a smell in them (including medication, chapstick, toothpaste, and any other smellables), and put them inside your cache boxes. Not only will they contain odors, but they'll keep your chips and cookies and other food fresh for weeks. You can even pre-open and crush a bag of chips (to save space), and after a month in an OPsak, they'll still be perfectly crunchy.

2. Hard-sided, IGBC-certified container. The honest truth is that 95% of the classic backpacking terrain in North America is black and/or grizzly bear terrain. Everybody knows that the Sierra Nevada and Yellowstone are bear habitats. That much is obvious. It's far less obvious that large parts of Florida, the ranges of the mid-south (Ouachitas/Ozarks), and even many of the desert ranges of the Southwest (Superstitions, Mazatzals) are bear habitats too - but they are! Unless you have solid and bulletproof information that you’re not in bear habitat (e.g. Catalina Island, where bears absolutely, definitely do not live), you should assume that you're in bear territory, and plan accordingly.

It is therefore imperative that a cache be fully bear-proof. That means that it must be in a sturdy, hard-sided container (no Ursacks!). But more than that, the container should be certified as bear-resistant by the Interagency Grizzly Bear Committee. An IGBC-certified container is a legal requirement for unattended food storage on many public lands. Not all hard-sided containers are IGBC-certified. Most coolers, for example, are not - and even if they are, they must usually be bolted or padlocked shut in order to be in compliance with regulations. A full, constantly-updated list of IGBC-certified products can be found here.

Even in the tiny minority of places where bears do not exist (low-elevation deserts, certain islands), you should take basically the same precautions. On one occasion while hiking in the low desert, I decided to use 5-gallon buckets instead of ammo boxes. To my horror, one of the caches was nearly gnawed through by a desperate rat! Not only did some poor rodent have to visit the dentist because of my actions, but it very nearly got into all my food, which would have been disastrous. The same thing applies with water jugs - animals will smash, bend, and otherwise mutilate gallon jugs of water in order to get some of that precious liquid. So even when you're not in bear country, it's wise to take the same precautions anyhow, just to avoid problems with other wildlife.

What kinds of IGBC-certified containers work well for caching? There are a few contenders:

  • Bear Canisters. There's an obvious advantage to bear cans - many backpackers already own them. Despite that, though, I find that bear cans aren't actually ideal for caching. They're simply too small. Any PCT hiker who's tried to cram 8 days of food into a bear can in the Sierra will attest to the fact that they tend to fill up very quickly. And once you start adding town food, replacement gear, and all your other Town-in-a-Box supplies, you'll find that a bear can probably isn't big enough.
  • Coolers. Most coolers are not IGBC-certified, but a few are. If you've got an IGBC-certified cooler, it can work well, as long as it's padlocked or bolted. The IGBC product list will generally detail the correct way to use it. But if you're planning a long trip with multiple resupply caches, those roto-molded coolers quickly become economically impractical.
  • Ammo Cans. Fortunately, there's one product on the IGBC list that's cheap and can be purchased en masse - the Army-surplus ammunition box. Ammo boxes themselves are NOT IGBC certified, but with a couple easy modifications - a couple lengths of U-channel bar and some bolts, along with a razor saw and a drill with carbide bit - you can make a huge, fully IGBC-certified container at home. You can expect to pay maybe $15-25 per ammo box, plus a couple bucks for the supplies needed to modify it. They come in a variety of sizes - commonly identified by the size of the ammunition stored within. Larger numbers correspond to smaller boxes. The "standard" 50-caliber box is too small to do Town-in-a-Box - it barely fits two days of backpacking food! The 40mm box is sufficient for about 3 days of food, plus Town-in-a-Box. The big boy, the 20mm box, can pretty comfortably hold up to 8 days of food, plus Town-in-a-Box. It's my preferred choice for most caching.

3. Bury your cache underground. You'll probably want to bury your cache anywhere that there are large animals capable of dragging away your food cache. Burying it keeps it to be out-of-sight and out-of-mind for critters. Yes, animals can dig, and maybe they'll be curious about your freshly-dug hole. But if burying our poop 6-8 inches deep is sufficient to keep animals from messing with it, then burying our odor-proof food cache least that deep (I recommend 8-12 inches) will probably be similarly effective. And I probably don't need to remind you that poop is not odor-free! Except mine, of course. :)

In order to dig a proper hole, you'll need the following:

  • A good shovel. We're talking a real shovel, not your poop trowel. Even with good site selection, you'll invariably have to dig out a big rock or cut through a few roots. That’s a job for a shovel that you can really stomp on and use some force with. Thankfully, there's no need to leave the shovel at your cache. Once you've placed your cache and filled the dirt back in the hole, it's easy enough to dig back up with bare hands - even after a couple months of letting the dirt settle and harden.
  • Plenty of patience. Your hole will need to be at least twice as big as you think. The problem is, we dig round holes, and our ammo cans are rectangular. So we'll need to dig a lot deeper and wider than it appears at first glance. Be patient, and give yourself plenty of time to complete the work.

It should be noted that there are some drawbacks to caching underground - namely, the LNT impacts of digging a hole. In most cases, I consider those drawbacks to be "worth it" in the name of greater food security. There are certain exceptions - most notably in truly arid desert environments where there aren’t bears or any other animal large enough to mess with a IGBC-certified and smell-proof container.

And keep in mind - caching is only recommended on super obscure/DIY routes, not on the Pacific Crest Trail. One hole in the middle of the woods isn't a big deal to me, provided that it's dug in a sustainable location and that you re-landscape the area to a natural appearance afterward. But if you've got a thoughtful, contrary opinion on the matter, I'd love to hear it in the comments. 

Human Safety

Two-legged critters are more likely to cause problems for your food cache than the four-legged critters are. Mere weeks before I began my 2020 Greater Yellowstone Loop, the treasure of Forrest Fenn was finally found. For years, it was strongly suspected to be in the Greater Yellowstone Ecosystem - not too far from where I was burying caches! Needless to say, I was relieved that fewer people would be poking around random trailheads in the GYE, looking for buried treasure.

On another occasion, I neglected to hide a resupply cache underground, as it wasn't in bear country. But I hid it a little too close to town, in the litter-and-creosote wasteland where people ride roughshod on ATV's. When I got to my cache location a few weeks later, my bucket had vanished without a trace. I hope the thief really enjoyed those crushed potato chips and Teddy Grahams.

The point is this: curious or malevolent humans can pose a slight risk to your cache in the backcountry. Here are a couple security tips I've learned the hard way:

  • Avoid well-traveled areas. It's probably not a good idea to cache in the vicinity of a busy trailhead. Maybe, if you've got a couple mile roadwalk down a dirt road away from the main road, go half a mile down the dirt road and then cache well off the road in a place only you can find it. GPS tag the location and take a picture to be certain!
  • Seriously, bury your stuff underground. People are lazy, and on the odd chance that they spot your hole, will probably lose interest if they dig down a few inches and find nothing.
  • Disguise your cache site as a dog grave. I like to print off a photo of a random poodle from the internet and write "RIP Fluffy" on it. Bury it a few inches down in the hole, so if anybody starts digging, they'll promptly find the epitaph and stop. Nobody wants to dig up a rotting pet carcass.

Proper Site Selection

As alluded to earlier, it's important to choose a good cache burial site. Here are a few tips I've picked up:

  • If you wouldn't poop there, you shouldn't cache there. It's easy to get "lazy" with your caches - a fully loaded Town-in-a-Box will be pretty heavy, and hikers aren't exactly known for their upper body strength. But take the extra time and walk a few tenths away from the road crossing or trailhead, so you're not in/near a high-foot-traffic area. The LNT standard of 200 feet from trails/roads/water is a good start, but I'd probably go with 200 yards rather than 200 feet in this case. A large cache hole is a bigger impact and more unsightly than a small cathole, so it's best to cache well away from where other people will be venturing - both for the security of your cache and out of respect for other visitors
  • Lush and green is your friend. I like burying my cache in areas of high soil moisture. In addition to keeping your stuff nice and cool, the land will recover more quickly in a greener, wetter environment. On a Greater Yellowstone Loop, my latter caches - which had been buried for close to 2 months by the time I reached them - had little green shoots already growing out of the dirt I'd overturned. Within a couple years, the site will become indistinguishable from its surroundings.
  • Flood plains offer easy digging. Even in areas that aren't particularly rocky, there are rocks everywhere. And when you start digging holes, you'll find more rocks than you ever knew existed. I've found that flood plains of creeks and rivers make for the best digging - there are simply fewer rocks there. If it's an area that only floods in the springtime, and you're caching in the summer, you probably don't have to worry about floods sweeping away your Teddy Grahams. Just make sure it's a broad floodplain so you're not caching too close to the watercourse itself.
  • Disguise your burial site. After you finish burying your cache, grab some leaves/rocks/forest duff and try to make your site look natural. There will still be a leftover dirt pile nearby, of course, but you can disguise that too with a little additional landscaping. I generally leave two small sticks atop the burial site in an L-shape - recognizable enough to tell me exactly where to dig, but subtle enough not to attract attention from strangers who happen to stumble across the site.
  • Tag your cache site with GPS. After a few months, memories fade. Take a photo, save the exact GPS coordinates on your phone, and make sure to send the coordinates to your emergency contact. Perish the thought, but if the worst case scenario happens and you disappear, SAR can dig up your cache and determine whether you made it this far or not.
Green and lush. Any trace of the burial site will quickly disappear in this environment.


4. Enjoy your cache

This is the fun part. There’s absolutely nothing better than rolling up to your cache and being able to immediately dive head-long into a large pile of food and drink. You don’t have to wait for a ride or slow service at the restaurant. And, if you’ve done Town-in-a-Box right, you’ll be able to stuff yourself to the gills.

A few tips for maximum effectiveness:

  • Plan ahead. I generally budget about three hours for my cache activities, including a healthy dose of relaxation. Given that caches are usually relatively close to a road of some sort, I try not to get there too late in the day - otherwise I’ll have to camp close to the road and/or night-hike. I find that early afternoon is best. After all, I’ve got to do laundry, and I want it to dry in the warm sunshine.
  • Start charging ASAP. Unless you’re carrying a solar charger and/or auxiliary battery in your backpack, the cache is your only opportunity to recharge your phone or other electronic toys. Sit down, take a couple swigs of pop, and then plug your phone into your battery bank right away. By time you’re done with your “town chores'', the phone will be ready to go. 
  • Do all of your town chores. It can be surprisingly hard to keep track of all the things you have to do at a cache - be it repairing ripped gear, doing laundry, or swapping out gear. I suggest making a list ahead of time so you don’t forget anything. There’s nothing worse than getting five miles down the trail and realizing that you could have jettisoned your microspikes at the last cache - or worse, that you forgot your mosquito headnet for this next section.
  • Relax. Long-distance hiking may be a leisure activity, but darned if that hobby doesn’t feel like work sometimes, particularly when you do it all day every day. It’s okay - necessary, even - to just hang once in a while. A few ideas to increase the enjoyment of your cache day:
    • Watch a show on your phone. I won’t tell if you cry when they shoot Old Yeller. 
    • Do a little fishing. Roads tend to follow rivers, which means there’s a decent chance your cache site isn’t too too far from water. Pick up a cheap spinner pole at a thrift store, hide it near your cache box, and spend the day pulling little brookies out of the stream. 
    • Play a game. Again, the thrift store is your friend. Wade past the 91 copies of Trivial Pursuit to find a board game, leave it in your cache box, and enjoy settling Catan or whatever.
  • Re-seal everything properly. If anything, a cache is a bigger bear magnet after it’s been emptied. You’ve just swapped out food for your rotting trash, which is far more pungent than the food was. Leave everything smellable sealed back inside your OPsaks, safely locked in the bear-proof container, and re-buried.


5. Retrieve your cache

It’s vitally important to pick up a cache promptly upon completion of your hike. If it’s not picked up, it’s mere litter, and negates all the good work you did to make it sustainable and critter-proof in the first place.

You will want to take some time, after you dig up your cache, to re-landscape the site to a fairly natural appearance. In addition to filling in the hole, I recommend spreading forest duff, sticks, and leaves. Try to spread around the inevitable residual dirt pile, and generally do your best to make it look like you were never there - in other words, leave no trace! You won’t be completely successful in this regard, but if you do your best, the site will largely recover within a year or two.

To reiterate - site selection matters. If you’re digging in a drier place, or one with sensitive vegetation, your impacts may last decades. If you’re digging in a green, lush place with quick-growing plants, the impacts will be more short-lived.

 *********************************************************************************


Food caching isn’t always - or even usually - the best or most appropriate choice for backpackers. But on extremely remote, DIY routes, it’s a useful part of a hiker’s toolkit. There are certainly many approaches to take to caching. In this guide, I could certainly be accused of overthinking it. But I’ve aimed to get hikers thinking outside the flat-rate box - and hopefully to inspire them to create a caching strategy that works well for them. Get out there, experiment a little, and report back! I’d love to hear other perspectives - please share your experience in the comments or ask a question!

Backcountry top-loader washer in action. Put the lid on before agitating! I don't recommend a plastic bucket anymore - a rodent nearly gnawed through one of my buckets on this trip.


Sunday, April 18, 2021

Deseret Hiking Route - 2021 Updates are Available

I am happy to announce that the second generation of the Deseret Hiking Route (DHR) information pack - Version 2021 - is now available. Its updates represent a significant improvement over the old route, in my opinion. They were developed as a result of recent hiker feedback, along with my own scouting missions and another year of staring at maps. Highlights of the updated route include:

  • Better, ground-verified route across Boulder Mountain (Section 3).
  • Large-scale re-routes in the Pocatello area (Section 9), resulting in easier logistics, more water, more snacks, and less pavement.
  • Several improvements in the Pioneer Range (Section 11) - more trail, less road, and more beautiful mountain scenery.
  • Clarified and greatly expanded GPX file (though not a full track!)
  • Many new alternate routes, many of which may eventually become the new Red Route, depending on hiker feedback.
  • Multitudes of "little improvements" here and there - mile markers on the maps, simplified naming conventions, dozens of new data points, etc.
  • New, less confusing verbiage around Public (for anybody) vs Private (gotta do your trail work!) resources.
This is also a good place to say thanks. I've been floored by the hiking community's enthusiasm for the route thus far. For those who've taken the time out of your day to read the guide, to ask a question, or suggest an update... thank you!

And if you've been on the fence about the DHR, now's a great time to revisit the question. If you've been meaning to ask for the resources but keep forgetting, it's time to drag that email out of your drafts folder and send it. If you've been procrastinating your trail work day, I encourage you to call your local hiking club and ask about opportunities. As spring turns to summer and our mass vaccination campaign continues at full tilt, there will be more and more opportunities to give back to the trails that we love so much. Seize the day!

 

What is the DHR?

The Deseret Hiking Route (DHR) is a roughly 1,000 mile route through the heart of the American West. It begins on the Utah/Arizona border and runs north through Utah and southern Idaho before terminating in the Sawtooth Mountains of central Idaho. The DHR is a route chock-full of world-class beauty and offers the prospective hiker the opportunity to explore amazing and oft-overlooked landscapes. The DHR is designed to be hiked as either a standalone route, or in conjunction with the Arizona Trail and Idaho Centennial Trail from Mexico to Canada. The DHR is completely unmarked and undesignated by any state or federal agency. For the experienced long-distance hiker, one who takes responsibility for their own route choices, personal safety, and happiness, I can think of few extant routes that can deliver the kind of satisfaction that the DHR offers.









 

Thursday, March 18, 2021

Re-thinking the Personal Locator Beacon

 

I'm no Luddite, but I must admit some misgivings about the ubiquity of technology in 21st-century life. When friends check their phones while we're hanging out, off in electronic la-la land, it bothers me. I'm not completely comfortable with the degree to which large tech companies can reconstruct our lives simply by snooping on our browsing habits, location data, and more. And, having just begun a job, bought a car, and signed a lease, I'm struck anew by how necessary - yes, necessary - it is to have an email address and access to electronic communication in the modern age.

Backcountry adventuring is not insulated from this broader societal trend. It's not a coincidence that the venerable Halfmile PCT maps are no more, "replaced" by an unjustifiably expensive set of Trails Illustrated maps. In reality, they've been replaced not by the TI maps, but by the Guthook PCT app, as well as the digital versions of those TI maps on Gaia GPS. Hikers who are increasingly steeped in a digital culture increasingly turn to digital resources to meet their navigational needs. We can rail against it all we want (and if you catch me in a offline/non-diplomatic moment, you may hear that screed), but like it or not, the tendency toward an all-digital navigational approach seems inexorable.

Navigation isn't the only area of the modern outdoor experience that's been digitized. In recent years, I've had more than few hikers tell me that it's dangerous - irresponsible, even - to not carry a personal Personal Locator Beacon (PLB) or similar satellite communicator in the backcountry. On one memorable occasion, a fellow CDT hiker chided me for not carrying a PLB. He told me that a PLB was required equipment, but a paper map was not. If his Guthook app failed, he could simply push his SPOT device and wait for rescue. This line of thinking is obviously terrible and a "special kind of stupid" - but unfortunately all too frequent.

I've owned a Personal Locator Beacon for 6 or 7 years now - long enough that I've had to renew its NOAA registration and really should have replaced the battery already. But in all that time, I've always treated it with a barely-restrained degree of contempt. I've regarded it as an intrusion on my life - an electronic "leash", as my friend Paul would say. I bring it only when there aren't any other options for rescue in case of injury - namely, when I'm hiking both (1) alone, and (2) off-trail. And the whole time, I grit my teeth and resent the fact that it's sitting in my hipbelt pocket, tying me to the outside world with invisible cords. I bring it mostly for my family's sake, and complain bitterly to myself about it.

The only non-gory bear attack photo I've got. This was shirt #2. It was soon soaked with blood as well. The wince says it all.

But I think my (admitted bad) attitude is starting to change. Two incidents in the course of the past year have impacted my thinking:

1) In 2020, I was attacked by a grizzly bear. I was able to bandage up my wounds and hike out, but had things happened just slightly different, I would have needed SAR to rescue me. If the bear had slashed my leg instead of my chest, I wouldn't have been able to walk. If I hadn't been able to control the bleeding, I would have needed medical attention immediately in order to survive. I didn't need my PLB, but in any other scenario, I probably would have.

2) In 2021, I took a fall while hiking in a desert canyon and shattered a bone in my heel. Thankfully, it happened within a couple hundred yards of a paved highway, and I was able to crawl up to the road where a good Samaritan picked me up. Had the fall occurred anywhere else, I would have required rescue, as I couldn't walk at all. In this desert environment, an inability to move coupled with a lack of water sources could have led to a grim outcome.

I don't consider myself particularly accident-prone. I generally make fairly conservative decisions when it comes to risk in the outdoors. Put simply, I try to do everything within my power to ensure that I never have a medical emergency in the backcountry. And yet, accidents happen - twice in a year, in my case. Without a PLB, either of the scenarios could have proved fatal, had circumstances played out a bit differently.

Crawling up this rockpile/slope on hands and knees: not fun.

What then, of the PLB? I'm beginning to appreciate it, rather than despise it. I turned 30 this year. The youthful illusion of invincibility is starting to wear off. And after my brushes with injury in the past year, it's tough to claim with a straight face that it "won't happen to me". And if it can happen to me, it can happen to anybody. It doesn't even need to be an injury - take a simple case of food poisoning in the backcountry. In deep wilderness, an inability to move can quickly become an inability to survive. 

I've made my peace with the personal locator beacon. I may not love it, but I certainly don't hate it anymore. As part of my re-thinking of the PLB, here are a few key considerations I've dwelt on:

1. The Right Device

Not all emergency-use satellite communicators are created equal. I won't try to create a full buyer's guide here, but just sketch out some general categories. From simplest to most complex:

  • A "true" Personal Locator Beacon. A classic example is the ACR ResQLink. The only thing it can do is send out an SOS signal and transmit a location. On the other hand, the signal on a true PLB is far stronger than that of more feature-rich devices, and it's paired with the most robust satellite network. It's free to register your beacon with NOAA, and if you ever need to actually activate your beacon, the manufacturer will generally replace it for free afterward.
  • A Satellite Messenger. A multifarious category, encompassing a wide range of features and options. Canonical examples include the SPOT devices or the Delorme inReach. Some of these messengers allow users to send a handful of different pre-set messages, from "daily check-in", to "please send help", to full-blown "SOS". Others, particularly newer models, allow for free-form text messaging and two-way communication. These devices usually require a monthly service plan or charge on a per-message basis. Some models have their own keyboards and screens, while others are designed to serve as an accessory to the smartphones that most people already carry. 
  • A Satellite Phone. It's exactly what it sounds like. One well-respected brand is Iridium. Not too many backpackers find themselves in need of a sat phone, though exceptions apply for commercial guiding operations, or long stretches in extremely remote areas of the globe (say, the polar regions). Sat phones are expensive, and so are the service plans.

Which is the right device for you? Tough to say, as it depends on how many features you want, and whether you're willing to pay for them. I've carried a barebones PLB for years, as I wanted to be unable to communicate with the outside world except in dire emergencies - that is, I wanted my electronic leash to be as long as possible. But my experiences in the past year have taught me that there's quite a bit of gray area when it comes to urgent medical needs. Though I was in little danger of dying in the aftermath of either of my recent incidents, it would have been enormously helpful to be able to contact medical help without them assuming that I was in need of a full-blown chopper rescue. When I broke my foot, being able to contact the county sheriff and have a couple folks help me limp out would have saved me a truly excruciating hour of crawling on bloody hands and knees over boulders and up steep slopes - and it might have made the difference in preventing further injury.

On the other hand, I'd hate to shoulder an expectation that I'll contact friends or family (or work - shudder!) while I'm in the backcountry. Part of the reason we head into the wilderness is to put our ordinary daily concerns on the back burner. Would having a more advanced device - capable of check-ins or 2-way messaging - compromise the reason I was out there in the first place? To some extent, yes. But I'm starting to wonder if the compromise might be worth it. I'm not there yet, but I think my attitude might be changing.

2. The Right Mindset

All that said, it's possible that carrying a PLB doesn't actually make for a safer trip. Consider again the fellow who told me he was carrying a PLB instead of paper maps . Instead of learning the navigational skills needed to survive and thrive on the often-poorly-marked CDT, he was using the PLB as a crutch. The presence of a PLB was almost certainly making his trip less safe. If safety equipment (be it a PLB, avalanche airbag, climbing helmet, etc) emboldens us to take risks that we wouldn't ordinarily take, then that safety equipment is useless at best and counterproductive at worst.

The best safety equipment we have is our brains. It's not exactly a profundity to say that it's far better to avoid a dangerous situation than to be bailed out of it by our safety gear. I try not to let the presence - or absence - of a PLB impact my decision-making. If I'd be more comfortable navigating that sketchy arete in the rain with a PLB, that's my brain's way of telling me that I'm making a bad decision.

3. The Right Message

So, how do we convince skeptics (like me) to bring a PLB? So often, our arguments in favor of PLB's revolve around guilt and shame: "you're irresponsible for not bringing one", or "what will your family say?" To me, that's the wrong approach. These arguments only put someone on the defensive and further entrench an anti-PLB mindset.

To me, the best way to encourage the use of PLBs is instead a message of liberation: "A PLB increases your odds of a good outcome, if something bad happens to you". A PLB is relatively lightweight, relatively compact, and can be stashed in a hipbelt pocket (for easy access!) and forgotten about unless it's needed.

Folks who don't carry a PLB aren't generally irresponsible. They simply have a different assessment of the costs versus benefits of carrying one. I've got a lot of sympathy for that argument. I used to agree. But after having experienced a couple of backcountry accidents and seeing the the costs first-hand, I'm starting to re-think my cost/benefit analysis when it comes to PLBs. And hopefully my recent experiences will help others do the same.

All photos in this post taken near the scenes of the crimes. Unpleasant things happen in pretty places!

Saturday, December 26, 2020

2020 - In Review


Well, that was a trainwreck.

Strictly speaking, 2020 wasn't "the worst year ever", or even "unprecedented". Such proclamations are most-often voiced by pundits with a poor grasp of history and a flair for the overly dramatic. There's no denying this was a miserable year, but it probably doesn't stack up to 541 (devastating famine across Europe and Asia after an Icelandic volcano threw a bunch of ash into the atmosphere; the Plague of Justinian) any of the years in the late 1340s (a third of Europe and a quarter of Asia killed by the Plague, Version 2.0), 1918 (a way deadlier pandemic, plus a brutal World War), or 1945 (wrap-up to the deadliest war in history and the deadliest genocide in history, the US nuking Japan, and the beginning of the Cold War)

But most of us weren't alive in 541, 1348, 1918, or even 1945. And as a matter of lived-experience, 2020 sure has been rotten. So before we wish it a hearty good riddance farewell, here's a brief review, as it pertains to backpacking adventures.

Gear:

  • Pairs of shoes:5
  • Zippers split:2
  • Zippers repaired: 2
  • Amount of Cuben tape used: way too much
  • Tents used:2
  • Tents found to be leaky: 1 
  • Tents used, in spite of being leaky: 1
  • Pairs of microspikes lost: 1 (it's the bear's fault)
  • Compasses lost: 2 (not the bear's fault)
Trips:
  • Long-distance hikes: 2 (Florida Trail; Greater Yellowstone Loop)
  • Medium-length backpacking trips: 1 (Ouachita Trail) 
  • Short backpacking trips:7
  • Miles hiked: 2,800+
  • States visited:9
  • National Parks visited:2
  • National Forests visited: 16
  • Wilderness Areas/WSA's visited: 19
Highest/Lowest/Fastest/Slowest:
  • Highest elevation: 13,448' (Gilbert Peak, Uintas)
  • Lowest elevation: sea level (Gulf Islands National Seashore, Florida Trail)
  • Highest point (metaphorical): Walking on the spine of the Tetons themselves
  • Lowest point (metaphorical): Oh crap, that's a grizzly
  • Longest full day, in miles: 27 miles (Florida Trail)
  • Shortest full day, in miles: 14 (trudging through the swamp on the Florida Trail)
  • Most consecutive days without seeing a human: 6 (Greater Yellowstone Loop)
  • Lightest packweight: 8 lbs (Florida Trail)
  • Heaviest packweight: 40 lbs (Greater Yellowstone Loop)
  Animal Encounters:
  • Gators seen: hundreds
  • Gators bellowing uncomfortably close to my tent during the night: 1
  • Gator problems: 0
  • Venomous snakes: 0
  • Dog problems: many
  • Jumped into the bed of a passing pickup truck to avoid a confrontation with a pack of unleashed and aggressive dogs: 2
  • Bears:11
  • Bears that didn't attack me: 10
  • Confirmed grizzly bears: 4
  • Confirmed black bears: 1
  • Mystery bears: 6 (too far away to tell)
  • Foxes that tried to sneak up on me: 1
  • Foxes that got pelted with rocks by a very ticked-off LarryBoy: 1
Human Encounters:
  • Shown overwhelming generosity by strangers: too many to count
  • Offered money by strangers who thought I was homeless:1
  • Given "trail magic": 2 
  • Given "trail magic" in a uniquely Florida style, by people who were proud of their regional and ethnic cultures and wanted me to feel welcome: 2
  • Hiker gatherings attended: 1 (pre-covid)
  • Randomly encountered friends in the middle of nowhere: 2
Camping:
  • Bag nights: 150+
  • Bathrooms slept in:1
  • Churches slept at: 2
  • AT-style shelters slept at: 4
  • Favorite campsite: stunning unnamed lake in the Beartooths
  • Least favorite campsite: mosquito-infested dystopian wasteland in the Bechler River area of SE Yellowstone
  • Cowboy camped: 0 (for the first time in many years!)

Previous years in review: 2019, 2018, 2017, 2016, 2014

In January, just after New Years, my good pal Blue Moon dropped me off at the the southern terminus of the Florida Trail. South Florida featured a full-blown swamp walk, beautiful oak and palm hammocks, and the occasional death-defying roadwalk.


Around the beginning of February, I reached north Florida and took a left turn, now heading west toward Pensacola. Highlights included the incredible Suwanee and Aucilla rivers. The weather took a turn for the worse, with regular drenching rainstorms rolling through every three days or so.


I finished up the Florida Trail during the first few days of March, ending with a beautiful walk along the beach to a historic US Army fort on the Gulf of Mexico. 

After finishing the Florida Trail, I got on a plane and headed to Arkansas to hike the Ouachita Trail. There was a minor buzz going on - an emerging virus was apparently making its way from China to the rest of the world, and some experts were saying that it was a concern. 

A week later, when I emerged from the woods in Mena, AR, the world had gone crazy. Hand sanitizer and toilet paper were nowhere to be found. Most states still had single-digit case counts, but it was clear that this coronavirus was going to be a bit of a problem. I hurriedly jumped on a train to Phoenix, to start the Grand Enchantment Trail. I figured being in the woods was for the best right now.


Things were changing fast. After just four days on the GET, I realized that continuing a long-distance hike was not a good idea right now - hitchhiking, passing through rural, vulnerable communities, and arranging transportation before/after a hike just wasn't responsible. Before things got any worse, I hopped on a plane and headed back to Michigan, where I could stay for a while.


In April, I took a quick hike on the North Country Trail in Michigan's Manistee National Forest, not too far from home.

In late May, I came to grips with the fact that my planned PCT hike wasn't going to happen. Covid-19 wasn't going away any time soon. Rather than rotting indoors however, I planned a long-distance hike that would be Covid-responsible - no transportation, no hitchhiking, no towns. I would drive to the trailhead, walk in a circle, and cache my food beforehand.

I headed west, doing a few warm-up hikes. First up was an exploratory jaunt on Boulder Mountain, scouting a re-route for the Deseret Hiking Route.

In June, I did a quick trip through the Tushars of south-central Utah, summiting all of the 12,000-foot peaks in the range.


Later that month, I did a pair of trips in the Uintas - one in the western part of the range...


 ...and one right along the spine of the range, the main Uinta crest.

All the while, I was living that #crappybeatupsubarulife, avoiding towns and sticking to wild places.

On the first of July, I began a Greater Yellowstone Loop near West Yellowstone, MT. I trudged through plenty of snow in the Tetons, but the views made it all worth it.


The Snake River and Wyoming ranges were slightly less spectacular, but still filled with beautiful alpine flowers. 

I had picture-perfect weather in the Gros Ventres, ideal for for walking the crest and recently-glaciated shelves.

The Absarokas, true to form, were wild, rugged, and full of grizzlies, one of whom objected to my presence.

The fine hospital staff in Cody, Wyoming stitched me up and sent me on my way. It took a few weeks before I was healed up enough to continue the route.

In August, I resumed the route, passing through the Beartooths, still one of my favorite ranges of all time.

I sashayed through the northernmost Absarokas, and later passed through the Gallatin Range, choked in thick smoke by wildfires burning on the West Coast. 


The trek concluded with a jaunt through the Madisons. I completed the loop near West Yellowstone on the last day of the month, just as the season's first snowflakes began to fall. 

In September, I did a short jaunt into the northern reaches of the Wind River Range...

...and celebrated my thirtieth trip around the sun with a quick overnighter in the Wasatch.

Spot the moose!

I didn't get out too much for the rest of the year - car trouble and the practical realities of re-establishing myself after a couple of years on the road played a role - but I anticipate getting out a lot more in 2021, particularly if and when coronavirus dies down due to vaccination.

A Year of Failure - Kind Of...

I originally intended to do four long hikes in 2020 - the Florida Trail, Ouachita Trail, Grand Enchantment Trail, and the Pacific Crest Trail. Of the four, I only successfully completed one. I completed the Florida Trail, and quit the Ouachita a couple days early because the weather, and the upcoming forecast, combined to make it a bit miserable. I don't regret quitting it.

The Grand Enchantment and Pacific Crest trails are a different story. I quit the GET after 4 days due to the worsening Covid-19 situation, and my PCT hike was entirely a no-go. While I acknowledge that "having to skip a vacation with a fancy title" is pretty far down the list of coronavirus-related hardships, I'd be lying if I said I wasn't a little bummed about not being able to do those hikes.

Still though, I managed to see plenty of beautiful things, and I am happy with how quickly I changed gears to pull off a Greater Yellowstone Loop, which is probably the most beautiful hike I've ever done.

What's Next

The end of the year marks a significant shift in lifestyle for me. Since spring of 2018, I've been on the move constantly, never spending more than two months in a single place. I've probably walked 10,000 miles in that time, road-tripped across the country several times, and generally enjoyed adventuring full-time.

But living out the the back of a car or a backpack does get a little bit old. And as much as I enjoy adventure, it's not the only iron I have in the fire. Lord willing, I plan to return to full-time employment in 2021. I will have an apartment, rather than a Subaru and a storage unit. My outdoor trips will be measured in days, not months. And you can be sure that I'll document those trips on this blog as irregularly as I always do!

It's been a rough year, in some way, for just about everybody. But our hope isn't merely in the turning of the calendar to 2021, the promise of a Covid vaccine on the horizon, or the end of the malignant Trump administration. Our confidence is that whether it's the year 20, 202, or 2020, that the same God is in control and we can depend on his goodness... even when there's a bad-tempered bear heading our way.

Happy New Year.




Saturday, December 19, 2020

From Whence Did the Grinch Steal Christmas?


Like many children, I grew up reading Dr. Seuss's holiday classic, How the Grinch Stole Christmas. Seuss (also known by his birth name,Ted Geisel) spins the heartwarming yarn of an irascible hillside hermit who tries to steal Christmas from the neighboring town of Who-ville. But his heart "grows three sizes" upon learning the true meaning of Christmas, and he abandons his Grinchy ways, even sharing in the town's celebration himself.

When I got older and developed a quasi-obsession with mountains and wild places, I noticed that there really aren't that many places - anywhere on this planet - that fit Who-ville's locale as described in the book. I began to wonder - where exactly is Who-ville?

TL;DR: With a reasonably high degree of confidence, I believe that Glacier View, Alaska is the only plausible match for the fictional town of Who-ville.

Background

A crash course on the Grinch, in case your childhood was sad and stunted:

The Grinch, a grumpy green recluse, lives in a cave in the mountains north of a village called Who-ville. The Grinch's general misanthropy is manifest most overtly in his abhorrence of the Whos' annual Christmas celebration. Having putting up with their singing, feasting, and general merrymaking for "fifty-three years now", the Grinch decides, one Christmas Eve, to steal their holiday accoutrements while they're all sound asleep. 

After dressing up as Santa Claus and disguising his dog Max as a reindeer, the Grinch rides a sleigh down into town and, sliding down each chimney, systematically burglarizes the Whos' houses, stealing their gifts, foodstuffs, decorations, and Christmas trees. He's spotted only once - by a two-year-old, Cindy-Lou Hoo, who believes he's Santa Claus. The Grinch prevaricates, telling the child that he's taking the tree back to his workshop for repairs. He then dispatches her back to bed. 

The Grinch shoves the Christmas trappings up the Whos' chimneys and loads it all onto his now-overflowing sleigh. With much protestation, Max pulls the sleigh thousands of feet up to the peak of nearby Mt. Crumpit, where the Grinch plans to dump the cargo over the side of a cliff. Before completing his crime though, the Grinch pauses to observe the reaction of the townspeople, who are just now waking up and realizing that their Christmas has been stolen. But to the Grinch's horror, he hears not weeping, but singing! Despite their lack of gifts, decorations, or food, the Whos are celebrating Christmas all the same. The Grinch concludes that Christmas must mean "a little bit more" (though exactly what is not specified). His heart changed, the Grinch rides back down the mountain into town, bringing back everything he had stolen. The Whos magnanimously accept him, even granting him the honor of carving the rare roast beast.

Sources and Canonicity

Unsurprisingly, Hollywood has done several re-treads of the original Grinch story. Not all of them should be considered "canon", though. For example, How the Grinch Stole Christmas! (2000), starring Jim Carrey, contains an elaborate backstory for the Grinch's malfeasence featuring childhood bullying and unrequited love. None of this is even alluded to in the original. For the purposes of this analysis, we will take two sources as canon:

I see these two resources - and only these two - as canon because they're the only productions to which Geisel actually contributed. All other adaptations and remakes may be entertaining, but they're not authoritative.

Link to book text

Link to movie 

Observations

1. Who-ville is located in an anglophone country. We know this from Cindy-Lou's name, as well as the fact that the Grinch speaks English in rhymes and anapestic tetrameter - something that would be highly unlikely if Geisel were translating from another language. 

Source for illustrations

2. There are mountains to the north of Who-ville. The book states explicitly that the Grinch in a cave above and north of Who-ville. From the movie, we can see that the cave is located in the mountains.

3. At least 42 people live in Who-ville. Forty-two figures are visible, joined hand-in-hand, during the song that stirs the Grinch's cold heart.

4. Mt. Crumpit is located to the south of Who-ville. This is admittedly an inference, however it seems to follow naturally from the way that animated features are typically shot. We know from #2 that the Grinch lives north of town and we see him whizzing down to Who-ville (before he steals Christmas) going from left-to-right across the page/screen. This means that the camera is pointing east as he journeys south through the frame.

Source for movie stills
 

After stealing Christmas and begins climbing up to Mt. Crumpit, he continues to move left-to-right across the frame - presumably using the same camera angle. And upon his repentance and his return to town, he now moves from right to left across the screen - now going northbound. It seems that in all of the "travel" scenes, the camera is pointing east.


5. Mt. Crumpit towers over Who-ville by at least ten thousand feet. The book says that the Grinch climbed three thousand feet up the side of Mt. Crumpit, however the movie says ten thousand feet. It's certainly not wrong to say that you climbed three if you climbed ten, but it is wrong to say you climbed ten if you climbed three. Therefore, we defer to the movie on this point - ten thousand feet it is!

6. Mt. Crumpit lies within ~30 miles of Who-ville. The book says that it was a "quarter past dawn" when the Grinch finally made his getaway. The movie slightly contradicts this - a "quarter of dawn", meaning a quarter before dawn. In either case, the Grinch certainly couldn't get too far - perhaps a couple hours - before the Whos woke up and discovered that their Christmas had been stolen. 

So, with Max pulling the sleigh, how far could they have gotten? The answer, of course, is "almost nowhere" - ten thousand vertical feet in two hours is pretty much unthinkable for any wingless animal. However, to be charitable, we'll use typical dogsled speeds - 10-14 mph - and assume that the Grinch could have made it at most 30 miles. Sure, Max wouldn't be equal to an entire team of sled dogs, especially with his gigantic load. However, he certainly did have adequate motivation, in the form of the Grinch's cracking whip.

7. Who-ville has snow on the ground, in town, at Christmastime. This is shown in both the book and the movie. Using the Principle of Mediocrity,a sort of probabilistic argument used in speculative cosmology and philosophy, it makes most sense to assume that this is an ordinary year and that Who-ville generally experiences a white Christmas.

 

Analysis

Almost immediately, we notice that the story must be set in either the United States or Canada. There are plenty of places that speak English, but most of them don't have mountains high enough (i.e the UK) or Christmas snowfall at elevations where people live (i.e. Australia). We could consider nations like Pakistan, which certainly has mountain/climate factors working for it, but while English has official-language status and is widely spoken as a second language, virtually nobody speaks it as a first language - muttering to themselves as the Grinch does.

We therefore narrow our search to the US and Canada. A number of places look initially promising, but turn out to be duds. For example, Lone Pine, CA is out - though Mt Whitney towers more than 10,000 feet above town, it's rare that snow falls in the town itself. Farther north, wintertime snowfall continues to be a problem. Greenwater, WA lies within the requisite distance of Mt. Rainier, but once again, it doesn't typically see snow in the winter. Put simply, there are very limited number of towns where you can climb 10,000 feet in thirty miles and get wintertime snowfall at all elevations. For that, you have to go north - very far north.

Farther north though, towns become a lot more infrequent. The majority of the high peaks in the Canadian Rockies lie within vast areas of National Park land or de fact wilderness. The coast ranges of British Columbia are even more desolate - there are a few towns, but in all cases, the towns are a little too far away from the peaks, or are in the wrong direction. The ranges here run in a generally NNW-SSE direction, which means that the high peaks are either east or west of the towns, not south of them.

That brings us to Alaska. The land of the midnight sun is sparsely populated, but does have a few hardy hamlets worth discussing. Helpfully, many of the ranges in southern Alaska run east-west, which means that towns are north or south of the peaks. One of those ranges is the famous Chugach Range. It's one of the snowiest ranges in the world, and tops out at more than 13,000 feet.

Paralleling the Chugach to the north is the Talkeetna Range. In between the two ranges flows the Matanuska River, paralleled by the Glenn Highway.  There's a tiny town along this stretch of highway - Glacier View, Alaska.

All maps via Caltopo

Glacier View lies at the foot of the huge Matanuska Glacier, at an elevation of about 2,400 feet. Its economy is based around the tourism industry - local businesses include a pizza parlor, zipline facility, and several lodges. The population was 234 as of the 2010 Census, though that number undoubtedly includes some people who live miles away from town, but are nonetheless classified as part of Glacier View for census purposes. Glacier View is 26 miles NNE of Mt. Marcus Baker, the best candidate for Mt. Crumpit. The town isn't a tightly-clustered idyllic village like Who-ville is - but hey, we're applying critical analysis to a Dr. Seuss book. You can't have it all.

Glacier View is furthermore the only eligible town anywhere in the US or Canada that I've been able to find, despite hours upon hours of pouring over maps. If anyone has an alternate candidate that fits the evidence, please let me know!

via Google Earth

There are two candidates for Mt. Crumpit in the Chugach:

1. Mt. Marcus Baker. Marcus Baker is the highpoint of the Chugach, at a staggering 13,176' above sea level, and 10,700' above Glacier View. By Alaska mountaineering standards, Marcus Baker is looks like a benign climb via the NNW approach - from Who-ville - and features a sheer drop-off on its south side. 

2. Mt. Thor. Thor has a cooler name than Marcus Baker, but that's about all it has going for it. Thor tops out at 12,251 feet above sea level, or about 10,100' above Glacier View. But in contrast to Marcus Baker, Thor's north (Who-ville) side is guarded by some seriously nasty-looking cliffs. Even with the strength of ten Grinches plus two, Thor would have been a grueling mountaineering objective - too much for the Grinch and Max, weighed down with many tons of Christmas trinkets. Mt. Thor is also another two miles farther from Glacier View than Mt. Marcus Baker is. For these reasons, I believe we can safely discard Mt. Thor in favor of Mt. Marcus Baker.

As a bonus, Marcus Baker has a more gradual north slope and a sheer drop-off on its south face, matching the description in the book and movie.


Conclusion

I was surprised at just how few Who-ville candidates there were. Peaks reaching ten thousand feet above sea level aren't exactly uncommon - but peaks that reach more than ten thousand feet above their surrounding terrain sure are. And as we get farther north, those immensely-tall peaks become less common, as glaciation erodes them quickly. And even if they do exist, there's probably not a town nearby.I guess that Glacier View is just special. If I were part of Glacier View's tourism council, I'd certainly promote my town as the Real Who-ville!

Thanks for joining me on this silly, fun excursion. It's been a difficult year for many people, and in such a year, it's particularly important to stop and celebrate our traditions, our families, and most importantly, the birth of Christ our savior.

Welcome Christmas, bring your cheer to all Whos, far and near. Christmas day is in our grasp, so long as we have hands to clasp. Welcome Christmas, while we stand, heart to heart and hand in hand.

Merry Christmas.