News
SpaceX begins installing new ‘Raptor 2’ engines on Super Heavy booster
SpaceX has begun installing new ‘Raptor 2’ engines on Super Heavy Booster 7 after the prototype completed a range of tests and returned to the company’s South Texas ‘Starbase’ rocket factory.
Earlier this month, SpaceX transported Booster 7 (B7) in the opposite direction, returning the 67-meter (~220 ft) tall rocket to Starbase’s orbital launch site (OLS) for the second time after it was forced to head back to the factory for repairs. Repairs completed, SpaceX dove headfirst into the process of verifying that the booster had been returned to full health and immediately filled its tanks to the brim with at least 3000 tons (>6.5M lb) of liquid nitrogen and oxygen – better known as a cryogenic proof test.
Less than 48 hours after completing its first post-repair test, Booster 7 sailed through another full cryoproof test without losing a beat. On May 13th, two days later, SpaceX attached a crane to Super Heavy B7 and removed it from the orbital launch mount before rolling the rocket back to Starbase’s build site on May 14th. Without official confirmation, which is increasingly rare, it was impossible to determine the results of the testing with certainty, but the speed of the process and Booster 7’s rapid launch mount removal made the two most extreme outcomes the most likely.
A quick return to the build site could have been explained by a significant vehicle failure or a major issue with SpaceX’s repair job – no point in continuing to test a vehicle that can’t be fully tested. On the exact opposite hand, a near-perfect test campaign in which all objectives were more or less achieved without major hiccups could also explain the quick return. In general, the evidence was in favor of the more optimistic explanation. Had a major issue been uncovered during the first post-repair cryoproof, it’s difficult to imagine that SpaceX would have completed the exact same test – in full less than 48 hours later.
However, SpaceX moved an in-situ Raptor engine installation stand towards Booster 7 and the orbital launch mount shortly before testing restarted, hinting – for the moment – that the company wanted to begin installing Raptor engines immediately after cryoproof testing. But mid-way through testing, the stand was moved back to its storage area and Super Heavy was instead removed from the mount and returned to the factory, adding a little uncertainty.
Concerns were immediately assuaged on May 17th when SpaceX was spotted moving Raptor engines from a production tent to the ‘megabay’ assembly building containing Booster 7. While the location of the new bay makes it difficult to peek inside from public viewpoints, preventing direct confirmation, it’s very likely SpaceX has begun installing new Raptor 2 engines on Super Heavy B7.
Additionally, confirming some of the more optimistic speculation about SpaceX’s decision to move Booster 7 back to build site, two of the three Raptor engines spotted on May 17th were also labeled “E26” and “E28.” Unless SpaceX’s engine numbering conventions have changed, the labels identify the engines as three of 20 ‘Raptor Boost’ engines that will ultimately populate the outer ring of Super Heavy B7’s aft end. More importantly, the installation of any Raptor Boost 2 (RB2) engines likely indicates that SpaceX has decided to install a full set of 33 Raptors on the booster before kicking off static fire testing.
To limit risk, SpaceX could have begun test-firing Booster 7 with just 1-3 Raptor engines installed and gradually added more as confidence grew. Instead, SpaceX appears to have accepted the added risk of losing 33 brand-new Raptor 2 engines in one fell swoop in return for the possibility of a much faster test campaign. If there are no major surprises during static fire testing, in other words, Booster 7 could be ready for flight far more quickly if the process begins with all 33 engines already installed. Installing Booster 7’s Raptors, heat shield, and aerocovers will be easier back at the build site.
Doing it all at once should also help prevent Booster 7 from suffering Booster 4’s fate and wallowing, unfinished, for months without completing a single useful test. If the gamble works, the first stage of a two-stage Starship could be ready for an orbital launch attempt in just a few months. If the gamble fails and Booster 7 is damaged, destroyed, or otherwise unable to pass the necessary tests, SpaceX will simply move on to Booster 8 sooner than later, having wasted less time on a more cautious Booster 7 test campaign.
It’s unclear how long it will take SpaceX to install all 33 Raptors, construct a heat shield around those engines, and finish buttoning up the rest of Booster 7. In an adjacent assembly bay, SpaceX appears to have nearly finished assembling a similarly upgraded Starship – Ship 24 – that’s first in line to ride Booster 7 into space. The company has also tentatively requested road closures for three 12-hour test windows on May 23rd, 24th, and 25th that either vehicle could use.
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
