News
NASA contracts SpaceX for a second crewed Starship Moon landing
NASA says it exercised a contract option to purchase a second crewed Starship Moon landing from SpaceX.
Aside from its general existence, though, very little else is known about the new contract. NASA has yet to discuss when it will launch or which Artemis mission it will be attached to. A step further, it’s not actually clear why two crewed “demonstrations” are needed or what the difference between those two missions is. But more importantly, a broader Artemis Program manifest overview published days later revealed that NASA has plans for a truly unusual gap in crewed Moon landings in the mid-2020s.
Mere days after the announcement, an official NASA schedule showing the agency’s plans for the Moon and Mars over the next ten years explicitly contradicted it, showing only two Starship HLS demonstrations: one uncrewed and one crewed. Assuming that was simply a matter of poor coordination, the graphic reveals another bizarre reality: NASA appears to be explicitly planning for a three-year gap between SpaceX’s first crewed Starship landing in 2025 and the next crewed Moon landing, which the graphic suggested might occur in 2028.
Every single crewed Apollo Program mission to the Moon – including one aborted circumlunar mission, two missions to lunar orbit, and six successful landings – happened in less than four years. As published, NASA’s current Artemis plan would be akin to completing Apollo 11 – the first crewed Moon landing – in 1969 and then sitting around and waiting until 1972 for the next landing attempt. It’s difficult to properly convey just how bizarre such a huge gap would be.
There are only two obvious possible explanations. First, NASA might prefer a multi-year delay between crewed Moon landings to building and launching another SLS Block 1 rocket, in which case the three-year landing gap is explicitly the fault of years of SLS Block 1B delays – specifically NASA and Boeing’s work on the rocket’s larger Exploration Upper Stage (EUS). Second, it could be the case that NASA and/or SpaceX expects Starship’s first crewed landing to be delayed by one or several years. In 2018, SLS Block 1B was expected to debut as early as 2024. In 2022, NASA now says Block 1B will debut no earlier than 2027, while the last Block 1 launch is NET 2025.

The first explanation is arguably much likelier given that structuring schedules based on the assumption of delays would make very little logistical sense. If SpaceX were to be ready on or close to the original schedule, that would leave NASA’s Moon landing program sitting on its hands for a third of a decade. In an alternative scenario, if NASA was planning to take full advantage of every year it has and SpaceX’s Starship demonstration was still delayed, the space agency would simply end up with more SLS and Orion hardware on hand than it planned for – only a problem if the rocket is literally incapable of launching more than once every year or two. There are few conceivable scenarios where having a mission waiting on a rocket would be preferable to having a rocket waiting for a mission
In other words, NASA probably doesn’t want to plan for a three-year gap between crewed Moon landings. Rather, the anchor NASA has chained the Artemis Program to – SLS and Orion – is likely giving it no choice in the matter. Worse, if SLS Block 1B and EUS development are as poorly managed as SLS Block 1, it’s possible – if not likely – that Artemis IV and V will slip another year or two. As a result, even in the likely scenario that SpaceX’s crewed HLS demonstration runs into a year or so of delays, there could still be a three or even four-year gap between crewed NASA Moon landings right when the program should be getting up to speed.
SpaceX, meanwhile, is privately developing Starship with the ultimate intent of landing humans on Mars. Without NASA’s interest and support, the Moon is a distraction from SpaceX’s real goals. Additionally, through NASA’s Human Landing System (HLS) program, SpaceX will be providing Starship as a service, meaning that the company will retain full rights to and ownership of any system that results. Put simply, there’s a real possibility that NASA’s seemingly extraordinary lack of motivation will create a scenario in which SpaceX could outgrow the space agency’s usefulness in the mid-2020s.

If, for example, SpaceX privately human-rates Starship for launches and entry, descent, and landing; it could use the Starship HLS lander it’s developed with NASA to land its own astronauts on the Moon without the need for SLS, Orion, or NASA. Given that the full extent of NASA’s Artemis Program ambitions appears to be one Moon landing per year, there would be plenty of room for SpaceX to perform multiple additional landings independent of NASA while the space agency’s contractors struggle to build and launch a single SLS rocket in the same time-frame.
Given the political power behind the SLS/Orion programs, it’s not clear if NASA will ever be willing or able to publicly support or take advantage of that logical and likely inevitable maturation of SpaceX’s Starship HLS capabilities. A crewed Moon mission – and especially a crewed Starship landing – successfully completed without the need for SLS or Orion could put NASA’s unsustainable rocket and spacecraft in a very uncomfortable position. Already, the HLS program has relegated SLS/Orion to the role of an Earth-Moon taxi service that just so happens to cost more than $4 billion per launch.
Above all else, uncertainty continues to reign over NASA’s longer-term human spaceflight plans – helped in no small part by the space agency’s lack of any obvious overarching strategy. NASA officials may religiously repeat phrases about how the Artemis Program aims to “sustainably” return humans to the Moon and pave the way to landing astronauts on Mars, but that doesn’t change the fact that the agency’s tangible, funded plans show virtually no evidence of serious preparations for either goal. Only time will tell where that rudderless ship ends up.
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.