<?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/"
	>

<channel>
	<title>Wildlife Promise &#187; Suncor</title>
	<atom:link href="http://blog.nwf.org/tags/suncor/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nwf.org</link>
	<description>The National Wildlife Federation&#039;s blog</description>
	<lastBuildDate>Tue, 21 May 2013 03:11:09 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Exxon&#8217;s Stealth Moves to Run Tar Sands into New England</title>
		<link>http://blog.nwf.org/2012/10/breaking-through-the-corporate-cover-of-the-trailbreaker/</link>
		<comments>http://blog.nwf.org/2012/10/breaking-through-the-corporate-cover-of-the-trailbreaker/#comments</comments>
		<pubDate>Tue, 09 Oct 2012 17:39:43 +0000</pubDate>
		<dc:creator>Tony Iallonardo</dc:creator>
				<category><![CDATA[Global Warming]]></category>
		<category><![CDATA[Enbridge]]></category>
		<category><![CDATA[Exxon Mobil]]></category>
		<category><![CDATA[keystone xl]]></category>
		<category><![CDATA[Maine]]></category>
		<category><![CDATA[New England]]></category>
		<category><![CDATA[Northeast]]></category>
		<category><![CDATA[oil]]></category>
		<category><![CDATA[Oil Sands]]></category>
		<category><![CDATA[Suncor]]></category>
		<category><![CDATA[tar sands]]></category>
		<category><![CDATA[Trailbreaker Pipeline]]></category>
		<category><![CDATA[Vermont]]></category>

		<guid isPermaLink="false">http://blog.nwf.org/?p=67880</guid>
		<description><![CDATA[We&#8217;ve written before about Big Oil&#8217;s new playbook on tar sands: using stealth tactics to make it harder for the public to figure out what dangerous projects they have in mind and trying to pull one over on the public. Bearing locally-based... <a href="http://blog.nwf.org/2012/10/breaking-through-the-corporate-cover-of-the-trailbreaker/" class="more">Read more &#62;</a>]]></description>
				<content:encoded><![CDATA[<p>We&#8217;ve written before about Big Oil&#8217;s <a href="http://blog.nwf.org/2012/07/tar-sands-giants-sneaky-new-playbook-revealed/">new playbook </a>on tar sands: using stealth tactics to make it harder for the public to figure out what dangerous projects they have in mind and trying to pull one over on the public. Bearing locally-based labels like “Portland Pipe Line Corporation” and “Montreal Pipe Line Limited,” the proposed <a title="Trailbreaker NWF" href="http://http://www.nwf.org/Global-Warming/Policy-Solutions/Drilling-and-Mining/Tar-Sands/Trailbreaker.aspx" target="_blank">Trailbreaker tar sands pipeline</a> is actually owned by ExxonMobil, via its Canadian Subsidiary Imperial Oil, with tar sands giant Suncor Energy having a minority stake in the company.</p>
<p>Imperial and Suncor are among the largest developers of Canadian tar sands oil. This convoluted corporate maze of oil behemoths is in bed with Enbridge, the company behind the Kalamazoo River oil spill, the most costly onshore spill in U.S. history. Now, it apparently wants to pump tar sands oil from Alberta through Vermont, New Hampshire and Maine to the port of Portland for overseas markets. <a title="Tar Sands" href="http://www.nwf.org/Global-Warming/Policy-Solutions/Drilling-and-Mining/Tar-Sands.aspx" target="_blank">Tar sands oil</a> is a heavy, corrosive, diluted bitumen and is known as one of the dirtiest, most-polluting, hardest-to-clean-up fuels on the planet. The tar sands business is booming in Canada and the corporate hawks are positioning to pounce on the profits they see in this dirty product by using New England communities as conduits to export markets.</p>
<p>It’s no wonder ExxonMobil doesn’t want to come clean. The company’s not clean. It was ExxonMobil that caused the infamous 1989 Valdez spill, a disaster that spewed 11 million gallons of oil into Alaska’s pristine waters. In July 2011, the company’s Silvertip Pipeline dumped 42,000 gallons of oil into Montana’s Yellowstone River.</p>
<div class="fl-img-left"><div id="attachment_12513" class="wp-caption alignleft" style="width: 262px"><a href="http://blog.nwf.org/2011/02/enbridge-starts-to-back-pedal-as-michigan-oil-spill-clean-up-cost-rise/riveroiled/" rel="attachment wp-att-12513"><img class=" wp-image-12513    " src="http://b50ym1n8ryw31pmkr4671ui1c64.wpengine.netdna-cdn.com/wp-content/blogs.dir/11/files/2011/02/RiverOiled-300x225.jpg" alt="Kalamazoo River Enbridge Oil Spill" width="252" height="210" /></a><p class="wp-caption-text">840,000 of tar sands crude spilled into Michigan&#8217;s Kalamazoo River last year</p></div></div>
<div class="fl-img-left"></div>
<div class="fl-img-left">
<p>And the plot thickens. Exxon’s apparent partner in the Trailbreaker tar sands plot is Enbridge, the company that owns the line from Ontario to Montreal that could connect to the line to Portland. In 2010, an Enbridge pipeline rupture poured a million gallons of oil into Michigan’s Talmadge Creek and Kalamazoo River, an incident which an independent review found was due to extreme negligence.</p>
<p>The New England Trailbreaker project would reverse the flow of the current Portland-Montreal Pipe Line (PMPL) going from Portland, Maine, to Quebec. Under the Trailbreaker scheme, tar sands would flow across Canada and through Vermont, New Hampshire and Maine through this pipeline. And this oil flowing to Portland would not help the people of those states even if they wanted it because the most likely would be exported or sent to refineries by ship. The people of New England would be left with all the harm – ruptures and pumping station breakdowns that could threaten thousands of clear lakes and rivers and unspoiled forests.</p>
<p>The people of Vermont, New Hampshire and Maine have a long history of valuing their forests, rivers and lakes. <strong>They deserve straight talk and full disclosure, not backroom deals shrouded in a complicated a corporate structure that hides the true identity and motives of the real players who see these states as just a “pass-through” to the coast and a pass-through to easy profits.</strong></p>
<p>“This pipeline presents a double whammy.  ExxonMobil’s apparent partner in this tar sands pipeline scheme is Enbridge, which has disastrous safety record and is responsible for the devastating Kalamazoo River tar sands spill in 2010,” said Jim Murphy, Vermont-based Senior Counsel with National Wildlife Federation. “Enbridge spilled a million gallons of tar sands oil into the Kalamazoo River, the most expensive domestic pipeline spill in history that will mar the river for years, maybe decades. Independent review found that extreme negligence led to the spill. Vermont doesn’t need this type of disaster.”</p>
<p>These oil giants have a dirty track record. Let’s not let them add to that record.</p>
<p>Get the Facts: <a href="http://blog.nwf.org/2012/10/breaking-through-the-corporate-cover-of-the-trailbreaker/final-corporate-fact-sheet/" rel="attachment wp-att-67994">Final Corporate Fact Sheet</a></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.nwf.org/2012/10/breaking-through-the-corporate-cover-of-the-trailbreaker/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Crews Report Progress in Stopping Spill at Colorado Tar Sands Refinery</title>
		<link>http://blog.nwf.org/2011/12/crews-report-progress-in-stopping-spill-at-colorado-tar-sands-refinery/</link>
		<comments>http://blog.nwf.org/2011/12/crews-report-progress-in-stopping-spill-at-colorado-tar-sands-refinery/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 20:42:07 +0000</pubDate>
		<dc:creator>Miles Grant</dc:creator>
				<category><![CDATA[Conservation]]></category>
		<category><![CDATA[Colorado]]></category>
		<category><![CDATA[energy]]></category>
		<category><![CDATA[oil]]></category>
		<category><![CDATA[oil spill]]></category>
		<category><![CDATA[Sand Creek]]></category>
		<category><![CDATA[South Platte River]]></category>
		<category><![CDATA[Suncor]]></category>
		<category><![CDATA[tar sands]]></category>

		<guid isPermaLink="false">http://blog.nwf.org/wildlifepromise/?p=37537</guid>
		<description><![CDATA[While they&#8217;re still working to pinpoint the source, workers have made progress in keeping an oil spill north of Denverfrom getting any worse: Federal officials say a trench dug to block toxic chemicals from seeping from a refinery into a... <a href="http://blog.nwf.org/2011/12/crews-report-progress-in-stopping-spill-at-colorado-tar-sands-refinery/" class="more">Read more &#62;</a>]]></description>
				<content:encoded><![CDATA[<p><div id="attachment_37276" class="wp-caption alignright" style="width: 310px"><a href="http://blog.nwf.org/wildlifepromise/2011/12/as-colorado-oil-spill-cleanup-efforts-continue-cancer-causing-benzene-found/in-day-nov-24-27-2011-david-zalubowski-special-to-the-denver-post/" rel="attachment wp-att-37276"><img class="size-medium wp-image-37276  " src="http://b50ym1n8ryw31pmkr4671ui1c64.wpengine.netdna-cdn.com/wildlifepromise/files/2011/12/ColoradoTarSandsSpill-300x215.jpg" alt="" width="300" height="215" /></a><p class="wp-caption-text">Oil spill cleanup worker in Commerce City, CO (NWF photo)</p></div>While they&#8217;re still working to pinpoint the source, workers have made progress in keeping an <a href="http://www.denverpost.com/search/ci_19473903#ixzz1fgnXZlwT">oil spill north of Denver</a>from getting any worse:</p>
<blockquote><p>Federal officials say a trench dug to block toxic chemicals from seeping from a refinery into a creek is working.</p>
<p>Environmental Protection Agency spokesman Matthew Allen said Monday a 240-foot trench completed over the weekend is preventing a gasoline-like substance from seeping from the Suncor Energy refinery into Sand Creek and the South Platte River.</p>
<p>Crews over the weekend worked in subfreezing temperatures cleaning up the spill, which may have been caused by a leaking pipe.</p></blockquote>
<p>Staff in our <a href="http://www.nwf.org/Regional-Centers/Rocky-Mountain.aspx" target="_blank">National Wildlife Federation Rocky Mountain Regional Center</a> will be keeping a close eye on the investigation. It&#8217;s not the first time this refinery, which processes tar sands into gasoline, has been the target of an regulators:</p>
<ul>
<li>A previous operator of the refinery, Conoco, in 1993 was ordered by a federal judge to &#8220;take all measures necessary to terminate the discharge of all pollutants into Sand Creek from the refinery property.&#8221;</li>
<li>The refinery was last <a href="http://www.denverpost.com/popular/ci_19445307?source=pop_neighbors_colorado">penalized</a> by the state Hazardous Materials and Waste Management Division in 1998, when Conoco was fined $72,500 after cancer-causing benzene was discovered in Sand Creek. The refinery also was ordered to clean up sulfur emissions.</li>
<li>In 2009, the U.S. Department of Labor&#8217;s Occupational Safety and Health Administration <a href="http://www.denverpost.com/business/ci_11856753">cited</a> the facility for workplace safety and health violations, proposing $130,500 in penalties.</li>
</ul>
<div>And now the latest spill, which comes just weeks after the State Department delayed a decision on the <a href="http://www.nwf.org/Global-Warming/Policy-Solutions/Drilling-and-Mining/Tar-Sands.aspx" target="_blank">Keystone XL tar sands pipeline</a> proposed by TransCanada. That pipeline would carry up to 900,000 barrels per day of tar sands oil from Canada to refineries on America&#8217;s Gulf Coast. The pipeline would cut through six American heartland states, including Montana, South Dakota, Nebraska, Kansas, Oklahoma and Texas.</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.nwf.org/2011/12/crews-report-progress-in-stopping-spill-at-colorado-tar-sands-refinery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
