S. 2660 (119th)Bill Overview

Modern Risk Detection Act of 2025

Transportation and Public Works|Transportation and Public Works
Cosponsors
Support
Republican
Introduced
Aug 1, 2025
Discussions
Bill Text
Current stageCommittee

Read twice and referred to the Committee on Commerce, Science, and Transportation.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

The bill, titled the Modern Risk Detection Act of 2025, adds a subsection to 49 U.S.C. § 60102 directing the Secretary (of Transportation) to ensure that standards under that chapter allow the use of risk-based approaches, concepts, or principles to the maximum extent practicable. In short, it instructs the Department to permit owners and operators of certain pipeline facilities to use risk‑based methods when complying with applicable standards.

Why people may split

Whether the bill’s broad mandate will improve safety by enabling data-driven prioritization (centrists/conservatives) versus whether it will be used to weaken prescriptive protections (progressive).

Watch point

Relative to its intended legislative type, this bill is a concise statutory amendment that clearly inserts a directive into the U.S. Code to permit risk-based approaches, but it provides very limited operational detail.

The bill, titled the Modern Risk Detection Act of 2025, adds a subsection to 49 U.S.C. § 60102 directing the Secretary (of Transportation) to ensure that standards under that chapter allow the use of risk-based approaches, concepts, or principles to the maximum extent practicable.

In short, it instructs the Department to permit owners and operators of certain pipeline facilities to use risk‑based methods when complying with applicable standards.

The text is brief and does not define “risk-based” or specify additional enforcement, funding, or reporting requirements.

Passage40/100

Content-wise this is a low-cost, narrowly focused statutory clarification that could gain support from industry and administrative reform proponents; its vagueness and potential framing as a deregulatory rollback of safety rules create an opposition vector from safety advocates and some lawmakers. The bill's simple structure helps its prospects, but absence of compromise features, cost estimates, or clarifying definitions and any procedural hurdles in the Senate temper the likelihood.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a concise statutory amendment that clearly inserts a directive into the U.S. Code to permit risk-based approaches, but it provides very limited operational detail.

Contention55/100

Whether the bill’s broad mandate will improve safety by enabling data-driven prioritization (centrists/conservatives) versus whether it will be used to weaken prescriptive protections (progressive).

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Likely helpedCities · Federal agencies

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Potential benefitIncreases regulatory flexibility for pipeline owners/operators by allowing risk-based, performance-oriented compliance…
  • Potential benefitEncourages adoption of modern risk-management tools (data analytics, predictive maintenance, prioritization of high-ris…
  • Potential benefitCould spur innovation and investment in condition-monitoring and risk-detection technology by creating a regulatory fra…
Likely burdened
  • Potential burdenCould weaken prescriptive safety protections if risk-based approaches are used to justify reduced inspections, mitigati…
  • CitiesEffectiveness of risk-based approaches depends on data quality, analytic capacity, and proper implementation; critics m…
  • Federal agenciesMay increase regulatory complexity and oversight burden for the federal regulator, which must evaluate and approve dive…
03 · Why people split

Why the argument around this bill splits.

Whether the bill’s broad mandate will improve safety by enabling data-driven prioritization (centrists/conservatives) versus whether it will be used to weaken prescriptive protections (progressive).
Progressive30%

A mainstream progressive would approach this bill cautiously.

They would acknowledge that modern, data-driven risk management can improve safety and target resources, but would be concerned that the open-ended instruction to allow risk-based approaches could be used to weaken prescriptive safety standards or reduce inspections.

They would want clear guardrails, definitions, transparency, and maintenance of minimum safety requirements to prevent regulatory backsliding.

Likely resistant
Centrist60%

A pragmatic moderate would see this as a relatively narrow, technical change to encourage modern, risk-informed compliance where appropriate.

They would like the potential efficiency gains from letting operators use data-driven approaches but would worry about ambiguity and uneven implementation without guidance.

They would rate the bill as promising if accompanied by clearly defined standards, oversight, and evidence that public safety will not be diminished.

Split reaction
Conservative90%

A mainstream conservative would generally view this bill favorably as it increases regulatory flexibility and allows operators to use modern, risk-based methods rather than rigid prescriptive rules.

They would see it as reducing unnecessary compliance burdens, encouraging innovation, and enabling more efficient allocation of resources.

They would be inclined to support it, though some conservatives might prefer even stronger language guaranteeing deference to industry-developed risk models and clearer limits on regulatory overreach.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood40/100

Content-wise this is a low-cost, narrowly focused statutory clarification that could gain support from industry and administrative reform proponents; its vagueness and potential framing as a deregulatory rollback of safety rules create an opposition vector from safety advocates and some lawmakers. The bill's simple structure helps its prospects, but absence of compromise features, cost estimates, or clarifying definitions and any procedural hurdles in the Senate temper the likelihood.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • The bill's text is brief and does not define which 'certain pipeline facilities' are covered or how the Secretary should balance risk-based approaches against prescriptive requirements; that ambiguity affects implementation and stakeholder reactions.
  • No cost estimate or regulatory impact analysis is included in the text; uncertainty about whether the change would materially reduce costs or affect safety could influence committee and floor support.
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Whether the bill’s broad mandate will improve safety by enabling data-driven prioritization (centrists/conservatives) versus whether it wil…

Content-wise this is a low-cost, narrowly focused statutory clarification that could gain support from industry and administrative reform p…

Unlocked analysis

Relative to its intended legislative type, this bill is a concise statutory amendment that clearly inserts a directive into the U.S. Code to permit risk-based approaches, but it provides very limited operational detail.

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis