News
SpaceX preps Starship, Super Heavy for another week of Raptor testing
SpaceX continues to work around the clock to prepare its latest Starship and Super Heavy booster prototypes for another week of testing – likely focused on firing up the Raptor engines installed on each vehicle.
Known as Booster 7 and Ship 24, SpaceX has been slowly testing both prototypes for approximately four months, beginning in April and May, respectively. Only in early August did the company cautiously begin attempting to ignite their Raptor engines as part of a process known as static fire testing – by far the most difficult and important part of qualifying both vehicles for flight.
Thanks to progress made in 2021, SpaceX already has significant experience testing an earlier orbital-class Starship prototype on the ground, but the process of testing Ship 24 is still fresh and unfamiliar for a number of reasons. For Booster 7, the challenges are even greater.
On top of major design changes made to Starship and Super Heavy over the last year as SpaceX continues to refine the rocket, the company also developed a substantially different version of its Raptor engine. Compared to Raptor V1, Raptor V2 almost looks like a new engine and can produce around 25% more thrust (230 tons versus 185 tons). SpaceX has also tweaked how the engine operates, particularly around startup and shutdown, further weakening the value of past experience testing Raptor V1 and V1.5 engines on Ship 20 and Boosters 3 and 4.
In other words, with Ship 24 and Booster 7 engine testing, it’s possible that SpaceX is effectively starting from scratch. Many aspects of testing – propellant conditioning, thermal characteristics, tanking, detanking, certain test stands – are likely mostly unchanged, but almost every aspect of a rocket is affected by its engines.


Before SpaceX began testing Raptor V2 engines on Starship and booster prototypes, it wasn’t clear if the changes between V1.5 and V2 would invalidate a lot of prior testing. After the start of Booster 7 and Ship 24 static fire testing, it’s now clear that a lot of that earlier work has to be redone. It’s also clear that despite some of the simplifications in Raptor V2’s design, operating the engine on Starship and Super Heavy is much harder get get right.
Since mid-July, SpaceX has completed around 15-20 ‘spin-prime’ tests between Ship 24 and Booster 7 – more of that kind of test than any other prototype in the history of Starbase has performed. Spin-prime tests flow high-pressure gas through Raptor’s pumps to spin them up without igniting anything. It’s unclear why so many of those tests are being done, what SpaceX is gaining from it, or why the company appears to have completely stopped conducting preburner tests (a more life-like spin-prime with partial combustion).
Regardless, eight weeks after the start of engine testing, Booster 7 has only performed three static fires (two with one engine, one with a max of three or four engines), and Ship 24 has only completed one static fire with two engines. Before either vehicle can be considered ready for flight, a day that could easily never come, each will likely need to conduct multiple successful static fires with all of their Raptor engines (6 on S24 and 33 on B7).
If the pace of Booster 7 testing doesn’t change, the vehicle could be months away from a full 33-engine static fire attempt – perhaps the single most important and uncertain test standing between SpaceX and Starship’s first orbital launch attempt. Ship 24’s path to flight readiness should be simpler, but it appears to be struggling almost as much.
According to CEO Elon Musk, “an intense effort is underway” to ensure that Super Heavy B7’s Raptor engines are well contained during anomalies, so that one engine violently failing won’t damage or destroy the booster, other engines, or the launch pad. That could certainly complicate the process of testing Booster 7, and it’s likely that SpaceX is taking some of the same actions to protect Ship 24.
In early September, after a partially successful Booster 7 static fire (its first multi-engine test) and numerous additional Ship 24 tests that failed to achieve ignition, SpaceX replaced engines on both vehicles. Booster 7 had one of 13 Raptor Center engines swapped out, while Ship 24 had one of its three Raptor Vacuum engines replaced.
On September 5th, SpaceX distributed a safety alert to Boca Chica’s few remaining residents, confirming that it wants to restart testing as early as Tuesday, September 6th. Especially as of late, that alert guarantees nothing, but it does at least open the door for SpaceX if Ship 24, Booster 7, and the positions of the stars happen to be in the right mood between 8am and 8pm CDT. Additional opportunities are available on September 7th, 8th, 9th, and 12th.
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.”
