Connect with us

News

SpaceX’s response to Crew Dragon explosion unfairly maligned by head of NASA

SpaceX's first spaceworthy Crew Dragon capsule seen prior to its first Falcon 9-integrated static fire and a post-recovery test fire three months later. (SpaceX)

Published

on

In a bizarre turn of events, NASA administrator Jim Bridenstine has offered harsh criticism of SpaceX’s response to Crew Dragon’s April 20th explosion, suffered just prior to a static fire test of its eight Super Draco abort engines.

The problem? The NASA administrator’s criticism explicitly contradicts multiple comments made by other NASA officials, the director of the entire Commercial Crew Program, and SpaceX itself. Lest all three of the above sources were either blatant lies or deeply incorrect, it appears that Bridenstine is – intentionally or accidentally – falsely maligning SpaceX and keeping the criticism entirely focused on just one of the two Commercial Crew partners. The reality is that his initial comments were misinterpreted, but an accurate interpretation is just as unflattering.

Stay ahead of the curve and be the first to learn about new industry trends each week!

Follow along as our team gives you their take on the biggest stories of the week.

Ultimately, Bridenstine responded to a tweet by Ars Technica’s Eric Berger to correct the record, noting that the criticism was directed at his belief that SpaceX’s “communication with the public was not [good]”, while the company’s post-failure communication with NASA was actually just fine. In fact, according to Commercial Crew Program (CCP) Manager Kathy Lueders, NASA team members were quite literally in the control room during the pre-static fire explosion and the failure investigation began almost instantly.

A blog post and official update published by NASA on May 28th further confirms Lueders’ praise for the immediate SpaceX/NASA response that followed the failure.

“Following the test [failure], NASA and SpaceX immediately executed mishap plans established by the agency and company. SpaceX fully cleared the test site and followed all safety protocols. Early efforts focused on making the site safe, collecting data and developing a timeline of the anomaly, which did not result in any injuries. NASA assisted with the site inspection including the operation of drones and onsite vehicles.”
— NASA, May 28th, 2019

Why, then, are Bridenstine’s comments so bizarre and unfair?

A trip down memory lane

Back in mid-2018, Boeing’s Starliner spacecraft suffered a major setback (albeit not as catastrophic as Crew Dragon’s) when a static fire test ended with a valve failing to close, leaking incredibly toxic hydrazine fuel all over the test stand and throughout the service module that was test-fired. The failure reportedly delayed Boeing’s Starliner program months as a newer service module had to replace the contaminated article that was meant to support a critical 2019 pad-abort test preceding Starliner’s first crew launch.

According to anonymous sources that have spoken with reporters like Eric Berger and NASASpaceflight.com, the anomalous test occurred in late-June 2018, followed by no less than 20-30 days of complete silence from both Boeing and NASA. If Boeing told NASA, NASA certainly didn’t breathe a word of that knowledge to – in Bridenstine’s words – “the public (taxpayers)”. Prior to Mr. Berger breaking the news, Boeing ignored at least one private request for comment for several days before the author gave up and published the article, choosing to trust his source.

Boeing’s Starliner spacecraft. (Boeing)

After the article was published, Boeing finally provided an official comment vaguely acknowledging the issue.

“We have been conducting a thorough investigation with assistance from our NASA and industry partners. We are confident we found the cause and are moving forward with corrective action. Flight safety and risk mitigation are why we conduct such rigorous testing, and anomalies are a natural part of any test program.”
— Boeing, July 21st, 2018 (T+~30 days)

SpaceX, for reference, offered an official media statement hours after Crew Dragon capsule C201 suffered a major failure during testing, acknowledging that an “anomaly” had occurred and that SpaceX and NASA were already working closely to investigate the accident. Less than two weeks after that, Vice President of Mission Assurance Hans Koenigsmann spent several minutes discussing Crew Dragon’s failure at a press conference, despite the fact that it was off topic in an event meant for a completely different mission (Cargo Dragon CRS-17).

Advertisement
-

“Earlier today, SpaceX conducted a series of engine tests on a Crew Dragon test vehicle on our test stand at Landing Zone 1 in Cape Canaveral, Florida. The initial tests completed successfully but the final test resulted in an anomaly on the test stand. Ensuring that our systems meet rigorous safety standards and detecting anomalies like this prior to flight are the main reasons why we test. Our teams are investigating and working closely with our NASA partners.”
— SpaceX, April 20th, 2019 (T+several hours)

Within ~40 days, NASA published an official update acknowledging Crew Dragon’s accident and the ongoing mishap investigation. Meanwhile, a full year after Starliner’s own major accident, NASA communications have effectively never once acknowledged it, while Boeing has been almost equally resistant to discussing or even acknowledging the problem and the delays it caused. On May 24th, NASA and Boeing announced that Starliner’s service module had passed important propulsion tests (essentially a repeat of the partially failed test in June 2018) – the anomaly that incurred months of delays and required a retest with a new service section was not mentioned once.

During the second attempt, a Starliner service section successfully completed a test that ended in a partial failure during the first attempt ~11 months prior. (Boeing/NASA)

On April 3rd, NASA published a Commercial Crew schedule update that showed Boeing’s orbital Starliner launch debut (Orbital Flight Test, OFT) launching no earlier than August 2019, a delay of 4-5 months. In the article, NASA’s explanation (likely supplied in part by Boeing) bizarrely pointed the finger at ULA and the technicalities of Atlas V launch scheduling.

In other words, NASA somehow managed to completely leave out the fact that Starliner suffered a major failure almost a year prior that likely forced the OFT service section to be redirected to a pad abort test.

Following SpaceX’s anomaly, the company (and NASA, via Kathy Lueders) have been open about the fact that it means the Crew Dragon meant for DM-2 – the first crewed test launch – would have to be redirected to Dragon’s in-flight abort (IFA) test, while the vehicle originally meant to fly the first certified astronaut launch (USCV-1) would be reassigned to DM-2. Thankfully, this practice can be a boon for minimizing delays caused by failures. Oddly, Boeing has not once acknowledged that it was likely forced to do the same thing with Starliner, albeit with the expendable service section instead of the spacecraft’s capsule section.

Again, although the slides of additional CCP presentations from advisory committee meetings have briefly acknowledged Starliner’s failure with vague mentions like “valve design corrective action granted” (Dec. 2018) and “Service Module Hot Fire testing resuming after new valves installed” (May 2019), NASA has yet to acknowledge the Service Module failure and its multi-month schedule impact.

An official slide from NASA Commercial Crew Manager Kathy Lueders, presented in May 2019 – one month after C201’s explosion – during a NASA Advisory Committee (NAC) meeting. (NASA)

So, if SpaceX’s moderately quiet but otherwise excellent communication of Crew Dragon’s explosion was unsatisfactory and worthy of pointed criticism straight from the head of NASA, the fact that Boeing and NASA have scarcely acknowledged a Starliner anomaly that caused months of delays must be downright infuriating, insulting, and utterly unacceptable. And yet… not one mention during Bridenstine’s bizarre criticism of SpaceX’s supposed communication issues.

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

SpaceX’s Anthropic deal has a catch, and Elon Musk just addressed it

Elon Musk says SpaceX’s Anthropic compute deal cuts both ways after Chamath floats higher prices.

Published

on

By

Elon Musk pushed back on Sunday against the idea that SpaceX’s compute contract with Anthropic is a one way bet, after venture capitalist Chamath Palihapitiya argued the company could use a termination clause to charge the AI lab far more.

“It works both ways, of course. If compute becomes plentiful and cheap, SpaceX revenue will drop. No crying in the casino for either party,” Musk wrote on X Sunday evening, replying to a clip of Palihapitiya’s comments shared by AI commentator Rohan Paul.

On the All-In podcast released Sunday, Palihapitiya said either side can walk away from the agreement on 90 days’ notice. If data center supply tightens, he argued, SpaceX could exercise that option and bring the contract back at two to three times the current price, and Anthropic would have little choice but to accept. He called it “the kingmaking move,” according to BigGo Finance.

The clause itself is not new. SpaceX disclosed in its IPO filings in May that Anthropic would pay $1.25 billion per month for dedicated capacity at its Colossus clusters through May 2029, nearly $45 billion in total, with both companies able to terminate on 90 days’ notice, as Teslarati reported at the time. SpaceX’s later compute deals with Google and Reflection AI carry similar exit terms.

What has changed is the political backdrop. Palihapitiya’s thesis rests on incoming Democratic governors pulling tax incentives for data centers and slowing new construction. In Texas, Gov.-elect Gina Hinojosa campaigned on a moratorium on new data center approvals, and Deutsche Bank analysts warned last week that SpaceX’s Texas compute capacity could face delays. SpaceX and Tesla shares both fell after the midterm results.

Advertisement
-

A slowdown would favor companies that already own capacity. SpaceX acquired xAI in February and has been renting data centers to outside AI labs before the space is needed for Grok. At the Baron Investment Conference on Friday, Musk said SpaceX was “getting 50 billion a year for 35 billion dollar investments” and that it can bring a data center online in eight or nine months, compared to two and a half years for competitors. He also said SpaceX is tracking toward an annualized revenue rate above $100 billion in December, with a “best guess” of $500 billion by December 2027.

Musk’s reply points to the other side of the clause. Anthropic has signed large compute agreements with Amazon, Google and Microsoft, and if that capacity comes online faster than new construction slows, the AI lab would have its own leverage to renegotiate or leave. Musk has called Anthropic “obviously currently the leader in AI,” and it remains one of SpaceX’s largest compute customers.

SpaceX shares rose more than 2 percent in overnight trading late Sunday after closing Friday at $134.27, according to Stocktwits.

Continue Reading

Elon Musk

Elon Musk spotlights the Starlink rescue that got through where no cell tower could

Elon Musk spotlighted how Starlink helped rescuers reach five people stranded in Kazakhstan’s snowy mountains.

Published

on

By

Elon Musk put a spotlight on a mountain rescue in eastern Kazakhstan on Sunday, writing “Starlink saves lives” in response to a post describing how SpaceX’s satellite internet helped five stranded people reach emergency crews.

The post from DogeDesigner, which had been viewed more than 500,000 times by Sunday afternoon, said the group’s SUV broke down about 15 kilometers from the village of Kystau Kurchum in an area with no usable mobile network. Starlink carried their call for help and kept them in contact with rescuers, who used the connection to locate them.

The rescue itself took place in October. Local outlet YK.kz reported on October 22 that Kazakhstan’s Ministry of Emergency Situations responded to the breakdown in the Kurchum district of East Kazakhstan region and noted that the group stayed in touch through Starlink. Rescuers covered roughly 100 kilometers in a Trekol, a low pressure tire vehicle built for snow and marshland, then escorted the disabled SUV back to Kystau Kurchum. Nobody needed medical attention.


Conditions in the region were rough at the time. Kazakh broadcaster Channel 7 identified the five as hunters caught in a snow trap and said satellite communication allowed rescuers to pinpoint where they were. A spokesperson for the East Kazakhstan emergency department said a storm warning was in effect and urged residents not to leave populated areas unless necessary. The same weather stranded seven utility workers repairing power lines in the nearby Kuygan rural district, according to Tengrinews.

Kazakhstan has been one of Starlink’s more notable markets in Central Asia. Teslarati reported in 2024 that Starlink was serving 1,731 of the country’s 1,879 schools, with the country’s Education Minister saying it had set a new standard for internet service in schools.

Rescue stories like this one have followed Starlink for years, usually in places where ground networks fail or never existed in the first place. Then Florida CFO Jimmy Patronis called Starlink a “game changer” for search and rescue crews during Hurricane Milton, and SpaceX and T-Mobile switched on Starlink Direct to Cell in North Carolina to push emergency alerts to phones after Hurricane Helene.

The next target is dead zones for people who do not carry a dish at all. SpaceX is building out Starlink Mobile and earlier this week selected Qualcomm to supply core infrastructure for a planned terrestrial 5G network in the United States, which it intends to pair with its next generation satellite constellation.

Sunday’s post is at least the third time Musk has written “Starlink saves lives” on X this week, following identical posts on November 5 and November 7.

Continue Reading

Elon Musk

SpaceX will perform Starship double catch attempt with Flight 15

Published

on

Credit: SpaceX

SpaceX plans to attempt what will be a defining moment in rocket reusability on Starship Flight 15.

As Elon Musk announced in a recent X post, SpaceX will attempt to catch both the Super Heavy Booster and the Starship upper stage during the upcoming orbital flight. If successful, it will mark the first time that all parts of an orbital rocket return to Earth intact, a breakthrough Musk has called essential to making life multiplanetary.

Previous flights have demonstrated the tower-catch technique with Super Heavy. SpaceX has successfully caught V1 boosters three times (on Flights 5, 7, and 8), with some even reflown. The Ship upper stage has never been caught.

Returning from orbital velocity after deploying payload makes it a significantly harder challenge due to higher energy, heat loads, and the need for precise belly-flop reentry, a flip maneuver, and a final landing burn to settle between the Mechazilla tower’s chopstick arms.

Flight 15, using Booster 22 and Ship 42 (both Block 3 vehicles), is targeted for no earlier than Friday, November 13, 2026, from Orbital Launch Pad 2 at Starbase, Texas. The 75-minute window opens at 4:45 p.m. CT, pending regulatory approval. After hot staging and separation, the booster is planned to return for a catch roughly 6 minutes and 35 seconds after liftoff.

The Ship will insert into a roughly 275 km orbit, deploy 26 advanced Starlink V3 satellites, complete about 14 orbits over more than 22 hours, and—if systems check out—perform a deorbit burn, reentry, flip, and landing burn for a tower catch at approximately T+22 hours 32 minutes.

SpaceX confirms Starship 15 launch window with massive ambitions

A simulation shown during SpaceX’s October earnings call depicted the Ship descending in a belly-flop attitude, flipping upright with a short engine burn, and being captured by the arms:

Contingency splashdown zones exist in the Gulf of Mexico (booster) and Pacific (Ship) if a catch is not viable. SpaceX has stressed rigorous health checks before committing the Ship to a return-to-launch-site trajectory.

Musk has described the odds of success on this first dual-catch attempt as “more likely than not,” noting a steady stream of additional flights is already scheduled if needed. Full recovery would enable rapid inspection, refurbishment, and reflight—slashing costs and supporting the high launch cadence required for Starlink expansion, lunar missions, and eventual Mars settlement.

As Musk put it, this is “the critical breakthrough needed to make life multiplanetary.”

Continue Reading