News
SpaceX installs Raptor Vacuum engine on first orbital-class Starship
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.
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.
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.
Tesla welcomed JPMorgan analysts to one of its factories earlier this month, with the Wall Street firm highlighting its findings in a new note to investors. One of the more pertinent pieces of information is that Tesla admitted to slowly integrating Model Y vehicles into its Robotaxi fleet, but it has a good reason.
JPMorgan analysts recently toured Tesla’s Fremont Factory and met with the company’s investor relations team, emerging with a clearer picture of the automaker’s Robotaxi strategy. According to the bank’s note, Tesla is intentionally limiting the addition of Model Y vehicles to its existing Robotaxi fleet.
The firm’s analysts said:
“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change in performance, comparable to the leap from V13 to V14. The V15 upgrade encompasses seven core technologies, with ~40% of those currently being tested in the robotaxi fleet, where initial feedback has been encouraging.”
JPMorgan after meeting with Tesla recently in Fremont:
“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change… pic.twitter.com/W9yGCWRT3C
— Sawyer Merritt (@SawyerMerritt) August 20, 2026
Far from signaling delays or doubts about autonomy, the move reflects strong management confidence in the near-term scalability of the purpose-built Cybercab.
Tesla has operated its Robotaxi service primarily with modified Model Ys since launching in Austin and expanding to other markets. Yet the company is now deliberately holding back further Model Y conversions. The rationale is straightforward: leadership believes the Cybercab, a two-seat, steering-wheel- and pedal-free vehicle optimized for high utilization, can ramp production and deployment more efficiently in the coming months.
This dedicated form factor promises better unit economics for the majority of rides, which typically involve one or two passengers, while freeing consumer Model Y inventory for retail sales.
Supporting this pivot is Full Self-Driving (FSD) software version 15, which Tesla describes as a genuine step-change in performance, comparable to the leap from V13 to V14. The update incorporates seven core technologies; roughly 40 percent are already undergoing real-world testing in the current Robotaxi fleet, with early feedback described as encouraging.
Tesla is carefully managing software development to minimize regressions in core driving functions as new capabilities are added. Management positions V15 as the primary gateway to scaling unsupervised FSD. Importantly, the existing AI and Hardware 4 stack is already capable of running V15 and supporting unsupervised operation.
Cybercab itself is only the first vehicle on the platform. Tesla reiterated that additional form factors will follow, pointing to concepts such as the earlier “Robovan” demonstration as examples of how the architecture can evolve.
Tesla’s mysterious Robovan makes a sneak peek with Optimus in Terafab video
Parallel progress continues on the Optimus humanoid robot, which remains on track for start of production in the coming months, with commercial sales possible as early as the second half of 2027. Generation 3 details will be revealed closer to production to preserve competitive advantages, while Generation 4 scope will draw on real-world Gen 3 experience.
JPMorgan left the meeting with a deeper appreciation for Tesla’s manufacturing automation and maintained its $475 price target. The decision to slow Model Y Robotaxi integration is therefore not a setback but a calculated prioritization of a more efficient, purpose-built solution that management believes is ready to scale.
SpaceX CEO Elon Musk announced today that the company will likely attempt to catch the Starship upper stage with its launch tower arms “in a few months.”
In a post on X, Musk wrote, “Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.” He added that the first reflight of a Starship vehicle is expected by the end of 2026 or early 2027, describing it as “a fork in the road of history for consciousness reaching the stars.”
Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.
First reflight of the ship will be either end of this year or early next. That will be a fork in the… https://t.co/O5g9pqrzyo
— Elon Musk (@elonmusk) August 20, 2026
Musk’s prediction comes amid ongoing progress toward full reusability of the Starship system, a two-stage rocket designed for rapid turnaround and dramatically lower launch costs. Catching the upper stage, known simply as “ship,” with the Mechazilla tower’s mechanical arms would mark a major milestone. It would allow both stages to return directly to the launch site for quick refurbishment and reuse, eliminating the need for ocean recovery.
Musk has previously signaled plans for a ship catch. In July, shortly after SpaceX’s wildly successful Starship 13 mission, he stated that the company would attempt to catch the ship with the tower on the next flight unless problems emerged in the mission data review. Earlier comments also outline conditions such as successful soft ocean landings before attempting a land recovery to minimize risk.
SpaceX has solved Starship’s biggest challenge, Elon Musk says
The latest update from Musk adjusts this timeline to a few months, reflecting the iterative nature of the test campaign.
SpaceX has already demonstrated the tower catch technique successfully with the Super Heavy booster on a couple of occasions. The first successful booster catch occurred during Flight 5 in October 2024, when the massive first stage returned to the Starbase pad in Texas and was plucked from the air by the tower arms.
Additional catches followed on later flights, including Flight 7, proving the concept for the booster and building confidence in the system as a whole.
Achieving a similar catch for the upper stage would represent a significant step forward. The ship returns from much higher speeds and greater heat loads after orbital or near-orbital flight. Success would advance SpaceX’s goal of full and rapid reusability, potentially reducing the cost of access to orbit by a factor of 100 or more and supporting ambitions for frequent satellite deployments, lunar missions, and eventual Mars flights.
Musk has long emphasized that true reusability, refueling rather than discarding hardware, is essential for making humanity a multi-planetary species.
As SpaceX continues refining Starship through successive test flights, the coming months will test whether the ambitious catch timeline can be met. The combination of prior booster successes and improving ship landing precision suggests the company is steadily closing in on this historic capability.
SpaceX has achieved an incredible milestone by launching its 11,000th Starlink satellite into orbit.
This accomplishment occurred during the Starlink Group 17-50 mission, which lifted off on August 19 at 04:01 UTC from Space Launch Complex 4 East at Vandenberg Space Force Base in California.
Falcon 9 launches 24 @Starlink satellites from California pic.twitter.com/UscpmAxDls
— SpaceX (@SpaceX) August 19, 2026
A Falcon 9 rocket carried 24 Starlink V2 Mini satellites on this flight, successfully deploying them into low Earth orbit approximately one hour after liftoff. The first stage booster, identified as B1097 on its twelfth flight, landed successfully on the droneship Of Course I Still Love You in the Pacific Ocean.
According to tracking data compiled around that date, this deployment brought the total number of Starlink satellites in orbit to just over 11,000.
The Starlink program began with test satellites known as Tintin A and B, launched on February 22, 2018. The first operational batch of 60 Starlink satellites followed on May 24, 2019, when a Falcon 9 rocket lifted off from Cape Canaveral. Those initial satellites marked the start of a rapid expansion that has continued for more than seven years.
SpaceX has conducted hundreds of dedicated Starlink missions since then, routinely launching batches of 20 to 30 satellites at a time using reusable Falcon 9 rockets. By mid-2026, the company had already surpassed 12,000 total satellites launched across all versions, with continuous replacements for units that deorbit as designed to manage space debris.
Looking ahead, SpaceX continues to expand the Starlink constellation to enhance global broadband coverage, capacity, and speed. The network already serves millions of users across more than 160 countries and supports applications ranging from residential internet to maritime, aviation, and emergency services.
Future plans center on next-generation hardware, including larger V3 satellites capable of delivering substantially higher throughput, which require the increased payload capacity of the Starship vehicle currently under development and testing.
In July, SpaceX submitted an application to the Federal Communications Commission seeking authority for a Gen3 constellation of up to 100,000 satellites. These spacecraft would operate in very low Earth orbit shells at altitudes near 325 kilometers and 475 kilometers. The filing requests use of existing Ku, Ka, V, and E band spectrum along with new greenfield W and D band frequencies between 92 and 275 GHz.
SpaceX states that the expanded system aims to deliver multi-gigabit symmetrical broadband to consumers, enterprises, governments, and billions of AI-powered devices worldwide while handling a majority of global internet traffic. Approval and subsequent deployment would depend on regulatory review and the operational readiness of Starship for high-volume launches.
This ambitious scale reflects SpaceX’s ongoing commitment to providing ubiquitous high-speed connectivity from space.
Tesla admits to slow Model Y Robotaxi integration, but for a good reason
Elon Musk gives a timeline for SpaceX’s first Starship catch attempt
