Denver — US natural gas production edged up to a fresh record high this week,largely due to gains in Texas, the Southeast, and the Appalachia region.
¿No está registrado?
Reciba alertas diarias y avisos para suscriptores por correo electrónico; personalice su experiencia.Registro
Modeled US production surpassed 79.8 Bcf/d on Sunday, setting the newrecord high, S&P Global Platts Analytics data shows. Over the past week, USproduction has been exceptionally strong, averaging 79.4 Bcf/d, with six ofthe highest output days on record.
Texas has led that growth. Month-to-date, production in the state hasaveraged nearly 18.8 Bcf/d, outpacing May's average by roughly 340 MMcf/d onincreases in the Permian Basin and East Texas Haynesville.
Gains in the Southeast are playing a role, too. In June, productionacross the region has averaged 11.5 Bcf/d and is up about 150 MMcf/d comparedto the prior-month average, with gains in the Haynesville and theLouisiana/Mississippi offshore being partially offset by declines from theAlabama offshore.
In the dry basins of Appalachia, gas production has averaged 27.5 Bcf/din June, a month-on-month increase of 300 MMcf/d and the highest monthlyaverage there on record.
After briefly touching modeled levels close to 28 Bcf/d earlier thismonth, Northeast production has since pulled back modestly, averaging justover 27.6 Bcf/d.
Looking ahead, it's possible that Northeast production growth couldflounder this summer, thanks to continued in-service /delays on RoverPipeline's upstream supply laterals.
While the Majorsville, Burgettstown and Sherwood laterals await anauthorization from the US Federal Energy Regulatory Commission, flows onRover's mainline have averaged just over 2.2 Bcf/d in June, or about 68% ofthe pipeline's designed 3.25 Bcf/d nameplate capacity.
Once those laterals enter service, though, an analysis by PlattsAnalytics shows that a corresponding increase in Appalachian production couldstill be delayed, owing to regional gas-processing constraints.
--J. Robinson, email@example.com
--Edited by Kevin Saville, firstname.lastname@example.org