Connect with us

News

GM’s self-driving arm Cruise hit with its latest fine over crash response

Credit: Cruise

Published

on

General Motors’ (GM’s) driverless ride-hailing company Cruise has been hit with its latest fine, after the company failed to disclose certain details about an accident involving a pedestrian last October.

Cruise has agreed to pay a $500,000 criminal fine over the record it submitted following an accident with a pedestrian last October, as detailed by the Department of Justice (DOJ) in deferred prosecution that was revealed on November 14 (via Automotive News). The decision was made within the U.S. Attorney’s Office in the Northern District of California, and it comes as the most recent legal penalty the company has had to pay after regulators said it “omitted” and “misrepresented” details about the accident.

According to NHTSA special agent Cory Legars, who is overseeing the Cruise case, the fine is intended to help hold Cruise and its staff accountable, following a “lack of candor” in response to the 2023 crash in which a robotaxi dragged and pinned a pedestrian.

The DOJ echoed the company’s withholding of certain details following the accident, which caused “multiple traumatic injuries” for the pedestrian, according to emergency responders. Cruise has also been criticized over its response to the accident by other agencies, including the California Public Utilities Commission (CPUC) and the state’s Department of Motor Vehicles (DMV).

Along with the fine, Cruise must also implement a safety compliance program, submit yearly reports to the U.S. Attorney’s Office, and cooperate with all government agency investigations.

In a written statement, Cruise Chief Administrative Officer Craig Glidden said that company maintained a “firm commitment to transparency with our regulators.”

Cruise leadership pledges more transparency, greater culture of safety in new letter

Cruise’s October 2023 accident and other crash response fines

In the accident, which took place on October 2, 2023, a Cruise robotaxi struck a pedestrian moments after she had been hit by a car with a human driver. The pedestrian ended up in the path of the Cruise vehicle, which hit her, dragged her about 20 feet, and engaged an emergency stop sequence that caused the vehicle to stop on top of her with hazard lights on until authorities arrived.

Advertisement
-
-

Following the accident, the DMV and other agencies noted that Cruise avoided sharing certain details, including exactly what the robotaxi did after it ran over the individual. Weeks later, Cruise disclosed a more full version of events, but it was only after the DMV specifically requested more details. The agency also suspended Cruise’s permit to operate self-driving vehicles, effective immediately.

“Cruise’s omission hinders the ability of the department to effectively and timely evaluate the safe operation of Cruise vehicles and puts the safety of the public at risk,” said Bernard Soriano, DMV deputy director, after the accident.

In the following weeks and months, Cruise would go on to see a significant staff and executive shake-up, with its two co-founders resigning alongside several other high-level employees. The company also went on to let go of around a quarter of its staff, before hiring several new executives in attempts to regain public and regulator trust and relaunch the service.

Cruise is currently aiming to reboot driverless ride-hailing sometime this year, though it has faced multiple fines from agencies and regulators in addition to the $500,000 agreement with the DOJ.

In June, following months of commission deliberation, Cruise was ordered by the CPUC to pay the maximum penalty of $112,500 for its crash response, after the company originally lobbied for a fine of just $75,000. In September, the NHTSA ordered Cruise to pay a $1.5 million fee, along with submitting a corrective action plan and additional details on how the company plans to fulfill reporting standards in any future incidents.

What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send us tips at tips@teslarati.com.

Cruise robotaxi pedestrian accident review concludes with strange findings

 

Advertisement
-
-

Zach is a renewable energy reporter who has been covering electric vehicles since 2020. He grew up in Fremont, California, and he currently lives in Colorado. His work has appeared in the Chicago Tribune, KRON4 San Francisco, FOX31 Denver, InsideEVs, CleanTechnica, and many other publications. When he isn't covering Tesla or other EV companies, you can find him writing and performing music, drinking a good cup of coffee, or hanging out with his cats, Banks and Freddie. Reach out at zach@teslarati.com, find him on X at @zacharyvisconti, or send us tips at tips@teslarati.com.

Advertisement
Comments

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

on

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

on

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

on

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading