Connect with us

News

SpaceX installs Raptor Vacuum engine on first orbital-class Starship

Starship S20's third round of Raptor Vacuum engine installation - hopefully for good. (NASASpaceflight - Nic Ansuini)

Published

5 years ago

on

Update: Providing the best views yet of the Raptor Vacuum installation process, SpaceX began installing one of Starship S20’s six engines (one of at least two recently trucked to the launch site) on Monday morning.

It remains to be seen exactly how many engines will be installed on Ship 20 or how many will be ignited during its first static fire test but barring the delivery of more Raptors, signs currently point to an initial test of two engines – one sea-level-optimized Raptor Center (RC) and one Raptor Vacuum with a much larger nozzle. Whenever Ship 20 does fire up those engines, it will be the first static fire of a RVac engine installed on a Starship and the first simultaneous, side-by-side static fire of two different Raptor variants. Since publishing time, SpaceX has cancelled a Tuesday road closure, pushing Starship S20’s first static fire attempt to no earlier than (NET) Wednesday evening.

For the third time in two months, SpaceX has begun installing Raptor engines on its first orbital-class Starship prototype – hopefully for good.

In no uncertain terms, Starship 20’s (S20) path to what could be its last Raptor installations has been about as windy and mysterious as they come. Starship 20 (S20) left the Starbase factory floor for the first time in early August – all six Raptors installed in another program first – for a brief fit check and photo op. After spending about an hour installed on top of Super Heavy Booster 4 (B4), Ship 20 was removed and returned to the build site, where teams removed all six engines and finished wiring and plumbing the vehicle.

Days before the ship’s long-anticipated trip to Starbase’s suborbital launch site for qualification testing, the mount SpaceX prepared for the process quickly had hydraulic rams – used to safely simulate Raptor thrust – were abruptly removed. Starship S20 was then installed on the Pad B mount, where SpaceX proceeded to reinstall six Raptors. Weeks later, after slow heat shield repairs neared completion, SpaceX again removed Ship 20’s Raptors and reinstalled the hydraulic rams it had removed – unused – the month prior. Finally, on September 30th, some seven weeks after the prototype arrived at the suborbital launch site, SpaceX put Starship S20 through its first major test – a lengthy ‘cryoproof’.

Now, ten days after completing a seemingly flawless cryoproof test on its first try, SpaceX has once again trucked multiple Raptors – at least one sea level and one vacuum engine – from the Starbase build site to Starship S20’s suborbital test stand. From the outside looking in, it’s hard not to view the contradictory path S20 took to its first tests – and is still taking to its first static fire(s) – as an unusually visible sign of some kind of internal tug of war or major communication failure between different SpaceX groups or executives.

It’s impossible to determine anything specific beyond the apparent fact that several of the steps taken from Ship 20’s first factory departure to its first cryoproof and static fire tests could have probably been deleted entirely with no harm done and many dozens of hours of work saved. At the end of the day, Starship S20 completed cryoproof testing without issue on the first try and is now seemingly on track to begin its first static fire test campaign later this month.

Advertisement
-
-
SpaceX reveals first orbital Starship with six Raptor engines
SpaceX repairing heat shield, reinstalling Raptors on first orbital-class Starship

At the moment, SpaceX has three possible static fire test windows scheduled from 5pm to midnight CDT on Tuesday, Wednesday, and Thursday (Oct 12-14). A similar Monday window was canceled days ago on October 7th, suggesting that more cancellations are probably on the horizon. For now, there’s a chance that Starship S20 – with anywhere from two to all six Raptor engines installed – will fire up for the first time before next weekend. It’s hard to say how exactly SpaceX will proceed. It’s not inconceivable that SpaceX will install all six engines and gradually ramp up to a full six-engine static fire over several tests.

Raptor Vacuum has identical plumbing but a far larger nozzle than its sea-level-optimized siblings. A larger nozzle boosts engine efficiency in or near vacuum.

Given that SpaceX has already static fired three Raptor Center (RC) engines on multiple Starship and Super Heavy prototypes, odds are good that Starship S20’s test campaign will be similar – beginning with a three-Raptor static fire, in other words. SpaceX could then add one, two, or all three Raptor Vacuum engines into the fray for one or more additional tests with 4-6 engines total. It’s also possible that suborbital launch mount and pad limitations will prevent more than three engines from firing at once, in which case SpaceX would presumably perform two separate tests of Ship 20’s Raptor Center and Raptor Vacuum engines.

Given that two Raptor variants have never been static fired simultaneously on the same vehicle, it’s hard to imagine that SpaceX won’t also want to perform one or several combined static fires with Raptor Vacuum and Raptor Center engines on Ship 20.

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 Full Self-Driving insurance program with heavy discount expands

Published

12 hours ago

on

August 3, 2026

By

Lemonade has expanded its innovative Autonomous Car insurance program to Tennessee, giving Tesla owners in the state a substantial discount on Full Self-Driving (FSD) miles. Announced on August 3, the product offers 50 percent off every mile driven with FSD activated, positioning the digital insurer as a leader in pricing insurance around autonomous technology.

The program, marketed as Lemonade Autonomous Car insurance, uses a direct connection via Tesla’s Fleet API (with customer permission) to automatically distinguish FSD-engaged miles from manual driving. Policyholders pay a low base rate when the vehicle is stationary and a few cents per mile when moving, with the 50 percent reduction applied specifically to FSD miles.

Coverage includes standard protections such as liability, collision, comprehensive, roadside assistance, and Tesla-specific benefits like access to certified repair shops and emergency crash services. Eligible vehicles require Hardware 4, as well as recent firmware.

Lemonade first unveiled the product on January 21 of this year, describing it as a first-of-its-kind offering designed for self-driving cars, starting with Tesla FSD. It began rolling out in Arizona on January 26, followed by Oregon about a month later. Subsequent expansions brought it to Indiana in early June 2026 and Colorado later that month.

Tennessee marks the fifth state.

Tesla Full Self-Driving gets outrageous insurance offer with insanely cheap rates

The discount rests on Lemonade’s strong belief in the safety of Tesla’s FSD system. The company cites Tesla’s data showing that FSD-driven miles are twice as safe as those driven manually, or associated with roughly a 50 percent crash reduction.

Lemonade Co-founder and President Shai Wininger has emphasized this distinction: “Traditional insurers treat a Tesla like any other car, and AI like any other driver. But a car that sees 360 degrees, never gets drowsy, and reacts in milliseconds can’t be compared to a human.”

He added that “Teslas driven with FSD are involved in far fewer accidents” and committed that as FSD software improves and becomes safer, Lemonade’s prices will drop further.

Tesla Full Self-Driving gets an offer to be insured for ‘almost free’

This approach leverages Lemonade’s existing pay-per-mile technology and AI-driven risk models, which analyze nuanced vehicle data including software version and sensor performance. The company expects the model to reward higher FSD usage with greater savings while supporting mixed households that include both Tesla and non-Tesla vehicles under one policy. Bundling with home, renters, or pet insurance can yield additional discounts.

As autonomous driving technology advances, Lemonade’s state-by-state expansion of usage-based pricing that directly reflects real-world safety data represents a notable shift in how insurers evaluate risk.

Tesla owners in the five available states – Arizona, Oregon, Indiana, Colorado, and now Tennessee – can obtain quotes quickly through the Lemonade app or website, potentially lowering the overall cost of ownership for vehicles equipped with advanced driver-assistance systems. Further states are expected as regulatory approvals progress.

Continue Reading

Cybertruck

Tesla quietly made the Cybertruck even stronger

Published

16 hours ago

on

August 3, 2026

By

Credit: Tesla

Tesla has continued to flex the strength, rigidity, and robustness of its all-electric pickup, the Cybertruck. In fact, since 2019, Cybertruck’s ability to avoid dents, dings, and even gunfire has been one of the main selling points Tesla has used to attract buyers who are looking for a vehicle that can handle the most intense challenges.

But that does not mean Tesla is not still actively trying to make it even better.

In a new hardware update, Tesla has decided to change the material of the Cybertruck’s underbody panels from aluminum to carbon fiber, a move that aims to not only increase pricing efficiency but also improve strength.

RELATED:

Tesla Cybertruck is officially the safest pickup, IIHS says

Cybertruck Lead Engineer Wes Morrill confirmed the change was made to the Cybertruck recently after it was spotted by Coleton Guerin of Out of Spec. This particular trim level was a Cyberbeast, but it is being applied to all trims to keep supply chain efficiency high and have less variance across trim levels.

Morrill said that Tesla tested different materials for the underbody panel protection, and carbon fiber performed better than aluminum, which is what the company was using since its first deliveries in 2023.

Additionally, there are some efficiency improvements because Tesla can better form the areas around the bolts to keep underbody airflow cleaner than previously.

Carbon fiber is traditionally lighter and more durable than aluminum, which is why it is such a popular material among luxury automakers, and EV makers will utilize some of the materials around battery packs to save weight.

This is the first instance of Tesla utilizing carbon fiber on the Cybertruck’s exterior to help with overall performance and strength. As previously mentioned, Tesla used aluminum to protect the underside of the body, but it is pretty typical for the company to continue making engineering changes that will improve the car in the future.

Continue Reading

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

1 day ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading