Table of content
- Why three certifications and a methodology, in one guide
- How this fits into a mechanical integrity program
- API 510 — Pressure Vessel Inspector
- API 570 — Piping Inspector
- API 653 — Aboveground Storage Tank Inspector
- Risk-Based Inspection: API RP 580 vs. API RP 581
- NDT method selection, at a glance
- Recent standard updates at a glance
- Key takeaways
- FAQs
- References
- Further reading
Why three certifications and a methodology, in one guide
A refinery, terminal, or chemical plant’s fixed equipment — pressure vessels, process piping, and storage tanks — doesn’t fail randomly. It fails through specific, identifiable damage mechanisms (corrosion, cracking, fatigue) that develop at predictable rates once you know what’s in the equipment and what’s flowing through it. Managing that risk is the job of a mechanical integrity (MI) program, and three API individual-certification schemes anchor how most MI programs staff their in-service inspection work: API 510 (pressure vessels), API 570 (process piping), and API 653 (aboveground storage tanks). Overlaid on all three is Risk-Based Inspection (RBI) — the methodology (API RP 580 and API RP 581) that decides which equipment gets inspected sooner, which can wait, and with which NDT method.
This guide is written for refinery and plant integrity teams who need to understand how these pieces fit together: what each certification actually covers, how RBI changes what gets inspected and when, and at a high level, which NDT methods are typically used for each equipment class. A companion article, the Damage Mechanism to NDT Method Matrix (API 571), goes deeper on method selection by failure mode — this guide stays at the program level.
How this fits into a mechanical integrity program
API 510, 570, and 653 are equipment-class-specific, not interchangeable: 510 covers pressure vessels, 570 covers in-service metallic piping systems, and 653 covers aboveground storage tanks. A refinery’s fixed-equipment mechanical integrity (MI) program needs inspection coverage across all three equipment classes, and because the eligibility tracks and exam structure are nearly identical across all three certifications — the same 7.5-hour, 170-question exam format, the same tiered education/experience schedule — it’s routine for a senior inspector to hold all three concurrently rather than specializing in just one.
Risk-Based Inspection doesn’t replace the inspection requirements the three codes already set — it decides how those requirements get applied in practice. An RBI study ranks equipment by calculated risk (probability of failure × consequence of failure) and produces a recommended next-inspection date and technique for each item; a 510/570/653-certified inspector then executes and documents that plan. Equipment flagged as higher risk gets inspected sooner or more thoroughly than a code’s uniform default interval would require; equipment with calculated low risk may be deferred within what the code allows. This also connects to fitness-for-service work under API 579-1/ASME FFS-1 and to the damage mechanisms catalogued in API 571 — covered in depth in the companion Damage Mechanism to NDT Method Matrix article, which this guide references rather than duplicates.
API 510 — Pressure Vessel Inspector
API 510, formally the Pressure Vessel Inspection Code: In-service Inspection, Rating, Repair and Alteration, certifies inspectors with a broad knowledge base covering the maintenance, inspection, repair, and alteration of pressure vessels, typically in refining and petrochemical service.
Exam. A 7.5-hour exam day: a short tutorial, a 2.75-hour closed-book session, a 45-minute lunch break, then a 3.75-hour open-book session. There are 170 total questions (110 closed-book, 60 open-book), but only 140 are scored — 30 are unscored pretest items. The exam is in-person only, at Prometric testing centers; the open-book portion provides on-screen excerpts of the relevant code sections rather than allowing personal notes.
Eligibility (per Appendix B of the API 510 standard) is tiered by education: a bachelor’s or technical engineering degree plus 1 year of experience; a 2-year associate degree plus 2 years; a high school diploma plus 3 years; or no formal education plus 5 or more years. Experience must fall within the last 10 years and be gained while employed by, or under contract to, an authorized inspection agency. For the three lower tiers, at least 1 year of that experience must specifically involve supervising or performing inspection under API 510. Three or more years of technical military service can substitute for the bachelor’s-degree track.
Recertification runs on a 3-year cycle (with a 90-day window before expiry and a 90-day grace period after, with late fees). It requires at least 20% of the inspector’s time over the cycle spent on pressure-vessel inspection work, 24 hours of continuing professional development (CPD), and — every other cycle (every 6 years) — a 25-question open-book web quiz in place of sitting the full exam again.
Current edition: API 510 is currently in its 11th edition, which API describes as adding a new, detailed part on evaluating inspection findings to confirm vessels remain fit for service, incorporating lessons learned from industry incidents.
API 570 — Piping Inspector
API 570, formally the Piping Inspection Code: In-service Inspection, Rating, Repair, and Alteration of Piping Systems, covers in-service metallic piping systems — specifically process piping, distinct from the vessels covered by 510 or the tanks covered by 653.
Exam. The same structure as API 510: a 7.5-hour exam day, 170 total questions (140 scored, 30 unscored pretest items), 110 closed-book and 60 open-book, administered in person only.
Eligibility follows the same tiered education/experience schedule as API 510, including the same code-specific carve-out: for the three lower tiers, at least 1 year of that experience must specifically involve supervising or performing inspection under API 570.
Recertification runs on the same 3-year cycle: at least 20% of time on in-service piping inspection or supervision, 24 CPD hours, and a 25-question, 4-hour open-book web quiz every 6 years.
Current edition: API 570 is in its 5th edition, published April 4, 2024. The key changes in that edition: it formally defines an Inspection Supervisor role and its responsibilities, strengthens requirements for inspecting, testing, maintaining, and repairing pressure-relief devices, and adds requirements for reviewing and deferring repair recommendations.
API 653 — Aboveground Storage Tank Inspector
API 653 (formally Tank Inspection, Repair, Alteration, and Reconstruction) covers aboveground storage tanks (ASTs). First published in 1991, it was created partly to give a uniform national program that could support state and local AST regulatory requirements. The certification is ANSI-accredited and meets ISO/IEC 17024.
Exam. The same 7.5-hour, 170-question structure as API 510 and 570.
Eligibility (Annex D of the API 653 standard) follows the same tiered education/experience schedule as the other two certifications; for all tiers except the bachelor’s-degree/military track, experience must be in the design, construction, repair, operation, or inspection of ASTs, including at least 1 year supervising or performing API 653 inspection activities.
Recertification runs on the same 3-year cycle: at least 20% of time on AST inspection or supervision, 24 CPD hours across at least 2 categories, and a 25-question, 4-hour open-book web quiz every 6 years — failing that quiz twice forces a full re-exam.
Current edition and recent revisions: API 653 is in its 5th edition. Two revisions since are worth noting: Addendum 1 (2022) formally recognized automated UT mapping and acoustic emission as recognized inspection technologies and strengthened documentation requirements, and Errata 2 (February 2025) clarified definitions and application limits, reinforced licensed-inspector/engineer oversight language, and corrected an inspection-interval equation error — Addendum 1 added newly recognized technologies rather than merely correcting existing text, while Errata 2 was a pure correction pass with no fundamental technical changes.
Risk-Based Inspection: API RP 580 vs. API RP 581
Risk-Based Inspection is a methodology for prioritizing and scheduling inspection effort based on a structured estimate of probability of failure (PoF) multiplied by consequence of failure (CoF) for each piece of equipment, rather than applying the same inspection interval uniformly across everything. The output is typically a risk ranking — often shown as a risk matrix — that directs inspection resources (frequency, method, and extent) toward the equipment carrying the highest calculated risk.
Two API documents are easy to confuse, and the difference matters for anyone setting up a program:
- API RP 580, “Risk-Based Inspection,” is the framework and management-system standard. It defines what a sound RBI program must contain — roles and responsibilities, data and information requirements, how a qualitative-to-quantitative program should be structured and governed — but it is not itself a calculation procedure. Current edition: 4th edition.
- API RP 581, “Risk-Based Inspection Methodology,” is the quantitative (or semi-quantitative) calculation procedure — the actual PoF and CoF models and damage-factor calculations, tying into the damage mechanisms catalogued in API 571, that an RP 580-compliant program uses to produce the numbers behind its risk ranking. Current edition: 4th edition, 2025.
In short: 580 is what a program must contain and how it should be governed; 581 is the specific quantitative math used to calculate PoF, CoF, and risk under that framework. A plant can run an RP 580-compliant program using simpler qualitative risk matrices without the full RP 581 methodology, which is more data-intensive and typically run in dedicated RBI software.
Worth flagging as emerging, not settled: an August 2025 Inspectioneering journal article by an industry consultant proposes “sunsetting” the semi-quantitative API RP 581 methodology in favor of a fully quantitative next-generation RBI approach. This is one leading voice’s personal recommendation in a trade publication, not an announced API committee decision — readers should not take it as a signal that RP 581 is being withdrawn or replaced.
NDT method selection, at a glance
The choice of NDT method is driven by equipment class and damage mechanism; the companion Damage Mechanism to NDT Method Matrix article covers this in full detail, mapping specific damage mechanisms from API 571 to detection methods. At the program level, the typical pattern looks like this:
- Vessels (API 510): UT thickness gauging and corrosion mapping for general or localized metal loss; UT shear-wave and radiographic testing (RT) for weld integrity and crack detection; magnetic particle (MT) and liquid penetrant (PT) testing for surface-breaking cracking on welds and nozzles; acoustic emission (AE) for broad-area screening, often used ahead of a decision on whether to open a vessel for internal entry.
- Piping (API 570): UT thickness gauging at condition monitoring locations (CMLs); guided-wave UT (GWUT) for screening long runs of insulated or otherwise inaccessible piping; RT for weld and girth-weld integrity; MT/PT for surface cracking at welds and supports.
- Tanks (API 653): UT thickness gauging of shell courses; automated UT floor-scanning or magnetic flux leakage (MFL) for tank-bottom corrosion mapping — automated UT mapping specifically was recognized as an accepted technology in API 653’s 2022 Addendum 1, alongside acoustic emission; AE for overall tank screening; MT/PT for shell and roof weld inspection; vacuum-box or bubble testing for bottom seam leak testing.
For the full picture — which method actually catches which damage mechanism, and why — see the Damage Mechanism to NDT Method Matrix article.
Recent standard updates at a glance
Standard | Current edition | Key recent change |
|---|---|---|
API 510 | 11th edition | Adds a detailed part on evaluating inspection findings to confirm fitness for service; incorporates lessons learned |
API 570 | 5th edition (April 4, 2024) | Formally defines an Inspection Supervisor role; strengthens pressure-relief-device requirements; adds repair-deferral review requirements |
API 653 | 5th edition | Addendum 1 (2022): recognizes automated UT mapping and acoustic emission; Errata 2 (Feb 2025): clarifies definitions, reinforces oversight language, corrects an interval-equation error |
API RP 580 | 4th edition | Framework/management-system standard |
API RP 581 | 4th edition (2025) | Quantitative RBI calculation procedure |
Separately, one industry voice has proposed retiring API RP 581’s semi-quantitative approach in favor of a fully quantitative method — see the RBI section above for why this should be read as an opinion, not a standards change.
Key takeaways
- API 510, 570, and 653 are equipment-class-specific certifications — vessels, piping, and tanks, respectively — not interchangeable or substitutable for each other, though it’s common for one inspector to hold all three.
- Risk-Based Inspection doesn’t replace the inspection requirements set by 510/570/653; it determines how those requirements get applied — which equipment gets inspected sooner, which can be deferred within code limits, and with which method.
- API RP 580 is the RBI management framework; API RP 581 is the quantitative calculation methodology that framework can use. They are not the same document and are not interchangeable terms.
- Specific numeric in-service inspection intervals and certification exam fees vary and are condition- and risk-dependent — check the current standard and your facility’s RBI program rather than relying on a fixed figure.
- A companion article, the Damage Mechanism to NDT Method Matrix (API 571), covers NDT method selection by specific damage mechanism in full detail; this guide stays at the certification and program level.
FAQs
Do I need all three certifications — API 510, 570, and 653? Only if your work spans all three equipment classes. Many inspectors specialize in one; it’s also common, given the nearly identical exam format and eligibility structure across all three, for a senior inspector to hold all three concurrently.
What’s the difference between API RP 580 and API RP 581? 580 is the RBI framework and management-system standard — what a program must contain and how it should be governed. 581 is the quantitative calculation methodology a 580-compliant program can use to actually compute risk numbers. They’re often confused but are not the same document.
How often do I need to recertify? All three certifications (510, 570, 653) run on the same 3-year cycle, requiring continuing professional development hours and a minimum proportion of time spent on relevant inspection work, with a shorter open-book quiz available every 6 years in place of the full exam. This article does not state specific in-service inspection intervals for the equipment itself, since those are risk- and condition-dependent under RBI rather than fixed numbers.
Does RBI replace the inspection requirements in API 510/570/653? No. RBI determines how and when those requirements get applied — it doesn’t override the codes. See “How this fits into a mechanical integrity program” above.
Where can I find detail on which NDT method catches which specific damage mechanism? See the companion Damage Mechanism to NDT Method Matrix (API 571) article, which maps damage mechanisms to detection methods in detail; this guide covers method selection only at the program level.
References
- API, API 510 Pressure Vessel Inspector certification page (api.org/products-and-services/individual-certification-programs/certifications/api510).
- API, API 570 Piping Inspector certification page (api.org/products-and-services/individual-certification-programs/certifications/api570).
- API, API 653 Aboveground Storage Tank Inspector certification page (api.org/products-and-services/individual-certification-programs/certifications/api653).
- API, trade announcement for the 11th edition of API 510 (api.org/products-and-services/standards/important-standards-announcements/tradeannouncement-api510).
- Inspenet, “API Piping Inspection Standards Updates” — API 570 5th edition, April 2024 (inspenet.com/en/news/api-piping-inspection-standards-updates/).
- Inspenet, retrospective on 35 years of API 653 — Addendum 1 (2022) and Errata 2 (February 2025) (inspenet.com/en/?p=245441).
- Inspectioneering, “Risk-Based Inspection Planning” — general RBI framing (inspectioneering.com/blog/2014-11-17/4253/risk-based-inspection-planning).
- Distributor listings cross-checked for API RP 581’s current (4th) edition, 2025: oviss.jp and normservis.sk.
- Inspectioneering journal, “Sunsetting API RP 581 Risk-Based Inspection Semi-Quantitative Methodology” (August 2025) — an individual consultant’s proposal, not an API committee decision (inspectioneering.com/journal/2025-08-28/11677/sunsetting-api-rp-581-risk-based-inspection-semi-quantitative-methodology).
Further reading
- Damage Mechanism to NDT Method Matrix (API 571) — the companion reference tool for method selection by damage mechanism.
- Weld Inspection: Visual, Surface and Volumetric NDT — background on the weld-inspection methods referenced above.
- NDT Certification Guide: ISO 9712, SNT-TC-1A and NAS 410 — for readers comparing API’s inspector certifications to other personnel-certification schemes.
- CUI Detection Compared: PEC, Guided Wave, Profile RT, Thermography — method selection for corrosion under insulation, a key RBI driver.
- API 510, 570 and 653 Inspection Explained — a deeper plain-language walkthrough of the three certification scopes.




There are no comments yet!