Connect with us

News

SpaceX set to finish three Starship prototypes in the same month

The tank sections of two full-scale Starship prototypes stand side by side as they speed towards completion. (NASASpaceflight - bocachicagal)

Published

on

SpaceX appears to be on track to complete its third Starship prototype in a month just days after the company finished testing a new steel tank and at the same time as it prepares to roll another full-scale ship to the launch pad.

Postponed by several weeks after the (fleeting) success of the Starship serial number 4 (SN4) prototype, violently destroyed by a minor testing mishap on May 29th, SpaceX’s fifth full-scale Starship tank section (SN5) could roll to an adjacent testing facility at any point in the next few days. In fact, SN4’s successor has likely been ready to begin tank proof and static fire testing for several weeks since it was stacked to its full height on May 12th. SN4 rolled to the launch pad on April 23rd and remained SpaceX’s top Starship priority until its demise more than a month later.

As it turns out, the explosion that destroyed the ship also launched a ~25 metric ton (~55,000 lb) counterweight installed a few days prior some 100m (300+ ft) into the air, where it proceeded to fall back to earth and obliterate the steel mount Starship SN4 sat on. The loss of that pad hardware necessitated its own several-week delay but SpaceX appears to be nearly done installing and outfitting replacements as of June 18th – an incredible turnaround given the scale and complexity of everything involved. Of course, the whole purpose of those rapid repairs is to get back to the business of testing Starships as quickly as possible.

SpaceX recently finished stacking Starship SN6’s tank section barely a month after its predecessor – and did so side by side. (NASASpaceflight – bocachicagal)

SN5

Initially expected as early as 8am local on June 17th, Starship SN5’s trip to the launch pad has been a long time coming. Completed around May 20th after approximately a month of concerted effort, the ~30m (100 ft) tall tank departed SpaceX’s Vehicle Assembly Building (VAB) for the first on June 13th, although it was quickly moved back inside as technicians simultaneously worked to complete Starship SN6.

Previously scheduled to become the first Starship to reach its full height with the installation of a functional nosecone, SN5 will likely pick up where SN4 left off, instead. That process will effectively be no different, albeit sans nosecone, starting with ambient and cryogenic proof (pressure) tests and eventually moving to one or several static fires with either one or three Raptor engines. Testing the quick disconnect umbilical port that caused SN4’s demise will also likely be a priority. If all goes according to plan in that first week or two of tests, SpaceX may finally be ready to launch a full-scale Starship prototype for the first time, performing a 150m (~500 ft) hop test with SN5.

Advertisement
Starship SN5 steps out of its perch inside the VAB for the first time since assembly began. (NASASpaceflight – bocachicagal)

However, since CEO Elon Musk first discussed plans for an initial 150m hop test, SpaceX received a surprise suborbital launch license from the FAA, rather than the limited experimental permit most expected. That license effectively allows SpaceX to perform an unlimited number of Starship tests as long as the trajectory follows the administration’s strict safety guidelines and remains suborbital. Unless SpaceX’s ~150m target was based in some technical limitation, the sky is quite literally the limit for a more ambitious flight debut if the company believes Starship SN5 can handle it.

SN6

In the event that Starship SN5 follows its predecessor into a less early (but still early) grave, SpaceX thankfully won’t have to wait long at all to continue its hardware-rich test program. When Starship SN5 first departed the VAB on June 13th, it did so to give SpaceX room to finish Starship SN6, placing its aft engine section on a stand inside the building and stacking the upper two-thirds of the ship’s tank on top.

Starships SN5 and SN6, May 23rd. (NASASpaceflight – bocachicagal)
Starships SN5 and SN6, June 7th. (NASASpaceflight – bocachicagal)
Starships SN5 and SN6, June 16th. (NASASpaceflight – bocachicagal)

Several days to a week or more of internal and external work remain to fully mate the two Starship SN6 sections, but the vast majority of its assembly is now behind SpaceX. SpaceX continues to refine its methods with each successive prototype, gradually producing Starships that are getting closer and closer to the ideal finished product. There’s a chance that, unlike Starship SN4, SN5 can be modified with the installation of a nosecone and flaps to support more ambitious 2-20 km (~1.2-12 mi) flight tests if it makes it over the 150m hurdle unscathed but if not, SN6 could become the first Starship to have a nosecone installed.

SN7

Last but absolutely not least, SpaceX recently built a new Starship test tank for the first time since March. While stouter than an actual Starship-class methane or oxygen tank, this particular test tank is maybe only 25% shorter than the methane tanks installed on Starship prototypes. According to Musk and effectively confirmed by writing all over the prototype, this particular test tank – formerly Starship SN7 – was built to determine if a different kind of steel could be preferable for future ships.

Starship SN7 survived its first cryogenic pressure test largely unscathed despite developing a leak mid-test. (NASASpaceflight – bocachicagal)
Leak be damned, the SN7 test tank was quickly repaired and will likely be tested again in the next few days. (NASASpaceflight – bocachicagal)

Shortly after the June 15th test began to wind down, Musk announced that the new material (304L stainless steel) had performed quite well, reaching 7.6 bar (110 psi) before it sprung a leak. The fact alone that it sprung a leak instead of violently depressurizing is already a major sign that 304L is preferable to 301L, as it means that Starships built out of it could fail much more gracefully in the event of a leak instead of collapsing or violently exploding. A step further, SpaceX has already managed to repair the leak on SN7 and will likely test the tank again in the next few days.

Meanwhile, Musk says that a second improved 304L test tank is already on its way, after which SpaceX will likely attempt to build and test the first fully-304L Starship prototype. Further down the line, SpaceX intends to develop its own custom steel alloy, optimized specifically for Starship’s needs. The first tests of that ’30X’ alloy could begin as early as August 2020 according to a February Musk tweet.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

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 Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Published

on

(Photo: Hector Perez/YouTube)

Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.

Tesla Assisted Smart Summon (ASS) improvements

There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:

“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.

This caused me to sprint across the lot to retrieve the vehicle:

Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.

It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:

I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.

It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.

New Disengagement Categories

This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.

I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.

I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.

I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.

Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.

Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.

Inconsistency with Regional Traffic Patterns

Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.

In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.

Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.

This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.

Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.

“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”
This could be one of those examples that Tesla just has to figure out.

Highway Operation

Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.

However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:

Better Maneuvering at Stop Signs

Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.

I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.

This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.

FSD seems to have worked through this particular maneuver:

FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.

Continue Reading

News

Tesla plans to resolve its angriest bunch of owners: here’s how

Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.

Published

on

tesla-asia-model-3
Credit: Tesla Asia/Twitter

Tesla has a plan to make Hardware 3 owners whole after CEO Elon Musk admitted that those with that self-driving chip in their cars will not have access to unsupervised Full Self-Driving.

The company’s strategy is so crazy that it is sort of hard to believe.

Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.

During the Tesla Q1 earnings call on Wednesday, Musk finally clarified what the company’s plans are for Hardware 3 owners, what they will be offered, and what Tesla will have to do internally to prepare for it.

The answer was somewhat mind-boggling.

Musk said:

“Unfortunately, Hardware 3 — I wish it were otherwise, but Hardware 3 simply does not have the capability to achieve unsupervised FSD. We did think at one point it would have that, but relative to Hardware 4, it has only 1/8 of the memory bandwidth of Hardware 4. And memory bandwidth is one of the key elements needed for unsupervised FSD.”
He continued, stating that HW3 owners would have the opportunity to trade their cars in at a discounted rate in order to get the AI4 chip:

“So for customers that have bought FSD, what we’re offering is essentially a trade-in — like a discounted trade-in for cars that have AI4 hardware, and we’ll also be offering the ability to upgrade the car, to replace the computer. And you also need to replace the cameras, unfortunately, to go to Hardware 4.”
Obviously, Tesla has a lot of people to work with and make this whole thing right. Musk was adamant that HW3 would be capable of FSD, and now that the company has finally admitted that it is not, there are some things that could come of this.

There has been open talk about some sort of class action lawsuit against Tesla. The promises that Tesla made previously could be considered a breach of contract or even false advertising, and that’s according to Grok, Musk’s own AI program.

Musk went on to say that Tesla would likely have to establish new microfactories to effectively and efficiently replace HW3 computers and cameras:

…So to do this efficiently, we’re going to have to set up, like kind of micro factories or small factories in major metropolitan areas in order to do it efficiently. Because if it’s done just at the service center, it is extremely slow to do so and inefficient. So we basically need like many production lines to make the change.”
This is going to be an extremely costly process, especially if Tesla has to buy real estate, properties, and equipment to complete this work. Additionally, there was no wording on pricing, but Musk never said it would be free. It will likely come with some kind of price tag, and HW3 owners, after being left hanging for so long, will have something to say about that.

Advertisement



Continue Reading

Elon Musk

SpaceX just got pulled into the biggest Weapons Program in U.S. history

SpaceX joins the Golden Dome software group, deepening its role in America’s most expensive defense program.

Published

on

By

US Golden Dome space defense system (Concept render by Grok)

SpaceX has joined a nine-company group developing the core operating software for the Golden Dome, America’s next-generation missile defense system. According to a Bloomberg report, SpaceX is focused on integrating satellite communications for military operations and is working alongside eight other defense and artificial intelligence companies, including Anduril Industries, Palantir Technologies, and Aalyria Technologies, to build software connecting missile defense capabilities.

The Golden Dome concept dates back to President Trump’s 2024 campaign, and on January 27, 2025, he signed an executive order directing the U.S. Armed Forces to construct the system before the end of his term. The system is planned to employ a constellation of thousands of satellites equipped with interceptors, with data centers in space providing automated control through an AI network.

FCC accepts SpaceX filing for 1 million orbital data center plan

Space Force Gen. Michael Guetlein, director of the Golden Dome initiative, has described the software layer as a “glue layer” that would enable officers to manage and control radars, sensors, and missile batteries across services. The consortium is aiming to test the platform this summer.

Trump selected a design in May 2025 with a $175 billion price tag, expected to be operational by the end of his term in 2029, though the Congressional Budget Office projected the cost could reach $831 billion over two decades.

The Golden Dome role is only the latest in a string of military wins for SpaceX. As Teslarati reported, the U.S. Space Force awarded SpaceX a $178.5 million task order on April 1, 2026 to launch missile tracking satellites for the Space Development Agency, covering two Falcon 9 launches beginning in Q3 2027. That came on top of more than $22 billion in government contracts held by SpaceX as of 2024, per CEO Gwynne Shotwell, spanning NASA resupply missions, classified intelligence satellites through its Starshield program, and military broadband.

The accumulation of defense contracts, now including a seat at the table on the most expensive weapons program in U.S. history, positions SpaceX as the dominant infrastructure provider for American national security in space. With a SpaceX IPO still on the horizon, each new contract adds weight to what is already one of the most consequential companies in aerospace history, raising real questions about how much of America’s defense architecture will depend on a single private operator before it ever trades publicly.

Continue Reading