News
SpaceX Dragon XL could double as a crew cabin for lunar space station
A recent modification to SpaceX’s Dragon XL lunar cargo resupply contract with NASA suggests that the spacecraft could be used as an extra crew cabin and bathroom at a lunar space station known as Gateway.
The contract modification was made around April 1st of this year and provided SpaceX around $121,000 to complete the latest study on the potential utility of its expendable Dragon XL spacecraft beyond the primary goal of resupplying a space station orbiting the Moon. Designed to deliver at least five metric tons (~11,000 lb) of pressurized and unpressurized cargo to Gateway, Dragon XL will launch on SpaceX’s own Falcon Heavy rocket – currently the only super heavy-lift launch vehicle in operation – and meant to heavily borrow from hardware and systems already developed for Crew and Cargo Dragon.
NASA first announced its selection of SpaceX for the Gateway Logistics Services (GLS) contract back in March 2020. More than a year later, very little has been said (or visibly done) to progress from that announcement to a true contract – an unusually long period of inactivity for such a significant program.
Of note, as recently as April 2021, NASA officials made it clear that they were still in the cryptic process of “reviewing” the Artemis program, leading to such a long delay between the GLS award announcement and finalization of an actual contract with SpaceX. Of note, back when it was announced, NASA’s nominal plan was to begin Dragon XL cargo deliveries as early as 2024 to support the Artemis Program’s first crewed Moon landing attempt.
Since then, however, other crucial aspects – namely the concept of operations and Human Lander System (HLS) meant to carry astronauts to and from the Moon – have evolved significantly. Weeks after NASA’s GLS announcement, the space agency awarded approximately $1 billion to three prospective HLS providers – SpaceX, Dynetics, and a team led by Blue Origin. A little over a year later, NASA announced a shocking decision to award that initial HLS Moon landing demonstration contract to SpaceX and SpaceX alone.
More or less simultaneously, NASA it made it clear that it was seriously studying the possibility of performing Artemis-3 – the first crewed Moon landing attempt in half a century – without Gateway. Along those lines, the SLS-launched Orion spacecraft and HLS lander (a custom variant of SpaceX’s Starship) would dock directly in lunar orbit instead of separately docking to Gateway to transfer crew. NASA’s decision to solely select Starship as its future Moon lander was so surprising in large part because of how starkly the vehicle’s potential capabilities contrast with the rest of the Artemis Program.
As many have already noted, the very existence of a Starship with capabilities close to what SpaceX is working towards – now a practical inevitability for the company to complete its HLS contract – brings into question the architecture NASA has proposed for Artemis. Currently, the nominal plan is to launch astronauts into an exotic high lunar orbit with NASA’s own SLS rocket and Orion spacecraft – an inconvenient orbit only needed to make up for said spacecraft’s shortcomings. Prior to recent developments, Orion would then dock with Gateway. The HLS vehicle would follow and crew would eventually transfer to the lander, which would then carry 2+ astronauts to and from the surface of the Moon and re-dock with Gateway, followed by Orion returning those astronauts to Earth.
Given that Starship offers enough pressurized volume to rival even the vast International Space Station (ISS) in a single launch, the entire concept of Gateway – an almost inhumanely tiny space station – becomes dubious. If Orion also doesn’t need Gateway to transfer its astronauts to the lander, which NASA has all but confirmed, it’s difficult to see what value Gateway could offer outside of a very expensive technology demonstration. Including a planned Falcon Heavy launch of the first two Gateway segments, station production, and the possible need for expensive Dragon XL cargo deliveries, Gateway could easily end up costing NASA $4-5 billion before it hosts a single astronaut.
NASA is already deeply concerned about the apparent likelihood of Congress systematically underfunding the HLS and Artemis programs outside of SLS and Orion, going as far as selecting just a single HLS provider after clearly indicating a desire for redundancy given enough funding. NASA’s HLS contract with SpaceX is expected to cost around $2.9 billion. The next cheapest option – Blue Origin’s proposal – would reportedly cost around $6 billion. In other words, if NASA were able to stop work and Gateway and redirect that funding elsewhere, it could almost already afford two HLS providers without a larger budget.
Given that NASA has selected SpaceX for HLS and GLS, it’s not impossible to imagine that the space agency is growing increasingly aware that Gateway and Dragon XL look more than a little redundant beside the Starship vehicle NASA itself is now funding SpaceX to realize. For now, though, work on all three programs continue. Most recently, NASA and SpaceX are studying the possibility of adding a toilet and using Dragon XL as an extra crew cabin and bathroom to augment the tiny habitable volume of Gateway’s lone habitat. Only time will tell where the cards ultimately fall.
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
