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 has extended its Bay Area ride-hailing service to include pickups and drop-offs at San Francisco International Airport (SFO). The update, shared via the company’s official channels on July 21, allows users in the region to request rides directly to and from one of California’s busiest airports.
The expansion builds on Tesla’s secured limousine permit for SFO operations. Public records show the permit became effective March 20, 2026, and remains active through January 31, 2027. Tesla vehicles operating the service now display authorized limousine permits issued by the City and County of San Francisco.
Our Bay Area rideshare service now goes to SFO ✈️
— Tesla AI (@Tesla_AI) July 21, 2026
Tesla’s ride-hailing program in California relies on Model Y vehicles equipped with Full Self-Driving (Supervised) technology. Human safety drivers remain present in compliance with state regulations, distinguishing the service from fully driverless operations.
The Bay Area geofence covers a broad area spanning north of San Francisco to south of San Jose, offering extensive connectivity across the region.
UPDATE: Elon Musk reveals why Tesla didn’t say ‘Robotaxi’ upon California launch
This SFO addition follows earlier progress at other Bay Area airports. Tesla previously expanded service to San Jose Mineta International Airport (SJC) in late 2025. The company had engaged with SFO, SJC, and Oakland International Airport officials as early as September 2025 to secure necessary approvals for passenger transport.
The service provides a new option for travelers seeking electric, app-based transportation integrated with Tesla’s ecosystem. Rides are booked through Tesla’s dedicated ride-hailing application, which handles matching, routing, and payments. Pricing follows standard ride-hailing models, with potential adjustments based on distance, time, and demand.
Tesla’s California ride-hailing program launched in July 2025 with an initial invite-only rollout in the Bay Area. It started alongside operations in Austin, Texas, marking the company’s second major U.S. market.
The Bay Area remains a primary focus in California, with service centered on high-demand corridors connecting residential, commercial, and now major transportation hubs. This latest airport integration represents a practical step in Tesla’s broader mobility ambitions within the state.
Tesla has officially revealed its 2026 Summer Update, which comes with a variety of crazy new features, including Navigation fixes that owners have been wanting for months.
Tesla routinely releases a larger update with the Spring, Summer, Fall, and Winter updates, where it ships a variety of new features, bug fixes, and other additions to customer cars.
The 2026 Spring Update featured things like “Hey Grok” voice assistance, a redesigned self-driving app, Unreal Engine visual upgrades, and more.
🚨 TESLA’S SUMMER UPDATE FOR 2026 IS HERE:
Featuring:
✅ Self-Driving Stats in Mobile App
✅ Caraoke with Scoring
✅ Automatic Navigation
✅ Preferred Routes
✅ Set Arrival Energy from Mobile App
✅ Send Custom Wraps from Mobile App
✅ Rear Display Lock
✅ Other Improvements
🔌… https://t.co/C9IW3egEhH
— TESLARATI (@Teslarati) July 21, 2026
Tesla’s Summer Release has about ten new features; we’ll show you each and detail them below:
New Grok Voice Commands
“Grok can now make phone calls, search and play music, adjust climate, open the glovebox, and answer questions about your Tesla.”
Self-Driving Stats in Mobile App
“View and share self-driving stats from the mobile app.”
Caraoke With Scoring
“Caraoke now scores your singing while in Park. High scores are saved to your Tesla profile.”
Automatic Navigation
“Automatic Navigation now adapts to your routine.
In addition to Home, Work, and upcoming calendar events, your vehicle can now suggest and route to places you visit regularly – like a school drop-off on the way to work, or the gym on the way home.”
Preferred Routes
“For a more personalized experience, navigation now prioritizes routes that you’ve taken before”
Set Arrival Energy from Mobile App
“Set your desired Arrival Energy from your phone.”
Send Custom Wraps from Mobile App
“Skip the USB drive and upload a custom wrap of your car from the mobile app. Instructions for creating a custom wrap here: https://github.com/teslamotors/custom-wraps.”
Rear Display Lock
“Kids can watch content on the rear screen, but only the front row can control it through the rear screen app.”
Other Improvements
- Find Superchargers by name when searching for a destination
- Add Apple Music songs to queue from search and artist page
- Set your preferred zoom level for the Self-Driving visualization
- Intro animations for new Model 3 and Y
Tesla’s reason for Starlink integration on Cybercab might surprise you, as the company’s Head of AI, Ashok Elluswamy, finally shed some light on the reason they are putting a satellite internet terminal on its ride-hailing-geared vehicle.
On Monday, Tesla officially confirmed that it would integrate Starlink V5 terminals into Cybercab vehicles, something many Tesla fans had figured the company would do, as the vehicle is primarily geared toward giving rides without any passenger intervention.
Starlink V5 directly integrated in Cybercab pic.twitter.com/FxzTtzjB6I
— Tesla (@Tesla) July 20, 2026
The ability to access the internet would allow riders to work or play in the car with their devices. It seemed like a more-than-reasonable feature to add to the Cybercab, which made its way off the production lines for the first time earlier this year.
Tesla reveals first vehicle model to receive Starlink integration
However, the move is not for the rider, as Elluswamy confirmed on Monday night. Instead, it’s actually for Tesla to be able to have a constant connection to the cars in the Robotaxi fleet so it can troubleshoot issues, contact riders, or resolve other issues.
Elluswamy said:
“It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.”
It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.
— Ashok Elluswamy (@aelluswamy) July 20, 2026
Many initially assumed the option of constant connectivity would be enabled on the Cybercab for passenger entertainment or work. With the Cybercab, passengers won’t be doing anything but enjoying the ride, so it seemed more than logical that they would be hanging out with Starlink internet access as an amenity.
However, Tesla’s primary concern with Robotaxi is safety, and nailing these first unsupervised rides is a crucial step to setting a good narrative on how effective driverless transportation can be.
Being able to get in touch with passengers or a vehicle if something is wrong is a crucial part of the overall experience, and preventative measures are being taken by Tesla to ensure a smooth process, even in the worst-case.
Tesla expands ridesharing service in California to new hotspot
Tesla reveals 2026 Summer Update with crazy fixes to Nav and more
