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.
Tesla’s two recently-defunct flagship models, the Model S and Model X, are getting a big upgrade, according to the company’s Head of AI, Ashok Elluswamy.
Older Hardware 3 Model S and Model X vehicles have been the last major holdouts in Tesla’s Full Self-Driving v14 Lite rollout, and that wait now appears to be ending.
Tesla brings closure to flagship ‘sentimental’ models, Musk confirms
At Tesla’s Cybercab launch, AI chief Ashok Elluswamy told Ryan McCaffrey that he thought the S and X build “was supposed to go out last week.” Evidently, Elluswamy expects the suite to be rolled out to those HW3 Model S and Model X very soon:
For my @Tesla friends – and specifically Model S & X owners with HW3 who are waiting on FSD v14 Lite – I spoke to @aelluswamy at the Cybercab launch, & when I asked for an ETA on v14 Lite for S/X owners, he said, “Oh, I thought it was supposed to go out last week.”
So: soon! 🙌
— Ryan McCaffrey (@DMC_Ryan) September 7, 2026
Those cars are not the current Model S and Model X, which already ship with Hardware 4. They are the pre-refresh flagships built around Tesla’s older Autopilot computer, often called HW3 or AI3.
Tesla stopped putting that computer in new vehicles years ago, which is why owners treat these S and X cars as a closed generation. Model 3 and Model Y vehicles on the same computer began receiving v14 Lite in late June 2026 and saw a wider North American expansion in July. South Korea followed as an early international market. The S and X versions of the same software never joined that wave.
v14 Lite is Tesla’s way of squeezing the current v14 driving stack onto hardware that cannot run the full AI 4 model. The company describes the process as distillation: behaviors learned on the newer computer, including reinforcement learning and offline models, are compressed so the older chip and cameras can use them as a guide.
Early descriptions put the distilled network at roughly 15 percent of the original size. The result is still supervised Level 2 driving. Tesla has been clear that HW3 cannot support unsupervised Full Self-Driving or robotaxi operation because of memory and bandwidth limits.
The feature list is what made the wait so frustrating for S and X owners, as plenty of new features are to be shipped with it.
Official notes for the first Lite build, firmware 2026.20.5.1, added parking, unparking, and reversing; arrival options for a parking lot, street, driveway, or curbside; speed profiles that stay available at all times; and start-from-park engagement. Tesla also claimed better handling of merges, forks, pedestrians, traffic lights, and cut-ins, plus fewer false slowdowns and smoother lane centering.
A mid-July follow-on build, 2026.20.6.10, added more of the Hardware 4 interface, including a standalone Self-Driving app and the ability to start a trip from Park without a brake-pedal confirmation.
Elluswamy called that version the one “likely going to wide release.”
That wide release already reached most other HW3 cars in the United States and Canada. International timing still depends on regional validation and regulatory approval. For S and X owners, the remaining work appears to be model-specific validation rather than a new software stack.
There is no official Tesla changelog or build number for those two models yet, only Elluswamy’s offhand timeline. Some HW3 drivers who already have Lite report large gains over v12.6; others have described new indecision or phantom braking. The next test will be whether the same software lands cleanly on the older flagships that have waited the longest.
Yesterday, we reported on Tesla Cybertruck getting some major adjustments from a manufacturing standpoint in an effort to make the all-electric pickup more cost-effective, more reliable, more serviceable, and more easily produced.
Tesla Cybertruck engineer reveals new changes in ‘constantly evolving’ pickup
One of those changes was the addition of a self-reinforcing polypropylene aero shield that sits underneath the truck. Previously, Tesla utilized aluminum for this, but the self-reinforcing polypropylene was more durable while also being cheaper and lighter.
Tesla has revealed another small change it made to the Cybertruck, and it has to do with the side repeater cameras.
Tesla does not wait for a new model year to improve its vehicles. On September 8, Cybertruck lead engineer Wes Morrill posted side-by-side photos of an updated side repeater camera housing now rolling off the line at Gigafactory Texas.
The triangular camera pod mounted on the front fender looks almost identical at first glance. A closer look reveals a revised contour that uses the air already flowing around the truck to keep the lens clearer in rain and road spray.
The side repeater camera was updated – the version on the left is the newer part which uses passive geometry to create airflow disturbance that better keep water off the lens while driving. No cost penalty, just pure vision improvement. pic.twitter.com/wAbXtcL1Jf
— Wes (@wmorrill3) September 8, 2026
The side repeater cameras sit in an exposed position on the Cybertruck’s angular stainless-steel body.
In wet weather, they readily collect water droplets that can degrade the image Autopilot and Full Self-Driving use for lane changes and blind-spot monitoring. Early production trucks sometimes left owners wiping lenses by hand or accepting temporary restrictions on driver-assistance features.
Tesla has added washers to cameras on certain other models and on Cybercab prototypes, but those active systems add cost, complexity, and extra potential leak points.
The new housing solves the problem with passive geometry. Subtle changes in the surround create localized airflow disturbances as the vehicle moves. Those eddies physically push water droplets away from the optical surface. Morrill called the result “pure vision improvement” achieved at “no cost penalty.” Once the production mold is updated, every subsequent part costs the same as the original.
The advantages compound quickly. Clearer cameras in rain improve the reliability of driver-assistance features precisely when they are needed most. The design consumes no extra energy and introduces no new failure modes.
New Cybertrucks built after the tooling changeover receive the updated part automatically. Some owners of trucks delivered as late as June 2026 have already confirmed they received the revised housing. Retrofit questions have appeared in replies, and the cameras appear electrically compatible, though Tesla has not announced an official service program.
A few millimeters of reshaped housing will not make headlines the way a new battery pack does, but these changes are incremental and increase the Cybertruck’s effectiveness as a vehicle over time.
This improvement illustrates how Tesla continues to refine the Cybertruck after volume production began. Better wet-weather vision, zero added cost, and no extra hardware add up to a meaningful gain in everyday usability and safety.
Tesla is rolling out a new version of its Full Self-Driving suite to some owners that comes with the massive addition of a safety feature.
Tesla is rolling out Automatic Collision Evasion with the 2026.27.6 Software Update, which started rolling out to some vehicles last night. We received the update, along with Full Self-Driving v14.3.9, as well as v14.2 Lite, which has identical release notes as the previous version and seems to have some refinements and improvements in behavior and performance.
🚨 Tesla FSD v14.3.9 is rolling out as well as 2026.27.6 which includes Automatic Collision Evasion
Brand new safety features from a software update. My Tesla gets better everytime I get one of these pic.twitter.com/ctrMiQXWhM
— TESLARATI (@Teslarati) September 8, 2026
However, most of the attention has fallen on the Automatic Collision Evasion feature, which we covered in an article last week.
The function will activate Full Self-Driving to “try to keep your vehicle safe and then continue driving. It can engage in the following situations while you are driving manually:
- Scenario 1: A frontal collision is imminent and braking alone may not avoid it.
- Scenario 2: Your vehicle detects that you are not sufficiently attentive to the road (for example, reaching toward the back seat), or that Full Self-Driving (Supervised) may have been unintentionally disengaged.”
Essentially, FSD will take over when the vehicle determines you are not paying sufficient attention or are heading toward a potential collision. The addition of this feature is incredibly useful as distracted driving is a major issue in today’s world.
Along with the new safety feature is Tesla FSD v14.3.9, which has no additional release notes compared to the previous version, but in my first drives, my first impression is that operation is great, and parking is still sort of a pain point.
Just took a 15-mile round trip to the gym and back
Pretty on par with what FSD is nowadays – really good. Not enough time to see what’s good and what’s bad, but these first rides on any version feel shockingly good. They’re all pretty identical https://t.co/WN1qTg4bhE
— TESLARATI (@Teslarati) September 9, 2026
Additionally, Tesla v14.2. Lite has arrived. A great review of that is available here:
— Zack (@BLKMDL3) September 9, 2026
The addition of an Automatic Collision Evasion feature is similar to that of other collision avoidance systems that are used by companies like Hyundai, Kia, and Genesis. These programs typically utilize radar and camera sensors to apply emergency brakes autonomously, though evasive steering in a manual driving mode is pioneered primarily by Tesla’s newest addition.
Tesla’s two defunct flagship models are getting a big upgrade
This tiny Tesla Cybertruck adjustment has big advantages
