News
SpaceX preparing Super Heavy, Starbase for booster’s next steps
Amid a flurry of deliveries and work on several new Starship boosters, SpaceX is preparing the first truly finished Super Heavy for its next steps.
Partially completed by early September, Super Heavy Booster 4 (B4) supported SpaceX’s iconic ‘full stack’ fit test back on August 6th before returning to the build site but has mostly just floated around Starbase’s launch and test facilities in the seven weeks since its second trip to the pad. On September 10th, CEO Elon Musk himself suggested that SpaceX had plans to static fire the booster as early as mid-September – more than six weeks ago. Obviously, nothing even approximating Super Heavy testing transpired. Instead, at least relative to rapid-fire Starbase operations in the two years prior, SpaceX has almost absentmindedly worked on the booster, mostly completing partially-finished wire runs that run its full 69m (~225 ft) length.
In the last few weeks, though, the type of work being done on Super Heavy B4 has changed.



On September 26th, to give the Starbase construction crew more room to install giant arms on the orbital pad’s ‘launch tower,’ SpaceX removed Super Heavy B4 from the launch mount for the second time, temporarily relocating it to an unused patch of the pad’s old landing zone. Booster 4 hasn’t been moved since. However, while probably a bit slower than SpaceX would have liked, large-scale work on the Starship launch tower was effectively completed last week with the installation of two giant rocket-catching ‘Mechazilla’ arms.
A great deal of work has also been done on Starbase’s orbital tank farm over the last two months, including the installation of the last few storage tanks, the ‘sleeving’ of those tanks, a great deal of plumbing, and the start of real propellant deliveries. Save for a few days spent testing Starship S20 in late September and mid-October, the pad construction crews that have to evacuate the pad for 6-12 hours for every test have had three full months to work without interruption. Perhaps the most optimistic explanation for the unusually long gap between Booster 4 and Ship 20 rollout and testing is that SpaceX consciously chose to put off vehicle tests to avoid disrupting orbital launch site construction and retasked nearly all Starbase workers for that construction.
Regardless, with the launch tower and orbital tank farm now more or less structurally complete and work already underway to prepare the tank farm to support its first booster tests, most of the work that may have been drawing focus and resources away from ship and booster preparations appears to be wrapping up. That may be why, for the third time, SpaceX technicians began removing a number of Raptor engines from Super Heavy B4 around the start of October.
Aside from removing around a third to half of Super Heavy’s 29 Raptors, SpaceX also began slowly but surely installing parts of a steel heatshield designed to protect those engines during ground testing, ascent, and reentry. Newer Raptors have also been trickling from Starbase’s build site to the launch pad for installation on the booster and more engines will likely be (re)installed as heatshield installation progresses.

Perhaps the most unusual part of recent Super Heavy B4 work is the apparent application of some kind of foam around several racks of pressure vessels (COPVs), hydraulic manifolds, and umbilical connections installed around the booster’s base. Those racks will eventually be enclosed inside steel ‘aerocovers’ already staged beside Super Heavy. A number of Twitter users believe that the foam being selectively applied is for acoustic deadening – meant to protect sensitive electronics, valves, and computers from the brutal environment Super Heavy itself will produce at liftoff and during ground testing.
Ultimately, with Booster 4 work ramping back up and the zenith of orbital pad construction activity now likely behind SpaceX, preparations for major Super Heavy testing will hopefully resume. SpaceX has yet to perform a full Super Heavy wet dress rehearsal (WDR; fully filling a rocket’s tanks and performing a launch countdown) or fire up more than three Raptors on a booster or ship prototype. With any luck, that will finally change in the final months of 2021.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.