News
SpaceX beats Falcon 9 recovery records after company’s heaviest launch ever
Completed on May 30th, SpaceX’s latest Falcon 9 booster recovery smashed several internal speed records, unofficially cataloged over the years by watchful fans.
In short, as the company’s experienced recovery technicians continue to gain experience and grow familiar with Falcon 9 Block 5, the length of booster recoveries have consistently decreased in the 12 months since Block 5’s launch debut. Already, the efficiency of recovery processing has gotten to the point that – once SpaceX optimizes Block 5’s design for refurbishment-free reuse – there should be no logistical reason the company can’t fly the same booster twice in ~24-48 hours.
The road to rapid reusability
Rarely will it make headlines, but the fact remains that SpaceX’s ultimate goal is not just to reuse Falcon 9 (and other) boosters, but to do so with a level of routine efficiency approaching that of modern passenger aircraft. It’s reasonable to assume that chemical rockets might never reach those capabilities, but they may certainly be able to improve enough to radically change the relationship between humans and spaceflight.
Along that line of thinking, SpaceX CEO Elon Musk decided years ago that an excellent representative goal for Falcon 9 would be to launch the same booster twice in 24 hours. In the last year or so, that largely arbitrary target has changed a bit and is now believed to be a bit wider, aiming for booster reuse within a few days of recovery. This is a pragmatic adjustment more than a technical criticism of Falcon 9.
In general, Falcon 9 simply doesn’t have the performance necessary for routine reusability timelines measured in hours. The majority of SpaceX launches need enough of Falcon 9’s performance to necessitate recovery aboard one of SpaceX’s two drone ships, typically stationed at least a 200-300 km (100-200 mi) offshore. That fact alone almost single-handedly kills any chance of sub-24-hour booster reuse, given that the process of towing the booster-carrying drone ship back to port happens at a max speed of ~10 mph (15 km/h). Just gaining permission to enter the port itself often involves waits of 6+ hours a few miles offshore.
Low orbit, low mass Falcon 9 missions are much more promising for extremely rapid reusability, given that both of SpaceX’s West and East coast landing zones are located just a few miles (or less than 1500 feet, in the case of LZ-4) from their corresponding launch pads and processing facilities. However, these missions are quite rare, while SpaceX’s own low Earth orbit (LEO) Starlink launches will likely involve payloads so heavy that long-distance drone ship recoveries will be necessary.
Finally, there are Falcon Heavy launches, most of which will allow for both side boosters to return to the Florida coast for landings at LZ-1/LZ-2. However, these pose their own barriers to rapid reuse, mainly due to the fact that side boosters – while technically just Falcon 9 boosters – would need major changes to support a single-stack Falcon 9 launch. Falcon Heavy launches simply aren’t going to happen back-to-back over a period of 24-48 hours, so that option is also out of the question.
This means that SpaceX’s only real option for practical rapid reuse is to instead focus on something closer to a weekly launch capability for Block 5 boosters, meaning that the same booster would be able to launch, land, return to shore, and prepare for the next launch in the same week. Even then, launch site readiness may still stand in the way of truly radical improvements in booster reuse and launch frequency. After each launch, SpaceX’s pads and transporter/erectors take a significant beating, requiring routine repairs and maintenance before returning to flight-readiness. Barring major improvements, SpaceX has demonstrated minimum launch-to-launch times of roughly 10 days, and cutting that figure by 50-90% will be a major challenge for a rocket as powerful as Falcon 9.
B1049 takes a step forward
Despite the many logistical reasons that Falcon 9 will likely never lend itself to routine ~24-hour reusability, having that latent capability would still mean that the hardware is advanced enough to offer that efficiency. Even if SpaceX can’t literally fly each booster at its operational capacity, nearly refurbishment-free reflights will still translate into dramatically lower launch costs. Modern civilian aircraft need not fly every second of every day to still be affordable to operate (excluding amortization costs).
Ultimately, SpaceX has been taking small steps in that direction ever since the company began recovering (and reusing) Falcon 9 boosters. Falcon 9 B1049’s third recovery has been one of the best (and most record-breaking) steps yet, but those records were only just broken The most significant statistic to come out of the post-Starlink v0.9 recovery is that B1049.3 took less than 30 hours to go from docking in port to being horizontal on a SpaceX booster transporter. The previous record-holder was Falcon 9 B1046.2, requiring approximately 40 hours for the same feat. B1049.3 also holds the record for fastest recovery overall – just 48 hours from docking to being transported to a SpaceX hangar – but only beat B1051 by about half an hour. In general, Falcon 9 Block 5 has been privy to consistently quick recovery operations and B1049 is just the latest in a long line of reusable SpaceX rockets.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Turn-by-turn navigation is not new technology.
For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.
Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.
Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.
Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.
But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.
This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.
More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.
It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?
Multiple Data Sources
First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.
Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.
Persistent Learning
FSD seems to struggle with persistent learning from driver interventions.
Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.
This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.
I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.
The next thing I’ve noticed, and this might be controversial, is that Nav has gotten even worse.
I think that might actually be a good thing; Tesla seems to be adjusting it. They just need to adjust it the opposite way.
The car is taking extremely strange routes to very… https://t.co/UHg3tVfNA2
— TESLARATI (@Teslarati) June 16, 2026
Reasoning, Scaling, and Intuition
Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.
Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.
Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.
Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.
Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.
A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”
Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”
🚨 A Tesla Cybertruck, which is illegal to drive in the UK due to safety concerns, has been seized by police in Greater Manchester
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a… pic.twitter.com/cqhdPok3DM
— TESLARATI (@Teslarati) June 16, 2026
The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.
The Greater Manchester Police Department then added:
“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”
The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.
Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.
A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.
Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.
A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.
CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.
Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:
The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.
Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.
This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
