The SELF DRIVE Act Returns: Why Congress Is Taking Another Shot at AV Regulation

Congress is making its third attempt at federal autonomous vehicle legislation. The SELF DRIVE Act, introduced in February 2026, follows failed efforts in 2017 and 2021. This time feels different, not because the bill is perfect, but because the industry has fundamentally changed since the last attempt.

Autonomous vehicles are no longer experimental. They’re operating commercially in Phoenix, Austin, Los Angeles, and San Francisco. 34 states have enacted their own AV regulations, creating a patchwork that’s making nationwide deployment nearly impossible. And China is pulling ahead in every metric that matters: vehicle miles traveled, cumulative rides, and vehicles in operation.

The legislative window is narrow but real. The 2026 Surface Transportation Reauthorization creates a viable path forward, and the bill has rare bipartisan sponsorship from Rep. Bob Latta (R-OH) and Rep. Debbie Dingell (D-MI). For an industry facing regulatory fragmentation and international competition, this might be the moment federal AV policy actually happens.

What the SELF DRIVE Act Actually Does

The Safely Ensuring Lives Future Deployment and Research In Vehicle Evolution Act expands NHTSA’s authority over automated driving systems, focusing on Levels 4 and 5 automation. At its core, the bill does three things:

First, it establishes new Federal Motor Vehicle Safety Standards specifically for ADS-equipped vehicles. Manufacturers must submit “safety cases” demonstrating their systems meet safety requirements, a concept borrowed directly from aviation’s FAA certification process.

Second, it creates a National Automated Vehicle Safety Data Repository for crash and incident reporting, bringing transparency to an industry that’s operated largely without standardized public data.

Third, it preempts state regulations on ADS design, construction, and performance while leaving licensing, registration, and insurance requirements at the state level. This federal preemption is the bill’s most contentious provision, particularly for states like California that have invested heavily in their own AV frameworks.

Section 6 addresses cybersecurity, though modestly. It requires the Secretary of Commerce to review existing connected vehicle supply chain security rules (primarily focused on Chinese hardware and software), brief Congress within 180 days, and mandates that manufacturers develop written cybersecurity plans as part of their safety case submissions.

Why the Aviation Framework Makes Sense (And Where It Falls Short)

The safety case approach isn’t arbitrary. Aviation has one of the best safety records of any transportation sector, built on decades of rigorous, evidence-based certification. When the FAA evaluates aircraft systems, they’re looking at comprehensive documentation that demonstrates how autonomous systems behave under varied conditions.

For AVs, this makes intuitive sense. Like aircraft, these are complex autonomous systems where failures have safety implications. The difference is scale and environment.

The FAA has had nearly a century to build expertise in certifying autonomous systems and has mature cybersecurity frameworks woven into that certification process. NHTSA is still early in this journey. More critically, aircraft operate in highly regulated, controlled airspace. Autonomous ground vehicles will share roads with human drivers, pedestrians, cyclists, and vastly more unpredictable variables.

And here’s where the analogy starts to strain: aviation has robust, integrated cybersecurity standards like DO-326A and DO-356A built into safety certification. The SELF DRIVE Act borrows aviation’s safety case structure but leaves most of the cybersecurity framework behind.

The Industry Impact: Who Wins, Who Pushes Back

For OEMs and AV technology companies, federal preemption is a huge win. It ends the impossible task of meeting conflicting requirements across 34 different state frameworks. It creates a clear compliance path and enables true interstate deployment.

But it comes with costs. Safety case documentation is resource-intensive. The vague language around what constitutes “sufficient” or “appropriate” safety creates interpretation challenges. And for an industry already struggling with affordability and margin pressure, new compliance requirements hit hard.

Suppliers face their own challenges. Tier 1, 2, and 3 companies will need to demonstrate cybersecurity capabilities and supply chain transparency in ways many aren’t prepared for. For suppliers also working with, or as, defense contractors, this overlaps with CMMC requirements, creating dual compliance burdens.

The insurance industry is openly opposed to federal preemption, arguing they need access to vehicle data for risk assessment and that insurance regulation has historically been state-level. State regulators, especially in California, are watching closely to see how much authority they’re ceding to Washington.

For fleet operators and mobility services, the bill creates operational clarity but leaves critical questions unanswered: liability frameworks, insurance requirements, and incident response protocols remain ambiguous.

What Comes Next

Even supporters acknowledge the bill faces an uphill battle. Previous attempts at federal AV legislation failed in both 2017 and 2021, and this version will encounter similar resistance from state regulators, insurance industry groups, and lawmakers wary of federal overreach.

But unlike those earlier attempts, there’s a realistic legislative vehicle: the 2026 Surface Transportation Reauthorization could fold in AV provisions even if the standalone bill stalls. That creates a pathway forward that didn’t exist before.

If passed, the timeline is clear: the bill instructs DOT and NHTSA to finalize the rule by September 30, 2027, with a compliance date to be determined within that rulemaking. That’s a tight window for an agency that typically takes years to develop new vehicle safety standards.

The industry response will be measured. OEMs won’t publicly oppose safety-focused legislation, but expect quiet lobbying against prescriptive technical requirements. Startups and tech companies want regulatory clarity but fear barriers to entry. And everyone is watching to see if federal preemption survives negotiations with states that have invested heavily in their own frameworks.

The practical reality? Even with a September 2027 deadline, NHTSA’s rulemaking process involves notice-and-comment periods, technical working groups, and inevitable legal challenges. Manufacturers are already deploying under existing frameworks and won’t wait for federal clarity to continue. The bill creates a foundation, but the details that actually govern day-to-day operations won’t be settled quickly.

Progress over perfection might be the mantra, but the autonomous vehicle industry is about to find out if imperfect federal legislation with a 2027 deadline is better than no federal legislation at all.