API 1160: Hazardous Liquid Pipeline Integrity, Risk, and Repair

API Recommended Practice 1160 is a voluntary industry standard from the American Petroleum Institute that gives hazardous liquid pipeline operators a structured way to manage the integrity of their systems. Now in its third edition, published in 2019, API 1160 walks operators through building, running, and improving an integrity management program that lines up with the federal requirements in 49 CFR 195.452.¹ The federal rule is mandatory. API 1160 is not. But because the standard translates the legal obligations into a workable process, many operators use it as the backbone of their written integrity programs.

What API 1160 Applies To

The standard is written for pipelines carrying hazardous liquids. Under federal regulation, that means petroleum, petroleum products, anhydrous ammonia, and ethanol or other non-petroleum fuels (including biofuels) that are flammable, toxic, or could harm the environment if released in significant quantities.² Crude oil, gasoline, jet fuel, diesel, and liquefied petroleum gases all fall inside that scope.

API 1160 is not itself a regulation. No operator gets fined for violating it directly. What it represents is an industry consensus on best practices, and its structure closely tracks what the Pipeline and Hazardous Materials Safety Administration expects operators to do under the federal rule.¹ Following the recommended practice goes a long way toward demonstrating compliance.

High Consequence Areas Set the Scope

The federal integrity management rule applies to any pipeline segment that could affect a High Consequence Area. HCAs include commercially navigable waterways, high population areas, other populated places like incorporated cities and towns, and unusually sensitive areas such as drinking water sources and ecological resources.³ If a segment could affect one of these, it is covered.

Operators have to verify these risk factors at least annually, and no longer than every 15 months, because new construction, shifts in population, or newly identified sensitive resources can bring additional pipe under the rule. When a new HCA appears, the operator has five years to complete a baseline assessment of the newly covered segments.⁴

How the Program Works

API 1160 organizes integrity management as a continuous cycle: gather data, assess risk, inspect the pipe, fix what you find, and evaluate how well the program is working.¹ The starting point is dividing the system into manageable segments and building a data management plan for each one.

Data integration is more involved than it sounds. Federal regulations list over twenty categories of information that operators must pull into their analysis: pipe diameter, wall thickness, grade, seam type, coating condition, maximum operating pressure, cathodic protection readings, close interval survey results, depth of cover, stress corrosion cracking findings, and the location of foreign line crossings, among others.⁴ Storing this in a geographic information system is not the point. Operators have to analyze how the data points relate in space, like whether corrosion anomalies cluster near foreign line crossings.

API 1160 also requires a formal Management of Change process. Any modification to the pipeline, its operations, or the integrity program itself has to be evaluated before implementation. That catches situations where an operational change, like increasing throughput or switching products, could introduce a threat the existing program was not designed for.

Assessing Risk

Risk assessment is where the program decides what to worry about and in what order. Operators identify every credible threat to each segment, then evaluate how likely each threat is to cause a failure and how severe the consequences would be. API 1160 supports multiple approaches, from relative risk ranking models to more quantitative, scenario-based analyses.

Threats generally fall into three categories. Time-dependent threats, like internal and external corrosion, get worse the longer they go unaddressed. Stable threats, such as manufacturing defects or old construction damage that has not grown, stay roughly the same over time but can still cause failures under the right conditions. Time-independent threats, like third-party excavation damage or weather-related ground movement, can happen at any time regardless of the pipe’s age.¹

The consequence side considers what would happen if a release occurred at a specific location. A failure in a remote stretch of desert is a different problem than a failure near a municipal water intake. The resulting ranking drives which segments get assessed first, which method is used, and how aggressively repairs are scheduled.

Choosing an Assessment Method

Federal regulation permits four assessment approaches, and API 1160 gives guidance on when each is appropriate.

In-line inspection uses instrumented tools, commonly called smart pigs, that travel through the pipeline collecting data on wall condition. Magnetic Flux Leakage tools detect metal loss from corrosion. Ultrasonic Testing tools measure wall thickness directly. Segments susceptible to cracking require tools capable of detecting crack anomalies.⁵
Hydrostatic testing fills the segment with water and pressurizes it above its maximum operating pressure to prove structural integrity. It validates strength without pinpointing individual anomalies.
External Corrosion Direct Assessment is a multi-step process using aboveground surveys and targeted excavations to evaluate corrosion on segments where running in-line tools is impractical.
Other technology is permitted if the operator can demonstrate it provides an equivalent understanding of the pipe’s condition, with advance notification to PHMSA at least 90 days before the assessment.⁵

In-line inspection is the default. The regulation only allows the other approaches when in-line inspection is impractical because of the pipeline’s construction (diameter changes, sharp bends) or operational limits like low flow or pressure.⁴

Repair Timelines

What happens after an assessment finds a problem is the area where the rules are most specific and operators have the least room for judgment. Federal regulation sets three remediation tiers based on severity.

Immediate Repair Conditions

Certain findings require the operator to either reduce pressure or shut down until the repair is complete. These include metal loss exceeding 80 percent of nominal wall thickness, any anomaly where the calculated burst pressure falls below the maximum operating pressure, dents on the top of the pipe (above the 4 and 8 o’clock positions) showing metal loss or cracking, and top-side dents deeper than 6 percent of the pipe’s diameter.⁶ If no recognized remaining-strength calculation method applies, the operator has to reduce pressure by at least 20 percent until the repair is done.

60-Day and 180-Day Conditions

Less severe anomalies still trigger mandatory timelines. The 60-day category includes top-side dents deeper than 3 percent of the pipe’s diameter and bottom-side dents with any sign of metal loss or cracking. The 180-day category covers dents deeper than 2 percent that affect girth or seam welds, and top-side dents deeper than 2 percent without the complications that would push them faster.⁶

The repair methods themselves range from installing steel sleeves over damaged sections, to grinding out minor surface defects, to cutting out and replacing pipe. In some cases the operator can reduce the segment’s maximum operating pressure as an interim or permanent measure instead of performing a physical repair. API 1160 walks through the decision process for choosing the right response based on defect type, severity, and operating conditions.¹

Reassessment Intervals

Integrity management is not a one-time exercise. After the baseline, operators must reassess each covered segment on intervals that cannot exceed 68 months, and scheduling within that window is risk-based: higher-risk segments come up sooner.⁴

Variances are possible in limited situations. One path requires an engineering justification supported by external monitoring technology that provides an equivalent understanding of the pipe’s condition. The other applies when the necessary inspection technology simply is not available for that segment. Both require advance notification to PHMSA (270 days for engineering-based variances, 180 days for technology unavailability) and a showing of interim measures.⁷

Between formal assessments, operators track performance metrics like leak frequency, the number and severity of anomalies found in each cycle, and how quickly repairs are completed.⁴

Prevention and the Feedback Loop

Assessment and repair address problems that already exist. The preventive side of API 1160 focuses on keeping new problems from developing. Corrosion prevention is the most direct example: maintaining cathodic protection systems and protective coatings to slow the electrochemical reactions that eat away at buried steel. The standard expects operators to monitor cathodic protection effectiveness and address deficiencies before measurable metal loss occurs.

Third-party damage prevention is a different problem, since it depends on people who do not work for the operator. API 1160 addresses this through public awareness programs, participation in one-call excavation notification systems, and increased patrolling in areas with heavy construction. For segments in or near HCAs, the stakes justify more aggressive measures like physical barriers or additional depth of cover.¹

The effectiveness of these measures feeds back into the risk assessment. If corrosion rates decline after a cathodic protection upgrade, the segment’s risk profile improves. If third-party damage incidents rise near a rapidly developing area, the profile worsens and may trigger an earlier reassessment. That feedback loop is what API 1160 means by continuous improvement, and it is what separates a paperwork exercise from a program that actually reduces the likelihood of a pipeline failure.

1
American Petroleum Institute. API Recommended Practice 1160, 3rd Edition
2
eCFR. 49 CFR 195.2 – Definitions
3
eCFR. 49 CFR 195.450 – High Consequence Area Definition
4
eCFR. 49 CFR 195.452 – Pipeline Integrity Management in High Consequence Areas
5
GovInfo. 49 CFR 195.452 – Pipeline Integrity Management in High Consequence Areas
6
eCFR. 49 CFR 195.452 – Pipeline Integrity Management in High Consequence Areas
7
GovInfo. 49 CFR 195.452 – Pipeline Integrity Management in High Consequence Areas