My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD02156
CWCB
>
Board Meetings
>
Backfile
>
2001-3000
>
BOARD02156
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 3:12:53 PM
Creation date
10/4/2006 7:11:54 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/16/2006
Description
ISF Section - ISF Subcommittee Recommendations
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.
/
11
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 />-2 - <br /> <br />b. The Board will only accept an Injury with Mitigation proposal if: <br /> <br />I) The proponent establishes that no other reasonable alternative exists to . <br />provide full protection of the ISF water right; and <br /> <br />2) Mitigation is proposed that will allow the depletion to take place while <br />continuing to preserve or improve the natural environment to a reasonable <br />degree. <br /> <br />c. When evaluating the reasonableness of alternatives, the Board may consider economic <br />and environmental consequences of each alternative. <br /> <br />d. The Board will only consider mitigation in an area other than the affected stream reach if <br />no reasonable alternatives exist for mitigation on the affected stream reach. <br /> <br />3. Process for Submittal and Processing of Injury with Mitigation Proposals <br /> <br />The Subcommittee recommends that the Board concur with the process set forth below for <br />the submittal and evaluation of Injury with Mitigation proposals. <br /> <br />a. Staff Review. To initiate CWCB staff review of an Injury with Mitigation proposal, the <br />proponent must provide the following information in writing: <br /> <br />I) Location of injury (stream(s) affected, length of affected reach(es)) <br />2) Quantification of injury (amount, timing and frequency) <br />3) Type of water use causing the injury <br />4) Hydrologic analysis showing why full ISF protection is not possible. <br />5) Detailed description of the proposed mitigation, including any measures taken to <br />reduce or minimize the injury <br />6) Statement of how the proposed mitigation will enable the Board to continue to <br />preserve or improve the natural environment of the affected stream to a reasonable <br />degree in spite of the injury <br />7) Identification and feasibility analysis of any other alternatives considered, including <br />discussion of environmental and economic benefits and consequences of each <br />alternative <br /> <br />b. DOW Consultation. After receipt and review of the required information, staff will <br />consult with the DOW and with the entity that originally recommended the affected ISF <br />water rights(s) (if other than DOW) to determine whether additional field work is <br />necessary and to identify any scheduling concerns. Staff will request a recommendation <br />from the DOW as to whether the proposed mitigation will enable the Board to continue to <br />preserve or improve the natural environment of the affected stream to a reasonable degree <br />in spite of the injury, <br /> <br />c. Board Review. Using the two meeting process required by ISF Rule 8i.(3), staff will <br />bring the proposal to the Board for preliminary consideration after completing its review <br />of the proposal and consultation with DOW. Staff will work with the proponent and <br />interested parties to address any preliminary concerns prior to bringing a proposal to the <br />Board. Preliminary consideration by the Board may result in requests for more " <br /> <br />Flood Protection. Water Project Planning and Finance. Stream and Lake Protection <br />Water Supply Protection. Conservation Planning <br />
The URL can be used to link to this page
Your browser does not support the video tag.