Connect with us

News

Cruise to reduce self-driving fleet by 50% in SF following robotaxi crash

Credit: @b0noi/Twitter

Published

on

The California Department of Motor Vehicles (DMV) has asked General Motors’ self-driving unit, Cruise, to temporarily reduce its robotaxi fleet by 50% in San Francisco. The request came after one of the company’s driverless vehicles was involved in a crash with a fire truck last week. 

The California DMV noted that its is investigating “recent concerning incidents” involving autonomous robotaxis in the city. With this in mind, the DMV has advised that Cruise must reduce its San Francisco fleet by half until the investigation is completed and the self-driving company takes appropriate actions to improve road safety. 

Following is the CA DMV’s statement about Cruise’s recent robotaxi incidents. 

“Safety of the traveling public is the California DMV’s top priority. The primary focus of the DMV’s regulations is the safe operation of autonomous vehicles and safety of the public who share the road with these vehicles. 

“The DMV is investigating recent concerning incidents involving Cruise vehicles in San Francisco. The DMV is in contact with Cruise and law enforcement officials to determine the facts and requested Cruise to immediately reduce its active fleet of operating vehicles by 50% until the investigation is complete and Cruise takes appropriate corrective actions to improve road safety. Cruise has agreed to a 50% reduction and will have no more than 50 driverless vehicles in operation during the day and 150 driverless vehicles in operation at night. 

“The DMV reserves the right, following investigation of the facts, to suspend or revoke testing and/or deployment permits if there is determined to be an unreasonable risk to public safety.”

Advertisement
-

With Cruise agreeing to reduce its fleet by 50%, the company also released a blog post explaining the circumstances that led up to the accident. As per Cruise, the robotaxi identified the emergency vehicle almost immediately as it came into video. The robotaxi operator also noted that the vehicle initiated a braking maneuver and reduced its speed, but it was ultimately unable to avoid the collision. 

Following is Cruise’s post about the incident. 

“While our investigation is ongoing and we remain in contact with city officials and regulators, we wanted to provide an update on our preliminary analysis on the incident involving an emergency vehicle colliding with a Cruise AV. 

Advertisement
-

“First and foremost, our primary concern remains with our passenger and their well-being. We have been in contact to offer support and will remain in touch. 

“In terms of what occurred around the scene of the collision there are many aspects that looked typical from the AV’s perspective and several factors that added complexity to this specific incident. 

“The AV positively identified the emergency vehicle almost immediately as it came into view, which is consistent with our underlying safety design and expectation. It is worth noting, however, that the confines of this specific intersection make visual identification more challenging – for humans and AVs alike – as it is significantly occluded by buildings, meaning that it is not possible to see objects around the corner until they are physically very close to the intersection. 

“The AV’s ability to successfully chart the emergency vehicle’s path was complicated by the fact that the emergency vehicle was in the oncoming lane of traffic, which it had moved into to bypass the red light. 

“Cruise AVs have the ability to detect emergency sirens, which increase their ability to operate safely around emergency vehicles and accompanying scenes. In this instance, the AV identified the siren as soon as it was distinguishable from the background noise. 

“The Cruise AV did identify the risk of a collision and initiated a braking maneuver, reducing its speed, but was ultimately unable to avoid the collision.

Advertisement
-

“During the course of more than 3 million miles of fully autonomous driving in San Francisco we’ve seen an enormous number of emergency vehicles – more than 168,000 interactions just in the first 7 months of this year alone. Our first responders are trying to balance keeping all of us safe while quickly responding to emergency scenes and we’re grateful for their work and dedication.

“We realize that we’ll always encounter challenging situations, which is why continuous improvement is central to our work. We will continue to work in partnership with regulators and city departments on EMV interactions to reduce the likelihood of incidents like these happening again.”

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

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

News

Tesla Robotaxi app update now tells riders if Cybercab is the better choice

Tesla’s Robotaxi app now shows ETAs, wait times and availability for Cybercab and Model Y.

Published

on

By

Concept art of a Tesla Cybercab in Las Vegas Strip as rendered via Grok

Tesla has rolled out a new vehicle selection screen in its Robotaxi app, and it puts the numbers riders care about most in front of them before they book.

Version 26.11.0 of the app shows the estimated arrival time, the expected wait and current availability for each vehicle option on a single screen, according to a video shared by @gheeunit  on X on November 7. Riders deciding between a Cybercab and a Model Y Robotaxi can now compare those figures side by side instead of picking a car first and learning how long it will take afterward.

Tesla first gave riders that choice on September 3, the day paid Cybercab rides began in Austin. The original version of the screen listed the Cybercab, which seats two, next to the Model Y, which seats four. A later build, 26.8.2, added a seating capacity indicator so groups knew which car would fit them. What it did not show was whether choosing the Cybercab meant standing on the curb a few extra minutes.

That question matters more now than it did two months ago. Tesla had 45 Cybercabs on the Texas DMV roster when rides started. By late October the state listed 573, alongside 631 Model Ys, and community trackers logged a record 1,576 Cybercab sightings across Austin on Halloween alone. With two large fleets sharing one service area, the closest car and the quickest pickup are not always the same vehicle.

Advertisement
-

Inline availability also changes what happens when demand spikes. If no Cybercab is free nearby, the rider sees that on the selection screen rather than after trying to book one.

For now the comparison is mostly an Austin feature. Riders in Dallas, Houston, Fort Worth and the Florida markets are still matched with Model Y vehicles, though Tesla said on its third quarter earnings call that Cybercab rides would launch in Dallas this month.

The update follows a steady run of smaller changes to the rider experience. Late last month Tesla brought a quiet mode that blacks out the cabin screen to Model Y Robotaxis after first testing it in the Cybercab, and it has stretched Austin service to run from 6 a.m. to 2 a.m.

The Cybercab side of that selection screen is about to get much busier. Elon Musk said this week that Tesla will wind down Cybertruck production at Gigafactory Texas around the middle of 2027 to make room for more Cybercab output, and Tesla has said it is aiming to get Cybercabs to customers by the end of this year.

Tesla has not published official release notes for version 26.11.0.

Advertisement
-
Continue Reading

Cybertruck

Tesla is ending Cybertruck production

Published

on

Credit: diagnosticdennis/Instagram and @smile__no via Tesla Owners of Santa Clarita Valley/X

Tesla is ending Cybertruck production sometime in mid-2027, according to CEO Elon Musk.

Musk made the announcement on X last night, which came as a shock to many. He said that the Cybertruck will end production “to make room for increased Cybercab production” at Gigafactory Texas.

It is a huge blow to the fans of Tesla who have come to love the Cybertruck and identify with it as a symbol of their fandom. It has been the best-selling electric pickup, but it has had an underwhelming sales performance in terms of what was expected. This is mostly due to Tesla not meeting the prices it planned to offer the Cybertruck, as its unveiling and actual release were four years apart.

Overall, the responses were mixed. Some fans understood the move toward Cybercab production, especially as Tesla is truly pushing the autonomous future through its Robotaxi platform. However, others did not understand it.

“Damn, how many Cybercabs do you guys need?” one response read. Another said it was “Sad but understandable.”Even analyst Gary Black had responded to the news, stating he hoped Tesla planned to replace it with a traditional pickup design.

It doesn’t seem like that will be the case.

Tesla is so hell-bent on delivering autonomy and eventually providing a driverless service that owning a car seems like an arbitrary idea, according to their thesis. Instead, Cybercabs will be available to pick you up and drop you off on demand, safely, without any human help.

As a result, Tesla has thinned its lineup considerably, and one can only ask where the vehicle lineup goes from here. Eventually, it seems like Cybercab could be the only vehicle that Tesla will sell.

Continue Reading

Elon Musk

SpaceX’s next Starship flight set to make history on Friday the 13th

SpaceX is targeting Friday, November 13 for Starship Flight 15 and its first ship catch.

Published

on

By

SpaceX is targeting Friday, November 13 for Starship Flight 15, the mission the company plans to use for its first attempt at catching the ship itself with the launch tower.

SpaceX Vice President of Launch Kiko Dontchev shared the date on stage at the UP.Summit on Thursday, according to Ars Technica’s Eric Berger, who was in attendance. It is the first launch target to come directly from a SpaceX executive. Until now, the public schedule had relied on FAA air traffic planning slides, which listed Flight 15 for no earlier than November 8 and later November 12. SpaceX has not posted an official mission page yet, and no launch time has been shared.

The date lands inside the window Elon Musk sketched out last month. Speaking at Giga Texas on October 10, Musk said the flight would “probably launch a little bit before Thanksgiving,” as Teslarati reported. On SpaceX’s third quarter earnings call ten days later, he confirmed that Flight 15 would try to catch both the Super Heavy booster and the ship, and put the odds of a successful ship catch at “more likely than not.” SpaceX also aired an animation of the maneuver during that webcast, showing the ship swinging vertical over Starbase before dropping into the tower’s chopsticks.

The hardware is ready. Booster 22 fired all 33 of its Raptor engines for a full duration static fire at Pad 2 on October 25. Ship 42 followed with a single engine burn simulating a deorbit maneuver on October 26 and a 60 second firing of all six engines the next day, according to NASASpaceflight. Ship 42 had already rehearsed the catch in September, when the Pad 2 arms lifted it into position and crews connected the quick disconnect arm while the vehicle hung from the tower.

The remaining hurdle is regulatory. The FAA’s Starship page does not yet list a Flight 15 license. SpaceX President Gwynne Shotwell said in October that, after “significant constructive engagement with the FAA,” she expects the license to cover a return to the launch site and a tower catch for both stages. Bringing the ship home means a reentry path that heads toward land, rather than ending over open ocean as every Starship flight so far has.

Advertisement
-

SpaceX has caught Super Heavy three times, on Flights 5, 7 and 8, but the ship comes back from orbital velocity and has never been caught. Flight 14 on September 28 was the first Starship to reach orbit, deploying 26 Starlink V3 satellites before splashing down despite an early engine shutdown that Musk blamed on engine computer software.

Musk has called a successful ship catch “the first time that there’s been full recovery of an orbital class rocket,” and he has already named the step after it: a Flight 16 where both the booster and the ship fly again. NASASpaceflight reports that Ship 43, the next vehicle in line, is set for static fire testing in December.

Continue Reading