Threat Category

Equipment / Appurtenance / Connection Issues

Threat category

Equipment / Appurtenance / Connection Issues

This family covers leaking or deteriorated fittings, threaded connections, valve appurtenances, and other connection problems where the practical concern is often leakage, loosening, local wall disturbance, or whether the hardware condition has changed since the last review.

Why this category matters

Equipment and appurtenance issues can be easy to overlook in anomaly review because they may appear as small geometry changes, local metal loss, or weakly classified calls. In practice they can become important quickly when threads deteriorate, fittings loosen, valves leak, or poorly installed hardware changes the local stress state or creates a leak path.

  • Equipment-related leakage or degraded fittings often drive more immediate field action because the concern can be operational as well as structural.

Quick scan

Category summary

2 topics currently available in this threat family.

Common concern drivers

  • Leaking or loosening threaded fittings and small-bore connections
  • Valve, vent, drain, instrument, or bypass appurtenance condition
  • Run-to-run appearance of new or changed hardware at the location
  • Corrosion, vibration, fatigue, or unsupported loading at the connection

Common data gaps

  • Missing appurtenance drawings, maintenance records, or as-built details
  • Weak field confirmation of which fitting or valve hardware is actually present
  • Sparse leak history or inspection history for the connection

Common decision pitfalls

  • Treating a leaking fitting as only minor corrosion or only a small geometry note
  • Ignoring thread deterioration, vibration, or loosening because the pipe body looks acceptable
  • Missing new or altered appurtenances between runs

Field verification themes

  • Field review should confirm the actual hardware, leakage path, thread condition, support, and whether the fitting or appurtenance has loosened, cracked, or deteriorated.
Quick Methods and Reference Cards

Connection integrity review

Use a hardware- and mechanism-focused review instead of treating the issue as pipe-body corrosion only.

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.

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

API / ASME

Why it fits: Useful across many topic pages as high-level FFS context, especially when conditions are interacting, irregular, escalation-level, or not well served by one simple method family.

Limitation: It is not a pipeline-specific integrity management procedure and should not be treated as a direct replacement for pipeline regulations, company procedures, or topic-specific methods.

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.

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

API / ASME

Why it applies: Useful across many topic pages as high-level FFS context, especially when conditions are interacting, irregular, escalation-level, or not well served by one simple method family.

What it generally addresses: Broad fitness-for-service guidance that helps frame damage mechanisms, assessment pathways, documentation discipline, and escalation beyond simple screening methods.

Limitations: It is not a pipeline-specific integrity management procedure and should not be treated as a direct replacement for pipeline regulations, company procedures, or topic-specific methods.

Supporting context

Supporting / Cross-Discipline References

Helpful when the review needs integrity-management, regulatory, or cross-discipline context beyond the primary method family.

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.

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.