Connect with us

News

SpaceX set to launch reused Dragon on a new Falcon 9 as NASA requests delay

Falcon 9 B1050 lifts off during the first Block 5 launch of Cargo Dragon.(Tom Cross)

Published

on

An electrical fault aboard the International Space Station (ISS) has forced NASA to delay SpaceX’s CRS-17 Cargo Dragon launch from May 1st to May 3rd, giving the station’s crew more time to fix the issues at hand.

A new Falcon 9 Block 5 booster is tasked with launching the spacecraft and completed a static fire test at SpaceX’s LC-40 pad on April 27th. The Cargo Dragon capsule, however, completed its first orbital resupply mission (CRS-12) in September 2017 and has since been refurbished for a second launch. After CRS-17, three launches remain on SpaceX’s CRS1 NASA contract between now and early 2020, after which Dragon 2 (i.e. Crew Dragon) is expected to take over. However, a recent failure during a Crew Dragon test have thrown those plans into question.

Cargo Dragon’s 17th mission

Known as C113, the CRS-12 capsule is the last Dragon 1 manufactured by SpaceX, leaving a fleet of five flight-proven spacecraft for SpaceX to complete the eight remaining ISS resupply missions under its Commercial Resupply Services 1 (CRS1) contract. CRS-17 is the latest installment in SpaceX’s ISS resupply saga and is manifested with ~2500 kg (5500 lb) of cargo.

Along for the ride are NASA’s Orbiting Carbon Observatory-3 (OCO-3) and the multi-experiment STP-H6 investigation, two large pieces of hardware that will be delivered to the ISS in Dragon’s unpressurized trunk. After being berthed to the ISS, astronauts will unpack dozens of packages stored inside Cargo Dragon’s cabin. Sometime later, the station’s Canadarm2 will be used to grab OCO-3 and STP-H6 and install each on the outside of the space station, where they will hopefully live long and scientifically fruitful lives.

SpaceX and NASA have assigned a new Falcon 9 Block 5 booster – likely B1056 – to launch CRS-17. To preserve the scene of Crew Dragon C201’s April 20th explosion, the booster will attempt to land around 20 miles (32 km) offshore aboard drone ship Of Course I Still Love You (OCISLY). Originally scheduled for April 25th, CRS-17 was delayed to the 26th, 30th, 1st, and now May 3rd, most of which were requested by NASA for ISS scheduling purposes.

The latest delay – from May 1st to no earlier than (NET) May 3rd – was triggered by an unexpected electrical fault aboard the ISS, cutting the redundancy of its Canadarm2 (SSRMS) control systems from two strings to one. In other words, Canadarm2 – used to ‘grapple’ and berth spacecraft like Cargo Dragon and Cygnus to the station – is now just one electrical fault away from being rendered inoperable. CRS-17 will stay grounded until two-string (i.e. single fault) redundancy is returned to Canadarm2 and additional impacted systems.

In the event that ISS astronauts and NASA ground control are able to repair the electrical systems in a timely fashion, CRS-17 is scheduled to launch at 3:11 am EDT (07:11 UTC) on May 3rd.

The International Space Station was captured in October 2018 during a Soyuz fly-around. (NASA/Roscosmos)

In the shadow of Crew Dragon

A recent catastrophic failure of Crew Dragon (i.e. Dragon 2) raises serious questions about SpaceX’s follow-up CRS2 contract, but the nominal plan involves retiring Dragon 1 after CRS-20 and flying all future cargo missions with flight-proven Crew Dragon spacecraft. In the likely event that Crew Dragon C201’s failure delays SpaceX’s CRS2 schedule by several months, there are contingency plans to continue flying refurbished Dragon 1 spacecraft.

However, each Dragon 1 was designed for a maximum of three orbital missions, meaning that SpaceX’s current capsule fleet can support no more than six additional resupply missions before they reach the end of their usable lifespans. SpaceX thus has two potential buffer missions – CRS-21 and CRS-22 – that could theoretically account for up to a year of Dragon 2 delays. Beyond that, additional Dragon 2 delays could create a gap where NASA would have to supply the ISS without SpaceX’s services.

In a best-case scenario, SpaceX and NASA will quickly uncover an unequivocal culprit of C201’s catastrophic explosion, fix the technical and organizational failures that allowed it to happen, and be back on their feet in no time. In reality, it’s likely that the failure will delay future Crew Dragon (and thus Dragon 2) launches by a minimum of 6-12 months. SpaceX will likely need to change up the launch order of its capsules, reassigning DM-2’s Crew Dragon to the in-flight abort (IFA) test and the US Crew Vehicle 1 (USCV-1) Crew Dragon to SpaceX’s first crewed demonstration mission (DM-2). After such a serious and potentially fatal failure, it’s even possible that NASA will require an additional uncrewed orbital launch before permitting SpaceX to fly astronauts on Crew Dragon.

Given that SpaceX’s nominal CRS2 plan involved lightly modifying and reusing Dragon 2s after crewed missions, the future (and schedule) of the company’s Cargo and Crew contracts are intimately intertwined. With any luck, SpaceX and NASA will be able to solve the technical, organizational, and logistical problems now facing them and ensure a stable future for Dragon 2. In the meantime, Cargo Dragon’s CRS-17 mission offers SpaceX a chance to partially verify that Cargo Dragon C201’s issues are are relegated to Dragon 2 and Dragon 2 alone.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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