News
SpaceX’s repaired Starship booster survives back-to-back cryoproof tests
SpaceX’s upgraded Starship booster has completed a second and third cryogenic proof test in rapid succession after undergoing repairs to fix damage suffered during the first round of testing.
Testing began almost immediately after SpaceX rolled the repaired Super Heavy booster back to the orbital launch site (OLS) on May 6th. After a quick installation on the pad’s stool-like launch mount and another day of systems checks and integration, Booster 7 charged headfirst into its first post-repair cryoproof on May 9th.
Instead of cautiously feeling out the repaired plumbing and header tank over a series of small tests, SpaceX immediately performed a full cryogenic proof (cryoproof) and filled Booster 7 to the brim with about 3000 tons (~6.6M lb) of liquid nitrogen (LN2) or a combination of LN2 and liquid oxygen (LOx). Standing about 67 meters (~220 ft) tall and 9 meters (~30 ft) wide, it took about two hours to fully fill Super Heavy’s tanks with the equivalent of one and a half Olympic swimming pools of cryogenic liquid.
As always, that liquid (well below –320°F or –196°C) rapidly chilled the booster’s 4mm (~0.16″) thick steel tanks to cryogenic temperatures, which then froze moisture directly out of the humid Texas air, coating almost all of Super Heavy’s exterior with a layer of frost and ice.
SpaceX began detanking Booster 7 soon after the fill process was completed. Thanks to plenty of insulated plumbing and well-insulated ground storage tanks, SpaceX is able to recover nearly all of the LN2 and LOx used during cryoproof testing, which helps avoid the hundreds of semi-truck delivers that would otherwise be required to replenish the tank farm after even a single test.
As if to demonstrate that, SpaceX proceeded to put Booster 7 through a whole new cryogenic proof test just two days later, on May 11th. Once again, Super Heavy was fully loaded with thousands of tons of liquid nitrogen and oxygen. Unlike Cryoproof #2’s immediate detank, SpaceX – judging by the frost levels – kept Booster 7 topped off for a good hour before detanking.
In a last-minute surprise, after fully detanking B7 at the end of Cryoproof #3, SpaceX refilled the booster’s liquid oxygen tank with a few hundred tons of LN2 or LOx. Once the rocket’s thrust section reached some degree of thermodynamic equilibrium, SpaceX remotely retracted and reconnected the orbital launch mount’s Super Heavy umbilical. The launch mount umbilical or ‘quick disconnect’ is responsible for connecting Super Heavy to the pad’s gas supplies, propellant storage, power, and communications. The test SpaceX completed after Cryoproof #3 may have been a rough simulation of one scenario Starship could easily face: a post-ignition launch abort. In other words, if an orbital Starship launch was aborted just before liftoff but after quick-disconnect retraction, could it quickly reconnect to the booster with zero human intervention?
In a scenario where a QD failed to reattach to a fully-fueled Super Heavy after a launch abort, the odds of a catastrophic fire or explosion would immediately shoot up to near-certainty. In moderate quantities, simultaneously venting gaseous methane and oxygen from the same rocket is risky but manageable. Venting hundreds – let alone thousands – of tons while trapped on the ground would amount to creating a multi-hour fuel-air bomb just waiting for a spark. Multiple Starship prototypes (SN4, SN10) have already been destroyed in part by the flammability of methane gas.
Combined with the completion of two full cryogenic proof tests in less than two days, it appears that Super Heavy B7’s repairs were extremely successful. Had the first post-repair cryoproof not gone more or less perfectly, it’s hard to imagine that SpaceX would have attempted or completed an almost identical test two days later. If the second cryoproof hadn’t been nearly perfect, it’s even harder to imagine that SpaceX would have accepted the risk involved in detaching Booster 7’s umbilical during the same test window.
On May 12th, SpaceX’s main pad crane attached a lift jig to Super Heavy B7, implying that it will likely be removed from the orbital launch mount in the near future. If the repaired booster aced its tests, SpaceX’s next step would likely be Raptor engine installation and the start of static fire testing. It’s unclear if SpaceX wants to install all 33 engines at once or begin with a small handful. It’s also unclear if SpaceX will return Booster 7 to Starbase’s production facilities to finish Raptor, heat shield, grid fin, and aerocover installation.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
