SF4010 (Legislative Session 94 (2025-2026))
Certain autonomous vehicles regulations provision
Related bill: HF3513
AI Generated Summary
Purpose
This bill seeks to regulate the use of autonomous vehicles in Minnesota. It defines key terms, sets rules for when automated driving systems can operate (including driverless operation with official permission), requires safety and financial responsibilities, and creates rules for on‑demand autonomous vehicle networks. It also aims to create a uniform statewide framework by preempting conflicting local rules.
Key Definitions
- Automated driving system (ADS): the hardware and software capable of performing the entire dynamic driving task on a sustained basis.
- Autonomous vehicle: a motor vehicle equipped with an ADS designed to function as a level 4 or 5 system (per SAE J3016).
- Dynamic driving task (DDT): real-time driving functions such as steering, acceleration, monitoring the road, object detection, planning, and signaling—not including trip planning or selecting destinations.
- Dynamic driving task fallback: the process by which a driver or ADS returns to a minimal risk condition after a failure or exit from the intended driving domain.
- Minimal risk condition (MRC): a safe state a vehicle can reach to reduce crash risk if the trip cannot be completed.
- First responder interaction plan: procedures for responders on how to interact with an autonomous vehicle, including communication and safety steps.
- Operational design domain (ODD): the specific conditions under which an ADS is designed to function (environment, geography, time of day, etc.).
- On-demand autonomous vehicle network: a software-enabled system that dispatches autonomous vehicles to transport passengers or goods.
- SAE J3016: the 2021 revision of the standard taxonomy for driving automation terms.
- First responder plans, vehicle inspections, signage requirements, and financial responsibility standards are all tied to these definitions.
Main Provisions
Definitions added to law
- Adds Subdivisions for Automated Driving System, Autonomous Vehicle, Dynamic Driving Task, and related terms to Minnesota Statutes.
Operation without a human driver (driverless operation)
- An autonomous vehicle may operate without a human driver only if: (a) it meets the ADS/vehicle requirements, (b) the operator has authorization from the commissioner, and (c) a first responder interaction plan is provided to the commissioner and the DPS.
- Applications for driverless operation require identifying information for the applicant and the vehicle(s) and a statement certifying compliance with the ADS requirements and the first responder plan.
- The commissioner must approve or deny a complete application within 30 days.
- Authorizations do not expire on their own and remain active unless suspended, revoked, or canceled; updates must be provided within 30 days of material changes; failure to update can trigger suspension.
- A human driver may still operate an autonomous vehicle if they are present and in control.
Driver and licensure concepts
- When the ADS is engaged with no human present, the ADS is treated as the driver for purposes of traffic laws; the operator can be cited if noncompliant.
- An autonomous vehicle with authorization may be considered licensed to operate under state law if authorized.
Collision and reporting
- If a collision occurs, the human driver must follow existing reporting rules; an autonomous vehicle without a human driver must stay on the scene as required by law and report the collision as appropriate.
Financial responsibility and insurance
- Vehicle owners must carry proof of financial responsibility at least at a specified minimum.
- Operators using the ADS must maintain financial responsibility of at least $1,000,000 for third‑party liability, with requirements to cover basic economic loss benefits and uninsured motorist benefits as applicable.
- Financial responsibility can be satisfied by a lawfully issued insurance policy or eligible surplus lines policy, and is not automatically increased just because the vehicle uses an ADS.
Dynamic driving task and safety basics
- Reiterates that the ADS must perform the entire dynamic driving task and must fail to a minimal risk condition if it cannot complete the task or exits its operational domain.
- Requires the vehicle to operate in compliance with Minnesota traffic and safety laws, unless an exemption is granted.
- Federal certifications and safety standards (and any exemptions) must be acknowledged as applicable.
On-demand autonomous vehicle networks
- Such networks may transport passengers or goods in Minnesota if they meet the specified sections.
- They cannot accept traditional street hail requests and must disclose fare methods in advance.
- Must provide ride receipts listing origin, destination, time/distance, and total fare after rides.
- Vehicles must display distinctive signage or emblems at all times while active.
- Pre-service inspections are required, with annual inspections thereafter; inspection records must be kept for three years.
- If wheelchair accessibility is not available, networks must direct riders to accessible providers when reasonably possible.
Not a common carrier
- On-demand networks are not considered common carriers, and Chapter 221’s provisions do not apply to these networks.
Commercial autonomous vehicles and vehicle standards
- Autonomous vehicles that are also commercial motor vehicles must follow CMV rules except for provisions that only apply to human drivers.
- For CMVs, the ADS components may be treated as parts like a mirror for measurement purposes.
Equipment standards for driverless operation
- Vehicles designed to operate exclusively without a human driver are not subject to motor vehicle equipment laws that relate to human-driver operation.
Governing authority and local preemption
- State law governs autonomous vehicles, ADS, and on-demand networks.
- Local ordinances conflicting with state law are preempted.
- Local entities cannot impose extra licensing, permitting, taxes, or fees specific to autonomous operations (with limited airport-related allowances for fees and staging areas).
Significance and Expected Impacts
- Creates a statewide framework for driverless operation and autonomous vehicle networks.
- Establishes a clear license/authorization process for operating autonomous vehicles without a human driver.
- Sets financial responsibility requirements to address liability and protection for the public.
- Introduces standardized safety practices, including first responder interaction planning and routine vehicle inspections.
- Enables on-demand autonomous vehicle networks while maintaining consumer protections like fare disclosure and receipts.
- Preempts local laws to promote uniform statewide adoption, while permitting airport-specific considerations.
How It Changes Existing Law
- Adds new definitions and subdivisions to clarify ADS, autonomous vehicles, dynamic driving task, fallback, and related terms.
- Establishes a formal authorization regime for driverless operation, including plans for first responders and ongoing updates.
- Introduces a mandatory $1,000,000 minimum for third-party liability for autonomous vehicle operation.
- Creates specific rules for on-demand autonomous vehicle networks, including signage, inspections, and accessibility considerations.
- Preempts local control by mandating state-wide standards and limiting local licensing or surcharge authorities for autonomous operations.
Practical Considerations
- Companies aiming to deploy driverless autonomous vehicles must prepare an authorization package and a first responder interaction plan.
- Operators must ensure robust financial responsibility coverage and be ready for regulatory inspections and record-keeping.
- Local governments will need to align with the statewide framework rather than crafting separate autonomous vehicle rules.
Potential Areas for Further Oversight
- Details of the first responder interaction plan content and the exact process for plan approval.
- How “material changes” to operator information are defined and managed.
- Specifics on how the $1,000,000 financial responsibility floor interacts with different insurance products and state requirements.
- Implementation timelines and exemptions for airports or special jurisdictions.
Relevant Terms - automated driving system - autonomous vehicle - dynamic driving task - dynamic driving task fallback - minimal risk condition - first responder interaction plan - operational design domain - on-demand autonomous vehicle network - SAE J3016 - authorization to operate without a human driver - proof of financial responsibility - third-party liability - collision reporting - distinctive signage - vehicle inspections - not a common carrier - preemption - traffic and motor vehicle safety laws - commercial autonomous vehicle - wheelchair accessibility (and alternatives)
Bill text versions
- Introduction PDF PDF file
Upcoming committee meetings
- Transportation on: March 25, 2026 15:00
Past committee meetings
- Transportation on: March 18, 2026 15:00
Actions
| Date | Chamber | Where | Type | Name | Committee Name |
|---|---|---|---|---|---|
| March 02, 2026 | Senate | Action | Introduction and first reading | ||
| March 02, 2026 | Senate | Action | Referred to | Transportation |
Citations
[
{
"analysis": {
"added": [
"Automated driving system means the hardware and software that are collectively capable of performing the entire dynamic driving task on a sustained basis regardless of whether the dynamic driving task is limited to a specific operational design domain."
],
"removed": [],
"summary": "Adds Automated driving system definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.3b"
},
{
"analysis": {
"added": [
"Autonomous vehicle means a motor vehicle equipped with an automated driving system designed to function as a level 4 or 5 system under SAE J3016."
],
"removed": [],
"summary": "Adds Autonomous vehicle definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.3c"
},
{
"analysis": {
"added": [
"Dynamic driving task means the realtime operational and tactical functions required to operate a vehicle in onroad traffic including but not limited to lateral and longitudinal motion control, monitoring the driving environment, object and event detection, recognition, classification and response, execution, maneuver planning, and enhancing conspicuity via lighting, signaling, and gesturing."
],
"removed": [],
"summary": "Adds Dynamic driving task definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.24a"
},
{
"analysis": {
"added": [
"Dynamic driving task fallback means (1) the response by the person or human driver to perform the dynamic driving task or achieve a minimal risk condition after a failure, exit the operating design domain, or other specified circumstances, and (2) the response by an automated driving system to achieve minimal risk condition given the same circumstances."
],
"removed": [],
"summary": "Adds Dynamic driving task fallback definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.24b"
},
{
"analysis": {
"added": [
"First responder interaction plan means a document of procedures describing how first responders should interact with an autonomous vehicle, including communication with fleet support, safe removal and towing, recognition of autonomous mode, and any necessary information deemed necessary by the manufacturer."
],
"removed": [],
"summary": "Adds First responder interaction plan definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.29a"
},
{
"analysis": {
"added": [
"Human driver means a natural person in a vehicle with a valid license to operate a motor vehicle who controls all or part of the dynamic driving task."
],
"removed": [],
"summary": "Adds Human driver definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.34a"
},
{
"analysis": {
"added": [
"Minimal risk condition means a condition to which a person or a human driver or an automated driving system may bring a vehicle after performing the dynamic driving task fallback to reduce the risk of a crash when a given trip cannot or should not be completed."
],
"removed": [],
"summary": "Adds Minimal risk condition definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.40c"
},
{
"analysis": {
"added": [
"Ondemand autonomous vehicle network means a transportation service network that uses a software application or other digital means to dispatch or otherwise enable the prearrangement of transportation with autonomous vehicles for purposes of transporting passengers or goods."
],
"removed": [],
"summary": "Adds Ondemand autonomous vehicle network definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.49a"
},
{
"analysis": {
"added": [
"Operational design domain means the operating conditions under which an automated driving system is specifically designed to function including but not limited to environmental, geographical, and time-of-day restrictions and the requisite presence or absence of certain traffic or roadway characteristics."
],
"removed": [],
"summary": "Adds Operational design domain definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.50a"
},
{
"analysis": {
"added": [
"SAE J3016 means the April 2021 revision of the Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles published by SAE International."
],
"removed": [],
"summary": "Adds SAE J3016 definition to Minnesota Statutes 2024 section 169.011.",
"modified": []
},
"citation": "169.011",
"subdivision": "Subd.70a"
},
{
"analysis": {
"added": [
"Requires that a person not cause or allow an autonomous vehicle to operate on public roads unless conditions in subdivision are met."
],
"removed": [],
"summary": "Autonomous vehicle requirements under 169.251.",
"modified": []
},
"citation": "169.251",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Establishes that operation without a human driver requires authorization from the commissioner and compliance with certain conditions."
],
"removed": [],
"summary": "Operating without a human driver; authorization framework under 169.251.",
"modified": []
},
"citation": "169.251",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"Preserves human drivers' ability to operate an autonomous vehicle equipped with controls."
],
"removed": [],
"summary": "Human drivers permitted to operate autonomous vehicles under 169.251.",
"modified": []
},
"citation": "169.251",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
"Defines licensure framework for automated driving systems when no human driver is present."
],
"removed": [],
"summary": "Definition of driver licensure under autonomous vehicles under 169.251.",
"modified": []
},
"citation": "169.251",
"subdivision": "Subd.4"
},
{
"analysis": {
"added": [
"Requires human driver to comply with section 169.09 following a collision."
],
"removed": [],
"summary": "Collisions involving autonomous vehicles – Subd.1.",
"modified": []
},
"citation": "169.252",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Autonomous vehicle without a human driver must remain on scene when required by 169.09, consistent with 169.251."
],
"removed": [],
"summary": "Collisions involving autonomous vehicles – Subd.2.",
"modified": []
},
"citation": "169.252",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"Person authorized to operate autonomous vehicle without a human driver must report any collision consistent with 169.09."
],
"removed": [],
"summary": "Collisions involving autonomous vehicles – Subd.3.",
"modified": []
},
"citation": "169.252",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
"Owner must maintain proof of financial responsibility in the same form and at the same minimum limits as 65B.48 and 65B.49."
],
"removed": [],
"summary": "Financial responsibility requirements – Subd.1.",
"modified": []
},
"citation": "169.253",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Requires operator to maintain proof of financial responsibility at minimum limits of $1,000,000 combined single limit per occurrence for third-party liability."
],
"removed": [],
"summary": "Operating an autonomous vehicle without proof of financial responsibility – Subd.2.",
"modified": []
},
"citation": "169.253",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"Allows satisfaction of financial responsibility via an insurance policy or eligible surplus lines insurer per 60A.195 to 60A.2095."
],
"removed": [],
"summary": "Satisfaction methods for financial responsibility – Subd.3.",
"modified": []
},
"citation": "169.253",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
" authorizes operation of ondemand networks with compliance to 169.251 to 169.257; requires specific operational safeguards."
],
"removed": [],
"summary": "Ondemand autonomous vehicle network – Subd.1.",
"modified": []
},
"citation": "169.254",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Ondemand networks may not accept traditional street hail; must meet other network-specific rules."
],
"removed": [],
"summary": "Ondemand autonomous vehicle network – Subd.2.",
"modified": []
},
"citation": "169.254",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"An autonomous vehicle that is also a commercial motor vehicle must operate under state laws governing commercial motor vehicles, except provisions applying only to a human driver do not apply to autonomous vehicles without a human driver."
],
"removed": [],
"summary": "Operation of commercial autonomous vehicles under 169.255 – Subd.1(a).",
"modified": []
},
"citation": "169.255",
"subdivision": "Subd.1(a)"
},
{
"analysis": {
"added": [
"If the vehicle is a commercial motor vehicle, parts of the automated driving system are considered a mirror for width measurement."
],
"removed": [],
"summary": "Operation of commercial autonomous vehicles – Subd.1(b).",
"modified": []
},
"citation": "169.255",
"subdivision": "Subd.1(b)"
},
{
"analysis": {
"added": [
"An autonomous vehicle designed to be operated exclusively without a human driver is not subject to Minnesota motor vehicle equipment laws or regulations that relate to or support operation by a human driver."
],
"removed": [],
"summary": "Autonomous vehicle equipment standards – Subd.1.",
"modified": []
},
"citation": "169.256",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Autonomous vehicles, automated driving systems, and ondemand autonomous vehicle networks are governed exclusively by state law; local ordinances conflicting with state law are preempted."
],
"removed": [],
"summary": "Controlling authority – Subd.1(a).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(a)"
},
{
"analysis": {
"added": [
"Political subdivisions must not impose additional requirements or restrictions specific to autonomous vehicles or automated driving systems."
],
"removed": [],
"summary": "Controlling authority – Subd.1(b).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(b)"
},
{
"analysis": {
"added": [
"Political subdivisions must not require a license, permit, or impose a tax or fee for ondemand vehicle networks that is specific to operation of such networks."
],
"removed": [],
"summary": "Controlling authority – Subd.1(c).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(c)"
},
{
"analysis": {
"added": [
"Airport authorities may impose reasonable fees on ondemand vehicle networks consistent with fees charged to similar passenger transportation services at the airport."
],
"removed": [],
"summary": "Controlling authority – Subd.1(d).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(d)"
},
{
"analysis": {
"added": [
"This section does not exempt an ondemand vehicle network company from taxes of general applicability."
],
"removed": [],
"summary": "Controlling authority – Subd.1(e).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(e)"
},
{
"analysis": {
"added": [
"This section does not prohibit any political subdivision from enforcing traffic and road rule ordinances."
],
"removed": [],
"summary": "Controlling authority – Subd.1(f).",
"modified": []
},
"citation": "169.257",
"subdivision": "Subd.1(f)"
},
{
"analysis": {
"added": [
"Chapter 221 does not apply to ondemand autonomous vehicle networks."
],
"removed": [],
"summary": "Preemption: ondemand autonomous vehicle networks are not subject to local restrictions under Chapter 221.",
"modified": []
},
"citation": "Chapter 221",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Reference range for surplus lines insurer and related financial responsibility provisions.",
"modified": []
},
"citation": "60A.195 to 60A.2095",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Financial responsibility requirements cross-reference.",
"modified": []
},
"citation": "65B.48",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Financial responsibility cross-reference and uninsured motorist benefits related to 169.253.",
"modified": []
},
"citation": "65B.49",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Referenced in collision reporting requirements; existing statute.",
"modified": []
},
"citation": "169.09",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Range of sections governing autonomous vehicles and related networks.",
"modified": []
},
"citation": "169.251 to 169.257",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Licensure acceptance for autonomous vehicle operators.",
"modified": []
},
"citation": "Minnesota Statutes Chapter 171",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Surplus lines insurer provisions referenced for financial responsibility.",
"modified": []
},
"citation": "60A.195 to 60A.2095",
"subdivision": ""
}
]Progress through the legislative process
In Committee