RegulusPipeline research

Search Updates Timeline Research Projects Coverage Profile

Open research interfaceRegulatory evidence, ready for agents.

Public, read-only access. No account or API key required.

Start herellms.txt InstructionsLLM guide API contractOpenAPI WorkflowAgent skill ConnectMCP setup

Regulus · Pipeline research

About Terms Privacy

Source-first · Read-only · Citation-ready

49 CFR 198.61 - How is a State notified of PHMSA's final decision? | Regulus

Add to project

Projects

No projects yet

Export Official source

Regulation documentation

49 CFR Part 198

Location

titleTitle 49 — Transportation subtitleSubtitle B — Other Regulations Relating to Transportation chapterChapter I — Pipeline and Hazardous Materials Safety Administration, Department of Transportation subchapterSubchapter D — Pipeline Safety partPart 198 subpartSubpart D—State Damage Prevention Enforcement Programs

7 sections

Subpart A—General2

§ 198.1Scope.§ 198.3Definitions.

Subpart B—Grant Allocation2

§ 198.11Grant authority.§ 198.13Grant allocation formula.

Subpart C—Adoption of One-Call Damage Prevention Program5

§ 198.31Scope.§ 198.33[Reserved]§ 198.35Grants conditioned on adoption of one-call damage prevention program.§ 198.37State one-call damage prevention program.§ 198.39Qualifications for operation of one-call notification system.

Subpart D—State Damage Prevention Enforcement Programs7

§ 198.51What is the purpose and scope of this subpart?§ 198.53When and how will PHMSA evaluate State damage prevention enforcement programs?§ 198.55What criteria will PHMSA use in evaluating the effectiveness of State damage prevention enforcement programs?§ 198.57What is the process PHMSA will use to notify a State that its damage prevention enforcement program appears to be inadequate?§ 198.59How may a State respond to a notice of inadequacy?§ 198.61How is a State notified of PHMSA's final decision?§ 198.63How may a State with an inadequate damage prevention enforcement program seek reconsideration by PHMSA?

Browse regulation

Subpart A—General2

§ 198.1Scope.§ 198.3Definitions.

Subpart B—Grant Allocation2

§ 198.11Grant authority.§ 198.13Grant allocation formula.

Subpart C—Adoption of One-Call Damage Prevention Program5

§ 198.31Scope.§ 198.33[Reserved]§ 198.35Grants conditioned on adoption of one-call damage prevention program.§ 198.37State one-call damage prevention program.§ 198.39Qualifications for operation of one-call notification system.

Subpart D—State Damage Prevention Enforcement Programs7

§ 198.51What is the purpose and scope of this subpart?§ 198.53When and how will PHMSA evaluate State damage prevention enforcement programs?§ 198.55What criteria will PHMSA use in evaluating the effectiveness of State damage prevention enforcement programs?§ 198.57What is the process PHMSA will use to notify a State that its damage prevention enforcement program appears to be inadequate?§ 198.59How may a State respond to a notice of inadequacy?§ 198.61How is a State notified of PHMSA's final decision?§ 198.63How may a State with an inadequate damage prevention enforcement program seek reconsideration by PHMSA?

Related 2 Definitions History 12 Authority 14

RegulationsTitle 49Subtitle BChapter ISubchapter DPart 198Subpart D—State Damage Prevention Enforcement Programs49 CFR 198.61

Regulationcurrent

49 CFR 198.61

How is a State notified of PHMSA's final decision?

Current as of 2026-08-18 Government source

eCFR editorial compilationAuthoritative but unofficial

1 passages

PHMSA will issue a final decision on whether the State's damage prevention enforcement program has been found inadequate in accordance with 49 CFR 190.5.#

Previous§ 198.59 Next§ 198.63

Related 2 Definitions History 12 Authority 14 Community

Only explicit, source-backed relationships are shown.

Rulemaking2

80 FR 43836

Pipeline Safety: Pipeline Damage Prevention Programs

198.61 · cited in rulemaking

77 FR 19800

Pipeline Safety: Pipeline Damage Prevention Programs

198.61 · cited in rulemaking

Ask the corpus

Claims link back to retrieved source passages.

Record details

Retrieved: Aug 20, 2026
Version: 2026-08-18

c2a2bdffc3bc43b981…