SB 667 adds Section 7615 to the California Public Utilities Code and requires railroad corporations to install and operate wayside detector systems on tracks used by freight trains. The bill defines a wayside detector system (including hot wheel bearing detectors and other defect sensors), sets maximum spacing between detectors by carrier class, and creates a CPUC-driven approval and enforcement regime for carrier response plans.
The law ties train speed to detector coverage (capping speed where spacing isn’t compliant until a compliant detector issues a ‘no defects’ message), directs railroads to file a response plan via an expedited Tier 3 advice letter, and gives the California Public Utilities Commission authority to adopt technical standards, alerting and inspection procedures, and a minimum $25,000 penalty per violation. The measure exempts tracks owned or leased by short-line carriers that have a speed limit of 10 mph or less.
At a Glance
What It Does
The bill requires rail carriers to deploy and operate wayside detector systems along freight routes, mandates inclusion of hot wheel bearing detectors, and prescribes maximum spacing distances that vary by carrier class. It links train speed to detector coverage and requires carriers to submit a detector response plan for CPUC review.
Who It Affects
Class I, II, and III freight carriers operating in California, regional short-line owners of higher-speed track, freight train crews and dispatchers, shippers dependent on timely freight movement, and the California Public Utilities Commission which must write implementation rules and enforce compliance.
Why It Matters
SB 667 shifts more operational safety responsibility to rail carriers and the CPUC by codifying detector coverage and response expectations at the state level, creating nontrivial capital, operational and enforcement consequences for freight operations, and inserting California-specific safety requirements into an area shaped by federal law.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 667 creates a state-law baseline for wayside detection of freight-train defects. It defines a wayside detector system broadly to include devices that scan passing trains for hot wheel bearings, hot wheels, acoustically detected defective bearings, dragging equipment, shifted loads, low hoses, excessive rail temperature, and poor wheel condition.
The statute requires railroad corporations to install and operate such detectors on or adjacent to any track used by a freight train and mandates that each detector include a hot wheel bearing detector.
The bill imposes maximum spacing between consecutive detectors on a continuous track: 10 miles for class I carriers, 25 miles for class II, and 35 miles for class III. Where tracks fall short of those spacing standards, SB 667 constrains operations: a freight train operating on a segment between noncompliant detectors may not exceed 10 miles per hour.
The train may only increase speed above 10 mph after it passes a compliant detector that has transmitted a message indicating no defects.Operationalizing those rules requires railroad corporations to submit a wayside detector system response plan to the California Public Utilities Commission via an expedited Tier 3 advice letter process. The CPUC must adopt rules and processes that set minimum technical requirements for detectors, a process for carrier submission and commission review, procedures for delivering detector alerts to train crews, standards for post‑alert inspections, and obligations to ensure employee awareness of those standards.
The statute also directs the CPUC to adopt implementing rules that include a penalty of not less than $25,000 per violation.Finally, the statute narrows its reach: it does not apply to any track owned or leased by a class II or class III carrier that has a posted speed limit of 10 miles per hour or less. That exemption leaves low‑speed short-line operations outside the detector-and-speed regime the bill establishes for higher‑speed freight service.
The Five Things You Need to Know
Adds Section 7615 to the Public Utilities Code and defines “wayside detector system” to include hot wheel bearing detectors and a list of monitored defects.
Sets maximum spacing between wayside detectors on a continuous track at 10 miles for class I carriers, 25 miles for class II carriers, and 35 miles for class III carriers.
Imposes a 10 mph speed cap for freight trains operating on track segments lacking compliant detector spacing; trains may exceed 10 mph only after passing a compliant detector that has issued a ‘no defects’ message.
Requires railroad corporations to file a wayside detector system response plan with the CPUC via an expedited Tier 3 advice letter; directs the CPUC to adopt minimum technical standards, an approval process, crew alerting procedures, and post‑alert inspection standards.
Establishes a civil penalty floor of $25,000 per violation and exempts tracks owned or leased by class II or III carriers with a posted speed limit of 10 mph or less.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definition of wayside detector system
The statute begins by defining a wayside detector system as one electronic device or a linked series of devices that scan passing freight trains for defects. The definition is intentionally broad: it lists hot wheel bearings and wheels, acoustically detected bearing defects, dragging equipment, shifted loads, low hoses, excessive rail temperature, and poor wheel condition. That breadth gives the CPUC room to require different sensor types and data outputs when adopting minimum requirements.
Installation requirement and spacing by carrier class
This subdivision obligates railroad corporations to install and operate networks of wayside detectors on or adjacent to any track used by freight trains and mandates inclusion of hot wheel bearing detectors. It sets carrier‑class spacing maximums—10, 25, and 35 miles—placing the highest density requirement on class I carriers. Practically, that forces larger carriers to fill gaps along long corridors and requires smaller carriers to evaluate where their lines cross with higher‑class routes to ensure coverage or accept operational constraints.
Operational speed rule tied to detector coverage
Where a track segment between detector sites does not meet the statutory spacing, the bill caps freight speed at 10 mph. A train may only accelerate beyond 10 mph after it passes a compliant detector and receives a message that no defects were detected. That creates a binary operational trigger: detector outputs (and their timely, reliable delivery to crews) will determine whether trains run at normal speeds or are held to a low‑speed operational mode.
Response plan filing and CPUC rulemaking
Railroad corporations must submit a wayside detector response plan to the CPUC through an expedited Tier 3 advice letter. The CPUC is charged with adopting implementing rules that cover minimum detector technical requirements, the carrier submission and approval process, the mechanism for delivering alerts to train crews, standards for inspections after alerts, and employer obligations to ensure employee awareness of inspection standards. The subdivision also directs the CPUC to establish a penalty of at least $25,000 for violations, giving the commission both regulatory and enforcement responsibilities.
Exemption for very low‑speed short lines
The statute excludes tracks owned or leased by class II or class III carriers that have a posted speed limit of 10 miles per hour or less. That narrow exemption recognizes low‑speed yard, industrial, and terminal trackage where the operational and cost trade‑offs of detector deployment are different, but it leaves higher‑speed short lines and interchange mainlines squarely inside the new requirements.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Communities along freight corridors — earlier detection of hot bearings and dragging equipment reduces the risk of derailments, spills, and property damage, improving local public safety and environmental protection.
- Emergency responders and local governments — more reliable detection and notification can shorten response time and reduce the scale of incidents they must manage.
- Freight customers and shippers — consistent detector coverage should lower catastrophic equipment failures and associated service disruptions over time, improving supply‑chain reliability.
Who Bears the Cost
- Railroad corporations (class I–III) — must pay for capital installation, ongoing maintenance, integration of detector outputs with operations, and training for crew response to alerts; larger carriers face denser spacing requirements and higher near‑term capital outlays.
- Short‑line carriers with track above 10 mph — while very low‑speed lines are exempt, many class II/III carriers operating at higher speeds will need to invest in detectors or accept operational limits that slow traffic.
- California Public Utilities Commission — must design, review, and enforce technical standards and plans, creating administrative workload and potential need for technical expertise and inspection resources.
- Freight train crews and dispatchers — will need new operational procedures, must rely on real‑time alerts, conduct post‑alert inspections, and accept speed constraints that complicate scheduling and dispatch.
- Shippers and logistics managers — may face slower transit times or increased variability where detector coverage gaps force 10 mph operations or precautionary inspections.
Key Issues
The Core Tension
The central dilemma is safety versus operational and economic disruption: higher detection density and strict responses reduce the risk of catastrophic equipment failures but increase capital and operating costs, add procedural burdens for crews, and risk slowing freight flow through false positives or communication failures — a trade‑off that pits near‑term throughput and industry expense against longer‑term reductions in accident risk and public harm.
SB 667 intends to raise baseline detection and response expectations, but it leaves several implementation details unresolved. The statute defers key technical specifications to CPUC rulemaking (minimum detector performance, communication formats, latency tolerances, and which entity is responsible for installing and operating detectors where track rights are shared).
Those open questions will determine whether the measure yields quick defect detection or frequent operational disruption caused by false positives, communication failures, or ambiguous ‘no defect’ messaging.
The bill also sits in a complex federal environment. The Federal Railroad Safety Act promotes national uniformity in railroad safety and channels primary regulatory authority to federal agencies; however, it permits state action under certain conditions.
SB 667’s effectiveness and legal durability may hinge on how the CPUC frames its rules to avoid conflict with existing or future federal regulations and whether the federal government later issues covering regulations. Finally, the $25,000 minimum civil penalty is blunt; without clear definitions of what constitutes a violation and whether the penalty is per train, per day, per missing detector, or per incident, carriers face significant enforcement uncertainty and potential for large aggregate fines.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.