News
SpaceX tests Starship and Frankenstein ‘test tank’ simultaneously
After another few weeks of downtime, SpaceX has simultaneously tested the first orbital-class Starship prototype and a Frankenstein-esque ‘test tank’ at its South Texas facilities. While nothing that occurred was all that visually spectacular, the afternoon of testing was still noteworthy for a couple of reasons.
First up, following a successful six-engine Raptor static fire – the first in Starbase history – on November 12th, all signs pointed to Starship S20 attempting another static fire (its fourth) on December 1st. In the almost three weeks of inactivity between those planned tests, SpaceX likely performed extensive inspections of the pathfinder prototype and its Raptor engines. Technicians also repaired the minor heat shield damage and tile loss that testing incurred and patched a few other ‘holes’, effectively leaving Ship 20 with the first fully finished heat shield by the end of November.
Earlier this week, one of the few remaining Boca Chica Village residents received a safety notice from SpaceX indicating that a static fire test was scheduled on Wednesday, December 1st – followed soon after by a notice to mariners (NOTAM) warning boaters to keep to a safe distance. Two hours into the 10am to 6pm CST test window, Starship S20 was already venting and starting to get frosty, confirming that propellant loading had begun. A little over an hour later, it was clear that SpaceX had aborted the first static fire attempt of the day. For the next three hours, Ship 20 exhibited some unusual behavior including new vents, an apparent header tank pressurization or fill test, and still more odd venting in new places.
In the middle of Starship’s weird nose-related testing, SpaceX began simultaneously loading a new ‘test tank’ known as B2.1 with liquid nitrogen (LN2) – marking the first truly simultaneous test of multiple Starship test articles. As Ship 20 seemingly detanked for the second time that day, the B2.1 tank was fully loaded with LN2 and apparently pressure-tested not long after. A few hours later, the test tank was also detanked and the road to the pad was reopened, marking the end of the day’s testing.
Normally, nothing is particularly unusual or noteworthy about test tank testing. Since January 2020, SpaceX has routinely built and tested tanks that are effectively just shorter versions of actual tanks and hardware, using them to qualify changes to Starship’s design, materials, operations, and more before applying those changes to full-size prototypes. B2.1 is the tenth dedicated test tank to reach the launch pad in a little under two years.
Normally, the ‘B2.1’ name SpaceX has given the tank would imply that it’s a newer booster test tank (using Bx instead of BNx) following in the footsteps of BN2.1, which passed cryogenic and load testing this summer. Instead, though, B2.1 is a bit of a nightmarish amalgamation of seemingly random Starship and Super Heavy parts. Its forward dome is an old, unused booster section complete with the hexagonal structure grid fins would have been brace against. Its aft section is a booster thrust structure. Up to that point, it’s effectively just a copy of BN2.1.
However, SpaceX inexplicably installed a Starship thrust dome inside B2.1’s booster thrust structure, creating a test tank with no obvious relevance to any conceivable Starship or Super Heavy design or prototype. Further, SpaceX rolled B2.1 to the launch site for testing only after installing it on an unused device that’s believed to be the aft half of a dedicated booster structural test stand. In theory, a sort of ‘cap’ would be fitted on top of a booster or test tank installed in the stand’s base and strong cables would connect the two, allowing SpaceX to subject prototypes to compressive stress – like, perhaps, the forces a booster might experience while carrying a fully-fueled 1300-ton Starship to space. The upper half of that test structure has yet to be moved to the launch site.
Altogether, the weird half-complete test stand and bizarre fusion of ship and booster parts make B2.1’s purpose and initial testing a complete mystery. It’s unclear what value it provides that makes it more of a priority than, say, finally starting to test the first flightworthy Super Heavy booster (B4). Ultimately, the most interesting thing about B2.1’s test debut is the fact that it appears to mark the first use of Starbase’s brand new orbital tank farm, which is approaching completion.
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
