News
SpaceX fully stacks Starship rocket for the first time in six months
For the first time in more than six months, SpaceX has stacked both stages of its next-generation Starship rocket, creating the largest and most powerful launch vehicle ever fully assembled.
It’s not the first time. SpaceX has conducted three other ‘full-stack’ Starship demonstrations: once in August 2021 and again in February and March 2022. But earlier this year, SpaceX (or at least CEO Elon Musk) decided to give up on the Starship upper stage and Super Heavy booster prototypes that had supported all three of those prior tests and, at one point, been considered a candidate for the rocket’s first orbital launch attempt. Booster 4 and Ship 20 were consigned to a retirement yard by June 2022.
By then, SpaceX had already begun testing the new favorites for Starship’s orbital launch debut: Super Heavy Booster 7 (B7) and Starship 24 (S24). Almost exactly six months after the start of that busy period of testing, both prototypes recently reached the point where SpaceX was confident enough in their progress to combine the two for the most challenging phase of Starship testing yet.
After an aborted predawn attempt on October 11th, SpaceX technicians worked out some mystery kinks in crucial infrastructure located at Starship’s first (nearly) finished orbital launch pad in Boca Chica, Texas. As part of a cart-before-horse gamble made by CEO Elon Musk that has seen SpaceX entirely remove legs from all recent Starship and Super Heavy prototypes in the hope that it will one day be able to catch the building-sized rocket stages out of mid-air, the company has built a launch tower ~145 meters (~475 ft) tall and outfitted it with three giant robotic arms. Two of those arms are identical and linked together, forming a sort of claw that could one day close around hovering rockets to preclude the need for landing legs. A simpler third arm swings in and out to connect Starship’s upper stage to the launch pad’s power, propellant, and gas supplies.
The ‘chopsticks,’ as they’re known, have another even more important purpose: assembling Starship rockets at the launch pad. Thanks to their sturdy connection to a tower with a foundation sunk deep into the Boca Chica wetlands and a design that forgoes a hanging hook or jig for giant arms, they are far less sensitive to winds than the immense crane otherwise required to stack Starship on top of Super Heavy. Sitting a stone’s throw from the Gulf of Mexico, storms and high winds are not exactly uncommon.
Around sunset on October 11th, SpaceX had better luck on its third attempt and was able to move the arms into place under Ship 24. Weighing 100 tons or more (~220,000+ lb) and measuring nine meters (~30 ft) wide and ~50 meters (~165 ft) tall, the Starship was then slowly lifted about 80 meters (~250 ft) off the ground, translated over to Booster 7, and lowered on top of the 69-meter-tall (~225 ft) first stage. After about two more hours of robotically tweaking their positions, the two Starship stages were finally secured together. With the arms still attached to Ship 24, SpaceX workers were able to approach the rocket and prepare to connect the swing arm’s quick-disconnect umbilical to Starship.
Since they began qualification testing in April and May 2022, Booster 7 and Ship 24 have each completed several cryogenic proof tests, eight ‘spin-primes’ of some or all of their Raptor engines, and several static fires of those same engines. Most recently, Ship 24 ignited all six of its Raptors, but the seemingly successful September 8th test was followed by more than a month of apparent repairs. Booster 7 last completed a static fire that ignited a record seven of its 33 Raptor engines – offering an idea of how much further SpaceX still has to go to finish testing the Super Heavy.
According to CEO Elon Musk, Booster 7 and Ship 24 will attempt Starship’s first full-stack wet dress rehearsal (WDR) once all is in order. The prototypes will be simultaneously loaded with around 5000 tons (~11M lb) of liquid oxygen and methane propellant and then run through a launch countdown. Diverging just before ignition and liftoff, a WDR is meant to be more or less identical to a launch attempt.
-
If the wet dress rehearsal goes to plan, SpaceX will then attempt to simultaneously ignite all 33 of the Raptor engines installed on Super Heavy B7, almost certainly making it the most powerful liquid rocket ever tested. Even if all 33 engines never reach more than 60% of their maximum thrust of 230 tons (~510,000 lbf), they will likely break the Soviet N-1 rocket’s record of 4500 tons of thrust (~10M lbf) at sea level. It would also be the most rocket engines ever simultaneously ignited on one vehicle. SpaceX will be pushing the envelope by several measures, and success is far from guaranteed.
It’s unclear if SpaceX will immediately attempt a full wet dress rehearsal or 33-engine static fire. Based on the history of Ship 24 and Booster 7 testing, it would be a departure from the norm if the company doesn’t slowly build up to both major milestones with smaller tests in the interim. At minimum, assuming WDR testing is completed without major issue, SpaceX will likely attempt at least one or more interim static fires with fewer than 33 engines before attempting the first full test.
If both milestones (a full WDR and 33-engine static fire) are completed without significant issue, there’s a chance that SpaceX could move directly into preparations for Starship’s first orbital launch attempt without unstacking the rocket. In the likelier scenario that some issues arise and some repairs are required, the path will be more circuitous but should still end in an orbital launch attempt late this year or early next.
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.
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.
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.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
