This episode of the Pipeliners Podcast features Jim Curry of Babst Calland discussing the latest developments in PHMSA’s Notice of Preliminary Rulemaking on CO2 pipelines.
The conversation covers key aspects of the proposed rule, potential challenges in implementation, and what the future holds for CO2 pipeline regulation.
Jim shares insights on the regulatory landscape, the impact of the Satartia, Mississippi incident, and how industry stakeholders are responding to evolving safety and compliance requirements.
PHMSA CO2 Notice of Preliminary Rule Making Show Notes, Links, and Insider Terms
- PHMSA (Pipeline and Hazardous Materials Safety Administration) the U.S. federal agency within the Department of Transportation responsible for regulating and enforcing pipeline safety standards, including hazardous liquid and CO₂ pipelines.
- Notice of Proposed Rulemaking (NPRM) a formal regulatory document issued by PHMSA proposing changes to existing regulations and soliciting public and industry comments before finalizing a rule.
- CO₂ Pipeline a pipeline used to transport carbon dioxide, commonly for enhanced oil recovery (EOR), carbon capture, utilization, and sequestration (CCUS) projects.
- Satartia, Mississippi Incident a 2020 CO₂ pipeline rupture caused by a geotechnical failure during extreme weather, which released dense CO₂ gas and became a major catalyst for renewed CO₂ pipeline regulation.
- Part 195 the section of federal pipeline safety regulations governing hazardous liquid pipelines, including crude oil, petroleum products, HVLs, and CO₂ pipelines.
- Highly Volatile Liquid (HVL) a regulatory classification under Part 195 traditionally applied to certain liquid hydrocarbons with high vapor pressure; PHMSA proposed redefining CO₂ as an HVL, triggering enhanced regulatory requirements.
- Supercritical CO₂ a dense phase of carbon dioxide that occurs at high pressure and temperature, commonly used in CO₂ pipelines and exhibiting properties of both gas and liquid.
- Regulatory Freeze Memo an executive directive issued during a presidential transition that temporarily halts or withdraws pending federal regulations not yet published in the Federal Register.
- Federal Register the official daily publication for U.S. federal agency rules, proposed rules, and public notices; a rule is not legally proposed until it appears here.
- Vapor Dispersion Modeling analytical modeling used to predict how released CO₂ or other vapors spread based on terrain, weather, pressure, and volume, critical for integrity management and emergency planning.
- Integrity Management (IM) a risk-based regulatory framework requiring operators to assess, monitor, and mitigate pipeline risks using data, inspections, modeling, and corrective actions.
- Geohazard a geological or environmental condition (e.g., landslides, erosion, flooding) that can threaten pipeline integrity, highlighted due to the Satartia failure.
- Depth of Cover the amount of soil or material covering a buried pipeline; reduced depth of cover can increase risk and may require remediation under proposed rules.
- Leak Detection System technology or procedures used to identify unintended pipeline releases, proposed to be explicitly required for CO₂ pipelines.
- Above-Ground Facility (AGF) pipeline-related infrastructure such as pump stations, valve sites, and meter stations, proposed to require CO₂ vapor detection and alarms.
- Conversion to Service the regulatory process allowing a pipeline to be converted from one regulatory classification to another (e.g., Part 192 gas to Part 195 hazardous liquid service).
- Part 192 the section of federal regulations governing natural gas transmission and distribution pipelines.
- Pressure Test a method of verifying pipeline integrity by subjecting it to pressures above normal operating levels, historically a key requirement for pipeline conversions.
- ILI (In-Line Inspection) tools, often called “smart pigs,” used to inspect pipelines internally for defects, corrosion, or deformation.
- Spike Test a short-duration pressure test intended to expose latent defects, proposed as part of CO₂ conversion requirements.
- Close Interval Survey (CIS) a corrosion assessment technique used to evaluate the effectiveness of cathodic protection along a pipeline.
- Cathodic Protection (CP) a corrosion control method that protects buried or submerged pipelines from metal loss.
- API (American Petroleum Institute) a major industry trade association that develops standards and often coordinates industry comments on proposed pipeline regulations.
- GPA Midstream (formerly GPA) an industry trade association representing midstream companies, referenced as a possible conduit for coordinated regulatory comments.
- LPAC (Liquid Pipeline Advisory Committee) a federal advisory committee that reviews PHMSA liquid pipeline rulemakings and provides recommendations before rules are finalized.
- Enhanced Oil Recovery (EOR) the use of injected CO₂ to increase oil production, historically associated with CO₂ branch lines that are partially exempt from Part 195.
- Class VI UIC Well a type of Underground Injection Control well regulated by EPA for permanent CO₂ sequestration, treated differently than EOR wells in the proposed rule.
- Public Awareness Program a long-standing regulatory requirement for operators to educate communities near pipelines on safety, emergency response, and recognizing pipeline incidents.
- Risk-Based Regulation a foundational pipeline safety principle that tailors requirements based on actual risk factors rather than fixed distances or assumptions.
PHMSA CO2 Notice of Preliminary Rule Making Full Episode Transcript
Russel Treat:
Welcome to the “Pipeliners Podcast,” episode 377, sponsored by EnerSys Corporation, providers of POEMS, the Pipeline Operations Excellence Management System, operations and compliance software for the pipeline operator to address safety program management, control room management, and field operations. Find out more about POEMS at enersyscorp.com.
[background music]
Announcer: The Pipeliners Podcast, where professionals, bubba geeks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations. Now your host, Russel Treat.
Russel:
Thanks for listening to this podcast. We appreciate you taking the time, and to show the appreciation, we give away a customized Yeti tumbler to one listener every episode. This week, our winner is Luke Abbott of Targa Resources.
Congratulations, Luke. Your Yeti’s on its way. To learn how you can win this prize, stick around till the end of the episode. This week, Jim Curry of BAPS Callen joins us to talk about the new Notice of Preliminary Rulemaking from PHMSA on CO2. Jim, welcome to the Pipeliners Podcast.
Jim Curry: Hey, Russel, it’s good to see you. Thanks for having me. I’ve been looking forward to being on one of your podcasts for a long time. I’m a big fan, so thanks for having me on.
Russel: It’s always good to meet a fan. Always good to meet a fan. Podcasting is a weird vehicle because I do this every week and I don’t necessarily hear back from people every week. It’s nice to hear the feedback, so thanks.
Jim: Absolutely.
Russel: Look, before we dive in do you mind giving us a little bit of introduction? Tell us a little bit about who you are, your background, and how you got involved in CO2 pipeline rulemaking.
Jim:
Yeah, absolutely. Gosh, I was thinking about this morning, Russel, as I was getting ready, and I realized I’ve been doing this for 19 years now, pipeline safety, that is. I started my legal career at PHMSA. I was a lawyer there right after law school for about five years, doing all things pipeline safety.
I was doing enforcement, rulemaking, legislative work, you name it. We had a pretty small chief counsel’s office then. I got to do everything. It was a great place for a young lawyer. To get thrown into. Went out in private practice in 2010.
I was at another firm here in DC for about five years, and then opened, along with Keith Coyle and Brianne Kurdock, my partners. Keith’s now a former partner, and we can talk about that later. Opened a new office for Babst Calland. We’re a law firm. We service the energy industry.
We’ve grown our office from about 3 people to about 18 people since then. It’s been a great experience. We continue to focus on pipeline safety in my group. I’m the managing shareholder of the DC office and part of our pipeline practice group. I still do everything pipeline safety.
I do other things as well, but probably 90 percent of my work or so is pipeline safety, doing rulemaking, policy development, enforcement, appellate litigation, work up on the Hill, rulemakings like the CO2 rules. That’s a little bit about my background. I’m excited to be here today.
Russel:
I’m glad to have you. We’re going to jump into CO2 here in a second, but it’s probably appropriate because Keith Coyle has been a perennial guest. He’s been my go-to guy now for, gosh, six or seven years for all things rulemaking, all things PHMSA. He has gone over to the dark side.
[laughter]
Jim: He has.
Russel: I’m kidding. I’m hoping Keith listens to this and he captures that. I hope he laughs when he hears it.
Jim:
I’m sure he will. We were very sorry to see our good friend and colleague, Keith Coyle, leave the firm, but a tremendous personal and professional opportunity for him to be tapped over there as the politically appointed chief counsel at PHMSA.
He’s already hit the ground running. Nobody knows more about how that agency operates and its underlying law than he does. That’s a great opportunity for him.
Russel:
It’s a great opportunity for him, and it’s good for the industry, too, because he really knows the operators and their needs, and he understands…When I saw that, [laughs] my first reaction is, “That’s so cool. That’s such a great pick. He’s going to do a great job.”
Then, immediately after that, I’m like, “What does that mean for me? Who do I talk to about rulemaking? Is he going to be able to talk to me anymore?”
Jim: [laughs]
Russel: We’ll reach out to Keith and we’ll figure all that out. Keith, if you’re listening, congratulations. I look forward to our next conversation. Let’s pivot here. I asked you to come on and talk about CO2. Right before the change in administration, the CO2 Notice of Proposed Rulemaking hit the federal register. We got to the notice…I can’t remember if it hit…
Jim: It didn’t.
Russel: It didn’t.
Jim:
It almost did, and that’s…
[crosstalk]
Russel: That’s right. We got the announcement from PHMSA that it was going to, but it didn’t actually get there. Right.
Jim: That’s right.
Russel: Where are we with CO2 rulemaking? Is it dead or what? What’s going on?
Jim:
The short answer to your question is, I don’t think it’s dead. I think it will ultimately go forward in some form, although probably not in the same form that it was put out in its unofficial version. Right before the inauguration, PHMSA posts an unofficial copy of the proposed rule to its website, sends the rule to the federal register, but it never makes it there before inauguration day.
Under president Trump’s regulatory freeze memo, the rule gets pulled back by PHMSA, gets pulled out of the Federal Register before it can actually be noticed publicly. It’s not an official proposed rule, but we all know what’s in there, right? We were able to access it. PHMSA has now pulled it down off its website.
If you’re looking for it, you can drop me an email, I’ll send it to you. It’s not actually publicly available anymore. You know what, I think to understand where the rule might go next, it’s helpful to understand why PHMSA put it out in the first place and kind of the stakeholders that I think they were trying to be responsive to.
PHMSA announced this rulemaking back in 2022, largely in response to an accident on a CO2 pipeline down in Satartia, Mississippi, was a release from a full bore rupture caused by a geotech event, essentially extreme weather event. Heavy rain, pipe on a hillside, girth weld failure, and there was a release of CO2.
PHMSA was largely responding to that accident and the public and NGO kind of cries for more regulation in the aftermath of that accident. Really up until that accident CO2 pipelines, it was a pretty quiet place. Folks weren’t out there on the conference circuit talking about these assets. Really, that accident made all the difference in the world.
PHMSA is trying to, I think, telegraph to, or was trying to telegraph to public and the NGOs, “Hey, we’re going to step up our game. I think, to be clear here, a lot of the public and NGO criticisms of CO2 pipeline safety and what PHMSA was doing were really not all that fair.
There’s a lot of information out there that just wasn’t accurate in terms of folks saying CO2 pipelines are dangerously unregulated. It’s not true. They’ve been regulated by PHMSA, one of the part 195 liquids regs since the mid-1990s. They have a great safety record.
If you look at the safety record from the ’90s forward we do not have any fatalities. There are incidents to be sure, but not a lot of significant incidents. That’s just a little bit of background on why they did what they did. I think from an industry perspective…
Russel:
From my perspective, Jim, I think there’s another aspect. All this all that’s true. I acknowledge all that. I think Satartia was a major pivot point for CO2 regulation. The other thing that’s driving that is all this stuff around capture, sequestration, and all these guys that are trying to get CO2 projects permitted and constructed to do capture and sequestration.
The public, where these guys are looking to build these pipelines, is saying these are dangerous, there’s no rules for regulation, CO2 is unique. They’re making some really valid points. Those operators want the regulations so that they can say, “Look, there are regulations and we’re exceeding those regulations.”
Jim:
You’re exactly right, Russell. I should say that my comments here, personal comments, not necessarily reflective of any of my clients. I would agree with you generally. I think it seems worthwhile to advance some form of CO2 rule to put those public safety concerns to rest.
Look these developers that are out there building new projects and even the operators of existing facilities, they’ve adopted some pretty advanced approaches and techniques around dispersion modeling and other issues.
They’re already doing the things, many of the things at least at a broad level that PHMSA has included in the proposal. I think you’re probably right that industry wants to get this in the books and move forward.
Russel: Could you broad brush for us what’s in the rule? What does it actually contain?
Jim:
Sure. Let’s talk about kind of buckets of issues. They’re going to be a number of elements of this rule that are not controversial. There are others that at least appear to me to be somewhat problematic. We’ll talk about the specific elements of the role, but let’s just talk about the buckets on places where operators and other industry stakeholders might want to think about as they’re going through the role.
First, I think some of the proposed requirements when you actually look at implementing them as a practical matter on the ground, I think some of them would be, unless they’re modified, pretty difficult to implement as proposed.
I think there’s room for improvement there as the trade associations and others go back to PHMSA and talk about this rule, there’s some tweaks that can be made to make it a lot more practicable. That’s one. A second set of issues, and a lot of this actually isn’t even in the proposed text, like the actual text, a mandatory tax would change part 195. It’s in the preamble.
There’s a lot of language in there that either implicitly or explicitly assumes a level of risk around CO2, which I’m not sure is terribly well supported in the rule itself. That is PHMSA makes a number of statements about how dangerous CO2 releases are, how far they can travel.
It only points to limited evidence supporting that. Look, I’m not saying that CO2 releases have no risk. Some of them do. We have to grapple with that and be very clear about what those risks are.
In many cases, PHMSA is taking a broad brush and said, “Wow, look how dangerous this is. We need these huge buffers.” Etc. I think what industry can do is come back and say, “Look, no, we’ve done the modeling. Here’s how this material behaves when it gets out. Here’s where it goes. Here’s what the risks are.”
Calibrating those risks to what our actual data shows rather than this kind of broad brush CO2 scary thing that PHMSA is doing in the…
[crosstalk]
Russel:
You got to be a little careful about that, Jim, and I’ll give you my perspective. The liquid rule is generally addressing things that if there’s a rupture, they spill onto the ground, they flow through the same places that the water would flow if it was water, and it’s an environmental risk, primarily.
Now, there can be explosive risks and other things too, but primarily, it flows on the ground. CO2 has a radically different behavior and a radically different set of risks.
Jim: I agree.
Russel:
For people that don’t understand the risks, or maybe don’t understand CO2 behavior, so CO2 exists under pressure in a pipeline. The minute it hits atmospheric pressure, it flashes into CO2 gas and CO2 solid, or what most people would refer to as dry ice.
The dry ice is dangerous because it’s minus 126 degrees Fahrenheit. The CO2 gas, while not a…What am I trying to say? It’s not poisonous, but it displaces oxygen. When it mixes with water, it creates carbonic acid. If I breathe it at high density, I’m either, A, going to be starved of auctions, or I could have some lung damage.
If there’s any wind or it’s warm, it will disperse pretty quickly. The big thing was Satartia is it happened on a day where it was cold and foggy and all that gas rolled to some low places and stayed there. To me, it’s not that I don’t think PHMSA is really wrong, but I think that what they’re not doing is they’re not characterizing the risk. They’re just saying it’s risky, but they’re not characterizing the risk.
Jim:
Everything you just said that’s all accurate that the behavior of the commodity really is different. 100 percent. I think where the rub is PHMSA saying look, we need to put in the rules, certain provisions that assume that CO2 when it gets out, is going to do X, Y, and Z.
Let me give you a specific example, and it’s the location based requirements. There’s some significant new rules on location where if you’re a developer, and you locate your CO2 pipeline within two miles of a residence, you got to document why it was impracticable to avoid those areas.
I’ll tell you, even in the most rural parts of the United States, it’s hard to be two miles away from somebody. You can do it in some places, but it’s tough to do. This isn’t a ban on locating CO2 pipelines within two miles of residence.
What it does is it creates this inference that everybody within two miles of the line is at risk and that’s not true. In all cases, the fact of the matter is that the level of risk really depends on the asset, the pressure, the volume, weather conditions, terrain conditions.
Risk is different in different locations, even on the same asset. Certainly it’s different across multiple assets, but instead of acknowledging that, “Hey let’s look really hard and see where the highest risk is.” Just saying if you’re within two miles, there’s this inferred risk, and I think that’s going to unnecessarily make the public nervous.
Are there some areas where CO2 could get two miles? There might be. I’ve not seen that in any of the dispersion modeling results that I’ve seen. It’s usually a lot less. My only point in all of this is that I think PHMSA should be a little bit more careful in terms of how it articulates what the risk is, instead of saying there’s just two miles saying, “Well it’s depends. Let operators tailor their approach on where the risk is.”
That’s a fundamental concept of part 195 and the integrity management rights. It’s always been in there. Yeah, but I don’t disagree with you that there is risk and this is a different commodity. It’s just let’s approach it in a more tailored way.
Russel:
What are some of the things in the rule that are not controversial…
[crosstalk]
Russel: …that industry would pretty much say, “Yeah, that just makes sense. We’re already doing that.” Or, “That’s a logical next step.”?
Jim:
Yeah. I mean, my personal view on this is that there are a number of provisions that are pretty straightforward. That’s not to say operators shouldn’t review them carefully and just make sure and make comments where they need tweaks, but at a kind of a higher level approach.
Integrity management is one PHMSA proposed to require vapor dispersion modeling that includes things like temperature, weather conditions, terrain, pipeline parameters, the makeup of the CO2. That’s something operators are doing already. Developers are doing already.
That’s something that, again, at a higher level, operators are going to welcome that, because it puts on the books something they’re already doing to try to be safe. I don’t anticipate a lot of controversy around that.
In terms of other relatively straightforward provisions. There’s a new right-away inspection requirement where you got to look for geohazards and depth of cover. That’s going to be pretty straightforward. Operators are already looking for geohazards. They’re taking action to address the ones that they need to address.
There are some new requirements around remediating reduced depth of cover. That’s a new thing. I think, though, that a lot of operators are already doing that, at least in the areas where it makes sense to do it. Probably not a huge controversy there.
Leak detection is another one. Some fairly straightforward changes to apply leak detection to CO2. Most operators are already doing that anyway. Vapor detection and alarms. This is a new thing where at any above-ground facility, whether it’s a pump station, a valve site, meter station, PHMSA is proposing to have CO2 vapor detection. This also would apply to HVL lines, so hydrocarbon, HVL, your butane lines, things like that.
Russel: Most operators are doing that already.
Jim:
Yeah, that’s right. I don’t see that being controversial. There’s some reporting changes. One of the bigger changes in the role is that PHMSA is now applying Part 195 to other phases of CO2.
For the most part, CO2 has moved to what’s called a supercritical phase, which is like a dense vapor phase. There are some projects out there that are proposed to move CO2 in a gas phase.
PHMSA is proposing to bring in CO2 under Part 195, regardless of whether it’s gas, liquid, supercritical. That’s expected. We knew that was going to happen. I don’t think that’s terribly controversial.
There’s a couple of other ones. There’s some fracture control requirements. Those have been in there for a long time, since the mid-1990s. They’re now going to be more prescriptive. Operators expected that. That’s just a handful of some of the non-controversial changes. If you’d like, we can get into the ones that are a little bit trickier.
Russel:
I want to talk about that first because I’m sure that’s the stuff that people are more interested in. I think it’s important. A lot of times…well, I don’t know. I’m stating something that’s an opinion. I don’t really have any fact to back up.
I think sometimes that we read these rules, and we get all hung up on the one or two things that are a bit outlandish, and we don’t look at the 9 or 10 things that are reasonable, and straightforward, and appropriate, right?
Jim: Yeah.
Russel: I always want to cover that because the industry, we do want to do better. We do want to be safer. We do want to do those things that make sense and are reasonable, economic, sustainable, all that stuff. What’s the bits that’s a bit more controversial?
Jim:
There’s a few. One, we already started talking about, and that’s this essentially set of location-based requirements. I already talked about one of them, this two-mile provision, where, if you are a developer and you put a new line in, and you are less than two miles from any residence, occupied structure, place, and assembly, you have to document why it was impractical to avoid that.
Again, that’s not a location requirement. You can be less than two miles, but there again the inference is that something about two miles is there’s a heightened safety risk. I don’t know if operators will necessarily agree with that in all cases. That’s one.
There’s another buffer provision, which basically you have to do a population density survey. That one’s actually a wider buffer. That’s a four-mile buffer. It’s two miles on either side of the pipeline.
You got to figure out everybody who lives there, and you have to collect personal information about each individual cell phone numbers, whether they’re mobile or not, whether they are able to get out in the event of a release, so on and so forth.
As an initial matter, to be very clear, industry wants to educate people who live near pipelines on what to do if there’s a release and give them the tools they need to be safe so. You know this as well as I do, the industry has been doing that on a public awareness program for a generation or more with good success. Again, the question here is more of a practicability question.
I think operators want to protect people. I know they do. Is it practicable to get personal information from individuals within two miles of the center line of a pipeline? I can imagine areas of the United States where, if pipeline operator shows up at your house and says, “Can I have your cell phone number? How old are you?”
Russel: [laughs]
Jim: “Can you get out of here on your own?”
Russel: I wouldn’t want to try that back in the hauler’s Appalachia, let me tell you.
Jim: But as proposed, they have to do it. Operators are not going to be able to make people give up that information.
Russel: No.
Jim:
The question here, the challenge for us as operators, who want to protect people, is to say, is this practicable? Can we do this? If not there, is there a better way? I think this is the opening of a conversation on that point.
Also, probably even the bigger problem…I think we’ll get through that, we’ll figure out how what the right answer is there. The bigger problem though is this — and it’s like that two-mile proximity issue, only bigger — the inference is if you live within two miles on either side of a pipeline, so a four-mile corridor, there’s somehow a greater risk in that area.
Is that true in the case of every CO2 pipeline? If I have a four-inch line, am I going to have CO2 that moves miles and miles away from that line? Let’s see what the modeling says. If it doesn’t, maybe that buffer doesn’t need to be as big, or we at least need to acknowledge that this is an interesting commodity.
It behaves in certain ways. We have good ways of modeling that. Let our decisions be based on that modeling and not on these really big assumptions that we need huge…
[crosstalk]
Russel:
What we’re talking about is what is an appropriate level of public safety. Because I would argue, from a public perspective, the closer I am to the pipeline, the greater my risk.
I would make that argument. I think that argument’s true. But how far away do I have to get before my risk is near zero? How near zero do I need to be? That’s more of a technical argument, versus it’s two miles. Because at two miles, for most pipelines, in most situations, there’s zero risk, I would think.
Jim: That’s right.
Russel: At one mile, for most pipelines, in most situations, there’s zero risk.
Jim: That’s right.
Russel:
That creates a unnecessary burden without creating any additional safety performance, which is the point you’re making. You’re right. If PHMSA says it’s got to be two years, then people who don’t know the technical pieces of that are going to read that and they’re going to go, “Oh, it’s got to be two miles.” Sorry, two years.
If it’s got to be two miles, then people that don’t know are going to read that and say, “If it’s less than two miles, that’s bad.” Well, not necessarily bad.
Jim:
That’s right. That’s what we don’t want to happen. I think we owe it to the public to just be a little bit…They can understand. They can understand things. When you explain, I think they can understand something less than, “Oh, it’s got to be two miles.”
[crosstalk]
Russel: I think people, by and large, want to be educated. They want to know the details, right? They want to know the details.
Jim:
That’s one. I think we as an industry can get to a good spot on that. It’s probably going to need to be a little bit more risk-based, a little more focused, but I think we can get where we need to be on that.
[crosstalk]
Russel: I think industry wants to know those answers too.
Jim: For sure. [laughs]
Russel: I want to know that, for this pipeline and this location, I need to be concerned about people within this proximity. Industry wants know that.
Jim: Yeah, they absolutely do. They absolutely do. Also, they want to program their resources…
Russel: They want that to be reasonable. I don’t want to have to worry about people that I don’t need to worry about.
Jim:
Exactly. Couple of other ones. Let’s talk about conversion to service. This is a really interesting one. Conversion. What is conversion to service? This is a provision that’s been in the code since the late ’70s that allows you to convert a non-part 195 line to a part 195 line.
That could be you’re converting an unregulated asset to 195 service, or you’re converting a part 192 gas pipeline to 195 service. You’ve been able to do that since the late 1970s. Basically, what you had to do is do a careful review of the line, make a plan, review records, pressure-test the line, make any repairs you need to make, and then you could convert.
The bargain there has always been, you didn’t have to comply with the design and construction requirements as if the line were new because, in most cases, you could not do that because of the very specific requirements and all the API standards, and ASME standards incorporated into the code.
Older lines are part 192 lines, don’t necessarily line up with part 195. You didn’t need to rebuild, redesign, reconstruct the line. That’s been in the code since the ’70s. FERC actually asked for that in 1978 or ’79 when PHMSA first did this rulemaking.
They said, “Wait a minute. You can’t make people comply with design and construction requirements. They’re never going to be able to do it, and then we won’t be able to reuse these assets. They’ll lose their economic value.”
PHMSA said, “All right, we won’t make people do that. We’ll make them pressure-test.” That’s been the role for my whole life. PHMSA was proposing to change that arrangement and require converted lines to comply with current design and construction standards.
I think that’s a major change. I think operators should ask, is that going to work? The devil’s in the details here. Say you’re converting a 192 line to 195 service…
Russel: I can tell you right off the face of that, if I found myself in a situation where I was required to take a existing line but do all the things I would do for a new line, then that project becomes completely uneconomic.
Jim: Yeah, because you’re digging up every girth weld and…
Russel: You dig up every well, you’ve got to expose every valve, you’ve got to categorize every stick or pipe. Nobody’s doing that.
Jim:
That’s right. We have other tools. We have ILI tools, we can pressure-test, we can do selective digs, that sort of thing. Even, let’s say you built a line to part 192 20 years ago. Is that going to comply with part 195 design and construction standards today?
It’s not because those rules have changed and the incorporated versions of the key standards, API 5L for line pipe, 1104 for welding, those have all changed. The versions have changed over the years. I think the good news here is PHMSA has basically said in this rulemaking, “We’re open to comments on whether this is practicable or not.” I think operators should weigh in on that, for sure.
This isn’t just for CO2. This is all hazardous liquid lines. There are some heightened provisions for CO2 and HVL lines, but this design and construction thing we’re talking about is any kind of conversion to part 195. I would encourage operators to focus on this one.
There’s some other stuff in the conversion rules too. If you’re going to convert to CO2, you have to spike-test. You got to do close interval surveys, coding surveys, you got to run ILI tools. Those provisions are also worth taking a look at. A number of operators will do some of those things, perhaps not all of them, and it’s going to depend on the assets. I’d encourage folks to look at that.
In terms of other bigger-picture items that are worth taking a look at, I’ll give you two more. One is this proposal to redefine carbon dioxide as a highly volatile liquid. In 195, highly volatile liquids have always been defined as liquid hydrocarbons with a certain vapor pressure.
Your butanes and things like that, your more volatile NGLs, will test out as highly volatile liquids. PHMSA is now proposing to include CO2 as a highly volatile liquid. When you first hear that, you say, “Well, CO2 is volatile. That makes sense.”
Russel: I don’t agree with that, though, because most of those things are explosive. When I think of volatile, I think of explosiveness. CO2 is not explosive. In fact, it’s the opposite.
Jim:
That’s right. I think this is one where it’s going to require some more parsing. The first thing that hits from my perspective on this redefinition is, HVL, the acronym is used throughout the code to drive heightened requirements throughout the code for over-pressure device inspection, integrity management, valve spacing.
I think valve spacing is going to be a big one. If you have an HVL line under the valve rule and you’re in an HCA, you have to have much tighter valve spacing. It’s about half the distance that you would have for other types of assets. That’s going to drive a lot of valve installation potentially on new projects. That’s worth taking a look at.
The way that PHMSA has done this in its proposed change to the rules, it would retroactive that requirement to the final effective date of the valve rule so that it would retroactive that requirement to lines built after April of 2023.
There are some significant legal problems with that, and actually think it’s probably a mistake on PHMSA’s part. It’s probably easy to fix, but that’s how 195, 260 modification is drafted. I encourage folks to take a look at that and comment on that.
Like I said, there’s a host of other things that would happen on CO2 assets if they’re redefined as HVLs. Different pressure testing requirements, different over-pressure device testing requirements. That’s number one.
Russel:
I think what’s going on there is PHMSA is trying to say that we need to enhance standard of care for CO2. We already have a rubric for that and that’s HVL. Let’s just classify CO2 as HVL, and then we’ve got an enhanced standard of care. That’s where they’re coming at it.
From an engineering basis, that’s fundamentally flawed because the nature of the fluid is different, the nature of the risk is different, the nature of the infrastructure’s different, and right now, all that matters.
Jim:
Let me give you one more. Just looking through my notes here. This one’s interesting. This is actually in the scope provision of part 195. There has long been an exception in 195(i) for CO2 branch lines that branch off and go to enhanced oil recovery injection wells.
There’s these little branch lines coming off the manifold that go out to the wellhead, and they inject it into the formation, inject CO2. The small branch lines have been exempt from Part 195. They’re in the production field, typically remote areas.
PHMSA has proposed a modification to that, to treat essentially the same kind of branch line, where if that branch line goes to a permanent sequestration wellhead, Class VI, UIC wellhead, not an EOR wellhead, that that line is not exempt.
It’s full part 195. They don’t really explain why there’s a different treatment there. If you just go out and look at these things, they’re very similar, smaller diameter going out to the wellhead for permanent sequestration.
I think this is an area where some operators may want to comment and say, “Let’s have some fidelity here. Let’s treat the EOR lines the same as classics lines. They’re doing the same thing, very similar things.”
Russel:
Jim, before we start talking about where we’re in the process, I want to roll back a little bit. Are there other types of operators other than CO2 that are impacted by this and what are those…?
[crosstalk]
Jim:
Definitely. The dispersion modeling provisions that we talked about earlier, this rule would actually apply those to HVL operators too. I think a number of HVL operators are already doing some form of dispersion modeling.
May or may not be a big impact, but I would encourage them to take a look. The conversion to service regs that we talked about, not just for CO2, but also for other assets…
[crosstalk]
Russel: Any 192 to 195 transition.
Jim: Yeah, or even a non-regulated to 195 transition. Those are the two biggies for me.
Russel: For listeners, make sure that people in your company are aware of these facts so that you don’t read this as a CO2 rule and think, “We’re not CO2. It doesn’t affect us.” It’s a 195 rule that’s mostly about CO2.
Jim: That’s a good way to talk about it, for sure.
Russel:
That’s one key takeaway from this particular conversation. Then lastly, I want to pick up and talk about where we go for here. We said that it’s a not-yet-published rule. It’s been pulled back.
It’s not congressionally mandated, but there is a fair amount of industry, and regulatory, and public interest in getting this done, so it’s probably going to happen in some time frame. You’ve been saying this as we’ve been talking, “Make your comments. Make your comments.” That’s where we are in the process.
Operators should review the rule, look for the things they’re concerned about, and get their comments in either directly to PHMSA or through whatever industry peer they use, whether that’s API, or GPA, or whatever.
Jim: That’s exactly right. They won’t be official rulemaking comments, but you can still reach out to the agency and say, “Hey, look, here’s what works and here’s what doesn’t.”
Russel: The next thing that’ll happen is the agency will take all that stuff, they’ll distill it all down, and then they’ll call for an LPAC meeting. During the LPAC, they’ll take this before that committee and make recommendations. Now is the time you have the opportunity to effect change.
Jim: That’s right.
Russel: Don’t waste the opportunity. [laughs]
Jim: That’s right. I think we’ll get to the right place as a stakeholder group.
Russel: Great. How do you feel about your first appearance on the Pipeliners Podcast?
Jim:
This has been great. I’ve enjoyed chatting with you. You ask great questions. I feel like we’ve had a great discussion. I appreciate it.
[crosstalk]
Russel:
I’ve enjoyed having you. I think you did well. Keith is going to be jealous, because normally, when Keith comes on, I ask him some kind of question from out of bounds that he’s not ready to answer. I don’t think I did that to you, so he’ll be jealous.
[laughter]
Jim: That’s great.
Russel: Thanks for coming. Appreciate your time.
Jim: Thank you.
Russel:
I hope you enjoyed this week’s episode of the Pipeliners Podcast and our conversation with Jim. Just a reminder before you go, you should register to win our customized Pipeliners Podcast YETI Tumbler. Simply visit pipelinepodcastnetwork.com/win and enter yourself in the drawing.
If you’d like to support the podcast, best way to do that is to leave a review. You can do that wherever you happen to listen.
[background music]
Russel: If you have questions, ideas, or topics you’d be interested in, please let me know on the Contact Us page at pipelinepodcastnetwork.com or reach out to me on LinkedIn. Thanks for listening. I’ll talk to you next week.



