News
SpaceX’s first high-flying, triple-Raptor Starship is almost finished
SpaceX’s first high-flying, triple-engine Starship prototype is rapidly approaching completion at the same time as the company is preparing for the rocket’s predecessor to lift off on its inaugural test flight.
Known as serial number 5 (SN5), it will be the fifth full-scale Starship prototype completed by SpaceX since November 2019 and the fourth since late-January 2020. Following in the footsteps of Mk1, SN1, SN3, and SN4, SpaceX CEO Elon Musk has recently stated that Starship SN5 will be the first prototype to have three Raptor engines and a nosecone installed and could be the first to be outfitted with new and improved aerodynamic control surfaces.
In the meantime, Starship SN4 is perhaps less than 30 hours away from performing a third Raptor static fire test, potentially paving the way for the biggest challenge yet for a full-scale Starship prototype: powered flight. Scheduled no earlier than 9am CDT (14:00 UTC), May 13th, Starship SN4’s next static fire is meant to ensure that a replacement Raptor engine is functioning properly. If successful, the building-sized rocket will effectively be ready to attempt its first launch – also a first for the Starship program overall – pending FAA approval.
As illustrated in the unofficial diagram above, nearly all of the individual sections that will make up Starship SN5 appear to be more or less complete, excluding some ambiguity added by the interchangeable nature of some of the steel rings all Starships are built out of. For the current design and assembly strategy, Starships are comprised of eight separate sections, themselves made up of stacks of 2-4 steel rings. Altogether, excluding the conical nose section, a single Starship requires approximately 20 of those ~1.8m (6 ft) tall steel rings to reach its full height.
Currently, SpaceX has been focused on testing just the tank section of Starship prototypes, representing the vast majority of the technical challenges that must be solved to fully realize the next-generation launch vehicle’s ambitions. Excluding a smaller secondary liquid oxygen tank situated in the tip of Starship nosecones, the nose section is effectively irrelevant – putting the cart before the horse – until Starship tank sections are more of a known quantity.
When that would be the case was entirely up in the air until just the last week or so, when Starship SN4 became the first full-scale prototype to pass a cryogenic proof test, perform a wet dress rehearsal (WDR) with real propellant, complete static fire(s) with a Raptor engine installed, and – finally – pass a more challenging cryogenic pressure test in quick succession. With those milestones passed for the first time ever, SpaceX has effectively proven that it’s solved the what is arguably the most unprecedented aspect of its Starship program: building orbital-class pressure vessels for pennies on the dollar on the South Texas coast.
Of course, doing it once with Starship SN4 is not the same as fully confirming that SpaceX’s extremely exotic South Texas rocket factory is capable of producing repeatable results with future rockets. While incredibly improbable, Starship SN4’s multiple successes could be a fluke. Additionally, as Musk has noted, the goal is to complete two entire Starships every week once the factory is fully optimized. SpaceX has already achieved a monthly production rate for its current line of prototypes, an extremely encouraging sign for the practicality of Musk’s stretch goal.
In the prototype stage, that speed of production has been incredibly useful, enabling SpaceX to move at a pace of launch vehicle development almost unheard of since NASA’s Apollo Program. At the moment, Starship SN4 has passed all tests thrown at it so far and will soon be attempting the riskiest Starship test yet with its inaugural hop attempt. If the ship were to be destroyed, one would traditionally expect a bare minimum of a few months of program delay. Instead, Starship SN5 could be more or less complete even before SN4 receives FAA permission for its first flight, meaning that a replacement will already be ready to roll to the launch pad if or when SN4 is destroyed.
In a best-case scenario, if Starship SN4 continues to pass the tests thrown at it, including one or several hops, SpaceX will instead be entering a new phase indicative of what’s to come: the concurrent testing and operation of a fleet of Starships. A step further, if Starship SN4 succeeds, Starship SN5 appears to be on track to become the first prototype to have a full three Raptor engines and a nosecone installed, as well as the first to attempt a high-altitude (20 km/12 mi) flight test.
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
