API RP 574 — Inspection Practices for Piping System Components

What API 574 covers, and the three things it deliberately leaves alone

API RP 574 describes how to inspect the physical components of a piping system: pipe and tubing, fittings, flanges and gaskets, bolting, valves, and the supports, shoes, hangers and spring cans that carry the line. Alongside that it covers the inspection tools — ultrasonic thickness instruments, radiographic profile techniques, boroscopes, hardness testers — and, most usefully, the practice for recording and treating thickness data so that a corrosion rate calculated from it means something. It is written as the technical companion to API 570.

Three things it deliberately does not do. It does not set inspection intervals or classify piping by consequence — that is API 570. It does not tell you whether a component measured below its minimum required thickness may remain in service — that is API 579-1/ASME FFS-1, and it needs an engineering assessment, not an inspector's judgement. And it does not identify or explain damage mechanisms; API RP 571 does that, and without it a CML plan is guesswork with a spreadsheet attached.

The distinction is not academic. In audit after audit, an owner justifies a gap by citing 574's permissive language against a 570 requirement that is mandatory. Where the interpretation is genuinely contested — mixed-code circuits, alloy piping, retirement thickness disputes — it is worth putting the position in writing before the audit, which is one of the routine outputs of ASNT Level III consulting: a documented technical basis signed by someone competent to hold it.

Minimum required thickness: two numbers that are not the same number

Every piping component has a pressure design thickness, calculated to the construction code — for process piping, ASME B31.3 — from design pressure, outside diameter, allowable stress, joint efficiency and the appropriate coefficients. It also has a structural minimum: the wall required to carry the pipe's own weight, the contents, insulation and normal external loads on the spans the line is actually supported at. API 574's tabulated structural minima exist because the pressure design thickness for a large-diameter low-pressure line can come out absurdly thin — thin enough that the pipe would sag or buckle long before it burst.

The governing minimum required thickness is the greater of those two. The recurring error runs both ways. Programmes that use the structural table as the retirement thickness on a high-pressure line will run a component past the point where it can hold pressure. Programmes that use pressure design thickness alone on a large low-pressure header will retire the line on a number that ignores dead load entirely, and will be unable to defend it if the line deflects or a support fails.

Two further traps sit inside the same table. The default structural values are for carbon and low-alloy steel — they do not transfer to stainless or nickel alloys with different moduli and different support behaviour. And they assume conventional support spans with no unusual external, thermal or vibratory loading; a line on long spans, or one carrying a heavy valve mid-span, needs the number calculated, not looked up.

Where CMLs go, and why the damage mechanism chooses the location

A condition monitoring location is only as good as the reasoning that put it there. The damage mechanisms credible for the circuit dictate the placement: erosion-corrosion puts metal loss on the outer radius of elbows, at the branch of tees, in reducers and immediately downstream of control valves, orifices and any point where the fluid flashes. Under-deposit and dead-end corrosion put it at low points and at the stagnant ends of deadlegs. Corrosion under insulation puts it at penetrations, at insulation terminations, at low points and under damaged cladding — nowhere near the points chosen for straight-run thickness readings.

This is why a CML plan is a technical document with a rationale, not a list of accessible points. The most common structural weakness in an otherwise well-run programme is that the CML set was established at commissioning, never revised after a damage mechanism review, and never extended when process conditions changed — new feedstock, higher sulphur, a revamp that moved a mixing point. The readings are good; they are simply being taken where nothing is happening.

Volume is the second problem. A moderately complex unit carries tens of thousands of CMLs across hundreds of circuits, each with a history, a rate and a next-due date, and spreadsheets stop being defensible somewhere around the first turnaround. That data belongs in an inspection data management system that holds the isometric, the CML, the reading history and the calculated rate as one linked record rather than four files that agree only by luck.

Thickness readings that survive a corrosion rate calculation

A corrosion rate is a difference between two measurements, which means the error in the rate is the sum of the errors in both. Three sources dominate. First, repeatability: a reading taken 40 mm from last time's reading on a generally corroded surface is not the same reading, and on a pitted or grooved surface it may differ by more than a decade of real loss. Permanent marking, a photograph in the record, and a grid rather than a point are what make the second survey comparable to the first.

Second, temperature. Sound velocity in steel falls as the metal heats, so an instrument calibrated at ambient reports a hot component as thicker than it is by roughly one percent per 100°F above calibration temperature. Applied consistently and never corrected, that bias produces a circuit that appears to be corroding slowly while the wall quietly disappears — and it produces the reverse artefact, an apparent negative corrosion rate, whenever a shutdown survey is compared against an on-stream one.

Third, the starting point. Corrosion rates computed against nominal wall are fiction. Seamless pipe to ASME B36.10M is permitted a 12.5 percent under-tolerance, so a nominal 0.280 in Sch 40 six-inch pipe may have left the mill at 0.245 in with nothing wrong with it. Where the installed baseline was never measured, the honest treatment is to say so and to calculate the rate from measured data only. Where the numbers already carry a decision — a retirement, a turnaround scope, a fitness-for-service submission — independent review of inspection reports before the decision is cheaper than defending the arithmetic afterwards.

Injection points, deadlegs and small bore: the three circuits that actually fail

Injection points concentrate damage over a short length. Where a chemical, a wash water or a corrosion inhibitor enters the process, mixing, flashing and impingement can remove wall at rates an order of magnitude above the parent circuit. The inspection circuit is therefore drawn separately, beginning at least 12 inches or three pipe diameters upstream of the injection point, whichever is greater, and extending downstream to the second change in flow direction. Inside that boundary, single-point readings are not adequate — the loss is local, and a grid or a profile radiograph is what finds it.

Deadlegs behave differently. Stagnant fluid, water drop-out, settled solids and the absence of inhibitor make the far end of a deadleg the worst part of the circuit, and it is invariably the least accessible. Long-standing deadlegs from decommissioned equipment are the classic case: nobody owns them, they are not on the current isometric, and the first sign is a leak. The reliable remedy is a documented deadleg register with each one either monitored at its stagnant end or physically removed.

Small-bore piping fails by a mechanism a thickness programme does not measure. Vibration-induced fatigue cracks socket welds and unsupported branch connections; the wall is full thickness right up to the moment it separates. Threaded connections add a second mode. Managing small bore therefore means a plan built around bracing, support and visual or surface examination — not a thicker grid of UT points.

Valves, flanges, bolting and supports — the components the thickness grid skips

API 574 covers more than pipe wall, and the parts it covers beyond pipe wall are the parts most programmes under-inspect. Valve bodies and bonnets thin like any other pressure boundary, particularly in erosive or wet service, and body-wall readings are rarely on the CML list. Seat tightness and shell testing follow API 598 when a valve returns from overhaul, and the shop record for that test is the evidence an auditor asks for when a valve is credited as an isolation point.

Flanged joints fail for reasons that have nothing to do with general corrosion: face damage, radial scoring across the seating surface, warped or thermally distorted flanges, incorrect gasket material, and bolting that was neither torqued to a procedure nor recorded. Bolting itself corrodes preferentially in wet insulated service and at the nut-to-flange contact, and stud condition is a legitimate inspection item, not a maintenance afterthought.

Supports are the most consistently missed. The pipe-to-shoe and pipe-to-support contact point traps moisture and debris and produces external corrosion that a UT grid on the top and sides of the line will never see; the metal loss is on the underside, at exactly the location carrying load. Spring can travel indicators that are bottomed out, hangers taking no load, and guides seized by corrosion all change the load distribution the structural minimum thickness assumed in the first place.

Turning 574 data into an interval you can defend

The output of the whole exercise is one number: the date of the next inspection. Remaining life is the measured thickness less the required thickness, divided by the corrosion rate. API 570 requires both a long-term rate, computed from the earliest reliable reading, and a short-term rate from the most recent readings, with the more conservative of the two used unless an engineer documents why not. The short-term rate exists precisely to catch a process change that a fifteen-year average will smother.

The interval is then the lesser of half the remaining life or the maximum permitted for the piping class, and where the remaining life is short, the interval collapses accordingly rather than defaulting to the class maximum. Auditors sample this arithmetic more often than they sample the readings, because it is where the programme either converges on reality or quietly drifts away from it — a mis-set required thickness, a stale rate, an interval carried over from the previous cycle without recalculation.

At programme scale that calculation has to run automatically against current data, with the underlying readings, the rate basis and the required thickness all visible on the same record. Where the circuits fall inside an OSHA process safety management programme, the same records are what demonstrate mechanical integrity for covered equipment, which is why owners increasingly run them inside mechanical integrity software rather than reconstructing the trail from archived reports each time an auditor asks.

The findings that recur against a 574-based programme

Six findings appear over and over. Required thickness recorded as the structural minimum on a circuit where pressure design governs, or vice versa. Corrosion rates calculated against nominal wall, ignoring mill under-tolerance, on lines whose installed baseline was never measured. On-stream readings never corrected for metal temperature, and compared directly against shutdown readings. CML sets unchanged since commissioning despite a documented change in service. Injection point circuits monitored as ordinary straight-run piping. Deadlegs on the isometric with no reading at the stagnant end.

What links all six is that none of them is a measurement error. The technician did the job correctly; the framework around the reading was wrong. That is why the corrective action for a 574 finding is almost never retraining the UT technician — it is revising the inspection plan, the required thickness basis, or the data handling rules, and then re-examining the population of circuits the same error touched.

Extent of condition is the part owners underestimate. A single mis-set required thickness is one finding; the same error copied across every circuit built from the same template is a programme finding, and the auditor will ask how many circuits share the template. If you would rather find that out before an audit than during one, a documented gap review against your own written programme is the cheapest version of the exercise — start a conversation with the scope of the circuits in question and the standards your programme cites.

Procurement traps: buying pipe against a mill certificate that no longer describes the pipe

API 574's CML and TML methodology assumes the starting point — the mill certificate thickness — is still true when the survey begins. It frequently is not. A spool ordered as Schedule 40 arrives with a mill certificate showing 0.365 in nominal, but the mill's own under-tolerance of −12.5% means the as-delivered wall could legitimately be as thin as 0.319 in on the day it was installed, before a single day of corrosion. A baseline TML reading taken and compared against the nominal drawing thickness rather than the certified as-built thickness produces a corrosion rate that is partly real and partly an artefact of mill tolerance, and the error compounds every survey afterward.

The fix is procedural rather than technical: retain the mill certificate against the circuit isometric, and use the certified thickness, not the nominal schedule thickness, as the CML baseline. Where a certificate cannot be located for legacy piping, treat the first survey as the baseline rather than backdating a corrosion rate to an assumed construction thickness — a rate calculated from an assumed starting point is not a measured rate, whatever the report format implies.

This is a recurring finding in third-party audits of piping inspection programmes precisely because it looks correct on paper. The report shows a baseline, a current reading, and a calculated rate, and none of those three numbers is wrong in isolation — the error is that the baseline was never verified against what was actually installed.

Request a consultation