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

MKBHD just ordered the Tesla Cybercab with his hair on the line

MKBHD ordered a Tesla Cybercab, two years after betting his hair Tesla couldn’t sell one.

Published

on

By

Rendering of Marques Brownlee (MKBHD) stands in the parking lot of Kearny Point (his New Jersey studio headquarters), looking at a gold Tesla Cybercab.

Marques Brownlee spent two years betting his hair that Tesla would never sell a Cybercab to regular buyers for under $30,000 before 2027. On Friday, he posted on X that he had been invited to buy one. “Alright chat I’m in,” the YouTuber known as MKBHD wrote, before sharing a screenshot that read “Your Cybercab Order is Confirmed.”

The bet dates back to Tesla’s We, Robot event in October 2024, when Elon Musk unveiled the two seat Cybercab and said customers would be able to buy one for less than $30,000, with production starting “before 2027.” Days later, in a video titled “The Tesla Robotaxi is Confusing,” Brownlee called the timeline “notorious Elon stuff” and said that if Tesla pulled it off, he would “shave my head on camera because I’m that confident.”

Musk accepted the challenge in February, when the first production Cybercab rolled off the Giga Texas line. Asked on X whether Tesla would sell a Cybercab to a customer for $30,000 or less before 2027, he answered “Yes,” and added “Gonna happen,” as Teslarati reported at the time. Brownlee narrowed the terms in a September video, saying the bet was that a “golden robotaxi with two seats and no driver and no steering wheel and no pedals” would not ship “to regular people like you and me for $30,000 before the end of this year.”

Tesla’s invite only order page now lists the Cybercab at $29,990, ten dollars under that line, with estimated deliveries in December. Buyers put down a $1,000 non-refundable deposit, must take delivery in Austin, Dallas, Fort Worth, Houston or San Antonio, and are limited to one vehicle each. A $299 per month Autonomy Subscription is required for the car to operate.

Brownlee is not conceding. “My hair is safe for several reasons,” he wrote, pointing out that no Cybercabs have been delivered and that orders are invite only rather than publicly available. He also noted that the car is limited to personal use inside Tesla’s existing Robotaxi geofences, calling it “a paperweight if I take this thing home,” though he acknowledged that point was never part of the bet. He then asked Grok to set a timer for 48 days, which lands on December 31.

Advertisement
-

Musk responded directly. Replying to Brownlee’s breakdown of the order page, he said the Cybercab “will be available nationwide, as we receive regulatory approval,” and agreed that “the monthly fee is too high”. He said it should match the cost of FSD and connectivity on Tesla’s other models, “more like ~$115/month.” In a separate reply about Brownlee’s hair, Musk wrote, “He’s a chicken.”

Where Brownlee’s car would go is unclear. He lives in New Jersey, far outside any Robotaxi service area, and Tesla’s agreements restrict where owners can operate the vehicle and how they can resell it, as Teslarati detailed.

Continue Reading

Elon Musk

SpaceX makes history, catching Starship from orbit for the first time

SpaceX caught Starship’s upper stage with its launch tower for the first time on Saturday.

Published

on

By

Ship 42 fires its engines as it descends toward the Starbase launch tower’s chopstick arms, moments before SpaceX caught a Starship upper stage for the first time on Flight 15. (Credit: SpaceX)
Ship 42 fires its engines as it descends toward the Starbase launch tower’s chopstick arms, moments before SpaceX caught a Starship upper stage for the first time on Flight 15. (Credit: SpaceX)

SpaceX caught a Starship upper stage with its launch tower for the first time on Saturday, bringing Ship 42 back to Starbase after roughly 22 and a half hours in orbit on Flight 15. No company has ever returned the upper stage of an orbital rocket to its launch site and caught it.

Ship 42 lifted off Friday evening on top of Booster 22, reached orbit and deployed all 26 of its Starlink V3 satellites. Three of those satellites carried cameras to photograph the ship’s heat shield, and SpaceX said the imagery showed it was in good shape for reentry, allowing controllers to pass on a backup splashdown option overnight. By Saturday morning, SpaceX posted on X that “Pad and tower systems are go for catch.” After about 14 orbits, the ship fired its engines to leave orbit, came back through the atmosphere and was caught by the tower’s chopstick arms.

 

The catch salvages a flight that started with a setback. Super Heavy did not make it back to the tower on Friday. “We were initially go for a catch, but in the later stages of the coast, the booster aborted itself for a GNC issue that it detected and that put it into its landing offshore,” SpaceX’s Dan Huot said. The booster hovered over the Gulf of Mexico before its flight termination system triggered and it came down in the water.

Elon Musk said Saturday that the booster ran short on propellant because its engines slightly underperformed. The fix, he wrote, is better engine consistency with Raptor V3.2 and a flight software change to cut the engines “about one second earlier” so enough fuel is left for the return. “This booster loss does not change our timeline to reach high volume, fully reusable Starship flights,” Musk added.

Advertisement
-

The ship is the harder half of that goal, and the one SpaceX had never recovered. Super Heavy has now been caught three times, most recently in March 2025, while every previous ship ended in the ocean or was lost. Falcon 9 lands its boosters routinely but throws its upper stage away on every launch. Musk described a full Starship recovery on SpaceX’s third quarter earnings call as a “profound technology milestone,” and Saturday’s catch shows the hardest piece of it can work.

That piece matters for nearly everything SpaceX is planning. Reusable ships are what make the economics of launching Starlink V3 satellites at scale work, along with the Starmind orbital compute constellation. NASA’s Artemis lunar lander also depends on refilling Starships in orbit with repeated tanker flights, which requires vehicles that can fly again quickly. Musk has said he expects Starship to reach a weekly launch cadence in the first half of 2027.

Flight 15 also improved on the last Starship mission in September, which reached orbit but ended after about three hours with a Pacific splashdown when some engines shut down. Before this flight, SpaceX had shown an animation of the ship catch during its earnings webcast, and Musk put the odds of pulling it off on the first try at “more likely than not,” as Teslarati reported.

Continue Reading

News

Tesla Cybercab ownership will come with plenty of strings attached

Published

on

Credit: Tesla

Tesla’s long-promised Cybercab is finally available for personal purchase, at least for a select few in the Austin area. But it’s far from a straightforward ownership experience.

The $29,990 price tag comes with a stack of restrictions that redefine what “owning” the vehicle actually means. The two-seat, steering-wheel-free Robotaxi, previously limited to Tesla’s own fleet, now carries contractual terms that limit where it can go, how it can be used, and whether it can even move without an active paid subscription.

Opening Night of Orders

Late on November 13, Tesla announced that select customers were being invited to order a Cybercab for personal use.

Tesla Cybercab goes on sale for $29,990, slated for December deliveries

The estimated purchase price is $29,990 before taxes, paired with a non-refundable $1,000 deposit and an estimated December 2026 delivery in Austin, Texas. The first month of the required :Autonomy Subscription,” priced at $299 per month is included.

After that, the vehicle needs an active subscription to operate at all. The announcement confirmed that customer sales had begun, albeit on an invite-only basis rather than a public order page.

The Fine Print for Buyers

For those invited to order, the agreements (Cybercab Order Agreement, Terms of Use, and Autonomy Subscription Agreement) impose significant constraints. Major points include:

  • A mandatory Autonomy Subscription (currently listed at $299 per month on the order screen, first month included) is required; without it, the Cybercab will not operate.
  • Personal, non-commercial use only; ride-hailing, Robotaxi network participation, delivery, or rental requires separate written authorization or product enablement from Tesla.
  • Operation restricted to Tesla-enabled Robotaxi geofences and supported service areas, which the company can expand, shrink, or alter; the vehicle may be technologically prevented from operating outside them.
  • No unauthorized modifications (including wraps, window tint, or wheel changes) without Tesla or an authorized provider.
  • Restricted resale and transfer: written permission required, with contractual damages of at least $50,000 (or full transaction value if higher) for unauthorized sales; Tesla also reserves repurchase rights at a company-determined fair market value, with the owner covering return costs.
  • Safety or improper-use “strikeouts” (three or more) can trigger a one-week suspension of autonomous features without prorated refund.
  • Owners remain responsible for insurance, registration, charging, parking, and general cleaning; the subscription covers certain maintenance items such as tires, windshields, filters, and camera cleaning, plus limited towing.
  • Manual controls on the touchscreen allow only short-distance movement up to about 2 mph and require a valid driver’s license; they are not for public-road driving.

Why These Terms Might Exist

Tesla’s approach prioritizes control over a vehicle designed without traditional human controls and intended primarily as transport-as-a-service, something that Musk has hinted toward for some time now. Restricting commercial use and modifications could be as much of a software integrity, safety, and data collection effort as it is a safety effort.

Fleet consistency could also be in regulatory scrutiny early on in the Cybercab’s days of public operation.

The subscription model generates ongoing revenue beyond the low vehicle price and ensures the car remains connected and updatable, something that will keep the Cybercab as safe as possible as new updates roll out.

Buyback and resale limits reduce the risk of vehicles circulating outside Tesla’s operational and service ecosystem.

It apperas that personal ownership is secondary to the broader Robotaxi network strategy, as Musk has previously stated that the vast majority of Cybercabs would remain Tesla-owned.

Pickup Locations and Musk’s Pricing View

Initial deliveries are estimated for Austin, but personal vehicles are able to operate in any of Tesla’s Robotaxi geofences:

Those who have been invited to order can also have their personal Cybercab delivered to numerous locations in Texas, including:

  • Austin
  • Dallas
  • Houston
  • San Antonio
  • Fort Worth

As far as the monthly “Autonomy Subscription,” it appears Musk already wants it to be low. He acknowledged last night on X that the subscription price is too high. Along with detailing that the Cybercab will be available nationwide as regulatory approval is received, Musk said the monthly fee should match the cost of FSD and Premium Connectivity, which is about $115 per month.

The launch marks a milestone for unsupervised personal autonomous vehicles, but the fine print makes clear that buyers are purchasing a highly constrained asset whose usefulness is tightly bound to Tesla’s software, service network, and geographic approvals.

Continue Reading