PHMSA's New Approach — 40+ Rulemakings Instead of One, and What's Actually in Them

If you've been watching the PHMSA rulemaking docket lately, you may have noticed something unusual: a flood of proposed rules, all dropping around the same time. That's not an accident, and it's worth understanding what changed and why.

For years, PHMSA's approach to regulation was to bundle changes together into large, comprehensive packages - what the industry came to call "mega rules." The logic made sense on paper: consolidate related changes, move through the rulemaking process once, get everything done together.

The problem was the comment process. Every comment submitted on a proposed rule has to be considered before a final rule can move forward. When you bundle dozens of code sections into a single package, it only takes a handful of contested provisions to hold up the entire rulemaking. Proposed rules were sitting in limbo for years - not because of disagreement on most of what was in them, but because a few provisions generated enough comment volume to bottleneck everything else.

PHMSA has changed its approach. Instead of one large package, the agency recently issued over 40 separate rulemakings — breaking what used to be a single massive undertaking into smaller, targeted pieces. The practical effect is straightforward: most of these won't generate significant comment volume, so they move through the process faster. It's more work on the front end for the agency, but it's a smarter way to build regulatory momentum without letting everything grind to a halt over a handful of contested provisions

Most of It Is Housekeeping — But Important Housekeeping

The bulk of this latest round of rulemakings is administrative in nature. We're talking about updating incorporated-by-reference standards, correcting minor errors in past regulations, and formalizing procedures for things like interpretation requests, declaratory rulings, and enforcement proceedings. There's also a set of clarifications confirming that newer technologies can be used for certain mandated activities.

None of it is earth-shattering. But "housekeeping" doesn't mean inconsequential. These kinds of clarifications matter because they define what compliance actually looks like in practice - and they can open up options that were previously ambiguous

The Changes Worth Paying Attention To

A few of the proposed changes are substantive enough to flag, specifically:

• New Technologies Get a Green Light

PHMSA is proposing to allow drones and satellite technology for right-of-way patrols. The agency is also proposing to allow remote monitoring of rectifiers on hazardous liquid pipeline systems, provided the rectifiers are physically inspected at least once annually. This mirrors what PHMSA already approved for gas transmission lines under the same annual physical inspection condition.

One thing worth thinking through if your organization is moving toward drone-based patrols: for OQ purposes, drone operators conducting right-of-way patrols are likely performing a covered task. That means they'd need to be qualified under your OQ program before they're doing it.

• Annual Report Deadline Moves

Gas operators - gathering, transmission, and distribution - may now have until June 15th instead of March 15th to file annual reports under these proposed changes. That's three additional months, which matters for operators who are typically pulling data from the prior year while managing other end-of-year workloads.

• Incident Threshold Gets Clarified

PHMSA is proposing to clarify how property damage gets calculated when determining whether an incident meets reporting thresholds. Specifically, costs associated with obtaining permits and removing or replacing infrastructure that was undamaged by the event - think the cost to temporarily remove pavement needed for access and repair - would not need to be included when calculating the property damage threshold. That's a meaningful clarification for operators who have wrestled with how to count indirect costs in incident reporting.

The financial threshold itself would be revised to $149,700, indexed to inflation. Since the threshold has always been inflation-indexed, this doesn't change the actual dollar value in effect for 2026 - but it does eliminate the need to check the PHMSA website to find the current figure. It'll be in the regulatory text.

• Construction Notification Thresholds Rise

PHMSA is proposing to raise the monetary threshold that triggers OPID notifications for replacing or modifying existing gas pipeline facilities from $10 million to $20 million. For maintenance tasks on Underground Natural Gas Storage facilities, the trigger would increase from $200,000 to $300,000. Both thresholds would be indexed to the Producer Price Index for construction materials going forward.

• Valve Inspection and Installation Timelines Change

Two proposed changes to valve requirements are worth flagging. First, hazardous liquid and CO2 pipeline valve inspection frequency would shift from twice per calendar year to once per calendar year, with a maximum interval of 15 months. Second, the deadline for making rupture mitigation valves operational after construction, replacement, or installation work would be extended from 14 days to 90 days - for gas transmission, hazardous liquid, and carbon dioxide pipelines. Both changes reflect practical realities that operators have been navigating for a while.

Bottom Line

PHMSA's shift away from mega rules is a meaningful change in how federal pipeline regulation gets made. Smaller, more targeted rulemakings move faster and are easier to engage with. The current round is mostly administrative, but the substantive changes - particularly around new technologies, incident reporting calculations, and valve timelines - are worth reviewing against your current operations.

As always, the comment period is the time to weigh in if any of these proposals create operational problems. With smaller rulemakings, the comment-to-finalization cycle should be shorter than what the industry has been used to - which means less time between a proposed rule and an effective date.