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.
News
SpaceX’s Starfall just went from secret to storefront
SpaceX now pitches Starfall missions with 1,000 kg payloads, weeks of microgravity, and Starlink connectivity.
SpaceX has put up a dedicated commercial page for Starfall, its disk shaped reentry capsule, laying out for the first time what customers actually get when they book a flight. The page, live at spacex.com/starfall, pitches “affordable, routine access to microgravity” and invites companies to get in touch about flying manufacturing, research or testing payloads.
The specs are short and specific. Each Starfall mission carries up to 1,000 kg of payload, supplies 1 kW of power and connects through an Ethernet interface. Mission length is tailored to the customer, and the payload stays online the entire time through Starlink, which means researchers can pull data from an experiment while it is still in orbit instead of waiting for splashdown.
SpaceX is launching a secret spacecraft that could change how things are made in space
SpaceX is aiming the service at three markets. Biomedical customers are told they can grow stem cell organoids, replacement tissue and layered biomaterials. Pharmaceutical companies are pitched on protein and small molecule drug crystals, which form smaller and more uniform shapes without gravity driven convection. Materials science rounds out the list, with semiconductors and other next generation materials grown in vacuum and microgravity.
The page also makes clear which rocket SpaceX is counting on. “By launching on Starship, Starfall brings a reliable and scalable cadence previously unavailable to the market,” the company wrote, contrasting weeks of continuous microgravity with the seconds offered by drop towers and parabolic flights. No price or first operational flight date is listed.
The commercial push is a sharp turn from how Starfall started. SpaceX said almost nothing about the capsule ahead of its first flight in June, and nearly everything known came from FAA and FCC filings describing a disk about 10.2 feet wide and 2.5 feet tall that can return 2,200 pounds of cargo. By its second flight on the Bandwagon-5 rideshare in October, Starfall was listed by name on the mission page, though SpaceX still did not say what it carried.
Customers appear to be lining up. SpaceX said in its third quarter results that it signed three commercial Starfall missions during the quarter. On the earnings call, President Gwynne Shotwell described the capsule as providing “routine relatively low cost access to microgravity environments for scientific research, including improving our understanding of diseases like cancer and diabetes,” and said the three new missions would fly on Starship.
The branding effort extends past the website. SpaceX added a Starfall T-shirt to its online store on Monday as part of a batch of new merchandise, giving the program a place next to Starship, Starlink and Starshield in the company’s lineup.
The move also puts SpaceX in more direct competition with companies it launches. Varda Space Industries, which has built much of the in-space manufacturing market so far, flew its W-Series 7 capsule on the same Bandwagon-5 mission as Starfall in October. Varda’s capsules are roughly three times smaller than Starfall, and SpaceX controls the ride to orbit for both.
Starfall’s near term cadence depends on Starship. SpaceX is preparing for Flight 15 after completing static fires of Ship 42 and its Super Heavy booster in late October, and is aiming to catch both stages with the launch tower on that flight.
Elon Musk said weeks ago during SpaceX’s third-quarter earnings call that the company’s Grok Bot, its autonomous AI Agent platform, was showing “the fastest growth of a product” that he’d ever seen in his life.
Now, SpaceXSI is scaling back Grok Bot users’ weekly limits, much to the surprise of those who have relied on it to take away monotonous tasks in their lives.
Elon Musk’s terse November 1 reply on X captured a sharp tension in the early days of agentic AI. Responding to a user who asked for a Grok Bot usage reset after hitting 100 percent with four days still left on the weekly cycle, Musk wrote: “The cost of serving Grok Bot was unsustainably high relative to revenue.”
@DogecoinNorway The cost of serving Grok Bot was unsustainably high relative to revenue
— Elon Musk (@elonmusk) November 1, 2026
The post arrived amid a wave of similar complaints from paying subscribers whose meters had jumped unexpectedly toward or to the limit, sometimes overnight and with little corresponding activity. It also stood in clear contrast to statements Musk had made only days and weeks earlier.
On the SpaceX third-quarter earnings call in mid-to-late October, Musk had described Grok Bot in almost the opposite terms. He called it “the fastest growth of a product that I’ve ever seen in my life” and said he had “never seen anything grow this fast.”
Company figures put paid weekly users at roughly 800,000 earlier in the month, more than doubling over the prior period. Daily active users had climbed from under 100,000 in early September to over 600,000 by late October.
Musk emphasized that the product has no free tier and that users appear to be getting real value beyond what they pay. In other remarks, he noted that usage per user was rising rather than declining, the opposite of the usual decay pattern for new software.
Grok Bot, launched around August, functions as an always-available agent with its own persistent cloud computer; it can schedule, research, shop, browse, and execute multi-step workflows even after the user steps away. Access is bundled into X subscription tiers (roughly $30, $100, and $200 per month) and certain Cursor plans, drawing from shared weekly usage pools whose exact sizes have not been publicly detailed.
The economics of that model are what Musk’s November 1 post put in the spotlight. Agentic systems burn far more compute than ordinary chatbot exchanges. Each task can trigger repeated model calls, tool use, web actions, and sustained background work.
When growth is as rapid as Musk celebrated, the absolute compute bill scales quickly even if average revenue per user stays fixed under flat monthly subscriptions. Industry observers noted the opportunity cost as well: the same GPUs can be rented to other AI labs at higher rates.
A simple back-of-the-envelope comparison circulating after the post illustrated the gap: if every reported daily user paid the top tier, annualized subscription revenue would still be modest relative to the scale of compute infrastructure SpaceX is building and leasing to companies like Anthropic.
Some users also reported possible dashboard anomalies around the same period, though Musk’s framing treated the underlying cost-revenue imbalance as the core issue rather than a pure metering glitch.
The juxtaposition is the core of this exchange. Within roughly two weeks of publicly framing Grok Bot as an unprecedented success with strong unit economics and no free tier, Musk acknowledged that serving the same product had become unsustainable relative to the revenue it generates.
For the broader industry, the episode underscores a structural challenge of the agent era: demand is real and growing faster than many expected, yet the cost of fulfilling that demand through always-on, multi-step agents can outrun subscription pricing before companies can adjust limits, introduce metered billing, or raise prices.
Musk’s reply did not promise an immediate reset or higher allowances; it simply stated the constraint. In doing so, it supplied a rare, explicit public data point on the unit economics of a high-profile AI agent just as adoption numbers were still being celebrated as the fastest in Musk’s experience.
The tension between rapid, paid growth and the compute required to deliver it is now on the record.
News
Tesla owners who tap Emergency Drive Away for fun are in for a surprise
Tapping Activate on Tesla’s Emergency Drive Away reportedly triggers a $539 service bill without moving.
Tesla owners who press Activate on Emergency Drive Away may be on the hook for a service bill even if their car never leaves the Supercharger stall.
Yaro, who posts about Tesla service cases on X as @Tutrifour, said a customer called after tapping Activate while still plugged into a Supercharger. The owner was about to pull away, remembered the cable was still connected and stopped. The car never moved, but the touchscreen showed a red alert reading “Emergency Drive Away has been activated” with “Service is required” underneath. A Service Mode screenshot showed the active alert BMS_a228_EmergencyDriveAwayServiceRequired, which Yaro said only Tesla Service can clear.
Here is a lesson to Tesla owners. Don’t press Activate on the new Emergency Drive Away feature on your Tesla because service charges $539 to inspect the charge port and to clear the alert. Yes, even if you didn’t move the car an inch. https://t.co/NZJENw4SQv
— Yaro (@Tutrifour) October 30, 2026
The cost of clearing it was the bigger surprise. “Don’t press Activate on the new Emergency Drive Away feature on your Tesla because service charges $539 to inspect the charge port and to clear the alert. Yes, even if you didn’t move the car an inch,” Yaro wrote. The $539 figure comes from that single case, and Tesla has not published a set price for the inspection or commented on the post. Yaro also noted that the car would still charge with the alert on screen.
Tesla launched Emergency Drive Away on October 1 with software update 2026.38.3, letting drivers pull away from a U.S. Supercharger with the cable still attached, as Teslarati reported. To use it, a driver shifts into Drive while connected, holds the brake and taps Activate. The prompt warns that driving with the cable connected will damage the vehicle and the Supercharger, and that short camera recordings will be shared with Tesla.
Tesla Charging has been clear about what follows a real activation. Repairs to a Supercharger stall can run up to $25,000 depending on the site, a service visit for the car’s charge port is mandatory, and deliberate misuse “will invoke additional penalties.” What the company had not spelled out is that the service requirement is triggered the moment Activate is pressed, not the moment the cable breaks away.
From an engineering standpoint, that is the cautious choice. Once Activate is pressed, the car cannot be sure the charge port latch was not stressed, so flagging it for inspection removes the guesswork. It also means the button carries a price on its own, which is a stronger deterrent against casual use than any warning screen.
Customer called because they have an active alert after tapping ACTIVATE on the new Emergency Drive Away feature. They didn’t actually drive away but were about to until they “remembered” they had the charge cable connected.
This alert can only be cleared by Tesla Service. https://t.co/SkHyJJPFwU
— Yaro (@Tutrifour) October 28, 2026
The report follows the feature’s first known real world use, when a driver in Austin during F1 weekend appeared to trigger it by accident and dragged the Supercharger cable along with the car. The Reddit user who filmed it said the driver seemed to have only half read the prompts.
For owners, the takeaway is to treat the red prompt as a stop sign. If it appears after shifting out of Park by mistake, shift back and unplug the normal way from the touchscreen, the Tesla app or the button on the charge handle. Activate is meant for moments when staying at the stall is the bigger risk, and Tesla is now pricing it that way.
SpaceX’s Starfall just went from secret to storefront
Grok Bot users hit with weekly limits early, Elon Musk explains what happened
