SAFE Act
- Sponsor
- Sen. Young, Todd [R-IN]
- Committees
- Commerce, Science, and Transportation Committee (primary)
- Last action
- Jul 28, 2026
Bottom line
The bill aims to enhance road safety and regulatory compliance by improving federal agencies' ability to identify and prevent unsafe motor carriers from operating under new identities to avoid accountability.
What it actually does
This bill mandates the Comptroller General of the United States to conduct a comprehensive study on 'chameleon carriers'—entities that evade safety regulations or penalties by operating under new identities. Concurrently, it requires the Federal Motor Carrier Safety Administration (FMCSA) to develop and implement an advanced automation tool to detect such carriers during the USDOT number registration process, including provisions for inter-agency data sharing and an appeals process for denied applications.
Proponents argue
Supporters argue that the SAFE Act is a critical step to close dangerous loopholes exploited by unsafe motor carriers, protecting the public from preventable accidents, fatalities, and injuries. They contend that leveraging advanced technology and comprehensive data analysis will significantly improve enforcement capabilities and ensure greater accountability within the freight industry.
Opponents contend
Potential critics might raise concerns about the accuracy and potential for false positives of an automated detection tool, which could unfairly burden legitimate businesses. They may also highlight privacy implications associated with extensive data sharing among multiple federal and state agencies, and question the overall cost and feasibility of developing such a sophisticated system within the specified timeframe.
The bill is relatively concise and straightforward, making it accessible for an informed reader to evaluate its core proposals within a reasonable timeframe.
Section 1
Short Title
This section formally establishes the short title of the Act as the 'Safety and Accountability in Freight Enforcement Act' or the 'SAFE Act.' This provides a concise and recognizable name for the legislation.
Supporters argue
Supporters argue that a clear and descriptive short title helps in public discourse and legislative tracking, immediately conveying the bill's purpose.
Critics contend
No specific opposition is typically raised against the naming of a bill, as it is standard legislative practice.
Tradeoffs
None.
Section 2
Definition of 'Chameleon Carrier'
This section provides a detailed definition of a 'chameleon carrier,' which includes motor carriers, brokers, freight forwarders, or their affiliates that operate under a new identity to avoid compliance, penalties, enforcement actions, negative compliance history, or to evade increased insurance premiums or cancellations due to safety records. This definition is crucial for identifying the target of the bill's enforcement efforts.
Section 3
Comptroller General Study on Chameleon Carriers
This section requires the Comptroller General of the United States to conduct a study within one year on chameleon carriers. The study must estimate their prevalence, the fatalities, serious injuries, and property damage they cause, analyze their evasion methods, assess existing Department of Transportation (DOT) enforcement capabilities and shortcomings, and provide legislative recommendations. The Comptroller General may collaborate with other entities for this study.
Section 4
FMCSA Advanced Automation Tool Development
This section mandates the FMCSA Administrator to develop, test, and implement an advanced automation tool within one year to detect chameleon carrier applications for USDOT numbers. The tool must identify specific characteristics indicating evasion, compile evidence, and provide automated decision support while retaining human responsibility for final determinations. It requires extensive data sharing agreements with various federal and state agencies and establishes an appeals process for denied applications, including notification of flagged factors and a 30-day redetermination period.
The detailed definition of 'chameleon carrier' includes specific criteria such as avoiding compliance with FMCSA orders, statutory requirements, civil penalties, enforcement actions, negative compliance history, or evading increased insurance premiums or cancellations by obtaining new insurance under a different identity or corporate form.
Section 2(3)
Why it matters:While definitions are standard legislative practice, the extensive and specific nature of this definition is foundational to the entire bill's scope and enforcement, making it more than just boilerplate. Its placement ensures legal precision but requires careful reading.
Case for: Supporters argue that this comprehensive definition is essential for providing a clear legal basis for identifying and prosecuting evasive carriers, ensuring that the automation tool and enforcement actions are precisely targeted.
Case against: Critics might argue that the breadth of the definition could potentially be interpreted to include legitimate business restructurings, leading to unintended scrutiny or administrative burdens for compliant entities.
Estimated impact: This definition directly determines which entities will be subject to the bill's new detection and enforcement mechanisms, potentially impacting thousands of motor carriers and related entities.
The bill requires the Administrator to enter into Memoranda of Understanding (MOUs) with a broad list of federal agencies—including the Departments of the Treasury, Justice, Homeland Security, Commerce, State, and the United States Postal Service—to share information needed for the advanced automation tool.
Section 4(b)(2)
Why it matters:The inclusion of such a wide array of agencies indicates a significant expansion of data sharing, which is crucial for the tool's effectiveness but also raises substantial privacy and inter-agency coordination questions. Its placement might be seen as standard detail for implementation, but its implications are far-reaching.
Case for: Proponents argue that comprehensive data sharing from diverse sources is absolutely necessary to effectively detect sophisticated chameleon carrier schemes that often involve financial, legal, and identity manipulations across various domains.
Case against: Privacy advocates and some industry groups might express concern over the broad scope of data sharing, citing potential risks of data breaches, misuse of information, or the aggregation of sensitive data without sufficient safeguards.
Estimated impact: This provision establishes a framework for unprecedented data sharing across numerous federal agencies to combat a specific type of fraud, potentially impacting the privacy of business and personal data on a national scale.
A 'Rule of Construction' explicitly states that nothing in the Act allows the final use of an automated decision made by the advanced automation tool for any relevant registration or the issuance of a USDOT number.
Section 4(f)
Why it matters:This provision is a critical check on the power of automation, ensuring human oversight for final decisions. Its placement might be intended to clarify the limits of the tool after its capabilities have been described, but it's a significant detail for due process.
Case for: Proponents emphasize that this rule is vital for maintaining due process and preventing legitimate businesses from being unfairly penalized by algorithmic errors, ensuring that human judgment remains paramount in critical regulatory decisions.
Case against: Some might argue that requiring human review for every flagged application could reduce the efficiency gains expected from an advanced automation tool, potentially leading to bottlenecks in the registration process.
Estimated impact: This rule ensures that the automation tool serves as a decision support system rather than a final decision-maker, preserving human accountability and appeal rights for all applicants.