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

News

SpaceX set to launch astronauts and a classified Falcon Heavy mission on the same day

SpaceX plans three launches Thursday, including Crew-13 astronauts and Falcon Heavy’s first classified NRO mission.

Published

on

By

Crew Dragon sits atop Falcon 9 at sunrise on Cape Canaveral's pad 40, less than a day before four astronauts are set to launch to the ISS. (Credit: SpaceX)
Crew Dragon sits atop Falcon 9 at sunrise on Cape Canaveral's pad 40, less than a day before four astronauts are set to launch to the ISS. (Credit: SpaceX)

SpaceX is lining up one of the busiest single days in its history, and the company offered a preview on Wednesday morning with a simple post on X: “Sunrise at pad 40.” The video and photos show Falcon 9 standing at Space Launch Complex 40 at Cape Canaveral, roughly a day before it is scheduled to carry four astronauts to the International Space Station.

That launch is only the first of three SpaceX missions planned for Thursday, October 1, across both coasts.

Crew-13 is targeting liftoff at 11:10 a.m. ET, with a backup opportunity Friday at 10:47 a.m. ET. NASA astronaut Jessica Watkins will command the mission, with NASA’s Luke Delaney as pilot and Canadian Space Agency astronaut Joshua Kutryk and Roscosmos cosmonaut Sergey Teteryatnikov serving as mission specialists. According to NASA, Dragon is set to dock with the forward port of the station’s Harmony module around 8 p.m. ET, less than nine hours after launch. Watkins is the only member of the crew who has flown before, and Kutryk will become the first Canadian to reach orbit through NASA’s Commercial Crew Program.

The Falcon 9 booster is flying for the third time after supporting Crew-12 and a Starlink mission, and it will attempt a landing at Landing Zone 40 beside the pad. That site made its debut in February when the Crew-12 booster touched down there, as Teslarati reported at the time. Crew-13 will relieve the Crew-12 astronauts, who have been aboard the station since the middle of February.

On the West Coast, another Falcon 9 is scheduled to lift off from Vandenberg Space Force Base in a window running from 2:18 to 3:16 p.m. ET, a flight NASASpaceflight lists as a Transporter rideshare mission.

The day is set to close at 11:53 p.m. ET, when Falcon Heavy launches from Launch Complex 39A with NROL-97, the first National Reconnaissance Office payload ever to fly on the rocket. SpaceX rolled the vehicle out to the pad Tuesday night. Its two side boosters, which previously flew GOES-U, ViaSat-3 F3 and NASA’s Roman Space Telescope, will return to Landing Zones 1 and 2, while a new center core will be expended in the Atlantic. The Roman launch took place on August 30, so NROL-97 will come barely a month later as Falcon Heavy’s third flight of 2026 and 14th overall.

NASA taps SpaceX to launch the telescope that could unlock new worlds

If all three Florida boosters land as planned, it would be the first time the Space Coast has seen landings at LZ-40, LZ-1 and LZ-2 on the same day, according to the Orlando Sentinel, which has warned residents in Brevard, Orange and Volusia counties that more than one sonic boom is possible.

The schedule arrives just three days after Starship reached orbit for the first time on Flight 14 from Starbase, Texas, deploying 26 Starlink V3 satellites. If Thursday’s missions stay on time, SpaceX will have flown Starship, Falcon 9 and Falcon Heavy from four different pads in about four days.

Crew-13 is also the start of a longer run for Dragon. NASA recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification, keeping Dragon as the agency’s only operational ride to the station while Boeing’s Starliner remains grounded.

Continue Reading

News

Tesla Cybercab and Semi have more in common than you might think

Published

on

Credit: Tesla

Although the two vehicles are built for completely different use cases, Tesla utilized engineering expertise while developing both the Cybercab and Semi to build a thermal architecture that would fit both vehicles. Of course, with some slight revisions.

The development was noted by Lars Moravy and Dan Priestley last week at Tesla’s Semi Handover event in Sparks, Nevada, where the company showed off its dedicated production facility for the Class 8 truck.

Tesla’s decision to develop one thermal architecture for both the Cybercab and Semi is one of the more revealing engineering choices in the company’s 2026 lineup:

“We designed it at the same time we designed the Cybercab and we said okay we’re going to take our most efficient vehicle and our biggest vehicle and we’re going to take one thermal system and make it work for both.”

Core parts, meaning the compressor, pumps, and heat exchangers, are shared, with only modest changes to cooling-loop sizing and a larger radiator on the truck. The result, they said, is a compressor and thermal stack already proven across millions of miles, delivering “reliability from day one.”

Priestley also highlighted a practical payoff of the indirect design:

“There’s no AC lines, there’s no refrigerant lines…It comes from the factory fully charged, sealed with refrigerant, and it just exchanges coolant. It doesn’t actually run refrigerant up to the front of the vehicle.”

This eliminates potentially leak-prone plumbing that would otherwise require hands-on service, reducing overall uptime and potentially cutting into business margins. The megamanifold runs cabin HVAC and every powertrain heating and cooling loop at once, recapturing waste heat from motors and the battery instead of dumping it the way a diesel engine does.

The approach is just the latest chapter in a continuing story of stretching thermal solutions across wildly different vehicles. Model Y’s Octovalve evolved into the Super Manifold used on Cybertruck, and later Model S/X refreshes. Cybercab then introduced Supermanifold V3, which Tesla says is 80 percent automated to build and 38 percent more efficient than typical automotive thermal systems.

Tesla has done the same with the 4680 cells, both being utilized in the Cybertruck and Semi, and with heat-pump compressors that Priestley noted were already common across the passenger-car fleet.

Concurrent development of crucial vehicle elements buys scale and reliability that a truck-only thermal system could not match. High-volume passenger car parts are cheaper and more accessible, which can give fleets a sealed, low-maintenance loop of operation from their first day of operation.

For owners and operators, that translates into less energy spent on cabin heat in the colder months, fewer refrigerant-related repairs, and a thermal architecture already stress-tested at passenger-car volumes before the first high-volume Semi left the lines in Nevada.

Continue Reading

Elon Musk

Elon Musk weather update tips Tesla Roadster speculation into Plaid Mode

Published

on

elon musk
Credit: Tesla

Tesla CEO Elon Musk certainly tipped off some details of the Tesla Roadster event with a broadening of information regarding the company’s decision to delay the unveiling for two weeks.

For years, people have speculated about what the Roadster will be capable of. While there have been plenty of things said about what it *could* do, we have not seen or been told by Tesla what it will actually be capable of.

However, over the past few days, Tesla’s weather updates have truly pushed the speculation into Plaid Mode, basically all but confirming the car will have some sort of aerial capability — whether that would be hovering or fully flying remains to be seen — but it definitely seems that it will be able to leave the ground intentionally.

“Because this event can only be held outdoors…”

Tesla posted on Monday that it would delay the Roadster event until October 15, and it indicated that it had to do this because the event “can only be held outdoors.”

With the potential SpaceX collaboration to develop cold-gas thrusters that will help the vehicle go airborne, doing this indoors is probably not a safe, or even plausible, possibility.

FAA Airspace Restriction

The FAA gave Tesla a Temporary Flight Restriction (TFR) for 10,000 feet above ground level, much higher than the typical 2,000-foot restrictions that are usually placed at SpaceX’s McGregor, Texas site.

Tesla Roadster event requires restricted airspace, and the FAA obliges

Some have said that this massive increase is due to Tesla’s need to restrict unauthorized drone use for spying on the event.

Elon Admits High Winds

“Due to high winds, the new Roadster demo is postponed by 2 weeks,” Musk said in a post on X yesterday.

A reply reading, “What’s strong wind got to do with a car demo with four grounded wheels?” was directly below Musk’s post, satirically and sarcastically probing for more details.

All signs are pointing toward an aerial demonstration for the Roadster.

Continue Reading