Connect with us

News

SpaceX prepares Starship, Super Heavy for milestone Raptor static fire tests

Starship S20 and Super Heavy B4 are fast approaching readiness for their first crucial tests - including multiple Raptor static fires. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has scheduled a full week with as many as 30 hours of road and beach closures for Starship and Super Heavy testing and is working hard to prepare the first orbital-class ship and booster for several major challenges.

First rolled to SpaceX’s Starbase orbital launch site more than six weeks ago and stacked together for the first time on August 6th, the company has spent the last month putting the finishing touches on Starship 20 (S20) and Super Heavy Booster 4 (B4) – ranging from heat shield installation to plumbing and wiring. Perhaps most importantly, SpaceX has also installed some or all of the Raptor engines that are expected to support the ship and boosters’ first static fire qualification tests.

For a number of reasons, those static fires – and a few additional tests expected to precede them – could be huge milestones for SpaceX’s Starship program.

SpaceX appears to have begun finalizing the Raptor engines that will be aboard Super Heavy for its first major static fire testing. (NASASpaceflight – bocachicagal)

Earlier this month, after rolling Starship S20 to the launch pad for the second time and installing it on one of two suborbital launch/test mounts, SpaceX began the process of installing Raptor engines (again for the second time) on the rocket. Beginning with two center sea level-optimized Raptors, SpaceX then installed a Raptor Vacuum engine on Ship 20. The implication: when S20 fires up for the first time, it might be doing so with two kinds of Raptor engines – a first for the Starship program.

Since Raptor Vacuums first began static fire testing at SpaceX’s McGregor, Texas development campus around Q4 2020, the company has yet to fire up an RVac engine on a Starship prototype. Starship’s current design features three gimballing sea-level Raptors and three vacuum-optimized variants with much larger nozzles – all in close proximity inside a 9m-wide (30 ft) skirt.

S20 had six engines installed for the first time in Starship history on August 4th. (Elon Musk)
Those engines were removed when S20 returned to the launch site late last month but have been gradually reinstalled over the last two weeks. (NASASpaceflight – bocachicagal)

As such, the first Starship static fire with any combination of Raptor Center and Raptor Vacuum engines will be a significant milestone for SpaceX. Eventually, that will likely culminate in the first static fire(s) of a Starship (likely S20) with all six Raptors installed – a test that will effectively qualify that prototype for its first orbital launch attempt.

Meanwhile, things are arguably even more complex for Super Heavy. Aside from a single three-engine static fire completed by Super Heavy Booster 3 (B3), Starship’s first stage has never come close to a full-up static fire with all 29-33 Raptor engines installed. Whenever that occurs, Super Heavy will likely become the most powerful rocket ever tested and – like with Starship – will be more or less qualified for its first flight if the test goes according to plan.

Advertisement
-->
Super Heavy B4’s first and second trips onto the orbital launch mount. (SpaceX/SPadre)

SpaceX already installed a full 29 Raptor engines on Super Heavy B4 last month. After returning to Starbase, those engines were removed and eventually reinstalled a few weeks later – albeit with a number of replacements. Now, having spent the last 11 days sitting on the orbital pad’s launch mount, SpaceX has begun to replace at least one of Booster 4’s 29 installed engines. It’s unclear why but the fact that SpaceX is replacing engines at the launch pad – instead of rolling Super Heavy back to the build site for the third time – is an encouraging sign that B4 is nearly ready for its first proof and static fire tests.

Due to all the recent activity, it’s almost impossible to tell whether Starship S20 or Super Heavy B4 will be first onto the figurative saddle for ambient pressure, cryogenic, and static fire proof testing. What is clear, though, is that SpaceX has five six-hour testing windows scheduled every day next week. Stay tuned for updates on the next steps for SpaceX’s first orbital-class ship and booster pair.

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 Full Self-Driving lands in a new country, its 7th

Published

on

Credit: Tesla Korea

Tesla Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.

On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:

This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.

Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.

However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.

Tesla Full Self-Driving appears to be heading to Europe soon

The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”

Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.

For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.

Continue Reading

Elon Musk

Tesla CEO Elon Musk teases insane capabilities of next major FSD update

Published

on

Credit: Tesla China/Weibo

Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.

Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.

However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”

There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.

One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.

We experienced it most frequently at intersections, especially four-way stop signs.

Elon Musk hints at when Tesla can fix this FSD complaint with v14

In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.

Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.

However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.

Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.

Continue Reading

News

Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad

Published

on

Credit: Teslarati

Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.

With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.

While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.

With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.

However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.

The Good

Lack of Brake Stabbing and Hesitation

Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.

This was a major problem.

However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.

This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.

Speed Profiles Seem to Be More Reasonable

There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.

Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.

It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.

Better Overall Operation

I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.

v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.

The Bad

Parking

It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.

This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.

However, this was truly my only complaint about v14.2.

You can check out our full 62-minute ride-along below:

Continue Reading