Connect with us

News

SpaceX shuffles Starships, gears up for more Super Heavy static fires

Published

4 years ago

on

SpaceX is busy preparing for the orbital launch debut its next-generation Starship rocket, but the company’s South Texas rocket factory is also working around the clock to prepare several more sets of ships and boosters for the flight testing that will follow.

That was more obvious than usual on November 8th, when SpaceX made moves to prepare both of its finished Starships for new phases of testing. SpaceX kicked off the busy day by removing Starship S25 – a newer prototype that arrived at the launch site just three weeks prior – a stand dedicated to proof testing ships. Three hours later, after spending three of the last four weeks sitting on top of Super Heavy Booster 7, Starship S24 was ‘destacked’ (lifted off of B7 and lowered onto a stand on the ground) in the early afternoon.

Booster 7, Ship 24, and Ship 25 have all been busy since mid-October. SpaceX stacked Booster 7 and Ship 24 for the first time on October 11th and then attempted to test the fully-stacked rocket on October 13th. By some accounts, although almost nothing was visible to the public, the first full-stack test may have gone poorly, potentially even endangering pad technicians that approached the rocket to troubleshoot. On October 16th, SpaceX fully destacked Ship 24, and CEO Elon Musk noted that the company was “proceeding very carefully” to avoid an explosion that could set “Starship progress back by ~6 months.”

But if there was a major issue on October 13th, SpaceX didn’t show it, and Ship 24 was reinstalled atop Booster 7 on October 20th without any obvious maintenance or repairs. SpaceX then kicked off an unusual series of tests on October 24th, during which it only filled the liquid oxygen (LOx) or liquid methane (LCH4) tanks of Super Heavy B7, Ship 24, or both vehicles at once. A rare NASA briefing on October 31st later called them “single-species prop[ellant]” tests – a kind of extra-cautious testing that had never been seen before at Starbase. A few days prior, a member of NASA’s Aerospace Safety Advisory Panel (ASAP) noted that an accidental explosion that damaged Booster 7 in July had caused SpaceX to “increase [the rigor of its] systems engineering and risk management,” explaining the sudden influx of unusually conservative testing.

By the time Ship 24 was destacked from Booster 7 on November 8th, SpaceX had completed seven single-species tests, four of which involved loading LOx or LCH4 into both stages and three of which only tested Super Heavy. Booster 7 and Ship 24’s tanks were fully filled and LCH4 and LOx were never simultaneously loaded on either stage.

NASA’s October 31st briefing reported that SpaceX had plans to destack Ship 24 before conducting additional static fire testing with Booster 7. While B7 completed 1, 3, and 7-engine static fires in August and September, those tests were nowhere close to the full 33-engine static fire required to properly qualify the most powerful rocket in history. According to NASASpaceflight.com managing editor Chris Bergin, SpaceX’s next goal is to fire up approximately half of Super Heavy B7’s Raptors.

Strangely, although Ship 24 was believed to have completed all of the standalone testing needed to clear it for flight, SpaceX installed the vehicle on a stand used for Starship static fire testing on November 9th, implying that more standalone testing may be required. For now, that shouldn’t pose a problem as long as SpaceX wraps up any additional Starship testing around the same time as Booster 7’s next static fire campaign wraps up, but it could delay full-stack launch readiness if it takes any longer.

Advertisement
-
-

Finally, after Ship 25 was removed from SpaceX’s other Starship test stand on November 8th, it was rolled back to Starbase’s Starship factory. Ship 25 first rolled to the launch site on October 19th and has since completed four visible tests. On October 28th, Ship 25 survived a pneumatic proof test that showed that its tanks were leak-free and capable of surviving flight pressures (roughly 6-8.5 bar or 90-125 psi). Three cryogenic proof tests followed on November 1st, 2nd, and 7th. The first cryoproof was likely just that – a test that pressurized Ship 25’s tanks and filled them with cryogenic liquid nitrogen (LN2) or a combination of liquid oxygen and LN2.

The next two tests likely took advantage of the customized test stand, which has been semi-permanently outfitted with a set of hydraulic rams that allow SpaceX to simulate the thrust of six Raptor engines while Starship’s structures are chilled to cryogenic temperatures and loaded with roughly 1000 tons (~2.2M lb) of cryogenic fluids. If a Starship can survive those stresses on the ground, the assumption is that it will likely survive similar stresses in flight.

Assuming that Ship 25’s first several proof tests were successful, which they appear to have been, SpaceX returned the prototype to its Starbase factory to install six Raptor engines and a series of shields and firewalls that will protect those engines from each other. Once fully outfitted, Ship 25 will return to the launch site for static fire testing and take Ship 24’s place on Suborbital Pad B. Ship 24 took approximately two months to go from its last cryoproof to its first static fire. But its testing got off to a relatively rocky start, so Ship 25 could be ready sooner.

SpaceX could begin the next phases of Booster 7 and Ship 24 testing as early as November 10th or November 13th.

Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla briefly offered this Robotaxi part for your personal car

Published

1 hour ago

on

July 28, 2026

By

Credit: @tpgoebel | X

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.

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.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

3 hours ago

on

July 28, 2026

By

Credit: Tesla

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:

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.

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.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

24 hours ago

on

July 27, 2026

By

Credit: Tesla

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.

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.

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.

Continue Reading