News
Tesla starts disabling FSD Beta’s “rolling stop” feature with V10.10 update
Just as indicated in the National Highway Traffic Safety Administration’s (NHTSA) Safety Recall Report, Tesla has started rolling out an over-the-air software update that removes FSD Beta’s ability to perform “rolling stops.” The function was deemed by the NHTSA as a driving behavior that may increase the risk of collisions.
Images of FSD Beta 10.10’s release notes were recently shared online, hinting that the company is now actively addressing the issue outlined in the recent recall. It remains to be seen how long it would take Tesla to update its FSD Beta fleet to the new v10.10 software, especially since there are now nearly 60,000 drivers who are part of the early access program.
Following are the release notes of FSD Beta 10.10.
Early Access Program – FSD Beta 10.10
– Smoother fork maneuvers and turn-lane selection using high fidelity trajectory primitives.
– Disabled rolling-stop functionality in all FSD Profiles. This behavior used to allow the vehicle to roll through all-way-stop intersections, but only when several conditions were met, including: vehicle speed less than 5.6 mph, no relevant objects/pedestrians/bicyclists detected, sufficient visibility and all entering roads at the intersection have speed limits below 30 mph.
– Improved generalized static object network by 4% using improved ground truth trajectories.
– Improved smoothness when stopping for crossing objects at intersections by modeling soft and hard constraints to better represent urgency of the slowdown.
– Enabled lane changing into an oncoming lane to maneuver around static obstacles, when safe to do so.
– Improved smoothness for merge handling by enforcing more consistency with previous cycle’s speed control decisions.
– Improved handling of flashing red light traffic controls by adding more caution for events where crossing vehicles may not stop.
– Improved right of way understanding at intersections with better modeling of intersection extents.
A look at FSD Beta 10.10’s release notes suggests that Tesla’s “rolling stop” feature was not really as aggressive or dangerous as initially feared by critics. As noted by the company, FSD Beta’s “rolling stops” are only enabled when several conditions are met, and those conditions are fairly conservative. Tesla’s FSD Beta safety record would support this thesis, as the company noted in the NHTSA’s Safety Recall Report that it was not aware or any warranty claims, field reports, crashes, injuries, or fatalities that resulted from the advanced driver-assist system’s “rolling stop” function. “As of January 27, 2022, Tesla is not aware of any warranty claims, field reports, crashes, injuries or fatalities related to this condition,” the NHTSA’s report read.
While the removal of FSD Beta’s “rolling stop” feature was considered a recall of over 53,000 Teslas, the fact remains that the issue was completely addressed through a simple over-the-air update. Owners whose vehicles were part of the recall were also not required to do anything specific except to ensure that their vehicles were connected to the internet. This was something that was highlighted in the remedy for the issue indicated in the NHTSA’s Safety Recall Report.
“Tesla will disable the ‘rolling stop’ functionality on affected vehicles, starting with firmware release 2021.44.30.15. Firmware release 2021.44.30.15 is expected to begin deployment OTA to affected vehicles in early February 2022. The disablement will carry forward in firmware release 2021.44.30.15 and later releases. No further action is necessary from owners who install firmware release 2021.44.30.15 or a later release on their vehicles,” the NHTSA’s Safety Recall Report read.
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
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.
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.
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.
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.
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.
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.
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.
Watch Falcon 9 launch the USSF-385 mission from pad 4E in California https://t.co/CAdbx85Ydy
— SpaceX (@SpaceX) September 26, 2026
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.
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.
Elon Musk’s AI Grok Bot can now handle banking while your Tesla FSD handles the road
SpaceX just got the green light Starship has waited years for
