News
SpaceX rolls Raptor Vacuum engines to launch pad for Starship’s next tests
For the second time, SpaceX is gearing up to install a full six Raptor engines on the first orbital-class Starship prototype.
This time around, though, there’s reason to believe that the preparations SpaceX is making aren’t a false start and could culminate in one or several record-breaking Starship static fires as early as next week.
SpaceX installed Raptors on Starship S20 for the first time in early August, outfitting the 50m (165 ft) tall prototype with a full six engines as part of a fit test that ultimately saw it installed on top of a Super Heavy booster. Ship 20 only spent an hour on top of Booster 4, though, and was quickly returned to Starbase build site for Raptor removal and final outfitting. Ship 20 was then rolled back to the launch site and installed on one of two suborbital launch mounts and test stands in mid-August, where it has sat ever since.
Between September 4th and 10th, SpaceX then appeared to install three sea-level-optimized Raptor Center (RC) engines and one Raptor Vacuum (RVac) engine on Starship S20 before the prototype had completed any proof testing. Whether that set of installs was a fit test or an aborted attempt at full installation, SpaceX seemingly paused at three or four Raptors and ultimately removed the lone RVac and one or more of S20’s sea-level engines. Another sea-level Raptor was (re)installed on September 15th.
After a frenetic month of back and forth with no obvious rhyme or reason, all of Ship 20’s Raptors were removed and a series of hydraulic rams used to simulate engine thrust – removed, unused, back in August – were reinstalled. Starship then completed pneumatic and cryogenic proof tests in the last few days of September.
After another ten or so days of unusual downtime, SpaceX began reinstalling Raptors on Ship 20 – one sea-level and one vacuum – around October 10th for a static fire test campaign that began about a week later. Finally, on October 21st, SpaceX fired up the orbital-class prototype for the first time, also completing the first test of a Raptor Vacuum engine installed on a Starship. Barely an hour later, Starship S20 performed a second test, simultaneously firing up both RVac and RC engine in another first.
Barely a full day after that successful back-to-back static fire test, SpaceX rolled two more sea-level Raptors to the suborbital pad and installed them on Ship 20. Another unusual week of downtime later and, on October 28th, SpaceX has rolled two more Raptor Vacuum engines from the build site to the launch pad and staged them beside Starship. Once installed, Starship S20 will, for the second time, be fully outfitted with six Raptors. Having already fired up two of those engines without needing either replaced, though, there’s a decent chance that all six will actually be used before Ship 20’s next bout of engine removal/installation deja vu.
SpaceX has never fired more than three engines at a time on a Starship prototype or at its suborbital test site, so a number of firsts potentially lay before Ship 20 as it nears a second round of static fire testing. There is some uncertainty as to whether the suborbital test stands can actually handle the stress from static fires with more than three Raptors, but if they can, then S20 will likely be the first prototype to ignite more 4+ engines and could become the first Starship to fire all six engines at once.
SpaceX currently has one possible test window scheduled from 10am to 6pm CDT on Monday, November 1st, though it could be another week or more before Starship S20’s next static fire attempt if past trends continue.
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
