News
SpaceX finishes stacking new Starship for the first time in six months
For the first time in more than half a year, SpaceX has stacked a new Starship prototype to its full height, hopefully marking the end of a period of relatively slow progress.
That period began when Starship S20 was stacked to its full height in early August 2021. Until very recently, Ship 20 was said and expected to be the prototype assigned to Starship’s first orbital test flight, making it exceptionally important. In an unusual change in attitude, SpaceX may have felt the same, which may explain why Starship S20’s first static fire test took place more than two months after it first left the factory. A year prior, Starships SN9, SN10, SN11, and SN15 all completed proof testing a matter of weeks after rollout.
That sudden change of pace relative to past development has meant that Ship 20 is the only Starship prototype SpaceX has tested since May 2021 and the only Starship to graduate from final assembly to testing in the last six months. In that period, Ship 20 has completed a few major cryogenic proof tests and four static fires – two of which ignited all six Raptor engines. While Ship 20’s six-engine tests were unprecedented and marked a major program milestone, SpaceX once static-fired Starship SN9 three times in one day in January 2021.
However, that period of sluggish prototype testing may finally be coming to an end. In August 2021, when SpaceX stacked Starship S20 and Super Heavy B4 for the first time, the general assumption was that the seemingly imminent march towards orbital flight testing would be similar to SpaceX’s attempts to land a Starship from medium altitude between December 2020 and May 2021 – lots of prototypes in flow and multiple back-to-back tests and launches, in other words. That was not the case.
Starship S21, for example, began final assembly in mid-October 2021 and its tank section and nose section were both fully stacked less than a month later. However, rather than stack them into a second complete ship, SpaceX has left those separate assemblies sitting around Starbase for the last three months. Simultaneously, while Ship 21’s apparent limbo seemed to imply that SpaceX was implementing another block upgrade and moving on to newer prototypes, the company actually started stacking Starship S22 about a week after S21’s separate sections were completed. Only three months later have SpaceX’s plans for those three sections finally become clear.
On February 14th, 2022, Ship 22’s tank section followed Ship 21’s nose section into Starbase’s high bay assembly facility, where they were quickly stacked to form a full Starship prototype the same day. This raises the question: why?



Given that Starship S20 effectively completed qualification testing with three successful static fires in December 2021 and a fourth in early January 2022 and has been seemingly ready to fly ever since, its Super Heavy booster readiness – not ship readiness – that appears to be holding SpaceX back. Perhaps because of pad readiness issues, SpaceX has yet to perform a single Super Heavy static fire test – or even a less risky wet dress rehearsal – at the orbital launch site. As such, it’s hard to say why SpaceX has suddenly decided to finish Ship 22 instead of focusing on a newer version of Starship (S24) and Super Heavy (B7) – both of which are expected to debut upgrades.
It’s possible that Ship 22 is being completed merely as practice for the Starbase workforce, who have gone half a year without fully assembling another ship prototype, but then there would have been no reason not to install Ship 21’s nose on Ship 21’s tank section instead of withholding it for Ship 22. Ship 22 could also be a replacement for Ship 21 if appearances are misleading and SpaceX uncovered issues with the older prototype during testing but again, no booster is ready to launch either ship.
Regardless of the outcome or purpose of Ship 22, seeing any new Starship prototype completed is an exciting and interesting change of pace after half a year of following the windy paths of Ship 20, Booster 5, and Ship 21 to their uncertain goals.
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.