The question of when Uber first launched its self-driving car program is more complex than it initially appears. While public perception might point to grand announcements and media events, a closer examination, fueled by previously unseen emails, reveals a more nuanced and arguably secretive timeline. This article delves into the crucial moments and decisions that marked the initiation of Uber’s autonomous vehicle endeavors, shedding light on the actual beginnings of a program that would soon face both technological hurdles and public safety crises.
To truly understand when Uber’s self-driving car program began, we need to look beyond the headlines and explore the strategic moves, political maneuvers, and quiet testing phases that characterized its early stages. This investigation will uncover a timeline marked by ambition, regulatory loopholes, and ultimately, a tragic incident that forced a critical re-evaluation of the entire self-driving industry.
The Seeds of Autonomy: Pre-Launch Maneuvering in Arizona
Arizona, under the governorship of Doug Ducey, emerged as a pivotal location for Uber’s autonomous vehicle ambitions. Emails obtained by The Guardian expose a concerted effort by Uber to cultivate a favorable environment in the state, starting well before any public announcement of a self-driving car program. As early as 2015, Uber executives engaged with Governor Ducey’s office, seeking to solidify their operations and expand their footprint in Arizona. This courtship involved offering workspace to Ducey’s staff in San Francisco, showering praise on the governor, and promising economic benefits to the state.
An Uber self-driving car undergoing tests in Arizona, illustrating the early stages of their autonomous vehicle program and the state’s role in facilitating its development.
Governor Ducey reciprocated this enthusiasm, actively assisting Uber in navigating state regulations and even publicly promoting the company. This friendly relationship was solidified in April 2015 when Ducey signed a bill legalizing ride-sharing, an event attended by Uber executives and drivers. Uber’s gratitude was palpable, with emails revealing discussions about Governor Ducey wearing an Uber shirt at the signing ceremony and effusive praise from Uber officials for Ducey’s “thought leadership” on innovation.
This groundwork laid the foundation for Arizona to become a testing ground for Uber’s more ambitious projects, including self-driving cars. In June 2015, Uber established a customer support center in Phoenix, followed by a collaboration with the University of Arizona’s College of Optical Sciences, ostensibly for mapping car fleets and lidar technology research. Crucially, on the same day as the university announcement, Governor Ducey issued an executive order that paved the way for the public testing of autonomous vehicles, provided they had human safety drivers. This order, remarkably favorable to Uber, even allowed for fully driverless pilot programs on university campuses, demonstrating the extent of Arizona’s accommodating stance.
Pittsburgh’s Public Debut: August 2016
The public unveiling of Uber’s self-driving car program occurred in August 2016 in Pittsburgh, Pennsylvania. This announcement marked the moment when Uber customers could, for the first time, hail self-driving cars, albeit with safety drivers present. This was widely reported as Uber entering the self-driving car race and represented a significant step forward in the company’s technological development.
However, while Pittsburgh served as the public launchpad, behind the scenes, Arizona was already playing a more clandestine role.
The Secret Arizona Testing: Kicking Off in August 2016
Contradictory to the Pittsburgh fanfare, emails reveal that Uber’s self-driving car program quietly initiated testing in Arizona at virtually the same time as the Pittsburgh announcement. On August 19, 2016, an Uber policy executive informed Governor Ducey’s deputy chief of staff that “starting this weekend” Uber would “start testing some self-driving functionality” in Arizona. This email, seemingly innocuous, unveiled the commencement of real-world autonomous vehicle testing on Arizona roads, unbeknownst to the public.
An Uber test driver in a self-driving vehicle, highlighting the crucial role of safety drivers during the initial testing phases of the program in Arizona and elsewhere.
Uber justified the lack of public disclosure by stating their focus was on the Pittsburgh pilot launch. However, the emails indicate a conscious decision to keep the Arizona testing program under wraps. Uber even sought Governor Ducey’s office’s assistance in discreetly informing the Phoenix police department about the self-driving vehicles operating on public roads, further emphasizing the secretive nature of this initial phase.
Arizona’s regulatory environment, characterized by a lack of specific autonomous vehicle regulations and Governor Ducey’s welcoming stance, allowed Uber to operate without mandatory public disclosure or stringent oversight. This regulatory vacuum became a key factor in Uber’s decision to expand its self-driving program in Arizona.
San Francisco Setback and Arizona’s Open Arms: December 2016
Later in 2016, Uber’s self-driving car program faced a significant hurdle in California. When Uber launched its autonomous vehicles in San Francisco in December without obtaining the required permits, the California Department of Motor Vehicles revoked the registration of Uber’s test vehicles due to safety concerns, including reports of running red lights.
Faced with this regulatory roadblock in California, Uber swiftly relocated its self-driving program to Arizona. Governor Ducey seized this opportunity to publicly contrast Arizona’s approach with California’s, stating, “Arizona welcomes Uber self-driving cars with open arms and wide open roads.” This public embrace further solidified Arizona as Uber’s primary testing ground for autonomous technology. Notably, Governor Ducey’s statement neglected to mention that Uber had already been secretly testing self-driving cars in Arizona for months.
The Fatal Crash and Program Suspension: March 2018
The culmination of Uber’s early self-driving car program timeline arrived tragically in March 2018. An Uber self-driving vehicle, operating in Tempe, Arizona, struck and killed a pedestrian, Elaine Herzberg. This marked the first fatal crash involving a self-driving car and a pedestrian in the United States and triggered a national conversation about the safety and regulation of autonomous vehicle technology.
Law enforcement examining the Uber self-driving vehicle involved in the fatal accident in Tempe, Arizona, an event that significantly impacted public perception and regulatory scrutiny of autonomous vehicle technology.
In the aftermath of the fatal crash, Governor Ducey, who had been a staunch supporter of Uber’s autonomous program, suspended the company’s right to test self-driving cars on Arizona public roads. This reversal highlighted the significant shift in public and political sentiment following the accident. Uber also suspended its self-driving vehicle testing programs in Pittsburgh, San Francisco, and Toronto, signaling a major setback for its autonomous ambitions.
Scrutiny and Safety Concerns
The fatal accident in Arizona brought intense scrutiny to Uber’s self-driving technology and the regulatory environment that had enabled its rapid deployment. Reports emerged highlighting the frequency of “interventions” – instances where human safety drivers had to take control of Uber’s autonomous vehicles due to system errors or safety concerns. Compared to competitors like Waymo (Google’s self-driving car spin-off), Uber’s intervention rates were significantly higher, raising questions about the maturity and safety of its technology.
The incident also underscored the limited oversight provided by Arizona’s self-driving vehicle oversight committee, which, despite being established to advise on safety and regulations, appeared to have been largely inactive and ineffective. The composition of the committee, dominated by state appointees rather than independent experts, further fueled concerns about its impartiality and effectiveness.
Conclusion: A Launch Timeline Defined by Ambition and Oversight Lapses
In conclusion, pinpointing the exact “launch” of Uber’s self-driving car program requires differentiating between public perception and operational reality. While August 2016 in Pittsburgh marked the public debut, the true operational launch, characterized by real-world testing on public roads, quietly commenced in Arizona around the same time. This Arizona launch, facilitated by a lenient regulatory environment and a close relationship with state authorities, was initially conducted in secrecy, highlighting a strategic approach that prioritized rapid deployment over public transparency and potentially, thorough safety validation.
The timeline reveals a narrative of ambition, where Uber sought to quickly establish itself as a leader in the burgeoning self-driving car industry. However, this ambition, coupled with regulatory loopholes and insufficient oversight, ultimately culminated in a tragic accident that forced a critical reckoning for Uber and the broader autonomous vehicle sector. The Arizona experience serves as a stark reminder of the critical importance of robust regulation, public transparency, and rigorous safety standards in the development and deployment of transformative technologies like self-driving cars.
