Cities Aim to Curb Robotaxi Operations
This is a weekly update diving into a key story from the tech landscape. For insights on self-driving vehicles, regulations, and road policies, keep an eye on the developments in this space.
How it started
Nevada made history in June 2011 by becoming the first state to legalize self-driving cars on public roads, well ahead of their actual deployment. This was three years prior to Tesla launching its Autopilot feature, five years before Waymo separated from Google’s self-driving initiative, and seven years before the first commercial robotaxi service began in Arizona. Nevada’s proactive stance was largely driven by lobbying efforts, particularly from Google, which viewed the state as an ideal testing ground for its prototypes. The legislation even included a clause allowing drivers to text while the automated system was engaged.
At that time, many regions embraced self-driving cars, eager to showcase their commitment to innovation. Little did they know that over a decade later, they would be revisiting their policies to regulate these very vehicles. While federal regulators are still working to establish safety standards, legislation aimed at creating rules for autonomous vehicles has been stalled in Congress for years. This legislative gridlock has pushed local lawmakers to draft their own regulations to ensure that robot cars adhere to some form of road rules.
The outcome has been a fragmented set of regulations for robotaxi operators, a scenario that many industry leaders had hoped to avoid. As robotaxis expand into new areas, local officials are uncovering unforeseen challenges posed by these new residents, prompting the creation of even more rules and increasing complexity for operators.
How it’s going
While municipalities typically lack control over vehicle manufacturing standards, they wield significant authority over street operations. Consequently, they have been enacting their own laws to manage the deployment of robotaxis. There isn’t a precise tally of local regulations passed since robotaxis became mainstream, but in the absence of federal guidelines, cities and states are asserting their authority to impose order amid the chaos.
For instance, Minneapolis is contemplating an ordinance that would require human monitors in autonomous vehicles, effectively banning driverless operations. Meanwhile, the San Diego City Council has passed a resolution aimed at preventing Waymo from operating at the airport and granting local agencies direct control over AVs during emergencies. Austin firefighters have raised concerns about the Tesla Cybercab’s lack of traditional controls, arguing that it could complicate emergency responses. They are advocating for AV developers to implement rapid-response towing protocols and establish direct communication with human operators for emergencies.
Interestingly, the pushback against autonomous vehicles is transcending traditional political boundaries. Historically, Republicans were seen as more supportive of self-driving technology, while Democrats were more skeptical. This trend has been evident in several Democrat-led cities—like New York City, Chicago, and Washington, DC—that have yet to legalize driverless cars. However, even some Republican-led states, including Kentucky, Oklahoma, South Dakota, and Iowa, are now considering stricter regulations.
Even in California, a hub for tech innovation, lawmakers are exploring ways to impose limits on robotaxis. Several bills have been introduced to grant cities the authority to cap AV fleet sizes, restrict operating hours, or enforce local permit bans. Additionally, emergency protocols are being drafted to require AV companies to provide local police and fire departments with physical override access or emergency shut-off mechanisms.
Some municipalities are also leveraging their land-use and zoning powers to regulate robot cars. Culver City has looked into emergency moratoriums on building permits for AV fleet facilities, while Santa Monica has utilized local noise and traffic ordinances to limit 24-hour charging hubs. It seems that even robotaxis are not immune to local opposition.
What happens next
As the local discourse around autonomous vehicles heats up, AV developers are increasingly eyeing international markets as a potential refuge from the regulatory hurdles in the US. Waymo plans to expand its services to London, Tokyo, and Munich, while Uber is gearing up for operations in Manchester, Madrid, and Dubai. If the regulatory landscape in the US becomes too convoluted, these companies may find more welcoming environments abroad.
Nonetheless, the US remains the most promising market for profitability, especially as development costs continue to rise. Instead of confronting stringent local regulations directly, companies like Waymo, Zoox, and Aurora are focusing on states with laws that prevent individual cities from banning their technology. At the national level, industry trade groups are actively advocating for more preemption powers to establish unified standards.
While Congress may eventually pass overarching safety legislation, it’s unlikely that any federal bill would strip cities of their essential powers over policing, zoning, and emergency responses. States will also have a role, which may sometimes align with or contradict their cities. Even airport authorities are proposing their own regulations for robotaxis. AV companies should prepare for this patchwork of rules—it’s here to stay.
By the way
* Even if federal legislation like the proposed SELF DRIVE Act is enacted, cities and states will retain their authority over local road usage. This means that cities will continue to be the primary decision-makers regarding robotaxi permissions for the foreseeable future.
* Texas may have fewer regulations governing self-driving cars than most states, but California remains the benchmark. Obtaining a deployment permit from the California Public Utilities Commission is regarded as a significant safety endorsement within the industry.
