My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD01898
CWCB
>
Board Meetings
>
Backfile
>
2001-3000
>
BOARD01898
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 3:08:33 PM
Creation date
10/4/2006 7:04:25 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/21/2001
Description
Legislative Session Wrap-Up - SB 01-216 Implementation (Recreational In-Channel Diversion Rules)
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.
/
7
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 /> <br />23 <br /> <br />g. <br />. <br />h, <br />i, <br />j, <br />k, <br />I. <br /> <br />m, <br /> <br />Proofthat the Board does not have an ISF on the affected stream reach, or <br />proof that the RICD will not cause material injury to an ISF on the <br />affected stream reach; <br />Proof that the RICD would promote the maximum utilization of waters of <br />the State; <br />Proofthat the amounts requested in the RICD application are available for <br />appropriation; <br />Proof of the effect that the RICD will have on the water quality <br />classification ofthe stream in question; <br />Proof that the water quality is appropriate for the recreational uses sought; <br />Any and all required Federal, State, and local permits and the applications <br />therefor. By way of example, without limiting this condition, under the <br />federal Clean Water Act, section 404 and section 401 pennits may be <br />required; <br />A written statement from the county in which the RlCD is located, and <br />from the adjacent upstream and downstream counties, indicating their <br />support for and/or concerns about the RICD; <br />Documentation of the effects that the RICD will have on current flood <br />elevations; and, <br />Infonnation about existing gages on the affected stream, <br /> <br />n. <br /> <br />0, <br /> <br />6, Staffinput. After receiving and reviewing the infonnation provided by the Applicant <br />pursuant to Section 5 of the RlCD rules, the Staff shall provide a written report to the <br />Board, Such written report shall include recommended findings of fact and a Staff <br />recommendation, Staff shall provide the Applicant with a copy of the report. If the <br />Staff determines that the Applicant has not provided adequate information under Rule <br />5, the Staff shall notity the Applicant of such deficiencies, The Applicant shall have <br />seven days from its receipt of such notification to provide the necessary infonnation, <br /> <br />. <br /> <br />7, Findings without a hearing, If no party has requested a public hearing, the Board may <br />adopt the Staff's recommended findings of fact and recommendation at any regularly <br />scheduled or special meeting of the Board, Within 90 days after the closing of the <br />period for filing of statements of opposition, pursuant to section 37-92-102(6)(c), the <br />Board shall report its findings to the water court for review. Said findings shall be <br />based on the record, The record shall include all submissions to the Board by the <br />Applicant, by the Staff, and by any party, <br /> <br />8. Reuuest for a hearing, Any party may request that the Board hold a public hearing <br />regarding a RlCD, Such requests must be submitted, in writing, to the Board office, <br />within 10 days after the closing of the period for filing statements of opposition. <br /> <br />9, Hearing Procedures, Once a hearing is requested pursuant to Rule 8 of the RICD <br />rules, the Director shall appoint a hearing officer to set the date of the hearing and <br />establish the procedures by which evidence will be offered. <br /> <br />. <br /> <br />3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.