The release notes for Tesla FSD Beta V11.3 have been shared online. Observers from the electric vehicle community suggest that Tesla Full Self-Driving Beta 11.3 is rolling out to the company’s employee FSD Beta testers, at least for now.
The following are Tesla’s FSD Beta V11.3 release notes:
- Enabled FSD Beta on highway. This unifies the vision and planning stack on and off-highway and replaces the legacy highway stack, which is over four years old. The legacy highway stack still relies on several single-camera and single-frame networks, and was setup to handle simple lane-specific maneuvers. FSD Beta’s multi-camera video networks and next-gen planner, that allows for more complex agent interactions with less reliance on lanes, make way for adding more intelligent behaviors, smoother control and better decision making.
- Added voice drive-notes. After an intervention, you can now send Tesla an anonymous voice message describing your experience to help improve Autopilot.
- Expanded Automatic Emergency Braking (AEB) to handle vehicles that cross ego’s path. This includes cases where other vehicles run their red light or turn across ego’s path, stealing the right-of-way.
- Replay of previous collisions of this type suggests that 49% of the events would be mitigated by the new behavior. This improvement is now active in both manual driving and autopilot operation.
- Improved autopilot reaction time to red light runners and stop sign runners by 500ms, by increased reliance on object’s instantaneous kinematics along with trajectory estimates.
- Added a long-range highway lanes network to enable earlier response to blocked lanes and high curvature.
- Reduced goal pose prediction error for candidate trajectory neural network by 40% and reduced runtime by 3X. This was achieved by improving the dataset using heavier and more robust offline optimization, increasing the size of this improved dataset by 4X, and implementing a better architecture and feature space.
- Improved occupancy network detections by oversampling on 180K challenging videos including rain reflections, road debris, and high curvature.
- Improved recall for close-by cut-in cases by 20% by adding 40k autolabeled fleet clips of this scenario to the dataset. Also improved handling of cut-in cases by improved modeling of their motion into ego’s lane, leveraging the same for smoother lateral and longitudinal control for cut-in objects.
- Added “lane guidance module and perceptual loss to the Road Edges and Lines network, improving the absolute recall of lines by 6% and the absolute recall of road edges by 7%.
- Improved overall geometry and stability of lane predictions by updating the “lane guidance” module representation with information relevant to predicting crossing and oncoming lanes.
- Improved handling through high speed and high curvature scenarios by offsetting towards inner lane lines.
- Improved lane changes, including: earlier detection and handling for simultaneous lane changes, better gap selection when approaching deadlines, better integration between speed-based and nav-based lane change decisions and more differentiation between the FSD driving profiles with respect to speed lane changes.
- Improved longitudinal control response smoothness when following lead vehicles by better modeling the possible effect of lead vehicles’ brake lights on their future speed profiles.
- Improved detection of rare objects by 18% and reduced the depth error to large trucks by 9%, primarily from migrating to more densely supervised autolabeled datasets.
- Improved semantic detections for school busses by 12% and vehicles transitioning from stationary-to-driving by 15%. This was achieved by improving dataset label accuracy and increasing dataset size by 5%.
- Improved decision making at crosswalks by leveraging neural network based ego trajectory estimation in place of approximated kinematic models.
- Improved reliability and smoothness of merge control, by deprecating legacy merge region tasks in favor of merge topologies derived from vector lanes.
- Unlocked longer fleet telemetry clips (by up to 26%) by balancing compressed IPC buffers and optimized write scheduling across twin SOCs.
Here are the V11.3 release notes again if you haven't seen them. Very happy to see improvements in rain reflections as that was rare, but could give some insane errors #FSDBeta @elonmusk pic.twitter.com/ZIOcIhmUMd
— Dirty Tesla (@DirtyTesLa) February 20, 2023
Several longtime FSD Beta testers have pointed out some key improvements that would likely be very appreciated by users in V11.3. These include the systems’ improved handling through high speed and high curvature scenarios, as well as improvements to Automatic Emergency Braking (AEB). With the improvements in place, FSD Beta V11.3 would behave closer to a proper human driver.
Comments from longtime Tesla FSD Beta testers also suggest that V11.3 is still only being released for company employees for now. Considering Tesla’s past updates, it would not be surprising if the greater FSD Beta fleet gets the V11.3 update in the coming week or so. This is, of course, unless V11.3 ends up going the way of FSD Beta V11, which was released to employees in November but not to the greater fleet of FSD Beta testers.
The Teslarati team would appreciate hearing from you. If you have any tips, 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.