Pacific Connector line moves closer to fruition
The US FERC issued a final environmental impact statement on Pacific Connector Gas Pipeline's proposed 36-in. OD sendout pipeline, moving the project one step closer to fruition.
Christopher E. Smith
OGJ Pipeline Editor
HOUSTON, May 1 -- The US Federal Energy Regulatory Commission issued a final environmental impact statement (FEIS) on Pacific Connector Gas Pipeline LP's proposed 36-in. OD sendout pipeline, moving the project one step closer to fruition.
The proposed line would extend from Jordan Cove's LNG terminal—which was issued its FEIS as part of the same proceeding—about 234 miles southeast across Coos, Douglas, Jackson, and Klamath counties in Oregon to a terminus near Malin, Ore. From there the proposed line would interconnect with the existing pipeline systems of Gas Transmission Northwest Corp., Tuscarora Gas Transmission Co., and Pacific Gas & Electric Co.
The 1-bcfd Pacific Connector pipeline would include 1 compressor station, 4 meter stations, 4 pig launchers-receivers, 16 mainline block valves, 5 communication towers, and additional communications equipment at 8 existing towers.
Pacific Connector has entered into agreements with seven customers who have requested 1.49 bcfd through the proposed line. Upon finalization of LNG supply commitments at the Jordan Cove terminal, Pacific Connector will allocate, if needed, the available 1 bcfd amongst the seven customers.
Its route crosses 218 waterbodies (some multiple times) within 6 hydrological subbasins. Installation under 3 major rivers (Coos, Rogue, and Klamath) will use horizontal directional drilling, while 3 waterbodies (Kentuck Slough, Catching Slough, and the Medford Aqueduct) will be bored, 1 river (South Umpqua) will have diverted crossings, and the remainder of the waterbodies will be dry crossed, except for the open cut wet crossing of a portion of Coos Bay.
Pacific Connector's current proposed route reduced the crossing of the Coos Bay estuary to less than 2½ miles.
Contact Christopher E. Smith at firstname.lastname@example.org.