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.
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.
News
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.
SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.
A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.
Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.
Launch rehearsal complete ahead of Starship Flight 14 pic.twitter.com/h5LBYyBqi4
— SpaceX (@SpaceX) September 24, 2026
Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.
Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.
The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.
Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”
Elon Musk
Google just picked SpaceX for its first step into orbital AI
Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.
Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.
The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.
The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.
MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.
SpaceX and Google mull massive partnership on Musk’s orbital data dream: report
Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.
The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.
Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”
Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.
Tesla Full Self-Driving release in the EU gets delayed
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
