Elements of an API 653 Tank Inspection Program
Owners often treat API 653 as a series of one-off inspections, but the standard assigns the owner-operator responsibility for a managed program that ties inspections, records, and repairs together over a tank's life. This page lays out the program elements - roles, records, intervals, and the data that drives them - for the integrity engineer building or auditing that program. It is the management-view companion to the inspection definitions.
API 653 Program Elements in one line: An API 653 tank inspection program is an owner-operator responsibility that ties together the inspection schedule, the qualified people performing and evaluating inspections, the records that establish corrosion history, and the repair and re-rating decisions those records drive. API 653 governs in-service aboveground storage tanks after they are built to API 650; the program is what keeps a tank fit for service between inspections.
Owner Responsibility and Roles
API 653 places the program squarely on the owner-operator, who must ensure inspections happen, are done by qualified inspectors, and are evaluated by a competent engineer or inspector. The standard governs tanks built to API 650 welded tanks once they are in service, so the program picks up where construction leaves off.
Defining who does what is the first program element. The certified inspector performs and documents; an engineer evaluates fitness-for-service and approves repairs, alterations, and re-ratings. Muddying those roles - letting the inspection contractor also sign off on suitability without independent evaluation - is a common program weakness auditors flag.
Records That Establish Corrosion History
The heart of the program is the record set. Original construction data, prior inspection reports, thickness measurements, repair and alteration history, and settlement surveys together establish the corrosion trend that everything else depends on. Without a baseline and a history, you cannot compute a corrosion rate, and without a rate you cannot set a defensible interval.
Thickness data drives the shell and bottom decisions, so a consistent measurement-location scheme matters. A tank bottom corrosion survey and periodic tank settlement survey feed the record set that the next interval is calculated from. Continuous instrumentation such as SCADA level and temperature history can supplement this record but does not replace the physical inspection.
Intervals, Repairs, and Re-Rating
The program has to set and defend inspection intervals from the corrosion rate the records establish, with a not-to-exceed ceiling. The dedicated page on inspection types and intervals in API 653 covers external, ultrasonic, and internal inspections and how their intervals differ. The program element here is making sure the calculation is done and documented, not just the inspection performed.
When inspection finds thinning or damage, the program routes it to a decision: repair, alter, re-rate to a lower level, or take out of service. Those decisions require engineering evaluation and their own records. A program that inspects but has no defined path from finding to decision leaves the most important step - what you do about a problem - undocumented.
Common Misconceptions
The first misconception is that a passing inspection is the deliverable. The deliverable is a maintained program: a defensible interval, a complete record trail, and a decision path. A single clean inspection with no program behind it does not establish fitness for service over time.
The second is that continuous monitoring can replace API 653 inspections. SCADA data on level, temperature, and overfill events supports the program and can inform risk, but it does not measure shell thickness or bottom corrosion. The physical inspection remains the basis; monitoring supplements it.
Frequently Asked Questions
Who owns an API 653 inspection program?
The owner-operator. API 653 assigns responsibility for ensuring inspections occur, are performed by qualified inspectors, and are evaluated by competent personnel to the tank owner-operator, even when the fieldwork is contracted out.
What records does an API 653 program need?
Original construction data, all prior inspection and thickness reports, repair and alteration history, and settlement surveys. Together these establish the corrosion history that drives the next inspection interval and any fitness-for-service decision.
Can SCADA monitoring replace API 653 inspections?
No. Level, temperature, and overfill monitoring supplement the program and can inform risk-based decisions, but they do not measure shell or bottom-plate thickness. Physical inspection remains the basis of the API 653 program.
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.