News
SpaceX repairing heat shield, reinstalling Raptors on first orbital-class Starship
SpaceX has begun reinstalling three of the six Raptor engines that will power the first orbital-class Starship and repairing the heat shield that will hopefully protect it on its first trip to space.
Known as Starship 20 or S20, the 50m (~165 ft) tall steel rocket prototype has been stationed at one of SpaceX’s two suborbital testing pads since August 13th. No testing has been done, though, and a small army of SpaceX technicians and engineers have instead spent the last three or so weeks effectively turning a collection of steel tanks, tubes, and parts into a functional rocket. While it’s unclear why SpaceX chose to do that outfitting work at an unsheltered launch pad, new activity suggests that it may be almost complete.
Exactly one month ago, SpaceX stacked Starship S20 on top of Super Heavy Booster 4 (B4) on August 6th, briefly creating the largest rocket in history and completing a fit test that was admittedly just as much a photo op. Ship 20 was rapidly destacked and returned to SpaceX’s Starbase factory, where all six of its Raptor engines were removed. About a week later, Ship 20 returned to the pad and has remained installed on Suborbital Pad B ever since.
At the time, the implication was that SpaceX had removed Ship 20’s engines to allow the prototype to complete cryogenic proof testing with hydraulic thrust simulators. However, despite having carefully modified Pad B over several weeks for that exact purpose, those modifications were rapidly removed before Ship 20’s second rollout. Precluding a proof test with thrust simulation, the next logical conclusion was that SpaceX would still perform a cryogenic proof test before reinstalling Ship 20’s Raptors and moving on to a static fire campaign.
Now, even that appears to have been p1recluded. Instead, as if Ship 20 were the second or third or fourth in a series of prototypes, SpaceX rolled three center Raptors to Pad B on September 5th and began installing the engines on Starship on the 6th. It’s hard to say anything with confidence given how chaotically Starship S20’s to-be-determined qualification testing has changed in the last several weeks but, with plenty of uncertainty, Raptor installation implies that the vehicle will perform its first ambient pressure and cryogenic proof tests with engines installed.
It remains to be seen if Ship 20’s three vacuum-optimized Raptor engines will also be installed over the next few days (seemingly the logical assumption) or if SpaceX will instead complete proof tests and center Raptor static fire testing before finally moving into new territory. SpaceX has never static fired more than three Raptors at once and certainly never tested multiple Raptor Vacuum (RVac) engines in close proximity – let alone all six simultaneously.
Meanwhile, much of the focus of the last few weeks appears to have been on finishing Ship 20 plumbing and avionics wire runs, though it’s hard to say exactly what has been done. What is extremely visible and easy to follow, though, is the process of finishing the first orbital-class Starship heat shield and repairing a few hundred tiles broken during its pathfinder installation. SpaceX has installed 500-1000+ tiles on flown Starship prototypes like SN15 but the company has never come close to the ~15,000 needed to cover the entire windward side of the world’s largest rocket upper stage.
SpaceX has undertaken that process for the first time over the last six or so weeks and unsurprisingly seen a number of successes and failures. At some point along the way, a significant fraction of the ceramic, dinner-plate-sized tiles SpaceX technicians installed chipped, broke, shattered, or ran into other fitment issues. Over the last month or so, a great deal of progress has been made fixing those problem tiles and SpaceX has also more or less completed tile installation on the angular ‘aerocovers’ that protect Starship’s flap mechanisms – requiring dozens of custom tiles with complex shapes and curves.
As of September 6th, Starship S20’s heat shield appears to be around 95% complete and the installation of Raptor engines implies that the rocket’s plumbing, avionics, and tankage are also nearly finished. In other words, after many weeks of work, SpaceX’s first orbital-class Starship prototype could be ready to kick off cryoproof and static fire testing just a week or so (and maybe less) from now. Stay tuned for updates!
-
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
