Elon Musk's Loop: Autopilot & Security Breach

Security Breach Reported in Las Vegas Loop System

Just under two weeks following its formal debut, The Boring Company’s Loop infrastructure in Las Vegas experienced its initial security compromise.

Records obtained by TechCrunch through public records requests reveal that on June 21st, coinciding with the concluding day of the International Beauty Show, a vehicle lacking authorization gained access to the Loop’s network of Tesla taxis operating beneath the city.

Details Revealed Through Email Correspondence

The disclosed email exchange between the Loop’s operations manager and a representative from Clark County offers further details regarding the Loop’s functionality.

These details extend beyond the security incident itself, encompassing the system’s unexpected dependence on an electric vehicle not manufactured by Tesla, and future intentions to enable Tesla’s Autopilot driver-assistance technology within the Loop.

Furthermore, internal communication confirms that the system does not currently operate with full autonomy.

Incident Response and System Security

The Boring Company (TBC) contacted the Las Vegas Metro Police Department to address the unauthorized entry.

According to an email, the driver of the vehicle was compliant and subsequently removed from the system.

Although no harm came to any individuals as a consequence of this breach, the occurrence presents a potential public relations challenge for TBC.

The company has previously emphasized the security and safety features of its $53 million system at the Las Vegas Convention Center (LVCC).

Contractual Security Measures

The management agreement between TBC and the LVCC stipulates the implementation of “physical barriers” to prevent unauthorized vehicle access to the tunnels.

These barriers include security gates at entry points to the system and numerous concrete bollards surrounding the above-ground stations.

Lack of Official Comment

Neither TBC nor the LVCC provided responses to inquiries concerning the incident.

TechCrunch intends to update this report should either organization offer further clarification.

Key Takeaway: The incident highlights potential vulnerabilities in the Loop’s security infrastructure despite stated preventative measures.

Autopilot Consideration for Loop Vehicles

Recently obtained email correspondence, as reported by TechCrunch, reveals details extending beyond unauthorized access. These communications illuminate plans held by The Boring Company (TBC) regarding its Tesla fleet within the Las Vegas Convention Center (LVCC) Loop.

Specifically, TBC intends to expand the number of Tesla vehicles operating in the Loop from 62 to 70. Furthermore, the company seeks authorization to enable Tesla’s Autopilot technologies within these vehicles. Currently, all driver-assistance systems are deactivated during operation by human drivers.

The proposed expanded operation necessitates the activation of seven distinct active safety features. These include automatic emergency braking, forward and lateral collision alerts, obstacle-aware acceleration, blind-spot monitoring, lane departure prevention, and emergency lane departure warnings.

In addition to these, TBC aims to utilize two “full Autopilot” capabilities: lane centering and traffic-aware cruise control.

A letter from TBC president Steve Davis to the Clark County Department of Building & Fire Prevention, acquired by TechCrunch alongside the emails, outlines the rationale for employing Autopilot.

Davis argued that disabling these features “removes a safety net” from a “validated and legally permissible technology.” He referenced Tesla’s Q1 2021 Safety Report, which indicated that drivers utilizing Autopilot experienced crashes at a rate less than 25% of those driving without it or active safety features. Davis asserted that deactivating these systems elevates the risk of accidents.

However, the National Highway Traffic Safety Administration (NHTSA) initiated a formal safety investigation into the technology last week, prompted by a series of incidents.

Jerry Stueve, director of building and fire protection for Clark County, responded via email, stating that the request would be considered. He also requested a clearer definition of “autodrive” and its implications.

Davis acknowledged that the term “Autopilot” can be ambiguous, varying based on the vehicle and driving conditions. This perspective appears to contrast with that of his superior, Elon Musk, who dismissed criticism of the name as “idiotic” and misleading.

Davis clarified that the vehicles are not intended to be “autonomous” or “self-driving.” He emphasized that Tesla Autopilot and active safety features enhance safety while a fully attentive driver remains prepared to assume control at any time.

Autopilot and Autonomous Driving: A Critical Difference

A fundamental distinction exists between autopilot and truly autonomous driving, and this difference appears to be at odds with initial promises made by The Boring Company (TBC) to the Las Vegas Convention and Visitors Authority (LVCC) regarding the Loop system.

Prior to construction, TBC’s land use application from May 2019 explicitly stated: “Tesla Autonomous Electric Vehicles (AEVs) will transport passengers rapidly through underground tunnels, connecting to three subterranean stations.”

Further reinforcing this expectation, a planning document from July 2019 highlighted: “The implementation of autonomous electric vehicles within underground tunnels represents an innovative transportation approach designed to minimize interference with existing infrastructure and building operations.” Similar phrasing has been consistently used in subsequent applications, including proposals for an expanded Vegas-wide Loop network encompassing numerous stations.

The Agreement and Expectations of Autonomy

A management agreement obtained by TechCrunch in January revealed that “[The LVCC] contracted the People Mover System, partially due to the potential for autonomous vehicle operation… The agreement acknowledges the intention to transition from human drivers to fully autonomous systems and includes provisions for fee adjustments, scheduled for review by December 31, 2021, to reflect this operational shift.”

However, meeting this deadline now appears highly improbable. In June, Stueve communicated to Davis that securing approval for autonomous operation would necessitate “extensive evaluation, testing, and validation,” a process potentially requiring considerable time.

Davis responded directly, clarifying: “To ensure clarity, we are not requesting, nor are we seeking, autonomous or self-driving capabilities within the system.”

Shifting Goals and Current Status

This exchange suggests a significant shift in expectations. The initial vision of a fully autonomous transportation system, as presented in TBC’s applications and the agreement with LVCC, is now being re-evaluated.

The focus appears to have moved away from full autonomy, potentially impacting the long-term financial arrangements outlined in the original agreement. The implications of this change for the future of the Vegas Loop remain to be seen.

The Role of Human Operators in the Loop System

A dual challenge exists regarding The Boring Company’s Loop system. Firstly, full driverless operation of Tesla’s Autopilot may remain distant. Secondly, and potentially more critically, the Loop currently depends significantly on human drivers to fulfill stringent safety regulations governing underground transit networks, as defined by national standards.

Passenger safety within these systems – encompassing monorails, subways, and electric vehicle-based transport – is paramount, necessitating preparedness for events like power failures, fires, and flooding.

Safety Protocols and Driver Responsibilities

According to the LVCC Loop’s design basis document, acquired by TechCrunch alongside related email correspondence, “trained drivers function as the system’s primary safety mechanism.” In emergency scenarios, driver-led passenger guidance constitutes the main risk mitigation strategy.

Further documentation obtained by TechCrunch from BFP corroborates this. Should a fire occur, the driver is tasked with “assisting passengers during evacuation and directing them towards the nearest exit.” This includes providing verbal instructions and offering physical assistance when necessary.

As drivers guide passengers, they are required to “continuously monitor the group to ensure all individuals are following closely.” This constant visual check is a key safety measure.

Beyond emergency response, drivers are also responsible for managing passenger behavior and, importantly, for monitoring the Autopilot system’s performance. Davis communicated in June that drivers would “ensure oversight of active safety features and be prepared to assume manual control of braking and steering when needed.”

The Absence of a Clear Path to Full Autonomy

A review of numerous documents and emails – including those detailing planned expansions of the LVCC Loop – revealed no outlined plan or timeline for The Boring Company to transition to fully autonomous operation.

When questioned about adherence to safety principles for autonomous systems established by the American Society of Civil Engineers, The Boring Company stated that “criteria specific to autonomous operation are not applicable” because the system will retain human drivers.

The future operational model of the Loop – whether aligned with statements to Clark County or the LVCC – remains to be seen.

Vehicle Diversity and ADA Compliance

Furthermore, the assumption that the Loop fleet will consist exclusively of the latest Tesla models may be inaccurate.

Compliance with the Americans with Disabilities Act (ADA) necessitates vehicle diversity. A TBC executive informed Clark County officials in July of plans to procure a non-Tesla, ADA-compliant electric vehicle for the LVCC Loop.

The email indicated a vehicle utilizing a low-range lead-acid battery, matching the specifications of the Tropos Motors Able electric utility vehicle. Neither Tropos Motors nor The Boring Company responded to requests for comment.