On July 28, 2026, Senators Todd Young (R-Ind.) and Andy Kim (D-N.J.) introduced S.5150, the Safety and Accountability in Freight Enforcement (SAFE) Act. The bill targets “chameleon carriers,” trucking companies that close after safety violations, then reopen under new DOT registration numbers using the same drivers, equipment, addresses, and management to escape penalties and shed their safety records. S.5150 directs FMCSA to build an automated screening tool that cross-references ownership, driver identity, equipment, address, and insurance continuity to flag reincarnated entities at registration, and requires the Comptroller General to deliver a GAO study within one year on chameleon carrier prevalence, associated fatalities, and property damage.
That study requirement is also a regulatory admission: no reliable federal estimate of how often this happens currently exists. FMCSA’s SaferSys lookup shows only the current DOT number’s safety record. It does not link prior operator identities to a current entity. A self-insured shipper performing standard carrier vetting today has no practical way to distinguish a clean-history new entrant from a reincarnated problem operator.
Who it affects
Self-insured shippers, logistics companies, and employers carrying commercial auto SIRs in the $250,000 to $1 million range bear this exposure directly when they contract with outside carriers. A carrier with a history of out-of-service violations or equipment defects who closes and reopens under a new DOT number carries that risk forward while presenting a clean record in FMCSA’s public database. The self-insured entity that contracts with that carrier and documents a standard SaferSys check has performed what passes for current due diligence, and that standard is now legally insufficient.
The reserve mechanism
The May 14, 2026 Supreme Court decision in Montgomery v. Caribe Transport II, decided 9-0, held that state-law negligent hiring claims against freight brokers and shippers survive the Federal Aviation Administration Authorization Act’s preemption provision because they fall within the FAAAA’s own safety exception. The ruling resolved a longstanding circuit split and makes negligent carrier selection a live cause of action in every state court.
For self-insured fleet risk managers, this creates a two-layered reserve problem. First, frequency from chameleon carrier incidents does not appear in historical triangles under the carrier’s current DOT identity. The prior crash history was never linked to the current registration, so the self-insured’s loss data treats that carrier as a zero-history entrant. Second, severity is elevated: when a plaintiff can show that the contracting entity’s only due diligence was a SaferSys lookup of a DOT number with less than two years of operating history and no prior-entity cross-reference, punitive damages under a negligent hiring count are a realistic closing value. Neither the frequency uplift nor the punitive severity loading appears in development triangles built before Montgomery and before the SAFE Act’s admission that no baseline prevalence data exists.
For a full treatment of how contracted-carrier incidents feed into fleet auto liability IBNR assumptions, see Commercial Auto and Fleet IBNR for Self-Insured Trucking, Delivery, and Transit. The punitive severity dynamic parallels what a Texas jury imposed in the $49 million OPG Logistics verdict, where a carrier with no documented safety infrastructure drove a punitive award that dwarfed the underlying compensatory claim.
What this means for your next review
Ask your actuary whether your fleet development triangle separates owned-fleet losses from contracted-carrier losses. If the two books are blended, any frequency or severity uplift from chameleon carrier incidents is invisible in the data. Ask also whether your carrier vetting protocol is documented at a level that survives a Montgomery negligent-hiring claim: a SaferSys printout showing a DOT number with under three years of operating history and no prior-entity cross-reference will not establish due diligence under post-Montgomery scrutiny. Until FMCSA’s proposed automated screening tool creates a reliable continuity database, this vetting gap remains a reserve adequacy question that actuaries cannot quantify from current data.
Sources
- S.5150 SAFE Act bill text, GovInfo (introduced July 28, 2026)
- Senator Young press release on SAFE Act, July 28, 2026
- FreightWaves: New Senate bill targets chameleon carriers, July 28, 2026
- Montgomery v. Caribe Transport II, LLC, Supreme Court opinion (May 14, 2026)
- Faegre Drinker: Supreme Court Decides Montgomery v. Caribe Transport II (May 2026)
- FMCSA insurance filing requirements and SaferSys documentation