Update from USAC

USAC (Utah Steam Access Coalition) sends a news letter once and while and this message was sent today.  If you are not subscribed to the news letter then get on it!

This issue is ours to Win.


The next Legislative Session begins on January 27th. So why are we contacting you so early? The answer is simple – we’ve learned from our experience on the Hill, and this year it’s going to be different. This year, we’re contacting you early, and we will be contacting you often. This year we want to see our compromise legislation become law.


Last year, our voices were heard. HB68 was defeated, and this issue was single-handedly the most talked about at the Capitol. We have our legislator’s attention, and we need to keep that momentum moving forward. Over the next few months, we are going to lay out a detailed but simple plan to keep this conversation going.


Here’s 2 quick steps that you can do right now!


Step 1 – we need you to look up your legislators, and shoot them an email to open the discussion. Tell them that you support the Stream Access Compromise. We need you to know who they are, and they need to know who you are. Click the link to look them up: http://le.utah.gov/GIS/findDistrict.jsp


Step 2 –  Most importantly, if their names are on this list, please contact us immediately. 


Those legislators on this list have either never voted on the stream access issue, or voted against us in 2010. It is of critical importance that we get the opportunity to speak with them. In order to do that, we need you, their constituents, to tell them that this issue matters.


This issue is solvable. Contact your lawmakers, advocate compromise, and let’s solve this issue once and for all. Keep an eye on your email for the next move in the coming weeks. We stand 3,300+ strong, and we can do this!


Board of Directors

Utah Steam Access Coalition



, , , ,

One Response to “Update from USAC”

  1. David Says:

    I recently signed up with USAC but am still having a hard time understanding exactly what is going on. I’ve read the USAC compromise language. How specifically does the compromise language differ from what is currently in place?


Leave a Reply