News
SpaceX’s first flight-proven Starship could fly again, says Elon Musk
Elon Musk says that SpaceX wants to reuse its first flight-proven Starship prototype, although the rocket’s second hop might come after the debut of a totally different ship.
On August 4th, for the first time ever, a full-scale Starship prototype measuring some 9m (30 ft) wide and 30m (~100 ft) tall lifted off from SpaceX’s Boca Chica, Texas test facilities. Just three weeks shy of the first anniversary of Starhopper’s last flight test, Starship serial number 5 (SN5) essentially repeated the stubby prototype’s 150m (~500 ft) hop before (relatively) gently landing on an adjacent concrete pad.
Over the last several days, SpaceX has gradually been working through the unprecedented task of inspecting, safing, and relocating a flight-proven Starship. At the same time, the company has to check out the fixed launch mount structured that supported the test flight and provided Starship with power, propellant, and wired communications. As teams work to get both ship and mount ready for round two, CEO Elon Musk has taken to Twitter to discuss some of SpaceX’s nearer-term goals and plans for Starship testing – including SN5’s role in them.

Starship SN5’s hop debut was a spectacular success for SpaceX, verifying that steel and radically simple and manufacturing techniques can quickly build a cheap pressure vessel capable of controlled flight. The flight also reaffirmed that the next-generation Raptor engine is capable of operating uninterrupted for at least ~50 seconds, although Starhopper’s 150m hop proved the same thing some 20 engine prototypes and 13 months prior.
Still, while it unequivocally proved that SpaceX is on the right track, both the lead-up to Starship SN5’s hop and the hop itself hint that a few kinks will still need to be worked out. Notably, during SN5’s hop, part of Raptor engine SN27 appeared to catch fire at some point after ignition, producing substantial flames that lasted for at least 10 seconds. For any rocket engine, an onboard fire is always a possibility, but most engines are either designed to tolerate the inhospitable environment they create or heavily insulated from it.



Festooned with sensitive wires and harnesses, Raptor prototypes are likely not meant to experience an extended onboard fire and remain functional, but SN27 nevertheless did just that. At a minimum, Starship SN5 thus likely needs a new Raptor engine before it can begin to prepare for a second hop.
The prototype will also assuredly need several new landing legs after destroying at least two during its launch and landing debut. It’s worth pointing out that the leg damage visible above is almost certainly the result of an intentional design choice, ensuring that landings slightly rougher than expected transfer most of their stress into Starship’s legs instead of its hull. Given just how simple they appear, the current leg design likely makes them effectively disposable, allowing SpaceX to focus its effort on unsolved problems as a more refined and reusable leg design comes to fruition.

Aside from confirming that SpaceX at least intends to reuse Starship SN5 on future hops, Musk revealed that he wants to refine the launch procedure until the company is able to easily perform multiple Starship hops per day. This suggests that the next one or several months could be chock full of Starship hop attempts. Musk also noted that Starship SN6 – a prototype built along SN5 and effectively completed weeks ago – would likely attempt its first flight before SN5 hops a second time. SpaceX began stacking the upgraded Starship SN8 prototype just a few days ago, raising the question of whether Starship SN6 would be made redundant before it could even left the factory.
Thankfully, it seems that the ship will instead be able to work alongside its sister (SN5) to help SpaceX simplify and expedite Starship test and launch operations. As of now, it’s unclear when SpaceX intends to restart Starship testing, but Musk’s comments point towards the next test happening far sooner than later.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.