Forest Road NF-1509, Larch Mountain

[View Larger Map]

I need to set the stage for this post a bit, since we're visiting an area that's likely unfamiliar to most people in the Portland area, despite being fairly close to the city and very close to major tourist spots in and around the Columbia Gorge. Larch Mountain, 30 or so miles due east of Portland, is one of these tourist spots: A huge and (hopefully) extinct shield volcano that includes the highest point of the western Gorge (4062'), with a famous view from the top, reachable by Larch Mountain Road whenever the road isn't closed by snow. It gets a lot of snow, and a lot of rain when it isn't snowing, and many of the Gorge's famous waterfalls (Multnomah, Wahkeena, Oneonta, etc.) are on creeks that flow north off the mountain or out of its eroded crater. A raindrop that falls on the north side of Larch Mountain likely ends up on Instagram on its way back to the Pacific Ocean. Meanwhile creeks that flow south off the mountain flow into the forbidden Bull Run Watershed and become part of the Portland city water supply, so a raindrop that falls there could flow out of somebody's showerhead, drop some minerals on their shower door, and then flow through some pipes to the Willamette, and eventually back to the Pacific that way. Or maybe it'll end up inside a beer bottle and eventually wind up on the far side of the planet, who knows. There's also a third possibile destination: Several large creeks with unfamiliar names -- Gordon Creek, Buck Creek, Trout Creek, and a few others -- flow due west off Larch Mountain toward the Sandy River, and a raindrop that falls somewhere on this western slope will likely get to the Sandy completely unseen by anyone. This watershed area is roughly south of Larch Mountain Road, and north of the Bull Run boundary and the invisible force field barrier that probably keeps eviloers out of our water supply, and also keeps the watershed's resident Sasquatch population from sneaking out for midnight junk food. I mean, as far as I know.

Anyway, the uppermost part of this area, the first couple of miles west of the summit, largely belongs to the Mt. Hood National Forest, but is outside the national scenic area boundary except for the very top of the mountain. West of there it becomes a checkerboard of BLM and private timberland, and then more private timberland mixed with scattered farms and rural homes, and then some undeveloped Metro greenspace along the Sandy River. So there's actually a lot of public land around here, but as far as I can determine exactly one hiking trail in the entire area south of Larch Mountain Road; it's obscure, less than a mile long, and not the thing we're visiting today. What the area does have is a web of little-known and rarely-used forest roads, all gated and closed to motor vehicles, so they function as really wide trails. They don't always go anywhere interesting or offer dramatic scenery along the way, but if you just want to go walk in a forest for a few hours without meeting a single other human being -- or any coronaviruses said human being might be superspreading -- these roads do fit the bill for that.

So with that long prelude out of the way, let's get to the destination for this post. A bit over 8.5 miles from the start of Larch Mtn. Road, you're greeted by a very weatherbeaten sign welcoming you to the Mt. Hood National Forest. On your right, immediately past this sign, is the... trailhead? Intersection? I'm not sure which word applies here, but it's a spot where you can pull off the main road and park, and there's a gate, and a road behind the gate that continues south. If you know where to look, signs tell you this is the Lower Larch Mountain Gate, and the road behind it is Forest Service road NF-1509. (Depending on which map you look at you may see it labeled as 1509-000, with or without the hyphen, which is its full 7-digit road number.) This road is flat, and level, and the first ~2 miles of it are even paved. Which is really unusual if you know anything about Forest Service roads, especially gated ones.

The deal here is that this road doubles as a service road into Bull Run for the Portland Water Bureau, and triples as a service road for the Bonneville Power Administration, which has a major powerline corridor south of here. One of the Forest Service road inventory reports that I've been linking to a lot lately (specifically a huge spreadsheet inside this report) has a semi-cryptic description for this road: "Under SUP w/COPWB for Road Maintenance, OF=BPA Accesses BPA Transmission Towers". I'm reasonably sure COPWB stands for "City of Portland Water Bureau", and the "OF" refers to another column indicating who the primary maintainer or maybe user of the road is. Or something along those lines. I don't know the exact arrangements, but someone who uses the road and is paying for its upkeep thinks the first 2.3 miles ought to be paved, so it is.

I couldn't find a lot of other info about the road besides that official road list. Basically just was a lost dog notice from several years ago, and a 2018 sighting of Anchusa officinalis right at the gate/trailhead. Apparently this is a non-native/invasive plant that's taken up residence here and there around the region, but it's not considered that bad as far as nonnative plants go as it's known for producing lots of nectar for pollinators. So watch out for bees, I guess.

In any case, before you start hiking, you'll want to look around for a blue arc painted on the street in front of the gate. Don't park past it; the gate opens outward, and there's a small but nonzero chance it might need to while you're there. One that's all sorted, the road heads south-southeast from the gate, meandering side to side a bit, crossing several forks and branches of Gordon Creek in the process. These streams rush downhill into deep forested canyons to the west, and you'll catch occasional glimpses through the trees suggesting there'd be a really nice view in that direction if only there wasn't a forest in the way, but at no point does it actually open up and let you see more than that, which is too bad.

At least the near-solitude is nice. I encountered one other person near the start of the trail with two large and very good dogs, and later was passed twice by an official Portland Water Bureau truck. First as he was heading out to the gate and again on his way back back. At first I thought maybe the driver was off shift and going home, then the second time I figured maybe he popped out to grab a late lunch down in Corbett or Springdale, though he must've driven extremely fast once he hit a main road to be back so soon. Or maybe he was going home but forgot his hat or something. Later I figured out (via a recent "Interim Measures Watershed Report") that the water bureau employs a number of "watershed rangers" here, and one of their duties is making the rounds checking the various gates into the area, and generally sort of securing the perimeter.

At one point along the road, just before it meets an old decommissioned side road (no. 1509-041, if you're keeping track at home), a small creek passes under the road in a culvert and then disappears over the edge of a cliff just steps from the road. A little map-based guessing suggests this miiight be the top of a waterfall, possibly up to 70' high, though I've never read anything about one being here. And just below that, it looks like the stream tumbles down a steep slope maybe another 150' to where it joins Gordon Creek, kind of like the stretch of creek below Wahkeena Falls. I'm not a big fan of sheer cliffs and didn't peek over the side of this one, so I'm not positive about any of this, mind you. I tried to check it out from below a couple of weeks later via an old BLM road, but I couldn't find it from there, so either it's not visible from below due to trees, or possibly I was just looking up the wrong creek, as there are several others that join Gordon Creek at around the same spot. At this point I'm about two-thirds convinced there isn't a safe or practical way to settle the question, at least for a risk-averse person like yours truly. This might be a perfect use case for a drone, actually, but I'm still trying to figure out whether drones are legal here, plus I don't actually own any drones.

So after that unsolved mystery, the next point of interest is the spot where the road turns to gravel, right after the four-way intersection with a pair of decommissioned, dead-end roads (1509-180 and 1509-190). As far as I can figure out, those were purely logging roads and they just end after a while without going anywhere interesting, and they're well on the way to being reclaimed by the forest, so exploring them further seems like a lot of effort for very little reward. I don't know why the paving ends where it does, and whether that's connected to the two side roads. I don't have any theories about that, unfortunately.

After a half-mile or so of gravel road, the forest abruptly opens up and you're in the powerline corridor. The buzzing wires overhead belong to the Bonneville Power Administration, and carry power to Portland from various dams along the Columbia as well as the one commercial nuclear plant at Hanford.

This spot is also home to another four-way intersection. You can turn around and go back at this point, which is what I did, but if you wanted to keep going you have a couple of options. To your left, a gravel road heads uphill under the powerlines. This is a continuation of NF-1509, so you can keep going that way if you feel like hiking under powerlines. Eventually it intersects with NF-20, another forest road that runs sort of parallel to NF-1509 but a bit further up the mountain. In fact you can form a loop route this way, heading south on either NF-1509 or NF-20 to the power corridor, connecting to the other road from there, and then heading back to Larch Mt. Rd. that way. The 2010 USFS study that resulted in decommissioning NF-20 and the side roads along 1509 mentioned this route as a known recreational use of the area, but since the area isn't managed for recreation they went ahead and tore up the road anyway. NF-20 is still passable on foot (and I'll finish that post eventually) but going by bike now is going to be a hassle unless maybe you've brought a BMX stunt bike and your advanced half pipe skills, or you're up for a bit of cyclocross. On the other hand, getting from the NF-20 trailhead to the NF-1509 one or vice versa involves a stretch of Larch Mountain Road, which would be fine -- even fun -- by bike, but sketchy if you're trying to walk it.

To your right from the crossroads is road 1509-016, which continues on west under the powerlines to the National Forest boundary and then beyond under various other names. This long stretch of road figures in several variants of the (highly unofficial) Dark Larch cycle route, eventually ending up somewhere vaguely near the eastern side of Oxbow Park. Looking that direction, in the distance I could see the same Water Bureau ranger truck that had passed me earlier, because there's plenty more perimeter that needs securing off in that direction.

It turns out the gate check thing is less about evildoers and more about germs, specifically Cryptosporidium, a waterborne intestinal parasite that causes diarrhea in people and animals, and can cause more serious disease in immunocompromised people. The microbe has an outer shell that largely protects it from chlorine in water, so if it exists in your watershed, just chlorinating your water supply isn't enough, and you also need an expensive filtration system to keep these little bastards out of the water supply. Portland doesn't currently have one of those systems, and didn't want to build one, and (uniquely) got away with a series of repeated waivers until a few years ago, arguing that its water supply is so remote and pure and natural and pristine thanks to the watershed closure plus chlorine that it would be a huge waste of time and money building a plant.

But the bug kept popping up sporadically in water quality tests, most likely because you can't close the entire watershed area to all animal life, and you may have heard about what bears famously do in the woods. So the city eventually stopped getting state waivers about this in 2017 and had to agree to build a filtration plant by 2027. In the meantime the city agreed to various mitigation measures so they could continue using the watershed until the new system was ready. Hence the "interim" in the "Interim Measures Watershed Report" I mentioned earlier. The confusing thing here is that the positive tests that caused all of this trouble are not thought to be from a human source, so I'm not clear on how doing more to keep motor vehicles out of the area helps with that. Unless maybe there have been recent hushed-up events involving bears driving trucks, in which case humanity has more to worry about than a little watershed mischief.

That same report notes that they've left out key details of the local security arrangements, because security. Which is why you don't want to take the remaining option at the intersection. Going straight ahead would put you on road 1509-510, which continues south and downhill into dense, dark, creepy Mirkwood-like forest, flanked by stern Bull Run Watershed signs strictly forbidding you from going any further in that direction. Assume you're on camera here, in other words, even if you don't see any obvious cameras. It's bound to happen eventually, at least. The fabled force field barrier I mentioned is probably around here somewhere too. It's quote-unquote probably just the kind you bounce off of, and not the kind that disintegrates you on contact, though it's hard to be sure since both are invisible. And more to the point, speaking as a Portland water customer, I am asking you nicely not to go that way.

Before we leave here, take a closer look at the trees on the Bull Run side. Notice how they're packed together and are all about the same size? A natural undisturbed forest wouldn't form a uniform wall of trees like that. What you're looking at was one of Portland's dirty little secrets for most of the second half of the 20th Century. People tend to think Bull Run is an oasis of pristine wilderness except for a couple of unavoidable dams and some water works infrastructure, but that's not really true. In 1958 the Forest Service concluded they could rake in an extra million dollars per year by allowing logging in Bull Run. Everyone had sort of assumed this was prohibited by the 1904 federal law governing the watershed -- signed by Teddy Roosevelt and everything -- but the agency decided it had found a loophole: The law limited access to authorized personnel only, but neglected to limit exactly who could be authorized and what they could be authorized to do, so they ran with it and started authorizing logging companies to clearcut Portland's city water supply. They suspected this would be a tad unpopular, so the plan was to do the logging semi-clandestinely and rely on the same 1904 law to keep the public from finding out. You might think city government would object to this. What possible inducement could there be for them to go along with this? Apparently the Forest Service brought in some tame industry-friendly scientists of theirs, who argued that old growth trees were "decadent" and prone to forest fires, and probably listened to beatnik jazz records and indulged in a bit of tree communism when nobody was looking, while freshly-planted trees were young, vigorous, non-combustible, upstanding citizens. I may have paraphrased that a bit. The fire argument was especially persuasive just then, as over 2000 acres of Forest Park had burned in 1951 (and in 2021 the city worries it's overdue for another fire now), and the same year saw the fourth and last (so far) Tillamook Burn, in the Coast Range due west of Portland. So the city went along, though perhaps wondering privately why it needed to stay on the down-low if it was such a good idea and based on settled science.

So this arrangement worked out as planned until July 1973, when a federal lawsuit ended up exposing what was really going on. (The suit was a front page Oregonian story that day, just below President Nixon refusing to comply with Watergate subpoenas.) Until then, the party line was that any logging that may or may not be happening was on a small scale, with a negligible impact. As one absurd example, here's an April 1973 Oregonian profile of a gentleman who, yes, was logging somewhere in Bull Run, rather close to one of the main reservoirs, but his was a rustic one-man operation and harvested almost no trees. And due to extremely strict watershed rules he was doing this with adorable draft horses -- Clydesdales and Percherons, just like in the beer commercials -- instead of modern machinery that would compact the soil and hurt trees (other than the ones he was there to hurt). And to protect the watershed from what horses do in the woods, the horses wore cute special diapers, and the guy even had a special shovel ready in case of diaper accidents. And he'd recently been on a national trivia game show about all this, and Hollywood was interested in his life story, and it was all very bemusing for a simple man of the forest. And in short, things were just peachy keen and bucolic on the Bull Run front, and please pay no attention to the chainsawing noises behind the curtain.

A 1973 City Club of Portland report on the watershed tried explaining the contradictory laws and rules and regulations applying to the area. Among other things, the Forest Service was insistent that per federal law, if the city didn't want clearcuts within its supposedly-reserved watershed, the city would have to write annual checks compensating the feds for lost revenue. Which the city wasn't keen to do.

After several years of legal wrangling, the sneaky feds lost the case in 1976, and if this was a Hollywood plotline the credits would've rolled at this point, and everyone lived happily ever after. That's not how things actually played out, though. A March 1976 Oregonian article described the timber sale situation as merely 'stalled' due to the lawsuit, and explained a major unintended consequence of the recent decision in the case. It seems the ruling was, specifically, that under the Bull Run Act the Forest Service did not have the discretionary authority to permit any commercial or recreational activity within the original 1892 boundaries of the reserve. This was a problem because the 1892 boundaries were based on a gross misunderstanding of the size and shape of the Bull Run River's actual watershed, and the original forbidden zone included over 40,000 acres that were physically outside of that watershed, but legally within it. The USFS had administratively shrunk the off-limits area in 1959 to roughly conform to the actual watershed, as -- law or no law -- keeping people out of the non-watershed area defied basic common sense, and enforcing that limitation cost money. Over the next nearly-two decades, a number of roads and trails extended into the formerly closed area, and people soon became very attached to them. But the judge concluded that this 1959 order was no more legal than the 1958 order allowing clearcuts.

An October 21st 1976 article told readers to "see it while you still can". Seems the judge had ruled that everything had to be gated off and secured by November 1st, and if anyone was caught violating the 1892 boundary both they and the Forest Service would be punished severely. The new off-limits zone included parts of the Oneonta, Eagle Creek, and Tanner Butte trails, along with the road to Ramona Falls, part of the Timberline Trail around Mt. Hood, and a third of Lost Lake, among other things. The one big exception to the closure was the Pacific Crest Trail, as was (and still is) governed by a separate act of Congress that superseded the old Bull Run law. So you could still hike that one trail, you just couldn't legally step off the trail even just little, at any time, for any reason, at any point between Paradise Park on Mt. Hood and a point near Cascade Locks.

The closure is mentioned in passing in a March 1977 Roberta Lowe article mostly about how the very dry winter of 1976-77 would likely affect the upcoming hiking season. She speculated that a "nasty" stream crossing on the upper reaches of Eagle Creek (on the Eagle-Tanner Trail #433) would in theory be less sketchy than usual in the coming year, if only it was legal.

Another Lowe article in May 1977 updating readers on the ongoing saga, the bureaucratic gears were still slowly grinding away when one of the state's congressmen and both senators introduced legislation to restore the old status quo and reopen the beloved closed areas. Not putting a whole lot of emphasis on the fact that they were also legalizing Bull Run clearcuts in the same law. Portland city government saw this in the fine print and made a fuss about it, but it was essentially a done deal at this point, the specific deal being that logging in Bull Run had to resume if the public ever wanted to see Ramona Falls or Wahtum Lake again.

In any event, the new law passed, and the clearcuts resumed, and this state of affairs continued for another 20 years, now protected by a special law and unaffected by all the spotted owl stuff going on in the outside world, right up until the 1996 floods, when the bill came due. Mud and silt from clearcuts poured into the Bull Run reservoirs, forcing the city's primary water supply offline. The city fortunately had (and has) a backup supply to switch to, but keeping the status quo was instantly a nonstarter, and Congress changed the law again, this time banning any further logging in the watershed. Sponsored by the same Senator Hatfield who pushed through the previous law, because legislating is like any other job: If you stay long enough, eventually you have to clean up messes you helped cause.

So that's where things stand now. As far as I know the feds haven't found a convenient loophole in the 1996 law yet, and if any top secret special ops logging was happening anyway it ought to show up on your favorite online map's airborne/satellite view. Of course the online photo is not the territory, and in theory the feds could lean on Google et. al. to conceal any new clearcuts, and make it more subtle than the obvious pixelation map services used to do in the mid-2000s. One of the key arguments in the 1973 suit was that if runoff from clearcuts damaged Bull Run's water quality, the city would be forced to build an expensive filtration plant much like the one it now has to build due to cryptosporidium. So when that plant comes online sometime around 2027, we may hear arguments about how the watershed closure is now obsolete and it's time to go in and clear out the trees before they catch fire due to climate change or something. And who knows, maybe the closure as it exists now would be overkill at that point; I know I'd be interested in visiting a few of the 20 or so waterfalls said to exist in the closed area, if that was legal. But I don't really see Portland going along with that sort of proposal anytime soon; as recently as 2019 the city passed a local ballot measure putting Bull Run protections into the city charter. There were already city ordinances to that effect, but the thought was that some future unsavory city council could simply repeal those ordinances and then do as it pleased with the city-owned parts of the watershed. So as of the 2019 measure, that can't happen without amending the city charter again, which would require another public vote.

Mauʻumae Nature Park

Switching gears again, next up we're visiting Honolulu's Mauʻumae Nature Park, uphill from the Kaimuki business district & the Kahala Mall, and below the Mauʻumae/Lanipō Trail we checked out a few months ago. This was supposed to be another hiking post; I saw "Nature Park" on a map, and a few scattered references to a loop trail. But not a lot of references, so it was probably uncrowded. So I figured I'd go check it out. The park totals 33 acres, separated by Koko Drive into a 4 acre lower section, partly developed as a regular neighborhood park, and a 29 acre undeveloped section where the loop trail is supposed to be. I say "supposed to be" because I completely failed to find it. There wasn't a sign with arrows pointing at it, and I walked back and forth along Koko Dr. a couple of times without seeing anything that looked like the start of a trail. So I ended up settling for some photos of the view from Koko Drive, which looks out at Kaimuki and the back side of Diamond Head. It's undeniably a nice view but not really why I was there, so I chalked this up as a loss. Still, I had photos of the place, so I created a draft blog post about the place but didn't feel especially motivated to do anything with it. I also never quite deleted the thing, because I kept wondering why there was a nature park here, specifically, and what the deal was with the missing trail.

Couple of caveats first: One, I don't currently have an Oʻahu library card, so there are some gaps in what I've been able to figure out that would likely be filled by old newspaper stories if only I could get to them. Two, these photos are from 2016, and your mileage may vary if you go there right now. (I remember being especially annoyed at not finding the trail since I was trying to take my mind off the horrifying Republican national convention that was happening that week.) So with that in mind, I have reason to believe the trail really does exist, and it's not just a scheme to milk City Hall for grant money or whatever. First, there's a GPS track of it on Alltrails, which actually predates me visiting by several years. Second, plugging those trailhead coordinates into Street View shows what looks like a couple of rough stone steps leading to, well, shorter grass than the surrounding grass and brush, which might be the start of a trail if you squint at it just right. And that imagery is from 2019. So my unsuccessful visit is bracketed by the evidence, unless maybe the trail phases in and out of existence according to the season or the phase of the moon. Or, more likely, you can find it if (and only if) you already know exactly where to look, and a motivated neighborhood volunteer who owns a weed trimmer has been there recently. If you do manage to find the trail, there's a geocache hidden somewhere along the trail, for extra credit. The description on that geocache explains "When I was a kid living about 130 yards from where this cache is, we knew this area as the gulch and was left undeveloped because it was needed as a watershed area. It later became the Mauʻumae Nature Park." Which turns out to be a key clue.

And sure enough, in the lower section of the park, right next to the landscaped play area, there's a fenced-off area with the usual imperious "Government Property - Keep Out" signs. These signs never explain which part of the government owns it or why, but the county GIS system says this area belongs to the Honolulu Board of Water Supply, and is home to that agency's Waialae West Well. This well opened in 1998 on the site of an older well named "Waialae Shaft" that operated from 1937 to around 1984. A 1938 book explains that it began construction in 1935 and was built at a 30 degree angle into the hillside for some reason. The book includes a couple of photos of sketchy-looking pump equipment at the bottom of the well, which I suppose must have been state-of-the-art back then. As for the present-day well, here's the federal Environmental Assessment back from when it was proposed, if you like reading that sort of thing as much as I do. (And no, I'm not being facetious about that.) One weird detail about it is that the 225' well is actually drawing in fresh water from below sea level. I am probably not the only person who finds this a bit surprising, even alarming, as the doc explains the science ^[1] behind this (and the linked footnote goes into more depth if you're really curious):

The Waialaie West Aquifer system provides the most common type of groundwater available on Oahu, consisting of a layer of infiltrated rainfall floating as a lens-shaped body over salt water. Fresh water floats on the heavier salt water, both of which permeate the subsurface rock. The density ration between fresh water and salt water is such that theoretically, for each foot that the fresh water lens stands above sea level, the lens extends 40 feet below sea level to a midpoint where salinity is half sea water. A transition zone of mixture grades upward to fresh water and downward to sea water. The presence of the fresh water head is due to relatively impermeable caprock, located along the coastline, which retards outward flow to the ocean.

It seems that right around the same time the original well was built, developers were planning to build a subdivision called "Kahala Heights" here, covering the entire hillside where the park is now. Somehow the state ended up owning the center of the proposed subdivision instead, though I don't know whether that was a straight business deal, or the Depression or WWII also figured into it. In any case, the state held the land as a buffer around the well, but I gather they did nothing else with the place during the decades they owned it, much to the frustration of the surrounding neighborhood. I don't know whether the whole park was actually fenced off or not, but it very well could have been.

A June 2000 Star-Bulletin article explains that the state had handed the land over to the city in 1991 -- several years after the original well had gone out of service -- and residents had big plans for the place. Volunteers had already built the elusive loop trail by the time of the article, and had been planting native plants starting around 1994. A couple of years later the city approved an official master plan for the park, finalized in July 2002 (see also a 2003 environmental assessment for the plan). That doesn't tell us very much about the nature area unfortunately, since the master plan for that part was to just leave it alone other than the existing nature trail. While the lower part of the park was slated to get some neighborhood park-type improvements, only some of which have actually happened so far. Among the things dropped from the finalized plan was a proposed Zen archery range, which would have replaced an existing one somewhere in Kapiolani Park. Strictly speaking it wasn't completely dropped, just moved to a timetable-less "Phase IV" of the comprehensive park plan, which is much more polite and non-confrontational than a simple 'no' would have been. Volunteer enthusiasm naturally ebbs and flows over time, and after that initial burst of urban planning excitement, there's a decade gap in easily-found news items until 2013, when residents were campaigning to close the park at night as it -- specifically the viewpoint part -- had become a late-night party spot. The park closes at 10pm now, so the campaigners may have gotten their rule change. Whether the city actually enforces the closure is, as always, anyone's guess.

For a little alternate history, here's the undated overall map for the proposed Kahala Heights subdivision. When I said this was roughly contemporary to the well, I was going by the earliest date stamps on some plat maps for various pieces of the development. These maps were updated and re-stamped every time anything about the map changed up into the mid-1980s or so when presumably everything was digitized. The future "natural area" portion of the park is shown filled with houses and crossed by a couple of never-built roads labeled simply "Road F" and "Road I", with a bunch of proposed and then canceled parcel numbers X'ed out. The maps also contain a bunch of hyphenated numbers that look like dates, specifically March 3rd of consecutive years from 3-3-13 thru 3-3-22. Those are actually "TMK numbers ^[2]", part of the state's unique property ID system, and I have to say I'm quite glad I figured that out before posting a whole paragraph trying to guess what was so special about March 3rd, which is something I had in an early draft of this post. The docs show the park as owned by the state, which was true past the point where the county stopped relying on paper maps. I suppose that after statehood in 1959, some poor junior surveyor must have drawn the short straw and had to go through every single map in the office with a pen and a jug of whiteout, manually updating anything that said "Territory of Hawaii" on it.

I did find a handful of random historical items by searching for "Kahala Heights", as that name was once used for the general neighborhood but largely fell out of use several decades ago, at least going by the stuff I can find on the internet easily. As a result, search results are (unusually) not completely swamped by real estate listings. In the present day the neighborhood generally goes by "Wilhelmina Rise", and becomes "Maunalani Heights" a short distance further uphill, per a 2017 Honolulu Magazine piece that explains the difference and drops in a little history of both. Anyway, I can't come up with much of a storyline linking these random historical items together, so I'm going to go with an oldest-to-newest bullet point list and call it even:

• The neighborhood is mentioned briefly in a biography of John Henry Wilson, whose Wikipedia bio describes him as "a civil engineer, insurgent, co-founder of the Democratic Party of Hawaii, and Mayor of Honolulu, Hawaii three times: from 1920 to 1927, from 1929 to 1931, and from 1946 to 1954." It seems the neighborhood had a small cameo role in the 1928 mayoral election. I don't know the whole story, because it's not included in the free Google Books excerpt of the book, but I gather there was an ongoing controversy about a stone crushing operation somewhere vaguely near Kahala Heights, and local Republicans were trying to make an election issue of it, arguing Wilson wasn't protecting neighborhood children and the local school properly. It turned out that the rock crushing operation was over half a mile from the school, and the people pulling the strings behind this astroturf campaign were snobby rich people in the beachfront Kahala neighborhood, because some things never change, and Wilson ended up regaining the mayor's office that year.
• Skipping forward to December 7th 1941, a 2016 Star-Advertiser story related a reminiscence from a longtime resident who was 11 when it happened. Confusing news reports were saying that something bad was happening across town at the navy base, so he and some friends hiked uphill somewhere in the the Kahala Heights area to get a better view, and just then a Japanese Zero flew by at about eye level. Not understanding what was going on, the kids waved at the pilot, and he saw them and waved back. A 2013 Orange County Register story related another Zero pilot story from someone else who was from Kahala Heights but saw the plane over in Aiea, much closer to the attack.
• Brief reference to a 1961 study on doing some urban renewal in the Kaimuki, Maunalani, and Kahala Heights neighborhoods. In a 1962 issue of "Housing and Planning References", a sort of quarterly bibliography of recent studies and publications relating to urban renewal topics nationwide and around the world. This might be what eventually led to the large public housing projects in Palolo Valley next door, which have about the same reputation as midcentury public housing does everywhere else.

So yeah. In summary Mauʻumae Nature Park is a land of contrasts. Still wish I could find that dumb trail, though.

---

footnote(s)

Ghyben-Herzberg Theory

The science behind this aquifer stuff is something called "Ghyben-Herzberg theory", dating back to work by a couple of German engineers in the late 19th Century, building on ancient Greek discoveries about density and buoyancy from thousands of years ago, just swapping out the bathtub and gold crown with fresh water and salt water inside semi-porous solid rock. And a bit of assuming one of those legendary spherical cows physicists keep going on about, as this 19th century model just gives you a general idea of what the state of your aquifer is at a given point in time and how much fresh and fresh-ish water there is. It doesn't tell you how much water it's safe to remove from the system without drawing saltwater in from the ocean and ruining your aquifer. For that you need to understand how much freshwater is naturally entering and exiting the system and how quickly saltwater can move in if the equilibrium shifts. I gather the aquifer here is a relatively simple example of this kind of system, as there were computer simulations of it as early as 1985. This 1985 paper explains that the Waialae West aquifer is separated from adjacent aquifers by dense, non-permeable volcanic dikes underground, and separated from the ocean by dense coastal marine sediments, so the above-sea-level groundwater doesn't just leak out to sea immediately (which makes it a good place to dig a well), and it isn't flowing sideways deep underground to a significant degree, which makes it easier to model. In fact it's a literal textbook example, in Seawater Intrusion in Coastal Aquifers: Concepts, Methods and Practices (1999, pp. 234-237), which looks at how closely a couple of models (the original Ghyben-Herzberg one, and a newer one called SHARP) model the actual behavior of the well, going by a nearly four decade dataset (1937-1975) from the well, and rainfall data from the same period. If I understand correctly, the classic model doesn't fit exactly because rainfall varies a lot between years and by season, and then the rainwater takes a while to make its way down into the aquifer.

A weird data point on how long it takes for rain to become aquifer water here comes from a 1973 study measuring tritium levels in water around Oahu. Tritium being a radioactive isotope of hydrogen with a half-life of about 12 years. It occurs naturally in very low levels, but at the time of the study the bulk of it in the environment was residue from above-ground nuclear tests. Among other things, this provided a unique way to date the groundwater, or in this case set a lower bound on it, since they found essentially zero tritium in well water from here, which they took to mean that tritium-enriched water had not yet filtered down into the aquifer in significant quantities since 1954, when the stuff would have begun entering the environment in detectable quantities. (They don't explain the 1954 date, but I imagine it relates to hydrogen bomb tests, or maybe ordinary non-fusion nuclear tests conducted in the open ocean.) I imagine this study would be unusually difficult to replicate in 2021, as you'd probably have to develop your own nukes first to supply the needed tritium, and most university IRBs tend to frown on that sort of thing these days.

Of course the hardest part of all is that even if you're figured out the natural rates of inflow and outflow and such down to all the decimal places you'll ever need, that rarely stops people from getting greedy and trying to push the envelope even further. There's the classic tragedy of the commons with everyone overdraws the aquifer a little and nobody feels responsible, and the modern plague of professional contrarian experts who will happily tell you you can draw 27% more water than you're doing now and it'll be fine according to these PowerPoint slides, just do it and be legends, etc. Or developers come to town touting a multi-billion-dollar scheme that unfortunately involves cutting through those coastal sediments and pulling the cork out of the bottom of the local groundwater supply, and (this being Hawaii) it gets approved quietly by an anonymous city bureaucrat in exchange for a suitcase of cash, steady no-attendance jobs for various no-good relatives, VIP trips to Vegas, and the other usual inducements.

TMK Numbers

TMK ("tax map key") numbers, which Hawaii uses instead of the township-range-section-lot arrangement used across much of the mainland. Here's a local realtor's blog post explaining this unusual system, as he explains it better than I can. A number like "3-3-15" says this is zone 3, section 3, plats 15, and that combined with the parcel numbers on an individual lot gives you the TMK. The full TMK for these lots would all have a leading '1', which is the island number for everything on Oʻahu, but in common use those are typically left off as implied. Linked from that post, here's a map of Oahu showing the zone & section layout of the island. The striking thing about that is that those boundaries correspond very closely to traditional moku and ahupua'a boundaries, which date back to many centuries before the first European visitors showed up, and in turn are largely based on natural watershed boundaries. Lots of other things follow the same lines to varying degrees, despite having nothing to do with watersheds or land tenure, like city, state, & federal legeslative districts, zip code boundaries, zones of the city park system, and so on.

Backstrand Road, and a small mystery

As I think I've mentioned once or twice now, one of my coping strategies during the ongoing pandemic has been to get outside when I can, while encountering as few other people as possible, ideally nobody at all. It's not just about avoiding getting sick; I've had all my shots, and will get my booster when it's available, and I've seen all the (pre-Delta) studies that say the odds of catching Covid outdoors is very low, especially if you're just passing someone on a trail for a few seconds. But people still stress me out, even knowing all of that. I also figure that even if I'm overreacting -- and I probably am, even with the Delta variant on the loose -- it's still an excuse to spend way too much time staring at maps and looking for the most obscure, least visited places I can come up with, which is a big part of the fun.

So a while back I ran across the US Forest Service Interactive Visitor Map and started poking around the Columbia Gorge on it, as one does. The key thing here is that this map shows Forest Service roads as well as trails, and a lot of these roads are either gated and closed to motor vehicles, or get so little traffic that they effectively count as trails. The downside is that they often don't go anywhere interesting, and just end in the middle of the forest at the site of an old 1960s clear cut, or power lines, or a cell tower, that sort of thing.

While staring at that map I noticed a couple of short forest roads branching right off the old Columbia River Highway just east of Bridal Veil, smack dab in the middle of the main tourist corridor, and I'd never heard of either of them. So those obviously went on the big TODO list, and now you're reading a post about one of them.

So right around the pushpin on the map above, roughly halfway between the Angels Rest trailhead and Wahkeena Falls, there's a small turnout off the eastbound side of the old highway, with a closed and dented gate and no obvious signage visible from the street. If you're like most people, you probably won't notice it at all, and if you do you'll probably assume it's private property of some sort, since that's exactly what it looks like. It sure doesn't look like a trailhead, at any rate. But this gate belongs to you, the federal taxpayer, and behind it is an old road the Forest Service calls "Backstrand Road", aka road number 3000-303. Past the gate, the road heads steeply uphill for a bit -- a back-of-the-envelope calculation and some guesswork says it's a 10% grade, within a few orders of magnitude or so -- and it then turns right/west at a corner with some old decorative rockwork, then widens and levels out for a short stretch, before petering out into dense underbrush.

At the corner where the road levels out, you can clearly see where the road once continued east as well, and a current county assessor's map shows that bit of road heading back down to the highway at a more reasonable angle. But that road has also been thoroughly consumed by the forest and you can't make any progress on foot in that direction either. So that's about all there is to do here. I didn't see any obvious side trails or other attractions. Glimpses through the trees suggest there'd be a decent view from the top of the trail if it wasn't for all the trees, but there are zero breaks in the trees so that's kind of a moot point.

So given all of that it's not surprising that a 2003 Forest Service roads assesment and its 2015 update both labeled the road as "low value" and recommended it as a high priority for decommissioning. But the reports also noted that the road wasn't a significant risk to anything or anyone if it was just left the way it is now. Which is probably why they still haven't gotten around to ripping it up in 2021. But why was the road here in the first place?

To me the road really doesn't look like your ordinary Forest Service logging road, even in its now-overgrown state. It just seemed like someone spent more money on it than the USFS likes to spend on logging roads. So I did a little digging and apparently this was private property with a house on it just twenty years ago. I know this because of four data points:

• The PortlandMaps entry for 49666 (!) E. Historic Columbia River Highway (the honest-to-goodness street address of the lot containing the road) has a last-sale date of 2001, and the assessor history shows that property taxes were being paid on the land before that sale, which tells us it was private property just 20 years ago. The entry also says the 27.36 acre lot is still technically zoned as residential.
• The road appears in 1961 and 1995 county survey records, the latter looking much like the current road layout. A comment on the 1995 survey refers to the road as a "driveway".
• The Multnomah County surveyor site also has a neat feature with aerial imagery taken periodically since 1998, which unfortunately I don't see a way to link to directly. The 1998 and 2002 image sets show a structure at the west end of the flat bit of road, while the 2004 edition shows fresh dirt where that structure was, and the latest edition shows nothing as the forest canopy has now grown in by a lot.
• I also managed to find some info about the former building, thanks to whoever had the brain-genius idea to auto-generate a "real estate listing" page for every street address in every dataset they could lay hands on, including obsolete stuff. The resulting pages are just search result-clogging SEO spam upwards of 99% of the time, but the listing for this place tells us the long-gone house was 974 square feet, built in 1958, with one bedroom, one fireplace, and baseboard heat.

I unfortunately couldn't find any news stories about the sale here. I suppose there either wasn't a press release at the time, or there was but nobody deemed it newsworthy.

That's not a very interesting story by itself, but there's a bit more history around here, and for that we have to zoom out a little. The state LIDAR map shows what kind of looks like a faint trail or service road or something heading west from where the house used to be, heading toward Dalton Creek.

Now, Dalton Creek was the subject of several OregonHikers forum threads, mostly in the late 2000s and early 2010s, several of them trip reports from people trying to sort out the "which waterfall is Dalton Falls" controversy (see my old Dalton Falls posts for more on that) and looking for additional falls on a few creeks immediately east of Angels Rest:

• April 2007: "Hidden in plain sight: a waterfall at Angels Rest!"
• February 2008: "Foxglove Falls 2-9-08"
• Early December 2010: "Foxglove Creek"
• Mid-December 2010: "Dalton Falls to Mist Falls Loop 12/19/10"
• Late December 2010: "Dalton - Foxglove Conundrum"
• Later December 2010: "Mesachie Creek"
• Mid-December 2013: "No Waterfalls on Devils Rest 11-Dec-2013"
• Late December 2013: "Angel's Rest (Nostalgia) Trip! (Dec 27)"
• December 2018: "Palmer Mill Rd/Primrose Path - Dec 7, 2018"

There were a couple of mentions of bushwhacking along Dalton Creek up from the old highway and sometimes climing all the way to Angels Rest from there, so apparently nobody realized there was a simpler and less thorny way to do the initial approach, a way that also skips traipsing along right past someone's house.

Dalton Creek is also the property line betwen the Backstrand Road property and a pair of small lots with diagonal property lines that together form a rough diamond shape totaling about 10 acres. Those property records show the Forest Service has only owned them since May 2002, and whoever owned them before was exempt from paying taxes on the land, so either another government body or some nonprofit group. I'm not positive I've found any news about that sale either, but I did find an April 2002 article that briefly mentions a possible upcoming land deal somewhere in the Bridal Veil area. It says the sale would cover 77 acres & could enable an ADA-compatible trail to Bridal Veil Falls someday, so it may be about a completely different land deal, or it might have covered the lots here and others elsewhere. The timing seems right, but there just aren't enough details to be sure.

Which brings us to the small mystery from the title of this post. A 1962 zoning map and an earlier 1950s tax assessor's map both label the diamond-shaped area as "YMCA". That got my attention, and before long I thought I had it all figured out: An April 1919 Oregonian story explained that local farmer George Shepperd (famous as the donor behind Shepperds Dell State Park) had also donated a house and land somewhere in the Bridal Veil area for a new YMCA camp. A WyeastBlog post about the nearby Bridal Veil Cemetery gives some backstory on Shepperd, his YMCA donation, and a series of strange and melancholy events in the years after he donated the falls. The trouble was that I couldn't find any subsequent news stories about the camp -- no grand tour when it opened, no vintage photos of kids doing crafts, nothing -- and a 1927 Metsker map doesn't show a YMCA camp here, or even any property lines corresponding to the camp we saw on the 1950s & 60s maps. Instead, it shows that roughly the entire area beyond the old mill town was then owned by a "Columbia Highlands Co.", including the Backstrand Road property, the future YMCA diamond, and points east all the way to Wahkeena Falls.

(Incidentally the other (and the oldest) ownership map I ran across was from 1889, and shows the whole area owned by a W. Dalton, who we met but learned nothing about in one of my old Dalton Falls posts, or maybe the Dalton Point one. He or she also doesn't figure into the present story any further, other than being the namesake of the creek here.)

Anyway, the Columbia Highlands company was incorporated in July 1915, and a brief business item the day after the big announcement noted it was capitalized at $400k and would be "a general brokerage firm dealing in real estate". Another item the following month finally explained what the company had in mind:

The Columbia Highlands Company was given permission last week by the state corporation department to plat and sell approximately 1760 acres of land along the Columbia River Highway, about 30 miles from Portland, and to construct a scenic road, clubhouse, and hotels. The company is capitalized for about $400,000, and its officers are Portlanders.

A similar Oregon Journal item also explained that the company is a consolidation of the interests of the Gordon Falls company, Charles Coopey, and Minnie Franklin.

Those names got my attention, and let me try to explain why briefly. "Gordon Falls" is an old name for Wahkeena Falls, Coopey was one of that company's founders (and namesake of Coopey Falls along the Angels Rest trail), and Franklin was the future Mrs. Charles Coopey, and the full story of the company is a whole other half-finished draft blog post I need to finish, but the short version is that the company proposed to build a woolen mill somewhere near Wahkeena Falls, to by powered by damming the creek above the falls. The mill would of course have its own company town nearby, to be named "Gordon Falls City", whose water supply would come from diverting Dalton Creek right here. It turned out the plan was not to build a new mill from scratch; instead the new mill would be a relocation of the famous woolen mill at Pendleton (which still exists today), disassembled and shipped west piece by piece. The whole scheme sounds outlandish, and it came to nothing when locals in Pendleton passed the hat and outbid the Gordon Falls investors, and found someone in town who was willing to take over the recently-closed mill. Which may have been the real plan the entire time, and the Gordon Falls City scheme was just a ruse to scare Pendleton into paying up. In any event, the company's stock was instantly worthless, and Portland-area investors who lost everything were outraged, and the whole mess ended up in court for years and years afterward.

The company's only real asset was all the land it had accumulated between Bridal Veil and Wahkeena Falls. Under modern bankruptcy law that land would go to pay off Gordon Falls creditors, but back then it just sort of quietly rolled over into the new Columbia Highlands company, just in time to try to cash in on the brand-new Columbia River highway next door. A May 1916 story announced the new business plan was to subdivide the company's holdings for summer homes and general development. The company's land extended way up into the hills and canyons above Bridal Veil, and in some alternate timeline where this plan panned out there are endless historic preservation battles around a cluster of fabulous but decaying Gatsby-like Art Deco mansions atop Angels Rest, which have proved to be prohibitively expensive to own and maintain. In our timeline, a pair of Journal stories from July 1916 note that part of the company's now-1700 acres had been surveyed and platted as residential property, and they had already sold a pair of lots totalling 2.5 acres with a prime view of (newly renamed) Wahkeena Falls, with home construction to begin shortly. Typically an item like this would be the kickoff for a long stretch of weekly or even daily real estate ads touting the area and reminding the reader that the area will be sold out soon and this may be their last chance to own a piece of the Gorge. But I couldn't find any sign that they had ever advertised Columbia Highlands, unless maybe the ads neglected to use the key phrase "Columbia Highlands", or the words were in an overly ornate Deco font that the newspaper database's OCR system couldn't parse. And what's more the Multnomah County Surveyor's Office GIS map has no trace of any of this alleged subdividing and platting ever being filed with the county, so it's anyone's guess what was really going on here. In any event, the next mention I found of the scheme was an August 1918 news item suggesting the company had changed plans again:

Following the annual meeting of the Columbia Highlands Company, held yesterday, it is announced that the directors have decided to carry forward a plan of development of their property through which the Columbia River Highway runs for nearly three miles. Trails will be developed to various scenic points, including the hanging gardens on Dalton Creek and numerous grottoes of exceptional scenic beauty. Attention will be given to lands adjacent to the highway, and steps will be taken to protect the shrubs, trees, and forest from the vandalism of thoughtless visitors.

A similar Oregon Journal article explained that the company was now just going to develop land along the highway, with the balance reserved as a privately-run tourist attraction. Hiking trails would come first, followed eventually by longer trips up into the mountains by burro or pack mule, I suppose along the lines of what you can still do at the Grand Canyon. The new board of directors listed a local judge as president of the firm, the other seats filled by familiar names, including Coopey as secretary, and Coopey's wife as treasurer. I'm reading between the lines here, but I wonder whether Coopey's presence on the board and long bitter memories of the woolen mill scheme were a hindrance to the Columbia Highlands operation, and they brought in a respectable outsider to be the public face of the struggling project going forward.

There is almost no further news about the company after that. A1922 public notice from the Secretary of State's office listed it among a large number of companies that had not maintained a current business license, or paid any fees, or made any required filings with the state over the past two years and were hereby officially dissolved. After that, the very last we see or hear of the company is a 1933 business item simply listing it under "dissolutions", with no indication of what happened during the intervening eleven years, other than the company name being all over that 1927 map. Did the 1922 notice finally get the attention of the company's lazy lawyers, who went back through the company's unopened mail pile and found the relevant "final notice" letters and somehow got back in the state's good graces? Did the dissolution order get tied up in an endless court case for a decade and change, without making the newspapers at any point? Or did various authorities just neglect to follow up on the 1922 order for all that time? July 1933 would've been during the initial burst of New Deal legislation, as it was becoming abundantly clear that 1920s laissez-faire business was on its way to the dustbin of history; maybe the state or the county figured it was time to tidy up some zombie corporations and other loose ends, before the feds did it for them. I do wish the company had at least managed to build a few of those trails before cratering, since (per the OregonHikers threads above) there still isn't a reasonable way for ordinary hikers to visit the "hanging gardens" along Dalton Creek.

That 1933 item is followed by another eleven-year gap, as we jump forward to the next historical map I could find. The 1944 Metsker map of the area is essentially identical to the 1927 one, but with the former Columbia Highlands properties now owned by a Catherine B. Fairchild, about whom I can find almost no information. The 1927 map showed the name "Fairchild" on a small lot along the highway. And if you look closely at the 1944 map you can see where someone applied whiteout in a few spots, replacing "Columbia Highlands" with the name of the new owner, suggesting this was either a recent development, or the news was slow in reaching the Seattle offices of "Metsker the Map Man"

Other than names on maps, the only news item I could find with a matching name or initials was a 1926 traffic item noted that a Mrs. C.B. Fairchild, of Aberdeen, WA, had broken a few ribs when her car flipped on a gravel road along the Washington Coast. This was part of a long list of traffic accidents and injuries around the region, so if somehow you're ever sent back in time by a century or so you might want to make a note to avoid driving or riding in cars if you can, because it sounds quite dangerous. This item was just below a group photo of the new state Republican committee, which (quite unlike the present day) had 8 female members out of 18 total. You can still tell it's the GOP, though, because the photo is 100% white, and everyone in it is scowling at the camera. Below all the traffic gore and mayhem, another item concerned a lobbying campaign to have a Three Sisters National Monument declared, which still hasn't occurred nearly a century later. The area does get National Park-level visitorship, but still doesn't have a budget or protection level to match. Or at least not yet.

But back to our story, specifically a 1952 front page story. It seems the Fairchild estate had been foreclosed upon a few years earlier for unpaid back taxes, with the land going to Multnomah County. The controversial part was that the county had then sold off large tracts of the land to private buyers -- including 600 acres in the general area we're visiting right now -- without first asking the state parks department whether they wanted any portion of the land. The county seems to have been caught flat-footed by the controversy; the head of the county land office explained that notifying the state wasn't his job, and in general the county preferred to get land back into private hands and back on the tax rolls, and besides they might have mentioned the Gorge land in passing while talking to the state about something else, so it was really the state's fault for dropping the ball. That didn't go over very well, and he ended up promising to notify the state first if any more Gorge properties ended up in county hands. Meanwhile the new owners in the area -- a Mr. & Mrs. Calvin C. Helfrich, an elderly couple who had picked up the property back in 1949 -- had already logged much of their acreage, and were talking about building summer cabins in the area, and had applied for water rights on Dalton Creek, echoing a few parts of the earlier Highlands and woolen mill efforts.

Later in October 1952, the Helfriches -- possibly stung by the recent public outcry and bad press -- donated 30 acres of the property to the YMCA to be used as an Indian Guide camp to be known as "Camp Helfrich". They also gave an adjacent half-mile of highway frontage to one of their sons, but the article doesn't specify in which direction so I don't know whether that included the Backstrand Road property or not. The article notes that both properties were still timbered, unlike much of the surrounding area. So the earlier Shepperd donation turns out to have been a total red herring, and I have no idea what happened to the land from that donation or even where it was, exactly.

Now that I had an actual name for the camp, I figured I could just put "Camp Helfrich" into Google and the library's newspaper database and the rest would be easy, just with a start date of 1952 instead of 1919. And once again I was surprised by how few results came back. First off, we have a 1953 fundraising campaign for the new camp, with a cringey photo of beaming white kids in pretend-Indian garb. And not long afterward, a 1954 classified ad offering the remaining 550 acres for sale at $40/acre. Which sounds like a good deal until you realize the 1949 foreclosure sale had privatized the land at just $8/acre. The ad may have had the desired effect though; it only ran once, and the State Parks department bought most of the land in 1955. 403 acres changed hands this time, including Mist Falls and Angels Rest, but not the land right around the new summer camp. The article doesn't mention what the state ended up paying per acre.

In 1959, a different donor gave $10k to the local Indian Guide program. A YMCA spokesman said they might use some of the money for a new longhouse building. Which, however, would be located at Camp Collins, their much better-known youth camp next to Oxbow Park, and not their supposedly dedicated Indian Guide camp further east, which wasn't mentioned anywhere in the article.

Two small Oregon Journal news items in 1958 and 1963 alerted parents about upcoming summer day camps at Camp Helfrich, along with a whole galaxy of other summer camp options. The 1958 notice said swimming was on the agenda, though it beats the heck out of me where you could put a swimming pool or a pond, or really any part of a summer camp for that matter, in this kind of terrain. Maybe it just wasn't a very good site for a summer camp, I dunno. The 1963 mention is the last newspaper item I could find about the camp, and that's where the historical record (or that portion of it that I can find on the internet for free) just sort of ends. Inconveniently none of the news items about the camp included a map of it or even gave a street address, so I don't even know how people got there from the highway, whether Backstrand Road once doubled as the camp entrance, or if the entrance was somewhere else and it's just been erased so well that there's no trace of it on the LIDAR map anymore.

The really puzzling thing about all of this is the complete lack of Google search results about the camp. That honestly surprised me a lot more than the lack of news items. I figured there would at least be a handmade web page from 2001 about a the place, or an Angelfire or Tripod site, with Boomers waxing nostalgic and swapping memories of their summer camp days, maybe even with a few teen crushes finally hooking up half a century later. But no dice. Then I checked the Wayback Machine in case those pages had been on Geocities or some other long-deleted location; I even checked Facebook in case there's a private FB group out there for camp alumni or former counselors, or just somone posting a photo or mentioning the place in any way, and I don't even like Facebook and trying to do a useful search there is even harder than getting straight answers out of 2021 Google. If nobody's nostalgic about an old summer camp, did the place ever really exist? I'm only mostly joking here. If you just tell everyone that signups are already closed, and the waiting list's full, whenever anyone tries to register their kid or to volunteer, you could probably keep a phantom summer camp on the books for a fair number of years before anyone caught on, or you got bored of the charade. I'm not sure why somebody might do this, maybe as part of an elaborate tax dodge, or as a cover story for a secret CIA sasquatch lab, that sort of thing.

Another more disturbing possibility is that the camp was 100% real, but was home to history's most successful summer camp slasher, just like in the movies but worse, and it all got covered up, and even now the few survivors are still being threatened or bribed to stay quiet. Call me a former 80s teenager if you like, but when I see an abandoned summer camp and a mysterious house in the forest next door with "666" in the street address, I can't help but draw a cinema-based conclusion or two. I mean, it doesn't strike me as the most likely real-life explanation; the camp was probably just surplus to requirements after the postwar baby boom subsided. It's just that it's hard to explain how an entire summer camp has been completely forgotten, poof, when it ought to still be within living, non-suppressed, memory of at least a few people out there.

So that's your writing prompt, o Gentle Reader(s): If you once attended Camp Helfrich and have fond (or otherwise) memories of it, feel free to leave a note below. Or if you didn't, but heard tales of what happened to the kids who did, feel free to drop that into the comments too. Or if you've been on the run from the secret CIA sasquatch lab since 1962 and want to finally tell your strange but 100% true story, I'm all ears. And while I'm lobbing questions out there, if you have any idea why the road's called "Backstrand Road", I'd be really curious about that too, since I found absolutely no info on the subject, and the name appears nowhere in any of the maps or news stories I've seen about the area.

Thx,
  mgmt.

Untitled (1978)

Some of you might remember that I used to do a lot of public art posts here a few years ago. That's not really where I'm focused right now, but I still have a few sitting around in drafts, so don't be surprised if a few posts like this one show up among all the semi-rugged outdoor stuff every so often. This time around I've got a few photos (as in exactly three photos) of another Lee Kelly sculpture I stumbled across a while back. This one is fairly small and sits outside the west entrance to St. Vincent Hospital in Portland's West Hills. I was picking someone up at the time, and they were only interested in going home, and I can't exactly ask people to wait while I work out the best camera angles for maximal artsiness, and I'm not up for making special trips and visiting hospitals for the art during a pandemic.

Like a lot of things Kelly made in the 70s, this one simply goes by Untitled. One of the photos clearly shows a date of 1975 on it, and this post originally had 1975 in the title, but a walk/bike/drive tour brochure from the Portland Art Museum's 2010 Kelly exhibititon has a date of 1978 on it. Kelly was in the loop on this retrospective so presumably he would know the right year. Maybe that's the year it sold, versus the year it was made, I dunno. More importantly, there's already a much larger Untitled (1975) of his out there, albeit located in a park in Seattle. Which makes me want to go with 1978 just for the sake of disambiguation. And neither of these should be confused with another Untitled circa 1974, outside a bank branch at NE 72nd & Fremont, or the Untitled (1973) at the Washington State Capitol in Olympia, or the Untitled Fountain that's picked up the name "Kelly Fountain" over time, on downtown Portland's transit mall. That's a lot of Untitleds, and I'm sure I'm just scratching the surface here. But in all fairness, if I was called upon to come up with names for them, I have no idea how I'd go about doing that. Maybe just randomly generate some names, or train a neural net on a bunch of modern art names, and invite people to people read whatever they like into the results, I dunno.

.

Donohue Creek Trail

View Larger Map

Next up we're checking out the obscure Donohue Creek Trail, in the Bridal Veil - Larch Mountain corner of the Columbia Gorge. It begins off Brower Road a bit north of Pepper Mountain, and if you don't recognize those names it's a clue as to why this is such an obscure trail. The trail heads east from there, eventually crossing its namesake creek and then joining an equally obscure north-south trail that I can't find the name of. Most of the trail is on Forest Service land, but the trail isn't an official USFS trail. Most of the trail looks exactly like a single lane gravel logging road, but you also won't find it on a list of official Forest Service roads, or official county roads, or any sort of road. Officially it doesn't exist at all, and yet here it is, so here we are.

The name originated with Our Mother The Mountain, a local cycling website, and at least three variants of a route they've dubbed "The Dark Larch". Lately someone's been adding these recently-coined names to OpenStreetMap where non-MTB people can stumble across them. Either on OSM itself or any site that uses it as a base map layer, which is how I bumped into it on AllTrails. A lot of these names are a bit... overwrought, and tend to elicit eyerolls when they show up in the OregonHikers forums -- like, the trail OregonHikers field guide calls the "Buck Creek Trail" (or the "Buck Creek on Larch Mountain Hike" due to the vast number of creeks named Buck Creek around the Northwest) is known as the "Dark Larch Wizard Trail" under this alternate naming scheme. My sense is that in the local hiking world, you don't call something a "wizard trail" unless it leads you to wizards, or at least a nice view of wizards in the distance, or maybe a place where there used to be wizards before the last clearcut. You and your hiking buddies can agree that the real wizards were the friends we made along the way, but no, that doesn't really count.

Going a bit further back, I gather someone named Donahue was once big in the timber business in this area. Besides the creek that this trail goes to, there was once a mill town named Donahue somewhere south of Larch Mt. Road, and a Donahue Road that heads south off Larch just east of Brower Road. This was a former county road built in 1889, and vacated in 1979, and is now a gated Weyerhaeuser access road popular with MTB riders. But that's an old road for a different day, or possibly never, since I'm not entirely sure that biking on Weyerhaeuser's roads is strictly legal. I'm not trying to scold anyone here; I'm just saying that if you're on a bike you can outrun corporate security goons if they're on foot, and outmaneuver them if they're in trucks, and do cool BMX tricks the whole time just to make the security dudes even angrier. That doesn't work so well if you're just hiking, unfortunately.

I'm not sure who built the "Donahue Creek Trail" here. I have found precisely zero useful information about the road and I don't know whether it was built by a previous private owner before the Forest Service, or whether the USFS built and then decommissioned it, long enough ago that you can't find any useful information about it online. But the road still exists other than a bit of superficial decommissioning right at the trailhead, just enough so it's basically invisible from Brower Rd. if you don't already know it's there, and it's effectively blocked for trucks and maybe for ATVs. But you can tell why it was built just by looking at it, going by the dimensions -- wide enough for a log truck, not wide enough for two-way traffic -- and by multiple areas along the road where all the trees are obviously the same age (and you can still see the decayed old stumps of much larger trees).

You can also tell by how road is laid out, with a main road and a couple of side branches off of it that look promising but just sort of dead-end after a while without really going anywhere. That's the problem with a lot of logging roads, and a big reason why you can't just turn them all into trails: The only interesting place they went was to a grove of valuable conifers, and they were all turned into 2x4s many decades ago, and there's no longer any reason for anyone to use the road. But roads don't just go away when they're obsolete. To be useful in the first place, a bunch of grading and steamrolling has to happen, followed by covering it in a layer of gravel to ensure nothing grows there. And that works remarkably well, and keeps old roads largely intact for decades on end with zero maintenace and no further traffic. Which is great right up until you realize you don't want all these roads after all and you'd like to be rid of them. That's when things get expensive. Here and there the USFS will do a more thorough decommissioning and "obliterate" the road -- that's their official term for it -- which means you break up and remove the old roadbed, pull up any culverts under it, and generally make the entire length of the road unusable by all vehicles. I've seen figures to the effect that this can cost up to $10k per mile, and Oregon alone has over 70,000 miles of Forest Service roads. Even we assume that maybe 20k miles of road are keepers, that's still around half a billion dollars to really get rid of the others, and Congress has never seen fit to allocate anything close to a down payment on that. And that's without taking any other states into consideration, and without doing anything about surplus roads on BLM, state/local, or private land. I've never seen even a ballpark figure for how many miles of those exist, quite possibly because nobody knows.

The trail has two trailheads on the west end: The one on the map above, if you can see it, and another south of there near where Brower Rd. crosses Young Creek. The north one might be easier to find from the road if you don't know where to look, and it's the only trailhead shown on OpenStreetMap, but the south one has space to park and not be in a ditch or halfway in the road, so I went with it. If I'm not mistaken, the first 800' or so from the north trailhead is a former county road / right of way. Seems that when the county closed off the old Road 458 -- the longer, original route of Brower Rd. -- they forgot to check whether everyone who lived along it also had legal access to the new road. At least one person wasn't, and after a few years of sort of trespassing on the land of an absent landowner nearby (a local cookie and candy tycoon) he filed a survey asking the county to build him a driveway across an uncooperative neighbor's land, in compensation for their earlier screwup. Though also proposing that the county butt out if he was able to cut a deal with said neighbor. I don't know how the dispute got resolved, but one way or another he got his driveway. And at the end of those 800 feet, you can still sort of tell where his cabin used to be, at the spot where the trail route abruptly turns 90 degrees and heads south instead of east.

The road meanders east from the trailhead and then sort of peters out as you near Donohue Creek, about two miles in (not counting wandering down side roads to see where they go) . I don't know if this was the east edge of the logging operation the road was built for, or maybe there used to a be a bridge here, I'm not really sure. At this point a real trail -- not an old road -- heads downhill to the creek and up the other side. I turned around at the creek, but the trail continues up the far bank and ends in a junction with a meandering, unnamed north-south track that connects to Larch Mt. Road on one end and ends somewhere near Bridal Veil Creek on the other. I wasn't feeling quite that ambitious when I visited. Plus that route puts you on private timberland outside the National Scenic Area boundary. Which is actually ok here -- the company honors the traditional social contract about public access, at least as of 2019, the most recent year I've found documentation for. On the other hand that area was logged within the last few years, so it's probably not a scenic gem right now.