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)

Advertisement
-

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.

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.

Advertisement
-

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
TESLARATI MARKETPLACE LIMITED-TIME OFFER

Give the gift of Tesla upgrades.

Shop for someone else or treat yourself. Get more shopping power with a Teslarati gift card.

YOU PAY $250
+
FREE BONUS $75
$325 TOTAL VALUE
Digital gift card delivered by email. Promotional terms apply.
View gift card details →
Comments

Elon Musk

Tesla Full Self-Driving v15 rollout begins: full release notes and improvements

Published

on

Tesla Reality View with FSD v15 (Credit: Tesla)

Tesla has announced that Full Self-Driving version 15 is now rolling out, after CEO Elon Musk said earlier today that the wide rollout would occur in December.

Now, Tesla is rolling out to Early Access Program (EAP) members v15’s first builds, and there are a lot of new improvements.

Tesla explicitly stated that safety improvements come in the form of “25x better handling of safety critical cases.” It is also rolling out “Tesla Reality View,” a new version of the Driver Visualization that appears to be much more realistic and could potential use Unreal Engine, according to the teaser video Tesla posted on social media. This “adds a live visualization of the drive that lets you see & control what FSD is planning to do.”

Perhaps the biggest improvements that Tesla mentioned, however, are that of Navigation fixes and better detection and aversion from potholes, debris, and animals, as well as “more natural speed handling in school zones and inclement weather.”

Tesla also added a new “Bike Rack Mode,” which will enable FSD’s use when bike racks or other hitch accessories are attached.

Tesla also revealed the full Release Notes for v15:

  • Upgraded vision encoder shared between FSD, Robotaxi, and Optimus, which is trained on millions of internet videos for improved generalization and data efficiency, improving the critical intervention rate by 25x.
  • Introduced Tesla Augmented Reality, replacing all of the explicit model signals into a single end-to-end visualization using less total compute.
  • Improved navigation by using an end-to-end learned model based on route preference data from the fleet.
  • Improved parking location selection by using personalized parking history, and the map will now display multiple parking options at your destination.
  • Improved driver monitoring by increasing vision-based attention monitoring availability with hats and sunglasses and decreasing strictness in higher speed driver profiles.
  • Improved detection of road signs, small animals, road debris, and chains.
  • Improved detection of potholes, road details, and avoidance of deep standing water.
  • Improved speed handling for each driver profile, school zones and speed limits, and inclement weather.
  • Improved Autoshift functionality by unifying with FSD-based gear predictions.
  • Tesla Reality View New: real-time generative driving visualization that continuously streams a view from an arbitrary virtual camera situated above your vehicle, enabling you to see and control what FSD is planning to do. Select between fullscreen visualizations, maps or a split view – or choose quiet mode for a calming cabin experience. Upcoming navigation turns display directly in the driving visualization. Turn signals are quieter and fade out after a few clicks.
  • Speed Camera Slowdown: FSD (Supervised) can now slow down when it detects a speed camera. Press the accelerator or increase your speed profile to cancel the slowdown. If you cancel twice at the same camera, your Tesla saves that location and will not slow down there again. To remove saved cameras, go to Controls > Service > Manage Saved Locations.
  • Bike Rack Mode With Bike Rack Mode, you can now engage FSD (Supervised) when a bike rack or similar hitch accessory is installed. When Bike Rack Mode is enabled, FSD (Supervised) pulls over near your destination and does not reverse. Autopark, Summon, and Backup chimes and warnings will be disabled.

It sounds like there are some really great improvements, and this is probably just a handful of what other improvements will come from these upgrades. For example, the UI changes will likely come with some other features that will be discovered upon the public having hands-on experience with it.

Musk said this morning that a wide release would occur sometime in December.

We’re looking forward to testing it when it arrives to us!

Continue Reading

Elon Musk

Tesla Full Self-Driving v15 gets release date from Elon Musk

Published

on

Tesla Full Self-Driving v15 has received an official release date from CEO Elon Musk, who says the newest and most capable version of the suite will go wide in December with the 2026 Holiday Update.

That means the first iterations of the suite could actually come sooner, as the Early Access Program is the initial batch of owners to receive a new FSD release. Musk’s comments released a few tidbits of information, but nothing overwhelmingly revealing about its capabilities.

Musk was talking about supervised fine-tuning, stating that it is like “getting a haircut with a chainsaw,” before stating that FSD v15 will roll out wide for owners next month:

Musk’s Confirmed Changes and Fixes

Musk simply confirmed the new Full Self-Driving version would roll out with the 2026 Holiday Update, and the only two explicit changes he confirmed were updates to the User Interface (UI) and two small changes.

Musk’s comments on the UI confirm there are big changes coming to it, as he stated:

The UI changes will likely upgrade AMD Ryzen-equipped Tesla vehicles running AI4 to visualize vehicles using the Unreal Engine, something that was found in coding last year:

Tesla plans to use Unreal Engine for driver visualization with crazy upgrade

Additionally, one user stated that their biggest complaints with v14’s most recent releases is that they have to “stop refusing to use the HOV lane” and last-second lane changes to merge or turn happen too frequently. Musk said these should be fixed in v15.

In the past, we’ve also gotten small bits of detail about the v15 release, including from Tesla’s Head of AI, Ashok Elluswamy, who stated back in September that there are improved safety and collision avoidance systems coming with the v15 release.

Tesla plans big safety improvements for Full Self-Driving v15

The big prediction for v15 is whether this will enable at least some unsupervised driving in personal Teslas. There are likely to be some massive jumps in capability, although FSD has already proven itself to be a great way to travel. Nevertheless, there are a lot of things it could do better.

FSD still struggles with parking, it has routine bugs from update to update, it does not recognize potholes or large bumps on the road, speed control is a common complaint, and Navigation has been one of the biggest pain points.

However, v15 will likely bring massive improvements to capability and give people more options, like potentially parking orientation and more refined spot selection. We can only wait and see what Tesla will include.

Continue Reading

News

Tesla Assisted Driving (TAD) lands approval in Italy, its 12th EU country

Published

on

Credit: Tesla

Tesla Assisted Driving (TAD), the European equivalent of the Full Self-Driving suite in the U.S., has officially landed approval to operate in Italy, the 12th European Union country to allow the suite.

Italy marks a huge accomplishment for Tesla’s approval processes in Europe, as it marks the first truly major European country to give an approval.

On November 20, Italy’s Ministry of Transport granted provisional type-approval for Tesla Assisted Driving (TAD), the company’s advanced driver-assistance system. Transport Minister Matteo Salvini announced the decision on X, describing it as “another step forward toward innovation, technology and the mobility of the future, whilst always prioritising public safety.”

The approval followed a thorough technical feasibility assessment and positions Italy as the twelfth European country to authorize the technology, but the first among the European Union’s largest markets.

TAD, previously marketed as FSD (Supervised), will roll out in Italy shortly through an Over-the-Air update and will be available on a subscription basis at €99 per month.

This Italian green light carries substantially greater weight than the preceding approvals. The system first received provisional type-approval from the Netherlands’ RDW in April. Subsequent recognitions came primarily from smaller countries, like Lithuania, Denmark, Belgium, Croatia, Finland, and others.

Italy, by contrast, is the Union’s third-most populous member state and one of the traditional “big four” alongside Germany, France, and Spain. Its urban environments are particularly dense and present a more demanding real-world test for the system than many earlier markets.

The approval also follows a late-October conversation between Elon Musk and Salvini, after which the minister publicly supported a swift EU-level decision. Full bloc-wide authorization requires a qualified majority of at least 15 member states representing 65 percent of the EU population. Italy’s move adds meaningful population weight and political momentum ahead of potential discussions in the Technical Committee on Motor Vehicles.

Tesla marked the occasion with a video of a vehicle navigating Roman streets near the Colosseum, underscoring the system’s ability to handle the city’s distinctive traffic patterns.

For Tesla, the Italian authorization represents a strategic foothold in a major European car market, potentially accelerating both customer adoption and the case for broader regulatory acceptance across the continent.

Continue Reading