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.
News
NHTSA just escalated its Tesla Cybercab investigation in a big way
NHTSA escalated its Cybercab audit into a sworn Special Order with a September 30 deadline.
Federal regulators have moved from asking Tesla questions about its Cybercab to demanding sworn answers. The National Highway Traffic Safety Administration issued a Special Order that requires a Tesla officer to sign an affidavit attesting to the completeness of the company’s responses, with a deadline of September 30.
The order builds on Audit Query AQ26002, which NHTSA opened on September 3, the same day Tesla began commercial Cybercab service in Austin. Teslarati covered that initial inquiry when it surfaced, noting the agency wanted to understand how Tesla certified a vehicle with no permanently attached steering wheel, pedals, or mirrors as compliant with Federal Motor Vehicle Safety Standards. A Special Order is a different tool and converts a fact finding review into a legally enforceable demand, the same mechanism NHTSA used against Tesla in 2023 during its Autopilot investigation.
Several of the 21 requests target a specific gap in Cybercab’s design. One asks whether Tesla used temporarily attached human controls at any point to help certify the vehicle, and if so, which standards depended on that equipment being present. Another quotes an existing rule directly: “The service brakes shall be activated by means of a foot control.” Cybercab has no foot pedal. NHTSA wants a detailed explanation of how the vehicle satisfies that requirement, and how it complies without the kind of exemption granted to Zoox in July under Part 555, the regulatory pathway built for steering wheel free vehicles.
The order does not claim Cybercab is unsafe or that Tesla broke a rule. It requires Tesla to explain, under oath, the reasoning behind decisions the company already made when it self-certified the vehicle. That distinction matters, but so does the exposure. Motor1’s reporting, summarized here, put potential civil penalty exposure as high as $139 million if NHTSA later finds the certification was flawed, on top of whatever criminal risk comes with a false sworn statement.
Tesla has not said publicly how it plans to respond. Cybercab is still carrying passengers in Austin through the Robotaxi app while the September 30 deadline approaches, and the company has continued expanding the vehicle’s footprint even as the regulatory question remains open. The Special Order does not pause any of that and just sets a date by which Tesla has to put its certification logic on the record, with a company officer’s name attached to it.
Investor's Corner
Tesla uber bull Ron Baron says ‘the time to buy the stock is now’
In a new interview on Wednesday, Tesla uber bull Ron Baron said that anyone looking to buy the company’s stock should do so as soon as they can.
Baron, founder and CEO of Baron Capital and one of Tesla’s most persistent institutional bulls, used a CNBC Squawk Box appearance on Wednesday to deliver a familiar message with fresh urgency: In his opinion, Tesla stock is a buy:
“The time to buy the stock is now. FSD is catching on, and it’s going to be bigger and bigger. 55% of new buyers are buying it (Teslas) with FSD. It’s going to be everywhere. It’s safer.”
The Baron Capital frontman’s case is built around Full Self-Driving. Tesla reported 1.48 million active FSD subscriptions in the second quarter, up 56 percent year over year, and company officials have said roughly 55 percent of new North American deliveries left with a subscription enabled.
Baron framed that attach rate as proof the product is moving from enthusiast extra to default expectation, and as a reason software, not just vehicle volume, should drive the next phase of value.
His conviction on Tesla shares is not theoretical, as Baron Capital made its first Tesla investment in 2014, after years of meetings that began around the 2010 IPO roadshow. The firm later built a large SpaceX position starting in 2017.
Ron Baron today in new interview on Tesla:
“The time to buy the stock is now. FSD is catching on, and it’s going to be bigger and bigger. 55% of new buyers are buying it (Teslas) with FSD. It’s going to be everywhere. It’s safer.” pic.twitter.com/Rv5PB0bVZ2
— Sawyer Merritt (@SawyerMerritt) September 16, 2026
Baron said those Musk-led bets have generated about $30 billion of the $71 billion in profits Baron Capital has produced for clients. He put the firm’s current exposure at roughly $25 billion in SpaceX and $5 billion in Tesla. Personally, he described SpaceX as his largest holding, at about $5 billion, with about $1.5 billion in Tesla and additional Tesla exposure through the firm’s funds.
That concentration is also a statement of loyalty. Asked about talk of a SpaceX-Tesla combination, Baron said he had already walked Elon Musk through arguments for and against a deal, then declined to repeat them on air. His public position was simpler: “Whatever you decide is better is what I’m going to support,” he said to Musk.
Baron also said that he picked up the farewell edition of the Model S after Tesla decided to sunset the vehicle earlier this year, calling it his favorite car he’s ever driven.
Elon Musk
SpaceX’s next Starship launch is about to attempt its biggest leap yet
SpaceX targets September 22 for Starship Flight 14, its first attempt to reach real orbit.
SpaceX has set September 22 as the target date for Starship’s 14th test flight, and this one carries a different goal than any of the 13 that came before it. Every previous Starship mission has intentionally flown a suborbital arc, reentering the atmosphere within the same hour it launched. Flight 14 is designed to send the craft into a genuine orbit around Earth for the first time.
The launch window opens at 7:15 a.m. Central time at Starbase in South Texas and runs for 75 minutes, pending regulatory approval, according to SpaceX’s mission description published Tuesday. If the flight goes as planned, Starship will circle the planet roughly six times at an altitude near 275 kilometers over about ten hours before a deorbit burn sends it toward a splashdown in the Pacific Ocean west of Chile, a departure from the Indian Ocean recoveries used on the last several flights.
The mission also marks the first attempt to put a working batch of Starlink V3 satellites into actual service. Flight 13 carried 20 of the new satellites in July, but because that mission never left a suborbital trajectory, the payload reentered along with the ship instead of separating into orbit.
SpaceX tells the FCC that Starship Flight 14 is going to orbit
Each V3 satellite is rated for roughly one terabit per second of downlink capacity, so a successful deployment on Flight 14 would be SpaceX’s largest single jump in network bandwidth since Starlink began flying on Falcon 9.
Flight 13 still did the heavier lifting on the technical side. That July mission flew a deliberately more stressful reentry profile to test Starship’s heat shield, and the ship survived its softest splashdown yet, intact enough for drone inspections shortly after landing. Elon Musk said the flight delivered “all the heat shield data we needed and then some,” a result Teslarati covered in detail when he later said SpaceX had solved the vehicle’s biggest reusability challenge. Flight 14 is where SpaceX starts spending that confidence on an actual orbital insertion rather than another controlled fall back to Earth.
One thing Flight 14 will not attempt is a tower catch of the ship. Musk floated the idea right after Flight 13, but walked the timeline back in August, saying a catch attempt was more likely “in a few months.” The Super Heavy booster will still aim for its own recovery, targeting an offshore landing point in the Gulf of America, the same approach used on recent flights.
September 22 is SpaceX’s own target, not a locked date. Starship’s schedule has slipped before over hardware readiness and FAA sign off, and the company has said as much in its own mission notes. But the plan itself represents the clearest marker yet that Starship is moving from a suborbital test program into something meant to carry paying payloads and, eventually, people.