Connect with us
Cruise car in Hayes Valley, San Francisco Cruise car in Hayes Valley, San Francisco

News

Cruise in hot seat amid Fire Department’s claims that robotaxis delayed responders in fatal incident

Credit: Cruise

Published

on

General Motors’ self-driving unit, Cruise, saw protests outside its San Francisco headquarters earlier this week. The protests come amidst the San Francisco Fire Department’s claims that some of the company’s autonomous robotaxis contributed to the tragic death of a pedestrian. 

The incident, which happened on August 14, involved a pedestrian who was hit by a car in the South of Market neighborhood of San Francisco. The pedestrian’s injuries were so severe that there was heavy bleeding, and the person was no longer responding to verbal commands. It was evident that the injured pedestrian needed urgent medical care, so it was pertinent to have the person transported to a hospital as early as possible. 

Public reports from the San Francisco Fire Department that were obtained by Forbes claimed that the behavior of Cruise robotaxis ended up impeding the workflow of emergency responders, so much so that critical medical care was delayed. One of the Fire Department’s reports about the incident reads as follows. 

“On 8/14/2023, I was assigned to Medic 87 and responded to Incident FD23108420, at 7th Street and Harrison, for an auto vs. pedestrian. Harrison Street is 4 lanes of one-way traffic heading westbound. Upon arrival on scene, the victim was found in the (2) left lanes of Harrison Street, suffering from life-threatening injuries. SFPD and E01 had arrived prior to M87’s arrival. SFPD had a vehicle parked in the #1 lane of Harrison, and E01 had positioned its apparatus across the left 2 lanes of Harrison to shield the patient from oncoming traffic. The right 2 lanes of Harrison were blocked by (2) autonomous Cruise vehicles that had stopped and were not moving, blocking ingress and egress to the incident scene. 

“The patient was suffering from life-threatening injuries, with a GCS 3, agonal respirations, and absent peripheral pulses. SFPD had applied a tourniquet to the left lower extremity to stop life-threatening bleeding from injuries sustained after being struck by a vehicle. Ventilations were assisted with a BVM, and the patient was packaged for rapid transport to a trauma center. 

Advertisement

“While loading the patient to the ambulance, the (2) Cruise vehicles were still stopped in the right 2 lanes of Harrison, prohibiting rapid egress from the scene. SFPD had attempted manual takeover of the autonomous vehicles, but were unsuccessful. This contributed to a delay in transport with a critical trauma patient. 

“SFFD members had to locate an SFPD officer and request him to move his vehicle to allow successful egress from the scene, but doing so further delayed patient care. These delays caused by (2) autonomous vehicles blocking a normal egress route from the scene contributed to a poor patient outcome, delaying the definitive care required in severe trauma cases. The patient was pronounced deceased at SFGH approximately 20-30 minutes after arrival due to severe blunt-force trauma.”

Cruise has spoken out against the Fire Department’s account of the event. In a comment to The San Francisco Standard, a Cruise spokesperson noted that “we did not impede the vehicle from getting to the hospital” and “what the fire department said is not accurate.” 

“The first vehicle promptly clears the area once the light turns green and the other stops in the lane to yield to first responders who are directing traffic. Throughout the entire duration the AV is stopped, traffic remains unblocked and flowing to the right of the AV. The ambulance behind the AV had a clear path to pass the AV as other vehicles, including the ambulance, proceeded to do so. As soon as the victim was loaded into the ambulance, the ambulance left the scene immediately and was never impeded from doing so by the AV,” Cruise noted in a statement

Cruise has reportedly provided a video to back up its claims. The video reportedly showed that while one Cruise robotaxi was indeed stopped at an intersection, there was a free lane to its right where traffic was moving. The video, which was reviewed by Forbes, did show numerous vehicles, including a small ambulance, moving through the free lane. However, the publication noted that it was not clear from the footage if the larger SFFD ambulance, which was likely transporting the severely injured pedestrian, could have navigated the area as easily. 

Advertisement

Below are incident reports from the San Francisco Fire Department. The case in question is described in Page 68 and 69 of the document.

Cruise San Francisco Reports by Simon Alvarez on Scribd

Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads-up. 

Advertisement

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Elon Musk

Elon Musk says Tesla will take Safety Drivers out of Robotaxi: here’s when

“The safety driver is just there for the first few months to be extra safe. Should be no safety driver by end of year.”

Published

on

Credit: Joe Tegtmeyer | X

Tesla CEO Elon Musk said today that the company plans to completely eliminate Safety Drivers from its Robotaxi fleet, which differs from the Safety Monitors it uses.

Tesla’s Robotaxi platform utilizes employees in the front passenger seat during city rides in Austin and the driver’s seat of the vehicles during highway operations in Austin, as well as during all rides in the Bay Area.

Tesla adjusts Robotaxi safety monitor strategy in Austin with new service area

Musk said the presence of a Safety Driver “is just there for the first few months to be extra safe,” but there are plans to remove them in an effort to remove the crutches the company uses during the early stages of Robotaxi.

The CEO then outlined a timeframe for when it would remove the presence of an employee in the driver’s seat in both Austin and the Bay Area. He said there “should be no safety driver by end of year.”

Advertisement

Having a Safety Driver or Monitor has been a major point of criticism from Robotaxi skeptics and Tesla critics.

However, Tesla has maintained that its priority in the early stages is the safety of riders, which will keep things running; even a single negative incident could derail self-driving efforts as a whole, including those outside of the company.

Advertisement

Tesla executives have said their attitude toward safety is “paranoid,” but for good reason: an accident could set back the progress that it and many other companies, including rivals like Waymo, have made in the past few years.

For now, it might be a point of criticism for some, but it’s smart in the near term. Musk plans for Tesla to have Robotaxi operating for half of the U.S. population by the end of the year as well, so it will be interesting to see if it can maintain these timelines.

Continue Reading

News

Tesla is already giving Robotaxi privileges hours after opening public app

This morning, Tesla launched the app in the Apple Store, giving iOS users the ability to download and join a waitlist in hopes of gaining access.

Published

on

tesla robotaxi app on phone
Credit: Tesla

Tesla is already giving Robotaxi privileges to those who downloaded the app and joined its waitlist just hours after it launched in the United States.

As the Robotaxi platform has been operating in Austin for several months, Tesla is now allowing the general public to download its app and call for a driverless ride in the city.

Tesla Robotaxi makes major expansion with official public app launch

The company previously sent invitations to select media outlets and Tesla influencers, seeking initial feedback on the performance of the Robotaxi platform.

There have been positive reviews, but, as with any Beta program, some mishaps have also occurred, although none have been significant.

Advertisement

As of the writing of this article, the City of Austin only lists one incident involving a Tesla Robotaxi, noting it as a “Safety Concern,” but not an accident or collision.

This morning, Tesla launched the app in the Apple Store, giving iOS users the ability to download and join a waitlist in hopes of gaining access.

Tesla is already granting Robotaxi access to several of those who have downloaded the app and gotten on the waitlist early:

Advertisement

With the launch of the public app, we were not too sure how soon Tesla would be able to initiate bringing more riders into the Robotaxi program. The immediate admittance for some riders just hours after the launch is a big positive and is surely a sign of strength for Tesla and its Robotaxi program.

What many will look for moving forward is the expansion of the geofence, which does not seem like a problem, as Tesla has already managed to do this on three occasions. The most recent expansion has expanded the service area to approximately 190 square miles.

People will also look for evidence of fleet expansion, a concern that has been a concern for many, especially since Tesla has not been completely transparent about it. They have revealed a recent service fleet growth of 50 percent, but there has been no specific number of vehicles mentioned.

Tesla reveals it has expanded its Robotaxi fleet in Austin

Advertisement
Continue Reading

News

Tesla explains why Robotaxis now have safety monitors in the driver’s seat

The update to Austin’s safety monitors became a point of interest among Tesla watchers on social media.

Published

on

Credit: Tesla

Tesla has provided an explanation about the presence of safety monitors in the driver’s seat of its autonomous Robotaxi units.

The autonomous ride-hailing service is currently being deployed in Austin and the Bay Area, with more cities across the United States expected to gain access to the service later this year.

Safety Monitors

When Tesla launched its initial Robotaxi program in Austin, the company made headlines for operating vehicles without a human in the driver’s seat. Even with this setup, however, Tesla still had safety monitors in the passenger seat of the Robotaxis. The safety monitors, which do not interact with passengers, have been observed to report issues and other behaviors from the autonomous vehicles in real time. 

Safety monitors on the driver’s seat were also employed in the service’s Bay Area rollout, though numerous members of the EV community speculated that this was likely done to meet regulations in California. However, with the expansion of the Austin geofence, riders in Tesla’s Robotaxis observed that the safety monitors in the city have been moved to the driver’s seat as well.

Tesla’s explanation

The update to Austin’s safety monitors became a point of interest among Tesla watchers on social media. Longtime FSD tester Whole Mars Catalog, for one, speculated that the move might be due to Texas’ new regulations for autonomous vehicles, which took effect recently. Interestingly enough, the official Tesla Robotaxi account on X responded to the FSD tester, providing an explanation behind the safety monitor’s move to the driver’s seat. 

Advertisement

“Safety monitors are only in the driver’s seat for trips that involve highway driving, as a self-imposed cautious first step toward expanding to highways,” the Tesla Robotaxi account noted.

Tesla has been extremely cautious with its autonomous driving program, particularly with the rollout of its Robotaxi service, which use Unsupervised FSD. This is quite understandable considering the negative media slant that Tesla is consistently subjected to, which could very well result in minute incidents or mistakes by Robotaxis being blown out of proportion.

Continue Reading

Trending