Threat Category

Weather-Related and Outside Force

Threat category

Weather-Related and Outside Force

This family covers geotechnical and strain-driven conditions where the integrity question is often about loading, movement, and segment behavior rather than one anomaly row.

Why this category matters

Terrain change, strain, and exposure can make routine-looking anomalies much more important and usually require segment-level rather than single-feature thinking.

  • Weather- and force-driven threats often depend on whether loading is active, consequence is elevated, and operator procedures require faster response.

Quick scan

Category summary

8 topics currently available in this threat family.

Common concern drivers

  • Active movement, changing support, or recurring strain indicators
  • Coincident cracks, weld issues, wrinkle bends, or circumferential features
  • Crossing, slope, thaw-settlement, or drainage context
  • Sparse movement trend or patrol history

Common data gaps

  • Missing IMU, strain, or survey history
  • Sparse ROW observations or geohazard records
  • Limited field confirmation of terrain and support condition

Common decision pitfalls

  • Treating movement as a single-feature issue
  • Ignoring segment-level loading
  • Monitoring without documenting whether the movement is active or stable

Field verification themes

  • Field work should capture terrain condition, support, drainage, exposure, and whether the pipe response matches the desktop interpretation.
Quick Methods and Reference Cards

Geohazard and strain review

Use segment-level loading and movement logic instead of relying on anomaly dimensions alone.

Dent Assessment and Management Guidance

API

Why it fits: Best for plain dents, dent at weld, dent with metal loss, and dent/strain interaction context.

Limitation: This app uses it as guidance context only; actual response criteria should follow approved company procedures.

Managing System Integrity for Hazardous Liquid Pipelines

API

Why it fits: Useful when operators need process discipline around evaluation, dig planning, repair scheduling, and record quality, especially on hazardous liquid systems.

Limitation: 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 fits: Useful for geotechnical movement, strain concern, wrinkle bends, and cases where terrain context may control next actions.

Limitation: This is broad guidance context and should be paired with local geohazard procedures and monitoring programs.

Pipeline Research Council International (PRCI) Research

PRCI

Why it fits: Useful when a topic needs research-backed context or when the engineer needs to understand where industry understanding remains uncertainty-sensitive.

Limitation: Research context does not replace approved company procedures, validated software, or enforceable regulatory requirements.

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.

Dent Assessment and Management Guidance

API

Why it applies: Best for plain dents, dent at weld, dent with metal loss, and dent/strain interaction context.

What it generally addresses: Guidance for understanding dent types, interacting conditions, and practical data needs for dent review.

Limitations: This app uses it as guidance context only; actual response criteria should follow approved company procedures.

Pipeline Research Council International (PRCI) Research

PRCI

Why it applies: Useful when a topic needs research-backed context or when the engineer needs to understand where industry understanding remains uncertainty-sensitive.

What it generally addresses: Industry research support covering dent interaction, crack threats, geohazards, inspection capability, validation limits, and best-practice development.

Limitations: Research context does not replace approved company procedures, validated software, or enforceable regulatory requirements.

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.

Open full references page

Drill Down by Workflow

Topics

Browse this threat family

Each topic follows the same summary-plus-accordion guidance model, but the drill-down is organized by sub-workflow.