News
SpaceX Super Heavy booster returns to launch pad after major repairs
SpaceX has returned its newest Super Heavy to Starbase’s orbital launch site (OLS) after rapidly repairing damage the booster suffered during its first round of testing.
Super Heavy Booster 7 (B7) left the High Bay it was assembled in for the first time on March 31st and rolled a few miles down the road to nearby Starship launch and test facilities on a set of self-propelled mobile transporters (SPMTs). On April 2nd, the roughly 67-meter-tall (~220 ft; 69m w/ Raptors) rocket was installed on top of Starbase’s lone orbital launch mount (OLM), setting the stage for crucial qualification testing.
The start of that process was exceptionally successful. On April 4th, after a smooth launch mount installation, SpaceX quickly filled Booster 7’s propellant tanks with a relatively benign cryogenic fluid (liquid nitrogen, liquid oxygen, or both) to simulate the thermal and mechanical characteristics of real flammable propellant. Despite the fact that the test marked the first time SpaceX had fully filled a Super Heavy prototype’s tanks, Booster 7 sailed through the ‘cryoproof’ without any obvious issue.
On April 8th, SpaceX moved Super Heavy B7 from the orbital launch mount to a structural test stand that had been installed and modified just a few hundred feet away in the weeks prior. This is where Booster 7’s near-perfect start to qualification testing took a bit of a turn. Booster 7 is only the third full-size Super Heavy prototype SpaceX has tested since July 2021. Like Booster 3 and Booster 4 before it, Booster 7 features some major design changes that ultimately make the prototype a pathfinder, necessitating extensive qualification testing.
To name just a few of the changes, Super Heavy B7 is the first booster fitted with a 33-engine puck and the first finished Starship prototype of any kind designed to use new Raptor V2 engines. With all 33 engines installed and operating a full thrust, Booster 7’s entire structure – and its aft thrust section especially – would be subjected to around 40% more thrust and stress than Booster 4, which indirectly completed structural testing with the help of a sacrificial test tank. Beyond differences in thrust and mechanical stress, Booster 7 is also the first Super Heavy to reach the test stand with secondary ‘header’ tanks meant to store landing propellant.
It’s unclear if those header tanks were fully filled and drained during Booster 7’s cryoproof, but they would not be quite as cooperative during a different kind of cryogenic testing on the structural test stand. The stand SpaceX modified specifically for Super Heavy B7 was outfitted with 13 hydraulic rams to simulate the full thrust of the booster’s central Raptor V2 engines – up to almost 3000 tons (~6.6M lbf) compared to Booster 4’s ~1700 tons (~3.7M lbf) with a smaller cluster of nine engines.
Implosion at the Structural Test Stand
After a few false starts and minor tests on the stand, Booster 7 finally managed some significant testing on April 14th. Judging by the rhythmic shattering of ice that built up on Super Heavy’s tanks, the test stand was able to simulate the thrust of Raptors to some degree and subject the booster to major mechanical stress that was felt from tip to tail. Within a few days, Booster 7 was removed from the test stand and returned to the high bay on April 18th. Around April 21st or 22nd, an image was leaked showing extensive damage inside Booster 7, confirming that the Super Heavy’s test campaign had been forced to end prematurely.

Right away, the damage shown in the photo hinted at an operational failure, meaning that mistakes made by the rocket’s operators may have been more to blame than a possible design flaw. The photo shows a short portion of B7’s liquid methane (LCH4) transfer tube that runs through the booster’s new liquid oxygen (LOx) header tank, which itself sits inside Super Heavy’s main LOx tank at the aft end of the rocket – a tube inside a small tank inside a large tank, in other words. Super Heavy’s LCH4 transfer tube generally does what it says, allowing methane to safely fly down through the main LOx tank and fuel up to 33 Raptor engines. At full thrust, that tube would need to supply around 20 tons (~45,000 lb) of methane per second.
However, on top of merely transferring methane through the oxygen tank, Booster 7 introduced a design change that allows some or all of that tube to change functions and become a header tank mid-flight. That would require a system of valves that could seal off the main LCH4 tank once it was emptied, turning the transfer tube into a sort of giant steel straw filled with enough LCH4 to fuel Super Heavy’s boost-back and landing burns.
The damaged transfer tube in the leaked photo of Booster 7 doesn’t look that unlike what one might expect to see if they sucked through one end of a straw while blocking the other end, collapsing the center. Translated to the scale of Super Heavy, after an otherwise successful day of structural testing, SpaceX operators may have accidentally closed or opened the wrong valves while draining the booster’s transfer tube of liquid oxygen or nitrogen. As the heavy liquid drained from the tube, a lack of pressure equalization could have quickly drawn a vacuum and caused the tube to implode.
On April 29th, a SpaceX fan turned analyst published an analysis that convincingly pinpointed the moment Booster 7’s transfer tube collapsed. Simultaneously, because it showed that the transfer tube likely imploded during detanking, the analysis more or less confirmed the above speculation that the failure had been caused by a degree of operator error or poor test design. Of course, it’s possible that a hardware or software design flaw contributed to or caused the anomaly or that something like a pressure differential in the LOx header tank and LCH4 header tube could also explain the damage, but the accidental formation of a vacuum during detanking is arguably the simplest (obvious) explanation.
After the image of the internal damage leaked, the immediate consensus among fans and close followers was that Booster 7 was beyond repair. Instead, SpaceX appears to have proven those assumptions wrong and somehow managed to repair the upgraded Super Heavy to the point that it was worth testing again less than three weeks after returning to the high bay. On May 6th, B7 was rolled back to the launch site and installed, for the second time, on the orbital launch mount.
Prior to the failure, the general expectation was that SpaceX would begin installing Raptor V2 engines as soon as Booster 7 passed structural testing. It remains to be seen if SpaceX wants to repeat Booster 7’s cryoproof or structural testing to ensure that its quick repairs did the job before proceeding into static fire testing as previously planned. Nonetheless, hope lives on for the Super Heavy prototype and new test windows have been scheduled from 10am to 10pm on May 9th, 10th, and 11th.
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.
Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.
When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer
The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.
All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.
The scale and consistency of the installation point to factory tooling rather than retrofit work.
A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.
Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.
It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.