My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2015-07-30_REPORT - P2012013
DRMS
>
Day Forward
>
Report
>
Prospect
>
P2012013
>
2015-07-30_REPORT - P2012013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/17/2022 9:43:56 AM
Creation date
7/31/2015 11:56:26 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
P2012013
IBM Index Class Name
Report
Doc Date
7/30/2015
Doc Name
Annual Fee, Report & Map
From
Shell Frontier Oil & Gas
To
DRMS
Email Name
THM
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.
/
11
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
MP Annual Report <br />RECEIVED <br />JUL 3 0 2015 <br />DIVISION OF REGLAMATI, <br />Permittee Name: <br />Shell Fron�OT&CM IBJ rw <br />Permit Number: <br />P-2012-013 <br />Operation Name: <br />Mahogany Research Project <br />County: <br />Rio Blanco <br />Annual Fee Due: <br />$86.00 <br />Anniversary Date: <br />August 7, 2015 <br />Permit Acreage: <br />0.00 <br />Current Bond Amt: <br />$0.00 <br />According to Colorado Statute, each year, on the anniversary date of the permit, an operator shall submit the Annual Fee, <br />an Annual Report and Map showing the extent of current disturbances to affected land, required monitoring information, <br />reclamation accomplished to date and during the preceding year, any new disturbance that is anticipated to occur during <br />the upcoming year, any reclamation that will be performed during the upcoming year, the dates for the beginning of active <br />operations, and the date active operations ceased for the year. <br />Information contained in this report is required and will be reviewed by the Division upon receipt and prior to the next <br />compliance inspection of the site. If, while completing this report, you learn that your site is not in compliance with the <br />rules and the act, it is advisable that the issues be rectified promptly to avoid possible enforcement action. <br />1. Is the affected area boundary clearly marked if you have an excavation or portal? YES NO <br />2. Is the site in final reclamation? YES NO <br />If "YES," please note time limits related to completion of reclamation, Rule 3.1.3. <br />3. What was the date of last <br />4. What date did prospectij <br />exploration activity? <br />For questions 1-16 refer to the Annual <br />Reports contained in the following <br />5. Number of acres currenj <br />DRMS prospecting NOI files for a <br />description of the specific drill pads, <br />6. Number of acres that wc <br />surface facilities, and other disturbances <br />included in each prospecting NOI issued <br />7. Number of acres that wc <br />to SFOGI. Each previously submitted <br />annual report includes a description of <br />8. Estimated new acreage <br />prospecting and reclamation activities <br />9. Estimated acres to be rel <br />conducted to date at each site. <br />Rule 5.6.1(e). <br />10. Total acres in various stages of reclamation, since permitted exploration activities began: <br />Total acres <br />Total acres <br />Total acres <br />Total acres <br />backfilled: <br />seeded w/ <br />w/topsoil <br />mulched w/ <br />approved mix: <br />replaced: <br />approved mulch: <br />Total acres <br />Total acres <br />Topsoil <br />Mulch application <br />graded: <br />fertilized w/ <br />replacement <br />rate (tons/ac): <br />a vd fertilizer: <br />depth (in.): <br />Seed <br />Fertilizer <br />Mulch <br />application <br />application <br />application <br />method: <br />method: <br />method: <br />11. Is weed control being conducted in accordance with an approved Weed Control Plan? YES NO N/A <br />If "YES", indicate the weed species, control area, control type, application rate and treatment date on the report map. <br />
The URL can be used to link to this page
Your browser does not support the video tag.