News
SpaceX’s orbital Starship launch debut could still happen this year
Despite the spectacular demise of a full-scale prototype just days ago, a senior SpaceX engineer and executive believes that Starship could still be ready for its first orbital launch attempt before the end of the year.
Even if the first launch attempt fails, that milestone – if realized – would be one of the single biggest upsets in the history of spaceflight, proving that Saturn V-scale orbital-class rockets can likely be built in spartan facilities with common materials for pennies on the dollar. Much like Falcon 1 suffered three launch failures before successfully reaching orbit, there’s a strong chance that Starship’s first shot at orbit will fall short, although each full-up launch failure would likely cost substantially more than the current prototypes being routinely tested to destruction in South Texas.
Most recently, what CEO Elon Musk later described as a “a minor test of a quick disconnect” went wrong in a spectacular fashion, causing a major liquid methane leak that subsequently ignited and created a massive explosion. Although Starship SN4 did technically complete its fifth Raptor engine static fire test just a minute or so prior, the ship and its immediate surroundings were obliterated by the violent explosion, leaving little more than steel shrapnel and the broken husk of a launch mount behind. It’s in this context that one of SpaceX’s most levelheaded, expert executives believes that an orbital launch could still happen this year.
While Starship SN4’s demise and the continued possibility of the ship’s orbital launch debut occurring less than seven months from now may seem at odds with each other, that’s actually just a side effect of the approach SpaceX has always taken when developing brand new rockets and spacecraft. Following the lead of the scrappy teams that used the exact same methods to design, test, and fly the massive Saturn rockets that took humans to the Moon, SpaceX has always preferred to learn by doing.
Inevitably, testing minimum viable products to their limits will lead to failures, but those failures are actually extremely valuable so long as they are extensively analyzed and learned from. That’s exactly what SpaceX has been doing for the last six or so months with full-scale Starship prototypes: building, testing, failing, and improving in an unending cycle. Built slowly with inferior methods, Starship Mk1 almost immediately during its first pressure test in November 2019. SpaceX took that failure, extracted all the insight it could, and dramatically improved its production methods before completing Starship SN1 barely three months later.
Prior to SN1, SpaceX built and tested two stout test tanks to failure, ultimately achieving pressures of ~8.5 bar – sufficient for reliable human spaceflight – with the second tank on January 30th, 2020. On February 28th, Starship SN1 was unfortunately destroyed by a faulty ‘thrust puck’ (Raptor engine mount). Just 10 days later, SpaceX successfully tested a third ad-hoc test tank, proving that it had already rectified the engine section design flaw. Hardware isn’t always the only problem, however, and Starship SN3 was destroyed by human operator error during a cryogenic proof test on April 3rd.
Starship SN4 was completed and moved to the launch pad less than a month later and began testing just a few days after that, quickly racking up milestones as it became the first full-scale prototype to pass cryogenic proof testing, perform a wet dress rehearsal (WDR) with real propellant, fire up a Raptor engine, and complete a more ambitious cryogenic pressure test. Prior to the ground systems fuel leak that killed it, SN4 was possibly just days away from attempting the inaugural flight of a full-scale Starship prototype.
With Starship SN4 now steel confetti, Starship SN5 – effectively complete – will likely take over where its predecessor left off, heading to the launch pad within the next week or so before attempting a cryogenic pressure test and Raptor static fire to clear it for flight. Per Koenigsmann, that flight debut could come just a few weeks from now – likely before the end of June if replacement ground equipment can be quickly completed. If Starship SN5 survives that hop debut, it may ultimately be upgraded with a nosecone, flaps, and two additional Raptor engines to perform a dramatic 20 km (~12 mi) flight, capped with a supersonic skydiver-style reentry and landing test.
Once that capability has been successfully demonstrated, Super Heavy development and orbital Starship operation and reentry are the next critical hurdles. If Koenigsmann is correct, it’s safe to say that the first fully heat-shielded Starships and the beginnings of the first one or several Super Heavy booster prototypes will begin to appear in South Texas within the next few months.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
