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

Elon Musk

NASA updated Artemis III and SpaceX’s role just got more complicated

SpaceX’s Starship is the key to NASA’s Moon plan and the timeline is already slipping.

Published

on

By

SpaceX has been at the center of NASA’s Moon ambitions for five years, and the updated Artemis III plan recently released by NASA makes that relationship more visible than ever. In April 2021, NASA awarded SpaceX a $2.89 billion contract to develop the Starship Human Landing System, selecting it as the sole provider to land astronauts on the Moon under Artemis III. Blue Origin filed legal protests, lost, and eventually received its own contract, but SpaceX was always the program’s primary lander contractor.

The original plan called for Starship to land two astronauts on the lunar south pole. That mission slipped as Starship development ran behind schedule, and in February 2026, NASA officially revised the Artemis III architecture entirely. The mission will now remain in low Earth orbit and serve as a crewed rendezvous and docking test between the Orion spacecraft and both the SpaceX Starship HLS pathfinder and Blue Origin’s Blue Moon Mark 2 pathfinder, with the actual Moon landing pushed to Artemis IV in 2028.

What makes SpaceX’s position particularly significant is the direct line between this week’s Starship V3 launch and the Artemis timeline. The Starship HLS is essentially a modified version of the V3 upper stage, meaning SpaceX cannot realistically prepare a lander for a 2027 docking test until it has demonstrated that the base vehicle flies reliably at scale. Flight 12, targeting this week, is the first data point in that sequence.

SpaceX Board has set a Mars bonus for Elon Musk

NASA has spent nearly $7 billion on Human Landing System development since awarding contracts to SpaceX and Blue Origin in 2021 and 2023, and NASA administrator Jared Isaacman has indicated a desire to drive down costs going forward. As Teslarati reported, before Starship HLS can put anyone on the Moon it has to solve a problem no rocket has demonstrated at scale, which is refueling in orbit, requiring approximately ten tanker launches worth of propellant loaded into a depot before the lander has enough fuel to reach the lunar surface.

The Artemis III mission described by NASA is essentially a stress test for every system that needs to work before any of that happens.

SpaceX has gone from a launch contractor to the single most critical hardware provider in America’s return-to-the-Moon program. With an IPO targeting a $1.75 trillion valuation and Elon Musk’s compensation tied directly to Mars colonization, the pressure on every Starship milestone between now and 2028 has never been higher.

Continue Reading

News

Tesla is making sweeping improvements to Robotaxi

Published

on

Credit: Tesla

Tesla is continuing to refine and improve its Robotaxi program from A to Z, and it is now going to make some sweeping changes to the smartphone app portion of the suite.

The company is aiming to make some sweeping changes with the release of Robotaxi app version 26.4.5, which was recently decompiled by Tesla App Updates on X. The update reveals significant new code, focused on remote operations, safety protocols, and seamless autonomous ride-hailing.

These improvements evidently signal Tesla’s preparations for scaling unsupervised Cybercab deployments, particularly the steering wheel-less variants spotted in production. The enhancements emphasize providing a reliable experience that gives passengers support when needed, along with operational efficiency.

Remote Operator Voice Calls

One standout addition is support for remote operator voice calls. The app now includes a dedicated native voice-communication system linking passengers directly to Tesla teleoperators via the vehicle’s cabin microphone and speakers.

This feature allows real-time assistance during rides, addressing issues like navigation questions or comfort adjustments without disrupting the autonomous journey. It builds on existing support protocols, making human intervention more accessible and intuitive.

Proactive Remote Assistance

The update introduces proactive remote assistance capabilities. Rather than waiting for passenger-initiated requests, the system can anticipate and offer help based on monitored conditions.

This might include something like suggesting route changes, climate adjustments, or addressing potential delays. By integrating AI-driven monitoring with human oversight, Tesla aims to deliver a smoother, more attentive experience that exceeds traditional ride-sharing services.

Manual Override and Remote Start for Steering Wheel-less Cybercabs

A key highlight for the wheel-less Cybercab fleet is manual override plus remote start functionality. Fleet operators and technicians can now temporarily take control or remotely start vehicles lacking steering wheels. This is crucial for lower-speed maneuvers, such as getting vehicles from tight parking situations or even performing maintenance.

Controls are strictly limited for safety–typically to speeds under 2 MPH–ensuring these interventions remain emergency measures only.

Tesla is adding a secure “Enable Manual Drive” mode that will allow those fleet operators or others to take control temporarily.

Additionally, a Remote Start feature, which authorizes an empty vehicle to begin a driverless ride alone.

Ride-Hailing and Dispatch Features

Ride dispatch has been enhanced with soft-matching and multi-stop support. The app can intelligently pair riders with available Cybercabs while accommodating multiple destinations in a single trip.

This optimizes fleet utilization, reduces wait times, and improves efficiency for shared rides. Soft-matching likely considers factors like proximity, rider preferences, and vehicle availability for better user satisfaction.

Rider-Cabin Sync, Real-Time Routing

New synchronization tools allow the rider’s app to mirror and control cabin settings like seating, climate, and entertainment directly from their phone. Real-time routing updates adapt dynamically to traffic or road conditions, while dynamic safety monitoring continuously assesses the environment.

The app can now push updates directly to the main screen, enabling Center Display Control. Additionally, there is a dedicated navigation protocol sharing the exact coordinates of road closures and construction, which could prevent the car from getting stuck and needing manual override.

These features create a cohesive, responsive experience where the vehicle and app work in harmony.

Kill Switch

A high-security command lets Tesla completely freeze a vehicle’s ability to drive. This would take the vehicle out of the Robotaxi fleet for any reason Tesla sees fit, and would not allow it to be put into gear even with the correct equipment, like valid keys.

Continue Reading

Elon Musk

SpaceX just forced Verizon, AT&T and T-Mobile to team up for the first time in history

AT&T, T-Mobile, and Verizon just joined forces for one reason: Starlink is winning.

Published

on

By

Starlink D2D direct to device vs Verizon, AT&T (Concept render by Grok)

America’s three largest wireless carriers, AT&T, T-Mobile, and Verizon, announced on On May 14, 2026 that they had agreed in principle to form a joint venture aimed at pooling their spectrum resources to expand satellite-based direct-to-device (D2D) connectivity across the United States in what can be seen as a direct response to SpaceX’s Starlink initiative. D2D, in plain terms, is technology that lets a standard smartphone connect directly to a satellite in orbit, the same way it connects to a cell tower, with no extra hardware required.

The alliance is widely seen as a means to slow Starlink’s rapid expansion in the satellite internet and mobile markets. SpaceX’s Starlink Mobile service launched commercially in July 2025 through a partnership with T-Mobile, starting with messaging before expanding to broadband data. SpaceX secured access to valuable wireless spectrum through its $17 billion deal with EchoStar, paving the way for significantly faster satellite-to-phone speeds.

The FCC just said ‘No’ to SpaceX for now

SpaceX was not shy about its reaction. SpaceX president and COO Gwynne Shotwell responded on X: “Weeeelllll, I guess Starlink Mobile is doing something right! It’s David and Goliath (X3) all over again — I’m bettin’ on David.” SpaceX’s VP of Satellite Policy David Goldman went further, flagging potential antitrust concerns and asking whether the DOJ would even allow three dominant competitors to coordinate in a market where a new rival is actively entering.


Financial analysts at LightShed Partners were blunt, saying the announcement showed the three carriers are “nervous,” and pointed to the timing: “You announce an agreement in principle when the point is the announcement, not the deal. The timing, weeks ahead of the SpaceX roadshow, was the point.”

As Teslarati reported, SpaceX’s next generation Starlink V2 satellites will deliver up to 100 times the data density of the current system, with custom silicon and phased array antennas enabling around 20 times the throughput of the first generation. The carriers’ JV, which has no definitive agreement, no financial structure, and no deployment timeline yet, will need to move quickly to matter.

Elon Musk’s SpaceX is targeting a Nasdaq listing as early as June 12, aiming for what would be the largest IPO in history. With Starlink now serving over 9 million subscribers across 155 countries, holding 59 carrier partnerships globally, and now powering Air Force One, the carriers’ joint venture announcement landed at exactly the wrong time to look like anything other than a defensive move.

Continue Reading