Threat Category

Stress Corrosion Cracking

Threat category

Stress Corrosion Cracking

This family covers crack-like indications and SCC-oriented workflows where signal credibility, colony behavior, and susceptibility context matter more than corrosion-style screening.

Why this category matters

Crack threats often escalate faster because classification uncertainty, pressure cycling, weld context, and validation needs can materially change the response path.

  • Crack-like threats are usually treated conservatively because uncertainty and failure behavior differ from corrosion workflows.

Quick scan

Category summary

2 topics currently available in this threat family.

Common concern drivers

  • Credible crack-like classification and colony behavior
  • SCC susceptibility and environmental context
  • Weld, strain, or dent interaction
  • Limited NDE, hydrotest, or validation history

Common data gaps

  • Weak crack-ILI confidence or incomplete susceptibility context
  • Missing prior digs, NDE, or hydrotest history
  • Uncertain weld or strain context

Common decision pitfalls

  • Treating crack-like calls as corrosion equivalents
  • Assuming the label alone proves the mechanism
  • Ignoring colony or susceptibility context

Field verification themes

  • Field review should focus on validation, NDE planning, colony confirmation, and coating/environment context.
Quick Methods and Reference Cards

Crack screening and susceptibility review

Use crack-management logic, susceptibility context, and validation discipline rather than corrosion-only methods.

Stress Corrosion Cracking Direct Assessment

AMPP / NACE

Why it fits: Most useful when reviewing SCC susceptibility, colony context, and targeted validation planning.

Limitation: Does not replace crack ILI qualification or company-specific validation protocols.

Assessment and Management of Cracking in Pipelines

API

Why it fits: Useful for crack-like indications, SCC review, seam-related threats, and weld-associated dents with cracking concern.

Limitation: Not a substitute for company-specific crack management procedures or specialist review.

In-line Inspection Systems Qualification Standard

API

Why it fits: Useful for data quality checks, feature confidence review, matching questions, and any topic driven by ILI limitations.

Limitation: This is a qualification and use framework, not a defect-specific engineering decision tool by itself.

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.

Stress Corrosion Cracking Direct Assessment

AMPP / NACE

Why it applies: Most useful when reviewing SCC susceptibility, colony context, and targeted validation planning.

What it generally addresses: Structured SCC assessment guidance covering susceptibility context and prioritization logic.

Limitations: Does not replace crack ILI qualification or company-specific validation protocols.

Assessment and Management of Cracking in Pipelines

API

Why it applies: Useful for crack-like indications, SCC review, seam-related threats, and weld-associated dents with cracking concern.

What it generally addresses: Practical cracking management guidance spanning crack threats, susceptibility, validation, and response planning.

Limitations: Not a substitute for company-specific crack management procedures or specialist review.

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.

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 crack-like review moves beyond ordinary screening and the engineer needs broader damage-mechanism and assessment framing.

What it generally addresses: General FFS structure, damage-mechanism identification, and advanced assessment mindset.

Limitations: API 579 is not a pipeline crack-management procedure and does not replace crack-specific operator workflows or specialist fracture-mechanics assessment.

PRCI research and guidance

PRCI

Why it applies: Useful as supporting research context for crack behavior, validation needs, and integrity-management decision discipline.

What it generally addresses: Industry research perspective where crack-like uncertainty or susceptibility drives review depth.

Limitations: Research support does not replace operator procedure or specialist crack assessment.

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.

Fitness-For-Service (API 579-1/ASME FFS-1)

API / ASME

Why it applies: Useful when crack-like review needs broader assessment framing, escalation awareness, and damage-mechanism context beyond one crack-management document.

What it generally addresses: High-level FFS context and cross-discipline assessment thinking.

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.

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.