News
SpaceX ‘go’ for 50,000-foot Starship launch debut after static fire, Elon Musk says
CEO Elon Musk says that SpaceX’s first fully-assembled Starship prototype is on track for its 15-kilometer (~50,000 ft) launch debut after completing a second three-engine static fire test on Tuesday.
Starship serial number 8’s (SN8) three Raptor engines ignited for a few seconds around 5:30 pm CST (UTC-6) on Tuesday, November 24th, less than four hours before a record-breaking Falcon 9 rocket launched another batch of Starlink satellites roughly a thousand miles to the east. Perhaps briefly producing upwards of 600 metric tons (6000 kN/~1.3M lbf) of thrust, Starship SN8’s second triple-engine static fire was actually the first with that particular trio of engines.
Back on November 13th, an otherwise successful one or two-engine static fire nearly ended in catastrophe when the hypersonic Raptor exhaust kicked up blade-like debris that severed crucial control cables and triggered an apparent engine meltdown. Thanks to a “burst disk” failsafe, Starship SN8 – unable to actuate valves needed to depressurize – was saved from what could have been catastrophic damage. Believed to be SN32, the damaged Raptor was subsequently removed on November 14th and replaced with SN42 on November 16th.
As such, SN8’s November 24th static fire was the first with that particular set of three engines, although it was technically the rocket’s second three-engine test. SN42 now (hopefully) proven to be flight-ready, it remains to be seen if SpaceX will attempt more static fires before Musk’s promised 15 km launch debut.
As of November 25th, SpaceX still has a static fire backup window open open from 8 am to 5 pm CST, while Starship SN8’s launch road closures remain in effect from 7 am to 6 pm on November 30th with backups from 8 am to 5 pm on December 1st and 2nd.
Having now spent more than a month at the launch pad, it’s increasingly unlikely that SpaceX will continue to choose caution first for upcoming Starship SN8 tests. As Musk recently noted and easily visible from public roads, SpaceX’s Boca Chica factory is developing an extraordinary backlog of giant steel rockets. Just today, November 25th, Starship SN9 (featuring “small improvements”) was stacked to its full 50-meter (~165 ft) height after SpaceX kicked off nose section installation. In simpler terms, if SN8 is destroyed during testing, Starship SN9 will likely be ready to roll to the launch site almost as soon as the pad is clear.
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 the rockets so quickly that it almost doesn’t make sense to spend more than a few weeks working through any given ship’s bugs for as long as prototypes remain firmly suborbital.
Musk also says that Starship SN15 will be the host of some mysterious “major upgrades”, likely implying some substantial manufacturing improvements and design refinements. Given that large portions of Starship SN15 (and likely SN16, too) are already visibly in work in Boca Chica, it makes even less sense to spend outsized amounts of time on a much earlier prototype.
It doesn’t come as a huge surprise, then, that Musk has given SN8 – warts and all – a 33% chance of successfully launching, ‘skydiving’ back to Earth, reigniting one or more Raptors, and landing in one piece. The only real certainty is that regardless of the outcome, Starship’s high-altitude launch debut is guaranteed to be spectacular. Stay tuned for updates as we get closer to SpaceX’s November 30th target.
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
