API 653 is the industry standard that governs how aboveground storage tanks are inspected, repaired, altered, and reconstructed after they are put in service. It is the rulebook tank owners follow to keep large storage tanks safe and legal over decades of operation. This guide explains what API 653 covers, how it differs from the tank construction standard, and what inspections it requires.
API 653 in one line: API 653 is the American Petroleum Institute standard for the inspection, repair, alteration, and reconstruction of aboveground steel storage tanks after they enter service. It sets out inspection types and intervals, minimum thickness and integrity criteria, and repair rules to keep welded storage tanks fit for service.
API 653 applies to aboveground welded steel storage tanks - the large vertical tanks used for crude, products, and other liquids - once they are in service. It governs the whole in-service life: how to inspect the tank, how to evaluate corrosion and minimum remaining thickness of the shell, bottom, and roof, and how to properly repair, alter, reconstruct, or relocate a tank so it stays fit for continued service. It relies on engineering evaluation to decide whether a tank can keep operating, needs repair, or must be taken out of service.
The standard is written for tanks originally built to API 650 (or the older API 12C), but its evaluation principles are also applied to tanks built to other codes. It is not a construction standard - it starts where construction leaves off.
It helps to see API 653 next to its companion standards. API 650 is the standard for designing and building new welded aboveground storage tanks. API 653 is the standard for inspecting, maintaining, and repairing those tanks once they are in service. And API 651, 652, and related documents cover corrosion protection and lining. In short: API 650 builds the tank, API 653 keeps it fit for service, decade after decade.
That distinction matters in practice - a repair or alteration under API 653 must bring the affected work back to the intent of the original construction code, so the two standards are used together throughout a tank's life.
API 653 defines several inspection types. Routine in-service (external) inspections are done frequently by operating personnel. Formal external inspections by a certified API 653 inspector are done on a set interval (commonly not to exceed five years, or per corrosion-rate calculation). Internal inspections - which require taking the tank out of service and cleaning it to examine the bottom and lower shell - are done on longer intervals set by the measured corrosion rate and bottom condition, with a maximum ceiling. Ultrasonic thickness testing and, for bottoms, techniques like magnetic flux leakage are used to quantify metal loss.
Certified API 653 inspectors carry out and document the formal inspections, calculate remaining life from corrosion rates, and set the next due dates. The result is a documented integrity history that operators and regulators rely on. This is periodic asset integrity work rather than continuous monitoring, so a SCADA platform like Merobix does not perform it - but the operational tank data it trends (levels, overfill events, and, where instrumented, corrosion or cathodic-protection signals) supports the integrity program that API 653 formalizes.
API 653 is the American Petroleum Institute standard for inspecting, repairing, altering, and reconstructing aboveground steel storage tanks after they are in service. It sets inspection types and intervals, minimum thickness and integrity criteria, and repair rules to keep welded storage tanks fit for continued service.
API 650 is the standard for designing and building new welded aboveground storage tanks. API 653 is the standard for inspecting, maintaining, and repairing those tanks once they are in service. API 650 builds the tank; API 653 keeps it fit for service over its operating life.
It defines routine external checks by operators, formal external inspections by a certified inspector (commonly at intervals not to exceed five years or per corrosion rate), and internal inspections on longer intervals set by measured corrosion rate and bottom condition, up to a maximum ceiling. Intervals tighten as measured corrosion rates increase.
Primary references from the standards bodies and regulators that define this topic:
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.