Welcome!

News Feed Item

Tom Steyer Letter to Secretary Kerry Regarding the Keystone XL Environmental Impact Statement

SAN FRANCISCO, Feb. 2, 2014 /PRNewswire/ -- Earlier today, NextGen Climate Action President Tom Steyer sent the following letter to Secretary of State John Kerry regarding the State Department's Final Environmental Impact Statement on the Keystone XL pipeline.

February 2, 2014

Secretary John Kerry
U.S. Department of State
2201 C Street NW 
Washington, DC 20520

Secretary Kerry:

I am sure you know that I have the utmost respect for the leadership you bring to the State Department when it comes to addressing the challenge of global climate change.

At his State of the Union speech on Tuesday, President Obama made clear the Administration's position when he stated that climate change is a fact.

For those of us in California experiencing an historic drought, as well as for those across the country who have been dealing with extreme weather, climate change affects us every day – impacting our economy, our health and our welfare.

Many of us have been heartened to hear that amidst your many pressing responsibilities, you intend to take an active role in advising the President on his decision regarding the Keystone XL pipeline.

In light of the concerns enumerated below, I urge you to launch an independent and transparent review of the work product contained in the Keystone XL Pipeline Environmental Impact Statement (FEIS) released last Friday.

Of particular concern are FEIS conclusions that conflict with and are contradicted by tar sands industry executives who confirm that they need the pipeline in order to continue to develop the tar sands and to reach international markets. The FEIS fails to consider that construction of the KXL pipeline is a necessity to fully maximize extraction of tar sands. 

Attached is an analysis of such assertions by tar sands executives, which includes such statements as:

These assertions reinforce the findings by NextGen Climate Action in late November of last year which demonstrate the pipeline is the economic key to unlocking the tar sands and, as such, will lead to more pollution in the air than would be generated if the pipeline was not built. 

Both the statements from the tar sands executives and the NextGen Climate Action report make clear the pipeline would fail the test established by the President during his speech at Georgetown last June: that no project that increases the amount of air pollution will be approved.

However, and despite the fact that some of the aforementioned assertions from tar sands executives were made as recently as last week, it does not appear that any of these representations were considered in the FEIS.  

How can the foreign companies who stand to financially benefit from the approval of the KXL pipeline assert that the pipeline is the key to their ability to develop the tar sands without these assertions being considered material to this report? This was a report that was designed to analyze exactly this issue of whether or not the pipeline would affect the development of the tar sands.

TransCanada and the tar sands lobby has time and time again justified the development of the pipeline by making the public policy argument that the pipeline would support U.S. oil independence.  But TransCanada has refused to commit to keeping the refined oil in the United States.

However, as you are aware from your time in Congress, while TransCanada's CEO has asserted that "every" drop of crude would stay in the United States, company officials have refused to testify to this when appearing before Congress. And to this day, TransCanada has refused to explain whether or not the refined oil will be shipped to economic competitors such as China, which has a significant investment in the project.

The failure to address the assertions made by tar sand oil executives that the pipeline is the key to unlocking the tar sands is the latest in a series of problems. Together, they make it clear it would be a disservice to President Obama, to our country and to the resolution of climate change to use the FEIS as a trusted document.  

These problems include:

  • The hiring of a TransCanada contractor – Environmental Resources Management (ERM) – to write the FEIS.
  • ERM's problematic representations about its ties to the tar sands industry on its conflict of interest disclosure form.
  • The Inspector General's investigation into this deception, an action taken only after persistent pressure from public interest groups.
  • Additional conflicts (herehere and here) that have come to light since the Inspector General's investigation began.
  • Repeated quotes (e.g., here and here) to news outlets from named and unnamed staff members at the State Department boasting of "rigorous conflict of interest procedures…" that "… ensure that no contractors or subcontractors have financial or other inappropriate interests in the outcome of a project." This assertion continued to be made even after the Inspector General's investigation was announced.
  • The unsurprising tilt of the draft FEIS toward ERM's client, TransCanada.
  • The interagency criticism (here and here) that the draft EIS drew because of its deep flaws.
  • The nearly identical nature of the final FEIS to the draft EIS, despite significant, contradictory information coming to light after the draft version was issued. This includes ignoring the realities of tar sands transportation, and estimates that Keystone XL would produce the pollution equivalent of more than 50 coal plants – an amount no serious expert thinks can be meaningfully offset. It also ignores the $30 billion in investment by companies backed by the Chinese government.
  • The apparent rush to get the EIS out the door before the Inspector General's investigation was complete – despite a recent request by over 20 House members asking that the FEIS be held until the investigation was completed.

And, in addition to this litany of issues that should disqualify this FEIS report from being used as a trusted document, there is now a report in the Canadian Press that seems to indicate officials in Ottawa were provided with the assurance that they would receive the favorable FEIS that they had lobbied so hard to secure. I have long said that Keystone is a pipeline that runs through — but no to — the United States. If the press reporting is accurate, it would now appear that foreign interests have a direct pipeline into the decision-making process of the U.S. government, which is simply unconscionable.

For all of these reasons, especially in the context of global climate change, it is critical that an independent and transparent review of the FEIS, and the process undertaken for its preparation, commence immediately. It is inappropriate and unfair to provide President Obama — who has stated that climate change is a fact and even articulated a clear test for the approval of a project such as the KXL pipeline – with a report that is not only on its face defective, but which has suffered from a process that raises serious questions about the integrity of the document.

Thank you for your attention to this serious matter.

Regards,

Tom Steyer

SOURCE NextGen Climate Action

More Stories By PR Newswire

Copyright © 2007 PR Newswire. All rights reserved. Republication or redistribution of PRNewswire content is expressly prohibited without the prior written consent of PRNewswire. PRNewswire shall not be liable for any errors or delays in the content, or for any actions taken in reliance thereon.

Latest Stories
Every successful software product evolves from an idea to an enterprise system. Notably, the same way is passed by the product owner's company. In his session at 20th Cloud Expo, Oleg Lola, CEO of MobiDev, will provide a generalized overview of the evolution of a software product, the product owner, the needs that arise at various stages of this process, and the value brought by a software development partner to the product owner as a response to these needs.
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
SYS-CON Events announced today that Enzu will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Enzu’s mission is to be the leading provider of enterprise cloud solutions worldwide. Enzu enables online businesses to use its IT infrastructure to their competitive ad...
In his session at DevOps Summit, Tapabrata Pal, Director of Enterprise Architecture at Capital One, will tell a story about how Capital One has embraced Agile and DevOps Security practices across the Enterprise – driven by Enterprise Architecture; bringing in Development, Operations and Information Security organizations together. Capital Ones DevOpsSec practice is based upon three "pillars" – Shift-Left, Automate Everything, Dashboard Everything. Within about three years, from 100% waterfall, C...
SYS-CON Events announced today that MobiDev, a client-oriented software development company, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. MobiDev is a software company that develops and delivers turn-key mobile apps, websites, web services, and complex softw...
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed ...
Web Real-Time Communication APIs have quickly revolutionized what browsers are capable of. In addition to video and audio streams, we can now bi-directionally send arbitrary data over WebRTC's PeerConnection Data Channels. With the advent of Progressive Web Apps and new hardware APIs such as WebBluetooh and WebUSB, we can finally enable users to stitch together the Internet of Things directly from their browsers while communicating privately and securely in a decentralized way.
While many government agencies have embraced the idea of employing cloud computing as a tool for increasing the efficiency and flexibility of IT, many still struggle with large scale adoption. The challenge is mainly attributed to the federated structure of these agencies as well as the immaturity of brokerage and governance tools and models. Initiatives like FedRAMP are a great first step toward solving many of these challenges but there are a lot of unknowns that are yet to be tackled. In hi...
With the proliferation of both SQL and NoSQL databases, organizations can now target specific fit-for-purpose database tools for their different application needs regarding scalability, ease of use, ACID support, etc. Platform as a Service offerings make this even easier now, enabling developers to roll out their own database infrastructure in minutes with minimal management overhead. However, this same amount of flexibility also comes with the challenges of picking the right tool, on the right ...
The cloud market growth today is largely in public clouds. While there is a lot of spend in IT departments in virtualization, these aren’t yet translating into a true “cloud” experience within the enterprise. What is stopping the growth of the “private cloud” market? In his general session at 18th Cloud Expo, Nara Rajagopalan, CEO of Accelerite, explored the challenges in deploying, managing, and getting adoption for a private cloud within an enterprise. What are the key differences between wh...
One of the hottest areas in cloud right now is DRaaS and related offerings. In his session at 16th Cloud Expo, Dale Levesque, Disaster Recovery Product Manager with Windstream's Cloud and Data Center Marketing team, will discuss the benefits of the cloud model, which far outweigh the traditional approach, and how enterprises need to ensure that their needs are properly being met.
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.