07.09.2014 Views

Alafia River Minimum Flows and Levels - Southwest Florida Water ...

Alafia River Minimum Flows and Levels - Southwest Florida Water ...

Alafia River Minimum Flows and Levels - Southwest Florida Water ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.8 Short-Term Compliance St<strong>and</strong>ard for Buckhorn Springs Main<br />

For the Buckhorn Creek/Buckhorn Springs Main system, PHABSIM analyses<br />

yielded a prescribed flow reduction of 15% for all months when run using<br />

Buckhorn Spring flow data, corrected for withdrawals. When using Buckhorn<br />

Creek flow data, corrected for withdrawals, the prescribed flow reduction was 5%<br />

for July through October, <strong>and</strong> 10% for the rest of the year except March when a<br />

20% reduction is appropriate. Buckhorn Spring Main accounts for a clear<br />

majority of the flow in Buckhorn Creek a large majority of the time. Both flow<br />

records generate answers that are similar. A 15% reduction in spring flow<br />

compared to a 10% reduction in creek flow does not differ greatly.<br />

<strong>Minimum</strong> flow requirements for the estuarine portion of the <strong>Alafia</strong> <strong>River</strong> are<br />

currently being evaluated by the District. Because compliance with minimum<br />

flows <strong>and</strong> levels for the estuary may be contingent on flow or discharge from<br />

Buckhorn Spring, we recommend that establishment of a minimum flow for the<br />

spring be deferred until analyses for the estuarine segment of the <strong>Alafia</strong> <strong>River</strong> are<br />

completed. The report for the estuarine portion of the <strong>Alafia</strong> <strong>River</strong> will include<br />

recommendations for minimum flows for Buckhorn Spring <strong>and</strong> will consider the<br />

PHABSIM analysis already performed.<br />

5.9 Compliance St<strong>and</strong>ards <strong>and</strong> Proposed <strong>Minimum</strong> <strong>Flows</strong> for<br />

the Freshwater Segment of the <strong>Alafia</strong> <strong>River</strong><br />

We have developed short-term compliance st<strong>and</strong>ards that comprise a flow<br />

prescription for preventing significant harm to the <strong>Alafia</strong> <strong>River</strong>. Compliance<br />

st<strong>and</strong>ards were developed for three blocks that represent periods of low (Block<br />

1), medium (Block 2) <strong>and</strong> high (Block 3) flows at two USGS <strong>Alafia</strong> <strong>River</strong>, FL gage<br />

sites (Tables 5-6). During Block 1, which runs from April 20 to June 24, the<br />

allowable withdrawal from the <strong>Alafia</strong> <strong>River</strong> that may be withdrawn for<br />

consumptive-use is 10% of the daily flow as measured at the USGS Lithia gage,<br />

once flows exceed 66 cfs. During Block 1, it is also proposed that no withdrawals<br />

be allowed when flows at the Lithia gage are below 59 cfs <strong>and</strong> that withdrawals<br />

when flows at the site are between 59 <strong>and</strong> 66 cfs not be allowed to lower the flow<br />

below 59 cfs. During Block 2, which extends from October 28 of one year to April<br />

19 of the next, withdrawals of up to 15% of the daily flow at the Lithia gage may<br />

be allowed, with the exception that withdrawals should not be allowed to reduce<br />

the flow to less than 59 cfs. During Block 3, which extends from June 25 to<br />

October 27, withdrawals should be limited to a stepped flow reduction of 13%<br />

<strong>and</strong> 8% of flows, with the step from 13% to 8% occuring at 374 cfs at the Lithia<br />

gage. Proposed Block 3 reduction also must comply with the low flow threshold<br />

<strong>and</strong> assure that withdrawals not reduce the flow to less than 59 cfs at the Lithia<br />

gage.<br />

5-25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!