News
SpaceX shuffles Starships, gears up for more Super Heavy static fires
SpaceX is busy preparing for the orbital launch debut its next-generation Starship rocket, but the company’s South Texas rocket factory is also working around the clock to prepare several more sets of ships and boosters for the flight testing that will follow.
That was more obvious than usual on November 8th, when SpaceX made moves to prepare both of its finished Starships for new phases of testing. SpaceX kicked off the busy day by removing Starship S25 – a newer prototype that arrived at the launch site just three weeks prior – a stand dedicated to proof testing ships. Three hours later, after spending three of the last four weeks sitting on top of Super Heavy Booster 7, Starship S24 was ‘destacked’ (lifted off of B7 and lowered onto a stand on the ground) in the early afternoon.
Booster 7, Ship 24, and Ship 25 have all been busy since mid-October. SpaceX stacked Booster 7 and Ship 24 for the first time on October 11th and then attempted to test the fully-stacked rocket on October 13th. By some accounts, although almost nothing was visible to the public, the first full-stack test may have gone poorly, potentially even endangering pad technicians that approached the rocket to troubleshoot. On October 16th, SpaceX fully destacked Ship 24, and CEO Elon Musk noted that the company was “proceeding very carefully” to avoid an explosion that could set “Starship progress back by ~6 months.”
But if there was a major issue on October 13th, SpaceX didn’t show it, and Ship 24 was reinstalled atop Booster 7 on October 20th without any obvious maintenance or repairs. SpaceX then kicked off an unusual series of tests on October 24th, during which it only filled the liquid oxygen (LOx) or liquid methane (LCH4) tanks of Super Heavy B7, Ship 24, or both vehicles at once. A rare NASA briefing on October 31st later called them “single-species prop[ellant]” tests – a kind of extra-cautious testing that had never been seen before at Starbase. A few days prior, a member of NASA’s Aerospace Safety Advisory Panel (ASAP) noted that an accidental explosion that damaged Booster 7 in July had caused SpaceX to “increase [the rigor of its] systems engineering and risk management,” explaining the sudden influx of unusually conservative testing.
By the time Ship 24 was destacked from Booster 7 on November 8th, SpaceX had completed seven single-species tests, four of which involved loading LOx or LCH4 into both stages and three of which only tested Super Heavy. Booster 7 and Ship 24’s tanks were fully filled and LCH4 and LOx were never simultaneously loaded on either stage.
NASA’s October 31st briefing reported that SpaceX had plans to destack Ship 24 before conducting additional static fire testing with Booster 7. While B7 completed 1, 3, and 7-engine static fires in August and September, those tests were nowhere close to the full 33-engine static fire required to properly qualify the most powerful rocket in history. According to NASASpaceflight.com managing editor Chris Bergin, SpaceX’s next goal is to fire up approximately half of Super Heavy B7’s Raptors.
Strangely, although Ship 24 was believed to have completed all of the standalone testing needed to clear it for flight, SpaceX installed the vehicle on a stand used for Starship static fire testing on November 9th, implying that more standalone testing may be required. For now, that shouldn’t pose a problem as long as SpaceX wraps up any additional Starship testing around the same time as Booster 7’s next static fire campaign wraps up, but it could delay full-stack launch readiness if it takes any longer.
Finally, after Ship 25 was removed from SpaceX’s other Starship test stand on November 8th, it was rolled back to Starbase’s Starship factory. Ship 25 first rolled to the launch site on October 19th and has since completed four visible tests. On October 28th, Ship 25 survived a pneumatic proof test that showed that its tanks were leak-free and capable of surviving flight pressures (roughly 6-8.5 bar or 90-125 psi). Three cryogenic proof tests followed on November 1st, 2nd, and 7th. The first cryoproof was likely just that – a test that pressurized Ship 25’s tanks and filled them with cryogenic liquid nitrogen (LN2) or a combination of liquid oxygen and LN2.
The next two tests likely took advantage of the customized test stand, which has been semi-permanently outfitted with a set of hydraulic rams that allow SpaceX to simulate the thrust of six Raptor engines while Starship’s structures are chilled to cryogenic temperatures and loaded with roughly 1000 tons (~2.2M lb) of cryogenic fluids. If a Starship can survive those stresses on the ground, the assumption is that it will likely survive similar stresses in flight.
Assuming that Ship 25’s first several proof tests were successful, which they appear to have been, SpaceX returned the prototype to its Starbase factory to install six Raptor engines and a series of shields and firewalls that will protect those engines from each other. Once fully outfitted, Ship 25 will return to the launch site for static fire testing and take Ship 24’s place on Suborbital Pad B. Ship 24 took approximately two months to go from its last cryoproof to its first static fire. But its testing got off to a relatively rocky start, so Ship 25 could be ready sooner.
SpaceX could begin the next phases of Booster 7 and Ship 24 testing as early as November 10th or November 13th.
Elon Musk
SpaceX’s Starship FL launch site will witness scenes once reserved for sci-fi films
A Starship that launches from the Florida site could touch down on the same site years later.
The Department of the Air Force (DAF) has released its Final Environmental Impact Statement for SpaceX’s efforts to launch and land Starship and its Super Heavy booster at Cape Canaveral Space Force Station’s SLC-37.
According to the Impact Statement, Starship could launch up to 76 times per year on the site, with Super Heavy boosters returning within minutes of liftoff and Starship upper stages landing back on the same pad in a timeframe that was once only possible in sci-fi movies.
Booster in Minutes, Ship in (possibly) years
The EIS explicitly referenced a never-before-seen operational concept: Super Heavy boosters will launch, reach orbit, and be caught by the tower chopsticks roughly seven minutes after liftoff. Meanwhile, the Starship upper stage will complete its mission, whether a short orbital test, lunar landing, or a multi-year Mars cargo run, and return to the exact same SLC-37 pad upon mission completion.
“The Super Heavy booster landings would occur within a few minutes of launch, while the Starship landings would occur upon completion of the Starship missions, which could last hours or years,” the EIS read.
This means a Starship that departs the Florida site in, say, 2027, could touch down on the same site in 2030 or later, right beside a brand-new stack preparing for its own journey, as noted in a Talk Of Titusville report. The 214-page document treats these multi-year round trips as standard procedure, effectively turning the location into one of the world’s first true interplanetary spaceports.
Noise and emissions flagged but deemed manageable
While the project received a clean bill of health overall, the EIS identified two areas requiring ongoing mitigation. Sonic booms from Super Heavy booster and Starship returns will cause significant community annoyance” particularly during nighttime operations, though structural damage is not expected. Nitrogen oxide emissions during launches will also exceed federal de minimis thresholds, prompting an adaptive management plan with real-time monitoring.
Other impacts, such as traffic, wildlife (including southeastern beach mouse and Florida scrub-jay), wetlands, and historic sites, were deemed manageable under existing permits and mitigation strategies. The Air Force is expected to issue its Record of Decision within weeks, followed by FAA concurrence, setting the stage for rapid redevelopment of the former site into a dual-tower Starship complex.
SpaceX Starship Environmental Impact Statement by Simon Alvarez
News
Tesla Full Self-Driving (FSD) testing gains major ground in Spain
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Tesla’s Full Self-Driving (Supervised) program is accelerating across Europe, with Spain emerging as a key testing hub under the country’s new ES-AV framework program.
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Spain’s ES-AV framework
Spain’s DGT launched the ES-AV Program in July 2025 to standardize testing for automated vehicles from prototypes to pre-homologation stages. The DGT described the purpose of the program on its official website.
“The program is designed to complement and enhance oversight, regulation, research, and transparency efforts, as well as to support innovation and advancements in automotive technology and industry. This framework also aims to capitalize on the opportunity to position Spain as a pioneer and leader in automated vehicle technology, seeking to provide solutions that help overcome or alleviate certain shortcomings or negative externalities of the current transportation system,” the DGT wrote.
The program identifies three testing phases based on technological maturity and the scope of a company’s operations. Each phase has a set of minimum eligibility requirements, and applicants must indicate which phase they wish to participate in, at least based on their specific technological development.

Tesla FSD tests
As noted by Tesla watcher Kees Roelandschap on X, the DGT’s new framework effectively gives the green flight for nationwide FSD testing. So far, Tesla Spain has a total of 19 vehicles authorized to test FSD on the country’s roads, though it would not be surprising if this fleet grows in the coming months.
The start date for the program is listed at November 27, 2025 to November 26, 2027. The DGT also noted that unlimited FSD tests could be done across Spain on any national route. And since Tesla is already in Phase 3 of the ES-AV Program, onboard safety operators are optional. Remote monitoring would also be allowed.
Tesla’s FSD tests in Spain could help the company gain a lot of real-world data on the country’s roads. Considering the scope of tests that are allowed for the electric vehicle maker, it seems like Spain would be one of the European countries that would be friendly to FSD’s operations. So far, Tesla’s FSD push in Europe is notable, with the company holding FSD demonstrations in Germany, France, and Italy. Tesla is also pushing for national approval in the Netherlands in early 2026.
News
Tesla FSD V14.2.1 is earning rave reviews from users in diverse conditions
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise.
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise for its smoother performance and smarter decision-making.
Videos and firsthand accounts from Tesla owners highlight V14.2.1 as an update that improves navigation responsiveness, sign recognition, and overall fluidity, among other things. Some drivers have even described it as “more alive than ever,” hinting at the system eventually feeling “sentient,” as Elon Musk has predicted.
FSD V14.2.1 first impressions
Early adopters are buzzing about how V14.2.1 feels less intrusive while staying vigilant. In a post shared on X, Tesla owner @LactoseLunatic described the update as a “huge leap forward,” adding that the system remains “incredibly assertive but still safe.”
Another Tesla driver, Devin Olsenn, who logged ~600 km on V14.2.1, reported no safety disengagements, with the car feeling “more alive than ever.” The Tesla owner noted that his wife now defaults to using FSD V14, as the system is already very smooth and refined.
Adverse weather and regulatory zones are testing grounds where V14.2.1 shines, at least according to testers in snow areas. Tesla watcher Sawyer Merritt shared a video of his first snowy drive on unplowed rural roads in New Hampshire, where FSD did great and erred on the side of caution. As per Merritt, FSD V14.2.1 was “extra cautious” but it performed well overall.
Sign recognition and freeway prowess
Sign recognition also seemed to show improvements with FSD V14.2.1. Longtime FSD tester Chuck Cook highlighted a clip from his upcoming first-impressions video, showcasing improved school zone behavior. “I think it read the signs better,” he observed, though in standard mode, it didn’t fully drop to 15 mph within the short timeframe. This nuance points to V14.2.1’s growing awareness of temporal rules, a step toward fewer false positives in dynamic environments.
FSD V14.2.1 also seems to excel in high-stress highway scenarios. Fellow FSD tester @BLKMDL3 posted a video of FSD V14.2.1 managing a multi-lane freeway closure due to a police chase-related accident. “Perfectly handles all lanes of the freeway merging into one,” the Tesla owner noted in his post on X.
FSD V14.2.1 was released on Thanksgiving, much to the pleasant surprise of Tesla owners. The update’s release notes are almost identical to the system’s previous iteration, save for one line item read, “Camera visibility can lead to increased attention monitoring sensitivity.”
