Dedicated page
Unknown / Unclassified Feature Regulatory Context
Threat Category: Threat Identification / Data Quality Support | Workflow: Data Quality / ILI Review
This page keeps the regulatory and repair-timing material separate from the core engineering workflow so the topic page stays easier to scan during a review.
This page provides original summary commentary and schedule-awareness context only. Standards, regulations, and recommended practices should be reviewed in their current official form, and operator procedures govern final application.
Quick scan
Regulatory and Timing Summary
Use this as schedule-awareness context, not as a compliance determination by itself.
Context
- Data-quality reviews often become the gating step because the operator first has to decide whether the inspection output is reliable enough to support classification, timing, or closure.
- Operators are generally expected to use procedures that fit the actual condition, the available data quality, and the response timing framework that applies to the system.
- Repair timing and remediation planning often become more conservative when the condition is interacting, uncertain, weld-associated, or difficult to screen confidently.
- A defensible record should show what data were used, what uncertainty remained, and why the chosen response path fit the condition.
Immediate / faster response cues
- A run-quality issue such as sensor loss, speed excursion, or degraded navigation confidence that materially affects a high-priority feature
- Conflicting data where the uncertainty itself could change whether a condition is immediate or scheduled
- Cases where the operator cannot justify continued reliance on the reported feature dimensions or classification without additional verification
Scheduled / planned response
- Reconcile tool performance notes, vendor comments, and field history before closing the review
- Pull prior runs, weld matching, and validation records when the current data set is not strong enough by itself
- Route for specialist or vendor review if the confidence issue changes prioritization or timing
Monitoring / conditional cases
- Monitoring is only reasonable when the uncertainty is bounded, decision impact is low, and the operator has a defined follow-up plan to restore confidence.
Timeline references
Applicable U.S. Context
These references help explain which documents set a clock and which documents guide prioritization or governance.
API RP 1160
Hazardous liquid IM process context
Why review it: Useful as integrity-management context for anomaly prioritization, remediation planning, documentation, and schedule governance, including cases outside HCA where an operator still needs a disciplined risk-based response process.
High-level timing references:
- API RP 1160 is a framework document, not a federal repair-timing table.
- It supports documented risk-based prioritization, remediation planning, reassessment discipline, and day-to-day anomaly management.
- The publicly available API material also notes that the principles of the RP are not limited only to pipelines regulated under 49 CFR Part 195, even though the RP is written for hazardous liquid integrity management.
Caution: Use API RP 1160 as process and defensibility context; fixed timing requirements still come from the applicable CFR section and operator procedures.
49 CFR 192.933
Gas transmission integrity management
Why review it: Useful when a gas transmission integrity assessment has identified a condition and the operator needs the federal timing framework for discovery, remediation, and monitoring buckets.
High-level timing references:
- Discovery: obtain enough information to determine whether the condition is a potential threat within 180 days after the integrity assessment, unless impracticable.
- Immediate repair conditions: the cited rule includes listed conditions that call for prompt repair, with temporary pressure reduction or shutdown until repaired if needed.
- One-year conditions: the cited rule includes listed conditions expected to be remediated within 1 year of discovery.
- Monitored conditions: less severe listed conditions may be monitored until the next scheduled assessment unless expected growth would move them into a 1-year condition sooner.
Caution: These buckets apply in the gas transmission integrity-management context and still depend on the actual condition, operator procedures, and whether the segment is inside the applicable rule framework.
49 CFR 192.710
Gas transmission outside HCA / MCA assessments
Why review it: Useful when the anomaly is on an onshore gas transmission segment outside HCA but still inside the federal outside-HCA assessment framework, such as Class 3, Class 4, or certain MCAs.
High-level timing references:
- Initial assessment: complete by July 3, 2034, or within 10 years after the segment first becomes covered, whichever is later.
- Discovery: obtain enough information to determine whether the condition is a potential threat within 180 days after the integrity assessment, unless impracticable.
- If a condition is discovered, remediation flows into 49 CFR 192.711, 192.712, 192.713, and 192.714 where applicable.
Caution: This applies only to the specific outside-HCA gas transmission populations covered by 49 CFR 192.710, not every gas anomaly everywhere on the system.
49 CFR 192.714
Gas transmission outside HCA repair criteria
Why review it: Useful when a gas transmission anomaly is outside HCA and the operator needs actual federal repair timing buckets rather than only IM-HCA timing language.
High-level timing references:
- Immediate repair conditions: the cited rule includes listed outside-HCA conditions that call for immediate repair upon discovery.
- Two-year conditions: the cited rule includes listed conditions that are expected to be addressed within 2 years of discovery.
- Monitored conditions: the cited rule also includes listed lower-severity conditions that may be recorded and monitored during later risk and integrity assessments.
- If an operator cannot meet certain time limits, the rule may require temporary pressure reduction and can trigger PHMSA notification in some cases.
Caution: The exact bucket depends on the specific condition, analysis under 49 CFR 192.712, and whether the segment is actually governed by the outside-HCA transmission repair rule.
49 CFR 195.452(h)
Hazardous liquid integrity management
Why review it: Useful when a hazardous liquid integrity assessment has found a condition in the integrity-management context and the operator needs the federal evaluation and remediation timing buckets.
High-level timing references:
- Discovery: obtain enough information to determine whether the condition is a potential threat within 180 days after the assessment, unless impracticable.
- Immediate repair conditions: the cited rule includes listed conditions that call for temporary pressure reduction or shutdown until repaired.
- 60-day conditions: the cited rule includes listed conditions expected to be evaluated and remediated within 60 days of discovery.
- 180-day conditions: the cited rule includes listed conditions expected to be evaluated and remediated within 180 days of discovery.
Caution: These buckets apply in the hazardous-liquid integrity-management context and still depend on the actual condition, operator procedures, and whether the line is subject to the applicable IM rule.
API RP 1173
Pipeline safety management system context
Why review it: Useful for both gas and hazardous liquid operators when anomaly timing decisions depend on management-of-change, risk governance, accountability, documentation, and continuous improvement.
High-level timing references:
- API RP 1173 does not set defect-specific repair deadlines.
- It helps define how operators govern decision-making, roles, records, reviews, and improvement actions around anomaly response and remediation planning.
Caution: Treat this as governance and process support, not as a replacement for CFR timing requirements or defect-specific engineering criteria.
Canadian context
Applicable Canadian Regulatory Context
Use these as high-level CER and CSA-awareness anchors when the pipeline or program falls under Canadian requirements.
Canadian requirements depend on jurisdiction, the governing regulator, the applicable edition of CSA Z662, and the operator’s procedures. This page provides summary awareness only and is not Canadian legal or compliance advice.
CER Onshore Pipeline Regulations section 4
Canada general code framework
Why review it: Useful as the Canadian starting point because it ties federally regulated liquid and gas hydrocarbon pipelines to the applicable Canadian regulatory framework and CSA Z662.
What it helps with: General applicability, operator procedures, and the role of CSA Z662 in design, construction, operation, and abandonment.
Caution: This is high-level framework context, not a defect-specific repair schedule or a substitute for reading the applicable edition of CSA Z662 and company procedures.
CER Onshore Pipeline Regulations section 40
Canada integrity-management program context
Why review it: Useful as the Canadian integrity-management anchor for evaluating and mitigating conditions that could adversely affect safety or the environment.
What it helps with: Integrity-management expectations for anticipating, preventing, managing, and mitigating adverse conditions.
Caution: This supports the program framework but does not itself act as a topic-specific repair table.
CER Onshore Pipeline Regulations sections 6.1 and 6.5
Canada management-system and process context
Why review it: Useful when the review needs Canadian context for hazard identification, data management, corrective action, documented processes, and defensible decision-making.
What it helps with: Management-system discipline, documented procedures, hazard evaluation, corrective and preventive action, and data management.
Caution: These sections describe system and process expectations, not topic-specific defect acceptance criteria or repair deadlines.
CER Onshore Pipeline Regulations section 55
Canada audit and program-review context
Why review it: Useful when documentation, audit readiness, and program-level follow-through are part of the discussion.
What it helps with: Audit expectations for integrity, control-system, safety, and damage-prevention programs.
Caution: This is governance context, not a defect-by-defect response table.