My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD01135
CWCB
>
Board Meetings
>
Backfile
>
1001-2000
>
BOARD01135
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 2:58:29 PM
Creation date
10/4/2006 6:50:31 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/22/2000
Description
ISF Section - Proposal for Injury with Mitigation - Case No. 3-99CW034, Nearburg
Board Meetings - Doc Type
Memo
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />_. '-- .-'....., <br /> <br />.:. '.'1 <br />.'2;1 <br /> <br />Current Status <br />Shortly after the March 2000 Board meeting, staff from the CDOW and the CWCB met with the :." <br />Applicant's engineer to discuss the Board's concerns with the Applicant's original plan for <br />Injury Accepted with Mitigation. The CWCB staff also wrote letters to the Applicant on April 4 <br />and April 20, 2000 (see Attachments 2 and 3) which summarized the outstanding issues staff <br />believed would need to be addressed prior bringing a final proposal back to the Board. Those <br />letters also extended an opportunity for the Applicant to meet with staff to discuss these concerns <br />and outlined the deadlines that the Applicant would need to meet in order to bring a final <br />proposal back to the Board at its May 2000 meeting. <br /> <br />Sally Hatcher, the Board's attorney in this case, received an "interim response" to the staff's <br />letters from Erich Schwiesow, the Applicant's attorney, on April 28, 2000 (see Attachment 4). <br />That letter indicated that the Applicant would be presenting an Injury Accepted with Mitigation <br />proposal AND a pre-existing practice analysis at the Board's May 2000 meeting. <br /> <br />On May 8, 2000, CWCB and AGO staffs received the Applicant's revised proposal for Injury <br />Accepted with Mitigation (see Attachment 5). The Applicant's current proposal is a hybrid of an <br />injury with mitigation proposal and a proposal that would require the CWCB to recognize certain <br />existing practices. As you know, section 37-92-102(3)(b), C.R.S. provides that: "Any such <br />appropriation [of the CWCB] shall be subject to the present uses or exchanges of water being <br />made by other water users pursuant to appropriation or practices in existence on the date of such <br />appropriation, whether or not previously confirmed by court order or decree." , <br /> <br />The proposal states that "diversions into Caster Ditch under the proposed schedule represent . <br />considerably less depletion to Trout Creek than was present under the historical practice." Based <br />on this claim, the Applicant has proposed the following diversion schedule: <br /> <br />WINTER 00/1-4/30) <br />Trout Creek at Caster Ditch <br />Measurement Point Allocation <br />~12c~ 2c~ <br /><12c~ Ic~ <br />S; 6 cfs 0 cfs <br /> <br />SUMMER (5/1-9/30) <br />Trout Creek at Caster Ditch <br />Measurement Point Allocation <br />~ 28 cfs 4 cfs <br /><28c~ 2c~ <br />s;17c~ I c~ <br />S;15c~ Oc~ <br /> <br />The Applicant's proposal incorporates a more detailed quantification of their claimed historic, <br />albeit undecreed, practice of diverting water at the headgate into Rankin Reservoir, and then into <br />Caster Ditch, and Lemon Drop Ditch, on a year-round basis. They use the quantification of this <br />historic practice as grounds for allowing diversions to continue into Caster Ditch and Pond at <br />times when the Board's Trout Creek instream flow water right is not being satisfied. The <br />Applicant has provided several signed affidavits from land owners and others individuals, who <br />claim that they are familiar with the historic diversion practices, to substantiate this claim. <br /> <br />. <br />
The URL can be used to link to this page
Your browser does not support the video tag.