API 570 — Piping Inspection Code

In-service inspection, repair, alteration, and rerating of process piping per ASME B31.3 — sets interval, CML, and class-based inspection extent.

Scope

API 570 — Piping Inspection Code — is the inspection-side companion to ASME B31.3 (Process Piping). API 570 governs in-service inspection of piping systems in petroleum, petrochemical, chemical, and similar process facilities. It applies to piping originally constructed to B31.3, B31.4, or B31.8 (with most application against B31.3). The scope includes hydrocarbon service piping, hazardous-service piping, and high-temperature piping in operating units. Utility piping (cooling water, instrument air) is generally excluded unless specifically incorporated by the operator's policy. API 570 establishes the Authorized Piping Inspector role, piping service classification system, inspection intervals per class, CML selection, and acceptance criteria for in-service piping. The current edition is the 5th Edition (December 2022) with Addendum 1 (2023).

NDT methods it governs

{"label":"API 570 Piping Inspection Code","href":"/blog/api-570-piping-inspection-code-requirements"}
{"label":"CUI Detection","href":"/blog/corrosion-under-insulation-cui-detection-guide"}
{"label":"Pipeline Integrity Inspection","href":"/blog/ndt-pipeline-integrity-inspection-guide"}
{"label":"Ultrasonic Testing (UT)","href":"/blog/ultrasonic-testing"}
{"label":"Risk-Based Inspection (RBI)","href":"/blog/risk-based-inspection-rbi-implementation-guide"}

Certifications that reference it

{"label":"API 570 Piping Inspector Certification","href":"/api-570-certification"}

Issuing body

API

Revision history

2023 —
2022 —
2016 —
2009 —

Related standards

api-510 · api-571 · api-579 · api-580 · api-581 · api-1104 · asme-b31-3 · asme-section-v-article-4 · asme-section-v-article-23

Applying this in an inspection programme

Code compliance is only demonstrable if the evidence behind it is: the procedure revision in force, the inspector's certification state and the instrument's calibration status at the time of test. Atlantis NDT provides ASNT Level III consulting for procedure and written-practice work against this code, training toward the certifications that reference it, and inspection management software that keeps that evidence recoverable years later. Request a consultation.

How a standard like this is applied in an inspection programme

A standard is only half of the requirement. It defines how an examination is performed and, in some cases, how results are classified — but the acceptance criteria that decide whether a component stays in service normally come from the construction or in-service code governing the item, not from the examination standard itself. Confusing the two is one of the more common findings in a procedure review: a procedure that correctly cites the examination standard but applies acceptance criteria from the wrong code or the wrong edition.

What has to be in place for compliance to be demonstrable

A written procedure qualified against this standard for the specific materials, thickness ranges and geometries in scope — not a generic procedure covering everything
Personnel certified for the method and level under ASNT SNT-TC-1A, ANSI/ASNT CP-189, NAS 410 or ISO 9712, current on the date the examination was performed
Equipment, probes and reference standards in calibration on that date, with traceability to a national standard under ISO 17025
The applicable edition of the standard recorded against the examination, so historical work stays assessed under the edition then in force
Technique sheets under the same revision control as the procedure above them — the most frequently uncontrolled document in an otherwise compliant quality system

Edition changes

When a new edition is issued, new work moves to it from a defined effective date that you set and record; work already performed stays assessed under the edition in force at the time. Retrospectively applying a new edition to historical dispositions invalidates the original acceptance decision and creates a substantially larger problem than the one being solved.

Where this usually goes wrong

Not in the technical content, but in reconstruction. An auditor picks an issued report and asks which procedure revision applied, who performed the work and whether they were qualified on that date, and whether the instrument and reference blocks were in calibration. Programmes that hold only current state can answer none of those. Binding the document revision, the qualification state and the calibration state to each inspection record as it is created turns that from an investigation into a lookup.