My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
INSPEC42531
DRMS
>
Back File Migration
>
Inspection
>
INSPEC42531
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 9:46:06 PM
Creation date
11/18/2007 11:27:04 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1980002
IBM Index Class Name
Inspection
Doc Date
5/19/2004
Doc Name
Proposed Decision & Written Findings for Reduced Inspection Frequency
From
DMG
To
Gunnison CountryTimes
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.
/
4
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
some small erosional features but overall, the general condition of the slope is stable. Vegetation <br />exists on most of the inslope but it is not enough to prevent erosion, but the embankrnent is <br />stable. The crest of the pond is approximately 10 feet wide for the entire length. The crest of the <br />pond is stable and a 25 foot portion has been lowered to act as the emergency spillway. There <br />aze no signs of cracking ,settling, subsidence, or any other signs of instability. The downstream <br />slope is in very good condition. Vegetation on the pond's outslope is moderate. No signs of <br />seeping, piping or wet spots have been noticed throughout the last five yeazs. The outlet is a 4" <br />fiberglass pipe that empties into a natural gully. The overall condition of the outlet is <br />satisfactory. Rock riprap is present to lessen the energy and erosional effects of the water exiting <br />the pipe. As noted above, the emergency spillway is a transverse depression in the crest that <br />could convey water over the top of the impoundment. However, since the pond truly is <br />oversized, the likelihood of water ever flowing over the crest is very minimal. Finally, as built <br />designs show that the pond was built as designed and certified by a professional engineer. <br />There aze no existing highwalls or known subsidence features associated with the Ohio Creek No. 2 <br />Mine <br />The Ohio Creek No. 2 Mine is not located near or above any urbanized areas, communities, <br />occupied dwellings, schools or other public or commercial buildings and facilities (Rule <br />5.02.2(8)(a)(v)). The nearest occupied dwellings aze approximately 1/3-mile away from the mine. <br />The one sediment pond continues to provide sediment control for the O.C. No. 2 Mine. The <br />vegetation in the area has been growing for eight years and the cover appears to be sufficient to <br />prevent any significant erosion from occurring at either azea. This statement is based on the fact <br />that no significant rifling or gullying has taken place at the site since initial reclamation in 1996. <br />On 25 April 2000 the Division and the Office of Surface Mining (OSM) conducted a joint <br />inspection of the Ohio Creek No. 2 Mine to determine the quality of reclamation as it related to off- <br />site impacts and specifically off-site sedimentation. The Division and the OSM found that no such <br />impacts existed. <br />The reclamation work at the Ohio Creek No. 2 Mine was completed by the Mined Land <br />Reclamation Boazd (through contractors) between June and October 1996. The cost of the <br />reclamation was $19,104.50. The Division currently holds a bond of $16,505.00. <br />Based on the Division's monthly inspection reports and OSM oversight inspections from the last <br />seven years (since final reclamation) the reclaimed azeas have remained stable and show no signs of <br />instability or mass movement. These azeas of interest include the remaining pond, the backfilled <br />portals and the backfilled bench azea. In addition, the Division has rot seen any subsidence-related <br />problems at or azound the mine site. <br />
The URL can be used to link to this page
Your browser does not support the video tag.