My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
GENERAL42614
DRMS
>
Back File Migration
>
General Documents
>
GENERAL42614
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 8:11:22 PM
Creation date
11/23/2007 11:53:15 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1981044
IBM Index Class Name
General Documents
Doc Date
6/29/1984
Doc Name
REVIEW OF EMPIRE ENERGY CORP RESPONSE TO STIPULATIONS 2 4 5 AND 6 FOR EAGLE NO 5 AND 9 MINES
From
MLRD
To
SANDY EMRICH
Permit Index Doc Type
STIPULATIONS
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.
/
2
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
-z <br />In addition to the three adjudicated springs discussed above, several <br />other springs are included in Empire's hydrologic monitoring program. <br />These are located on Map IV-13 and are identified as the North, East and <br />South Springs, and the Williams Fork No. 1 Strip Pit discharge. On <br />pages III-55 and 56 of the permit document, Empire has proposed to cease <br />monitoring the North, East and South Springs. <br />On page 4 of the 1983 Annual Hydrologic Monitoring Report it is stated <br />that monitoring of the East Spring was terminated in November 1983 and <br />on Table 24 of the report it is stated that monitoring of the South <br />Spring was terminated in November 1983. Data on these springs is <br />missing from the 1st Quarter 1984 Hydrologic Monitoring Data submittal. <br />No formal written approval for any spring monitoring reductions or <br />terminations has been granted by the Division. In order to clear this <br />matter up, I suggest that Empire Energy submit a technical revision to <br />the permit (as is required under Rule 1.04(136)), requesting the <br />monitoring reductions or deletions they feel are warranted. Prior to <br />this submittal, I would recommend a meeting with them to discuss the <br />proposed changes. <br />Also, it is somewhat unclear from the information on file whether or not <br />the North Spring and the Lippard Spring I share the same source, and at <br />what location this spring or these springs are being monitored. This <br />item needs to be clarified by Empire. <br />D. This request was for quarterly submittal of all hydrologic monitoring <br />results. Revised page IV-121b reflects the commitment by Empire Energy <br />to submit all hydrologic data on a quarterly basis. <br />Stipulation No. 5 <br />This stipulation directs Empire Energy Corporation to submit annual hydrologic <br />reports. The first such report covering the calendar year 1983 was submitted <br />on time. Review of this report will be discussed in a forthcoming memo. <br />Stipulation No. 6 <br />This stipulation requires Empire Energy Corporation to submit a report on all <br />overburden proposed to be used as plant growth media. Empire has submitted a <br />report for overburden from the 5A Portal area. All items within the <br />stipulation have been addressed in the report. Samples from four locations <br />were analyzed at 6-inch depth increments down to 36 inches. Results of these <br />analyses indicate that, except for nitrogen and phosphorus levels, the <br />overburden material sampled would be suitable as a plant growth medium. <br />Nitrate nitrogen levels are somewhat low (mean value for all samples = <br />3.3 ppm); however, given the organic matter concentrations of between 6 and <br />29%, this may not be a significant problem. Phosphorus levels were all less <br />than 2 ppm in the samples analyzed. Empire has stated in the report that at <br />the time of seeding, 30 lbs/acre of P205 will be added to the material. <br />The response to this stipulation is adequate. <br />/ep <br />Doc. No. 2410 <br />
The URL can be used to link to this page
Your browser does not support the video tag.