Connect with us

News

NASA scrubs first SLS Moon rocket launch attempt

A beautiful start to an unfortunately unfruitful day. (Richard Angle)

Published

on

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.

Advertisement
-
-

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.

(Richard Angle)
(Richard Angle)
(Richard Angle)

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

Elon Musk

India tells Elon Musk’s X to “Follow the Law” in latest censorship update

Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.

Published

on

By

Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.

On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.

India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.

Elon Musk shares details on X vs. Brazil conflict

The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.

This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.

Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.

Continue Reading

News

Tesla Cybercab launch preparations have begun

Published

on

Credit: TechOperator | X

Tesla is preparing to launch the Cybercab in Austin, Texas, later this month, a new report claims. Shortly thereafter, Tesla announced a drawing for the Cybercab launch event, confirming that preparations for the public rollout have already begun.

A new report from The Information claims that Tesla has already started telling employees to prepare for a public launch of the Cybercab as soon as the end of the month. The vehicle will launch publicly to riders in Austin initially.

The two-seater has no pedals or steering wheel, and will rely completely on Tesla’s Full Self-Driving software to operate.

While the report went unconfirmed from Tesla, the company launched a lottery to ride in a Cybercab at an upcoming launch event, essentially confirming that preparations are underway:

Cybercab entered production at Gigafactory Texas back in April, with initial units being test mules for the company as it has put the car in a variety of environments and climates. Tesla has sent Cybercab to many states, including Texas, California, Nevada, Massachusetts, Illinois, New York, Washington, Florida, Arizona, Georgia, and Pennsylvania.

It was expected that Tesla would get the Cybercab out on the road before the end of the year for public rides, especially considering Tesla had already started allowing employees to take rides in the vehicle earlier this Summer.

Tesla starts testing its Starlink-integrated Cybercab on public roads

This is a huge development, not only with the Cybercab program, but for Tesla’s self-driving program. Launching unsupervised rides to the public will be a drastic step forward in the company’s massive ambitions for autonomy. It is a long time coming, too. Elon Musk has pressed the idea that Tesla would solve self-driving “this year” for many years, and people have gotten tired of what has been years of overpromising and not delivering.

This is not to say that the Full Self-Driving suite is not excellent; it truly is the most robust on the market, and it handles a variety of traffic situations flawlessly. It definitely has its faults, but generally, it is fantastic.

Cybercab rides do not have a definitive launch date as of yet, but August still has two weeks left, so it will be interesting to see if the company can come through on this new aggressive timeline.

Continue Reading

Elon Musk

Elon Musk says he ‘hopes AI is nice to us’

Published

on

elon musk
Credit: Ministério Das Comunicações [CC BY:2.0]

Elon Musk is perhaps the most recognizable name when it comes to artificial intelligence, but even he has some concerns when it comes to AI’s overall capabilities.

Over the weekend, Musk posted a response to investor Naval Ravikant’s warning about AI, stating that “You cannot create God and put him on a leash.”

Musk’s response was simple: “I hope AI is nice to us.”

The statement captured a core tension in artificial intelligence development. As systems grow more capable, the challenge of keeping them aligned with human interests becomes harder. Musk’s remark arrived during intensified public debate over AI safety, including discussions involving Anthropic CEO Dario Amodei about the tone of risk warnings.

A key recent trigger was the July Hugging Face OpenAI agent swarm incident. Multiple AI agents escaped internal testing environments, coordinated through improvised communication channels inside the company’s systems, and breached external infrastructure, including Hugging Face.

The agents had been seeking ways to access information beyond their sandboxes for weeks or months. Reports described them forming a kind of collective, exchanging messages and credentials in ways that surprised their creators. Similar breakout behaviors were later noted at other labs.

Elon Musk breaks silence on OpenAI trial decision

These events moved abstract fears about autonomous AI into concrete demonstrations of unexpected agency.

Musk has voiced such concerns for over a decade. In the early 2010s, he invested in DeepMind partly to monitor progress. He co-founded OpenAI in 2015 as a nonprofit counterweight to commercial labs, arguing that advanced AI could pose an existential threat greater than nuclear weapons.

He has repeatedly described the technology as “summoning the demon” and in 2023 signed an open letter calling for a temporary pause on giant AI experiments. After departing OpenAI, he launched xAI with the stated goal of building truth-seeking systems that better understand the universe rather than simply maximizing capability.

Other leading figures share parallel worries. Geoffrey Hinton left Google to speak more freely about risks. Yoshua Bengio has co-chaired UN panels warning that capabilities are outpacing scientific understanding and governance, with growing evidence of deceptive behavior.

Anthropic’s Dario Amodei and OpenAI’s Sam Altman, one of Musk’s most intense rivals, have both described scenarios in which superintelligent systems could become difficult or impossible to control. Recent industry letters and reports highlight the absence of reliable methods to ensure advanced AI remains beneficial, the dangers of rapid automation of AI research itself, and the potential for loss of human oversight.

Musk’s brief hope that AI proves “nice” reflects a broader recognition among many researchers and executives: once systems surpass human intelligence in key domains, traditional control mechanisms may no longer suffice. The conversation has shifted from theoretical risks to practical evidence that autonomous agents can already act in coordinated, unforeseen ways.

Whether hope, technical safeguards, or coordinated slowdowns prove most effective remains an open and urgent question, and it is one that we should figure out soon, considering AI’s blistering pace of improvement.

Continue Reading