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

Tesla Roadster’s new patent preps white-knuckle speeds, keeping it grounded

Published

on

Credit: @BLKMDL3/Twitter

Ahead of its highly anticipated unveiling, Tesla’s upcoming Roadster received a new patent that aims to keep it grounded while enabling white-knuckle speeds.

The patent, which was granted on September 29, is titled “Electric Car Fan,” bluntly stating its design but not its purpose, which is further detailed in the text of the application. Interestingly, it comes two weeks before the Roadster event, which was delayed due to unfavorable weather on Thursday, which could cause issues, as Tesla revealed the event must be held outdoors.

The purpose is to solve a problem that is relatively unique to high-performance electric cars. Instant motor torque is useless if the tires cannot plant that force, and conventional wings and underbody tunnels generate downforce only when air is already rushing past the car. At launch, in slow corners, and under hard braking from modest speed, passive aerodynamic additions contribute essentially very little to downforce.

Tesla’s filing says that its fans can produce the downforce needed, independent of vehicle velocity, then ease off so the same hardware does not pile on drag at highway speeds, an issue that can come from excessive body modifications.

The hardware outlined in the patent is a ducted-fan package that is placed into the rear of the vehicle. An underbody inlet between the rear wheels feeds a duct that rises to a wide outlet in the diffuser. In that outlet are four axial fans, which are divided by vertical strakes. They will pull air from under the floor and press the chassis onto the pavement.

The language in the patent claims it can cut drag rather than add to it while simultaneously increasing downforce.

Tesla Roadster event requires restricted airspace, and the FAA obliges

The fans run from the high-voltage battery and a vehicle control system, so output can be modulated rather than left on as a fixed penalty.

There are additional strengths that can come from this design, like extra tire load at low speed, which can contribute to even more face-melting acceleration rates, decrease stopping distance, and sharper turn-in before a wing has air to work with. Adjustable fan speed lets the car add grip only when needed, so it can be catered to the force of a turn or acceleration.

These designs were previously used, and banned, in some competitive settings. The Brabham BT46B was banned in F1 competition for using a similar fan design and being labeled as too effective.

Tesla still lists the Roadster as having a sub-two-second 0-60 MPH time and a 250-plus-MPH top speed, and there are expectations for a SpaceX cold-gas thruster package that could not only increase acceleration but potentially cause the vehicle to hover.

It is important to note that a patent is not a production part, and packaging four fans in a rear diffuser, managing noise, and potential debris are all things Tesla must consider. With that being said, the patent being granted shows Tesla is designing the Roadster to go fast, but it is also attempting to use unique strategies to combat any issues it might have at those speeds.

Continue Reading

Investor's Corner

Tesla showrooms picked clean ahead of Q3 end as demand looks strong

Published

on

Credit: @thaichiminh1907/X

Tesla (NASDAQ: TSLA) showrooms have been picked clean ahead of the end of the third quarter of the year, as demand looks to be strong and delivery estimates for new vehicles are pushed into late 2026 and early 2027.

Tesla appears to have sold out of many of its Model 3 and Model Y trim levels in the United States, as only the Model Y RWD and Model Y All-Wheel-Drive are available for delivery before the end of the year.

Additionally, many showrooms are either completely empty or void of all but just one demo unit within the buildings themselves in an effort to bolster what could be one of Tesla’s best quarters in vehicle deliveries in recent memory.

Additionally, when I spoke to the guys at Tesla Mechanicsburg two weeks ago, when I returned the Model Y L, their third hauler of the week had just arrived, and every vehicle on it, along with every vehicle in their delivery lot, was accounted for and had a name attached to it for delivery.

Tesla saw a 25 percent increase in deliveries in Q2 compared to the same quarter the year before. The vast majority of the 480,126 units it delivered, 467,762 vehicles to be exact, were the Model 3 and Model Y.

In Q3 2025, Tesla delivered 497,099 vehicles, once again a figure that was dominated by the company’s two mass-market vehicles. Analysts have unusually wide predictions for this quarter, likely because so many firms missed the Q2 delivery figure by such a substantial margin; Wall Street predicted 408,000 cars, while Tesla delivered 480,000.

Goldman Sachs has Tesla slotted for 435,000 deliveries in Q3, while JPMorgan said it anticipates 482,000. The median guess is about 449,000 deliveries for Q3.

Interested in ordering a Tesla? Use my referral code for three free months of Full Self-Driving (Supervised) here.

Continue Reading

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading