API 510 Pressure Vessel Inspection Intervals
API 510 sets inspection intervals from the vessel's own corrosion behavior rather than a fixed calendar, and understanding that logic is what keeps a vessel legally and physically fit for service. This page explains how internal, external, and thickness inspections are timed by corrosion rate and remaining life, for the engineer scheduling a vessel program. It focuses on the interval logic, not the full code.
API 510 Inspection Intervals in one line: API 510 sets vessel inspection intervals from corrosion rate and remaining life, not a fixed calendar. Internal or on-stream inspections are scheduled from the corrosion rate and remaining corrosion allowance, external inspections on their own interval, and both are capped by not-to-exceed ceilings. A commonly applied rule limits the internal interval to a fraction of the vessel's remaining life.
The Inspection Types and Their Clocks
API 510 uses complementary inspections on different clocks. The external inspection - a visual of the shell, insulation, supports, and appurtenances - is done with the vessel in service and catches external damage and coating or insulation problems. The internal or on-stream inspection assesses the vessel's condition-controlling corrosion, and for many vessels requires entry when it is out of service.
Thickness measurement underlies the timing of both. Readings at fixed locations establish the corrosion rate, which is what turns 'how thick is it now' into 'how long until it reaches minimum.' Understanding the vessel's service - what a pressure vessel is exposed to - guides where those readings are taken.
Corrosion Rate and Remaining Life
The core calculation is remaining life: the corrosion allowance still available divided by the corrosion rate. A vessel corroding slowly with plenty of margin has a long remaining life and a long permissible interval; a fast-corroding vessel with little margin has a short one. The interval is set so the next inspection happens well before the vessel reaches minimum thickness.
A widely applied principle limits the internal inspection interval to a fraction of the remaining life, subject to a not-to-exceed ceiling. This is the same corrosion-rate-driven philosophy behind API 653 inspection intervals for tanks - condition sets the clock, with a hard cap so nothing goes indefinitely uninspected.
Interval Logic at a Glance
The structure below shows how the inspection types and their drivers relate. Actual maximum intervals come from the code and your remaining-life calculation - never schedule a real vessel from a generic table.
| Inspection | With vessel in service? | Interval driver |
|---|---|---|
| External visual | Yes | Own interval, with a ceiling |
| Internal / on-stream | Often out of service | Corrosion rate and remaining life, with a ceiling |
| Thickness (UT) | Yes where accessible | Feeds the corrosion-rate trend |
Common Misconceptions
The most common misconception is a fixed 'inspect every ten years' rule. There is a not-to-exceed ceiling, but the governing interval is remaining-life driven and often shorter, especially for corroding vessels. Treating the ceiling as the schedule ignores the vessel's actual condition.
Another is that a low current corrosion rate justifies stretching to the ceiling. Corrosion rates change with process conditions; an excursion caught by SCADA temperature or chemistry data can accelerate corrosion between inspections. Intervals should be revisited when the process changes, not set once and forgotten.
Frequently Asked Questions
How often does API 510 require internal inspection?
There is a not-to-exceed ceiling, but the governing interval is set from the vessel's corrosion rate and remaining life, and a common principle limits it to a fraction of that remaining life. Fast-corroding vessels are inspected sooner than the ceiling would allow.
What is remaining life in API 510?
The remaining corrosion allowance divided by the corrosion rate - how long until the vessel reaches its minimum required thickness. The inspection interval is set so re-inspection occurs well before that point, capped by a not-to-exceed ceiling.
Can I stretch the interval if corrosion is currently slow?
Only within the code's rules and with caution. Corrosion rates change with process conditions, so a currently low rate does not guarantee a low rate over the whole interval. Process excursions should trigger a review rather than being ignored.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- API 653, Tank Inspection, Repair, Alteration, and Reconstruction - American Petroleum Institute
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.