News
SpaceX making good progress towards Super Heavy static fire campaign
SpaceX appears to be making great progress towards the start of its first full Super Heavy static fire campaign, building upon extensive Starship testing and a single booster static fire completed in July 2021.
On May 14th, upgraded Super Heavy booster B7 was moved back to SpaceX’s South Texas Starbase Starship factory after completing a successful round of tests and smoothing out an otherwise rocky start to its life. It was not the booster’s first time on that journey: after first leaving the Starbase ‘nest’ on March 31st, Booster 7 suffered significant internal damage during a structural stress test on April 14th and was forced to return to the factory for repairs. Impressively, despite the cramped environment and extremely limited access to the interior of the Super Heavy’s primary and secondary propellant tanks, SpaceX engineers and technicians somehow completed those repairs and Booster 7 sailed through a new round of ‘cryoproof’ testing on May 9th and 11th.
In the ~20 days since its second return, SpaceX teams have been hard at work preparing Super Heavy B7 for its next major challenges – the results of which could determine whether the massive rocket helps launch a Starship into space later this year.
That goal, same as it has been for half a year, is to qualify the first Super Heavy booster for flight. To do so, SpaceX must – at long last – static fire a Super Heavy with all necessary Raptor engines installed. For Booster 7 and its near-term successors, that means 33 new “Raptor 2” engines capable of generating a total of ~7600 metric tons (~16.7M lbf) of thrust.
That’s exactly what SpaceX workers have been focused on doing since Booster 7’s second return to a Starbase assembly bay. Bit by bit, they have spent every day since installing Raptor 2 engines one at a time. Unfortunately, due to the Super Heavy’s relocation inside a brand new assembly building known as the Megabay, High Bay 2, or Wide Bay, the half-dozen or so unaffiliated photographers who have come to regularly photograph Starbase have yet to find an angle that shows the state of that engine installation progress.
Two weeks later, it’s clear that SpaceX is taking its time, which likely also implies that the company is simultaneously encasing Booster 7’s Raptors and engine section in shrouds that will protect them during static fire testing; as well as during launch, reentry, and landing if B7 makes it that far. That’s not guaranteed, however, and it could also simply be that installing 33 engines on the first attempt at installing any Raptor 2s on any rocket has proven much harder than expected.
On June 1st, CEO Elon Musk appeared to confirm that engines are still being installed on Super Heavy B7, but he also verified that “all Raptor 2 engines needed for [the] first orbital flight are complete.” That could include Starship S24, which needs three sea-level Raptor 2s and three vacuum-optimized Raptor 2s, but it’s still great news even if he only means it for Booster 7. SpaceX has been spotted delivering at least a handful of new Raptor 2 engines a week for the last month or two, which means that all 33 engines may already be onsite at Starbase. If some are still undergoing proof testing at SpaceX’s McGregor, Texas facilities, it could be a few more weeks before all necessary engines are onsite, but that milestone is likely close at hand if it hasn’t already been reached.
For Super Heavy Booster 4, which was inexplicably never static-fired, installation of all 29 of its Raptor 1 engines took just a few days, but the installation of a heat shield around those engines took at least a few weeks. On June 1st, SpaceX also began installing grid fins on Super Heavy B7, further indicating the company’s growing confidence in the booster.
Outside of booster outfitting, SpaceX has also been aggressively refilling the Starbase orbital launch site’s (OLS) massive tank farm, which is capable of storing, subcooling, and distributing thousands of tons of liquid oxygen (LOx), liquid methane (LCH4), liquid nitrogen (LN2), and a variety of gases. For a full wet dress rehearsal (WDR), which has also never been done with Super Heavy, SpaceX would need to fill the booster with around 3400 tons (7.5M lb) of propellant. Out of an abundance of caution, Super Heavy B7 will likely have far less propellant aboard during almost all of its static fire tests, but a full static fire with a full load of propellant – simulating most prelaunch conditions – will likely be one of the last main goals of any static fire campaign. At full thrust, 33 Raptor 2 engines will likely burn around 25 tons (~55,000 lb) of propellant per second, so a huge amount of propellant will be needed regardless.
In the same series of June 1st tweets, Musk also confirmed that SpaceX intends to proceed cautiously into its first true Super Heavy static fire campaign, testing engines “just one at a time at first.” Musk probably isn’t being literal, as a campaign in which Booster 7 tested every one of its 33 Raptors individually could easily take weeks, so it’s likely safe to interpret his words to mean that SpaceX is not going to leap straight from the first limited test of one or a few engines to all 13 center engines, all 20 outer ‘boost’ engines, or all 33 engines at once.
Almost three weeks into the process of engine and heat shield installation, Booster 7 could potentially be ready to return to the orbital launch site any day now, though there’s probably an equal chance that it’s still a few weeks away. Nonetheless, SpaceX is on the cusp of kicking off one of the most exciting and important test campaigns in the history of Starship.
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.