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’s Grok Bot is picking up the phone now, and the first calls are wild
Elon Musk wants Grok Bot users making phone calls, and one Comcast call saved $500.
Elon Musk is pushing Grok Bot users toward a feature that, until this week, few of them could actually use. “Try asking Grok @Bot to make calls!” Musk wrote on X Tuesday afternoon, quoting a demo from Sawyer Merritt that included audio from a live call.
Musk first announced calling on October 25, writing that the agent could “call someone or a business for you, make a request on your behalf, take notes on the response and send you a note summarizing the conversation.” There were no release notes at the time, and the feature only appeared in preview builds. That changed on Tuesday, when creator Peter Yang said all Grok Bot users should now be able to call US businesses. Musk reposted his demo.
Try asking Grok @Bot to make calls! — Elon Musk (@elonmusk) November 3, 2026
Yang’s call shows how far the feature goes. In his video, his bot dialed Comcast, worked through the phone menu, deflected small talk about the weather by saying it does not “have eyes on the sky,” turned down three upsells and used a cheaper fiber offer from competitor Sonic as leverage. His bill dropped from $84 to $45 per month on a faster plan, a savings of nearly $500 a year. The call ran about 25 minutes, and the bot paused to get Yang’s approval before accepting the final terms.
Merritt described what the user sees: a live transcript runs during the call, and when the business asks for something the bot does not know, an answer box pops up in the chat. The user types a reply and Grok relays it to the person on the line. Other users posted results Tuesday, including a $100 gift card recovered from Verizon Fios after a 51 minute call and a same day pediatric appointment, which Musk also shared. Not every call worked. One user said a rep refused to cancel a subscription once it was clear an AI was on the phone.
Grok @Bot can now call someone or a business for you, make a request on your behalf, take notes on the response and send you a note summarizing the conversation! — Elon Musk (@elonmusk) October 25, 2026
The Grok Bot terms require every call to identify itself as a virtual assistant calling on the user’s behalf and warn that calls may be recorded. Marketing, mass calling and impersonation are prohibited, and calling currently works only with US numbers.
The timing stands out. Days ago, users began hitting their weekly limits early, and Musk said the cost of serving Grok Bot was “unsustainably high relative to revenue,” as Teslarati reported. A call that spends most of its 25 or 50 minutes on hold is the kind of long running task that eats into usage, and SpaceXSI has not said how calls count against the weekly pool. Grok Bot is included from the $30 Premium tier of The X Subscription upward.
For Tesla owners, the agent has been in their cars since September 22 and is enabled across every Cybercab and Model Y Robotaxi. Musk has already pitched it for phone chores like scrubbing your number from spam call lists. Neither Tesla nor SpaceXSI has confirmed whether a bot can place one of these calls on request from inside the vehicle.
Tesla Full Self-Driving, which is now referred to in Europe as “Tesla Assisted Driving” (TAD), is getting hit with a handful of new changes at the hands of the Netherlands’ vehicle authority, the RDW (Rijksdienst voor het Wegverkeer).
On 3 November, the RDW announced that it has assessed and approved a set of changes to Tesla’s FSD Supervised driver-assistance system. The updates introduce the official European name TAD and impose stricter controls on the system’s speed behaviour.
The new name will appear on the in-car display, in the owner’s manual, and in all other driver-facing information. The change applies to Tesla models equipped with Tesla Assisted Driving and hardware version 4.0 (HW4) or later.
Importantly, the RDW stressed that the name change does not alter the system’s fundamental operation: it remains a supervised driver-assistance feature that supports the driver in performing driving tasks. The driver stays fully responsible for controlling the vehicle at all times.
Beyond the rebranding, the most significant functional adjustments concern speed settings. Drivers will still be able to set a speed margin, a percentage by which the system may exceed the applicable speed limit when necessary for safety or traffic flow. However, the maximum allowable margin has been reduced from +50% to a maximum of +10%.
In addition, every time the vehicle is started, the speed-margin setting will default to 0% deviation, and other speed-related functions will be disabled by default. These changes will be delivered through an over-the-air (OTA) software update from Tesla.
Tesla requested the RDW’s review of these “minor changes.” After evaluating how the modifications were implemented and how the system behaves, the authority found no adverse or unintended effects on the system’s operation or the vehicle’s driving behaviour. Consequently, the existing type approval remains valid under the same conditions and for the same use; no amendment or extension of the approval is required.
The RDW has informed the nine EU member states that have already accepted its type approval—Belgium, Denmark, Estonia, Croatia, Latvia, Lithuania, Slovenia, Slovakia and Czechia—about the updates. Broader EU-wide approval is still under discussion within the European Technical Committee on Motor Vehicles (TCMV). Those proceedings remain confidential, and the RDW has declined to comment on them.
The approved changes align with earlier discussions involving German authorities, which had advocated both for clearer naming to avoid misleading drivers and for a tighter speed offset.
By formally incorporating these adjustments while leaving the core type approval intact, the RDW has cleared the way for Tesla to roll out the updated TAD software via OTA to eligible vehicles in the Netherlands and the other countries that recognise the Dutch approval. The system continues to function strictly as supervised driver assistance, with the human driver remaining the responsible party.
Tesla has released a fresh point-of-view video capturing the next-generation Roadster’s headline stunt from its October 15 unveiling, giving fans a visceral look at the car as it jumps and rotates over its siblings within the company’s vehicle lineup.
Tesla posted the video on X today with the caption “POV you’re a flying car,” and the roughly 30-second clip reveals never-before-seen angles directly attached to the Roadster. It’s really unbelievable:
The sequence reveals the uncrewed prototype firing its cold-gas thrusters, lifting off the ground, and barrel-rolling fully inverted while sailing over a staged lineup that includes a Model 3, Model Y, Cybercab, Cybertruck, and Tesla Semi.
Here’s an image of it that Tesla shared right after the unveiling event for a better perspective of what you’re looking at:
Credit: Tesla
There are also some other cool takeaways from the video, including the shift to the inverted-ramp demonstration. The Roadster uses its underbody suction-fan system to climb, then lock itself upside down on the ramp.
This generates multiple Gs of downforce, which then translates into the Roadster releasing these systems to enable a mid-air roll. The car then settles on its wheels gently as thruster vapor provides a perfect cushion.
All of the runs at SpaceX’s McGregor, Texas, test site, which is where the unveiling took place, were autonomous. Elon Musk stated this was a safety measure.
Tesla shows what Roadster drivers will see on screen before thruster activation
Tesla’s vehicle-engineering chief Lars Moravy dubbed the mid-air roll the “kickflip,” prompting Musk to quip that Tony Hawk would be proud and that the car could clear even more of the fleet. The thrusters, which use high-pressure compressed air and fast electric actuators, provide the precise, short-duration force needed for both the launch and the controlled rotation; the same hardware is intended for production versions of the higher-end Thrust and Rocket trims.
The second-generation Roadster, first teased in 2017, has been delayed repeatedly. Musk has indicated production is targeted for 2028.
While the company has yet to publish full pricing or independent performance verification, the combination of extreme acceleration, ground-effect suction, and limited flight capability has already positioned the car as one of the most theatrical EV reveals in years.
Musk has also said Tesla plans a dedicated Texas test track so future owners can experience the maneuvers themselves, far from public roads. The new POV clip simply lets everyone else feel a fraction of that experience from the car’s own cameras.
Elon Musk’s Grok Bot is picking up the phone now, and the first calls are wild
Tesla Full Self-Driving gets hit with some adjustments in Europe
