News
SpaceX set to finish three Starship prototypes in the same month
SpaceX appears to be on track to complete its third Starship prototype in a month just days after the company finished testing a new steel tank and at the same time as it prepares to roll another full-scale ship to the launch pad.
Postponed by several weeks after the (fleeting) success of the Starship serial number 4 (SN4) prototype, violently destroyed by a minor testing mishap on May 29th, SpaceX’s fifth full-scale Starship tank section (SN5) could roll to an adjacent testing facility at any point in the next few days. In fact, SN4’s successor has likely been ready to begin tank proof and static fire testing for several weeks since it was stacked to its full height on May 12th. SN4 rolled to the launch pad on April 23rd and remained SpaceX’s top Starship priority until its demise more than a month later.
As it turns out, the explosion that destroyed the ship also launched a ~25 metric ton (~55,000 lb) counterweight installed a few days prior some 100m (300+ ft) into the air, where it proceeded to fall back to earth and obliterate the steel mount Starship SN4 sat on. The loss of that pad hardware necessitated its own several-week delay but SpaceX appears to be nearly done installing and outfitting replacements as of June 18th – an incredible turnaround given the scale and complexity of everything involved. Of course, the whole purpose of those rapid repairs is to get back to the business of testing Starships as quickly as possible.
SN5
Initially expected as early as 8am local on June 17th, Starship SN5’s trip to the launch pad has been a long time coming. Completed around May 20th after approximately a month of concerted effort, the ~30m (100 ft) tall tank departed SpaceX’s Vehicle Assembly Building (VAB) for the first on June 13th, although it was quickly moved back inside as technicians simultaneously worked to complete Starship SN6.
Previously scheduled to become the first Starship to reach its full height with the installation of a functional nosecone, SN5 will likely pick up where SN4 left off, instead. That process will effectively be no different, albeit sans nosecone, starting with ambient and cryogenic proof (pressure) tests and eventually moving to one or several static fires with either one or three Raptor engines. Testing the quick disconnect umbilical port that caused SN4’s demise will also likely be a priority. If all goes according to plan in that first week or two of tests, SpaceX may finally be ready to launch a full-scale Starship prototype for the first time, performing a 150m (~500 ft) hop test with SN5.
However, since CEO Elon Musk first discussed plans for an initial 150m hop test, SpaceX received a surprise suborbital launch license from the FAA, rather than the limited experimental permit most expected. That license effectively allows SpaceX to perform an unlimited number of Starship tests as long as the trajectory follows the administration’s strict safety guidelines and remains suborbital. Unless SpaceX’s ~150m target was based in some technical limitation, the sky is quite literally the limit for a more ambitious flight debut if the company believes Starship SN5 can handle it.
SN6
In the event that Starship SN5 follows its predecessor into a less early (but still early) grave, SpaceX thankfully won’t have to wait long at all to continue its hardware-rich test program. When Starship SN5 first departed the VAB on June 13th, it did so to give SpaceX room to finish Starship SN6, placing its aft engine section on a stand inside the building and stacking the upper two-thirds of the ship’s tank on top.
Several days to a week or more of internal and external work remain to fully mate the two Starship SN6 sections, but the vast majority of its assembly is now behind SpaceX. SpaceX continues to refine its methods with each successive prototype, gradually producing Starships that are getting closer and closer to the ideal finished product. There’s a chance that, unlike Starship SN4, SN5 can be modified with the installation of a nosecone and flaps to support more ambitious 2-20 km (~1.2-12 mi) flight tests if it makes it over the 150m hurdle unscathed but if not, SN6 could become the first Starship to have a nosecone installed.
SN7
Last but absolutely not least, SpaceX recently built a new Starship test tank for the first time since March. While stouter than an actual Starship-class methane or oxygen tank, this particular test tank is maybe only 25% shorter than the methane tanks installed on Starship prototypes. According to Musk and effectively confirmed by writing all over the prototype, this particular test tank – formerly Starship SN7 – was built to determine if a different kind of steel could be preferable for future ships.
Shortly after the June 15th test began to wind down, Musk announced that the new material (304L stainless steel) had performed quite well, reaching 7.6 bar (110 psi) before it sprung a leak. The fact alone that it sprung a leak instead of violently depressurizing is already a major sign that 304L is preferable to 301L, as it means that Starships built out of it could fail much more gracefully in the event of a leak instead of collapsing or violently exploding. A step further, SpaceX has already managed to repair the leak on SN7 and will likely test the tank again in the next few days.
Meanwhile, Musk says that a second improved 304L test tank is already on its way, after which SpaceX will likely attempt to build and test the first fully-304L Starship prototype. Further down the line, SpaceX intends to develop its own custom steel alloy, optimized specifically for Starship’s needs. The first tests of that ’30X’ alloy could begin as early as August 2020 according to a February Musk tweet.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
