News
NASA’s SLS Moon rocket almost aces vital prelaunch test on 7th try
Following several incomplete attempts in April, June, August, and September, NASA’s first Space Launch System (SLS) Moon rocket has almost aced a vital prelaunch test on the seventh try.
NASA says that “all objectives were met” during the ten-hour test, which wrapped up around 4:30 pm EDT (20:30 UTC) on Wednesday, September 21st. Despite the rocket running into multiple additional issues, some old and others new, the agency was confident enough in the preliminary results of the wet dress rehearsal (WDR) – deemed a “cryogenic demonstration test” – to reaffirm that it’s still working towards a third launch attempt as early as September 27th.
That launch date is not set in stone, but NASA also hasn’t ruled out the window after the latest round of SLS testing. The agency will host a press conference on Friday, September 23rd, to provide its final decision and offer more details about the seventh wet dress rehearsal.
Despite NASA’s apparent confidence after the test, which was admittedly smoother than most previous SLS tests at the launch pad, it was far from smooth. The immediate story of the “cryogenic demonstration test” dates back to the SLS Artemis I rocket’s second so-called “launch attempt” on September 3rd. During that attempt, the launch was aborted well before SLS was ready when NASA detected a major hydrogen fuel leak around one of the quick-disconnect umbilical panels that fuels and drains the rocket. Remote troubleshooting was unable to solve the problem, forcing NASA to stand down.
Over the last few weeks, teams inspected, tested, and repaired the faulty Tail Service Mast Umbilical (TSMU), preparing for a cryogenic proof test meant to verify that the issue was fixed. During that September 21st test, the TSMU still leaked significantly for the whole duration, but it did so more predictably and – unlike prior leaks – never violated the limits that would trigger a launch abort.
But near the end, a different umbilical panel developed a significant hydrogen leak that did violate those launch constraints, meaning that NASA would have likely had to stand down yet again if it had attempted to launch before completing additional testing. The test was completed successfully, but its goals and constraints were not the same as those facing a launch.
A NASA-developed rocket leaking hydrogen is unfortunately a tale as old as time. That the agency that struggled with hydrogen leaks throughout the 30-year career of the Space Shuttle appears to be just as flabbergasted by nearly identical problems on a new rocket – SLS – that has Shuttle ‘heritage’ on almost every square inch is not surprising, even if it is somewhat embarassing.
Liquid hydrogen fuel always has been and likely always will be a massive pain to manage in any rocket, but especially in a large rocket. As the smallest element in the universe, it is fundamentally leak-prone. Combined with the fact that it only remains liquid below the extraordinarily low temperature of -253°C (-423°F), generates ultra-flammable hydrogen gas as it continually attempts to warm to a more stable temperature, and naturally embrittles most metals, it’s an engineering nightmare by almost every measure.
For all that pain, hydrogen does provide rocket engineers exceptional efficiency when properly exploited, but even that positive aspect is often diminished by hydrogen’s ultra-low density. For rocket stages that have already reached orbit, hydrogen-oxygen propellant offers unbeatable efficiency. But for a rocket stage that will never be used in orbit, like the SLS core stage, hydrogen fuel is rarely worth the tradeoffs – a reality that SLS is unfortunately providing a strong reminder of.
Demonstrating the Groundhog Day-esque nature of NASA rockets and hydrogen leaks, the same leaky TSMU panel that aborted SLS’ September 3rd launch attempt (sixth WDR) and had to be fixed and retested on September 21st also caused a hydrogen leak that partially aborted the rocket’s third wet dress rehearsal attempt in April 2022. NASA then rolled the rocket back to the Vehicle Assembly Building (VAB), where workers spent almost two months inspecting and reworking the fuel TSMU and fixing other issues. During its first test (WDR #4) after rolling back to the pad in June, the same fuel TSMU leaked and NASA had to return the rocket to the VAB again to fix the problem.
The fuel TSMU then leaked on the SLS rocket’s first launch attempt (really WDR #5), but the problem was resolved and was not what caused NASA to stand down. It was, however, a primary reason behind NASA’s second aborted launch attempt (WDR #6). With any luck, the eighth time will be the charm.
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
