Three codes. Three asset classes. One mistake that gets expensive: assuming any of them are interchangeable.
API 510, API 570, and API 653 are the in-service inspection codes that govern pressure vessels, process piping, and aboveground storage tanks across the refining, petrochemical, and process industries in Canada. They share the same regulatory DNA — a maximum interval, a written inspection plan, certified inspector qualifications, and a path to fitness-for-service when a flaw is found. They differ on what they cover, how often the asset must be inspected, and which findings trigger which engineering response.
If you are responsible for an aging fleet of vessels, piping circuits, or atmospheric tanks at a Canadian site, this is the working summary your inspection budget should be built on.
The 30-second decision tree
In-service pressure vessels (most ASME Section VIII Div. 1, 2, 3 equipment) — Code: API 510 | Latest edition (as of 2026): 11th Edition, October 2022 (Errata 1, March 2023)
In-service metallic and FRP process piping — Code: API 570 | Latest edition (as of 2026): 5th Edition, February 2024
Aboveground welded steel storage tanks (built to API 650 or older API 12C) — Code: API 653 | Latest edition (as of 2026): Current published edition with periodic addenda
If the asset is a pressure vessel, API 510 governs. If it's process piping, API 570. If it's an aboveground welded tank, API 653. Simple in principle. Less simple when the asset is an integrally piped vessel skid, a knockout drum on a relief line, or a heat exchanger with internal piping — the kind of edge cases where a procurement spec gets written against the wrong code and the inspector arrives with the wrong qualification.
API 510 — Pressure Vessel Inspection
What it covers: In-service inspection, repair, alteration, and rerating of pressure vessels — primarily ASME Section VIII vessels in process service. Includes the inspection planning, frequency, and acceptance criteria that determine when a vessel is fit to remain in service.
Inspector qualification: API 510-certified inspector under the supervision (or as the responsible authorized inspector) of an organization with a documented inspection program.
Typical inspection types:
- External visual at fixed intervals (commonly ≤5 years)
- Internal inspection at intervals not exceeding half the remaining life or 10 years, whichever is less
- On-stream inspection (UT thickness, PMI, visual) on a documented frequency
- Pressure tests after major alteration
Common findings that trigger engineering work:
- Wall loss below MAWP-rated thickness → fitness-for-service evaluation under API 579-1/ASME FFS-1
- Cracking discovered by WFMT, PT, or PAUT → repair procedure development with welding engineering input
- Material substitution discovered through PMI/XRF → metallurgical assessment
In Canada, API 510 inspection is overlaid on jurisdictional requirements — in BC, that means coordination with Technical Safety BC (TSBC); in Alberta with ABSA. A clean API 510 program does both: meets the API code intervals and satisfies the provincial regulator's pressure equipment program.
API 570 — Piping Inspection
What it covers: In-service inspection, repair, alteration, and rerating of metallic and fiberglass-reinforced plastic (FRP) process piping systems and their pressure-relieving devices. Updated to the 5th Edition in February 2024, with strengthened guidance on inspection planning, damage mechanisms, and CUI management.
Inspector qualification: API 570-certified inspector working under a documented owner/user inspection program.
Typical inspection types:
- Visual external inspection on a circuit-by-circuit basis
- Thickness monitoring at established CMLs (Condition Monitoring Locations)
- Corrosion under insulation (CUI) inspection on susceptible circuits — increasingly via PEC, eddy current, and drone-based aerial NDT for CUI screening
- Class 1, 2, 3 service classification driving inspection frequency
Common findings that trigger engineering work:
- Localized thinning at injection points, deadlegs, or mix points → API 570 + API 579 fitness-for-service evaluation
- Crack-like indications in welds → PAUT/TOFD characterization, welding engineering review
- Failed CUI inspection on insulated circuits → repair scope, possibly insulation replacement
The 2024 update to API 570 places more weight on damage mechanism identification and risk-based inspection (RBI) integration. If your last piping inspection plan was written against the 4th Edition or earlier, the methodology gap is worth a review.
API 653 — Aboveground Storage Tank Inspection
What it covers: Inspection, repair, alteration, and reconstruction of welded steel aboveground storage tanks built to API 650 (or the older API 12C). Tanks in product service — crude, refined products, fuels, water for process — that fall under the API atmospheric tank fleet.
Inspector qualification: API 653-certified inspector for inspection planning and findings disposition.
Typical inspection types:
- Routine in-service external inspections (typically annual)
- External formal inspections (typically every 5 years)
- Internal inspections (typically every 10 years, modified by RBI and corrosion rate calculations)
- Floor scanning (MFL), shell UT thickness, and roof inspection during out-of-service intervals
Common findings that trigger engineering work:
- Floor plate thinning → settlement evaluation, repair plan, possibly partial reconstruction
- Shell distortion or settlement out-of-tolerance → engineering assessment under API 653 Annex B
- Coating breakdown → coating system reassessment under AMPP/NACE protocols, with PSC's coating inspection scope
External shell and roof inspection — particularly DFT, UT corrosion mapping, and CUI screening on insulated tanks — is increasingly delivered via drone-based contact NDT. Same auditable readings, dramatically lower access cost.
The integration mistake that costs Canadian operators the most
The expensive mistake is treating API inspection and provincial pressure equipment compliance as two separate programs.
In British Columbia, every pressure vessel and most process piping systems above the threshold pressure are regulated by Technical Safety BC. A vessel can be in API 510 compliance and still be out of TSBC compliance if the inspection records, repair documentation, or alteration submissions don't meet the provincial requirements. The same applies in Alberta with ABSA, in Saskatchewan with TSASK, and in Ontario with TSSA.
The right model is one inspection plan that satisfies both regimes. The codes are compatible. The execution rarely is, unless the inspection contractor is set up to handle both sides.
When findings trigger engineering — and what comes next
API codes don't tell you whether a flawed asset is fit to keep running. They tell you when to evaluate it.
The bridge from inspection finding to operating decision is fitness-for-service evaluation under API 579-1/ASME FFS-1. PSC's fitness-for-service and metallurgical engineering capability sits in the same office as our API inspection scope. When a UT reading shows wall loss below the as-built spec, the engineering call — remaining life, MAWP rerate, repair scope, or run-until-replacement — happens with one team that already has the data.
That integration is the difference between a clean integrity program and one that runs on emails between three different vendors.
Frequently asked questions
Do I need an API inspector if my asset is already covered by TSBC or ABSA? Yes, when the asset is in API-governed service. Provincial pressure equipment regulators set the legal compliance floor. API 510, 570, and 653 set the technical inspection methodology that most Canadian refining and process operators contractually require. They are complementary, not alternatives.
How often do I need to inspect under each code? API 510 generally caps internal vessel inspection at 10 years (or half the remaining life, whichever is less). API 570 frequencies depend on service class and corrosion rate. API 653 sets typical 5-year external and 10-year internal cycles, modified by RBI. Your inspection plan sets the actual intervals based on damage mechanism and service.
Can drone-based NDT support API inspection? Yes — for external scope. UT thickness, DFT, and PEC readings collected by a contact-based drone are compliant with the same standards (EN 12668-1, ASTM E1816-18, EN ISO 2178) referenced by API procedures. See drone-based aerial NDT for the full payload spec.
What happens when an inspection finds wall loss below the MAWP requirement? The asset moves into a fitness-for-service evaluation under API 579-1/ASME FFS-1. The result is one of: continue in service, derate, repair, or replace. PSC's metallurgical and mechanical engineering team performs FFS evaluations alongside the inspection scope.
Is the 2024 API 570 update worth re-baselining my piping program against? For most operators, yes. The 5th Edition strengthens guidance on damage mechanisms, CUI, and risk-based inspection — areas where an outdated program creates real exposure. A program written against the 3rd or 4th Edition deserves a methodology review.
Planning an API 510, 570, or 653 inspection in BC or Western Canada? PSC's certified API inspectors and engineering team are based in Coquitlam, BC and mobilize across Canada. Scope an API inspection and we will route the right inspector and engineer to your asset.
PSC delivers API 510, 570, and 653 inspection alongside fitness-for-service evaluation, metallurgical assessment, and welding engineering — one team from field reading to engineering decision.
.png)
%20(1).png)
