News
SpaceX is about to have a fleet of Starship rockets
SpaceX has finished the last major stacking event for the business half of its fifth full-scale Starship prototype, meaning that the company may be a week or less from having a fleet of Starships for the first time ever.
As of now, Starship serial number 5 (SN5) is on track to be completed in under a month, continuing a trend that SpaceX has managed over the entirety of 2020. Beginning in mid-January, SpaceX has completed several nosecone pathfinders, three test tanks, and three full-scale Starship prototypes – soon to be four once SN5 is finished. Once it is, however, SpaceX will be entering a new era of operations – fleet operations.
Up to this point, every full-scale Starship prototype and test tank SpaceX has built – excluding the tank SN2 was turned into in March – has been quickly destroyed over the course of one or two tests. For better or for worse, this has meant that SpaceX’s test and launch pad has always been more or less self-clearing, making way for the next prototype to roll out and begin testing after the scraps of its predecessor were removed. This time around, barring Starship SN4’s imminent demise, SpaceX will now have to deal with multiple completed Starship prototypes at the same time – a tiny taste of things to come.
For unknown reasons, SpaceX decided to swap out Starship SN4’s lone Raptor engine (likely SN18) after multiple wet dress rehearsals, partial engine tests, and two static fire tests – at least one of which was confirmed a success by CEO Elon Musk. Most recently, SpaceX removed Raptor SN18 to perform a more ambitious cryogenic pressure test, pushing Starship SN4’s propellant tanks all the way to 7.5 bar (~110 psi) at the same time as hydraulic rams simulated the thrust of three Raptor engines at the rocket’s base.
Instead of reinstalling Raptor SN18, SpaceX transported Raptor SN20 to the launch pad and installed it on Starship SN4 on May 10th, less than 24 hours after the prototype passed an orbital-class pressure test.
Aside from installing Raptor SN20, SpaceX teams have spent the last few days adding new COPVs (composite overwrapped pressure vessels) and plumbing to Starship SN4’s exterior – purpose largely unknown. While the new hardware is mostly a mystery, it is known that SpaceX is in the process of preparing SN4 and its new Raptor engine for a third wet dress rehearsal (WDR) and static fire test, necessary to ensure that Raptor SN20 is properly installed and functioning as expected.
Assuming that third static fire is successful, SpaceX’s will prepare Starship SN4 for its first flight, a ~150m (500 ft) hop test that will also be the first intentional flight of any full-scale Starship prototype since the program’s birth. For that hop test, SN4 will need some kind of attitude control system (ACS) thrusters to control its rotation and provide fine trajectory tuning to assist the ship’s lone Raptor engine. This is the likeliest explanation for the new hardware being installed on Starship SN4, as the ship does not currently appear to have ACS thrusters installed.
Starship Troopers
Of course, the first flight of a full-scale Starship prototype will probably be the riskiest test yet for the program and there’s a good chance that SN4 will meet its demise at some point during that flight. Enter Starship SN5.
As of May 12th, Starship SN5’s final two tank sections were stacked, effectively completing the most important half of the rocket (minus one final circumferential ring weld). SN5’s final outfitting of avionics and plumbing is still pending and will take at least a few days to a week or more, but that work can and has been completed after prototypes are transferred by road to the launch pad. Currently, Starship SN4 is occupying SpaceX’s one and only pad test stand, however, meaning that it wouldn’t make much sense to immediately move SN5 to the launch pad – at least until SN4 is done testing.
SN5 will also need a nose section and, perhaps, flaps installed, meaning that the full ship is likely still at least a week or two away from being finished, but that likely wont stop SpaceX from proof testing the rocket’s tanks if or when SN4 makes space at the launch pad.
According to comments made by Elon Musk, SN5 will likely become the first Starship prototype to have three Raptor engines installed and the first to attempt a truly high-altitude flight test if Starship SN4 is met with success in the coming weeks. As absurd as it feels to say, if SN5 completes triple-Raptor testing and a 20 km (~12 mi) flight test without issue, Musk has stated that the next step would be orbital flight tests. Starship SN6’s steel rings, meanwhile, are already being formed and stacked as SN5 nears completion.
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
