News
SpaceX’s response to Crew Dragon explosion unfairly maligned by head of NASA
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.
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).
“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.
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.
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.
Elon Musk
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.
For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.
For the most part, things are better in terms of overall behavior.
However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”
He added:
“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.
Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.
It’s in testing right now. Wide release in a few weeks.
— Elon Musk (@elonmusk) March 19, 2026
Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.
It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.
What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.
Cybertruck
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone
Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.
If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.
This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.
Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.
The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.
Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.
Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.
Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡
Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.
News
Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.
🚨 The NHTSA said it was upgrading a probe into Tesla’s Full Self-Driving (Supervised) platform to an “engineering analysis”
It will examine 3.2 million vehicles and aims to determine its effectiveness in evaluating degraded road conditions pic.twitter.com/2dkrv1mR8o
— TESLARATI (@Teslarati) March 19, 2026
The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.
The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.
Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.
However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:
“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”
It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”
The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.
The investigation is listed as EA26002.
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
