Weather-Related and Outside Force
Landslide / Slope Movement
Workflow: Geotechnical / Strain
Landslide or slope movement guidance covers areas where hillslope instability, creep, washout, or erosion may be changing pipe support, introducing bending, or driving segment-level strain concerns.
Quick scan
One-minute summary
Scan the essentials first, then open deeper sections as needed.
Overview
Landslide or slope movement guidance covers areas where hillslope instability, creep, washout, or erosion may be changing pipe support, introducing bending, or driving segment-level strain concerns.
Why it matters
Slope movement can rapidly change loading and can make otherwise moderate dents, weld concerns, circumferential metal loss, or crack-like calls much more consequential. These are usually operator-workflow problems as much as anomaly-review problems.
Top concern drivers
- Evidence of active slope instability or recent terrain change
- Strain, wrinkle bend, or geometry response in the affected segment
- Coincident cracks, circumferential corrosion, dents, or weld interaction
- Drainage change, erosion, or exposed pipe conditions
Immediate escalation cues
- Escalate when active movement or terrain change is evident
- Escalate when movement coincides with cracks, weld issues, or strain-sensitive geometry
- Escalate when the true movement extent is not well defined
Practical next steps
- Define the movement zone first so the review is not artificially narrowed to one anomaly row
- Check for strain-sensitive and crack-like features before settling on a response path
- Use clear documentation if monitoring is selected despite unresolved movement uncertainty
Overview
Landslide or slope movement guidance covers areas where hillslope instability, creep, washout, or erosion may be changing pipe support, introducing bending, or driving segment-level strain concerns.
Why It Matters
Slope movement can rapidly change loading and can make otherwise moderate dents, weld concerns, circumferential metal loss, or crack-like calls much more consequential. These are usually operator-workflow problems as much as anomaly-review problems.
Key Concern Drivers
- Evidence of active slope instability or recent terrain change
- Strain, wrinkle bend, or geometry response in the affected segment
- Coincident cracks, circumferential corrosion, dents, or weld interaction
- Drainage change, erosion, or exposed pipe conditions
- Limited monitoring history or unclear movement boundaries
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
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.
Geohazard and Land Movement Guidance Resources
PHMSA / Industry Guidance
Why it applies: Useful for geotechnical movement, strain concern, wrinkle bends, and cases where terrain context may control next actions.
Key limitations: This is broad guidance context and should be paired with local geohazard procedures and monitoring programs.
API 579
API
Why it applies: Useful as high-level fitness-for-service context when the condition needs broader damage-mechanism framing, documentation discipline, or escalation beyond simple screening.
Key limitations: It is not a pipeline integrity management rulebook and does not replace pipeline-specific methods, regulations, or company procedures.
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.
- Geotechnical and strain review often depends on bending, strain, and loading concepts rather than a simple anomaly dimension alone.
- The key analytical question is often whether the local feature is stable, load-driven, or part of a broader movement problem.
- Equation-style thinking can help frame strain and bending response, but terrain context and field evidence remain critical.
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.
- A dig may be driven by movement evidence, strain concern, or the need to confirm what local loading has done to the pipe.
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.
- Record support condition, surrounding terrain context, and whether strain or bending evidence matches the desktop interpretation.
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
- Define the movement zone first so the review is not artificially narrowed to one anomaly row
- Check for strain-sensitive and crack-like features before settling on a response path
- Use clear documentation if monitoring is selected despite unresolved movement uncertainty
- Route to geotechnical specialist review
- Assemble movement history and anomaly interaction context
- Plan field verification of terrain and pipe condition
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.
- Include terrain, support, strain, or movement observations that changed the 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.
Geohazard and Land Movement Guidance Resources
PHMSA / Industry Guidance
Why it applies: Useful for geotechnical movement, strain concern, wrinkle bends, and cases where terrain context may control next actions.
What it generally addresses: General geohazard context for land movement, right-of-way monitoring, and ground-driven pipeline loading concerns.
Limitations: This is broad guidance context and should be paired with local geohazard procedures and monitoring programs.
Supporting context
Supporting / Cross-Discipline References
Helpful when the review needs integrity-management, regulatory, or cross-discipline context beyond the primary method family.
API 579
API
Why it applies: Useful as high-level fitness-for-service context when the condition needs broader damage-mechanism framing, documentation discipline, or escalation beyond simple screening.
What it generally addresses: General FFS mindset, damage-mechanism identification, and structured assessment thinking across multiple degradation types.
Limitations: It is not a pipeline integrity management rulebook and does not replace pipeline-specific methods, regulations, or company procedures.
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.
PHMSA and CER public guidance resources
PHMSA / CER
Why it applies: Useful for public advisories, guidance notes, and regulator-facing context that help explain where industry attention has been focused.
What it generally addresses: Public guidance, advisories, and oversight context for integrity programs and field response.