Internal Corrosion
Internal Corrosion Review
Workflow: Metal Loss
Internal corrosion review is the workflow for metal loss that may be driven by the product stream, water hold-up, solids, deposits, flow disturbances, dead legs, drips, or other service-related internal conditions rather than outside environment alone.
Quick scan
One-minute summary
Scan the essentials first, then open deeper sections as needed.
Overview
Internal corrosion review is the workflow for metal loss that may be driven by the product stream, water hold-up, solids, deposits, flow disturbances, dead legs, drips, or other service-related internal conditions rather than outside environment alone.
Why it matters
Internal corrosion can look like ordinary metal loss in the listing while the real decision drivers sit in the operating context. Engineers often need to connect the feature to flow regime, low points, chemistry, inhibition performance, upset history, and the local piping configuration before deciding whether the condition is routine, active, or likely to recur.
Top concern drivers
- Service conditions that support internal corrosion, such as water, solids, CO2, H2S, MIC, or deposit build-up
- Location in a low spot, dead leg, drip, tee, lateral, injection point, reducer, or other flow-disturbance area
- Localized pitting, channeling, or morphology that suggests internal attack rather than uniform external loss
- Repeated internal activity, upset history, or weak inhibition / process control evidence
Immediate escalation cues
- Escalate when the location and service strongly support active internal corrosion or repeated attack
- Escalate when pitting, localized attack, or interaction could materially change timing or ranking
- Escalate when operating-context records are too weak to support a defensible closeout
Practical next steps
- Start by checking whether the feature sits in a place where internal corrosion actually makes sense, such as a low point, dead leg, tee, lateral, or upset-prone area
- Review service and chemistry history before closing the feature as routine metal loss
- Use prior digs or prior ILI runs to see whether the condition looks recurring, active, or segmentation-driven
- Escalate when service context is weak or the morphology suggests localized internal attack rather than mild general loss
Overview
Internal corrosion review is the workflow for metal loss that may be driven by the product stream, water hold-up, solids, deposits, flow disturbances, dead legs, drips, or other service-related internal conditions rather than outside environment alone.
Why It Matters
Internal corrosion can look like ordinary metal loss in the listing while the real decision drivers sit in the operating context. Engineers often need to connect the feature to flow regime, low points, chemistry, inhibition performance, upset history, and the local piping configuration before deciding whether the condition is routine, active, or likely to recur.
Common scenarios
- Metal loss at a low point where water hold-up and solids make internal attack more credible than outside corrosion
- Localized pitting near a tee, lateral, or dead leg where flow behavior may be driving attack
- A feature that looks routine until service upset history suggests changing internal conditions
- Repeated calls in the same service where the real question is whether mitigation or operating changes are working
Key Concern Drivers
- Service conditions that support internal corrosion, such as water, solids, CO2, H2S, MIC, or deposit build-up
- Location in a low spot, dead leg, drip, tee, lateral, injection point, reducer, or other flow-disturbance area
- Localized pitting, channeling, or morphology that suggests internal attack rather than uniform external loss
- Repeated internal activity, upset history, or weak inhibition / process control evidence
- Uncertain feature morphology or weak records on service conditions and operating changes
Data and Uncertainty
Core data
- Feature type and whether the reported condition is plain, interacting, or uncertain
- Depth and size information such as percent wall thickness, length, and local geometry extent
- Orientation and shape, including whether the feature is axial, circumferential, or irregular
- Reliable location information referenced to welds, bends, seams, and nearby anomalies
Context data
- Weld proximity and confirmation of girth-weld or seam association
- Pipe properties including wall thickness, grade/SMYS, diameter, and seam type
- Coating condition, environment, and any evidence of mechanical damage
- Pressure history, operating cycles, and local operating context where relevant
Advanced / situational data
- Detailed profile information for dents, strain-sensitive geometry, or irregular corrosion
- Prior ILI comparison to distinguish growth from reporting change
- Geotechnical, strain, or movement indicators if local loading may be part of the concern
- Excavation verification, NDE, UT mapping, or field observations when available
Missing or uncertain data that matters
- Missing or uncertain location control can change whether a feature is treated as plain body-pipe, weld-associated, or interacting
- Weak sizing confidence or classification uncertainty can materially limit screening quality
- Lack of prior inspection or field verification often increases the need for conservative judgment
Decision Logic
Can this be treated as a simple single-threat case?
Only if the local context, data quality, and nearby feature review support that assumption.
Is data quality sufficient for screening?
Check sizing confidence, classification notes, matching accuracy, and whether missing context could change the route.
Is this a candidate for excavation or further review?
Field verification becomes more appropriate when uncertainty or interaction materially affects prioritization.
Should this be escalated to specialist analysis?
Escalate when the feature involves weld interaction, crack concern, unusual geometry, or poor-quality data.
Methods and Frameworks
B31G / Modified B31G corrosion screening
Corrosion screening concepts used to understand whether reported wall loss may be significant as a corrosion feature.
When it may be used: Most useful when the feature includes isolated or grouped metal loss and the engineer is trying to understand corrosion significance or interaction potential.
When it is not appropriate: Not appropriate as a complete answer when deformation, dent interaction, crack suspicion, or unusual geometry changes the local mechanics.
Effective Area / RSTRENG-type thinking
Profile-sensitive corrosion concepts used to think through irregular or interacting wall-loss geometry.
When it may be used: Useful when corrosion morphology, grouping, or profile shape matters more than a single box dimension.
When it is not appropriate: Not appropriate as a full interaction method for dented regions, weld interaction, or cases where geometry loading dominates.
Internal corrosion mechanism review
Useful for connecting the listed metal-loss feature to service, water hold-up, deposits, flow regime, chemistry, and upset history before deciding how much weight to place on the dimensions alone.
When it may be used: Useful for connecting the listed metal-loss feature to service, water hold-up, deposits, flow regime, chemistry, and upset history before deciding how much weight to place on the dimensions alone.
When it is not appropriate: It does not replace pipe-metal-loss screening, field verification, or operator procedures; it helps explain why the feature may be present and whether it may recur.
Grouped / profile-sensitive corrosion review
Useful when internal attack is localized, pitted, irregular, or spread across a low-point or disturbed-flow region rather than one clean isolated box.
When it may be used: Useful when internal attack is localized, pitted, irregular, or spread across a low-point or disturbed-flow region rather than one clean isolated box.
When it is not appropriate: It does not by itself prove the active mechanism and should not be used without operating-context review.
In-line Inspection Systems Qualification Standard
API
Why it applies: Useful for data quality checks, feature confidence review, matching questions, and any topic driven by ILI limitations.
Key limitations: This is a qualification and use framework, not a defect-specific engineering decision tool by itself.
Managing System Integrity for Hazardous Liquid Pipelines
API
Why it applies: Useful when operators need process discipline around evaluation, dig planning, repair scheduling, and record quality, especially on hazardous liquid systems.
Key limitations: Guidance context only. It is not itself the enforceable repair timing rule, and it is less directly applicable to gas transmission than liquid integrity management workflows.
Manual for Determining the Remaining Strength of Corroded Pipelines
ASME
Why it applies: Most useful for general metal loss, axial corrosion, pitting, and corrosion screening discussions.
Key limitations: Included here only as reference context. This app does not perform calculations and users should follow approved company procedures.
Corroded Pipelines Recommended Practice (DNV-RP-F101)
DNV
Why it applies: Most useful for corrosion-oriented topics such as general metal loss, axial corrosion, circumferential corrosion, pitting, interacting metal loss, and corrosion interaction cases where profile and grouping matter.
Key limitations: This is corrosion-focused guidance and does not by itself resolve dent interaction, crack-like threats, or other non-corrosion damage mechanisms.
Modified B31G / RSTRENG Method References
Industry Practice
Why it applies: Most relevant to interacting metal loss, irregular corrosion morphology, and grouping decisions.
Key limitations: Use only through approved company workflows and software implementations; the method still depends on reliable profile data.
DNV-RP-F101
DNV
Why it applies: Useful as corrosion-assessment context for isolated, interacting, and complex-shaped metal-loss features and for thinking beyond simple box dimensions.
Key limitations: It is a corrosion-focused method family and does not by itself resolve dent interaction, crack-like behavior, or non-corrosion damage mechanisms.
API 579
API
Why it applies: Useful as broad FFS context when the corrosion condition becomes irregular, interacting, or difficult to close with ordinary screening assumptions alone.
Key limitations: API 579 is not a direct replacement for pipeline-specific corrosion methods or operator-approved response criteria.
API RP 1160
API
Why it applies: Provides integrity-management process context for anomaly prioritization, remediation planning, and defensible documentation.
Key limitations: Guidance framework only; enforceable timing comes from applicable CFR requirements and operator procedures.
PRCI research and guidance
PRCI
Why it applies: Useful when operator workflows need research-backed context on defect interaction, assessment limits, or field validation practice.
Key limitations: Research context is not itself an operating procedure or repair criterion.
- Corrosion-oriented equation frameworks help describe remaining strength, effective area, and why wall-loss profile matters.
- These concepts are useful for screening corrosion behavior, but they depend on good sizing, grouping, and location confidence.
- When interaction, deformation, or unusual loading is present, corrosion-only methods can become incomplete.
When This Drives a Dig
- The feature may drive a dig when uncertainty, interaction, or local context makes desktop screening alone hard to defend.
- A dig becomes more attractive when field confirmation could materially change repair timing, disposition, or specialist escalation.
- Corrosion grouping, unusual morphology, or uncertain location context often drives field verification.
Field Verification Workflow
- Confirm feature location, expose the pipe safely, and compare field location to the original screening data.
- Document actual condition, including coating state, surface condition, geometry, nearby welds, and whether the reported interaction is real.
- Capture measurements, photos, and any NDE or UT needed to support disposition.
Disposition and Repair Outcomes
- Disposition should state whether the feature was repaired immediately, scheduled for remediation, escalated for specialist review, or retained with justified monitoring.
- If field verification changed the understanding of the feature, document why the disposition changed from the original screening expectation.
Documentation and Defensibility
- Record the feature ID, location basis, data sources, and the assumptions used in the review.
- Document what method family was considered, what uncertainty remained, and why the selected response path was reasonable.
- If excavation or field review occurred, capture measurements, observations, photos, and what they changed in the decision process.
Practical Next Steps
- Start by checking whether the feature sits in a place where internal corrosion actually makes sense, such as a low point, dead leg, tee, lateral, or upset-prone area
- Review service and chemistry history before closing the feature as routine metal loss
- Use prior digs or prior ILI runs to see whether the condition looks recurring, active, or segmentation-driven
- Escalate when service context is weak or the morphology suggests localized internal attack rather than mild general loss
- Pull service, water, chemistry, and inhibition history for the segment
- Compare with prior runs or dig history for recurrence and growth
- Route for corrosion or operations review if the mechanism may still be active
- Plan field verification if morphology or service context is uncertain
Investigation / Documentation Guidance
Identification and Location
- Record feature ID, segment, stationing or mapping reference, and nearby weld or landmark context.
- State clearly whether the feature is isolated, interacting, or still uncertain.
Data Sources
- List the ILI run, prior runs, field notes, and any supporting drawings or weld data used in the review.
- If sources disagree, record that explicitly.
Field Verification
- If excavated, note what was observed, measured, and how it compared with the desktop interpretation.
Assessment Summary
- Capture the final engineering view in plain language, including what drove the response path and what uncertainty remained.
Related topics
References and Further Reading
Core applicable standards
Core Applicable Standards
Most directly relevant to this topic and commonly used to frame the main review path.
Managing System Integrity for Hazardous Liquid Pipelines
API
Why it applies: Useful when operators need process discipline around evaluation, dig planning, repair scheduling, and record quality, especially on hazardous liquid systems.
What it generally addresses: Integrity-management guidance that supports anomaly prioritization, remediation planning, documentation quality, and defensible workflow for hazardous liquid systems.
Limitations: Guidance context only. It is not itself the enforceable repair timing rule, and it is less directly applicable to gas transmission than liquid integrity management workflows.
Manual for Determining the Remaining Strength of Corroded Pipelines
ASME
Why it applies: Most useful for general metal loss, axial corrosion, pitting, and corrosion screening discussions.
What it generally addresses: Common corrosion assessment reference used to support remaining-strength thinking and corrosion response framing.
Limitations: Included here only as reference context. This app does not perform calculations and users should follow approved company procedures.
Corroded Pipelines Recommended Practice (DNV-RP-F101)
DNV
Why it applies: Most useful for corrosion-oriented topics such as general metal loss, axial corrosion, circumferential corrosion, pitting, interacting metal loss, and corrosion interaction cases where profile and grouping matter.
What it generally addresses: Corrosion assessment guidance covering single defects, interacting defects, complex corrosion shapes, and remaining-strength thinking for corroded pipelines.
Limitations: This is corrosion-focused guidance and does not by itself resolve dent interaction, crack-like threats, or other non-corrosion damage mechanisms.
Modified B31G / RSTRENG Method References
Industry Practice
Why it applies: Most relevant to interacting metal loss, irregular corrosion morphology, and grouping decisions.
What it generally addresses: Widely used corrosion-profile methodology references that support interaction and profile-based corrosion review.
Limitations: Use only through approved company workflows and software implementations; the method still depends on reliable profile data.
Supporting context
Supporting / Cross-Discipline References
Helpful when the review needs integrity-management, regulatory, or cross-discipline context beyond the primary method family.
In-line Inspection Systems Qualification Standard
API
Why it applies: Useful for data quality checks, feature confidence review, matching questions, and any topic driven by ILI limitations.
What it generally addresses: Foundational guidance for understanding ILI system qualification, performance, validation, and responsible use of inspection outputs.
Limitations: This is a qualification and use framework, not a defect-specific engineering decision tool by itself.
DNV-RP-F101
DNV
Why it applies: Useful as corrosion-assessment context for isolated, interacting, and complex-shaped metal-loss features and for thinking beyond simple box dimensions.
What it generally addresses: Profile-sensitive corrosion assessment concepts, interacting defects, and combined loading context for corroded pipelines.
Limitations: It is a corrosion-focused method family and does not by itself resolve dent interaction, crack-like behavior, or non-corrosion damage mechanisms.
API 579
API
Why it applies: Useful as broad FFS context when the corrosion condition becomes irregular, interacting, or difficult to close with ordinary screening assumptions alone.
What it generally addresses: General fitness-for-service framing for metal loss, pitting, laminations, dents/gouges, and documentation discipline.
Limitations: API 579 is not a direct replacement for pipeline-specific corrosion methods or operator-approved response criteria.
API RP 1160
API
Why it applies: Provides integrity-management process context for anomaly prioritization, remediation planning, and defensible documentation.
What it generally addresses: Workflow discipline, repair scheduling context, and record quality rather than defect mechanics alone.
Limitations: Guidance framework only; enforceable timing comes from applicable CFR requirements and operator procedures.
PRCI research and guidance
PRCI
Why it applies: Useful when operator workflows need research-backed context on defect interaction, assessment limits, or field validation practice.
What it generally addresses: Industry best-practice and research support for complex or uncertain conditions.
Limitations: Research context is not itself an operating procedure or repair criterion.
49 CFR Parts 192 and 195
PHMSA
Why it applies: Provide the U.S. regulatory framework that operators commonly review when anomaly evaluation, remediation, documentation, and timing decisions need to be tied back to pipeline safety rules.
What it generally addresses: High-level regulatory context for integrity management, repair timing, maintenance, evaluation, and documented response.
CSA Z662 Oil and Gas Pipeline Systems
CSA Group
Why it applies: Provides Canadian technical and program context where the operator or jurisdiction uses CSA Z662 to frame integrity, maintenance, repair, and evaluation practices.
What it generally addresses: Canadian pipeline systems context for integrity management, maintenance expectations, and defect-related technical framework.
Additional learning
Additional Learning Resources
Good places to deepen understanding of practical behavior, research context, and broader industry guidance.
Pipeline Research Council International (PRCI)
PRCI
Why it applies: Publishes research that helps engineers understand real-world behavior, inspection limitations, interaction effects, and emerging practices across many threat types.
What it generally addresses: Research-backed context for defect behavior, validation limits, and applied integrity practice.
NACE / AMPP corrosion and cracking guidance
NACE / AMPP
Why it applies: Useful for deeper understanding of corrosion mechanisms, SCC context, and related integrity practices that sit alongside pipeline-specific methods.
What it generally addresses: Mechanism-focused corrosion and cracking knowledge and supporting guidance.
DNV recommended-practice context
DNV
Why it applies: Useful when engineers want deeper conceptual grounding for interacting defects, corrosion behavior, or other complex assessment cases.
What it generally addresses: Cross-discipline recommended-practice context for advanced assessment thinking.