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.
Tesla has introduced an enhanced visualization in its Supercharger navigation system, building directly on the Site Maps feature rolled out a few months ago.
This latest software update adds detailed 3D icons that represent specific vehicle models parked at charging stalls, offering drivers a more precise view of site occupancy and layout.
The Site Maps debuted in Tesla’s 2025 Holiday Update, providing 3D overviews of select Supercharger locations with real-time stall availability.
Tesla supplements Holiday Update by sneaking in new Full Self-Driving version
Drivers could see which spots were open, occupied, or out of service when navigating to supported stations.
Now, the system takes this capability further by rendering accurate representations of Tesla vehicles, including distinctions between models such as the Model 3, Model Y, Model S, Model X, and Cybertruck. These icons appear as lifelike 3D renderings, complete with recognizable shapes and proportions that match the actual cars charging at the site:
Supercharger update now shows type of Tesla at charger as well.
Pretty cool. pic.twitter.com/J3NRSIgM0m
— DennisCW | wen my L (@DennisCW_) June 2, 2026
This refinement improves the user experience during road trips and daily charging stops. As drivers approach a Supercharger, the navigation display now shows not just generic occupied markers but identifiable vehicle types plugged into each stall.
Blue indicators highlight active charging sessions, while other visual cues denote availability or maintenance status. The feature integrates seamlessly with the existing map interface, allowing quick assessment of the best available spot based on vehicle size and positioning.
Tesla continues to expand the availability of these detailed Site Maps across its global network. Initially piloted at a limited number of locations, the rollout has progressed steadily, with more stations gaining support in recent software versions.
Owners benefit from better planning, as the system helps identify compatible stalls and reduces uncertainty upon arrival. The update reflects Tesla’s ongoing commitment to refining its navigation and charging ecosystem through iterative software improvements.
In addition to model-specific icons, the enhanced maps maintain all prior functionalities, such as integration with nearby amenities and energy usage predictions. This ensures a comprehensive tool for efficient Supercharging.
As Tesla’s fleet grows and the network scales, such features play a key role in optimizing the overall ownership experience. Future updates may extend similar visualizations to additional sites and incorporate even more data points for drivers.
With this piggyback enhancement, Tesla demonstrates how small but thoughtful additions can elevate an already useful tool, making Supercharger visits smoother and more informed for its customers. The company is expected to broaden the feature’s reach in upcoming releases, further solidifying its leadership in EV charging infrastructure.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla piggybacks recent Supercharger feature with update that takes it further
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
