Search results
Results from the WOW.Com Content Network
Congress enacted RCRA to address the increasing problems the nation faced from its growing volume of municipal and industrial waste. RCRA was an amendment of the Solid Waste Disposal Act of 1965. The act set national goals for: Protecting human health and the natural environment from the potential hazards of waste disposal.
The Resource Conservation and Recovery Act (RCRA) of 1976 was passed "to protect human health and the environment from the potential hazards of waste disposal, to conserve energy and natural resources, to reduce the amount of waste generated, and to ensure that wastes are managed in an environmentally sound manner."
Get AOL Mail for FREE! Manage your email like never before with travel, photo & document views. Personalize your inbox with themes & tabs. You've Got Mail!
The RCRA Corrective Action Program requires TSDFs to investigate and clean up hazardous releases at their own expense. [31] In the 1980s, EPA estimated that the number of sites needing cleanup was three times more than the number of sites on the national Superfund list. [154]: 6 The program is largely implemented through permits and orders. [157]
RCRA mandates that the federal government assist local communities in managing their wastes, declares that hazardous waste must be properly managed, and calls for research into better waste management practices. [11] RCRA also altered the definitions of responsibility for managing solid and hazardous waste.
In general, RCRA regulations are waste-specific, not source-specific, and thus may apply to any facility that generates mercury-containing wastes. RCRA regulations assign specific waste codes to five types of wastes that are either "characteristic" wastes or "listed" wastes. Mercury is both a characteristic and a listed waste under RCRA. [40]
Clean Harbors, Inc. was founded in 1980 in Brockton, Massachusetts, [5] [6] a Boston suburb, by Alan S. McKim, who continues as the company's CEO and chairman. (Alan has since been replaced by co-CEOs Michael Battles and Eric Gerstenberg).
The first version on Windows 95 was TAPI 1.4. TAPI 1.4 had support for 32-bit applications. The TAPI standard supports both connections from individual computers and LAN connections serving any number of computers. TAPI 2.0 was introduced with Windows NT 4.0. Version 2.0 was the first version on the Windows NT platform.