News
SpaceX sets dates for Starship static fire, high-altitude launch debut
CEO Elon Musk says that SpaceX is set to attempt one final Raptor engine static fire test before putting Starship through its high-altitude launch debut later this week.
Liable to begin as soon as November 30th per public road closure notices, Musk says that Starship serial number 8’s (SN8) launch debut – both Starship’s first fully-assembled flight test and first high-altitude launch attempt – is now scheduled no earlier than (NET) 8 am to 5 pm CST (UTC-6) on Wednesday, December 2nd.
November 30th will instead host what is believed to be a unique kind of static fire test for Starship SN8, hopefully proving that the rocket has a decent shot at surviving its risky launch debut.
As previously discussed on Teslarati, SpaceX’s Starship development strategy means that SN8’s survival is far less important than it may seem.
“On November 25th, Starship SN9 (featuring “small improvements”) was stacked to its full 50-meter (~165 ft) height. If SN8 is destroyed during testing, SN9 will likely be ready to roll to the launch site almost as soon as the dust settles.
Meanwhile, Starship SN10 is likely just 7-10 days away from a similar nosecone stacking milestone, and Starship SN11’s tank section is just one stack away from completion, likely putting it less than two weeks behind SN10. In other words, insofar as speed is a priority and each prototype is anywhere close to as cheap as Starship’s majority-steel bill of materials might suggest, SpaceX is building Starships so quickly that it almost doesn’t make sense to spend more than a few weeks working through bugs on any single suborbital ship.”
Teslarati.com — November 25th, 2020
In fact, delaying SN8’s launch to try to refine the rocket in situ and better ensure success could actually be to the detriment of successive prototypes and the Starship program in general. If, for example, a fundamental design flaw is revealed in Starship SN8 only after the prototype’s first test flight, SpaceX could be forced to scrap a huge amount of work done on as many as six, seven, eight, or even more subsequent prototypes. In that since, while it may seem like caution maximizes the value any single Starship prototype can provide SpaceX, that’s only true as long as the Starship design is mature enough that new fundamental flaws are unlikely to arise.
Given how young SpaceX’s agile Starship development program is, it would make very little sense to hinge months of work and more than half a dozen rocket prototypes on the quality and success of a less mature prototype unless all the vehicles in question are more or less identical final products. SN8 through SN15+ are certainly not final products in the sense that Starship is meant to be the largest reusable orbital spacecraft ever built.
As such, the Starship program is probably better off if SpaceX pushes vehicles to failure as quickly as reasonably possible. Having now spent more than two months at the launch pad while no less than three full-scale prototypes rapidly approach a similar level of completion, Starship SN8’s test flow is likely an overcorrection from a haphazardly rushed schedule to extreme caution.
Along those lines, SpaceX is now hopefully set on launching Starship SN8 within the near future. First, though, the company apparently plans to attempt another Raptor engine static fire test on Monday, November 30th. Scheduled between 7 am and 9 pm CST, the test has been described as a “handoff” static fire, referring to the process of switching each Raptor engine’s propellant feed from Starship’s main tank to much smaller ‘header’ tanks reserved for landings.
What exactly that handoff refers to is unclear. It could mean that SN8 will switch from main tanks to header tanks during a Raptor static fire test, though it’s unclear why that capability would be necessary unless Starship’s current header tank design is too small. “Handoff” could also refer to the process of switching between main and header tanks between Raptor operations – far more likely. In other words, Starship SN8’s Monday testing might involve two back-to-back static fires, performed with no human intervention. If successful, such a handoff static fire would simultaneously test Starship’s ability switch propellant sources and perform multiple Raptor engine ignitions – both necessary for a launch and landing.
Musk himself believes that Starship SN8 has a ~33% chance of successfully launching, reaching apogee, stably ‘skydiving’ ~14 km (~9 mi) back to Earth, reigniting Raptor engines, and landing in one piece. It’s unclear what will happen in the seemingly unlikely event that SN8 survives, but Starship SN9 is practically nipping at the relatively ancient prototype’s heels.
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
