Tesla Full Self-Driving (FSD) Beta 10.69.3.1 has been out for some time now, and Teslarati talked to a few beta testers about the update.
Below are some notes and observations about v.10.69.3.1 from Tesla FSD Beta Testers.
FSD Beta 10.69.3.1 and Lanes
Lane selection has been one of the issues that most FSD Beta testers bring up when they talk to Teslarati. Before 10.69.3.1, FSD Beta reportedly had trouble understanding when to switch lanes, which one to switch to, or when to remain in a lane. FSD Beta testers are still experiencing lane selection issues.
“Not only has lane selection in anticipating a turn been a step back for me, lane selection whilst performing dual lane left-hand turns still suffer. The car doesn’t stay in its assigned lane but drifts. This does not happen on right turns,” said Les, a long-time FSD Beta tester.
“Lane selection still has issues. Most of the time it’s ok, but occasionally, it does strange things like changing into the right lane momentarily, then back to the left when there is an upcoming left-hand turn,” noted FSD Beta tester Sandy.
Turn Issues in FSD Beta 10.69.3.1
Les and fellow FSD Beta tester Sandy mentioned other lane issues related to turns. Les noted that one of the biggest step back with FSD Beta 10.69.3.1 occurs when the car faces an upcoming turn.
“On previous builds, the car would only occasionally move in the opposite lane direction of an upcoming turn. On this build, virtually every turn I had upcoming, when the car got within half a mile of said turn, it would signal and move into the lane of the opposite direction,” Les said.
“Virtually every right turn I’ve had upcoming, the car, inexplicably, signals and changes into the left-hand lane. Same for left-hand turns, within half a mile out the car signaled and changed into the right-hand lane. Confounding to say the least, to the point of comedy,” he added.
Sandy noticed that his car requires interventions or disconnects at stop signs sometimes. In the past, other FSD Beta testers have mentioned that their vehicle experiences jerky movements or their signal lights turn off and on during intersections, traffic lights, and stop signs. It’s as if the car is deciding whether the driver wants to turn or not.
“Following and lane changes seem smoother and more natural,” said Sandy. “However, it still has issues that require intervention/disconnects. When it creeps at stop signs, it can make jerky movements with steering wheel and, imo, it creeps to slowly and takes too long before proceeding.”
Mixed Reviews for 10.69.3.1
As with all of Tesla’s FSD Beta updates, there have been a few good reviews and bad ones. Beta testers tend to focus on the issues, as it is their responsibility to report them so Tesla can improve FSD. However, testers also report significant improvements they see during their drives.
In the case of 10.69.3.1, it seems like FSD Beta received mixed reviews. Some testers believed that the update significantly improved the advanced driver assist software while others thought it was a step back.
“I have tested the 10.69.3.1 build on my Model Y, and it’s a giant leap forward from builds prior to 10.69,” observed Tony, a Model Y owner and a member of the FSD Beta program.
Tony noted that the biggest changes were improvements to acceleration, smoother turns, and less necessary steering wheel input. Sandy also observed more improvements with Tesla FSD Beta 10.69.3.1 rather than issues.
On the other hand, Les believed that v.10.69.3.1 was a step back for FSD Beta.
“These 10.69.3.1 step backs are the biggest in my FSD Beta testing experience to date. Previous builds have been much better for me. But again, I understand the process; updates are sometimes “2 steps forward and 1 step back.” I still enjoy testing. The product isn’t finished yet,” he said.
Tesla FSD Beta Wide Release
Tesla started the wide release of FSD Beta v.10.69.3.1 in late November. A day after its release, Tesla rolled out FSD Beta to cars with less than 100 Autopilot miles and Safety Scores lower than 80.
The EV maker rolled out FSD Beta V11 to a few testers already. FSD Beta V11 is Tesla’s single-stack update. However, update 10.69.3.1 seems to be rolling out to more testers.
Tesla also made Full Self-Driving Beta available to anyone in North America who purchases it from their car screen. Now that Tesla has released FSD Beta to anyone in North America interested in trying it out, the company might want to streamline its performance. Based on Teslarati‘s interviews with FSD Beta Testers, the software performs differently based on location, driver, terrain, and other factors.
“Phantom braking on city streets (not highways) returned for me in one bizarre instance; it wasn’t the sudden hard kind of braking, rather this was a new braking behavior that was slow and gradual almost to a stop while I was going straight in the middle lane of a three-lane road. Not at a turn, wasn’t going through an intersection, and the road was clear,” described Les in one instance.
“There were no cars around me so I let the car do its thing to see what it was doing; it literally started slowing from 40mph to 5mph before I disengaged and accelerated back up to speed. Very weird. I went back to that spot a couple days later and the car didn’t do it. It acted normal,” he explained.
Tesla Full Self-Driving has not received regulatory approval yet. It still faces a lot of skepticism, especially in terms of safety. Delivering consistent, reliable performances in various driving situations might help it get regulatory approval.
Are you an FSD Beta tester? Have you tried out V11? If you have, I’d like to hear from you! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.
Investor's Corner
Tesla opens the Q&A for its biggest earnings call yet
Tesla opens its Q3 earnings Q&A, and Cybercab, Robotaxi, Optimus and regulators loom over October 21.
Tesla has opened its shareholder question portal for the Q3 2026 earnings call, with the Say Q&A page already listing questions. Investors have until 4:00 p.m. EDT on October 20 to submit and vote on what management should answer.
The call is set for Wednesday, October 21. Tesla will post results after the market closes, with a live webcast at 4:30 p.m. CT, or 5:30 p.m. ET, through its investor relations site.
Say ranks questions by the number of shares behind the votes, which gives institutional holders extra weight over the retail crowd.
Ahead of Q2, retail investors asked why Robotaxi growth had stalled, when Cybercab would start customer rides, and where the Optimus Gen 3 ramp stood, while an institutional holder asked how Tesla and SpaceX would split Terafab duties. Cybercab has since answered one of those. Tesla said last week it has 300 plus Cybercabs serving Austin, up eightfold in 30 days, with Dallas named as the next city. The questions now are likely to move from when to how fast.
There is also a regulatory question hanging over the call. NHTSA has demanded sworn answers on how the pedal free Cybercab was certified against federal safety standards, with responses due October 30, nine days after the call. Whether an analyst raises it live is unknown, but it is the kind of exposure that tends to find its way into a Q&A.
The numbers will not be the main draw. Tesla already reported 486,532 deliveries and 13.7 GWh of storage for the quarter. Consensus sits around 43 to 45 cents per share on roughly $27.8 billion in revenue, according to Zacks, after a Q2 report that missed on EPS. Goldman Sachs, which holds a Neutral rating and a $360 target, argues the outlook for Robotaxi, FSD and Optimus will matter more to the stock than the quarter itself.
The call also lands six days after the rescheduled Roadster event, which Tesla will stream on X on Thursday, October 15, at 7:55 p.m. CT. If the Roadster shows up with a production date or a SpaceX thruster package, expect it to climb the voting list before the deadline.
Elon Musk
Ukraine says Starlink is cutting out its military drones as Poland calls out Elon Musk
Ukrainian officials allege SpaceX limited military Starlink speeds, disrupting drone missions; SpaceX has not commented.
Ukrainian officials are accusing SpaceX of placing a speed limit on the military version of Starlink that their forces use to fly drones, but SpaceX has not confirmed that any change was made. Presidential adviser Serhiy Beskrestnov said in a Telegram post on Wednesday that Starshield terminals have begun losing service when they move faster than about 100 miles per hour, according to a Reuters report. “Our defense forces did not receive a warning about this limitation, and this led to the disruption of several missions,” he wrote.
Ukraine’s 7th Rapid Reaction Corps told Reuters that connections dropped for 10 to 20 seconds at just 68 to 75 mph, which made the drones harder to control. Volunteer Serhiy Sternenko, citing military reports, said the dropouts are now starting at 37 to 43 mph. These accounts come from Ukrainian officials and military sources and have not been independently verified. Regular civilian terminals were reportedly not affected, according to EUalive.
.@POTUS: We told Zelensky, ‘You can do whatever you want to Russia, but don’t hit the refineries because that’s a world problem.’ And what does he do? He goes and hits the diesel fuel. He better damn well stop. https://t.co/CdRlMcPlKr
— Rapid Response 47 (@RapidResponse47) October 10, 2026
SpaceX has not publicly commented or explained what, if anything, changed. Beskrestnov and other Ukrainian officials believe the issue is intentional and point to the timing. Washington has been pressing Kyiv to stop long range strikes on Russian oil refineries after President Trump called for an “energy ceasefire,” and Musk posted on Saturday that “Zelensky has gone too far.” EUalive noted that neither Ukrainian nor Polish officials have presented evidence that the limit was ordered by Washington or by SpaceX, so the link to politics remains an allegation. Other explanations, such as a technical or policy change affecting fast moving terminals, have not been ruled out.
Poland’s foreign minister, Radosław Sikorski, responded on X by quote tweeting a Kyiv Independent report and writing: “Hey, @elonmusk, big man, are you playing politics with your products again? As your European customers, we are watching you.” Poland is the largest funder of Ukraine’s Starlink service, having supplied more than 29,000 terminals and covering operating costs Sikorski has put at roughly $50 million a year. The wording echoes their 2025 clash, when Musk told Sikorski to “be quiet, small man.” At the time of writing, neither Musk nor SpaceX had responded to the claims.
Hey, @elonmusk, big man, are you playing politics with your products again?
As your European customers, we are watching you.— Radosław Sikorski 🇵🇱🇪🇺 (@sikorskiradek) October 14, 2026
The dispute sits on top of a long history. Musk confirmed in February 2022 that Starlink was active in Ukraine after a request from a Ukrainian minister. That October, SpaceX asked the Pentagon to share the bill and Musk said the cost was approaching $20 million a month, before he reversed course and said SpaceX would keep paying. In December 2024 the Pentagon moved some of those terminals onto the Starshield service, the government version now at the center of the complaints.
SpaceX has also changed how its network treats certain terminals in Ukraine before, and that time it was with Kyiv’s cooperation. In February, Ukrainian officials confirmed that terminals believed to be used by Russian troops were disabled after coordination with SpaceX, a step that Ukrainian commanders later said hurt Russian assaults. Whether anything similar is behind the latest reports is unclear, which is why Kyiv is asking for answers.
Ukraine is already looking at backups. Defense tech company Stetman is developing its own satellite system, UASAT-NANO, and officials in Europe have discussed alternatives to Starlink since early 2025, though none match its scale yet.
Elon Musk
FAA kicks off review of SpaceX’s bid to fly Starship nearly every day
FAA is reviewing SpaceX’s plan for 456 Starship launches a year, up from 25 today.
The FAA said Tuesday that it will prepare an environmental impact statement on SpaceX’s proposal to run as many as 456 Starship launches and 912 landings a year from Starbase, Texas. SpaceX is currently authorized for 25 launches and 50 landings annually, which makes the request roughly 18 times the existing ceiling. The notice of intent is set to publish in the Federal Register on Wednesday.
The plan comes in two phases. Phase 1 would allow up to 100 launches and 200 landings a year, on any day and at any hour. Phase 2, which the FAA says could arrive within several years, would raise the limit to the full 456 launches, still at any hour but only on weekdays. The agency noted that 912 landings is the upper limit for the Texas facility no matter where a given mission begins, and that Starship and Super Heavy could come down at the launch site or in the Gulf and open ocean.
A draft statement will be released for public comment at a later date, and the FAA has not said when. According to the Federal Registar, written comments are due November 30 on regulations.gov under docket FAA-2026-12808, with in person scoping meetings on November 17 in Brownsville and November 19 in Port Isabel, plus a virtual session on November 18. The review will weigh air quality, wildlife, coastal resources, water, noise, and aviation, and the FAA said any increase beyond this proposal would need its own separate review.
The numbers look large next to what Starbase has actually done. Starship has flown three times from Texas this year, including Flight 14 on September 28, the first orbital flight, which deployed 26 Starlink V3 satellites. Bloomberg reported that Starbase has never launched more than five times in a calendar year. The current cap of 25 comes from an FAA approval in May 2025. In February, the agency also approved up to 44 Starship launches a year from Launch Complex 39A in Florida, so Phase 1 in Texas alone would more than double that allowance.
Musk has said Starship could eventually fly more than once per hour within less than a decade, per Bloomberg. The nearer term target is Flight 15. Musk said on October 10 that it is hopefully four to six weeks away and will try to catch the ship with the tower, as Teslarati covered. That flight still runs under the existing 25 launch limit, and so would every Starbase launch for as long as the new review takes.
As of mid morning Pacific time on Tuesday, SpaceX had not posted about the filing on its own account.