Connect with us
California DMV seems to want Tesla to advertise FSD & Autopilot California DMV seems to want Tesla to advertise FSD & Autopilot

News

Tesla Autopilot claims must be pursued outside court, rules judge

Credit: AI Addict/YouTube

Published

on

A federal judge in California has ruled in favor of Tesla in a case looking at whether or not the company misled consumers about the capabilities of its Autopilot advanced driving assistance system (ADAS). The ruling will prevent Tesla from facing class-action claims from larger groups blaming the Autopilot system for accidents, with the judge instead requiring the plaintiffs to pursue individual arbitration outside of court.

On Saturday, U.S. District Judge Haywood Gilliam said that four Tesla owners who were pursuing a class-action lawsuit against the company agreed to arbitrate legal claims when they accepted the terms and conditions of their online vehicle purchases (via Reuters). Although a fifth plaintiff did not sign an arbitration agreement, Gilliam ruled that the Tesla owner had waited too long to file a lawsuit against the company.

Plaintiffs initially alleged that they were misled to think the company was on the cusp of full autonomy upon purchasing the ADAS but were instead sold unreliable technology that has resulted in multiple accidents, injuries and deaths.

Tesla has denied doing anything wrong throughout the process.

Tesla to face twin Autopilot trials over fatal incidents

During the case, Tesla cited the arbitration agreement signed by four of the plaintiffs, and Gilliam rejected the plaintiffs’ claims that the arbitration agreements weren’t enforceable.

Advertisement
-

Tesla did not immediately respond to Reuters’ requests for comment on Monday, nor did lawyers for the plaintiffs.

The victory could set a precedent for ongoing and future cases surrounding Tesla’s Autopilot system, and it comes amidst the first U.S. trial in which plaintiffs claimed that the feature led to fatalities due to what they called untested, experimental technology.

The plaintiffs in that case say that Autopilot caused their Model 3 to drive off of a highway in Southern California at 65 miles per hour, then striking a tree and causing the car to start on fire. The accident, which took place in 2019, killed driver and vehicle owner Micah Lee and caused severe injuries to two passengers, including an 8-year-old boy.

Tesla noted that Lee had consumed alcohol prior to getting behind the wheel, though plaintiffs may argue that Lee’s blood alcohol content (BAC) was under the legal limit. Additionally, Tesla argued that human error caused the accident, adding that it could not be determined whether Autopilot was actually engaged at the time of the accident.

Crucially, Tesla doesn’t say that Autopilot or its Full Self-Driving (FSD) beta systems are fully autonomous, and the company alerts drivers that they must be ready to take complete control of the steering wheel at all times.

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

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

Elon Musk

Elon Musk’s AI Grok Bot can now handle banking while your Tesla FSD handles the road

Elon Musk says Grok Bot can manage your finances through linked bank and investment accounts.

Published

on

By

Concept of SuperGrok Bot handling banking in a Tesla via Grok
Concept of SuperGrok Bot handling banking in a Tesla via Grok

Grok Bot now wants access to your wallet, with SpaceXAI rolling out a new Finance integration for its agent platform that lets users link bank, credit card and investment accounts thereby letting their Bots help manage spending, investments and more. Elon Musk amplified the announcement on X with a short endorsement, “Grok Bot can manage your finances.”

The feature builds on two earlier steps. In early September, Grok gained the ability to answer questions about spending, savings, investments and cash flow using accounts connected through Plaid, starting with users in the U.S. Before that, on August 28, SpaceXAI let Grok Bot buy things online through Link, with users approving every spend request and the Bot receiving a single use card for each payment.

Musk has already shown how far he wants users to push it. In late August, when Tesla investor account Teslaconomics said he was weighing whether to give Grok Bot access to his bank accounts, Musk replied, “Try it out. If Grok Bot messes up, we will make you whole.” That promise goes beyond SpaceXAI’s consumer terms, which make users responsible for what their agents do and generally cap the company’s liability at the greater of fees paid or $100. SpaceXAI’s own documentation recommends requiring approval for purchases and financial transfers.

For Tesla owners, the update lands five days after Tesla brought Grok Bot into its vehicles, letting drivers hand off errands by voice while FSD (Supervised) handles the road. Bot access inside the car is currently limited to SuperGrok Heavy subscribers, though Connectors are open to anyone signed into Grok. With Finance linked, a driver could ask for a spending summary or a check on upcoming bills during the commute.

Grok’s role in the car has grown quickly since Tesla’s Summer Update let it control cabin features by voice. We have been using Grok Bot in our own Tesla for several weeks, and here’s how our latest test went.

Advertisement
-
Continue Reading

Elon Musk

SpaceX just got the green light Starship has waited years for

The FAA has cleared Starship Flight 14, setting up SpaceX’s first orbital attempt on Monday.

Published

on

By

SpaceX has cleared the last regulatory hurdle standing between Starship and its first trip to orbit. The Federal Aviation Administration issued the launch license for Starship Flight 14 late Saturday, keeping the mission on track for liftoff Monday, September 28, from Pad 2 at Starbase, Texas.

The 75 minute launch window opens at 7:15 a.m. Central, and Boca Chica Beach closures are also scheduled for September 29 and 30 as backup dates. This will be Starship’s first revenue generating mission.

The license was the missing piece after SpaceX completed a full wet dress rehearsal with Booster 21 and Ship 41 on September 24. At the time, the company said the flight remained on track pending regulatory approval. Because Flight 14 flies an orbital profile, the FAA had to sign off on a modified license that met its safety, payload and financial responsibility requirements.

Observers combing through the new FAA paperwork also noticed that lightning no longer appears among Starship’s listed launch hazards. If that holds, it matters more for where Starship is headed than for Monday’s attempt. Florida and Louisiana, home to LC-39A and the planned Starbase Louisiana site, see some of the most frequent lightning in the United States.

SpaceX tells the FCC that Starship Flight 14 is going to orbit

Flight 14 is the mission SpaceX has been building toward for months. Ship 41 will carry 26 Starlink V3 satellites, the first operational V3 units to be deployed, and attempt roughly six orbits at about 275 kilometers over a flight lasting just under 10 hours. SpaceX says the ship will only perform its orbital insertion burn after flight controllers confirm enough hardware redundancy remains for the deorbit burn at the end of the mission. Ship 41 is targeting a splashdown in the Pacific west of Chile, while Super Heavy will return to the Gulf of Mexico.

The date carries some symbolism as well. A Monday launch would come 10 years and one day after Elon Musk first presented the Interplanetary Transport System, the design that became Starship, at the International Astronautical Congress in Guadalajara, Mexico.

Advertisement
-

SpaceX has not announced what comes next, but air traffic planning slides reported this week, list Flight 15 no earlier than October 19 and a first Starship launch from LC-39A in Florida no earlier than October 30. Both dates depend on how Monday goes.

Continue Reading

News

SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout

SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.

Published

on

By

US Golden Dome space defense system (Concept render by Grok)

SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.

Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.

USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.

Starlink’s Starshield wins contract with US Space Force

The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.

Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.

The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.

Continue Reading