« Global Bioenergies receives €1.17M payment; 2H12 revenues of €1.78M | Main | European automakers welcome Obama’s announcement of comprehensive US-Euro trade talks; major focus on regulatory convergence »
EIA: planned capacity additions to US crude oil pipeline infrastructure should relieve Cushing bottleneck
14 February 2013
According to an analysis by the US Energy Information Administration (EIA), planned additions over the next two years to the US crude oil pipeline infrastructure should relieve the bottleneck at Cushing, Oklahoma which has been caused by the oversupply of oil resulting from the growth of crude oil production in the US mid-continent and Canada.
Historically, Cushing was the midcontinent hub for distribution of both crude oil imported to the US Gulf Coast and West Texas crude oil production; pipelines were built and configured to move that crude oil north to Cushing, and then on to refineries throughout the Midwest. However, as crude oil production has grown in the US midcontinent and Canada, the Cushing hub has become over-supplied.
Companies have been looking to relieve the resulting bottlenecks at Cushing by reconfiguring and expanding pipeline infrastructure to move crude oil south to the Gulf Coast refineries. Over the next two years, planned additions to pipeline takeaway capacity should be sufficient to ameliorate the current imbalance at the Cushing hub, EIA says.
|Pipeline infrastructure expansions in the Gulf Coast. Source: US EIA. Click to enlarge.|
Keystone. Over the last three years, pipeline capacity for delivering crude oil to Cushing has increased by about 815,000 barrels per day (bbl/d). Key to this increase was the construction of the 590,000 bbl/d TransCanada Keystone pipeline that originates in Hardisty, Alberta, Canada.
Phase 1 of the Keystone pipeline from Hardisty to Steele City, Nebraska, and on to Patoka, Illinois, was completed in June 2010. Phase 2 of the Keystone pipeline, which extended the pipeline from Steele City to Cushing, was completed in February 2011.
Pegasus. With added flows into Cushing from the north and west, and limited pipeline capacity to move crude from Cushing to Gulf Coast refineries, West Texas Intermediate (WTI) crude oil has traded at a substantial discount to crudes such as Louisiana Light Sweet and Brent. Until mid-2012, only one pipeline delivered crude oil from the Midwest to the Gulf Coast. The 96,000-bbl/d ExxonMobil Pegasus pipeline between Patoka, Illinois and Nederland, Texas, which originally shipped crude oil northward, was reversed in 2006 in order to ship Canadian heavy oil to the Gulf Coast.
Seaway. In May 2012, the 150,000-bbl/d Seaway pipeline, which also shipped crude north to Cushing from the Gulf Coast, was also reversed in order to move crude oil to the higher-priced Gulf Coast market. Seaway capacity was expanded by an additional 250,000 bbl/d in early 2013. Further capacity expansions from Cushing to the Gulf Coast are planned, including a twinning of the Seaway pipeline that is expected online in early 2014, increasing its total capacity to 850,000 bbl/d.
Gulf Coast Express. Transcanada’s Gulf Coast Project represents the Cushing-to-Gulf portion of the original Keystone XL pipeline plan. The 700,000-bbl/d Gulf Coast Express project is expected online in fourth quarter 2013.
Flanagan South Project. In anticipation of the new pipeline take-away capacity from Cushing, 1,225,000 to 1,315,000 bbl/d of new pipeline capacity to deliver crude oil into the Cushing hub is also planned. The largest among these projects is the 600,000 bbl/d Enbridge Flanagan South Project, which would parallel the company’s existing Spearhead Pipeline running from Patoka, Illinois to Cushing. Flanagan South is currently scheduled to be online in mid-2014.
Pony Express. Another prominent project is Tallgrass’ planned Pony Express conversion. The project would convert existing natural gas pipelines into 230,000-320,000 bbl/d of crude oil delivery capability from the Bakken formation and Denver-Julesburg basin to Cushing and nearby refineries in third quarter 2014.
Permian Basin pipelines. Crude oil produced in the Permian Basin faces the same transportation constraints as Canadian imports and producers in the mid-continent. Two pipelines currently transport crude oil from the Permian Basin to Cushing: the Plains All American Basin pipeline, which was expanded from 400,000 to 450,000 bbl/d in early 2012; and the 175,000 bbl/d Oxy Centurion pipeline. A third pipeline, the Sunoco Logistics West Texas Gulf pipeline, has the capacity to transport 300,000 bbl/d from the Permian Basin to Longview, Texas, where it connects with the Mid-Valley pipeline to Samaria, Michigan.
Because the existing pipelines are nearly fully utilized and deliver crude into the over-supplied Cushing hub and Midwest market, six pipeline projects that include pipeline reversals, expansion, and new lines that are either under construction or planned would provide 355,000 bbl/d of new capacity to move crude oil from the Permian Basin directly to the Gulf Coast in 2013, and 478,000 bbl/d of new capacity in 2014.
Summary. Over the past three years, 815,000 bbl/d of new pipeline capacity delivering crude oil to Cushing was added. Over the same period, only 400,000 bbl/d of new pipeline take-away capacity was added.
During the next two years an additional 1,190,000 bbl/d of pipeline capacity for delivering crude oil from Canada and the midcontinent to Cushing is planned, but this is balanced by 1,150,000 bbl/d of planned pipeline capacity additions to deliver crude oil from Cushing to the Gulf Coast.
In addition, about 830,000 bbl/d of new pipeline capacity is planned to move crude oil directly from the Permian Basin to the Gulf Coast, avoiding the congested Midwest. If this capacity is constructed and fully utilized, waterborne imports to the US Gulf Coast, particularly of light sweet crude oil, could drop significantly, the EIA said.
TrackBack URL for this entry:
Listed below are links to weblogs that reference EIA: planned capacity additions to US crude oil pipeline infrastructure should relieve Cushing bottleneck: