News
SpaceX’s Starship Raptor Vacuum engine plans laid out by CEO Elon Musk
Elon Musk says that SpaceX Starship engine upgrades are on track to begin static fire tests of a Raptor Vacuum variant as few as a “couple months” from now.
Designed to enable more efficient performance in thin atmosphere or vacuum, Musk admitted that the first version(s) of Raptor Vacuum (RVac) will likely be a compromise between efficiency and speed of development. Nevertheless, the faster SpaceX can prepare Raptor Vacuum for flight, the easier it will be for Starship to begin serious (sub)orbital flight tests.
As it turns out, SpaceX’s first and only official render of Raptor – published in September 2016 – showed the engine’s vacuum-optimized variant. In the years since, CEO Elon Musk has vacillated between keeping the vacuum engines as a central Starship feature and simply replacing them with regular sea level Raptors to expedite the spacecraft’s debut. The 2016 and 2017 vehicles featured a mixture of vacuum and sea-level engines, whereas Musk revealed a vehicle with sea-level engines only in 2018.
Perhaps less than a month after Musk’s September 2018 presentation, the SpaceX CEO made the decision to radically redesign the vehicle – newly christened Starship and Super Heavy – by moving from a carbon composite aerostructure to stainless steel. At first, the seven SL Raptors remained a part of the design, but Musk took to Twitter in 2019 to indicate that SpaceX had changed gears again and had reprioritized Raptor Vacuum development.
This came as a bit of surprise and it should go without saying that there’s a significant chance that Musk/SpaceX will oscillate in the opposite direction once again before Raptor Vacuum is actually ready for flight. This time, though, Musk has sketched out a development schedule and strategy that suggests SpaceX is much more serious this time.
Most notably, Musk claims that the first Raptor Vacuum prototype could be ready for static fire testing just a “couple months” from now, an immensely ambitious schedule for any large liquid rocket engine development program. Nevertheless, Musk did indicate that the “V1.0” Raptor Vacuum design would be significantly compromised and “suboptimal”, an intentional decision to prioritize the engine’s “speed of development”.
Even then, Musk believes that the first variant – featuring a shortened bell nozzle – could still be up to 12% more efficient than sea level Raptors and thus already 70-80% of the way to the physical limit of methane-oxygen rocket efficiency.
On a positive note, shrinking V1.0 Raptor Vacuum’s nozzle a bit from its nominal length will likely mean that SpaceX can static fire fully-integrated engines at its McGregor, TX test facilities, critical for speedy development. If not, the company has experience with alternatives through Merlin Vacuum, which can only be tested on the ground with its lengthy nozzle detached. This method just makes it dramatically harder to optimize a vacuum nozzle design, as full-scale, flight-like testing is nearly impossible if a given vacuum engine can’t be tested on the ground with said nozzle installed.
Vacuum engines need such large and unwieldy nozzles in order to make them as efficient as possible. In a very simplistic sense, a rocket engine nozzle directs the flow of superheated, ultrafast gases in order to squeeze as much momentum transfer as possible out of available propellant. The lower the pressure of the surrounding atmosphere is, the more those gases will expand immediately after leaving the nozzle – giant vacuum nozzles simply try to harness the additional momentum available from that extra expansion. This is why rocket exhausts appear to spread and thin out as launch vehicles reach higher and higher altitudes.
In this sense, the perfect theoretical vacuum nozzle is quite literally infinitely long. The job of vacuum rocket engineers is to find the perfect balance between that impractical theoretical perfection and the limits of real-world materials and dynamics. In theory, SpaceX’s sea-level Raptor engines have already been designed to operate in vacuum conditions, while the engine’s closed-cycle design and regeneratively (i.e. propellant) cooled nozzle should apply well to a vacuum design.
If SpaceX is lucky, there will be few roadblocks in the way of simply lengthening a SL Raptor-style nozzle and calling it a day, in which case it would be impressive but not all that surprising if SpaceX is actually able to begin RVac testing before the end of 2019. Once a rough V1.0 engine is in place, the process of optimizing efficiency can be done slowly and methodically, all while exploiting an unprecedented wealth of data from flight and orbit-tested Raptor Vacuum engines.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
