Operating Across State Lines

Published October 18, 2026

Law checked through October 18, 2026.

A Texas authorization does not automatically authorize autonomous operation or a transportation service in another state. Federal vehicle and aviation law can provide a common layer, while state operation, licensing, insurance, privacy, property, and local rules differ. A multistate program should identify the machine, mission, route, service, and actors in each jurisdiction. Comparative examples are starting points, not an assertion that every state has the same definitions or approval process. [1; 2; 3; 4]

Build a jurisdiction and activity map

The map should distinguish testing, deployment, commercial freight, passenger rides, delivery devices, drones, and remote support. It should identify where the vehicle operates, where personnel work, where services are sold, and where information is processed. A company's Texas headquarters is not the only relevant location.

The record should also separate effective statutes, rules, permits, proposals, and agency guidance. A bill tracker can reveal changes but does not itself supply operating permission. A route expansion should trigger review of each state's current requirements and the actual permits held.

Texas as the starting point

Texas Subchapter J defines the covered automated systems and vehicles and establishes operating conditions, driverless commercial authorization, first-responder plans, enforcement, and local limitations. The statute's treatment of an engaged ADS and human-driver requirements has its own scope. It should not be assumed to describe another state's law. [1]

Texas commercial trucking also retains separate state and federal layers. A carrier should identify registration, authority, insurance, inspection, maintenance, cargo, and applicable exemptions across the movement. A Texas exception for provisions reasonably applying only to a human does not rewrite the federal regulations. [5]

Arizona and Florida examples

Arizona § 28-9702 permits specified autonomous operation and requires a law-enforcement interaction plan and written statement for driverless fully autonomous operation. Its statement covers federal compliance, fallback, traffic-law capability, and title, registration, licensing, and insurance. Failure to submit the required material can support the stated cease-and-desist action. [2]

Florida § 316.85 treats the engaged ADS as operator within its provisions, permits fully autonomous operation without an onboard human, and separately addresses on-demand networks, insurance, teleoperation, and local uniformity. Its airport and seaport provisions preserve specified facility arrangements. Those details show why a general description such as permissive state is insufficient for operational planning. [3]

California's permit structure

California uses DMV testing and deployment requirements and separate passenger-service authority where applicable. The DMV announced adoption of updated rules on April 28, 2026, including heavy-duty vehicles and revised oversight. The actual adopted text, permit category, conditions, and effective provisions control. A manufacturer's existing light-duty permit should not be assumed to cover every new truck or service. [4]

The comparison should identify application materials, safety evidence, reporting, operational limits, interaction with law enforcement, and enforcement powers. California marketing proceedings are separate from Texas tort conclusions and should retain their own procedural status.

Drones and ground delivery devices

FAA authority remains central to flight, but state imagery, privacy, property, and local ground-site rules can differ. The FAA's state and local fact sheet explains the general division of authority, not a complete fifty-state compliance opinion. Texas Chapter 423 is one state-specific layer requiring its own analysis. [6; 7]

Personal delivery devices can have state-specific definitions, speed limits, weight or operating conditions, insurance, and local authority. Texas Chapter 552A should not be copied into another state's route plan. A device's qualification in Texas does not establish that it falls within the corresponding category elsewhere. [8]

Contracts, data, and incident response

Policies and contracts should identify territory, applicable approvals, changes, insurance, support, information rights, and responsibility for updates. Data privacy obligations may depend on residents, entity coverage, processing, and state-specific definitions rather than the robot's registration alone.

An incident plan should identify local responders, regulators, insurers, evidence, and reporting duties for the location and operation. A national fleet dashboard should not hide state-specific obligations behind a single compliance indicator. Recommended periodic review should focus on actual changes in law, permits, vehicles, routes, and service rather than mechanically advancing review dates.