News
A SpaceX surprise: Falcon Heavy booster landing to smash distance record
In an unexpected last-second change, SpaceX has moved Falcon Heavy Flight 3’s center core landing on drone ship Of Course I Still Love You (OCISLY) from 40 km to more than 1240 km (770 mi) off the coast of Florida.
Drone ship OCISLY is already being towed to the landing site, necessary due to the sheer distance that needs to be covered at a leisurely towing pace. The current record for distance traveled during booster recovery was set at ~970 km by Falcon Heavy center core B1055 in April 2019. If successful, Falcon Heavy center core B1057 will smash that record by almost 30% after sending two dozen spacecraft on their way to orbit. Falcon Heavy Flight 3 is scheduled to lift off in support of the Department of Defense’s Space Test Program 2 (STP-2) mission no earlier than 11:30 pm ET (03:30 UTC), June 24th. A routine static fire test at Pad 39A will (hopefully) set the stage for launch on Wednesday, June 19th.
This comes as a significant surprise for several reasons. First and foremost, the difference between a center core landing 40 km or 1300 km from the launch site is immense. For Falcon Heavy, the center core shuts down and separates from the rest of the rocket as much as a minute after the rocket’s two side boosters, potentially doubling the booster’s relative velocity at separation.

That extra minute of acceleration means that the center core can easily be 50-100+ km downrange at the point of separation. In other words, landing 40 km offshore aboard drone ship OCISLY would be roughly akin to a full boostback burn, meaning that the center core would need to nullify all of its substantial downrange velocity, turn around, and fly ~50-100 km back towards the launch site. Being able to perform such an aggressive maneuver would indicate that Falcon Heavy’s boost stage has a huge amount of propellant (delta V) remaining after completing its role in the launch.
To have STP-2’s center core recovery moved from 40 km to 1240 km thus indicates an absolutely massive change in the rocket’s mission plan and launch trajectory. For reference, Falcon Heavy Flight 2’s Block 5 center core (B1055) set SpaceX’s current record for recovery distance (970 km/600 mi) after launching Arabsat 6A – a massive ~6500 kg (14,300 lb) satellite – to a spectacularly high transfer orbit of >90,000 km (56,000 mi).
Why so spicy?
There are three obvious possibilities that might help explain why the STP-2 mission has abruptly indicated that it will require SpaceX’s most energetic booster recovery yet.
1. STP-2 is carrying at least 1-2 metric tons worth of mystery payload(s)
This is highly unlikely. The USAF SMC has already released a SpaceX photo showing the late stages of the STP-2 payload stack’s encapsulation inside Falcon Heavy’s payload fairing. Short of an elaborate faked encapsulation followed by the installation of additional mysterious spacecraft or some extremely dense hardware hidden inside, it’s safe to say that the STP-2 payload stack weighs what the USAF says it weighs, which is to say not nearly heavy enough to warrant a record-smashing booster recovery given the known orbital destinations.
The USAF further confirmed that there is no ballast on the stack, removing the possibility of a lead weight or steel boilerplate meant to artificially push Falcon Heavy to its limits.
2. STP-2’s already-challenging Falcon upper stage mission profile is even more exotic than described
Per official mission overviews, it’s already clear that STP-2 could be the most challenging launch ever attempted for SpaceX’s orbital Falcon upper stage. According to SpaceX itself, “STP-2…will be among the most challenging launches in SpaceX history, with four separate upper-stage engine burns, three separate deployment orbits, a final propulsive passivation maneuver, and a total mission duration of over six hours.”

While undeniably challenging, it’s not clear why it would require such a high-energy center core recovery. With a payload mass of just ~3700 kg, Falcon 9 has launched much larger payloads to (relatively) higher orbits, but this fails to account for the added challenge of long coasts and multiple different orbits. Also of note, the above graph (courtesy of a years-old USAF document) appears to disagree with SpaceX’s description of “four… upper-stage burns”, instead showing five burns (red spikes).
More likely than not, OCISLY’s ~1200-kilometer move can be explained largely by the reintroduction of what the above graph describes as the Falcon upper stage’s “disposal burn”, likely referring to a deorbit burn. On top of the delta V already required for the first four burns, it isn’t out of the question that an additional coast and deorbit burn from 6000 km (3700 mi) would push the recovery equation in favor of attempting to incinerate center core B1057.

3. USAF/DoD conservatism strikes again?
The last plausible explanation for this radical shift is that the US Air Force/Department of Defense (DoD) has decided last-second that they want more margins on top of their already-overflowing safety margins, quite literally pushing B1057 to the edge of its performance envelope to mitigate low-probability failure modes. This has been done to an even more extreme extent with the US Air Force’s recent GPS III SV01 launch, in which SpaceX was forced to expend a new Falcon 9 Block 5 booster to provide the extreme safety margins the USAF desired.
According to the USAF, the STP-2 mission – including launch costs – represents as much as $750M, coincidentally similar to the estimated cost of the GPS III SV01 satellite and an expendable Falcon 9 rocket. As such, it’s not out of the question that a similar level of paranoia/conservatism is in play for STP-2.

Numbers 2 and 3 are equally plausible explanations for this last-second booster recovery shift. Given the US military’s active involvement, it’s more likely than not that no explanations will be offered. Regardless, this surprise development is bound to result in a truly spectacular recovery attempt for SpaceX’s second Block 5 center core and will likely involve breaking several still-fresh records in the process.
Falcon Heavy Flight 3 is in the middle of rolling out to SpaceX’s Kennedy Space Center Pad 39A launch facilities for a routine pre-launch static fire test, scheduled to occur no earlier than 12:30 pm ET (16:30 UTC), June 19th. If all goes well, SpaceX should be on track for its first STP-2 launch attempt at 11:30 pm ET (03:30 UTC), June 24th.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.”
