News
SpaceX wants to launch its next Starship ASAP
Contrary to recent comments from CEO Elon Musk, SpaceX appears to be forging ahead at full speed in a bid to launch its next Starship ASAP.
Known as Starship serial number 10 (SN10), the prototype is the latest in a series of four ships SpaceX has ultimately set aside from low(er)-altitude development testing. Starship SN8 – the first functional prototype to reach its full height – debuted on December 8th, 2020, blowing expectations out of the water with a failure mere seconds before the end of a more than six-minute flight test. According to Musk, had a fuel tank remained properly pressurized from start to finish, SN8 could have very well stuck the landing on the first try.
Two months later, after the better part of two weeks of licensing and static fire test delays, Starship SN9 attempted to carry the torch forward but suffered an unrelated failure slightly earlier than SN8’s. One of two Raptor engines failed to ignite for a high-risk flip and landing burn, causing the Starship to impact the ground even more violently than its predecessor. It’s unclear why the ill-fated Raptor failed to ignite or why the engine that did ignite appeared to experience a major failure shortly thereafter but rocket propulsion is extraordinarily difficult – and Raptor is near – or at – the end of that scale.
While SpaceX obviously hasn’t spun around and fixed a complex Starship propulsion issue in a matter of days, Musk eventually revealed his opinion that he, his engineers, or some combination of both “were too dumb” to exploit one obvious way to mitigate the risk of engine failure during flip and landing. That ‘obvious’ tweak: reignite all three of Starship’s available landing engines, not just two.
In theory, with a fast-enough response time, Starship could ignite all three Raptors, perform a supercharged flip from a belly- to tail-down orientation, and selectively shut off one of the engines based on the data from what is essentially a midair static fire. In the event that all three engines are performing nominally, Starship would shut down the least useful engine (i.e. the Raptor with the least leverage) for a gentle two-engine landing burn.
That said, the ship landing burn has a clear solution. My greatest concern is achieving good payload to orbit with rapid & full reusability, without which we shall forever be confined to Earth.— Elon Musk (@elonmusk) February 5, 2021
Impressively, Musk said that SpaceX would implement those changes immediately, attempting the first three-engine reignition as early as Starship SN10’s launch debut. Already at the launch pad when Starship SN9 lifted off, SpaceX revealed plans to launch SN10 as early as February 2021 at the end of SN9’s test flight webcast.
A few days prior to SN9’s ill-fated test flight, Musk had also stated that Starship SN10 would perform a “cryoproof” test and only then have its three Raptor engines installed. Instead, in an apparent change of plans, SpaceX installed Starship SN10’s Raptors – SN39, SN50, and an unknown third engine – from February 5th to 7th.
On Sunday, local longtime resident Mary (aka BocaChicaGal) received an official safety alert from SpaceX, signaling plans for an explosive Starship test of some kind as early as Monday, February 8th. Historically, those overpressure safety warnings have only been distributed when SpaceX is preparing for a Starship static fire attempt. In other words, it’s possible that Starship SN10’s very first test could be a live wet dress rehearsal (WDR) with flammable liquid oxygen and methane propellant. If that WDR goes well, SpaceX could move directly into a one, two, or three-engine static fire.
Of course, as SN9’s lengthy test period rubbed in, Starship is still in the prototype stage and is far from a mature system, meaning that it’s always safer to expect delays than an on-time performance. To be clear, it’s far more likely that SpaceX will perform a familiar “cryo proof” test with non-flammable liquid nitrogen – perhaps hoping to complete a cryoproof and static fire in the same test window.
Either way, stay tuned for updates and follow along with NASASpaceflight’s excellent live coverage in the event that SpaceX really is prepared to static fire Starship SN10 between 9am and 6pm CST (UTC-6) on Monday.
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
