13.07.2015 Views

Human and Ecological Risk Assessment - Earthjustice

Human and Ecological Risk Assessment - Earthjustice

Human and Ecological Risk Assessment - Earthjustice

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 2.0Problem Formulationdata sources) <strong>and</strong> screened to develop the waste disposal scenarios modeled in the full-scaleanalysis.2.1.1 Identification of Waste Types, Constituents, <strong>and</strong> Exposure PathwaysTo identify the CCW constituents <strong>and</strong> exposure pathways to be addressed in this riskassessment, we relied on a database of CCW analyses that EPA had assembled over the pastseveral years to characterize whole waste <strong>and</strong> waste leachate from CCW disposal sites across thecountry (see Appendix A). The 2003 CCW constituent database includes all of the CCWcharacterization data used by EPA in its previous risk assessments, supplemented with additionaldata collected from public comments, data from EPA Regions <strong>and</strong> state regulatory agencies,industry submittals, <strong>and</strong> literature searches up to 2003.The CCW constituent database represents a significant improvement in the quantity <strong>and</strong>scope of waste characterization data available from the 1998 EPA risk assessment of CCWs(U.S. EPA, 1998a,b). For example, the constituent data set used for the previous risk assessments(U.S. EPA, 1999a) covered approximately 50 CCW generation <strong>and</strong>/or disposal sites, while the2002 CCW constituent database covers approximately 140 waste disposal sites. 1 The 2002database also has broader coverage of the major ion concentrations of CCW leachate (e.g.,calcium, sulfate, pH), that can influence CCW impacts on human health <strong>and</strong> the environment.2.1.1.1 Waste TypesTable 2-1 shows the waste types included in the 2002 CCW constituent database, alongwith counts of the number of sites with wastes of each type with constituent measurements inl<strong>and</strong>fill leachate, surface impoundment porewater, <strong>and</strong> whole waste.Comments received by EPA on the previous CCW risk assessment pointed out that theanalysis did not adequately consider the impacts of CCW leachate on the geochemistry <strong>and</strong>mobility of metal constituents in the subsurface. Commenters stated that given the large size ofthe WMUs <strong>and</strong> the generally alkaline nature of CCW leachate, it is likely that the leachateaffects the geochemistry of the soil <strong>and</strong> aquifers underlying CCW disposal facilities, which canimpact the migration of metals in the subsurface. To address this concern, EPA statisticallyevaluated major ion porewater data from the CCW constituent database for the waste streamsshown in Table 2-1. Based on this analysis <strong>and</strong> prevalent comanagement practices, EPA groupedthe waste streams into three statistically distinct categories: conventional CCW (fly ash, bottomash, slag, <strong>and</strong> FGD sludge), which has moderate to high pH; codisposed CCW <strong>and</strong> coal refuse,which tends to have low pH; <strong>and</strong> FBC waste, which tends to have high pH. As shown in Table2-1, each of these waste types included several waste streams that are usually codisposed inl<strong>and</strong>fills or surface impoundments. Note that some sites in the CCW database have more thanone waste stream, so the site counts for the different waste streams in a waste type category sumto more than the total site count for that waste type.1 Although EPA believes that the 140 waste disposal sites do represent the national variability in CCWcharacteristics, they are not the same sites as in the EPRI survey. During full-scale modeling, data from the CCWconstituent database were assigned to each EPRI site based on the waste types reported in the EPRI survey data.April 2010–Draft EPA document. 2-2

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

Saved successfully!

Ooh no, something went wrong!