News
NASA scrubs first SLS Moon rocket launch attempt
NASA has scrubbed the first attempted launch of its Space Launch System (SLS) Moon rocket after running into multiple issues, one of which could not be solved in time.
The delay is bad news for the tens to hundreds of thousands of tourists who traveled to Cape Canaveral, Florida to witness the launch in person. Worse, by NASA’s own implicit admission, there’s a good chance the main problem SLS encountered could have already been dealt with and rectified in advance of the launch attempt if the space agency had finished testing the rocket earlier this summer.
Ultimately, that omission turned the first SLS launch attempt into more of a continuation of the rocket’s first four wet dress rehearsal (WDR) attempts, none of which ended as expected. NASA engineers will now have to decide how to proceed and whether the SLS rocket can be made ready in time for another launch attempt on September 2nd or 5th. If not, the next opportunity could be weeks away.
As far as SLS test operations go, the August 28/29th launch attempt was fairly ordinary, with the rocket running into multiple issues – a few minor, a few significant, and one identical to a previous problem. The first problem – a hydrogen leak near the SLS rocket’s base – came after a risk of lightning delayed the start of propellant loading by more than an hour. A very similar, if not identical, hydrogen fuel leak had already occurred during official wet dress rehearsal testing in April and July.
That leak was fixed on the fly by properly chilling all related systems, and propellant loading was eventually completed – albeit a few hours late thanks to inclement weather. Shortly after, there were reports of a crack that needed careful analysis. Only later did NASA specify that the suspected crack was in the rocket’s foam insulation rather than its structures, the latter of which could have been a catastrophic problem.
Around the same time, the true showstopper of the day occurred when NASA attempted to chill the SLS Core Stage’s four RS-25 engines, all of which flew several times aboard reusable Space Shuttle orbiters. Three engines performed (mostly) as expected, flowing a bit of liquid hydrogen fuel to cool themselves down, but one – engine #3 – was never able to make progress toward the optimal temperature needed for ignition (~5°C/~41°F). After hours of remote troubleshooting attempts, no progress had been made, and NASA ultimately decided to scrub the launch attempt at T-40 minutes to liftoff.
Over the course of four separate wet dress rehearsal attempts in April and June 2022, NASA was never able to test the core stage’s engine chill capabilities. In a post-scrub press conference, Jim Free – NASA’s Associate Administrator of the Exploration Systems Development Division – revealed that all four engines were warmer than intended, further confirming that skipping a fully nominal wet dress rehearsal was likely a mistake. Clear and present evidence aside, Free stated that he and other executives still believed skipping that test was the right decision, claiming that ending explicit WDR testing reduced the number of times the rocket needed to be moved on its transporter.
Making the situation even harder to explain, Artemis I Mission Manager Mike Sarafin revealed in the conference Q&A that Boeing had changed the design of parts of the SLS engine chill (bleed) system after the Core Stage finally conducted a nominal static fire test at Mississippi’s Stennis Space Center. Completed in March 2021, the SLS rocket then sat inside NASA’s Kennedy Space Center, Florida Vehicle Assembly Building (VAB) for a full year before attempting its first wet dress rehearsal tests at the launch pad.
The first round of three WDRs were not as smooth as NASA expected and instead uncovered three relatively small issues: a hydrogen leak, a single faulty upper stage valve, and problems with a ground supply of nitrogen gas. Those small issues led NASA to roll SLS back to the VAB for repairs, incurring a minimum multi-week delay that stretched into two months. SLS also failed to complete a fourth WDR attempt in July 2022, but NASA decided to overlook the rocket parts and phases of preflight operations that were never actually tested as planned, one of which was the engine chill system.
If NASA cannot fix the RS-25 chill system within the next few days, it will be forced to roll the entire rocket and mobile launch platform back to the VAB to – at a minimum – replace its flight termination system (FTS). The US Eastern Range requires that all rocket FTS systems be tested no more than 15 days before launch, and NASA was able to secure special permission for a gap of up to 25 days. However, because Boeing’s Core Stage design places the FTS system in a location that is reportedly inaccessible at the pad, the entire SLS rocket will need to roll back to the VAB to have its FTS systems “retested” after that period.
As a result, NASA’s SLS launch debut will be delayed by several weeks (at best) if it can’t recycle for another attempt on September 2nd or 5th. The next window runs from September 20th to October 4th, but the SLS rocket took 10 days to go from its latest rollout to first launch attempt – a figure that doesn’t include the time required to remove the rocket from the pad, roll it back to the VAB, and conduct any necessary repairs or tests while back in the bay. If NASA can’t fix the engine problem at the pad by September 3rd or 4th, the true delay could be more like 4-6 weeks.
With any luck, that won’t happen, but it’s clear that a lot of stress and discomfort could have been avoided if NASA had gone into its first launch attempt knowing that its SLS rocket was truly ready.
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 launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
