If you own, operate, or maintain aboveground storage tanks, you’ve probably heard “API 653” come up in conversations about compliance, risk management, and long-term asset planning. But what does an API 653 tank inspection actually involve, and how do you know what type of inspection you need (and when)?
This guide breaks down what API 653 is, which tanks it applies to, who can perform inspections, what happens during the process, and how to prepare your site so you can reduce downtime and avoid surprises.
What Is an API 653 Tank Inspection?
API 653 is a widely recognized industry standard focused on the inspection and continued serviceability of in-service aboveground storage tanks. In plain terms, it’s a structured framework used to evaluate tank integrity over time so owners can reduce the likelihood of leaks, failures, unplanned outages, and costly environmental or safety incidents.
API 653 in plain English
API 653 is designed for in-service tank integrity management. It provides guidance for:
- Inspecting tanks over their operating life
- Determining if they remain fit for continued service
- Planning repairs and managing corrosion
- Documenting tank condition in a consistent, defensible way
What API 653 covers
API 653 goes beyond “a quick look around.” It can involve the inspection and evaluation of:
- Shell (tank wall) condition and thickness
- Bottom condition (a common risk area due to corrosion)
- Roof condition (fixed or floating, depending on tank type)
- Nozzles, manways, and appurtenances
- Foundations and settlement indicators (where applicable)
- Repairs, alterations, reconstruction, and even relocation considerations
API 653 vs. API 650: quick clarity
These standards are related, but they serve different purposes:
- API 650 is primarily for the design and construction of new welded storage tanks.
- API 653 is for the inspection, repair, and ongoing integrity management of tanks already in service.
If API 650 is “how the tank should be built,” API 653 is “how the tank should be maintained and proven safe to keep operating.”
Which Tanks Does API 653 Apply To?
API 653 is most commonly associated with steel aboveground storage tanks (ASTs) used to store petroleum products and other liquids. While the exact applicability can vary by tank type and service, API 653 is widely used as the go-to framework for managing in-service tank integrity across many industries.
Common tank types and industries
API 653 inspections are frequently performed for ASTs found in:
- Fuel terminals and storage depots
- Refineries and petrochemical sites
- Chemical and manufacturing facilities
- Aviation fuel storage and distribution
- Municipal and industrial water applications (in certain cases)
- Other facilities with large-capacity liquid storage
Built-to-code vs. “unknown standard” tanks
Many tanks were built to API 650 or similar standards. Others may be older, modified, or missing drawings and documentation. In practice, API 653 is often used as a widely accepted inspection and evaluation framework even when the original construction standard isn’t perfectly clear—especially when the goal is to manage risk responsibly and maintain robust inspection documentation.
What API 653 generally does not cover
API 653 typically is not intended for:
- Pressure vessels (usually governed by other codes/standards)
- Piping systems (which have their own inspection requirements)
- Underground storage tanks (USTs)
- Cryogenic or refrigerated tanks (often governed by different standards and methods)
If you’re unsure whether your assets fall under API 653, a qualified inspection provider can help you map the right standard to the right equipment.
Who Can Perform an API 653 Inspection?
Not every inspector is qualified to conduct an API 653 inspection in the way the standard intends. These inspections often require specific credentials and experience, especially when inspection results drive repair decisions or ongoing operating limits.
API 653 Authorized Inspector (and why it matters)
An API 653 Authorized Inspector is an individual who holds the API 653 certification and is qualified to perform inspections in accordance with the standard. This matters because:
- Findings can affect whether a tank is safe to keep operating
- Inspection intervals may be calculated based on results
- Repair recommendations often rely on accurate thickness data and evaluation
- Documentation must stand up to internal audits, insurer review, and regulatory scrutiny (as applicable)
When engineering support is needed
Some situations go beyond a routine inspection and require engineering evaluation, such as:
- Repairs or alterations that affect the tank’s integrity
- Significant corrosion concerns or unexpected thinning patterns
- Suspected settlement or foundation movement
- Complex service changes or unusual operating conditions
A strong inspection partner will clearly flag when additional engineering involvement is appropriate—without overcomplicating the process.
Owner/user responsibilities
API 653 also assumes the owner/operator plays an active role in the integrity management program. That usually includes:
- Maintaining records (reports, drawings, repair history, thickness data)
- Planning inspection timelines and coordinating access
- Ensuring safe work conditions, permits, and site readiness
- Aligning internal stakeholders (maintenance, operations, EHS)
Types of Inspections Under API 653 (And When Each Happens)
API 653 isn’t a single “one-size-fits-all” inspection. It includes multiple inspection types, each suited to different risk levels, tank histories, and operating realities.
Routine in-service monitoring (operator-led)
Routine monitoring is typically performed by site personnel and focuses on visible indicators that may suggest developing issues, including:
- Leaks or staining
- Coating damage or blisters
- Corrosion indicators
- Roof drainage problems or obvious deformation
- Unusual odors, sounds, or operational anomalies near the tank
This isn’t a replacement for formal inspection, but it’s an important early-warning layer.
Formal external inspection (in-service)
A formal external inspection is performed while the tank remains in service and typically includes:
- Visual inspection of shell, roof, nozzles, and attachments
- Review of exterior coating condition and corrosion hotspots
- Evaluation of containment and external site conditions
- Observations for settlement indicators or distortion (where relevant)
Depending on tank condition and goals, this may also include targeted NDT such as ultrasonic thickness (UT) measurements at key locations. UT helps quantify remaining wall thickness and identify thinning trends.
Internal inspection (out-of-service)
Internal inspections are more involved because they require taking the tank out of service. They are often essential for evaluating:
- Bottom condition and corrosion (a common driver of risk)
- Internal shell condition at lower courses
- Weld condition, pitting, and localized damage
- Evidence of water bottoms, sludge buildup, or operational issues
Internal inspections also require additional planning for:
- Cleaning and decontamination
- Gas-freeing and atmospheric testing
- Confined space entry protocols and safety controls
Special inspections and trigger events
Certain conditions can justify an inspection outside the normal schedule, including:
- Repairs or alterations
- Changes in product or service conditions
- Suspected damage, impact, or accelerated corrosion
- Unusual settlement, distortion, or operational upset events
- Post-incident checks (after storms, seismic events, or spills)
These inspections are about getting clarity quickly so the next decision is based on real data—not assumptions.
Inspection Intervals and How They’re Determined
One of the most common questions we hear is: “How often do I need an API 653 inspection?”
The most accurate answer is: it depends—on condition, history, and risk. Inspection intervals are generally determined through a combination of baseline guidance, measured corrosion rates, and practical risk-based thinking.
Baseline interval concepts (why “5 years” gets mentioned)
Many sites use a five-year cadence for planning formal external inspections as a starting point. But that’s often just an anchor. Intervals should be adjusted based on the tank’s real-world condition and operating context.
What changes the schedule
Several factors can shorten or extend inspection intervals, including:
- Measured corrosion rates (from UT data and prior reports)
- Product/service changes (especially if they introduce new corrosion risks)
- Presence of water bottoms or sludge
- Prior repairs and the quality/extent of those repairs
- Environmental exposure (coastal, industrial, chemical exposure, etc.)
- Age of the tank and history of findings
- Leak history or recurring problem areas
Risk-based thinking (without the math)
Risk-based inspection thinking comes down to two simple questions:
- How likely is damage to occur or progress to a critical level?
- If it does, how severe are the consequences (safety, environment, cost, downtime)?
A high-consequence tank with uncertain corrosion history should be managed differently than a well-documented tank with stable thickness trends.
How to Prepare Your Site for an API 653 Inspection (Owner Checklist)
Preparation can make the difference between a smooth inspection and one that turns into schedule creep. Here’s what helps most owners get the best outcome with the least disruption.
Documents to have ready
If available, gather:
- Prior inspection reports and thickness readings
- Tank drawings (including shell course details and nozzle data)
- Nameplate information
- Repair history (what was done, when, and by whom)
- Coating history and corrosion mitigation notes
- Any known operational changes over time
Even partial documentation is useful; it helps your inspector focus on likely problem areas and reduces redundant work.
Operational readiness
Plan for:
- Safe access: scaffolding, lifts, ladders, fall protection planning
- Insulation removal (if needed for inspection points)
- Surface condition considerations (coatings, corrosion scale, accessibility)
- Permits and safety requirements aligned with site rules
If an internal inspection is planned
You’ll also want to coordinate:
- Cleaning and waste handling contractors
- Downtime windows and isolation requirements
- Confined space entry procedures and rescue planning
- Atmospheric testing, ventilation, and safe lighting requirements
Ways to reduce downtime and cost
A few practical moves often pay off:
- Bundle scopes when possible (inspect multiple tanks during the same outage)
- Stage access ahead of time so inspection begins immediately
- Do a pre-job walkdown to prevent surprises
- Align inspection with scheduled maintenance outages
Why NDT Tanknicians for API 653 Inspections
API 653 inspections aren’t just about checking a box—they’re about giving owners clear, actionable insight into tank condition so you can plan maintenance, manage risk, and keep operations moving.
At NDT Tanknicians, our approach is built around three things:
- Safety-first planning that aligns with your site requirements
- Clear, organized reporting that supports internal review and compliance needs
- Practical recommendations that help you decide what to do next (and what can wait)
What makes a good inspection partner
When you choose an API 653 inspection provider, look for:
- API 653 Authorized Inspector capability
- Strong NDT support for reliable thickness and condition data
- Experience working within real site constraints (scheduling, access, safety rules)
- Documentation rigor so your records actually help set future intervals
Next steps
If you’re planning an inspection cycle (or you’re dealing with a tank that has limited history) we can help you define the right scope.
- Request an API 653 inspection quote
- Send us your most recent report for a quick interval and scope review
Recent Comments