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 Cybercabs take over Austin’s F1 weekend
Tesla Cybercabs swarmed Austin’s F1 Grand Prix as sightings hit a record during race weekend.
Tesla’s driverless Cybercabs used the Formula 1 United States Grand Prix in Austin as their biggest public stress test yet. On Sunday afternoon, Tesla head of AI software Ashok Elluswamy quoted a photo from X user Ben Steindl showing a long line of gold Cybercabs and Model Y Robotaxis stacked up on a road near Circuit of the Americas. “Robotaxis as far as the eye can see!” Elluswamy wrote. Steindl’s original post was more matter of fact: “@Tesla @robotaxi is busy for the Austin F1.”
The fleet also handled the trip home. The race started at 3 p.m. Central, and once it ended, Cybercab Spotter, an account that logs Cybercab sightings around Austin, posted that “People are requesting Cybercabs to get home.”
Robotaxis as far as the eye can see! 🤩
— Ashok Elluswamy (@aelluswamy) October 25, 2026
Tesla set this up days in advance without announcing it. Late on October 22, rider David Moss posted Robotaxi app screenshots showing the Austin service area wrapping around the track toward Elroy and FM 812, with ride requests open until 1 a.m. A banner in the app read “Last call is 1am · Limited to nearby dropoffs.” Austin rides ended at 11 p.m. as recently as early October, as Teslarati reported, before moving to midnight on October 17.
Not every rider got dropped at the gate. Early app searches showed spots like COTA Karting as “Service blocked,” and one rider who took a Cybercab to the track Friday said the rideshare area was less than a 20 minute walk from the front gate.
The weekend also produced a new activity record. Cybercab Spotter counted 1,250 Cybercab sightings in Austin on Saturday, qualifying day. The previous high was 1,072 on October 16. Sightings count the same car more than once, so they measure how busy the fleet is rather than how big it is. For size, the Texas automated vehicle registry listed 463 Cybercabs at midday Sunday, up from the 300+ Tesla claimed on October 10, when Elluswamy also said Dallas is next for Cybercab.
The track was out of reach for Tesla’s main rival. Waymo runs in Austin only through Uber, and its service area stops well short of COTA. Waymo did not announce any race day service.
Tesla has not said how many rides it gave to and from the circuit, or whether the expanded zone and 1 a.m. cutoff will stay after race weekend. On the third quarter earnings call, Elluswamy said 2 a.m. service is coming “pretty soon” and that Tesla plans to run Robotaxi around the clock before the end of the year. The company is also aiming to hand the first Cybercabs to customers before 2026 ends, which would put cars like these outside Tesla’s own fleet for the first time.
News
Tesla makes good on its Cybercab promise in just two weeks
Tesla Cybercab riders can now pull up a rear camera view and darken the screen.
Tesla has given Cybercab passengers a way to see what is behind them, along with a way to turn the cabin screen off entirely.
Riders in Austin can now bring up a live rearview camera feed on the Cybercab’s center display in the middle of a trip. Austin rider Ethan McKanna spotted the change late Friday night, posting from a ride that “You can now open the camera to view what’s behind you in Cybercab!” His photo shows a strip of rear camera video across the top of the screen, with another Cybercab following on a bridge. Sawyer Merritt shared the image Saturday and wrote that it “sounds like” there is also a new quiet mode that darkens the entire screen for riders who want to relax, sleep, or avoid a bright display at night.
The camera view goes beyond the rear feed. Tesla UI software engineer Evan, who posts as @CarCoder, replied to McKanna with a tip: “You can also tap it to see more cameras, and swipe it up or down to hide and show.” Until now, the Cybercab only showed its rear and repeater feeds on the “Please Exit Safely” screen at the end of a ride, so passengers could check for cyclists and traffic before opening a door.
Quiet mode surfaced a day earlier. Austin rider Jackson Blatz posted a video Friday morning of the new Robotaxi interface in a Cybercab with the option. Tesla has not published release notes for either feature.
The rear camera view moved quickly from request to release. Earlier this month, Cybercab rider Dan Burkland asked Tesla to let passengers pull up the rear and repeater cameras whenever they want, “especially for peace of mind.” Evan answered “In development,” as Teslarati reported at the time. About two weeks later, riders have it.
The feature fills a gap created by the Cybercab’s design. With no steering wheel, no pedals, no mirrors and no rear window, a passenger has no natural way to glance behind the car. The eight exterior cameras that feed Tesla’s autonomy software were already on board, so the change only required software.
There is also an AI angle to how it was built. Yun-Ta Tsai, a senior staff engineer on Tesla’s AI team, quoted Merritt’s post and wrote that the “(human) camera view tuning is optimized with Grok and implements part of the algorithm by directly programming the fixed-function hardware, so I don’t even need to check the datasheet.” Tsai did not say which part of the algorithm Grok handled. Grok already plays a bigger role inside the vehicle, with Grok Bot now enabled across every Cybercab and the Model Y Robotaxi fleet after Tesla brought the agent into its cars in September.
The two features join a busy week of changes for riders in Austin, which also brought a redesigned Live Activity for iPhone and Apple Watch and live trip sharing. They also arrive as Tesla prepares the Cybercab for life outside its own fleet. On the third quarter earnings call, Lars Moravy said the company is aiming to deliver Cybercabs to customers before the end of 2026. Tesla has not said whether the camera view and quiet mode will also come to its Model Y Robotaxis.
Elon Musk
Tesla shows what Roadster drivers will see on screen before thruster activation
Tesla’s Roadster video reveals a fighter jet inspired cockpit with a 5,500 PSI thruster gauge.
Tesla has given future owners their clearest look yet at the cockpit of its next generation Roadster. In a 34 second video posted to X on Friday afternoon, the company walked through the car’s touchscreen with a caption: “Inspired by fighter jet cockpits, Roadster’s interface was designed around the pilot.”
The clip opens on a black screen with red graphics and a 3D wireframe of the car, which sits beside the Roadster’s squared off yoke. Tapping parts of the model brings up controls for the rear wing, including low drag and high downforce positions, along with a charging page with a charge limit bar and a small music player. A row of tabs along the bottom reads Home, Vehicle, Listen, Climate and Navigate.
Most of the video is spent in Track Mode. The dashboard shows a live circuit map, a list of session lap times, brake and motor temperatures, and pressure and temperature readouts for each tire. A setup page lets the driver pick Auto, Low Drag, High Downforce or Custom aero modes, adjust aero balance and brake balance, and switch stability and traction control off. Along the bottom, a status bar reads “Thruster · 5,500 PSI” next to a “Boost Ready” indicator.
That gauge ties the software to the hardware Tesla showed off near Waco, Texas on October 15. The Thrust and Rocket versions use cold gas thrusters fed by carbon overwrapped pressure vessels, and Tesla lists 0 to 60 mph times of under 0.9 seconds and under 0.59 seconds for them, as Teslarati detailed in its breakdown of the three Roadster configurations. The base Performance car relies on a fan and ground sealing system for grip, and the aero settings on screen match the active wings and suction setup covered in our look at how the Roadster generates downforce.
The Roadster layout is a departure from the rest of Tesla’s lineup. Instead of a map centered screen, the Roadster puts the car itself at the center of the home page, and Tesla’s Roadster page lists two smaller forward displays alongside the main touchscreen. Tesla has not said whether any of the Track Mode telemetry will make its way to the Model 3 Performance or other vehicles.
The interface could still change before deliveries. Elon Musk said at the event that Roadster production will begin in 2028, and Tesla says the flagship Rocket version is not approved for public road use. Reservations are open with a $50,000 payment, while Thrust is listed as a limited release and Rocket is invite only.
Those who want to see the car in person will get their first chance this weekend. The Roadster goes on display in the lobby of the Petersen Automotive Museum in Los Angeles from October 24 to 27, according to Sawyer Merritt, the first time the public will be able to view it up close.
Tesla Cybercabs take over Austin’s F1 weekend
Tesla makes good on its Cybercab promise in just two weeks
