Doesn’t Play Well With Others…

Let me start by saying that I am glad that work is finally getting done on the Rubicon Trail.

What bothers me is the complete failure to communicate.

Again, the users were not a part of the planning for this work, the users were not made aware that the work was going to take place and the users were not allowed to volunteer during this maintenance effort. Or were they?

So, the Lake Tahoe Basin Managment Unit (LTBMU) was out on the trail last week rebuilding some of the rolling dips that were put in place way back in 2000. It is my understanding that the work was funded by the Rubicon Trail Foundation (RTF), but I have not confirmed that, yet.

The photos are not the best, but I blame the sun, or the shadows. This is rolling dip (always improperly referred to as a ‘water bar’) is number one. Back in the day, 28 of these were placed to prevent water from running down the trail. Back then, each rolling dip was rock lined to prevent erosion.

Unfortunately, the LTBMU did not consult anyone before doing the work. Obviously, they know absolutely everything. They must tour the trail every spring documenting the run-off from melting snow. They must know the best building techniques to build long-lasting rolling dips. Or not.

Where to begin. Many of the rolling dips that were rebuilt, shouldn’t have been. Of the original 28, there were a good eight that should never have been placed. But Placer went overboard. So did the LTBMU.

If you drive the Middle Fork Trail up Blackwood Canyon, you’ll see some absolutely great rolling dips. They’re HUGE. But the LTBMU did not build the same rolling dips for the Rubicon. These are mostly loose river rock that will break down and not last.

More dips…

Some of the drains are dug well enough to work but others are not, or worse, don’t exist.

Again, some don’t exist…

This missing rolling dip is the old 7A designation. There is a creek on the right that doesn’t quite reach the Arizona Crossing (rolling dip #8). The water will continue to flow all the way down the trail to number 7, where it will be directed off the trail.

So, I alluded to the fact that the users might have known about this work. But the more I look at the email, the topic might have been other work.

Here’s the deal, on September 27th, the Tahoe National Forest (TNF) reached out about an upcoming work party for October 9th. It was a drain building/cleaning effort. I don’t know all of the names to whom the email was sent. But Friends of the Rubicon (FOTR) received it.

I honestly don’t know if the work party ever happened. But I do know that four of the largest four-wheel drive clubs on the Tahoe end of the trail never got the word. The Lake Tahoe Hi-Lo’s, Tahoe Donner 4-Wheelers, Sierra Stompers and the Hills Angels never sent out an email to their members about a work party. Reno4x4.com never posted about an upcoming work party.

So, who dropped the ball?

FOTR got the word. I’m not on that email list so I only assume it went out to the list as at least one person let me know they got it.

RTF knew about the rolling dip work, if they did indeed fund it. I never saw anything on their website about it. Just looking at their website, I don’t see anything about maintenance projects. There is an FOTR page.

So, how is the typical user supposed to learn about possible project in order to make comments before the project? How is the typical supposed to learn about scheduled projects in order to help out or avoid the trail that day?

It seems like nobody sees a need to get the word out. That’s disappointing as the users should know. The users should be involved. Volunteer time can be used as matching funds for grants.

If we could only talk to each other.

.

Rubicon Ronin



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s