<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Coal Ash Spill &#187; stability problem</title>
	<atom:link href="http://www.coal-ash-spill.com/tag/stability-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coal-ash-spill.com</link>
	<description></description>
	<lastBuildDate>Tue, 11 Oct 2011 18:45:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Previous leaks should have signaled warning</title>
		<link>http://www.coal-ash-spill.com/news/2009/01/31/previous-leaks-should-have-signaled-warning/</link>
		<comments>http://www.coal-ash-spill.com/news/2009/01/31/previous-leaks-should-have-signaled-warning/#comments</comments>
		<pubDate>Sat, 31 Jan 2009 14:00:34 +0000</pubDate>
		<dc:creator>Jennifer Walker-Journey</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Alabama]]></category>
		<category><![CDATA[arsenic]]></category>
		<category><![CDATA[Coal Ash]]></category>
		<category><![CDATA[coal ash pond]]></category>
		<category><![CDATA[coal ash ponds]]></category>
		<category><![CDATA[coal ash spill]]></category>
		<category><![CDATA[dangerous materials]]></category>
		<category><![CDATA[Department of Environment and Conservation]]></category>
		<category><![CDATA[East Tennessee]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[Environmental Protection Agency]]></category>
		<category><![CDATA[EPA]]></category>
		<category><![CDATA[Kentucky]]></category>
		<category><![CDATA[Kingston]]></category>
		<category><![CDATA[landfill]]></category>
		<category><![CDATA[pond leaks]]></category>
		<category><![CDATA[power plants]]></category>
		<category><![CDATA[spill]]></category>
		<category><![CDATA[stability problem]]></category>
		<category><![CDATA[Tennessee]]></category>
		<category><![CDATA[Tennessee Department of Environment and Conservation]]></category>
		<category><![CDATA[Tennessee Valley Authority]]></category>
		<category><![CDATA[toxic]]></category>
		<category><![CDATA[TVA]]></category>

		<guid isPermaLink="false">http://www.coal-ash-spill.com/?p=180</guid>
		<description><![CDATA[Two small leaks that preceded December’s Kingston, Tennessee coal ash spill by years went largely ignored by the Tennessee Valley Authority, according to Forbes/Associated Press. The spill dumped more than a billion gallons of toxic ash and mud on to 300 acres of a rural east Tennessee neighborhood, pouring into nearby rivers and destroying property and wildlife [...]<p>SOURCE: <a href="http://www.coal-ash-spill.com">Coal Ash Spill</a> &rsaquo; <a href="http://www.coal-ash-spill.com/news/2009/01/31/previous-leaks-should-have-signaled-warning/">Previous leaks should have signaled warning</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Two small <strong>leaks</strong> that preceded December’s <strong>Kingston, Tennessee </strong><a href="http://www.coal-ash-spill.com"><strong><a href="http://www.coal-ash-spill.com/" title="" rel="external">coal ash spill</a></strong> </a>by years went largely ignored by the <strong><a href="http://www.coal-ash-spill.com/tag/tennessee-valley-authority/" title="" rel="external">Tennessee Valley Authority</a></strong>, according to <a href="http://www.forbes.com/feeds/ap/2009/01/06/ap5887279.html">Forbes/Associated Press</a>. The <strong>spill</strong> dumped more than a billion gallons of <strong>toxic ash and mud</strong> on to 300 acres of a rural east Tennessee neighborhood, pouring into nearby rivers and destroying property and wildlife in its wake. What remains are remnants of <strong>dangerous materials</strong> including arsenic, lead, chromium, manganese and barium.<span id="more-180"></span></p>
<p>In 2003 and 2006, two small <strong>leaks</strong> occurred at the Kingston plant, which raised the interest of the Tennessee Department of Environment and Conservation. That agency asked <strong>TVA</strong> to provide more information about the leaks but did not require a new storage system.</p>
<p>A <strong>TVA</strong> spokesman says the two smaller <strong>leaks</strong> were not related to December’s pond failure, and in both cases repairs were made to the ponds to stop the slow <strong>leaks</strong>. A 2008 inspection report of the Kingston ponds indicated that there were no structural problems with the ponds. However, officials say that the report indicated that <strong>TVA</strong> was irresponsible for not realizing that the previous <strong>spills</strong> pointed toward a <strong>serious stability problem</strong>.</p>
<p><strong><a href="http://www.coal-ash-spill.com/tag/coal-ash/" title="" rel="external">Coal ash</a> ponds</strong> are not regulated by the Environmental Protection Agency (EPA) because the EPA doesn’t consider the <strong>coal ash</strong> to be <strong>hazardous material</strong>. Federal agents oversee coal mines but don’t regulate the burning power plants. Some experts say states have done a poor job of monitoring the <strong>coal ash ponds</strong>.</p>
<p><strong>Tennessee Gov. Phil Bredesen</strong> said he is working to provide stronger oversight of the <strong>coal ash ponds</strong> in his state. Other states where <strong>TVA</strong> has <strong>coal ash ponds</strong> or landfills include <strong>Alabama</strong> and <strong>Kentucky</strong>.</p>
<p>SOURCE: <a href="http://www.coal-ash-spill.com">Coal Ash Spill</a> &rsaquo; <a href="http://www.coal-ash-spill.com/news/2009/01/31/previous-leaks-should-have-signaled-warning/">Previous leaks should have signaled warning</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coal-ash-spill.com/news/2009/01/31/previous-leaks-should-have-signaled-warning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
	</item>
	</channel>
</rss>

