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
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.
SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.
Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.
Watch Falcon 9 launch the USSF-385 mission from pad 4E in California https://t.co/CAdbx85Ydy
— SpaceX (@SpaceX) September 26, 2026
USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.
The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.
Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.
The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.
News
Tesla hints at new Roadster design in surprise clip
Tesla ended its Semi event with a Roadster teaser revealing a new front light bar.
Tesla closed out its Semi event in Nevada on Thursday night with a nod to its own history, dropping a short Roadster teaser that suggests the production car will look noticeably different from the prototype first shown in 2017.
“We can’t have a Semi event without the Roadster,” Tesla engineering executive Lars Moravy told the crowd before the clip played. The line was a deliberate callback. Tesla first revealed the next generation Roadster in November 2017 by driving it out of the back of a Semi trailer at the truck’s original unveiling in Hawthorne, California.
The new video opens on trailer doors swinging apart in the dark. A thin white light bar glows across what appears to be the nose of the car, Tesla and SpaceX logos flash over the frame, and the Roadster name appears before the clip ends on “See you next week.” Tesla posted the nine second clip on X after the livestream wrapped.
See you next week pic.twitter.com/BT52bGVxFu
— Tesla (@Tesla) September 25, 2026
The light bar is the most concrete design detail so far. The 2017 prototype used two separate curved headlamp pods, while a connected front light strip would bring the Roadster in line with the Cybertruck, Cybercab, Semi, and refreshed Model Y. Sawyer Merritt was among the first to point out what looked like part of a SpaceX logo in the video, something Tesla has not addressed.
That logo fits the buildup around the optional SpaceX Package, which Elon Musk has long said would use cold gas thrusters to improve acceleration and possibly allow the car to briefly leave the ground. Tesla’s “Go for launch” post on September 12 set the October 1 date, and invitations sent to reservation holders place the event in Waco, Texas, at 8:30 p.m. Eastern. Waco sits roughly 20 minutes from SpaceX’s McGregor rocket test site, where the FAA has put a temporary flight restriction in place from September 18 through October 2, covering a 1.5 nautical mile radius from the surface up to 10,000 feet.
Tesla is also taking money ahead of the reveal. The company reopened Roadster reservations earlier this week with a $5,000 refundable card payment, followed by a $45,000 wire transfer due within 10 days. That puts buyers at $50,000 committed before Tesla has published a price.
The original pitch set a high bar: 0 to 60 mph in 1.9 seconds before any upgrades, 620 miles of range, a top speed above 250 mph, and production in 2020. That timeline has slipped repeatedly, and Tesla has since pointed to production at Gigafactory Texas no earlier than 2027. The company has said next Thursday’s event will include pricing, specifications, and production targets, the three details original reservation holders have been waiting on for nearly nine years.
News
Tesla Full Self-Driving release in the EU gets delayed
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.