My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2010-08-05_HYDROLOGY - M1980135
DRMS
>
Day Forward
>
Hydrology
>
Minerals
>
M1980135
>
2010-08-05_HYDROLOGY - M1980135
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 4:17:32 PM
Creation date
4/5/2011 11:27:47 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1980135
IBM Index Class Name
HYDROLOGY
Doc Date
8/5/2010
Doc Name
Augmentation Plan
From
District Court
To
Pinneo Feedlot, LLC
Permit Index Doc Type
Hydrology Report
Email Name
MAC
Media Type
D
Archive
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
33
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).
View images
View plain text
a) Beginning in 2007, UPBCC installed a meter on all the existing irrigation <br />wells that are included in its plan for augmentation, including the Booth <br />Farm Well. From 1974 to 2006, monthly pumping volumes under the Booth <br />Farm Well Right were estimates included as part of annually approved <br />substitute water supply plans submitted by GASP to the State Engineer. <br />Based upon these data, the average annual volume of water pumped from the <br />Booth Farm Well is 135 acre-feet. <br />b) Return flows resulted from the portion of historical irrigation water <br />deliveries under the Booth Farm Well Right that were not consumed by the <br />crops. Because the well provided a supplemental irrigation source, the actual <br />rate of consumption of these deliveries equaled the application efficiency on <br />the farm. Because the farm was flood irrigated, an application efficiency of <br />60 percent is reasonable, and identical to the value used to estimate the well <br />water consumptive use for the UPBCC Augmentation Plan. Therefore, <br />return flows comprised the remaining 40 percent of the volume pumped from <br />the well. <br />c) Historically no water left the farm as surface flow. Therefore 100% of the <br />return flows from irrigation historically accrued to the river as groundwater <br />flow. To maintain the historical pattern of return flows in the future, Pinneo <br />will multiply the volume of water pumped from the Booth Farm Well, which <br />is delivered via existing laterals on the Booth Farm and subsequently <br />measured at the Booth Farm Recharge Ponds, by the applicable 40% return <br />flow factor to determine the unlagged return flow obligation. Because the <br />Booth Farm Recharge Ponds is located in the area historically irrigated by <br />the Booth Farm Well, the timing of the accretion of the return flow <br />obligations will naturally match the timing of historical return flows. This <br />method of handling return flow obligations will limit the consumptive use <br />credit consistent with the methodology and assumptions used for the Booth <br />Farm Recharge Ponds. Thus, the net credit at the river from recharge at the <br />Booth Farm Recharge Ponds will simply limit credit for the Booth Farm <br />Well Right water to no more than 60% of the pumped volume. For ease of <br />accounting, during the periods of time when water from the Booth Farm <br />Well Right is being delivered to the Booth Farm Recharge Ponds for <br />augmentation purposes, no other irrigation water will be used on the Booth <br />Farm from UPBCC shares, Jackson Lake Rights or other sources of <br />irrigation water. <br />d) Accordingly, future pumping and use for augmentation and replacement <br />purposes of the average annual amount of water historically pumped and <br />consumed under the Booth Farm Well Right (i.e., 135 and 81 acre-feet per <br />year, respectively) will not expand the historical consumptive use of that <br />water right, if future pumping occurs pursuant to the terms and conditions of <br />this decree. <br />17 of 33
The URL can be used to link to this page
Your browser does not support the video tag.