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.
News
Tesla Full Self-Driving (Supervised) v14.1.7 real-world drive and review
On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users.
Tesla started rolling out its Full Self-Driving (Supervised) v14.1.7 suite last night to owners, and there are several improvements to note within the new update that are at least the start of fixes to highly-mentioned issues.
On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users. However, there are a handful of shortcomings that are still present within the suite, which are not something that will be fixed within the span of a single update.
For what it is, Full Self-Driving does an excellent job of navigating — once you get it on its correct path. Our issues tend to be confined to navigation, routing, and the decision-making process that has to do with the way the car wants to get you to your destination. There were five things that happened on our first drive with v14.1.7 that are worth mentioning. The full drive will be available at the bottom of this article.
Navigation and Routing Still Seems to Be a Major Challenge
In past content, we’ve discussed the issues with routing and navigation, and how a Tesla chooses its path. Most noticeably, these issues occur in the same areas; for me, it’s my local Supercharger. My 2026 Model Y with AI4 continues to pick less-than-optimal routes out of the Supercharger, and in this instance, it actually chose to turn down a road, pull over, and give me the wheel, essentially asking, “Hey, can you get me on the right track here?”
This is still my biggest bone to pick with FSD, even more so than some of the bonehead moves it’s made in tougher scenarios (mostly parking lots with very limited visibility due to shrubs being planted in the worst possible locations). It’s rare that it happens, but this particular Supercharger has been a true thorn in the side of my Tesla.
This is not an issue that is confined to v14.1.7, or even v14 in general. Unfortunately, it is an issue that has persisted throughout my ownership experience, as well as during Demo Drives.
Still dealing with this Navigation/Routing issue. FSD still hasn’t figured out how to exit this Supercharger.
FSD chose to pull over and let me work it out of its predicament: pic.twitter.com/ZOIsA7eW2C— TESLARATI (@Teslarati) November 13, 2025
Stuttering and Hesitation at Intersections was Non-Existent
There was some confusion regarding my language in a recent article where I stated Tesla is confronting the issues that have been reported regarding the “stabbing” with braking.
“Tesla began the v14.1.4 launch last night, which included minor improvements and addressed brake-stabbing issues many owners have reported. In my personal experience, the stabbing has been awful on v14.1.3, and is a major concern.
However, many things have improved, and only a couple of minor issues have been recurring. Many of the issues v13 addressed are no longer an issue, so Tesla has made significant progress.”
It has undoubtedly improved, but it is not resolved.
With that being said, I did not feel a single example of hesitation, stabbing, or stuttering at a single intersection or instance when it has been present in the past. CEO Elon Musk said it would be fixed with v14.2, so it seems like Tesla is well on its way to resolving it.
Proper Handling of Crosswalks
It’s crazy how many people still do not stop for pedestrians at clearly-marked crosswalks. I had two instances of it happen during the drive, with FSD stopping for those pedestrians both times.
Human drivers did not stop either time:
Two instances of FSD stopping for pedestrians at crosswalks while human drivers proceed: pic.twitter.com/b4W7GXsXwH
— TESLARATI (@Teslarati) November 13, 2025
Handled Merging onto a Highway with an Inconsiderate Driver Well
Routinely, drivers will get over into the left lane, if they are able, to allow merging traffic to safely enter the freeway. It does not always happen this way, and it’s not required by law.
Not exclusive to v14.1.7, as many past iterations would have done this as well, but it was nice to watch the vehicle slow down to let that traffic pass. It then entered the freeway safely, and the entire maneuver was well done.
Not exclusive to v14.1.7, but just a great job of allowing highway traffic to pass before merging: pic.twitter.com/Hl9Hr0N5Jc
— TESLARATI (@Teslarati) November 13, 2025
Took an Appropriate Move with Oncoming Foot Traffic and Debris in a Tight Alleyway
This was probably the most on-edge I was during the drive because: 1) FSD chose to take an unnecessary alleyway, and 2) there was a box and oncoming pedestrians.
The car was aware of everything that was going on. In order to avoid the box, it would have had to turn toward the pedestrians, and in order to avoid the pedestrians, it would have had to turn into the box.
It chose to wait patiently, and after the pedestrians were past the car, FSD chose to proceed.
A patient FSD debates pedestrians and debris.
It chooses to not turn toward the humans or the box, instead waiting for a clear path to proceed. EXCELLENT and my favorite part of the drive pic.twitter.com/JNVxuxkhmn— TESLARATI (@Teslarati) November 13, 2025
Closing Thoughts
Overall, we’re very impressed with v14.1.7, and we think this is Tesla’s best iteration of the FSD suite yet, as it should be since it’s the newest version available. Tesla’s attention to detail regarding the brake stabbing is really well done, and it seems evident that a complete fix is on its way.
Other than the navigation issue at the very beginning, which was not an intervention, at least in my opinion, this was a really successful drive.
Elon Musk
Elon Musk debunks report claiming xAI raised $15 billion in funding round
xAI also responded with what appeared to be an automated reply, stating, “Legacy Media Lies.”
Elon Musk has debunked a report claiming his AI startup xAI had raised $15 billion from a funding round. Reports of the alleged funding round were initially reported by CNBC, which cited sources reportedly familiar with the matter.
CNBC’s report
The CNBC story cited unnamed sources that claimed that the new capital injection would help fund GPUs that xAI needs to train its large language model, Grok. The news outlet noted that following the funding round, xAI was valued at $200 billion.
Artificial intelligence startups have been raising funds from investors as of late. OpenAI raised $6.6 billion in October, valuing the startup at a staggering $500 billion. Reuters also reported last month that OpenAI was preparing for an IPO with a valuation of $1 trillion. Elon Musk’s xAI is looking to catch up and disrupt OpenAI, as well as its large language model, ChatGPT, which has become ubiquitous.
Elon Musk and xAI’s responses
In his response on X, Elon Musk simply stated that the CNBC story was “false.” He did not, however, explain if the whole premise of the publication’s article was fallacious, or if only parts of it were inaccurate.
Amusingly enough, xAI also issued a response when asked about the matter by Reuters, which also reported on the story. The artificial intelligence startup responded with what appeared to be an automated reply, which read, “Legacy Media Lies.”
xAI, founded in July 2023 as an alternative to OpenAI and Anthropic, has aggressively built out infrastructure to support its flagship products, including Grok and its recently launched Grokipedia platform. The company is developing its Colossus supercomputer in Memphis, which is heralded as one of the world’s largest supercomputer clusters.
News
Tesla reportedly testing Apple CarPlay integration: report
Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally.
Tesla is reportedly testing Apple’s CarPlay software for its vehicles, marking a major shift after years of resisting the tech giant’s ecosystem.
Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally. The move could help Tesla gain more market share, as surveys have shown many buyers consider CarPlay as an essential feature when choosing a car.
Not the usual CarPlay experience
Bloomberg claimed that Tesla’s tests involve a rather unique way to integrate CarPlay. Instead of replacing the vehicle’s entire infotainment display, Tesla’s integration will reportedly feature a CarPlay window on the infotainment system. This limited approach will ensure that Tesla’s own software, such as Full Self-Driving’s visuals, remains dominant.
The feature is expected to support wireless connectivity as well, bringing Tesla in line with other luxury automakers that already offer CarPlay. While plans remain fluid and may change before public release, the publication’s sources claimed that the rollout could happen within months.
A change of heart
Tesla has been reluctant to grant Apple access to its in-car systems, partly due to Elon Musk’s past criticism of the tech giant’s App Store policies and its poaching of Tesla engineers during the failed Apple Car project. Tesla’s in-house software is also deemed by numerous owners as a superior option to CarPlay, thanks to its sleek design and rich feature set.
With Apple’s retreat from building cars and Elon Musk’s relationship with Apple for X and Grok, however, the CEO’s stance on the tech giant seems to be improving. Overall, Tesla’s potential CarPlay integration would likely be appreciated by owners, as a McKinsey & Co. survey last year found that roughly one-third of buyers considered the lack of such systems a deal-breaker.
-
News6 days agoTesla shares rare peek at Semi factory’s interior
-
Elon Musk6 days agoTesla says texting and driving capability is coming ‘in a month or two’
-
News5 days agoTesla makes online ordering even easier
-
News5 days agoTesla Model Y Performance set for new market entrance in Q1
-
News6 days agoTesla Cybercab production starts Q2 2026, Elon Musk confirms
-
News6 days agoTesla China expecting full FSD approval in Q1 2026: Elon Musk
-
News1 week agoTesla Model Y Performance is rapidly moving toward customer deliveries
-
News4 days agoTesla is launching a crazy new Rental program with cheap daily rates