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
Tesla surges Robotaxi fleet ahead of Cybercab launch event
Tesla’s unsupervised robotaxi fleet quietly grew sevenfold in three weeks just before Cybercab Day arrives.
Tesla’s unsupervised Robotaxi fleet has grown far faster than the public numbers suggested, and the timing lines up with the company’s biggest autonomy showcase yet. According to data compiled by the crowdsourced Robotaxi Tracker, Tesla now has nearly 200 vehicles operating without a safety monitor across Austin, Dallas and Houston, yielding a roughly 7X increase in about three weeks.
The jump lands four days before this week’s Tesla Cybercab launch event in Austin, where the company plans to show off its purpose-built, two-seat robotaxi with no steering wheel or pedals in a live commercial setting for the first time. Stick with us on X and Facebook for live reporting from the event.
The strategic logic is straightforward. Tesla has spent the past year scaling Robotaxi in small, deliberate steps, first widening geofences, then extending operating hours, then quietly growing fleet size, usually with little advance notice. Ashok Elluswamy told investors on the Q2 earnings call that the program had logged more than 380,000 unsupervised miles with zero notable incidents, a safety record the company has leaned on to justify moving slowly. Critics have used the flip side of that caution, a fleet that appeared stuck around two dozen vehicles for months, as evidence that Tesla’s driverless ambitions were outrunning its actual deployment.
A fleet quietly scaling to nearly 200 vehicles right before Cybercab Day undercuts that argument without Tesla having to say anything about it directly. It also sets up the event to do double duty. Rather than simply introducing new hardware, Tesla can point to an operating base of unsupervised Model Ys already running at meaningful scale, then argue the Cybercab, which uses the same underlying Full Self-Driving stack according to earlier coverage of the fleet’s software upgrades, is a natural next steps. Tesla has separately been registering the two-seat Cybercabs with Texas regulators this week, with the count climbing from seven to 45 in a matter of days.
The two ramps, one in software-driven Model Y deployment and one in physical Cybercab registrations, are happening in parallel rather than in sequence. That suggests Tesla wants Thursday’s event to land as proof that the robotaxi business is already running at scale, not just a reveal of a new vehicle shape. Whether the unsupervised numbers hold up once Cybercabs start mixing into the same fleet is the detail worth watching once the event wraps.
Tesla is lowering the monthly price of its Cybertruck Windshield Protection Plan from $35 to $25. The new rate will apply to the first payment on or after October 1, 2026. Tesla has told subscribers that all other benefits stay the same.
The plan covers unlimited repairs for chips and minor cracks on the front windshield. It also includes one full replacement every 12 months at no extra charge. Additional replacements in the same year carry a $100 deductible. Service is performed with Tesla glass and camera calibration, which matters because Autopilot and Full Self-Driving rely on those lenses behind the windshield.
Looks like Tesla is decreasing the Cybertruck windshield protection plan price from $35 to $25
Awesome https://t.co/MRlTU1XTbf pic.twitter.com/PWkMZt1H7G
— TESLARATI (@Teslarati) August 28, 2026
There is no long-term contract. Coverage applies only to the front glass and does not include collision, vandalism, or weather damage.
The Cybertruck’s large, complex windshield has been more expensive to replace than glass on Tesla’s cars, which is why the pickup started at a higher subscription price. The $10 monthly cut reduces the annual cost from $420 to $300. Tesla has not publicly explained the change. The timing coincides with a year of claims data after the plan was extended to the Cybertruck.
Tesla sells several related protection products as monthly subscriptions through the Tesla app. The Windshield Protection Plan is also offered on other models. Model 3 and Model Y currently cost $16 a month. Those passenger-car rates are unchanged in the latest Cybertruck notice.
The Wheel and Tire Protection Plan covers road-hazard damage such as potholes, nails, and debris. Repairs are unlimited. Each wheel or tire replacement appointment has a $25 deductible. Pricing varies by model and whether the vehicle is a Performance version. Tesla is raising some of those rates on the same October 1 date.
Reported examples include Model 3 Performance moving from $16 to $24 and Model Y Performance from $20 to $24. Cybertruck wheel-and-tire coverage has been listed at $20 a month for the standard configuration.
A separate Luxe Package bundles four years of windshield coverage, wheel-and-tire coverage, and recommended maintenance on certain new Model S, Model X, and Cyberbeast orders, although the Model S and X are now defunct.
Tesla also offers an Extended Service Agreement after the basic vehicle warranty ends. That product covers many Tesla-manufactured parts rather than glass or tires. Together, the plans give owners a menu of targeted, cancel-anytime coverage instead of relying only on auto insurance.
UPDATE: The number has now been updated to 45 units, up from 7!
Here we go! Tesla has just added another 38 Cybercabs to its Robotaxi fleet, bringing the total up to 45, according to the Texas DMV.
Robots on robots on robots! This Thursday’s launch event is gonna be awesome🤖🤖🤖 pic.twitter.com/3HF24rHK4T
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.
Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.
The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.
Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:
🚨 There are now SEVEN Tesla Cybercabs registered with the state of Texas
We are just three days from Cybercab! pic.twitter.com/ndwhuFYsep
— TESLARATI (@Teslarati) August 31, 2026
Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.
Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.
The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.
Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.
The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.
Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.
Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.
Tesla surges Robotaxi fleet ahead of Cybercab launch event
Tesla Cybertruck windshield protection just got cheaper
