My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
REP43525
DRMS
>
Back File Migration
>
Report
>
REP43525
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/25/2016 12:45:45 AM
Creation date
11/27/2007 9:56:03 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1980007
IBM Index Class Name
Report
Doc Date
3/28/1997
Doc Name
FAX COVER
From
WRIGHT WATER ENGINEERS INC
To
DMG
Permit Index Doc Type
MINE INFLOW REPORTS
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.
/
6
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
MAR. -28' 97 (FR11 15:19 WRIGHT WATER <br />TEL:303 480 1020 <br />MEMORANDUM <br />TO: Colorado Division of Minerals and Geology <br />Dave Beny and Mike Boulay <br />Via FAX: 832-8106 <br />FROM: Wright Water Engineers, Inc. <br />Jonathan Jones, Gary Witt and Jonathan Kelly <br />DATE: March 28, 1997 <br />RE: Brief S„n,n,ary of Mazch 12, 1997 Meeting <br />P. 002 <br />Note: Because many of the issues that were discussed at the meeting are dynamic in nature, . <br />new data and other information continues to become available. Consequently, since additional <br />data and other information has become available since March 12, we felt tha[ it would he <br />benef cial to provide a status update on relevant topics. <br />Thank you very much for meeting with us on Mazch 12. We greatly appreciated the wide <br />ranging and frank discussion. We aze pleased that your general initial reaction to our March 7, <br />1997 Draft Technical Memorandum entitled Probable Hydrologic Consequences Technical <br />Revision Summary was favorable. We recognize that as you review the document in more <br />detail, along with the full Probable Hydrologic Consequences (PHC) Technical Revision <br />document, specific questions will arise that Wright Water Engineers, Inc. (WWE) and Mountain <br />Coal Company (MCC) will need to "officially" respond to. Nevertheless, it was very helpful to <br />learn that our cuaent analysis of PHCs appears to be headed in the right direction and that <br />WWE and MCC are generating the kind of information that you require. The purpose of this <br />memorandum is to briefly s~~**+*~a~ze the highlights of our March 12 discussion. <br />We began the meeting by noting that there aze many "blanks" within the Technical <br />Memorandum that cannot be filled until the necessary data aze organized and analyzed. We <br />indicated that MCC had carefully reviewed the Draft Technical Memorandum and that they <br />were confident that the PHC data collected during 1996 support the many findings and <br />conclusions in the Mazch 7 Draft Technical Memorandum. On the final version of the Technical <br />Memorandum, which WWE and MCC plan to submit to you with the PHC Technical Revision, <br />the necessary back-up data will be provided. Moreover, if some of the language, findings and/or <br />conclusions in the Draft Technical Memorandum need to be modified once the data have been <br />analyzed, W WE and MCC will update the memorandum, accordingly. <br />Update: Following our March 12 meeting, Jonathan spent the next two days a! the mine <br />working with MCC staff to compile and interpret key water quality data for 7996. In shore, the <br />data support the conclusion that, although there were measvrahle changes in North Fork flow <br />and water chemistry due to mine discharges, there were no adverse impacts to beneficial vse.s ur <br />downstream users as a consequence ofMCC's discharges to the North Fork in 1996. The basis <br />for this conclusion will be included in the final version of the Technical Memorandum. <br />OC <br />W <br />W <br />Z <br />v <br />Z <br />W <br />m <br />W <br />a <br />3 <br />H <br />V <br />ee <br />.~ <br />
The URL can be used to link to this page
Your browser does not support the video tag.