US Regulatory Landscape for Autonomous Vehicles

The regulatory landscape governing autonomous vehicles (AVs) in the United States is fragmented across federal agencies, 50 state legislatures, and a growing body of voluntary industry standards — with no single comprehensive federal statute yet enacted. This page maps the active jurisdictional structure, identifies the primary legal instruments and rulemaking frameworks, classifies the distinct regulatory tiers that apply to different vehicle types and deployment contexts, and establishes the decision boundaries that determine which body holds authority in a given scenario. For practitioners, researchers, and service seekers operating in this sector, understanding this framework is a prerequisite to assessing compliance exposure and deployment feasibility.

Definition and scope

Autonomous vehicles, as classified by the SAE International J3016 standard, span six levels of driving automation (Level 0 through Level 5), ranging from no automation to full self-driving capability with no human fallback requirement. The regulatory scope addressed here covers Level 2 through Level 5 systems operating on public roads — the range where federal and state safety authority becomes operative. Level 1 and Level 2 systems (partial and conditional automation) remain largely subject to existing Federal Motor Vehicle Safety Standards (FMVSS) administered by the National Highway Traffic Safety Administration (NHTSA). Level 3 through Level 5 systems, where the automated driving system (ADS) assumes primary or full control, have generated the most active regulatory contention because existing FMVSS were written for human-operated vehicles.

The NHTSA AV policy framework distinguishes between Automated Driving Systems (ADS) — software and hardware enabling SAE Level 3–5 — and Advanced Driver Assistance Systems (ADAS) at Level 1–2. This distinction is not merely taxonomic: it determines whether a manufacturer must petition for an exemption from specific FMVSS provisions, such as the requirement for a steering wheel and pedal controls. The autonomous vehicle regulatory landscape at the federal level is further shaped by the absence of a dedicated AV statute, meaning NHTSA currently operates under authority delegated by the National Traffic and Motor Vehicle Safety Act (49 U.S.C. § 30101 et seq.).

State-level authority fills the gap federal law leaves. As of the 2023 legislative session, at least 29 states and the District of Columbia had enacted AV-related legislation or issued executive orders (NCSL Autonomous Vehicles State Bill Tracking Database), addressing licensure, liability, insurance minimums, and operational design domain (ODD) restrictions. California, Arizona, and Texas represent three of the most developed state-level frameworks, with California's Department of Motor Vehicles maintaining distinct permit categories for testing with a driver, testing without a driver, and commercial deployment.

How it works

The regulatory mechanism for AVs operates through three parallel tracks:

  1. Federal safety standards and exemption petitions: NHTSA administers FMVSS under 49 C.F.R. Parts 500–599. Manufacturers deploying vehicles that deviate from human-driver assumptions — for example, a driverless vehicle with no steering wheel — must petition NHTSA for an exemption under 49 U.S.C. § 30113. NHTSA may grant exemptions for up to 2,500 vehicles per manufacturer per year for testing and limited commercial deployment, a cap that constrains scaled rollout. The agency also issues Automated Vehicle Guidance documents (AV 1.0 through AV 4.0) and the NHTSA Voluntary Safety Self-Assessment framework, which provides a 12-element disclosure structure for ADS developers.

  2. State operational licensing and permitting: States regulate the operational side — who may test, where, under what conditions, and with what insurance minimums. California requires AV testing permits issued by the DMV, with separate categories for manufacturer testing, driverless testing, and autonomous delivery. Arizona uses a governor's executive order model (Executive Order 2018-04) authorizing ADS-equipped vehicle testing on public roads with fewer prescriptive permit requirements. Texas HB 1791 (2017) established that no permit is required for ADS operation if the vehicle meets applicable federal standards and carries $500,000 in liability coverage.

  3. Standards body frameworks: SAE International, the IEEE Standards Association, and the American Association of Motor Vehicle Administrators (AAMVA) publish technical and operational standards that inform rulemaking without carrying direct legal force. NHTSA's guidance documents explicitly reference SAE J3016 as the definitional baseline for automation levels. NIST's AI Risk Management Framework (AI RMF), published in January 2023, applies to AI systems broadly and is increasingly cited in ADS safety assessments.

The levels of autonomy classification directly determines which track — or combination of tracks — applies to a given vehicle configuration.

Common scenarios

Scenario 1: Commercial robotaxi deployment in a dense urban area
A robotaxi operator seeking to launch a fare-paying, driverless service in San Francisco must hold a California DMV Autonomous Vehicle Deployment Permit and a separate California Public Utilities Commission (CPUC) Transportation Charter-Party Carrier permit. The operator must also comply with the CPUC's AV passenger service rules, which require an incident reporting protocol and specify minimum data retention periods. This dual-agency requirement — DMV plus CPUC — is specific to California and illustrates how state regulatory structures can layer obligations.

Scenario 2: Long-haul ADS-equipped freight trucking across state lines
An ADS freight operator running interstate routes encounters a patchwork: federal FMVSS and Federal Motor Carrier Safety Administration (FMCSA) hours-of-service and inspection regulations apply uniformly, but each state traversed may impose its own operational requirements. FMCSA has not yet issued ADS-specific rules for commercial motor vehicles as of the 2024 regulatory calendar, leaving operators to map compliance state by state. The autonomous systems safety standards applicable to commercial freight ADS are still largely voluntary at the federal level.

Scenario 3: Low-speed autonomous delivery vehicles (LSADVs) on sidewalks or bike lanes
Devices such as sidewalk delivery robots, operating at speeds below 20 mph and outside traditional roadways, fall outside NHTSA's vehicle jurisdiction entirely. Regulation defaults to municipal ordinances. At least 23 states had enacted LSADV-specific legislation as of 2023, with Pennsylvania's Act 130 of 2016 serving as one of the earliest enabling frameworks.

Decision boundaries

The critical jurisdictional and classification boundaries that determine applicable regulatory obligations are:

Federal vs. state authority: NHTSA holds exclusive authority over vehicle design and performance standards (preemption under 49 U.S.C. § 30103). States retain authority over driver licensing, vehicle registration, traffic laws, and operational conditions. A state cannot mandate a steering wheel if NHTSA grants an exemption, but it can restrict where and when that vehicle may operate.

ADS vs. ADAS classification: A Level 2 ADAS system — where the human driver remains in the loop and liable — faces no FMVSS exemption requirement. A Level 4 ADS with no human fallback triggers the exemption petition process and the NHTSA Voluntary Safety Self-Assessment disclosure obligations.

On-road vs. off-road vs. sidewalk operations: Vehicles operating exclusively on private property or closed courses are not subject to FMVSS or state DMV permitting. Sidewalk devices are not federally regulated as motor vehicles. Public road operation is the threshold that activates the full regulatory stack.

Commercial passenger service vs. personal use: The addition of commercial passenger service triggers additional licensing bodies — state PUC or equivalent — beyond the DMV permitting layer. This distinction separates robotaxi deployments from privately operated autonomous personal vehicles.

For a broader orientation to the federal regulatory structures governing autonomous systems outside the road vehicle context — including unmanned aerial systems and industrial robotics — the Autonomous Systems Authority provides the reference structure within which AV-specific regulation sits.

The Robotics Architecture Authority covers the technical and systems-design dimensions of autonomous vehicle platforms, including sensor integration architectures, real-time operating system frameworks, and the hardware-software interface standards that inform how safety-critical ADS components are designed and certified. Its coverage is directly relevant to practitioners who need to align technical architecture decisions with the NHTSA safety self-assessment elements.

Practitioners assessing compliance exposure should also cross-reference the federal regulations governing autonomous systems reference, which maps rulemaking activity across NHTSA, FMCSA, and other agencies with AV-adjacent jurisdiction.

References

📜 5 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

Explore This Site

Services & Options Key Dimensions and Scopes of Technology Services Tools & Calculators Website Performance Impact Calculator FAQ Technology Services: Frequently Asked Questions Overview Technology Services: What It Is and Why It Matters