20.02.2013 Views

EPA's Vessel General Permit and Small Vessel General

EPA's Vessel General Permit and Small Vessel General

EPA's Vessel General Permit and Small Vessel General

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

analyzed due to a lack of resources. EPA therefore does not know the types of PPCPs<br />

<strong>and</strong> the extent to which they are discharged by vessels.<br />

� While the Report to Congress included data for nonylphenols, EPA did not acknowledge<br />

this data in the body of the BE.<br />

The breadth of the extrapolations <strong>and</strong> the omissions made by EPA when characterizing the<br />

discharges authorized by the VGPs indicate substantial gaps <strong>and</strong> uncertainty in EPA’s<br />

knowledge of the pollutant discharges authorized by the VGPs. While the Services acknowledge<br />

that uncertainty exists in all risk analyses, the magnitude of uncertainty introduced into the BE<br />

analysis due to EPA’s lack of knowledge regarding authorized discharges is substantial. This<br />

further emphasizes the need for EPA to monitor discharges to gather additional information to<br />

more accurately identify stressors <strong>and</strong> determine which may be problematic. The EPA will<br />

monitor discharges from the following vessel systems: ballast water treatment systems, exhaust<br />

gas scrubbers, oily water separator, cruise ship graywater, <strong>and</strong> copper-based anti-fouling hull<br />

coatings.<br />

(3) Exposure to potentially harmful impacts<br />

In this section, we ask whether EPA has reliably estimated whether <strong>and</strong> to what degree listed<br />

resources are likely to be exposed to potentially harmful impacts of discharges authorized by the<br />

permit. EPA identified uncertainties in their effects analysis that could potentially limit the<br />

interpretation of results <strong>and</strong> conclusions. In order to address whether EPA has demonstrated<br />

sufficient knowledge of the exposures resulting from discharges authorized by the VGP, we must<br />

first review these uncertainties acknowledged by EPA for the BE’s assessment.<br />

Uncertainties in Exposure Estimates Identified by EPA<br />

The EPA used simple screening models to represent the estuarine <strong>and</strong> river water bodies <strong>and</strong> to<br />

estimate the exposure concentrations evaluated in the risk analysis of all U.S. waters navigable<br />

by vessels covered under the VGP <strong>and</strong> sVGP. They acknowledged that the use of such<br />

screening-level models is typically limited to identifying major water quality issues <strong>and</strong> to<br />

identify data gaps, not to perform risk analyses as they were used in the BE.<br />

EPA acknowledged that uncertainty was added to the analysis by the extrapolations needed to fill<br />

data gaps for the various combinations of vessel types, discharges, pollutants, <strong>and</strong> vessel<br />

populations. These extrapolations were required to develop the pollutant loads used in the<br />

modeling analysis. EPA also assumed that the background concentration for all pollutants in the<br />

harbor scenarios was zero. Therefore, the model output used to inform the effects analysis does<br />

not directly evaluate the potential for vessels to contribute to pollutant impairments or quantify if<br />

vessel pollutant loads serve as the “tipping point” between exceeding <strong>and</strong> not exceeding a given<br />

effect threshold. Rather than assess pollutant load contribution to existing baseline levels in the<br />

RAAs it modeled, EPA relied on the magnitude of risk quotients to provide a sense as to whether<br />

incidental vessel discharges covered under the VGP <strong>and</strong> sVGP would make notable or sizable<br />

contributions to existing harbor pollutant levels.<br />

308

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

Saved successfully!

Ooh no, something went wrong!