News
SpaceX schedules Starship’s first triple-Raptor static fire test
A photo posted by CEO Elon Musk confirms that SpaceX has successfully installed three functional Raptors on Starship SN8 just hours before road closure notices revealed the company’s first triple-engine static fire schedule.
Technically, it’s incorrect to say that Starship serial number 8 (SN8) is the first prototype to receive three Raptor engines. Back in late-September 2019, in the lead-up to Musk’s promised Starship update event, the company installed three Raptors on the first full-scale prototype, known as Starship Mk1. The engines were only installed as an apparent fit test or even a photo opportunity, however – evidenced by the fact that they weren’t actually plumbed to the Starship’s propellant tanks.
Even then, in September 2019, Starship Mk1 was far from ready to make use of Raptor engines and was more than a month away from attempting its first pressure and cryogenic proof tests – tests it quickly failed. As such, Starship SN8 – having more or less successfully passed its ‘cryo proof’ by October 9th – is undoubtedly the first ship to have a shot at igniting multiple Raptor engines at once.

Curiously, SpaceX remained quiet for several days after Starship SN8 passed its first big test. Whereas with past Starship prototypes SpaceX has often filed test plans (appearing in the form of road closures) even before the current phase of testing is complete, the company waited until Tuesday, October 14th to file closure notices for “SN8 static fire” testing.
Same as Starships SN4, SN5, and SN6, all of which successfully graduated from cryo proof to static fire testing (and even flight tests for the latter two), SpaceX began Starship SN8’s test campaign with a cryo proof. It took three days and at least as many attempts but SN8 ultimately “passed cryo proof” according to Elon Musk, likely meaning that the ship reached sustained pressures of 7.5 bar (~110 psi) or more.

Cryo proof complete, SpaceX installed Starship SN8’s engines – the first time multiple Raptors have been fully integrated with a rocket or test stand – in preparation for another Raptor first: multi-engine static fires. While modern computation fluid dynamics (CFD) and modeling mean that the great unknowns of rocket propulsion are rarely as opaque as they used to be, the first test of multiple powerful engines in close proximity is still a guaranteed recipe for surprises.
Thanks to expertise hard-won from nearly 100 Falcon 9 and Falcon Heavy launches, SpaceX is likely the world’s foremost expert in the challenges and dynamics of the proximity operation of more than two rocket engines. At the same time, though, Raptor is a dramatically different engine than Merlin 1D and while Starship will only have six engines at most, those six engines will produce thrust equivalent to almost two entire Falcon 9 boosters.

In other words, even with a (relatively) simple three-Raptor static fire, SpaceX will be treading new ground and will almost certainly end up learning one or several things about Raptor’s design and operation. More likely than not, SpaceX will begin Starship SN8’s static fire test campaign with a wet dress rehearsal (like a cryo proof but with real liquid methane and oxygen propellant) and transition into a Raptor spin prime (turbopump spin-up) or preburner test (a turbopump spin-up but with partial combustion) if the WDR goes smoothly. If all three Raptor engines appear healthy, SpaceX may recycle and attempt the first static fire just an hour or two later.
Starship SN8’s triple-Raptor static fire test window opened at 9pm CDT on October 14th and closes at 6am on the 15th, with an identical 9pm-6am backup on the 15th and another window from 8am to 4:30pm on the 16th. LabPadre (below) will continue to offer 24/7 views of Starship, including any static fire testing, while NASASpaceflight.com will likely provide live coverage once testing begins in earnest.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.