04.02.2013 Views

Report - Maryland Department of the Environment

Report - Maryland Department of the Environment

Report - Maryland Department of the Environment

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Oil Control Program - Pollution Remediation Activities<br />

PURPOSE<br />

The Oil Control Program (OCP) oversees remediation activities at sites where petroleum<br />

products have been discharged and are impacting soil or groundwater. The oversight<br />

ensures that responsible parties remediate <strong>the</strong> site in a timely manner, protecting <strong>the</strong> public's<br />

health and <strong>the</strong> environment. The majority <strong>of</strong> sites are gasoline service stations, both<br />

operating and closed. Sites also include businesses that have <strong>the</strong>ir own petroleum<br />

distribution systems for use in vehicle fleets and commercial and residential heating oil<br />

systems.<br />

AUTHORITY<br />

FEDERAL: Resource Conservation and Recovery Act - Subtitle I<br />

STATE: <strong>Environment</strong> Article, Title 4, Subtitle 4; COMAR 26.10<br />

PROCESS<br />

Groundwater and soil cleanups are highly technical in nature, usually requiring numerous site<br />

visits, meetings, and staff time. When a release <strong>of</strong> petroleum product is reported to OCP, a<br />

team <strong>of</strong> specialists is assigned to investigate. The team prioritizes <strong>the</strong> response effort to <strong>the</strong><br />

release, based on product type, amount released, and potential impacts from <strong>the</strong> release.<br />

Each site is in violation by virtue <strong>of</strong> <strong>the</strong> fact that a release has occurred. Inspection<br />

frequency is also determined as site-specific conditions warrant. During <strong>the</strong> inspection <strong>of</strong><br />

remedial sites, conditions are documented and <strong>the</strong> responsible party is given direction and<br />

advised <strong>of</strong> <strong>the</strong> status <strong>of</strong> compliance. There are cases where <strong>the</strong> responsible party fails to<br />

perform <strong>the</strong> necessary steps to remediate <strong>the</strong> discharge. If enforcement action is warranted,<br />

<strong>the</strong> action will be performed in accordance with MDE’s guidelines and procedures.<br />

SUCCESSES/CHALLENGES<br />

The field activity performed by OCP staff continues to reflect <strong>the</strong> commitment in time and<br />

resources needed to adequately oversee <strong>the</strong> cleanups performed by responsible parties in<br />

<strong>the</strong> State. Multiple site visits during <strong>the</strong> fiscal year are needed to ensure compliance with<br />

approved corrective action plans, especially at release sites that could impact drinking water<br />

wells. OCP has found that a strong field presence and frequent communication with <strong>the</strong><br />

responsible party increases compliance. This approach has more <strong>of</strong>ten than not resulted in<br />

<strong>the</strong> containment <strong>of</strong> releases to <strong>the</strong> property where <strong>the</strong>y occurred and for those that had<br />

already migrated <strong>of</strong>f <strong>the</strong> site, <strong>the</strong> implementation <strong>of</strong> a remedial response that prevents fur<strong>the</strong>r<br />

migration.<br />

This reporting period, OCP has been able to reduce <strong>the</strong> identified sites from 1,619 in FY<br />

2008 to 1,424 in 2009. This is <strong>the</strong> fifth year a decline has been noted. This may be<br />

attributable to OCP case managers’ prioritization <strong>of</strong> workload and sustained effort to move<br />

cases toward closure.<br />

MDE FY 2009 Annual Enforcement and Compliance <strong>Report</strong> 66

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!