United States: Judicial Review Of PHMSA Order: Limitations Of Agency Deference

The 5th Circuit U.S. Court of Appeals reversed several key aspects of a PHMSA Final Order in a recent opinion issued on August 14, 2017. That decision is significant for the fact that few final actions by this agency have been presented for judicial review, and, of those, even fewer have been successful. The decision is based on a complex set of facts and legal issues that went through several years of administrative appeals before the agency. As with most complex cases, many of the factual issues were unique, and are not likely to be repeated. There are a few larger, procedural themes to be gleaned from the decision that apply more broadly, however, both to this agency and administrative law generally.

The central issue presented in the case was whether an administrative agency can bring an enforcement action based on an interpretation of a rule not articulated previously. Four general themes can be drawn from the 5th Circuit decision, including: (1) deference to agency interpretations of statutes and regulations is coming under increasing scrutiny by courts (and Congress); (2) at the same time, Fair Notice and post hoc rationalization are being recognized more frequently as threshold concerns before considering agency deference; (3) narrative (performance based) rules can be more difficult to enforce than prescriptive rules; and (4) courts may view agency attempts to force a specific technology as suspect when reliable technology does not yet exist.

Agency Deference Is Increasingly Subject to More Scrutiny

The 5th Circuit decision joins a growing number of cases challenging whether and how much deference should be given to federal agency decision making during judicial review. The concept of judicial deference to administrative decision making was articulated in the case of Chevron v. NRDC 467 U.S. 837 (1984). Chevron arose from an EPA rule interpreting amendments to the Clean Air Act. For more than 30 years, Chevron and its progeny have been applied by courts in cases involving statutory and regulatory interpretation by agencies. In that case, the Supreme Court ultimately upheld EPA's interpretation, stating that "If...the court determines Congress has not directly addressed the precise question at issue, the court does not simply impose its own construction on the statute . . . Rather, if the statute is silent or ambiguous with respect to the specific issue, the question for the court is whether the agency's answer is based on a permissible construction of the statute." Id. at 842-43 (requiring that if Congress has addressed the question at issue, the court must give effect to that intent).

The Supreme Court has reviewed and slightly modified its holding in Chevron over the years with respect to agency deference. In particular, the Auer case held that an agency's interpretation of an ambiguous regulation is controlling unless it is "plainly erroneous or inconsistent with regulation." Auer v. Robbins, 519 U.S. 452 (1997); see also Bowles v. Seminole Rock, 325 U.S. 410 (1945). Both the Auer and Chevron doctrines have granted federal agencies wide latitude in interpreting statutes and regulations that they administer.

There has been extensive debate over the years about whether the courts have given too much deference to rulemaking and agency interpretations, or whether agencies should have more discretion because courts do not have the expertise, time, or resources to fully understand the technical issues often presented. The problem is made more acute where statutes direct judicial review straight to the U.S. Courts of Appeal, rather than District Courts. That requires the court to rely solely on the administrative record, without further fact finding allowed in appeal. The Pipeline Safety Act is such a statute, where appeals of final agency action go direct to the Courts of Appeal.

In recent years, support for Chevron agency deference has been waning, and an increasing number of courts and others are questioning the constitutionality of these doctrines with respect to ensuring separation of powers. Then Judge, now Justice, Neil Gorsuch noted in a 10th Circuit decision "Chevron ... permit[s] executive bureaucracies to swallow huge amounts of core judicial and legislative power and concentrate federal power in a way that seems more than a little difficult to square with the Constitution of the framers' design." Gutierrez-Brizuela v. Lynch, 834 F.3d 1142 (10th Cir. 2016). In addition, earlier this year, the House introduced and passed H.R. 5, "The Regulatory Accountability Act of 2017," which proposes to amend the Administrative Procedure Act to set forth a "de novo" standard for questions of law, including the interpretation of statutes and rules by agencies and would prohibit a court from interpreting a gap or ambiguity as justification for deferring to the agency's interpretation of questions of law (thereby diminishing, if not eliminating, both Chevron and Auer deference).

Due Process and Fair Notice Limitations to Agency Deference

Even if agency deference remains unchanged, in recent years courts have identified limitations to the agency deference doctrine where an agency failed to provide due process and fair notice of its interpretation. Specific exceptions to Auer deference arise in relevant part when (1) the interpretation subjects an entity to unfair surprise, especially where penalties are involved; (2) an interpretation is offered for the first time in an enforcement proceeding and threatens substantial liability for prior conduct; and (3) an interpretation reflects an agency's post hoc rationalization. Christopher v. SmithKline Beecham, 132 S. Ct. 2156, 2166 (2012). Courts have noted the risk associated with agencies who issue "vague and open-ended regulation that they can later interpret as they see fit, thereby 'frustrating the notice and predictability purposes of rulemaking.'" Id. at 2168 (2012). In the recent 5th Circuit decision, the Court explained "We have warned that fair notice requires the agency to have 'state[d] with ascertainable certainty what is meant by standards [it] has promulgated.' " ExxonMobil Pipeline Co v. U.S. DOT, No. 16-60448, 2017 U.S. App. LEXIS 15144 (5th Cir. Aug. 14, 2017) (citing Diamond Roofing Co. Inc. v. Occupational Safety and Health Review Comm'n, 528 F.2d 654 (1976). The 5th Circuit did not apply deference because the agency's "post hoc litigation derived" interpretation of its regulation deprived the petitioner of fair notice. Id.

Vague Narrative Rules Are More Difficult to Enforce than Prescriptive Standards

Administrative rules can be narrative in form, or prescriptive. The former provides only general guidelines, while the latter sets out specific and measurable standards. Not surprisingly, it is easier to enforce prescriptive standards, because there are metrics that show compliance or non-compliance. Most agencies use both types of rules, and some regulatory topics evolve from narrative to prescriptive over time. Storm water regulations, for example, largely began as aspirational narrative standards (such as 'no taste, odor or color producing effects'), but evolved to include measurable criteria (such as 'nephelometric turbidity units' or NTUs). PHMSA regulations include more narrative performance-based standards than prescriptive, although not exclusively (construction criteria and cathodic protection are primarily prescriptive, for example).

In the recent 5th Circuit case, the primary issue revolved around a narrative rule that simply requires pipeline operators "to consider" whether a certain type of pipe may present a threat of accident. The pipe in issue – called "pre-1970 LF-ERW" welded pipe – is used in roughly one fourth of all liquid/oil pipelines in the U.S. It is not deemed dangerous in itself, as PHMSA has neither banned or even limited its use. There have been some incidents since the late 1980s involving this type of pipe and the development of certain defects on long seam welds, however, thus PHMSA requires that operators should consider that threat along with various other threats that are evaluated routinely.

As reflected in the administrative record, the Agency inspected this operator for its integrity management program many times before the Pegasus incident, and the operator evaluated the pipe many times for a variety of potential threats, including LF-ERW long seam failure, but it was not until after the incident occurred that PHMSA alleged the operator "failed" to identify the threat of long seam failure and in turn the anomaly that caused the incident. As the 5th Circuit concluded, the operator complied with the narrative rule because it clearly had "considered" the threat. Further, the fact that a release occurred, "does not necessarily mean that [the operator] failed to abide by the pipeline integrity regulations...If it did, then an operator [...] could never escape liability [...], thus nullifying the regulations and creating a strict-liability regime that Congress has not authorized. The unfortunate fact of the matter is that, despite adherence to safety guidelines and regulations, oil spills still do occur." ExxonMobil Pipeline Co v. U.S. DOT, No. 16-60448, 2017 U.S. App. LEXIS 15144 (5th Cir. Aug. 14, 2017). In this instance, the court questioned the agency's reliance on a new interpretation of general narrative rule after an incident, calling it a "post hoc litigation-derived standard."

Agency Requirements Not Yet Supported by Technology Are Difficult to Enforce

It may seem illogical for any agency to require the regulated community to achieve results that are not yet possible with existing technology. Yet that has been done for decades, often defended as 'technology forcing' rulemakings (e.g., EPA's evolving efforts to require increasingly efficient Clean Air Act controls, moving from rules requiring "Best Conventional Technology" to "Reasonable Available Control Technology" to "Maximum Achievable" (BCT-RACT-MACT), etc.). In the recent 5th Circuit case, PHMSA asserted after the fact that the operator should have been able to identify a defect that the Agency's own internal research reports and studies acknowledged were not yet capable of reliable identification using current technology. For the same reasons noted above, agency requirements to force actions that are not yet supported by technology may be viewed by courts as suspect.


The courts have never deferred blindly to all administrative agency decision making, but under the Supreme Court precedents in Chevron and Auer many courts have deferred to agency action in cases presenting complex facts and technology. Some lower courts in recent years have started to chip away at agency deference, however, whether through dicta questioning the doctrine or by creating or upholding exceptions to it. The Supreme Court now seems poised to amend Chevron and its progeny. As noted above, a bill was introduced in Congress earlier this year to legislatively limit agency deference, indicating the growing pressure to change long standing principles of administrative law. HR 5 passed the House and is presently being considered by the Senate Committee on Small Business and Entrepreneurship.

Non-prescriptive rules are typically more difficult to enforce, and they should be, because narrative rules can be subject to broad interpretation. Without clear guidance from an agency – not interpretations made after the fact of an incident or alleged violation – it is difficult for both an agency and the regulated community to define compliance. In those areas where Congress or administrative agencies expressly want to 'force' technology, it should be done in a manner that encourages innovation without punishing the regulated community where no technology yet exists to achieve the desired result.

Taken together, these themes from the recent 5th Circuit PHMSA opinion reflect several trends. Courts are increasingly reviewng agency action more closely, especially where rules are either vague or subject to broad interpretation. Deference is not due when an agency fails to provide fair notice of its interpretation and/or relies on a post incident rationalization. Finally, agency deference may not be afforded where no technology yet exists to achieve the agency's basis for alleging non-compliance.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.