My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2014-02-24_REVISION - M1986015
DRMS
>
Day Forward
>
Revision
>
Minerals
>
M1986015
>
2014-02-24_REVISION - M1986015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/16/2021 6:05:41 PM
Creation date
3/12/2014 1:46:41 PM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
M1986015
IBM Index Class Name
REVISION
Doc Date
2/24/2014
Doc Name
Response to preliminary adequacy review TR02
From
Bishop Brogden Associates
To
DRMS
Type & Sequence
TR2
Email Name
TC1
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.
/
16
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
Timothy A. Cazier, P.E. <br />February 24, 2014 <br />Page 2 <br />If this construction period does not coincide with the lower groundwater elevation, <br />please provide an explanation for the observed data. <br />a. Response: From discussions with Transit Mix and review of historical DRMS <br />filings, construction of the slurry wall began in October 2008, and was completed <br />January 2009. The approximate timeline for the beginning of construction is <br />documented in the November 2008 Annual Report submitted to the DRMS <br />(available on DRMS Image Documents and attached here as Figure 6). <br />Dewatering associated with mining processes was initiated inside of the slurry <br />wall at about this time, which accounted for the drop in water levels inside of the <br />slurry wall observed in Well Nos. MW -1, MW -2, MW -3 and MW -5. <br />b. Also, mining and dewatering was occurring outside of the slurry wall in the <br />northeast corner of Phase 2 from approximately September 2008 through June <br />2009. These mining and dewatering activities account for the drop on water level <br />observed in MW -6 and in the residential wells along 25th Lane. Note that the <br />water levels in the residential wells began to recover in about July 2009 when <br />those mining and dewatering activities stopped in the northeast corner of Phase 2 <br />outside of the slurry wall. By July 2009, MW -6 had been mined out and water <br />levels were no longer recorded from this monitoring well. <br />3) Comment: There is another precipitous drop (—]Oft) in groundwater elevation for four <br />of these same wells (e.g., MW -1, MW -2, MW -3, and MW -5) beginning about July 2009. <br />Please provide an explanation for the observed data. <br />a. Response: More aggressive dewatering inside of the slurry wall was initiated in <br />about July 2009 in preparation for the 90 -day liner performance test, which was <br />conducted between January and April 2010. Prior to the 90 -day test the pit was <br />dewatered starting in about July 2009, which accounts for the second drop in <br />water levels observed in MW -1, MW -2, MW -3 and MW -5 located inside of the <br />slurry wall. <br />It should be noted that starting in June 2009; additional monitoring wells (MW- <br />101, MW -102, MW -103 and MW -105) were constructed outside of the slurry <br />wall which document the difference in water level inside and outside of the slurry <br />wall. These wells were used to document the difference in ground water level as <br />part of the liner performance test. <br />4) Comment: The data for MW -6 ends about March 2009. Is this well still functional? Was <br />it abandoned properly? Please provide abandonment documentation. <br />a. Response: MW -6 was located in an area that has been mined through, and <br />therefore the well no longer exists. Documentation of the abandonment status of <br />MW -6 has been filed with the Division of Water Resources to document that the <br />well no longer exists. The abandonment report is attached for your reference. <br />www.bbawater.com _- <br />
The URL can be used to link to this page
Your browser does not support the video tag.