News
SpaceX installs new Starship on static fire test stand
SpaceX may be focused on preparing Starship S24 and Super Heavy Booster 7 for their potentially imminent orbital launch debut, but the rest of the company’s Starship factory isn’t just sitting around.
The laser focus on carefully testing Ship 24 and Booster 7 may have limited the effectiveness of Starbase rocket production, but the factory has continued to produce new ships and boosters. SpaceX has even conducted some limiting testing of a pair of prototypes meant to follow in the footsteps of S24 and B7. In mid-January, that process entered a new and more active phase as SpaceX transported Starship S25 from the factory to the launch pad.
The trip is not Ship 25’s first. Starship S25 first headed to SpaceX’s South Texas launch and test facilities on October 19th, 2022, shortly after the vehicle was fully assembled. Around three weeks of testing followed, and now Ship 25 is back for more.
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
Ship 25
The first round of tests was thorough and put Ship 25 through a pneumatic proof test, multiple cryogenic proof tests, and likely a few simulated thrust tests using six hydraulic rams.
“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.”
Teslarati.com – October 20th, 2022
As usual, SpaceX didn’t comment on the development or indicate how that initial proof testing had gone, but Ship 25’s January 14th, 2023 return to the launch site all but guaranteed that that testing had gone more or less according to plan. On January 17th, SpaceX lifted Ship 25 onto Starbase’s only Starship static fire test stand, further confirming that Ship 25 proof testing went to plan.
Soon after its November 2022 return to Starbase’s build site, six Raptor engines were moved into the High Bay and installed on Ship 25. The Starship’s aft was then likely buttoned up with a heat shield before it headed to the test site to begin its static fire test campaign. That campaign could tell us a lot about the status of Starship prototypes. To date, only two Ships have completed full six-Raptor static fire tests, and both took days, weeks, or months to build up to those six-engine milestones with multiple smaller tests. If Ship 25 were to skip those preliminary tests and immediately conduct a six-engine static fire, it would be a sign that SpaceX is significantly more confident in the current Starship design.
-
Booster 9
Ship 25 is believed to be paired with Super Heavy Booster 9, which recently finished its own round of proof tests. About two months behind Ship 25, Booster 9 rolled out of its Starbase assembly bay and headed to the launch site on December 15th, 2022. The Super Heavy prototype ultimately completed two partial cryogenic proof tests on December 21st and 29th, during which it was likely loaded with around a thousand tons of liquid nitrogen to simulate explosive liquid oxygen and methane propellant. Booster 9 then returned to Starbase’s factory on January 10th, 2023.
Assuming those tests went well, Raptor engine installation could begin at any moment. However, thanks to significant design changes and upgrades present on Booster 9, outfitting and testing this Super Heavy could take longer than usual. Many smaller changes are present, but the most significant by far is the addition of an upgraded version of Raptor. The engine’s combustion-related hardware is likely the same as the Raptor V2 engines present on Booster 7, Ship 24, and Ship 25. But the hardware used to steer each engine – called thrust vector control (TVC) – has been completely changed.
Instead of using a complex web of plumbing and hydraulic power units bolted to the side of Super Heavy, Booster 9’s 13 central Raptors will be electrically steered. That has allowed SpaceX to remove those power units (streamlining Booster 9’s exterior) and reduce the already rats nest of plumbing required to fuel, control, power, and steer dozens of high-performance rocket engines on one booster. SpaceX has been testing electric Raptor TVC for months at its McGregor, Texas development facilities, but it’s unclear if the new technology has progressed to the point that 13 upgraded engines are ready to be installed on Booster 9. In the meantime, SpaceX may install Booster 9’s fixed outer ring of 20 Raptor V2 engines – none of which gimbal or need new electric TVC hardware.
Once all 33 engines are installed, it’s likely that Booster 9 will be thoroughly tested to ensure that all 13 electrically-steered engines work well together before, during, and after numerous static fire tests. SpaceX will also need to verify that the batteries likely powering those new systems function as expected. During the peak stresses they will likely experience, the electric TVC could need to rapidly redirect more than 3000 tons (~6.6 million lbf) of thrust multiple times per second. The peak power required from Super Heavy’s batteries will likely be immense as a result.
For now, the start of Super Heavy B9’s own static fire test campaign could be months away and will have to wait until Starbase’s only orbital launch mount – currently occupied by Booster 7, Ship 24, and Starship’s first orbital launch campaign – is vacated. With that orbital launch debut unlikely to happen before March 2023, Booster 9 has plenty of time to relax inside Starbase’s Wide Bay while Ship 25 begins static fire testing at a separate stand.
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.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
