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.
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 just doubled its Miami Robotaxi geofence
Tesla just doubled the serviceable area that its Robotaxi platform can travel in Miami, Florida.
On November 16, Tesla announced a major expansion of its Miami service area with a message stating that it would now service substantially more of the city. A new map shows the new service area, which is roughly double the initial geofence, including key urban districts into Robotaxi for the first time.
Miami’s geofence for Tesla Robotaxi has expanded considerably https://t.co/GpBqendVRN
— TESLARATI (@Teslarati) November 16, 2026
Tesla first launched unsupervised Robotaxi rides in Miami on July 3, making it the company’s initial market outside of Texas and California. The original geofence covered a very limited portion of the western Miami-Dade area, including West Miami, Doral, Sweetwater, and Miami International Airport. It was roughly 25 square miles, before a small expansion put it at about 31.
Now, Downtown Miami, the popular Brickell neighborhood, and Miami Beach, which were deliberately left outside the boundary initially, now are included in operations. Riders can now hail Model Y vehicles booked through the Tesla Robotaxi app and have run 24 hours a day since mid-November.
The map now looks to be about 59 square miles, a roughly 92 percent increase. The new eastern edge of the geofence now includes Downtown, Bickell, Wynwood, Little Havana, and the Biscayne Bay waterfront, nailing down a lot of typical tourist locations for Miami visitors. Additionally, the new geofence also extends North, reaching Hialeah, and adding coverage closer to the airport corridor.
At its widest, the zone now stretches roughly 11 miles from west to east. Miami Beach remains outside the service area, though Elon Musk previously indicated beach coverage was “coming soon” after Florida Governor Ron DeSantis publicly called for it.
Relative to Tesla’s other markets, Miami’s roughly 59-square-mile zone is now larger than Orlando (about 26 square miles) and Tampa (about 24 square miles) combined.
It remains smaller than Texas hubs such as Austin (around 443 square miles), San Antonio (about 275), Houston (about 254), and Fort Worth (about 143), but the rapid growth brings it closer to competitor Waymo’s approximately 60-square-mile Miami footprint, which already includes beach areas.
For Miami residents and visitors, the expansion makes driverless rides practical for trips into the city’s densest commercial and residential core, offering a new option amid heavy traffic and limited parking.
For Tesla, covering higher-demand downtown corridors should increase ride volume, generate more real-world autonomy data, and strengthen its competitive position as it scales the Robotaxi network toward broader profitability and eventual Cybercab deployment. The overnight growth also signals accelerating operational confidence less than five months after the city’s launch.
Cybertruck
Tesla tuner pleading to save Cybertruck also wants to build CyberSUV
Tesla tuner Unplugged Performance, the company pleading to save the Cybertruck, detailed in a new phase of its plan to rescue manufacturing lines from Gigafactory Texas that it would also build a three-row CyberSUV.
UP has already navigated a lot of the difficult thought work, including how it will woo Tesla to turn over the all-electric pickup’s production lines at no cost or risk to them. Tesla has signaled it will wind down Cybertruck output at Gigafactory Texas sometime around the middle of next year.
Unplugged, the Hawthorne-based aftermarket specialist that has tuned Teslas since 2013, first floated an open offer on November 10 and followed with a more specific “Phase 3” outline on November 15. Under the structure, outside investors would fund the new company.
82% of respondents want a three-row CyberSUV. The line to build it is about to be dismantled. Our proposal keeps it alive at no added cost to Tesla. Tesla keeps the IP, signs its first FSD license, and earns on every vehicle.
👇 https://t.co/y9y33EuLPr— UP (@UnpluggedTesla) November 15, 2026
The line would leave Giga Texas on Tesla’s schedule, supplier contracts would transfer, and Unplugged would hire its own staff, drawing from interested Tesla alumni, without pulling current Tesla employees or engineering resources.
Tesla would retain intellectual-property ownership, final say on specifications and brand, a quality veto, and an option to reclaim the line. In return, Tesla would collect a license fee on every vehicle plus margin on parts it continues to supply, Full Self-Driving and Robotaxi revenue, and a no-cost equity stake in the new entity.
If Unplugged cannot meet demand or capital targets Tesla sets, it would withdraw.
UP looked at the overwhelming demand for a full-size SUV, something that Tesla has had a lot of demand for but has not developed internally. A poll put out by the tuner that surveyed 892 responses showed 82 percent of voters favored a CyberSUV. There is a substantially deeper market for three-row SUVs priced above $80,000 compared to pickups.
Not to mention, the new body tooling plus limiting other changes from the Cybertruck line would enable the company to use the existing platform to produce an all-terrain family vehicle while continuing to produce Cybertruck builds at a modest incremental cost.
Tesla has already shown interest in a CyberSUV, as it hid Cybertruck-inspired clay models of what appeared to be a full-size SUV in a video last year:
The proposal from UP also contemplates multiple configurations that would enable owners to utilize a full-fledged Robotaxi in the form of a CyberSUV, aiming to build one with conventional controls for private buyers while a no-wheel/pedal version would be available for the Robotaxi fleet.
Tesla has made it clear that its manufacturing space and cell capacity is set aside for Cybercab, but UP already has soft commitments from a conglomeration of investors, but it all hinges on Tesla’s willingness to engage.
Elon Musk
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.
In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:
“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”
@apostlejohn @WorldlyReviewer Coming soon. If things well, may start trials next month.
Much better to manage a fleet of cars than have to drive just one car by yourself!
— Elon Musk (@elonmusk) November 16, 2026
The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.
This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.
Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.
December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.
Tesla Cybercab goes on sale for $29,990, slated for December deliveries
Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.
The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.
Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.
For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.
Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.
