Ask any API 510 candidate to write the remaining-life formula on a whiteboard and they'll get it right within seconds: RL = (tactual − tmin) / CR. Ask the same person to defend which corrosion rate to use, which CML data to trust, and why the calculated interval isn't automatically the scheduled interval, and the confidence usually drops. That gap — between knowing the formula and knowing how to apply it to a real vessel with messy inspection history — is where API 510, the Pressure Vessel Inspection Code, actually lives. The code covers in-service inspection, rating, repair, and alteration of pressure vessels and the pressure-relieving devices protecting them, and its interval calculation is the backbone of every mechanical integrity program built around fixed equipment.
\nThis post walks through the interval calculation the way it actually gets applied in the field: the governing formula, the half-life rule and its ceiling, how corrosion rate selection changes the answer, how external and internal intervals diverge, and where risk-based inspection reshapes the whole conversation.
\n\nAPI 510 Section 7 ties the maximum inspection interval to the calculated remaining life of the vessel's controlling component — usually the shell course, head, or nozzle with the least corrosion allowance remaining, not necessarily the thickest or thinnest point in absolute terms. The formula:
\nRL = (tactual − tmin) / CR
\ntactual comes from the most recent UT thickness reading at an established CML. tmin is the minimum required thickness calculated per the original construction code (most commonly ASME Section VIII, Division 1) using the vessel's design pressure, temperature, material allowable stress, and joint efficiency — not a generic wall thickness assumption. CR is the corrosion rate, expressed in mils per year (mpy) or inches per year, derived from comparing thickness readings across time.
\nTake a real example: a carbon steel separator vessel, ASME Section VIII Division 1 construction, design pressure 285 psig at 400°F, calculated tmin of 0.312 in on the shell. Original nominal thickness was 0.500 in. The most recent UT survey reads 0.365 in at the governing CML, and the previous survey five years earlier read 0.398 in. Corrosion rate = (0.398 − 0.365) / 5 = 0.0066 in/yr = 6.6 mpy. Remaining life = (0.365 − 0.312) / 0.0066 = 8.0 years.
\n\nAPI 510 sets the maximum internal or on-stream inspection interval at the lesser of half the remaining life or 10 years, mirroring the logic used in API 570 for piping. Applied to the separator example above, RL/2 = 4.0 years, which becomes the governing interval since it's well under the 10-year cap. Note that the 10-year ceiling applies specifically to internal and on-stream inspection; external visual inspection intervals follow a separate rule (the lesser of 5 years or the required internal/on-stream interval, discussed below), and the two schedules frequently run on different clocks for the same vessel.
\nA subtlety that trips up less experienced inspectors: RL/2 is a ceiling, not a target. Nothing in API 510 requires you to push the interval out to the full calculated value. A vessel with intermittent, upset-prone service — batch reactors, vessels downstream of a unit with a history of process excursions — often warrants a shorter interval than the math strictly requires, and API 510 explicitly allows the inspector of record and the owner-user's inspection program to apply engineering judgment to shorten (never lengthen beyond the calculated maximum) the interval based on service severity, inspection history, and confidence in the data.
\n\nExternal visual inspection under API 510 runs on the lesser of 5 years or the required internal/on-stream interval, and its purpose is different from the internal/on-stream program: it's looking for external corrosion, coating and insulation condition, CUI indicators at penetrations and supports, foundation settlement, and nozzle/attachment weld condition — the things that indicate a vessel problem long before an internal inspection would otherwise be scheduled. For the separator example above, the internal/on-stream interval is 4.0 years, so the external interval can be no longer than 4 years; many owners schedule externals more often than the code maximum, especially for insulated vessels with CUI risk. Running two intervals in parallel, on different clocks, for the same vessel is normal and expected — and it's exactly the kind of detail that gets lost when a facility tracks inspection due dates in a spreadsheet maintained by whoever had time that quarter rather than a system built for it.
\n\nAPI 510 recognizes two corrosion rate calculations and requires the inspector to select the one that best represents current and anticipated future conditions:
\nThe governing principle is conservatism: when STCR and LTCR diverge meaningfully, and STCR indicates faster corrosion, API 510 practice is to use STCR unless the inspector has specific technical justification (a known, corrected upset condition, for instance) to discount it. In the separator example, if the two most recent readings actually showed 0.398 in to 0.365 in over 5 years (6.6 mpy) but the original-to-current LTCR calculated out to only 4.1 mpy, a competent inspector uses 6.6 mpy — the more conservative, recent-trend number — because using the lower LTCR would understate risk and overstate the safe interval.
\n\nNot every vessel has a clean two-point thickness history. Vessels that changed hands, vessels where CML locations weren't consistently re-measured at the same spot, or vessels coming off a long shutdown with no interim monitoring all present a data problem before they present a calculation problem. API 510 doesn't have a shortcut for missing data — the conservative default is to treat unverifiable remaining life as effectively unknown, which forces either a fresh full UT thickness survey to re-establish a defensible baseline, or a corrosion rate assumption pulled from API RP 571 damage mechanism guidance for the specific service (sour water, amine, caustic, etc.) until real data exists. This is a common finding when Atlantis NDT's ASNT Level III consulting team audits an inherited mechanical integrity program: the calculations on file are mathematically correct, but they're built on CML data that was never verified as measuring the same location twice.
\n\nMany facilities layer API 580/581 Risk-Based Inspection (RBI) methodology on top of the base API 510 calculation. API 510 does allow an RBI assessment per API RP 580 to set intervals in place of the half-remaining-life-or-10-year limits, including intervals longer than 10 years, provided the RBI assessment is reviewed and approved by the engineer and inspector at intervals not exceeding 10 years. Just as importantly, RBI lets facilities justify shorter intervals for high-consequence vessels (large inventory, toxic or flammable service, high population exposure) even when the corrosion-rate math alone would allow a longer wait, and it lets low-risk vessels (utility air receivers, low-pressure low-consequence vessels) get inspection resources prioritized elsewhere within the code-allowed maximum. RBI is a risk-prioritization layer, and API 510 remains the floor beneath it.
\nVessels in cyclic or fatigue-prone service — think amine contactors, hydrocracker reactors with hydrogen embrittlement exposure, or vessels subject to frequent startup/shutdown thermal cycling — often carry RBI scores that push their interval well below what RL/2 alone would calculate, because the governing damage mechanism (fatigue cracking, hydrogen-induced cracking, stress corrosion cracking) doesn't behave like uniform wall-thinning corrosion and isn't fully captured by a UT thickness trend at all. For these vessels, the interval calculation is only the starting point; the real inspection scope typically adds wet fluorescent magnetic particle testing (WFMT) at nozzle welds, phased array UT for crack detection, or hardness surveys per NACE MR0175/ISO 15156 for sour service vessels.
\n\nThe remaining-life calculation assumes a fixed tmin, but tmin isn't permanently fixed — it changes if the vessel is rerated (typically de-rated to a lower MAWP to extend service life on a thinning vessel) per API 510 Section 9, or if it undergoes a repair or alteration per API 510 Section 8 that changes the pressure boundary. A vessel approaching the end of its economically viable remaining life at its nameplate MAWP is sometimes rerated downward — recalculating tmin at a lower design pressure using the actual current thickness — which mathematically extends remaining life and resets the interval clock, without any metal being added. This is a legitimate, code-sanctioned path, but it requires a full engineering rerate calculation, not just a inspector's field judgment, and it needs to be documented and, where required, reviewed by the jurisdictional authority having jurisdiction (many US states require notification or approval for rerates on registered vessels).
\n\nTo see how these rules interact on a real vessel rather than a textbook shell course, consider a lean amine contactor at a gas processing facility — a common and instructive case because amine service combines uniform corrosion with localized attack at specific geometry, and because it's exactly the kind of vessel where a mechanical interval calculation alone is insufficient. The vessel is ASME Section VIII Division 1, carbon steel, design pressure 1,200 psig at 150°F, calculated tmin on the shell of 0.687 in against a nominal 1.000 in wall. Thickness surveys at the governing CML — located at the rich amine outlet nozzle, a known high-turbulence, high-corrosion location in amine service — show 0.795 in five years ago and 0.762 in at the most recent turnaround.
\nSTCR = (0.795 − 0.762)/5 = 6.6 mpy. The vessel's original construction-to-current LTCR calculates to 4.3 mpy, noticeably lower. Per API RP 571's guidance on amine corrosion, localized attack at high-velocity points like nozzles and elbows is a recognized damage mechanism that tends to accelerate rather than plateau, so the inspector uses the more conservative STCR. RL = (0.762 − 0.687)/0.0066 = 11.4 years. RL/2 = 5.7 years, comfortably under the 10-year cap, so the mechanical interval calculation alone would allow nearly six years before the next internal or on-stream inspection.
\nBut amine service also carries recognized susceptibility to amine stress corrosion cracking (SCC) at and adjacent to non-stress-relieved welds, a mechanism that thickness readings do not detect at all — cracking doesn't show up as wall loss on a UT thickness grid. An RBI assessment for this vessel, weighting both the consequence of a rich amine release (flammable, toxic H2S content, personnel exposure in a processing area) and the likelihood factor tied to weld stress-relief history, frequently drives the practical inspection scope well past what RL/2 alone would suggest: wet fluorescent magnetic particle testing at heat-affected zones, and in some programs, a shortened interval independent of the corrosion-rate-driven maximum. This is the scenario every API 510 inspector needs to internalize — the interval calculation answers \"how much wall thickness margin do we have,\" but it never answers \"is wall thickness the only thing that can fail this vessel.\" Treating RL/2 as sufficient justification to skip a targeted cracking inspection on a vessel with documented SCC susceptibility is a common and expensive mistake, and it's precisely the gap a competent RBI program, correctly integrated with the base API 510 schedule, is designed to close.
\n\nEvery interval decision needs to be reconstructable years later, by someone other than the inspector who made the original call. That means the file should show: the governing CML location and why it's the controlling point, the tmin calculation with its code edition/addenda basis, both LTCR and STCR figures with a stated reason for which one governed, the resulting RL and RL/2 (and the resulting external interval), any RBI adjustment applied and its basis, and the inspector of record's API 510 certification number and signature. Facilities running dozens or hundreds of vessels across multiple units lose track of this not because anyone is careless, but because the data lives in disconnected places — UT reports in one folder, corrosion rate spreadsheets in another, RBI scores in a third system that doesn't talk to either. Atlantis NDT's NDT inspection management ERP was built to close exactly that gap: CML history, calculated remaining life, interval due dates, and RBI flags in one system, so a turnaround planner can pull \"everything due in the next outage window\" instead of reconstructing it vessel by vessel from PDFs.
\n\nThe interval calculation itself is arithmetic. The judgment behind corrosion rate selection, CML placement, RBI weighting, and when to override the calculated maximum with a shorter, more conservative interval is what separates a program that catches problems early from one that discovers them during a shutdown inspection nobody expected to find anything. That judgment is built through structured API-code training, supervised inspection experience, and — for facilities without a Level III on staff — access to one who can review the program periodically. Atlantis NDT's NDT training and certification programs and ASNT Level III consulting services support both paths: training internal Level II inspectors to apply the code correctly and consistently, or serving as the outside Level III of record reviewing interval calculations, procedure adequacy, and CML program design for facilities that need that oversight without carrying it as a full-time headcount.
\nFor an asset-heavy facility, tying the API 510 interval calculation into a live digital twin of the unit — where every vessel's next-due date, corrosion trend, and RBI score is visible on the 3D model rather than buried in a spreadsheet — turns interval management from a periodic audit exercise into something the whole reliability team can see and act on continuously. Whether the entry point is a training gap, a program audit, or a technology upgrade, the underlying goal is the same: make sure the interval a vessel is actually inspected on matches the interval the code — and the data — says it should be.
\n\nAtlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.
\n