Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

AZ SB1417: Autonomous vehicles; safety; data

Dead/Failed Arizona · 2026 session

Last verified Oct 10, 2026 · official bill text

SB1417 · where it stands

This bill did not become law (dead/failed) · last action Jan 28, 2026.

What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

Arizona's SB 1417 (2026) would have amended the autonomous vehicle chapter (A.R.S. 28-9701 et seq.) so that a fully autonomous vehicle could run without a human driver only if its operator submitted a law enforcement interaction plan, a written compliance statement, proof of at least $5,000,000 in liability coverage per occurrence, update notices and quarterly safety reports. It was held in Senate committees with no action and died when the 2026 session ended June 13, 2026.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

None: the bill died and never became law. It would have required operators of driverless vehicles to file plans and quarterly reports, carry $5,000,000 per occurrence in coverage and report updates.

Key provisions

  1. Would require, for a fully autonomous vehicle without a human driver, a law enforcement interaction plan to the departments of transportation and public safety and a written statement on federal standards, minimal risk condition, traffic-law compliance, title, registration, insurance and a department identifier
  2. Would require proof of an active liability policy or financial responsibility of not less than $5,000,000 per occurrence
  3. Would require notice within ten days of any software or mapping update that materially changes operational behavior, with an updated compliance statement
  4. Would require a quarterly safety performance report covering miles driven in Arizona, collisions (including with vulnerable road users), near-miss events and software or map updates affecting detection
  5. Would let the department immediately issue a cease and desist letter if the plan or statement is not submitted
  6. Would require transportation department rules on safety data reporting formats, independent third-party performance audits and fleet identification and emergency responder access, and a memorandum of understanding with public safety
  7. Held in Senate committees with no action; died June 13, 2026

Latest legislative action

Jan 28, 2026. Senate read second time; died when the 57th Arizona Legislature's 2026 regular session ended June 13, 2026

Sponsors (showing 5 of 28)

NameRole
Primary
Primary
Primary
Primary
D Primary

Topics and industries

Related topics

Affected industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error