OCR Text |
Show 1.0. INTRODUCTION Tacoma Steam Plant #2 is a two-unit 43 Megawatt electric (MW J generating station which is fueled by a combination of wood waste and coal, supplemented with refuse derived fuel (RDF). The unit employs two bubbling fluidized bed combustors which consume the fuels identified. These fluidized beds also utilize limestone as a feed material, with the limestone being used to capture sulfur dioxide and hydrogen chloride in order to control acid gas emissions. The limestone is fed to the fluidized beds at calcium/sulfur (Ca/S) molar ratios of >3.1. During most of its operating history, the Tacoma Steam Plant #2 has operated without generating flyash with unusual concentrations of trace metals. However, during the period of October, 1990 - March, 1991, arsenic concentrations in the fly ash became variable (see Table I). These flyash concentrations of arsenic did not translate into failures of the Toxic Compound Leaching Procedure (TCLP), and they did not perterb the TCLP results (see Table I). These arsenic concentrations in fly ash did, however, cause three exceedences of the state IARC Metals Standards as shown in Table II. Table ll. Limits of Metal Concentrations in Flyash Products From Incinerators in the State of Washington Without Triggering Dangerous Waste Regulations IARC Metal Arsenic Barium Beryllium Cadmium Lead Nickel Strontium Zinc IARC Metal Compound A~03 BaCr04 BeO CdO Pb3(P04h NiO SrCrO" ZnCr04 ppmw as metal required to maintain IARC compound emissions < 100 ppmw (*) 75 54 (or Cr limited) 36 88 770 790 43 (or Cr limited) 36 (or Cr limited) (*) These values take into account the prior transmittal by Ebasco Environmental to the Washington Department of Ecology on Mar. 14, 1990 [8]. ----------------------------------------------------------------------------------------------------------------------- The IARC concentration exceedences occurred on Oct 16,1990; Feb 20,1991, and Feb 22,1991. The exceedences were limited to arsenic, and did not involve any other metal. Further, these exceedences demonstrate that the issue is clearly not related to the fIring of RDF. |