News
SpaceX making good progress towards Super Heavy static fire campaign
SpaceX appears to be making great progress towards the start of its first full Super Heavy static fire campaign, building upon extensive Starship testing and a single booster static fire completed in July 2021.
On May 14th, upgraded Super Heavy booster B7 was moved back to SpaceX’s South Texas Starbase Starship factory after completing a successful round of tests and smoothing out an otherwise rocky start to its life. It was not the booster’s first time on that journey: after first leaving the Starbase ‘nest’ on March 31st, Booster 7 suffered significant internal damage during a structural stress test on April 14th and was forced to return to the factory for repairs. Impressively, despite the cramped environment and extremely limited access to the interior of the Super Heavy’s primary and secondary propellant tanks, SpaceX engineers and technicians somehow completed those repairs and Booster 7 sailed through a new round of ‘cryoproof’ testing on May 9th and 11th.
In the ~20 days since its second return, SpaceX teams have been hard at work preparing Super Heavy B7 for its next major challenges – the results of which could determine whether the massive rocket helps launch a Starship into space later this year.
That goal, same as it has been for half a year, is to qualify the first Super Heavy booster for flight. To do so, SpaceX must – at long last – static fire a Super Heavy with all necessary Raptor engines installed. For Booster 7 and its near-term successors, that means 33 new “Raptor 2” engines capable of generating a total of ~7600 metric tons (~16.7M lbf) of thrust.
That’s exactly what SpaceX workers have been focused on doing since Booster 7’s second return to a Starbase assembly bay. Bit by bit, they have spent every day since installing Raptor 2 engines one at a time. Unfortunately, due to the Super Heavy’s relocation inside a brand new assembly building known as the Megabay, High Bay 2, or Wide Bay, the half-dozen or so unaffiliated photographers who have come to regularly photograph Starbase have yet to find an angle that shows the state of that engine installation progress.
Two weeks later, it’s clear that SpaceX is taking its time, which likely also implies that the company is simultaneously encasing Booster 7’s Raptors and engine section in shrouds that will protect them during static fire testing; as well as during launch, reentry, and landing if B7 makes it that far. That’s not guaranteed, however, and it could also simply be that installing 33 engines on the first attempt at installing any Raptor 2s on any rocket has proven much harder than expected.
On June 1st, CEO Elon Musk appeared to confirm that engines are still being installed on Super Heavy B7, but he also verified that “all Raptor 2 engines needed for [the] first orbital flight are complete.” That could include Starship S24, which needs three sea-level Raptor 2s and three vacuum-optimized Raptor 2s, but it’s still great news even if he only means it for Booster 7. SpaceX has been spotted delivering at least a handful of new Raptor 2 engines a week for the last month or two, which means that all 33 engines may already be onsite at Starbase. If some are still undergoing proof testing at SpaceX’s McGregor, Texas facilities, it could be a few more weeks before all necessary engines are onsite, but that milestone is likely close at hand if it hasn’t already been reached.
For Super Heavy Booster 4, which was inexplicably never static-fired, installation of all 29 of its Raptor 1 engines took just a few days, but the installation of a heat shield around those engines took at least a few weeks. On June 1st, SpaceX also began installing grid fins on Super Heavy B7, further indicating the company’s growing confidence in the booster.
Outside of booster outfitting, SpaceX has also been aggressively refilling the Starbase orbital launch site’s (OLS) massive tank farm, which is capable of storing, subcooling, and distributing thousands of tons of liquid oxygen (LOx), liquid methane (LCH4), liquid nitrogen (LN2), and a variety of gases. For a full wet dress rehearsal (WDR), which has also never been done with Super Heavy, SpaceX would need to fill the booster with around 3400 tons (7.5M lb) of propellant. Out of an abundance of caution, Super Heavy B7 will likely have far less propellant aboard during almost all of its static fire tests, but a full static fire with a full load of propellant – simulating most prelaunch conditions – will likely be one of the last main goals of any static fire campaign. At full thrust, 33 Raptor 2 engines will likely burn around 25 tons (~55,000 lb) of propellant per second, so a huge amount of propellant will be needed regardless.
In the same series of June 1st tweets, Musk also confirmed that SpaceX intends to proceed cautiously into its first true Super Heavy static fire campaign, testing engines “just one at a time at first.” Musk probably isn’t being literal, as a campaign in which Booster 7 tested every one of its 33 Raptors individually could easily take weeks, so it’s likely safe to interpret his words to mean that SpaceX is not going to leap straight from the first limited test of one or a few engines to all 13 center engines, all 20 outer ‘boost’ engines, or all 33 engines at once.
Almost three weeks into the process of engine and heat shield installation, Booster 7 could potentially be ready to return to the orbital launch site any day now, though there’s probably an equal chance that it’s still a few weeks away. Nonetheless, SpaceX is on the cusp of kicking off one of the most exciting and important test campaigns in the history of Starship.
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
