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

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.

Advertisement

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.

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.

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

Texas man charged in fatal Tesla crash where he blamed Autopilot

Published

on

A Texas man has been arrested and charged with manslaughter after his Tesla crashed into a home last month, striking a woman inside and killing her. The driver, Michael Butler, claimed the vehicle was in self-driving mode, but information from Tesla shows that Butler overrode the system.

Butler was arrested on Wednesday and booked at the Harris County, Texas, jail. He remained in custody through Thursday and Friday; he did not enter a plea, and his next court hearing is scheduled for Monday.

Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration

There are a handful of new clues in the case that could clear Tesla of any wrongdoing, especially as the woman who was killed’s family, the Avilas, filed a wrongful death lawsuit against Tesla and Butler, seeking at least $1 million in damages.

Charging documents from the Harris County prosecutor now show that Butler, who was working DoorDash the evening of the accident, had been using Full Self-Driving mode without incident through the duration of multiple deliveries that evening.

In the moments leading up to the crash, while in FSD and approaching a left turn, Butler pressed the accelerator pedal, overriding FSD’s speed control, and continued to push it until it reached 100 percent. This caused rapid acceleration; the brake pedal was never pressed, and there is no data to show that Butler aimed to turn away from the curb or house.

The charging documents state:

“I noted that the brake pedal was never pressed in the final minute before the crash. I also did not see any data to indicate that the driver attempted to turn away from the curb that he eventually struck. Further, I observed that no mechanical error was detected or recorded by the vehicle before BUTLER and the Tesla struck the curb.”

Additionally, a forensic analysis of Butler’s phone showed that he searched Google around the time of the crash with queries questioning why FSD was “too timid,” “not aggressive enough,” and even searched, “FSD is not aggressive enough for city driving.”

The documents outlined this:

“Investigator Veal also informed me that he had received BUTLER’s cell phone from Deputy Amad and that HDAO digital forensics team had completed a data extraction and download of the phone. Multiple Google searches related to Tesla had been made from BUTLER’s phone in the months leading up the crash. I noted multiple searches in May of 2026 indicating an apparent frustration with Tesla’s FSD mode, including the following searches: “Tesla fsd not aggressive enough 2026 model,” “Tesla fsd not [sic) aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “tesla fsd too timid.”‘

Tesla had claimed just after the crash that its internal data showed Butler had overridden the system’s speed control and pressed the accelerator completely, causing the vehicle to travel at an excessive rate of speed. Eventually, the car slammed into Avila’s house, killing her.

Butler has now been formally charged with Manslaughter, a felony.

Continue Reading

News

Tesla’s strong Q2 deliveries: Four key drivers behind the surprise

Published

on

(Credit: Tesla)

Tesla shocked with its quarterly delivery report yesterday by reporting it delivered 480,126 vehicles in the second quarter of 2026, a 25 percent year-over-year jump that crushed Wall Street estimates of roughly 400,000–408,000 units. Production reached 451,758, with Model 3 and Model Y accounting for the vast majority.

The result ended two years of annual delivery declines and drew down inventory, signaling demand that outpaced earlier production.

Tesla bears had long warned that the expiration of the U.S. federal EV tax credit would hammer demand. Without the $7,500 incentive, they argued, American buyers would balk at higher effective prices, leading to a sharp slowdown.

Will Tesla thrive without the EV tax credit? Five reasons why they might

That narrative has not played out as predicted. While U.S. EV sales faced broader headwinds, Tesla’s global numbers held firm, underscoring the company’s ability to offset domestic pressure through other levers.

There are several plausible factors that explain Tesla’s strength during this quarter. Let’s take a look at them:

Rising Gas Prices

Rising gas prices provided a powerful tailwind, especially in the U.S.

Geopolitical tensions tied to the Iran conflict pushed fuel costs higher earlier in the year, amplifying the lifetime savings of electric vehicles. Even as oil prices later moderated, the psychological and financial impact lingered, encouraging fleet operators and private buyers to accelerate EV purchases. European sales rebounded sharply, helping drive the quarter’s outperformance.

Full Self-Driving Adoption

Advances in Full Self-Driving (FSD) supervised software also appear to have boosted appeal. Tesla expanded FSD availability in select European markets and continued refining the system.

For tech-oriented buyers, the promise of future autonomy and enhanced driver-assistance features adds perceived value beyond the car itself. This differentiation helps Tesla stand out in a crowded market where competitors focus primarily on hardware and basic range.

Pricing Strategy, Affordable Configurations

Tesla’s offerings and its pricing strategy during Q2 further stimulated demand. Tesla introduced lower-cost versions of the Model 3 and Model Y, widening accessibility without sacrificing core margins.

These moves countered affordability concerns and attracted buyers who had been waiting on the sidelines. Combined with attractive financing and leasing options, the pricing strategy converted interest into actual orders more effectively than many analysts expected.

Broad European Recovery

Supported by government incentives, corporate fleet electrification, and easing political headwinds around CEO Elon Musk, Tesla was supplied additional momentum through stronger registration numbers throughout Europe.

Strong exports from the Shanghai Gigafactory and a production ramp at Giga Berlin ensured supply met this resurgent demand. Corporate buyers, in particular, accelerated transitions to EVs to meet sustainability targets, providing a steady volume base.

These elements created a virtuous cycle that delivered the strong deliveries report. While bears correctly flagged the loss of the U.S. tax credit as a risk, Tesla’s diversified playbook demonstrated that it could remain resilient against those headwinds. The Q2 beat suggests the company remains adept at navigating shifting market conditions, even as competition intensifies.

Continue Reading

News

Tesla Semi involved in first known fatal crash in Nevada

Published

on

Credit: Tesla

A Tesla Semi was involved in a fatal collision on U.S. Highway 50 in Dayton, Nevada, on Sunday, June 28, 2026, marking the first known fatal crash involving the electric Class 8 truck. The incident occurred around 7:20 a.m. at the intersection with Traditions Parkway, approximately 40 miles east of Reno and close to Tesla’s Gigafactory Nevada.

According to the Lyon County Sheriff’s Office and the Nevada State Police Highway Patrol, a semi-truck struck two passenger vehicles stopped at a traffic signal. The truck hit the vehicles from behind. Two people were pronounced dead at the scene, and a third person suffered life-threatening injuries and was flown to a hospital, Forbes reported.

Preliminary statements gathered at the scene by the Lyon County Sheriff’s Office suggested the truck driver may have fallen asleep at the wheel. However, the Nevada Highway Patrol, which is leading the investigation, stated that the official cause has not yet been determined.

Additional information is expected to be released early the following week. The truck was seized for evidence as part of the ongoing probe.

Responders at the scene included deputies from the Lyon County Sheriff’s Office, personnel from the Nevada Highway Patrol, Central Lyon County Fire Department, and the Nevada Department of Transportation. The crash led to the temporary closure of U.S. 50 in both directions.

The Tesla Semi is Tesla’s battery-electric heavy-duty truck, produced at the nearby Gigafactory in Nevada. Authorities initially described the vehicle as a semi-truck; its make was subsequently confirmed through reporting and scene identification; an interesting bit of information here, as the Semi is not yet available publicly and many do not know that Tesla builds electric trucks.

The investigation remains active, with no further official details on contributing factors or vehicle systems released as of early July 2026.

This incident highlights ongoing scrutiny of commercial vehicle safety on Nevada highways, particularly involving fatigue. Law enforcement continues to gather evidence and witness statements.

Continue Reading