Next up we're having a look at Nesika Falls, another very tall but little-known Columbia Gorge waterfall right in the middle of the main tourist corridor, a just a little over a mile east of Multnomah Falls and even closer than that to the Oneonta trailhead. If you're heading east on the old Columbia River Highway, you might notice a small parking lot with some sheer cliffs and mossy boulders behind it, and absolutely no signage of any kind to tell you why there's a parking lot here. Its most common use seems to be as a turn-around spot for tourists trying to score one of those $20 VIP parking spaces at Multnomah Falls Lodge, which may involve a slow crawl thru the tiny lodge parking lot followed by flooring it down the road (or continuing a slow crawl down the road, depending on traffic) to the closest turnaround (i.e. here) and back (i.e. here), and coming back for yet another slow crawl thru the completely full lot. A useful rule of thumb here is that if you find yourself using any driving techniques you learned during holiday shopping, you should accept that you are not currently having fun, will not begin having fun anytime soon, even if a parking spot opens up, and should probably rethink your plans for the day.
The second most common use of this lot is as unofficial (but free) overflow parking for Multnomah Falls. People who park here to use this spot as Multnomah Falls overflow parking tend to just trudge along the road, ignoring all the "No Pedestrian Access" signs along the way, including the ones on the narrow East Viaduct, and trying to duck in time every time an RV with extra-wide side mirrors rolls through. I tried that route once way back in the early 90s (as described here) and absolutely do not recommend it. What you want to do instead is look for trails heading up into the forest, and take the westbound one. There are no signs to tell you this, but this spot is an access point for Gorge Trail No. 400, the still-incomplete trail that might connect Troutdale to Hood River someday. The eastbound trail is easier to find, right at the east end of the parking lot, but it's not the trail you want right now. To find the westbound trail, cross the little road bridge or culvert immediately west of the lot, and look for a trail a few steps beyond there. When you cross the bridge, look down at the little creek it crosses. This is the same stream that forms the falls we're here to look at, so if it's just a trickle or it's dry entirely there's nothing to do but come back another day in a wetter season.
Assuming the creek's flowing, follow the trail uphill a short distance, maybe 50'-100', look uphill, and try to work out the route of that little creek as it comes downhill. If the creek's flowing but you don't see the falls, try going a bit further, or go back a bit, and look for gaps in the trees and underbrush, and keep trying until you see something resembling the photoset above.
Once you see it, look back toward the parking lot and note the large rock formation that completely blocks the view of the falls from the highway. If that wasn't there the waterfall would probably be a bit less obscure than it currently is.
After you've seen the falls from a distance and taken a few photos, continuing westbound on the 400 will take you to Multnomah Falls, specifically to the first switchback past the bridge. So you can either continue uphill to the top and skip most of the crowds, or you can head downhill, elbow your way thru the crowds, and hit the snack bar for a plate of genuine Multnomah Falls nachos, or whatever. Before choosing your adventure, look behind you at the junction. A vintage plaque, low to the ground, announces this is the "Ak-Wanee Trail", though nobody really uses that name anymore. This trail officially opened in 1978, and the name honors a young Yakima tribal member who worked on trail construction here and died in a car accident shortly before the trail opened to the public.
The trail figured in several Roberta Lowe newspaper columns over the next few years, primarily in the Oregon Journal:
- A 1979 Journal column explaining exactly how to find the unofficial and very, very steep Elevator Shaft trail.
- A 1980 Journal column explaining that the new trail had not been properly manicured yet, and was still a bit rough.
1984 Oregonian column (after the Journal went under), on hiking the 400 from Multnomah Falls through to the obscure Exit 35 Trailhead east of Ainsworth State Park. (That point marked the end of the trail until the short-lived Warrendale-Dodson segment opened a few years later, and it became the end of the trail again in 1996 after a big chunk of trail was erased by massive landslides a bit east of that trailhead.) The column mentions a dead-end bit of abandoned trail uphill from the present-day trail, built as an abortive attempt to route the trail closer to Nesika and Waespe Falls (another seasonal waterfall we'll visit as soon as I finish that post). They would certainly be less obscure if that had worked out, but we're told that the necessary blasting could have posed a hazard to cars and trains below so they dumped that idea.
The abortive spur trail seems to still exist, according to the state LIDAR map, with the trail junction located right about here. Though so far I have completely failed to find this trail at ground level. That's one limitation of LIDAR maps, especially in this part of the world: You can make out exactly what the ground is shaped like, but when you go to visit in person that ground may be under an impassable layer of brush, fallen limbs, poison oak, devils club, rusty nails, broken glass, old barbed wire, etc., and there's really no way to be sure until you get there. Another limitation is that LIDAR really just tells you that a potential creekbed intersects a cliff at a given spot and obviously can't tell you if there's any water in the creekbed.
- Also nearby, unofficially, or maybe closer to Waespe Falls next door, is the lower end of the Fire Escape trail, which is marked at the upper end by an ominous sign that reads "Fire Trail - Emergency Only". Peope often confuse it with the very similar Elevator Shaft trail which is a mile or so to the west, closer to Multnomah Falls. Even the OregonHikers Field Guide page about the Elevator Shaft manages to confuse the two. The key thing to know is the Elevator Shaft is supposed to be uphill only, while the Fire Escape is said to be down only, and for the life of me I have no idea why. I suppose it reduces the odds of people having to pass each other on these precarious routes, if nothing else. I have never done either one, but my understanding is that the main difference between the two is that the Elevator Shaft has an actual trail carved into it, with over 100 tight switchbacks, and you can see it on LIDAR and even Google Maps' satellite view, while the Fire Escape is just a talus slope that's known to be descendable in a pinch.
One unsolved mystery I have: If the bridge and maybe the parking lot date back to around 1916, and the trail only arrived in 1978, what was here before that? Was it really just a turnaround spot for heading back to Multnomah Falls all that time? I have no idea.
The name is fairly recent; it's just named after the Trails Club lodge near the creek, way up above the falls. It sort of fits with the existing pattern of real or invented Indian names bestowed on various places by non-Indians, mostly in the early 20th century. Which is not really ideal, but the lodge is about the only named landmark anywhere nearby, so I guess it'll do in a pinch. The other idea that's been proposed is some variation on "Farula Falls" or "Caddisfly Falls", as it's one of a handful of Gorge waterfalls that are home to Farula constricta[1], one of several rare caddisfly and stonefly species endemic to the Gorge. It's not a terrible name, but the thought of using it makes me sort of anxious, like I can't shake the idea that it'll attract the wrong kind of attention, from the sort of people who would happily wipe out the last survivors of an endangered species just to own the libs.
To summarize uses of either name across the interwebs: We've got two old OregonHikers forum threads in January and May 2011, followed by a 2013 thread about a then-new trails layer in Google Earth. IIRC one of those threads mentions what might be the abandoned spur trail, referring to it as a "convenient game trail". The name also appears on someone's WentHiking page and another photo linked from there. And that's about it, really.
If I'm not mistaken, under the right weather conditions this area becomes a celebrated ice climbing spot known as "New World Amphitheater", as discussed in two threads at Cascade Climbers, and featured in the Gorge ice climbing chapter of Northwest Oregon Rock. Translating their maps and names into non-climber, I thiiiink Nesika Falls freezes into "Black Dagger", while "Brave New World" is either a different route up the falls or it goes up one of several ephemeral streams immediately to the east, I'm not totally sure which. And "Blackjack" corresponds to a creek west of Nesika but I'm not 100% sure which one. I don't think I've seen any of these theoretically rather tall waterfalls actually flowing, so this is kind of a moot point, and it's why I generally don't bother with ephemeral waterfalls in this project: The only reliable way to see them would involve visiting while a major storm is in progress, which in turn means spending lots of time getting drenched and being cold and wet and miserable, which I can't recommend.
As I understand it, to be a great Gorge ice climbing spot, a place needs a couple of things: A fairly low-flow waterfall (ones that dry up in the summer are great for this) so it'll freeze all the way and not be a firehose in the face of anyone climbing it, and it should be one that runs down the face of a cliff instead of projecting outward like a lot of the major ones do, so it'll freeze on the cliff and not just make a big ice stalagmite at the base. This is not the case everywhere, btw; Helmcken Falls in British Columbia is supposed to be the world's ultimate ice climbing spot, and it's on a major river and forms a giant ice cone over the winter. But around here, if those conditions are met, then it's the taller the better. Speaking of which, I haven't seen any numbers on exactly how tall Nesika Falls is, so let's have a look at the state LIDAR map and see if we can work that out ourselves. I usually do this by trying to pick points above and below that clearly aren't part of the falls but as close to it as I can get, and subtract the altitude of one from the other. This tends to give numbers on the high side of the range but hopefully not by much.
First off -- starting at the old highway and proceeding uphill -- LIDAR says there's a small lower falls below the main one, maybe 15'-20' tall and hidden sort of behind the big rock formation here. (top; bottom). I haven't actually seen this one; it must be hidden in the dense brush back there, and you may need a machete to get a better look at it.
Then we have the main falls, which I think is what's shown in all of my photos. Given a top point at ~815', and a bottom one at 395', that gives us a 420' main waterfall. Seriously.
Then we have a number of smaller upper falls that are set back a bit from the main one and I suspect aren't visible from below. These miiight be visitable from above with a bit of bushwhacking, but I haven't tried this myself and this is not a legally binding warranty. Also, most of these drops are fairly short, and short drops on a small creek may not be very impressive in person, and your photos of them may not necessarily bring fame and fortune, just so we're clear on that. With those disclaimers out of the way, here's what LIDAR says is up there:
- Upper falls #1 (100') (top, bottom)
- Upper falls #2 (~30') (top, bottom)
- Upper falls #3 (~20') (top, bottom)
- Cascades(~50') (top, bottom)
- Upper falls #4 (~25') (top, bottom)
- Upper falls #5 (~20'?) top, bottom
- And another 20' one on a small tributary east of the main creek (top, bottom)
Just west of there, the one on the next sorta-obvious stream to the west (top, bottom) might be the "Blackjack" of the ice climbing world. It seems to drop a whopping ~550', which would be pretty impressive if there was any water at all going over it most of the year. But then, the lack of water means it erodes slower and stays taller longer, so whatever.
Before we wrap this up, let me point out a few other points of interest nearby, two of which are completely gone now, and another that never made it past the proposal stage but is kind of interesting anyway:
One of these points of interest was right by the parking lot until quite recently. The creek passes under the highway on an original 1914 bridge, or maybe it's just a culvert, and either way it's pretty small and boring. Around 1979, a local Eagle Scout decided this just wouldn't do and did some amateur masonry here as his Eagle Scout community service project, adding an ornamental bridge railing to the existing bridge. Thus reminding people why we don't usually task Eagle Scouts with civil engineering projects. Recreating the HCRH calls it the "Eagle Scout Bridge", and has a photo or two of it in its post-1979 state. There's even a photo of it in the Library of Congress archives. The National Register of Historic Places nomination for the highway labeled it a "non-contributing structure" and had a few brief and opinionated words to say about it:
Historically, there has been a structure at this crossing of an unnamed creek since the CRH's construction. The present masonry parapet walls on this small span date from the early 1980s, and represent an unsuccessful attempt to "restore" this bridge in the highway's style.
I started calling it the Monkey Jesus Bridge: In both cases a well-meaning member of the public decides to improve a thing that doesn't need improving, and... doesn't. It's said that for many years afterward, if you hung around nearby at dusk on the right evening, sometimes the ghosts of ancient Roman engineers would appear and poke at it with sticks and make cutting remarks in Latin about the crooked arches and the barbarian tribes that must have built them. It helps to remember that these guys have been guzzling wine from the same ghostly lead flagons for the last 2000 years and have become a bit irritable over the years. But that's all a moot point, because it's gone now. At one point during the pandemic there was an extended closure of the highway due to a combination of winter landslides and trying to clean them up in a full social distancing environment, and ODOT took advantage of that long closure to quietly make the 70s bridge railing vanish without a trace. There was no public outcry; in fact almost nobody noticed it was gone. And the esteemed Romans have switched to haunting the McMansions of Mt. Scott. Imagine something like Poltergeist, but the ghosts are just unreasonably angry about classical orders and the Golden Ratio, and barbarian tribes who don't even know how to build a villa properly.
- There was also an Oneonta train station or platform somewhere right around here in the early 20th century. A 1927 Metsker map has an all-caps "ONEONTA" label right around the turnout location, while the inset bit of map shows the locations of the "McGowan's Cannery", "Columbia Beach", and "Warren's Cannery" train stops, all in the Warrendale-Dodson area east of here. I haven't come across any historic photos of any of these stations, and most likely they were cheap and rustic, just enough platform so people could get on and off the train with a little dignity. The original road survey map for this stretch of the HCRH, aka County Road 754, covers the Multnomah Falls thru Oneonta Gorge area on page 2 of the PDF, and it definitely shows a train station named "Oneonta" that's separate from and some distance west of the "Oneonta Falls" label. It seems awfully strange to me that any train stop would be anywhere except right in front of Oneonta Gorge, or as close to there as is practical. There was never a town here, or farmland, or or any other reason to come here besides the famous wade-to-the-waterfall spot. Even the Oneonta Trail (which accesses the additional falls upstream of the gorge) wasn't built until the 1930s. Also note that although the tracks seem to be right next to the highway here, and it kind of looks like you could drop someone off or pick them up for their train commute into the big city, the space in beween the two is a roughly 100' cliff, and the highway engineers of 1916 neglected to put in a grand staircase to connect them.
The mystery not-a-trailhead also appears to be the exact spot where the Columbia River Highway would have intersected the never-built eastern half of County Road 625 (map pdf; ordinance pdf), since it was supposed to intersect the highway near the old train platform. This proposed road dates back to the 1890s, and the unbuilt part was a truly absurd idea. The western, built segment of road ran roughly parallel to -- and uphill of -- the Palmer Mill Road that Gorge fans may be more familiar with, which is actually a former railroad grade. The parallel country road might still exist as part of the maze of unmarked trails, tracks, and goat paths up in the Palmer Mill - Angels Rest area. The built segment ended around the location of the long-gone Palmer sawmill and its vanished mill town, and it won't surprise anyone to learn that the Bridal Veil Lumber company was the primary force behind the proposal.
From the Palmer area, the unbuilt segment would have made its way sort of northeast, descending into Multnomah Basin, albeit by a somewhat different route than the Multnomah Basin Road that was eventually built. Which brings us to the absurd part: From there, starting just east of the top of Multnomah Falls, the road would have dropped toward river level, or at least railroad level, by a series of tight, precipitous switchbacks immediately east of the unofficial Elevator Shaft trail. If you're ever tried that trail or even looked at it up close, it is very difficult to imagine how a usable road could ever be built there or anywhere nearby, especially back in the horse-and-wagon days. That segment ended right around the trailhead here, and then continued east along more or less the present-day route of the old highway as far as Elowah Falls, then home to another sawmill. The Bridal Veil timber company was behind the proposal, and some suspected that the plan wasn't to actually build the road as proposed, but to establish a public right of way across the land of nearby landowners, with the goal of eventually putting an enormous log flume through there. Some neighboring landowners were surprised to find their signatures had been forged on the petition, when they didn't actually support the proposal. One filed an objection noting that the road would be useless to him, as it was too steep for horses to climb while pulling an empty wagon.
So what next? What's the future of this place? The key thing to know is that the land is a piece of Benson State Park (like the lake next to Multnomah Falls) and is not owned by the Forest Service, and the state will probably never have the money to do anything with this place; they may not even know they own it. The lot was recently added to Google Maps as "Parking to hike to Multnomah Falls", and as that idea takes hold it'll start filling up before sunrise like every other place marked as Multnomah Falls parking. If you put up an official sign and drew attention to the place, either as Multnomah Falls economy parking or for the falls here, you would immediately have a parking nightmare on your hands, and I'm not sure where additional parking could possibly go; the other side of the road is a cliff, but (looking at street view from I-84 not quite a sheer cliff, so maybe a few parking spots could go there with a bit of creative cantilevering. And then revive the bit of spur trail so people have somewhere nearby to go instead of it just providing a longer way to either Multnomah Falls or the Oneonta area. And figure out how your signage should break it to midsummer tourists that the falls might have gone dry for the year and they really should have visited back in March while they were still semi-awesome. It would almost certainly accrue a bunch of one-star Yelp and Google reviews from the sort of tourist who doesn't get the whole "nature" thing, and thinks there's a hidden control room somewhere behind the scenes where a bored bureaucrat controls all the valves to turn the waterfalls off and on, while people at the other control panels handle the weather and the animatronic wildlife.
Footnote(s) 1. Insect stuff
More specifically, the species is known from one male and one female specimen, both collected here in April 1989, along with several collected at Mist Falls around the same time. All of them are now part of the 10 million specimen Entomology Collection at the Royal Ontario Museum in Toronto. The 1992 paper describing F. constricta is here:
Wiggins GB, Wisseman RW. NEW NORTH AMERICAN SPECIES IN THE GENERA NEOTHREMMA AND FARULA, WITH HYPOTHESES ON PHYLOGENY AND BIOGEOGRAPHY (TRICHOPTERA: UENOIDAE). The Canadian Entomologist. 1992;124(6):1063-1074. doi:10.4039/Ent1241063-6
The paper is unfortunately paywalled and I'm not sure I want to shell out $36 just to read it, JSTOR doesn't carry the journal, and unfortunately Sci-Hub has an incomplete copy of that issue, ending before it gets around to the paper in question. So that appears to be a dead end, but that's modern science for ya. Here's the abstract for it, at least:
Three new species are described in the caddisfly family Uenoidae: Neothremma prolata, from Hood River County, Oregon; Neothremma mucronata from Lassen County, California; and Farula constricta from Multnomah County, Oregon. Following examination of the holotypes of several species, misinterpretation of the male genitalia morphology of Farula wigginsi Denning is corrected, leading to the recognition of that name as a junior synonym of F. petersoni Denning. Interpretation of male genitalic morphology in the original description of F. geyseri Denning is revised. Phylogenetic relationships are inferred from male genitalic morphology for the species of Neothremma and Farula. Biogeographic patterns of the species in both genera are highly congruent with the phylogenies.
Let me just point out that coauthor Wiggins had the rare privilege of debunking Farula wigginsi, a proposed new species that someone else had named in his honor.
