Stand up for the facts!
Misinformation isn't going away just because it's a new year. Support trusted, factual information with a tax deductible contribution to PolitiFact.
I would like to contribute
The Keystone XL pipeline is years from operating and may, in fact, never be built.
But that doesn’t mean the 1,700-mile project from Canada’s oil-rich tar sands in Alberta that would bring heavy crude to the Gulf of Mexico isn’t already pumping product, at least rhetorically. The U.S. State Department is expected to decide by the end of March whether to grant a permit that must be issued for the pipeline to be built. (The State Department is involved because the pipeline would cross an international border.)
It’s a high-stakes, high volume, politically charged exercise. Environmentalists have protested -- and been arrested -- in recent days in front of the White House as part of their campaign to pressure President Barack Obama to reject the project.
The other side has been just as active. That includes U.S. Rep. Greg Walden, an Oregon Republican who has long supported the pipeline as a way to make the United States more energy self-sufficient and boost the economy -- even in Oregon.
Here’s what he tweeted Jan. 29, 2013: "Did you know that the#KeystoneXL project is expected to create 20,000 American jobs, including more than 800 in Oregon?"
That’s an attention-grabbing statement for two reasons. The first is the overall number of jobs at a time when the U.S. economy continues to struggle. The second concerns both numbers and geography. The pipeline as proposed would enter the U.S. in Montana and angle toward the Gulf on an eastward track through South Dakota and Nebraska. From there it continues to the Gulf.
Even if the route changes, the pipeline will be 1,000 miles (or more) from Oregon. So it’s fair to ask, how will a state so far removed from the project claim 800 jobs? Here’s a second, more basic question: Is the 20,000 "American jobs" cited by Walden and many other supporters of the project real?
Let’s take a look.
Sure enough, TransCanada, the company proposing the pipeline has cited the potential for 20,000 jobs. "The $7 billion oil pipeline is the largest infrastructure project on the books in the U.S. right now," the company said in a 2012 news release. "It would create 20,000 jobs: 13,000 in construction, 7,000 in manufacturing."
There have been numerous analyses and copious filings by the company itself in pursuit of the permit.
And yet, the conclusion that 20,000 jobs would be created is more than a bit slippery.
A 2011 study by Cornell University is absolute: "The company’s claim that KXL will create 20,000 direct construction and manufacturing jobs in the U.S is not substantiated," it states.
One of the more troublesome devices is this: The total is a reflection of something called "job years." Why is that important? A "job year" is a measure of one job performed for one year. That means if a single worker stays on the job for the two years the pipeline construction is expected to last, that single worker counts as two jobs.
The measure might be accepted -- and used -- by economists but it’s not what the average person thinks when hearing the word "job." TransCanada says the 20,000 jobs include 13,000 direct jobs, mostly construction and 7,000 indirect jobs. If the project takes two years, it means 6,500 actual direct jobs (plus or minus), which is the number the State Department uses.
Calculated that way, the actual number of people employed by the pipeline moves closer to 10,000, or some 6,500 workers in construction and 3,500 in manufacturing. Not 20,000.
Here’s another important point: These construction jobs are not permanent and, for the most part, aren’t necessarily local. The positions will disappear when the pipeline is complete. The State Department estimates that only 10 to 15 percent of these jobs can be filled with workers from communities in the pipeline’s path.
As for the broader (and always murky) world of indirect jobs, the study -- by Lara Skinner and Sean Sweeney at Cornell’s Global Labor Institute -- raises questions about an analysis by the Perryman Group, which was hired by TransCanada to look at economic impacts.
"The Perryman study is based on expenditure and sourcing data provided by TransCanada,
and none of that information has been disclosed or subject to independent review," the Cornell study says.
By their calculations, Perryman uses a multiplier of 18 job-years for every $1 million spent on the project. Skinner and Sweeney write that a more acceptable multiplier is 11 job-years for every $1 million spent.
"So a reasonable estimate of the total incremental U.S. jobs from KXL construction is about one-third of the figure estimated in the Perryman study and used by industry to advocate for the construction of KXL," the Cornell study concludes.
Let’s move on to the second part of Walden’s claim, that the pipeline would bring "800 jobs" to Oregon.
Unlike a lot of states far removed from the actual pipeline route, there is an official thread to Oregon.
In a January 2012 news release promoting the pipeline’s economic value, TransCanada says this: "Construction of Keystone XL is expected to create 7000 manufacturing jobs. Key support companies include: Welspun (pipe from Arkansas), Cameron (valves from Louisiana), Siemens (pumps, motors and related control equipment manufactured in Oregon, Ohio and Indiana) and dozens of other companies manufacturing everything from nuts and bolts to complex electrical control equipment."
That’s as specific as it gets, however. When asked for source material to back this claim of 800 jobs, Walden’s office referred to a Chamber of Commerce study. Sure enough, the publication says there will be 838 jobsattributable to the pipelinein Oregon by 2020. (Once again, the use of "jobs" is not what an average person expects.)
Chamber of Commerce spokeswoman Blair Latoff Holmes said the number was taken from a study commissioned by the pro-pipeline American Petroleum Institute, written by the Canadian Energy Research Institute and released in June 2011.
All of these studies are vulnerable to criticism because the formulas are by necessity often more art than science and the methodology used is not clearly expressed. That’s why the conclusions should be consumed with caution.
But tone matters too. In his statement, Walden seems absolute even while there is no clarification that the 20,000 figure refers to "job years," which is much different than the way "job" is commonly understood.
Walden has a somewhat stronger case on the Oregon job claim, mostly because TransCanada mentions Oregon by name as one state that would produce equipment needed for the project. As for the number 800, however, it is at best a guess.
That’s a pipeline full of uncertainty. We rate this claim Mostly False: It contains some element of truth but ignores critical facts that would give a different impression.
Email exchange, Andrew Malcolm, communications director Rep. Greg Walden, Feb. 19, 2013
"Keystone XL Pipeline Jobs By State,"U.S. Chamber of Commerce, Feb. 19, 2013
Press release, "TransCanada Releases Detailed Keystone XL Job Creation Data,"Jan. 10, 2012
Oregon Job Numbers, Keystone XL Pipeline, U.S. Chamber of Commerce, Feb. 19, 2013
Email exchange, Blair Latoff Holmes, Senior Director of Communications, U.S. Chamber of Commerce, Feb. 20, 2013
"The Impact of Developing the Keystone XL Pipeline Project on Business Activity in the US:
An Analysis Including State-by-State Construction Effects and an Assessment of the Potential Benefits of a More Stable Source of Domestic Supply," The Perryman Group, Waco, Texas; June 2010
"Economic Impacts of Staged Development of Oil Sands Projects in Alberta (2010-2035)," Canadian Energy Research Institute, June 2011
"EXECUTIVE SUMMARY: Final Environmental Impact Statement for the Proposed Keystone XL Project," U.S. State Department, Aug. 26, 2011
"Pipe dreams? Jobs Gained, Jobs Lost by the Construction of Keystone XL," Lara Skinner, Ph.D. and Sean Sweeney, Ph.D., Cornell University Global Labor Institute with Ian Goodman and Brigid Rowan The Goodman Group, Ltd., September 2011 (updated January 2012).
Read About Our Process
In a world of wild talk and fake news, help us stand up for the facts.