Remaining Life Calculations: How Corrosion Rate Drives Inspection Intervals

Remaining life calculations turn corrosion rate and UT thickness data into defensible inspection intervals under API 570, 653, and 510, with a worked example.

Atlantis NDT ·

The Number That Actually Matters: Remaining Life, Not Just Current Thickness

A UT thickness reading by itself tells you almost nothing. A crude unit piping spool reading 0.312 in. against a nominal 0.375 in. wall could be in excellent shape or six months from a leak — the number alone can't tell you which. What tells you which is the remaining life calculation: how fast the wall is thinning, how much wall you're required to keep, and how long you have before you cross that line. Get this calculation right and your inspection interval is defensible in an audit, in a management-of-change review, and in front of a jurisdictional inspector. Get it wrong — usually by using the wrong corrosion rate, the wrong retirement thickness, or comparing readings from different corrosion monitoring locations as if they were the same point — and you either inspect assets that don't need it or, worse, miss the ones that do.

This is the calculation that sits underneath every risk-based inspection (RBI) program built to API 580/581, every API 570 piping circuit reassessment, every API 653 tank internal/external interval, and every API 510 pressure vessel fitness-for-service review. It's also one of the most commonly miscalculated numbers in the industry, not because the math is hard — it's arithmetic — but because the inputs are so easy to get sloppy about.

The Basic Equation, and Where It Goes Wrong

The remaining life (RL) equation is simple on paper:

RL = (t_actual − t_min) / CR

where t_actual is the current measured wall thickness, t_min is the minimum required (retirement) thickness set by the governing design code or a fitness-for-service assessment, and CR is the corrosion rate in inches (or mils) per year. The retirement thickness itself comes from a pressure design calculation — for piping, typically the ASME B31.3 or B31.1 minimum wall equation based on design pressure, temperature, allowable stress, and pipe outside diameter; for pressure vessels, the ASME Section VIII, Division 1 formula for the governing component (shell, head, nozzle); for tanks, the API 653 minimum shell thickness table by course and diameter, or the calculated bottom plate minimum.

Where this goes wrong in practice: engineers pull t_min from a generic "corrosion allowance" figure on an old datasheet instead of recalculating it against current code minimums, or they use nominal thickness instead of actual as-built thickness as the numerator's starting point. Both errors compound. A retirement thickness that's 20 mils too conservative can force an unnecessary shutdown; one that's 20 mils too thin can push an asset past its safe operating life without anyone noticing, because the RL calculation will report a rosier number than reality supports.

Short-Term vs. Long-Term Corrosion Rate — Choosing the Wrong One Is the Single Biggest Error

CR is where most bad remaining-life numbers actually come from. You have two candidate rates: the short-term rate, calculated from the two most recent inspections, and the long-term rate, calculated from the original (or earliest reliable) thickness to the most recent reading, averaged over the full service life. API 570 and API 653 both direct you toward the more conservative — that is, the higher — of the two, unless there's a documented, understood reason the short-term rate reflects a real and permanent change in service conditions: a feedstock change, a new corrosion inhibitor program, a process unit revamp.

In practice this means: if a piping circuit ran at 2 mils per year for fifteen years and then the last two inspections show 8 mils per year, you don't get to average that into a comfortable 3 mils/year long-term rate. You use 8 mils/year until you understand why it changed — new sulfur content in the crude slate, a lost corrosion inhibitor injection point, a change in flow regime that's now causing erosion-corrosion at an elbow. Conversely, a single anomalously high short-term reading driven by measurement error or a localized, non-representative CML shouldn't be allowed to drive the whole circuit's interval down without checking it against a second UT technique or a grid of surrounding points.

A Worked Comparison

  • Long-term rate: original nominal 0.375 in., installed 18 years ago, current reading 0.291 in. → 0.084 in. lost over 18 years = 4.7 mils/year.
  • Short-term rate: reading 3 years ago was 0.318 in., current reading 0.291 in. → 0.027 in. lost over 3 years = 9.0 mils/year.
  • Governing rate: 9.0 mils/year (the higher of the two), until the cause of the acceleration is identified and resolved.

Where the Codes Set the Rules: API 570, API 653, API 510

Each governing code translates remaining life into an inspection interval slightly differently, and mixing them up is a common finding in third-party integrity audits.

API 570 — Piping

For in-service piping, API 570 sets the reinspection interval at the lesser of half the remaining life or a fixed code maximum — tighter for Class 1 (highly hazardous, high-consequence) circuits than for Class 2 or 3 piping. A circuit calculated at 9.0 mils/year with 0.088 in. of wall left above minimum has roughly 9.8 years of remaining life; the reinspection interval is capped well inside that window, not run out to the full RL figure. This half-life convention exists specifically to catch an acceleration in corrosion rate before the circuit gets anywhere near its retirement thickness.

API 653 — Aboveground Storage Tanks

Tank floor and shell remaining life is calculated separately by component, because the corrosion mechanisms differ: floor plates typically corrode from the soil side (external) or product side (internal, often concentrated at the water-oil interface), while shell courses corrode more uniformly from atmospheric or vapor-space exposure. Internal inspection intervals are tied to floor remaining life, capped at a code maximum regardless of how long the RL math says you have — because internal floor corrosion under coating disbondment or microbiologically influenced corrosion (MIC) can be highly localized and easy to underestimate from a sparse UT grid alone. This is why 100% floor scanning with magnetic flux leakage (MFL), followed by UT verification of flagged indications, has become standard practice rather than an optional extra on tanks past a certain age.

API 510 — Pressure Vessels

Vessel remaining life follows the same core equation, but t_min is calculated per component — shell, head, nozzle neck, reinforcing pad — using the applicable ASME Section VIII design formulas, and the governing component is whichever has the shortest remaining life. That's frequently a nozzle neck at a process connection rather than the shell, because nozzles see turbulence-driven erosion-corrosion and are, in a lot of programs, under-monitored relative to the shell courses that get most of the UT grid attention.

Building a Corrosion Monitoring Location Grid That Tells the Truth

A remaining life number is only as good as the CML it came from, and CML placement is where a lot of programs quietly fail. A grid of five thickness points on a straight run of 20-inch pipe tells you almost nothing about the elbow, tee, or reducer in that same circuit, because those fittings see different flow dynamics and corrode at different rates — often two to three times faster at an elbow extrados or immediately downstream of a control valve, where flashing or erosion-corrosion concentrates wall loss.

A defensible CML program places points at:

  • Each elbow (extrados, intrados, and neutral axis) on circuits with any history of erosion-corrosion or two-phase flow.
  • Immediately downstream of control valves, orifice plates, and pump discharges.
  • Dead legs and low-flow branch connections, where settling and under-deposit corrosion concentrate.
  • Tank shell courses at multiple clock positions per course, not just one "representative" point.
  • Any location flagged by a prior inspection, process upset, or repair — CMLs should accumulate across turnarounds, never reset.

Grid consistency matters as much as grid placement. If successive inspections don't hit the exact same CML — same location, same orientation, same measurement technique — the resulting "corrosion rate" is really just noise between two unrelated data points. This is one of the areas where scanning UT or phased array corrosion mapping earns its keep over single-point spot readings: a C-scan or grid map at a CML captures the true minimum thickness in the footprint rather than whatever single point the technician happened to hit, and it re-locates reliably from one turnaround to the next using photographic and dimensional references.

A Worked Scenario: Sulfidic Corrosion in a Crude Unit Piping Circuit

Consider a 12-inch, Class 1 piping circuit carrying atmospheric tower bottoms at 650°F in a crude unit processing a sour, high-TAN feedstock. Sulfidic corrosion is expected and evaluated against the McConomy curves relative to sulfur content and operating temperature. Original nominal wall is 0.500 in. (Schedule 40); t_min per the current B31.3 calculation is 0.291 in.

Turnaround inspection history: 0.437 in. eight years ago, 0.402 in. four years ago, and 0.379 in. this turnaround. Long-term rate from original nominal, over 22 years in service: (0.500 − 0.379)/22 = 5.5 mils/year. Short-term rate from the last two readings: (0.402 − 0.379)/4 = 5.75 mils/year. The two are close enough here that the governing rate is straightforward — the higher figure, 5.75 mils/year.

Remaining life: (0.379 − 0.291)/0.00575 = 15.3 years. Under API 570's half-life convention for a Class 1 circuit, the reinspection interval is capped well below that full figure — in practice, most programs would set this circuit for reinspection inside 5 years, both because of the Class 1 designation and because sulfidic corrosion mechanisms are known to accelerate nonlinearly if feedstock sulfur content or TAN increases. The RBI program should also flag this circuit for closer monitoring the moment the crude slate changes, independent of the calendar-based interval, because corrosion rate assumptions in an RBI model are only valid as long as the process conditions they were built on stay the same.

Common Errors That Quietly Corrupt the Calculation

  • Averaging across dissimilar CMLs. Combining an elbow reading with a straight-run reading into one "circuit average" corrosion rate masks the actual worst case on the circuit.
  • Using nominal instead of as-built thickness. Pipe mill tolerance alone can run well under nominal on some product forms; starting the RL clock from nominal instead of the actual initial thickness overstates remaining life immediately.
  • Ignoring measurement uncertainty. Conventional straight-beam UT has a realistic accuracy band that depends heavily on surface condition and technique; when the calculated corrosion rate is low and the interval between readings is short, that uncertainty can be a large fraction of the apparent wall loss, producing a corrosion rate that's mostly measurement noise. That's a real argument for less frequent but more rigorous readings over frequent, noisy ones on very slow-corroding circuits.
  • Not re-verifying t_min after a rerate or process change. A capacity increase, a temperature creep, or a MAWP change all move t_min. Continuing to compare current thickness against the original design t_min after any of those changes understates the urgency of the interval.
  • Treating RBI corrosion rate assumptions as permanent. An RBI model built five years ago on a feedstock slate that has since changed is running on stale corrosion rate inputs until someone updates it.

From Calculation to a Defensible Interval

The output that actually matters to a plant manager, an insurance underwriter, or a jurisdictional inspector isn't the remaining life number itself — it's the inspection interval derived from it, along with the documented basis for that interval. A defensible package includes the governing corrosion rate and which of short-term/long-term was used and why, the t_min calculation and its code basis, the CML history showing consistent measurement locations, and the code-mandated interval cap applied on top of the raw RL/2 math. Auditors reviewing a mechanical integrity program under OSHA's Process Safety Management standard (29 CFR 1910.119) or a comparable state program will ask for exactly this chain, not just a spreadsheet with a final "years remaining" column.

This is also where the practical difference between a Level II technician taking a UT reading and an ASNT Level III reviewing the resulting remaining-life package shows up: the Level III role is to catch exactly the errors above — the mismatched CML, the stale t_min, the averaged corrosion rate — before they turn into an inspection interval that looks defensible on paper but wouldn't survive a closer look.

Why Spreadsheet-Based RLA Breaks Down at Scale

A single-circuit remaining life calculation is a five-minute spreadsheet exercise. A refinery with several thousand active CMLs across hundreds of piping circuits, dozens of vessels, and a tank farm is a different problem entirely. Spreadsheet-based tracking tends to fail in predictable ways: CML naming conventions drift between turnarounds, the corrosion-rate formula gets copy-pasted incorrectly into a new row, and nobody notices a circuit's interval quietly slipping past its due date because there's no automated flag tied to the calculation itself.

This is the gap that purpose-built NDT inspection management software and NDT reporting software are built to close — CML history that persists automatically across turnarounds, corrosion rate and remaining life calculated the same way every time with the correct governing-rate logic built in, and inspection intervals that flag themselves as they approach the code-mandated cap rather than relying on someone remembering to check a spreadsheet. For facilities managing integrity data across a whole asset base, a digital twin platform takes this further by mapping CML history and remaining-life status directly onto a 3D model of the unit, so a turnaround planner can see at a glance which circuits, vessels, and tank components are approaching their reinspection window without hunting through separate reports for each equipment type.

Building the Skill In-House

Remaining life calculation is a core competency that belongs inside an owner-operator's mechanical integrity team, not solely with a third-party inspection contractor, because the people setting inspection priorities need to understand exactly what's driving each interval. NDT training that covers UT thickness gauging alongside the API 570/653/510 remaining-life framework gives inspection and reliability staff the ability to sanity-check a contractor's numbers rather than simply accepting a report at face value. For programs that need an outside check on methodology — CML grid design, RBI corrosion rate assumptions, or a specific fitness-for-service question — bringing in ASNT Level III consulting for a program review is typically far cheaper than discovering the gap during an incident investigation.

Atlantis NDT Products & Services

Running this as a programme, not a one-off

If you are responsible for an inspection programme rather than a single job, the recurring problem is rarely the code — it is keeping measured thickness, damage-mechanism assignment and next-inspection dates in one defensible place. Asset integrity management software covers keeping measured thickness readings per CML in one place, so the RBI (API 580/581) and fitness-for-service (API 579) work your integrity team or its specialists carry out starts from measured data rather than default rates. Atlantis supplies the NDT data and the software to hold it; it does not perform RBI or FFS assessments.

Atlantis NDT Products & Services

The half-life rule: turning remaining life into a next inspection date

Short answer: Under API 510 (11th edition, 2022), remaining life = (actual thickness minus required thickness) divided by the corrosion rate, where t-required excludes corrosion allowance and mill tolerance. Unless an RBI assessment justifies otherwise, the interval to the next internal or on-stream inspection is the lesser of half the remaining life or 10 years. If remaining life is under four years, the interval may be the full remaining life, up to two years. The external visual interval is the lesser of five years or the internal interval.

The sections above explain how corrosion rate drives remaining life. This section takes the last step that auditors and inspectors check first: turning a remaining-life number into a dated next inspection, using the rules as API 510 states them. The equipment-specific rules for piping and tanks are covered after the vessel rules. API codes are copyrighted, so everything here is paraphrased. Clause references are to the API 510 11th edition (October 2022, with errata in 2023 and 2025). Confirm against the edition your programme adopts. The interval is set by the inspector or engineer under the owner-operator's quality assurance system. NDE data feeds that decision but does not make it.

What API 510 actually says about remaining life

API 510 calculates remaining life in years as actual thickness minus required thickness, divided by the corrosion rate. Each term has a precise meaning in the code, and most errors come from using a near-miss definition:

  • Actual thickness is the thickness measured at a corrosion monitoring location (CML) during the most recent inspection.
  • Required thickness is the minimum thickness for the same CML or component, from the design formulas for pressure and structural loads, without corrosion allowance or manufacturer's tolerances. API 510 also lets it be reassessed through a fitness-for-service analysis under API 579-1/ASME FFS-1. That is an engineering assessment the owner commissions, not a default.
  • Corrosion rate is the rate the inspector selects, in consultation with a corrosion specialist, as best reflecting current conditions.

API 510 defines two rate calculations. The long-term rate uses the initial thickness at the CML and the current reading. The initial thickness is either the first measurement at that CML or the thickness at the start of a new corrosion environment. The short-term rate uses the previous and current readings. The code does not simply say "always use the higher." It lists factors to weigh when choosing:

  • whether damage is general or localized
  • impingement or erosion-corrosion
  • when the corrosion started
  • process changes such as water wetting, chlorides or lower pH
  • whether protective scale has formed or been stripped away
  • stagnant areas where deposits such as iron sulfide collect
  • whether the unit keeps operating within its integrity operating windows
  • whether a short-term spike came from a one-off event that has since been corrected

Choosing the higher rate, as described earlier on this page, is the conservative default many programmes adopt. The code's own test is which rate best reflects current conditions, and the choice must be documented.

API 510 also stresses data quality. Thickness and corrosion-rate data used for remaining life should be validated before they set next inspection dates. Bad data raises the risk of unexpected failure or of retiring a vessel too early. A statistical treatment of thickness data is allowed but must be documented. It may not suit vessels with random but significant localized corrosion.

The interval rules, in plain language

Inspection type (API 510)Default maximum interval, unless RBI justifies otherwiseNotes
Internal or on-stream inspectionThe lesser of half the remaining life or 10 yearsAn internal is not required at half the remaining life where thinning can be detected or monitored effectively from outside.
Thickness measurement inspectionThe lesser of half the remaining life or 10 yearsThe same short-remaining-life provision applies.
Remaining life under four yearsMay be the full remaining life, up to a maximum of two yearsApplies to both internal/on-stream and thickness intervals.
External visual inspection (aboveground vessels)The lesser of five years or the required internal/on-stream intervalPreferably done with the vessel in operation.
Projected-MAWP method (alternative)The interval works if the projected MAWP of the limiting component stays at or above the nameplate or rerated MAWP plus static head. Still capped at 10 years without RBI.Iterative: choose an interval, project the metal loss, then check MAWP.
RBI-based intervalsMay exceed the 10-year and half-life limits for internal and on-stream inspections and the 5-year external limitRBI-based external intervals must not exceed 10 years. An RBI interval beyond 10 years needs engineer and inspector review at least every 10 years.

Two points are easy to miss. First, the half-life rule is a ceiling, not a target. API 510 separately warns that when corrosion rates speed up or become unstable, the cause should be investigated using API RP 585. It also warns that relying on ever-shorter inspection intervals can be a riskier strategy than replacement, redesign or a material upgrade. Second, vessels in non-continuous service can count years of actual operation rather than calendar years. This applies only if, while idle, the vessel is isolated from process fluids and protected from corrosive internal environments.

Worked example 1: a vessel shell with a long remaining life

These figures are illustrative. Real values come from your design calculations and CML history.

  • CML on the lower shell course of a carbon steel drum. t-required for that course, from the construction-code formula without corrosion allowance: 0.420 in.
  • First reading at this CML (2006): 0.625 in. Previous reading (2020): 0.560 in. Current reading (2026): 0.540 in.
  • Long-term rate: (0.625 - 0.540) / 20 years = 0.00425 in./yr (4.25 mpy).
  • Short-term rate: (0.560 - 0.540) / 6 years = 0.0033 in./yr (3.3 mpy).
  • The inspector, with the corrosion specialist, finds no process change and uniform thinning. To stay conservative they select the long-term rate, 4.25 mpy, and record why.
  • Remaining life: (0.540 - 0.420) / 0.00425 = 28.2 years.
  • Half the remaining life is 14.1 years, which exceeds 10 years. The next internal or on-stream inspection is therefore due within 10 years, by 2036.
  • External visual: the lesser of five years or the internal interval, so due by 2031.
  • MAWP check for continued service: API 510 calculates MAWP using measured thickness minus twice the expected corrosion loss before the next inspection. That gives 0.540 - 2 x (0.00425 x 10) = 0.455 in., still above 0.420 in. The current MAWP is supported through 2036.

The governing date for the vessel is the shortest result across all its CMLs and components, not the shell alone. As noted earlier on this page, that is often a nozzle.

Worked example 2: a nozzle with less than four years left

  • Inlet nozzle CML with erosion-corrosion. t-required 0.270 in. Current reading 0.300 in. Selected rate 9 mpy (0.009 in./yr), from the short-term rate because the attack is localized and recent.
  • Remaining life: (0.300 - 0.270) / 0.009 = 3.3 years.
  • Remaining life is under four years, so API 510 allows the interval to be the full remaining life up to a maximum of two years. Half-life would give 1.67 years.
  • Now apply the MAWP projection. At a two-year interval, projected thickness = 0.300 - 2 x (0.009 x 2) = 0.264 in. That is below the 0.270 in. required. A two-year interval would not support the current MAWP. To keep projected thickness at or above 0.270 in., the interval must be no more than (0.300 - 0.270) / (2 x 0.009) = 1.67 years.
  • The decision belongs to the inspector and engineer. Options include a shorter interval, on-stream monitoring of the nozzle, a repair or replacement plan, or an owner-commissioned engineering assessment. The record must show which option was chosen and why.

This example shows why a remaining-life spreadsheet with only one formula is not enough. The two-year short-life allowance, the half-life ceiling and the MAWP projection can each give a different answer. The programme has to show which one governs.

Same logic in API 570 and API 653, different caps

API 570 (piping). The current edition (5th, February 2024) calculates remaining life in its section on remaining life. Interval setting is in its inspection-interval section, with a table of maximum intervals by piping class. API's own Body of Knowledge for the API 570 exam cites remaining life at 7.2 and intervals at 6.3.3 and Table 1. Thickness-measurement intervals follow the same principle: the lesser of half the remaining life or the class maximum in that table, plus separate rules for injection points and soil-to-air interfaces. Take the class-maximum figures from your licensed copy of the current edition. For class-specific detail see API 570 Class 1 inspection intervals and piping circuit CML inspection.

API 653 (tanks). Tank intervals use component-specific logic. Shell and bottom are treated differently, with bottom remaining life based on minimum remaining thickness after projected product-side and soil-side corrosion. External inspection intervals are tied to the shell corrosion rate, and internal intervals to projected bottom thickness, each with code maximums. API 653 Addendum 4 (July 2025) revised the text on tank-bottom thickness measurement, so check the current edition and addendum before quoting numbers. See API 653 tank inspection intervals explained.

Across all three codes, an RBI assessment under API RP 580 or 581 can justify different intervals. That is an owner-commissioned engineering assessment with its own documentation and review requirements, not a shortcut. For the trade-offs see time-based vs risk-based intervals.

New vessels, service changes and "no corrosion rate yet"

Remaining life needs a corrosion rate. New vessels, and vessels moved to a new service, do not have one yet. API 510 gives four ways to estimate a probable rate:

  1. Data from the owner's own vessels in the same or similar service.
  2. Readings from appropriately placed ultrasonic sensors.
  3. An estimate from a corrosion specialist.
  4. Published data for similar service.

Where none of these can be applied with confidence, the inspection plan must include on-stream direct measurement of wall loss after six months of service. Measurements continue at suitable intervals until a credible rate is established. API 510 notes that thickness readings taken over short intervals carry statistical scatter, so an early "rate" may not reflect the environment. If the assumed rate later proves wrong, the actual rate must replace it in the remaining-life calculation. That changes the next inspection date as well.

For large vessels with zones that corrode at clearly different rates, API 510 allows each zone to be treated on its own, with its own interval. It also lets a qualified corrosion specialist document that a vessel has no credible internal degradation mechanism. That vessel may then be exempt from internal inspection and corrosion monitoring. External inspection is still required.

Deferring a due date without breaking the rules

A calculated date is binding. The API 510 11th edition says a vessel may not be operated past its due date without a valid deferral. Deferrals must be documented and are meant to be the exception. A simplified deferral may be approved by the owner-operator only if all of the following are true:

  • The due date has not been deferred before.
  • The new date adds no more than 10 percent of the interval or six months, whichever is less.
  • A review of operating conditions and history supports it.
  • The owner's inspector and operations management consent.
  • The records are updated before the original due date passes.

Anything longer needs a documented risk assessment, or an update to an existing RBI assessment, under a formal deferral procedure. Calculated remaining life is one of the inputs that procedure considers.

The record an inspector or auditor expects

For each component or CML group, a defensible next-inspection-date record shows:

  • the t-required calculation and its code basis, without corrosion allowance
  • the thickness history at consistent CMLs, with method and instrument details
  • the long-term and short-term rates, the rate selected and the reasoning
  • the remaining life
  • which interval rule governs: half-life, 10-year cap, short-life allowance, MAWP projection or RBI
  • the resulting internal, thickness and external due dates
  • the name of the inspector or engineer who set them under the owner's QA system

At PSM-covered US facilities, 29 CFR 1910.119(j) also requires each inspection and test to be documented with the date, the person who did it, the equipment identifier, a description and the results. In Alberta, ABSA's AB-506 sets provincial interval and documentation requirements that apply alongside API 510. For PSM support see OSHA PSM mechanical integrity NDT.

Common half-life mistakes

  • Calculating to nominal minus corrosion allowance. Remaining life should be calculated to the required thickness, not to nominal thickness less the corrosion allowance. Mixing the two can either inflate or deflate remaining life.
  • Using remaining life itself as the interval. The interval is half the remaining life, capped. The full-remaining-life allowance applies only below four years and only up to two years.
  • Applying the 10-year cap to external inspection. The external cap is five years, or the internal interval if shorter, unless RBI justifies otherwise.
  • Ignoring the MAWP projection. As worked example 2 shows, it can govern for short-life components.
  • Letting dates slip because the rate "looks wrong". Investigate the data, but keep the date unless a documented deferral is in place.
  • Resetting the long-term rate after a repair without documenting a new corrosion environment. API 510 allows a new initial thickness only at the start of a new corrosion environment.

Where Atlantis fits

Atlantis NDT supplies the input data for these calculations. That includes UT thickness surveys at established CMLs, scanning UT and corrosion mapping to find true minimums in localized-corrosion zones, and PAUT where cracking is a concern. All of it is performed by ASNT-certified technicians under ASNT Level III oversight and reported against the owner's CML identifiers. The owner's API-certified inspector or engineer calculates remaining life and sets the next inspection date. Atlantis does not set intervals, perform RBI or FFS, or act as inspector of record. See pressure vessel inspection services. Request a CML thickness survey quote, or ask about corrosion mapping for short-life components.

Half-life rule FAQs

What is remaining life in pressure vessel inspection?

It is the years left before a component reaches its required thickness at the selected corrosion rate. It equals actual minus required thickness, divided by the corrosion rate.

What is the half remaining life inspection interval?

API 510 caps the interval between internal or on-stream inspections at the lesser of half the remaining life or 10 years, unless RBI justifies otherwise.

What if remaining life is less than four years?

The interval may be the full remaining life, up to a maximum of two years. Check the MAWP projection too, because it can be tighter.

Does t-required include corrosion allowance?

No. API 510 defines required thickness without corrosion allowance or manufacturer's tolerances.

Which corrosion rate should I use, long-term or short-term?

The one that best reflects current conditions, chosen by the inspector with a corrosion specialist and documented. Many programmes default to the higher of the two.

How is the API 570 next inspection date calculated?

The same way in principle: the lesser of half the remaining life or the class maximum in API 570's interval table. Use the current 5th edition figures.

Can an RBI assessment replace the half-life rule?

Yes. API 510 allows RBI under API RP 580 to set intervals beyond the half-life and 10-year limits, with required periodic review. It is an engineering assessment the owner commissions.

Next step

Atlantis performs the NDE this work needs and reports to your inspector of record. To go further, request an inspection quote. We reply within one business day.

Where Atlantis can help

Atlantis provides NDT inspection, ASNT SNT-TC-1A training, Level III consulting and NDT software.