Skip to main content

Baker Botts' Energy Litigation partners talk upstream and midstream disputes in 2019

Published by , Senior Editor
World Pipelines,


In the year to come, upstream exploration and production (E&P) companies will face numerous legal and regulatory risks arising out of day-to-day operations:

  • Continued uncertainty in oil and gas prices creates an environment ripe for contractual disputes, as joint ventures and operating partners assess the economic viability of their projects and historical obligations.  This is especially true in the offshore space, where projects have longer lead times and higher investment costs.  There may also be more disputes between lenders and borrowers in the energy industry.
  • For onshore companies, landowner disputes – seeking damages and monetary recovery beyond that provided in lease agreements -- have become increasingly common as more attention is placed on non-traditional methods of resource recovery such as hydraulic fracturing.
  • While the current administration has rolled back certain federal regulations, state and local governments continue to fill the void by reassessing standards for E&P activity, including setback requirements for oil and gas wells and pre-drill survey and testing regulations.
  • Congestion in the Permian Basin will continue, and there will more challenges in getting hydrocarbons to market, whether by rail, pipeline or otherwise.
  • New issue may arise in the exportation of oil and gas, with the United States becoming a new exporter of liquid hydrocarbons and with new LNG facilities coming online, in a world with increasing global trade disruptions.  

Baker Botts' Energy Litigation practice handles disputes involving all aspects of the exploration, production, distribution, and marketing of energy products.

Read the article online at: https://www.worldpipelines.com/business-news/17122018/baker-botts-energy-litigation-partners-talk-upstream-and-midstream-disputes-in-2019/

You might also like

 
 

Embed article link: (copy the HTML code below):