API 510 is the code that decides when a pressure vessel must be opened, what gets measured, and whether it can stay in service for another cycle. For operators across the Eastern Province, Jubail, and Yanbu running ageing refinery and petrochemical assets, a clean API 510 programme is the difference between a planned turnaround and an unplanned shutdown.
This guide is the operator's view: the intervals the code actually requires, how to build a thickness-monitoring strategy that produces meaningful remaining-life numbers, and the specific places where well-run programmes quietly drift out of compliance.
Codes referenced
The intervals API 510 actually requires
API 510 sets two separate inspection cycles that are easy to confuse. The internal or on-stream inspection drives the remaining-life calculation; the external visual inspection runs more frequently and catches insulation, support, and external corrosion issues.
The headline interval is ten years, but it is capped at one-half the remaining corrosion life. A vessel corroding faster than expected pulls its own interval in automatically. The code is conservative by design.
Where does a pressure vessel sit relative to the other in-service codes? Here are the default maxima side by side:
Source: API 510 §6.5, API 570 §6.3, API 653 §6.4. Default maxima; RBI may extend, remaining-life rule may shorten
Building a thickness-monitoring strategy that means something
The remaining-life calculation is only as good as the thickness data behind it. The most common failure is placing condition monitoring locations (CMLs) on a tidy grid rather than where corrosion actually occurs.
- Put CMLs where the damage mechanism predicts metal loss: bottom heads, liquid lines, turbulence zones, and known erosion-corrosion spots.
- Keep the same locations across cycles so the corrosion rate is a real trend, not noise from moving the probe.
- Cross-check on-stream ultrasonic readings against internal visual findings at turnaround.
Remaining life is corrosion allowance divided by corrosion rate. Get the rate wrong, from sloppy or wandering thickness readings, and every interval downstream is wrong with it.
Method selection matters here too. Wall-thickness monitoring, internal visual, and volumetric examination each answer different questions; our overview of NDT methods and standards used across KSA maps techniques to the damage they detect.
Where API 510 programmes drift out of compliance
Programmes rarely fail an audit on day one. They drift, predictably:
- Interval extensions granted on optimism rather than corrosion-rate data.
- External visual inspections skipped because the vessel "looked fine on-stream".
- CMLs quietly relocated between cycles, breaking the corrosion-rate trend.
- Repairs and alterations not re-rated or documented to ASME VIII.
The fix is the same closed-loop discipline that underpins any asset integrity management programme: findings feed the data system, the data system drives the next interval, and extensions require evidence. When metal loss exceeds the code allowable, the decision moves into a fitness-for-service assessment under API 579-1.
How IES supports API 510 programmes
IES brings certified inspectors, disciplined CML management, and reporting that holds up under operator and third-party scrutiny. The piping equivalent of this work runs under API 570, and the procurement side is covered in our buyer's guide to third-party inspection. To discuss your vessel fleet and turnaround schedule, talk to our team.
Questions buyers ask us
API 510 is the inspection code for in-service pressure vessels. It governs the inspection, rating, repair, and alteration of pressure vessels after they enter service, defining who is competent to inspect them, how often, and how to calculate remaining life from thickness data.
The maximum internal or on-stream inspection interval is ten years, or one-half the remaining corrosion life, whichever is shorter. External visual inspections run on a separate cycle with a five-year maximum. A risk-based inspection assessment can extend intervals within code limits when the data supports it.
API 510 covers pressure vessels, while API 570 covers in-service piping systems. They share the same philosophy of interval setting and remaining-life calculation, but apply to different equipment with different inspection methods and class definitions.
Yes. API 510 permits interval setting on a risk-based inspection (RBI) basis under API 580/581, which can justify extending intervals beyond the default maxima for low-risk vessels, provided the assessment is documented and periodically revalidated.
