Connect with us

News

SpaceX finishes stacking new Starship for the first time in six months

Published

4 years ago

on

For the first time in more than half a year, SpaceX has stacked a new Starship prototype to its full height, hopefully marking the end of a period of relatively slow progress.

That period began when Starship S20 was stacked to its full height in early August 2021. Until very recently, Ship 20 was said and expected to be the prototype assigned to Starship’s first orbital test flight, making it exceptionally important. In an unusual change in attitude, SpaceX may have felt the same, which may explain why Starship S20’s first static fire test took place more than two months after it first left the factory. A year prior, Starships SN9, SN10, SN11, and SN15 all completed proof testing a matter of weeks after rollout.

That sudden change of pace relative to past development has meant that Ship 20 is the only Starship prototype SpaceX has tested since May 2021 and the only Starship to graduate from final assembly to testing in the last six months. In that period, Ship 20 has completed a few major cryogenic proof tests and four static fires – two of which ignited all six Raptor engines. While Ship 20’s six-engine tests were unprecedented and marked a major program milestone, SpaceX once static-fired Starship SN9 three times in one day in January 2021.

However, that period of sluggish prototype testing may finally be coming to an end. In August 2021, when SpaceX stacked Starship S20 and Super Heavy B4 for the first time, the general assumption was that the seemingly imminent march towards orbital flight testing would be similar to SpaceX’s attempts to land a Starship from medium altitude between December 2020 and May 2021 – lots of prototypes in flow and multiple back-to-back tests and launches, in other words. That was not the case.

Starship S21, for example, began final assembly in mid-October 2021 and its tank section and nose section were both fully stacked less than a month later. However, rather than stack them into a second complete ship, SpaceX has left those separate assemblies sitting around Starbase for the last three months. Simultaneously, while Ship 21’s apparent limbo seemed to imply that SpaceX was implementing another block upgrade and moving on to newer prototypes, the company actually started stacking Starship S22 about a week after S21’s separate sections were completed. Only three months later have SpaceX’s plans for those three sections finally become clear.

Advertisement

On February 14th, 2022, Ship 22’s tank section followed Ship 21’s nose section into Starbase’s high bay assembly facility, where they were quickly stacked to form a full Starship prototype the same day. This raises the question: why?

Ship 21’s nose. (Richard Angle)
Ship 22’s tank section. (NASASpaceflight – bocachicagal)
Ship 21’s tank section (right) will probably be scrapped. (NASASpaceflight – bocachicagal)

Given that Starship S20 effectively completed qualification testing with three successful static fires in December 2021 and a fourth in early January 2022 and has been seemingly ready to fly ever since, its Super Heavy booster readiness – not ship readiness – that appears to be holding SpaceX back. Perhaps because of pad readiness issues, SpaceX has yet to perform a single Super Heavy static fire test – or even a less risky wet dress rehearsal – at the orbital launch site. As such, it’s hard to say why SpaceX has suddenly decided to finish Ship 22 instead of focusing on a newer version of Starship (S24) and Super Heavy (B7) – both of which are expected to debut upgrades.

It’s possible that Ship 22 is being completed merely as practice for the Starbase workforce, who have gone half a year without fully assembling another ship prototype, but then there would have been no reason not to install Ship 21’s nose on Ship 21’s tank section instead of withholding it for Ship 22. Ship 22 could also be a replacement for Ship 21 if appearances are misleading and SpaceX uncovered issues with the older prototype during testing but again, no booster is ready to launch either ship.

Regardless of the outcome or purpose of Ship 22, seeing any new Starship prototype completed is an exciting and interesting change of pace after half a year of following the windy paths of Ship 20, Booster 5, and Ship 21 to their uncertain goals.

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.

Comments

News

Tesla Full Self-Driving (Supervised) v14.1.7 real-world drive and review

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users.

Published

6 hours ago

on

November 13, 2025

By

tesla interior operating on full self driving
Credit: TESLARATI

Tesla started rolling out its Full Self-Driving (Supervised) v14.1.7 suite last night to owners, and there are several improvements to note within the new update that are at least the start of fixes to highly-mentioned issues.

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users. However, there are a handful of shortcomings that are still present within the suite, which are not something that will be fixed within the span of a single update.

For what it is, Full Self-Driving does an excellent job of navigating — once you get it on its correct path. Our issues tend to be confined to navigation, routing, and the decision-making process that has to do with the way the car wants to get you to your destination. There were five things that happened on our first drive with v14.1.7 that are worth mentioning. The full drive will be available at the bottom of this article.

Navigation and Routing Still Seems to Be a Major Challenge

In past content, we’ve discussed the issues with routing and navigation, and how a Tesla chooses its path. Most noticeably, these issues occur in the same areas; for me, it’s my local Supercharger. My 2026 Model Y with AI4 continues to pick less-than-optimal routes out of the Supercharger, and in this instance, it actually chose to turn down a road, pull over, and give me the wheel, essentially asking, “Hey, can you get me on the right track here?”

This is still my biggest bone to pick with FSD, even more so than some of the bonehead moves it’s made in tougher scenarios (mostly parking lots with very limited visibility due to shrubs being planted in the worst possible locations). It’s rare that it happens, but this particular Supercharger has been a true thorn in the side of my Tesla.

This is not an issue that is confined to v14.1.7, or even v14 in general. Unfortunately, it is an issue that has persisted throughout my ownership experience, as well as during Demo Drives.

Stuttering and Hesitation at Intersections was Non-Existent

There was some confusion regarding my language in a recent article where I stated Tesla is confronting the issues that have been reported regarding the “stabbing” with braking.

“Tesla began the v14.1.4 launch last night, which included minor improvements and addressed brake-stabbing issues many owners have reported. In my personal experience, the stabbing has been awful on v14.1.3, and is a major concern.

However, many things have improved, and only a couple of minor issues have been recurring. Many of the issues v13 addressed are no longer an issue, so Tesla has made significant progress.”
It has undoubtedly improved, but it is not resolved.

With that being said, I did not feel a single example of hesitation, stabbing, or stuttering at a single intersection or instance when it has been present in the past. CEO Elon Musk said it would be fixed with v14.2, so it seems like Tesla is well on its way to resolving it.

Proper Handling of Crosswalks

It’s crazy how many people still do not stop for pedestrians at clearly-marked crosswalks. I had two instances of it happen during the drive, with FSD stopping for those pedestrians both times.

Human drivers did not stop either time:

Handled Merging onto a Highway with an Inconsiderate Driver Well

Routinely, drivers will get over into the left lane, if they are able, to allow merging traffic to safely enter the freeway. It does not always happen this way, and it’s not required by law.

Not exclusive to v14.1.7, as many past iterations would have done this as well, but it was nice to watch the vehicle slow down to let that traffic pass. It then entered the freeway safely, and the entire maneuver was well done.

Took an Appropriate Move with Oncoming Foot Traffic and Debris in a Tight Alleyway

This was probably the most on-edge I was during the drive because: 1) FSD chose to take an unnecessary alleyway, and 2) there was a box and oncoming pedestrians.

The car was aware of everything that was going on. In order to avoid the box, it would have had to turn toward the pedestrians, and in order to avoid the pedestrians, it would have had to turn into the box.

It chose to wait patiently, and after the pedestrians were past the car, FSD chose to proceed.

Closing Thoughts

Overall, we’re very impressed with v14.1.7, and we think this is Tesla’s best iteration of the FSD suite yet, as it should be since it’s the newest version available. Tesla’s attention to detail regarding the brake stabbing is really well done, and it seems evident that a complete fix is on its way.

Other than the navigation issue at the very beginning, which was not an intervention, at least in my opinion, this was a really successful drive.

Continue Reading

Elon Musk

Elon Musk debunks report claiming xAI raised $15 billion in funding round

xAI also responded with what appeared to be an automated reply, stating, “Legacy Media Lies.”

Published

7 hours ago

on

November 13, 2025

By

Credit: xAI

Elon Musk has debunked a report claiming his AI startup xAI had raised $15 billion from a funding round. Reports of the alleged funding round were initially reported by CNBC, which cited sources reportedly familiar with the matter.

CNBC’s report

The CNBC story cited unnamed sources that claimed that the new capital injection would help fund GPUs that xAI needs to train its large language model, Grok. The news outlet noted that following the funding round, xAI was valued at $200 billion. 

Artificial intelligence startups have been raising funds from investors as of late. OpenAI raised $6.6 billion in October, valuing the startup at a staggering $500 billion. Reuters also reported last month that OpenAI was preparing for an IPO with a valuation of $1 trillion. Elon Musk’s xAI is looking to catch up and disrupt OpenAI, as well as its large language model, ChatGPT, which has become ubiquitous.

Elon Musk and xAI’s responses

In his response on X, Elon Musk simply stated that the CNBC story was “false.” He did not, however, explain if the whole premise of the publication’s article was fallacious, or if only parts of it were inaccurate. 

Amusingly enough, xAI also issued a response when asked about the matter by Reuters, which also reported on the story. The artificial intelligence startup responded with what appeared to be an automated reply, which read, “Legacy Media Lies.”

Advertisement

xAI, founded in July 2023 as an alternative to OpenAI and Anthropic, has aggressively built out infrastructure to support its flagship products, including Grok and its recently launched Grokipedia platform. The company is developing its Colossus supercomputer in Memphis, which is heralded as one of the world’s largest supercomputer clusters.

Continue Reading

News

Tesla reportedly testing Apple CarPlay integration: report

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally.

Published

10 hours ago

on

November 13, 2025

By

Credit: Tesla

Tesla is reportedly testing Apple’s CarPlay software for its vehicles, marking a major shift after years of resisting the tech giant’s ecosystem. 

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally. The move could help Tesla gain more market share, as surveys have shown many buyers consider CarPlay as an essential feature when choosing a car.

Not the usual CarPlay experience

Bloomberg claimed that Tesla’s tests involve a rather unique way to integrate CarPlay. Instead of replacing the vehicle’s entire infotainment display, Tesla’s integration will reportedly feature a CarPlay window on the infotainment system. This limited approach will ensure that Tesla’s own software, such as Full Self-Driving’s visuals, remains dominant. 

The feature is expected to support wireless connectivity as well, bringing Tesla in line with other luxury automakers that already offer CarPlay. While plans remain fluid and may change before public release, the publication’s sources claimed that the rollout could happen within months. 

A change of heart

Tesla has been reluctant to grant Apple access to its in-car systems, partly due to Elon Musk’s past criticism of the tech giant’s App Store policies and its poaching of Tesla engineers during the failed Apple Car project. Tesla’s in-house software is also deemed by numerous owners as a superior option to CarPlay, thanks to its sleek design and rich feature set.

Advertisement

With Apple’s retreat from building cars and Elon Musk’s relationship with Apple for X and Grok, however, the CEO’s stance on the tech giant seems to be improving. Overall, Tesla’s potential CarPlay integration would likely be appreciated by owners, as a McKinsey & Co. survey last year found that roughly one-third of buyers considered the lack of such systems a deal-breaker.

Continue Reading

Trending