API 570 Piping Inspection Code Explained For People Who Actually Have to Use It
API 570 is the standard for inspecting, rating, repairing, and altering piping systems that are already in service. The latest version is the 7th edition, published in 2022. It replaced the 6th edition that had been around since 2014. If you work in refining or petrochemical, you are almost certainly using it daily whether you realize it or not. The 7th edition made several notable updates. Risk-based inspection (RBI) methodology got more detailed integration throughout the document rather than being an add-on chapter. There were also clarifications on fit-for-purpose assessments, better alignment with ASME B31.3 for design-by-engineering calculations, and updated references to nondestructive examination methods. Material degradation mechanisms section was expanded significantly. That one matters because the old edition lumped a lot of stuff together and inspectors would skip past it. The big structural change is how the code now handles in-service inspection planning. It pushes harder on justifying inspection intervals based on actual corrosion data and operating history rather than default timelines. This isn't just paperwork. I ran into a situation last year where a refinery wanted to extend an inspection interval on a crude unit feed heater piping from 5 years to 10 based on minimal corrosion rates. The 6th edition would have let them get away with weaker justification. Under the 7th edition you need a documented reason that holds up under scrutiny, including data on temperature cycling effects and potential for localized corrosion under insulation. We spent three weeks compiling historical thickness readings and failure mode analysis before the plan was accepted.
How the Code Is Actually Structured
The 7th edition is organized into numbered chapters and annexes. The main body covers general requirements, inspection planning, examination techniques, evaluation criteria, repair and alteration procedures, and pressure testing. The annexes contain supplementary guidance including RBI methodology, damage mechanism flowcharts, and example calculations. Annex A through Annex F each serve different purposes. Some are mandatory while others are informational only. Confusing them costs time in the field. Chapter 5 on examination and measurement is probably the most frequently referenced section. It specifies what NDE methods are acceptable, when to use them, and how to interpret results. Section 5.3 deals specifically with thickness measurement survey procedures. The code requires a minimum survey area definition based on the piping system's risk classification and corrosion rate history. A high-risk system with aggressive service conditions gets a much more thorough baseline than something moving clean water at ambient temperature. I have seen inspectors cut corners here by applying low-risk survey criteria to high-risk lines. It comes back to bite you during the next turn-around when they find wall loss they should have caught years earlier. Chapter 6 covers evaluation of piping components. This is where you determine whether remaining thickness is adequate, whether detected flaws are acceptable, and whether the system can continue operating until the next inspection. The formula for minimum required thickness uses the same basic parameters as ASME B31.3 but the application and acceptance criteria come from API 570. The key difference between simply applying the formula and actually understanding what it tells you is knowing when the formula breaks down. It assumes homogeneous material and uniform corrosion. Pitting corrosion, erosion patterns, and metallurgical degradation like graphitization or temper embrittlement do not fit neatly into that assumption. The code acknowledges this in various sections but leaves a lot of interpretation to the inspector's judgment. That is both the strength and the weakness of this standard.
Repair and Alteration Procedures Chapter 7
Chapter 7 is where most people encounter friction. It lays out what constitutes a repair versus an alteration and the different approval paths for each. Minor repairs can often be handled by the authorized piping inspector without going through a full engineering review. Major alterations require design calculations, welding procedure qualifications, and sometimes a re-rating of the entire system. The line between minor and major is not always clear and the 7th edition did not completely resolve this ambiguity. I dealt with a case where replacing a single valve on a high-pressure steam line was debated for two weeks. One camp said it was a minor repair since it was a like-for-like replacement. The other camp argued that any component change on a Class 400 steam system constituted an alteration requiring re-rating. We ended up doing the full alteration paperwork because the insurance carrier's requirements were stricter than the code minimum. The code itself does not address insurance-driven requirements. Welding repairs under API 570 require preheat and post-weld heat treatment when the material specifications demand it. The code references ASME Section IX for WPS qualification but adds its own requirements for repair welds on in-service piping. Preheating during in-service repair is complicated by the fact that you cannot always shut down the line. The 7th edition provides guidance on heating techniques that work around operating conditions but the practical reality is that many field conditions make proper preheat difficult to achieve. You end up making engineering judgments based on what is actually achievable rather than what the ideal procedure demands. Document those judgments carefully. They will be tested during an audit or after an incident investigation.
Get the Full Details
Pressure Testing Requirements
Chapter 8 covers pressure testing after repairs and alterations. The standard test pressure is 1.5 times the design pressure for liquid tests. Gas tests require 1.1 times the design pressure with special precautions. The 7th edition tightened the requirements for pneumatic testing, adding more stringent safety considerations. This is not surprising given the number of incidents related to pneumatic test failures in the industry. In practice, pressure testing in-service piping systems is one of the most difficult applications of this code. You cannot always isolate the section you repaired. You cannot always drain and fill with test medium. I worked on a hydrotreater feed-effluent exchanger piping repair where we needed to pressure test a segment that shared headers with running units. The only viable option was a low-pressure pneumatic test with additional monitoring and exclusion zones. The code allows this under specific conditions but the documentation and safety measures required were extensive. The test itself took longer to set up safely than it would have taken to replace the entire section and bring it online fresh. Sometimes the code gives you an option that is technically compliant but practically worse than doing something else entirely.
Common Mistakes I See Onsite
Inspectors relying too heavily on default inspection intervals without reviewing actual corrosion data. The code is explicit about this but it keeps happening. Auditors flag it constantly. Confusing API 570 requirements with ASME B31.3 requirements. B31.3 governs new construction design. API 570 governs in-service inspection and repair. They overlap but they are not the same document. Using B31.3 acceptance criteria for an in-service evaluation can give you the wrong answer. Skipping the CSE (Corrosion Speed Estimate) recalculation after a major repair or alteration. The code requires updating the CSE when operating conditions change significantly. People forget this. The next inspection interval may be wrong as a result.
Accepting NDE results without verifying the examiner's certification level and equipment calibration. I have seen reports signed by Level II technicians who had let their certification lapse. The code requires current certification. It is easy to miss during a busy turn-around schedule.
Where to Get the Document
API 570 is a proprietary standard published by the American Petroleum Institute. You can purchase it from api.org or from authorized distributors. There is no legal free version. Any site offering a free PDF download is distributing it illegally. Don't bother with those copies. The printing quality, formatting, and page numbers matter when you need to reference a specific clause during an inspection or an audit. The illegal versions often have corrupted annexes or missing pages from the binding process. If your company already holds an API license or is an API member, you may have access through institutional licensing. Check with your engineering department or compliance team before buying individual copies. Bulk pricing is available for organizations that need multiple copies for field teams.
A Note on How Far This Code Actually Reaches
API 570 does not cover everything. It does not address offshore piping systems those fall under different standards like API RP 571 and associated offshore codes. It does not apply to process vessels or equipment that are covered by API 510. It does not govern pipeline transportation systems which fall under ASME B31.4 or B31.8. Within its scope it is comprehensive but the boundaries matter. I had a conversation with an inspector who was applying API 570 to a ship-to-shore loading arm and could not figure out why the acceptance criteria did not match what he expected. The loading arm was outdoor ambient service but it was still outside the normal scope of the code's typical refinery application. The code also does not provide detailed procedures for every possible repair scenario. It sets the framework and the requirements but leaves the specific engineering solutions to the authorized inspector and the responsible engineer. This is intentional. No single document can cover every combination of material, service condition, geometry, and degradation mechanism. The tradeoff is that you need competent people interpreting it rather than someone following a checklist blindly. Competent people are harder to find than checklists. One thing the 7th edition does not adequately address is the intersection with digital inspection technologies. Automated ultrasonic scanning, robotic crawlers, and digital radiography are becoming common but the code still references traditional hand-held UT and film radiography as primary methods. The acceptance criteria are tied to those methods. Using newer technologies requires engineering justification that the alternative method provides equivalent or better coverage. This is not impossible but it adds a layer of documentation that slows down adoption. I expect future editions to catch up. In the meantime, the companies moving fastest on this are the ones that built their internal procedures around the flexibility the code already provides rather than waiting for it to change.
