News
SpaceX’s first orbital Starship rocket engine is almost ready for testing
CEO Elon Musk says that SpaceX is “about a month away” from testing a rocket engine that will be essential for Starship and its Super Heavy booster to reach their full potential.
Known as Raptor Vacuum, the engine – as its name suggests – is a variant of the base Raptor engine optimized for maximum performance and efficiency in the vacuum of space. Although Starship could technically still function and likely reach orbit with only sea level-optimized Raptors installed, it would likely significantly limit the amount of payload it could carry into Earth orbit and would especially harm the ship’s performance to higher orbits and other planets.
Back in May 2019, Musk revealed that SpaceX had shifted gears again, forgoing a plan to begin orbital Starship flight operations with only sea level Raptors, gradually designing and phasing in RaptorVac engines much further down the road. Instead, SpaceX restarted (relatively) urgent work on the vacuum variant and Musk hinted that it would “aspirationally” be ready to support launches in the near term. A few weeks shy of a year later, Musk says that Raptor Vacuum testing could begin as early as June 2020.
For a variety of reasons, even if based directly off of an existing design, vacuum-optimized engines are typically much more complex than a comparable sea level variant. While efficiency is always relatively important for rocket engine design, it becomes even more paramount when dealing with vacuum rocketry, as the entire point of a dedicated vacuum-optimized engine is to eke as much efficiency as possible out of a launch vehicle’s orbital stage(s).
For example, even from a purely visual perspective, Merlin Vacuum (MVac) is substantially different when compared to the Merlin 1D engine it’s based on. Due to a number of major and largely unknown differences, the engines’ shared components are largely invisible. It’s unclear how similar they are but it’s safe to say that they share at least ~50% commonality. Obviously, the most apparent part of the difference between a vacuum-optimized engine and an atmosphere-optimized engine is the bell nozzle: MVac has a nozzle that is dramatically larger than M1D.
Raptor will be no different, with the sea-level variant featuring a nozzle about 1m (3.2 ft) in diameter, whereas RaptorVac’s bell will have a diameter closer to 2.5m (~8 ft). With SpaceX’s apparent May 2019 pivot back to working on RaptorVac now, the company has been working on a dedicated vacuum variant of the high-performance methane-oxygen engine for at least a full year. Now, perhaps beginning as early as June or July, Musk suggests that the first RaptorVac engine (SN0? SN1?) is almost ready to commence static fire testing.
The nature of that testing is a bit of a mystery. While it will almost certainly occur at SpaceX’s McGregor, Texas test and development facilities, it’s unclear if Raptor Vacuum’s first static fire test campaign will be attempted with the engine’s extended nozzle installed. Back in October 2019, Musk suggested that yes, Raptor Vacuum version 1.0 would have a nozzle small enough to operate at sea level without destroying itself or its test facilities. With Merlin Vacuum engines, SpaceX performs acceptance tests in Texas but only without their nozzle extensions installed. If Musk’s October 2019 comments remain true, that may not be the case for RaptorVac.
Either way, it will be thoroughly interesting to note the differences between RaptorVac and its sea level-optimized predecessor if or when Elon Musk or SpaceX releases photos of their newest engine as it nears its first major tests. Simultaneously, SpaceX is also readying a sea-level Raptor for its inaugural static fire test while attached to a full-scale Starship prototype, while the first test with three Raptor engines installed could be attempted just a few weeks from now.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
