News
SpaceX Starship test plans solidify after bad weather delays hop
Around the same time SpaceX was preparing for its 100th Falcon rocket launch, bad Texas weather forced the company to abort its second Starship hop test of the month.
Since that abort, SpaceX’s near-term Starship test plans have begun to solidify, offering a clearer picture of what to expect over the next week or two. Pending better weather at its Boca Chica, Texas test facilities, Starship serial number 6 (SN6) is still first in line and has been preparing for its hop debut ever since the prototype completed a Raptor engine static fire test on August 23rd.
Measuring approximately 30m (~100 ft) tall, SN6 is a full-scale Starship tank and engine section – the bottom ~60% and business end of the reusable orbital spacecraft. Of course, SpaceX has a ways to go before Starship is actually ready for its first orbital test flight, let alone reuse after such a test flight, but the company did take its biggest step yet towards that lofty ambitions with Starship SN5’s successful August 4th hop debut.
Effectively twins, Starship SN5 and SN6 have since been expected to take turns completing “several” hops to improve SpaceX’s familiarity with Starship launch operations and work towards a smooth procedure that can be completed multiple times per day. With SN6 now scheduled to hop no earlier than 8am CDT (UTC-5), September 3rd, 29 days after SN5’s debut, SpaceX still has its work cut out for it.
Nevertheless, SN5’s 150m (~500 ft) hop was the first flight of any kind for a full-scale Starship prototype, as well as the first use of an entirely new landing leg design and Raptor’s first flight in almost a year. In the history of rocket development, there is no precedent for launching and landing a prototype rocket and then repeating the same test with an entirely new prototype less than a month later.
Additionally, most of the 29 days since SN5’s first hop have been spent preparing Starship SN6 for a crucial “cryo proof” qualification test. Had that cryo proof been completed before SN5’s hop debut, SN6 could have been ready to fly as few as ~10 days later. That still leaves SpaceX a long ways away from multiple Starship hops per day but does offer encouragement that flight-proven Starship SN5 could be ready for its second hop not long after the pad is clear.
However, it appears that SpaceX instead plans to follow up SN6’s hop debut with a new ‘test tank’ meant to demonstrate an upgraded Starship “thrust puck” built out of a different steel alloy. Known as Starship SN7.1, the test will follow on the heels of a more traditional tank (SN7) that completed a record-breaking pressure test in June 2020 and proved that Starship would likely be better off with a different steel alloy.
While SN7 was a basic test tank (two domes and a few steel rings), SN7.1 adds a skirt section at its base and replaces the aft dome with a thrust dome. Likely built entirely out of a steel alloy closer to 304L than the 301 SpaceX has used for all prior Starship prototypes, that thrust dome features a new ‘thrust puck’ – the structural element Raptor engines attach to and transmit their thrust through.
Unlike past single tank tests, SN7.1 will be put through something more like a full prototype’s cryo pressure test. SN7.1 will be installed on a launch mount, allowing its skirt clamps to firmly secure the prototype to the stand, itself secured to a concrete slab on the ground. That launch mount also allows SpaceX to install a hydraulic ram designed to mechanically simulate the thrust of 1-3 Raptor engines without the risk involved in an actual static fire. SN7.1 is scheduled to begin testing no earlier than (NET) 8 am CDT (UTC-5), September 6th – just three days after SN6’s next planned hop attempt.
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
