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 next Starship flight set to make history on Friday the 13th

SpaceX is targeting Friday, November 13 for Starship Flight 15 and its first ship catch.

Published

on

By

SpaceX is targeting Friday, November 13 for Starship Flight 15, the mission the company plans to use for its first attempt at catching the ship itself with the launch tower.

SpaceX Vice President of Launch Kiko Dontchev shared the date on stage at the UP.Summit on Thursday, according to Ars Technica’s Eric Berger, who was in attendance. It is the first launch target to come directly from a SpaceX executive. Until now, the public schedule had relied on FAA air traffic planning slides, which listed Flight 15 for no earlier than November 8 and later November 12. SpaceX has not posted an official mission page yet, and no launch time has been shared.

The date lands inside the window Elon Musk sketched out last month. Speaking at Giga Texas on October 10, Musk said the flight would “probably launch a little bit before Thanksgiving,” as Teslarati reported. On SpaceX’s third quarter earnings call ten days later, he confirmed that Flight 15 would try to catch both the Super Heavy booster and the ship, and put the odds of a successful ship catch at “more likely than not.” SpaceX also aired an animation of the maneuver during that webcast, showing the ship swinging vertical over Starbase before dropping into the tower’s chopsticks.

The hardware is ready. Booster 22 fired all 33 of its Raptor engines for a full duration static fire at Pad 2 on October 25. Ship 42 followed with a single engine burn simulating a deorbit maneuver on October 26 and a 60 second firing of all six engines the next day, according to NASASpaceflight. Ship 42 had already rehearsed the catch in September, when the Pad 2 arms lifted it into position and crews connected the quick disconnect arm while the vehicle hung from the tower.

The remaining hurdle is regulatory. The FAA’s Starship page does not yet list a Flight 15 license. SpaceX President Gwynne Shotwell said in October that, after “significant constructive engagement with the FAA,” she expects the license to cover a return to the launch site and a tower catch for both stages. Bringing the ship home means a reentry path that heads toward land, rather than ending over open ocean as every Starship flight so far has.

Advertisement
-

SpaceX has caught Super Heavy three times, on Flights 5, 7 and 8, but the ship comes back from orbital velocity and has never been caught. Flight 14 on September 28 was the first Starship to reach orbit, deploying 26 Starlink V3 satellites before splashing down despite an early engine shutdown that Musk blamed on engine computer software.

Musk has called a successful ship catch “the first time that there’s been full recovery of an orbital class rocket,” and he has already named the step after it: a Flight 16 where both the booster and the ship fly again. NASASpaceflight reports that Ship 43, the next vehicle in line, is set for static fire testing in December.

Continue Reading

News

EVgo taps Tesla Superchargers for mass charging expansion

Published

on

Credit: EVgo

EVgo has tapped Tesla Superchargers for its most recent efforts to expand its charging presence in the United States, a move that seems logical based on the effectiveness of the automaker’s own infrastructure.

EVgo opened its first Supercharger site in Illinois, a 12-stall station near downtown Chicago at 3145 South Ashland Avenue in the Riverside Square & River’s Edge center, right beside a grocery store. This marks the start of the company’s plan to deploy hundreds of Supercharger stalls across the United States, primarily at grocery-anchored Regency Centers properties where drivers can shop, eat, or run errands while they charge.

The new location uses Tesla’s Magic Dock technology so both NACS and CCS vehicles can plug in natively without drivers needing to carry their own adapters. Peak power reaches 325 kW at this site, with pricing set between $0.25 and $0.35 per kWh depending on the hour—the same rate for Tesla and non-Tesla drivers.

The stalls also appear in Tesla’s in-car navigation and Trip Planner, making them easy for Tesla owners to find and route to. Illinois has seen EV registrations rise nearly 60 percent over the past two years, and EVgo’s broader network has experienced more than 700 percent growth in charging demand over three years, so the timing fits the market’s trajectory.

Choosing Tesla hardware through the Supercharger for Business program turns out to have been a smart, practical move.

Tesla’s V4 stalls and cabinets deliver high, reliable power with a proven track record of strong uptime, while Magic Dock delivers true dual-standard compatibility in one package. Because the sites show up in Tesla’s navigation tools, EVgo instantly gains visibility among millions of existing Tesla drivers, which should raise utilization and help the company double its addressable market as more vehicles adopt NACS. EVgo still owns the stations and sets pricing, yet benefits from Tesla’s established hardware, longer cables, and operational support.

The result is faster, lower-risk infrastructure expansion that serves every EV driver—Tesla or otherwise—with convenient, high-power charging at everyday retail locations. For drivers, that means fewer adapters, more predictable stops, and a denser network just as electric vehicles become everyday transportation.

Continue Reading

News

Tesla Giga Texas reportedly moves to 24/7 production

Published

on

Credit: @JoeTegtmeyer/X

Tesla’s Austin Gigafactory is reportedly shifting to round-the-clock vehicle production through the end of 2026, according to longtime drone observer Joe Tegtmeyer.

In his November 2 update, Tegtmeyer, widely regarded as one of the most reliable independent sources on Giga Texas activity (we call him the Drone GOAT), stated that the plant has added a night shift, creating two 12-hour production shifts.

Tegtmeyer said in his video:

“Now, I do have some interesting news about that when it comes to the production schedule here at Giga Texas, and things are actually looking pretty good, especially when you think about what the demand is and the delivery numbers that they’re looking for and what they’re expecting. So, normally they have shifts Monday through Friday. It’s a day shift and it’s about 10 hours long or so, give or take. But now they’re on day and night shifts and they’re going to 12-hour days. So they’re going to be adding or they have another shift. They have 12 hours for both of them. In addition to that, the typical downtime that we’re going to be seeing around the holidays, specifically Thanksgiving and Christmas to the New Year time frame is actually changed. And we’re not going to see those big several day events where there is no production. At least that’s what the plan is right now. So, it’s really a great sign, I think, when we consider what they’ve done in the past and what production and the deliveries have been so far. So, maybe it’s shaping up to be a really strong quarter.”

Previously, General Assembly typically operated on a single roughly 10-hour day shift, Monday through Thursday or Friday. The new arrangement keeps General Assembly on its Monday-to-Thursday schedule while adding overnight capacity, and most other areas of the factory continue working the full week with some weekend activity.

Notably, the plant is also forgoing the multi-day shutdowns around Thanksgiving and the Christmas–New Year period that have occurred in prior years

Giga Texas currently builds the Model Y, the larger Model Y L, the Cybertruck, and the Cybercab robotaxi. Tesla has not confirmed the shift change or specified which lines will receive the extra output. Recent comments suggest Cybercab production has been constrained by the pace at which the Robotaxi fleet can absorb new vehicles, making the Model Y and Model Y L the more likely beneficiaries as the company works through order backlogs.

Tegtmeyer’s November 2 footage and commentary also highlighted broader site progress. Cortex 2 continues to expand, with additional compute coming online, a roughly 25 percent lengthening of the structure on the north end, and work on a third cooling plant.

The Boring Company tunnel site showed increased activity in the large launch pit, while the Advanced Technology Chip Fab (a SpaceX–Tesla joint R&D facility) continued steel superstructure and heavy truss installation, along with concrete pours.

The reported capacity increase arrives as Tesla aims for a strong fourth quarter following solid third-quarter results. While unconfirmed by the company, the information aligns with Tegtmeyer’s consistent track record of accurate on-site observations.

If Tesla makes the decision to sustain the all-day production plans, the dual 12-hour shifts would meaningfully raise weekly output potential at one of Tesla’s most important manufacturing hubs.

Continue Reading