News
SpaceX’s upgraded Super Heavy booster sails through first major test
SpaceX’s first upgraded 33-engine Super Heavy booster appears to have passed a crucial test with surprising ease, boding well for a smooth qualification process.
Attempting that test so early on did not appear to be SpaceX’s initial plan. Instead, shortly before Super Heavy Booster 4’s third and likely final removal from Starbase’s ‘orbital launch mount’ (OLM) on March 24th, SpaceX transported a massive structural test stand from a Starbase storage yard to the orbital launch site (OLS), where technicians have focused on modifying nearby ground systems to support apparent structural testing of Super Heavy Booster 7. As of March 31st, all available evidence suggested that SpaceX was preparing that stand to verify Booster 7’s mechanical strength and simulate the major stresses it might experience before investing a significant amount of time and resources in qualification testing.
However, SpaceX appeared to change its plans at the last minute.
Instead of starting with structural testing, after a brief two-day pause, SpaceX rolled Super Heavy B7 into place and craned the giant booster onto the orbital launch mount on April 2nd. On April 3rd, the launch mount’s “quick disconnect” device connected Super Heavy to the pad’s ground systems. On April 4th, just two days after its installation on the OLM, Super Heavy B7 kicked off the first in a series of qualification tests that will determine when or if the booster ultimately supports Starship’s first orbital launch attempt.
If testing goes perfectly, SpaceX CEO Elon Musk recently stated that Starship and Super Heavy – likely Ship 24 and Booster 7 – could be ready for an inaugural orbital launch attempt as early as May 2022. SpaceX appears to have leaped headfirst into Super Heavy Booster 7 qualification testing in a move that significantly increases the likelihood of meeting that extremely ambitious schedule. Normally, with a first-of-its-kind prototype debuting multiple significant design changes, SpaceX would start slow, possibly beginning with a basic pneumatic proof test to verify structural integrity at flight pressures – about 6.5-8.5 bar (95-125 psi) – with benign nitrogen gas before calling it a day.
With Booster 7, SpaceX likely still performed a quick pneumatic proof but then immediately proceeded into a full-scale cryogenic proof test. With Super Heavy B4, for example, SpaceX performed several increasingly ambitious cryogenic proof tests, filling the booster more and more each attempt but never actually topping it off. On Booster 7’s very first day of testing and first cryogenic proof attempt, SpaceX fully loaded the upgraded Super Heavy with a cryogenic fluid (likely liquid nitrogen) in just two hours – all with no significant unplanned holds (pauses).
In those two hours, SpaceX likely loaded Super Heavy B7’s liquid methane (LCH4) and oxygen (LOx) tanks with roughly 3400 metric tons (~7.5M lb) of liquid nitrogen (LN2) – not far off what Super Heavy would actually weigh at liftoff. At the peak of the test, Booster 7 was almost entirely covered in a thin layer of ice produced as the cryogenic liquid inside its tanks froze water vapor in the humid South Texas air onto its skin – an effect that effectively turns uninsulated cryogenic rockets into giant fill gauges. On top of running into no apparent issues, Super Heavy B7’s first cryogenic proof is also the first time any Super Heavy prototype has been fully filled during testing – an important milestone for any rocket prototype, let alone the largest rocket booster ever built.
Completing a full cryogenic proof test on its first try makes Booster 7 fairly unique among all Starship prototypes – not just Super Heavies. The contrast with Booster 4, which barely completed a handful of partial cryogenic proof tests in more than half a year spent at Starbase’s orbital launch site, is also extremely encouraging, suggesting that Booster 7 won’t be sitting inactive for months at a time.
Still, cryogenic proofing is just one of several important tests Booster 7 needs to complete. Even if the first test was nearly perfect and SpaceX doesn’t attempt one or several more cryoproofs with higher tank pressures or other tweaked variables, Super Heavy B7 needs to complete wet dress rehearsal testing (WDR) with flammable LCH4/LOx propellant and demonstrate autogenous pressurization (using heated propellant gas to pressure its tanks). At some point, SpaceX will also need to install a full 33 Raptor V2 engines on the booster and seal off the whole engine section and each Raptor with a heat shield.
Depending on how many Raptor V2 engines are available, SpaceX could begin static fire testing with just a few engines installed and shielded and then install the rest of the engines and heat shield later on. On the other hand, performing static fires without a full heat shield could risk damaging unprotected cabling or other subsystems, in which case wet dress rehearsal testing would likely follow immediately after cryoproofing and before engine or shield installation. After being skipped over, the structural test stand may also factor into Booster 7 qualification sometime before engine installation.
All told, plenty of uncertainty remains, but Super Heavy B7’s auspicious start suggests that the Booster 4 experience is far from a template and that SpaceX is much less interested in wasting time this time around.
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
