Connect with us

News

NASA’s SLS Moon rocket almost aces vital prelaunch test on 7th try

Published

4 years ago

on

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.

Advertisement
-

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.

Advertisement
-
Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

6 hours ago

on

September 28, 2026

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

10 hours ago

on

September 28, 2026

By

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

12 hours ago

on

September 28, 2026

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading