News
SpaceX’s Starship rocket sails through first “flight-like” fueling test
SpaceX’s fully-assembled Starship rocket appears to have sailed through a major wet dress rehearsal test on the first attempt.
With the completion of that test, the next-generation SpaceX rocket has taken a big step toward its first orbital launch attempt. Starship measures around 120 meters (~394 ft) tall and 9 meters (~30 ft) wide, making it the largest rocket ever assembled. It’s designed to launch more than 100 metric tons (~220,000 lb) to low Earth orbit (LEO) in a fully-reusable configuration. At liftoff, Starship’s 33 Raptor engines will produce up to 7590 tons (16.7M lbf) of thrust, making it more powerful than any rocket in history by a large margin.
And on Monday, January 23rd, Starship likely became the heaviest rocket ever after SpaceX fully loaded the vehicle with propellant. Surprising most viewers, SpaceX also appeared to complete the complex test associated with that milestone without running into any major issues.
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
The apparent success is surprising because it simply hasn’t been SpaceX’s approach of choice while developing Starship. Since SpaceX began assembling Starhopper in an empty Texas field in 2018, the Starship program has been almost exclusively managed to prioritize speed and expect failures. The company almost always preferred to build, test, and learn from minimum-viable-product prototypes as quickly as possible, even if that meant that failures were guaranteed.
Because SpaceX expected failures, it learned from them and always had another prototype ready to carry the torch forward. Starship prototypes rarely completed ground or flight tests on the first try, as SpaceX was simultaneously learning – often catastrophically – how to test and operate those vehicles. The culmination of that failure-as-an-option strategy was a series of seven suborbital Starship tests – two short hops of identical prototypes and five launch and landing attempts of five more advanced prototypes between August 2020 and May 2021. On the fifth attempt, after four failures, a full-scale Starship successfully launched to 12.5 kilometers (~41,000 ft), shut off its engines, fell back to Earth, reignited its engines, flipped around, and landed in one piece.
By all appearances, the campaign was the ultimate corroboration of SpaceX’s development strategy. In the second half of 2022, however, SpaceX decided to dramatically change the Starship program’s approach to risk management and systems engineering. Starship testing has become exceptionally cautious over the last several months, as a result.
From fail-fast to slow-and-steady
There is a small chance SpaceX simply got lucky, but Starship’s first fully-assembled wet dress rehearsal test appears to indicate that that caution has paid off. Combined, both stages of the rocket – Ship 24 and Booster 7 – collectively completed dozens of separate proof tests and static fires since mid-2022. They also made it through several far more limited tests while stacked.
Having cautiously characterized each prototype about as well as it possibly could, SpaceX finally pulled the trigger on January 23rd. After hours of conditioning the Starbase, Texas orbital launch site’s giant tank farm, SpaceX opened the floodgates and loaded Ship 24 and Booster 7 with up to 4860 tons (~10.7M lbs) of cryogenic liquid oxygen and liquid methane propellant in about 90 minutes. Once fully loaded, the combined weight of the rocket and propellant likely exceeded 5000 tons (~11M lbs), making Starship the heaviest rocket in history. The next heaviest rockets ever built, Saturn V and N-1, weighed around 2800 tons (~6.2M lbs) fully loaded.
SpaceX was also able to drain Starship and return its propellant to the pad’s ground storage tanks about four hours after filling the rocket.
“Flight-like” testing
The company later confirmed that the test was a “full flight-like wet dress rehearsal,” as suspected, and noted that data gathered from it would “help verify a full launch countdown sequence, as well as the performance of Starship and the orbital pad for flight-like operations.” Parts of the test visible from unaffiliated webcasts like NASASpaceflight’s seemed to confirm as much. Shortly after Starship was fully loaded, for example, SpaceX activated the orbital launch mount’s fire extinguisher system, seemingly practicing the moments before the rocket would otherwise ignite its engines and take flight.
At no point during the wet dress rehearsal did SpaceX appear to enter any kind of hold or abort, indicating that the rocket’s systems were all working well enough together to smoothly complete it on the first try. The only mildly concerning behavior visible during the multi-hour test came shortly after Starship was topped off. Booster 7 opened one of its methane tank gas vents to relieve pressure and instead appeared to vent liquid methane, producing a flammable cloud thousands of feet long. More likely than not, the Super Heavy was slightly overfilled, and the liquid vent was an intentional response to that error. The cloud of methane thankfully did not find an ignition source, and Starship went on to finish the test as planned.
SpaceX has a lot of work left to prepare Ship 24 and Booster 7 for Starship’s first orbital launch attempt. Booster 7 must still complete one or several more static fires, during which it could become the most powerful rocket ever tested. To reduce risk, SpaceX will likely remove Ship 24 while testing Super Heavy, and reassemble the rocket only if Booster 7 passes its tests. SpaceX also needs to repair the pad after static fire testing and work with the Federal Aviation Administration (FAA) to finalize Starship’s first orbital launch license.
But after many false positives, Starship’s successful completion of a wet dress rehearsal on the first try has confirmed that the rocket’s orbital launch debut is – for the first time – actually close at hand.
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.

