News
SpaceX starts stacking Starship’s first orbital-class Super Heavy booster
By all appearances, SpaceX has begun the process of stacking what could become the first Super Heavy booster capable of supporting orbital Starship test flights.
Known as booster number 3 (BN3), numerous sections of the 70-meter-tall (230 ft) steel rocket have been spotted at SpaceX’s Boca Chica, Texas factory over the last six or so weeks – adding up to a substantial portion of what is now expected to be the first flightworthy Super Heavy. Earlier this year, SpaceX stacked Super Heavy BN1 to its full height but late design changes effectively rendered the prototype largely irrelevant and turned it into more of a manufacturing pathfinder and source of practice than anything else.
As a result, BN1 never even left the high bay it was built in before SpaceX workers cut the booster into scrap. As of May, while a handful of parts for booster number 2 have been spotted, signs indicate that BN2 will be turned into a small test tank to qualify Super Heavy’s complex and unproven thrust dome and engine section.
That leaves Super Heavy BN3. According to NASASpaceflight.com, SpaceX has nominally assigned booster BN3 to support Starship SN20 on its inaugural space launch attempt. Just last week, SpaceX filed an application with the FCC for permission to communicate with Starship and Super Heavy during that “orbital test flight” – paperwork that included a six-month launch window scheduled to open no earlier than June 20th.
If approved by the FCC and – far more importantly – the FAA, Starship’s first “orbital test flight” will circumnavigate three-quarters of the world in approximately 90 minutes, launching from Boca Chica and ending – if all goes well – with Starship SN20 gently splashing down near Kauai, Hawai’i. From the sparse documentation SpaceX included in the public application, it’s ambiguous if there will be an attempt to recover Super Heavy booster BN3 or if the test flight will actually be orbital, given that Starship SN20 wont complete a full orbit.
Technically speaking, although a Starship capable of safely launching from Texas to Hawai’i is almost unequivocally capable of reaching orbit, the safest possible “orbital” flight test for such a massive spacecraft would stop just shy of orbit. A guaranteed free-return reentry would make it almost impossible for Starship to reach orbit, fail to deorbit after its first ~90 minutes in space, and end up posing a risk to populated areas – like, say, the now-infamous boosters of China’s Long March 5B rocket. Regardless, it’s clear that the specifics of Starship’s first spaceflight attempt are still very much up in the air and liable to change over the next few weeks.



What isn’t up in the air is the fact that SpaceX will need to all but fully assemble and test Super Heavy booster BN3 and Starship SN20 before any potential space shot. Along those lines, SpaceX still has a huge amount of work to do. Per Twitter user Brendan Lewis’ accounting, SpaceX has at least six BN3 sections – amounting to 22 rings and two of three tank domes – either completed or awaiting integration. The process of stacking BN3 began sometime in the last 7-10 days when SpaceX joined two four-ring sections – including the booster’s common dome, likely pictured above.


SpaceX has mostly completed BN3’s engine section, including a thrust dome with plumbing cutouts for a full 28 Raptor engines. Most recently, what looks like a Super Heavy fuel manifold appeared in Boca Chica. That manifold will attach to the end of a supersized Super Heavy transfer tube – also spotted in work – used to route methane through the liquid oxygen tank to fuel its Raptor engines. Fueling 28 large, high-performance Raptors is no mean feat and requires a rat’s nest of plumbing to feed them more than 15 metric tons (~30,000 lb) of propellant every second at full throttle.
Put simply, a majority of Super Heavy booster BN3’s hardware appears to be ready or almost ready for integration. The eight rings now stacked represent approximately 20% of the rocket’s full height, leaving another 30 or so rings – 54m (~180 ft) – to go. Given how long BN1 assembly took SpaceX, the company has its work cut out for it to fully integrate BN3 by June 20th, and the first operational Super Heavy prototype will almost certainly need to complete several major tests before being cleared for flight. As such, an inaugural space launch attempt in June or July is wildly implausible, but it’s far from out of the question that Starship and Super Heavy could be ready for their first “orbital test flight” before summer turns to fall.
News
Tesla briefly offered this Robotaxi part for your personal car
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
News
Tesla Robotaxi gets sweeping but polarizing change
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

