BUILD America 250 Creates First Federal AV Truck Deployment Framework
House Transportation and Infrastructure Committee embeds self-driving truck policy in infrastructure reauthorization: no standalone rulemaking, no FMCSA docket yet.
What federal rules now govern autonomous truck deployment?
The House Transportation and Infrastructure Committee included a federal policy framework regulating the deployment of self-driving trucks in BUILD America 250, the infrastructure reauthorization package. This marks the first time Congress has written autonomous-vehicle deployment rules directly into highway legislation rather than leaving the work to FMCSA rulemaking.
No docket number exists yet. No effective date is public. The committee embedded the framework in the broader bill, which means carriers and technology developers will not see standalone Federal Register notices or comment periods for the autonomous-truck provisions. The regulatory path is legislative, not administrative.
Why this matters for carriers running or testing autonomous equipment
Federal Motor Carrier Safety Administration (FMCSA) has historically regulated commercial motor vehicle safety through the rulemaking process: notice, comment, final rule, effective date. Autonomous-truck deployment has lived in a gray zone: NHTSA (National Highway Traffic Safety Administration) handles vehicle design and crashworthiness; FMCSA handles the carrier, the driver, and hours-of-service compliance. Neither agency has published a comprehensive rule governing how a carrier obtains operating authority to run a truck with no human driver, what the CSA (Compliance, Safety, Accountability) scoring implications are when software makes the driving decisions, or how an autonomous system logs duty status.
BUILD America 250 changes that by writing the framework into statute. Carriers testing autonomous trucks in states with permitting programs, California, Arizona, Texas, Florida, have operated under state rules and voluntary federal guidance. A federal framework means uniform compliance obligations across state lines, which is the core promise of interstate operating authority. It also means carriers will face audits against statutory language, not voluntary best practices.
What the framework likely covers
The source does not detail the provisions. Based on prior congressional discussion of autonomous-truck policy, a federal framework typically addresses:
- Operating authority requirements, whether a carrier running autonomous trucks needs a separate MC number, a special endorsement on an existing USDOT registration, or new insurance minimums beyond the standard BMC-91 cargo bond and $750,000 liability floor.
- Safety fitness determination: how FMCSA scores a carrier when the "driver" is software. CSA percentiles are built on driver behavior: speeding, hard braking, hours-of-service violations, vehicle maintenance. An autonomous system does not have an MVR (motor vehicle record), cannot be drug-tested under 49 CFR Part 40, and does not fill out a paper log. The framework must define what gets scored and how.
- ELD compliance, electronic logging devices (ELDs) record duty status for human drivers under 49 CFR 395.8. An autonomous truck has no driver subject to the 11-hour driving limit or the 14-hour on-duty window. The framework must clarify whether autonomous systems file electronic records, and if so, under what standard.
- New-entrant safety audits, FMCSA conducts a safety audit within 12 months of a carrier's first USDOT registration. The audit verifies that the carrier has a controlled-substances testing program, driver qualification files, and a system for annual MVR checks. None of those apply to a truck with no human operator. The framework must define what an auditor reviews.
- Crash reporting and liability: who is the "driver" in a crash report when software was in control? How does the carrier demonstrate that the autonomous system was functioning as designed at the time of the crash? The framework must establish recordkeeping and disclosure obligations.
How this differs from FMCSA rulemaking
When FMCSA writes a rule, the agency publishes a Notice of Proposed Rulemaking (NPRM) in the Federal Register, opens a comment period (typically 60 to 90 days), reviews public input, and publishes a final rule with an effective date. Carriers and industry groups can submit technical comments, cost analyses, and operational objections. The final rule includes a preamble explaining how the agency responded to major comments.
A statutory framework in BUILD America 250 skips that process. The House committee wrote the language. The full House and Senate will vote on the bill. If it becomes law, the framework is immediately binding. FMCSA will issue guidance and enforcement bulletins interpreting the statute, but the core obligations are set by Congress, not by the agency's rulemaking record.
This matters for carriers because statutory language is harder to change than regulatory language. If a compliance obligation in the framework proves unworkable, for example, if the statute requires autonomous trucks to file ELD records in a format that does not exist, the fix requires an amendment to the law, not a petition for reconsideration at FMCSA.
What carriers testing autonomous trucks should do now
Carriers running pilot programs with autonomous-truck developers should:
- Review state permits against federal framework language, once the bill text is public, compare your state-level operating permits to the federal requirements. If the federal framework imposes stricter insurance minimums, recordkeeping obligations, or safety-fitness standards, you will need to comply with both.
- Audit your USDOT registration and operating authority, if the framework requires a separate endorsement or a new class of operating authority for autonomous operations, you will need to file an update with FMCSA. The MCS-150 (biennial update) form does not currently have a field for autonomous-vehicle operations. Expect FMCSA to issue a revised form or a supplemental filing requirement.
- Prepare for new-entrant-style audits, even if your carrier has held an MC number for years, the first deployment of an autonomous truck may trigger a safety audit under the new framework. Gather documentation showing how your autonomous system complies with the framework's safety-fitness standards.
- Track CSA implications, if the framework assigns CSA percentile points to autonomous-system events (hard braking, lane departures, following distance), those points will affect your safety rating and your eligibility for certain freight contracts. Review your telematics data to understand what events the system is logging and how those events map to CSA BASICs (Behavior Analysis and Safety Improvement Categories).
What happens next
BUILD America 250 must pass the full House, pass the Senate, and be signed by the President before the autonomous-truck framework becomes law. The timeline is uncertain. Infrastructure reauthorization bills typically take months to move through both chambers, and the Senate may amend the autonomous-truck provisions.
FMCSA will not publish a docket or open a comment period unless the statute directs the agency to write implementing regulations. Carriers should monitor the bill's progress through Congress and prepare to comply with the framework as soon as it is enacted. Unlike a traditional FMCSA rule, there may be no advance notice before the effective date.
