News
SpaceX Starship briefly becomes largest rocket in history – now what’s next?
On August 6th, after a great deal of anticipation, SpaceX stacked a Starship on top of a Super Heavy booster for the first time ever, very briefly assembling the largest rocket in history.
However, barely an hour after the two stages were integrated and (presumably) latched together, SpaceX lifted Starship (S20) off the booster, returned it to its transport stand, and rolled the ship back to the build site later that day. Though an extreme sensitivity to wind conditions has delayed the procedure, Super Heavy Booster 4 (B4) also appears to be on track to be removed from the orbital launch mount and sent either back to the factory or to a suborbital launch mount that’s been modified for booster testing.
For those that followed the process closely in the days and weeks prior, the fact that Starship’s first full assembly was just a fit check (and, really, more like 50:50 between fit check and photo op) came as no surprise. In the lead-up, it became clear through several reports that CEO Elon Musk had challenged SpaceX to stack Ship 20 and Booster 4 by August 5th and flown in several hundred employees normally stationed elsewhere to accomplish the feat.
Ignoring weather delays that prevented stacking on August 5th, SpaceX met Musk’s challenge in all but the literal sense, assembling the world’s largest rocket into one integrated stack for the first time ever. Even more significantly, despite the fact that SpaceX could have easily decided to stack two not-for-flight prototypes to sort of achieve the same feat, both stages – Ship 20 and Booster 4 – involved in the August 6th milestone are nominally destined for flight.
Barring surprises, the same exact pair is scheduled to support Starship’s first orbital test flight as early as this year. Before they can be cleared for flight, however, a great deal of work must still be completed – work that in some cases is unprecedented in the history of the Starship program.
Not long after the stacking milestone, Musk himself sketched out a few of the tasks still in front of the rocket. Namely, Musk says that SpaceX must still complete Starship S20’s partially-finished heat shield, install some form of heat shield(s) to protect Super Heavy Booster 4’s 29 naked Raptor engines; finish installing, plumbing, and activating 4-7 massive custom propellant storage tanks; and assemble, install, and activate a giant mechanical umbilical arm on the launch tower to fuel and power Starship.
All are undoubtedly crucial and Starship is unlikely to launch before any of them are more or less complete. However, the booster and ship themselves are arguably far more of a pressure point. Before they can be deemed ready for flight, both the ship and booster must complete unprecedented test campaigns on the ground.
Ship 20 will need to complete cryogenic proof testing to verify that the first Starship with six Raptor engine mounts is structurally sound. SpaceX has already modified one of its two suborbital Starship launch mounts for that purpose. Once cryo proof and hydraulic ram testing is complete, those six rams will likely be removed and six Raptor engines will be installed in their place, potentially setting up Ship 20 to become the first Starship prototype to static fire six engines – and any number of Raptor Vacuum engines.
Super Heavy Booster 4 will be faced with an even more ambitious static fire test campaign as SpaceX likely gradually installs more and more engines. Depending on how focused SpaceX is on speed over thoroughness, that process could involve gradually adding 2-5 engines after every static fire or could result in SpaceX starting with 4-9 engines and then immediately jumping from 9 to a full 29-Raptor static fire.
Only after completing those crucial qualification tests is SpaceX likely to stack Ship 20 and Booster 4 for a second time and enter the first true full-stack Starship launch flow – hopefully culminating in the first orbital launch attempt later this year, but only as soon as the FAA completes an environmental review and approves the rocket’s launch license. Technically, FAA approval could come next month or it could take the agency a year or more – it’s almost impossible to predict without official information. However, given SpaceX’s track record with Starship prototypes and Booster B3, it’s likely that a flightworthy Starship and Super Heavy will be stacked on the pad and ready to launch just a few months from now.
Stay tuned for updates on that potential standoff in the making and Starship’s progress towards its first orbital test flight.
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
