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.
-
-
Lemonade has expanded its innovative Autonomous Car insurance program to Tennessee, giving Tesla owners in the state a substantial discount on Full Self-Driving (FSD) miles. Announced on August 3, the product offers 50 percent off every mile driven with FSD activated, positioning the digital insurer as a leader in pricing insurance around autonomous technology.
The program, marketed as Lemonade Autonomous Car insurance, uses a direct connection via Tesla’s Fleet API (with customer permission) to automatically distinguish FSD-engaged miles from manual driving. Policyholders pay a low base rate when the vehicle is stationary and a few cents per mile when moving, with the 50 percent reduction applied specifically to FSD miles.
If you’re driving a Tesla in Tennessee, FSD miles now cost 50% less to insure with Lemonade. Autonomous Car is now live in TN.https://t.co/4CDTuhyORi pic.twitter.com/QZk4LBIs6f
— Lemonade (@Lemonade_Inc) August 3, 2026
Coverage includes standard protections such as liability, collision, comprehensive, roadside assistance, and Tesla-specific benefits like access to certified repair shops and emergency crash services. Eligible vehicles require Hardware 4, as well as recent firmware.
Lemonade first unveiled the product on January 21 of this year, describing it as a first-of-its-kind offering designed for self-driving cars, starting with Tesla FSD. It began rolling out in Arizona on January 26, followed by Oregon about a month later. Subsequent expansions brought it to Indiana in early June 2026 and Colorado later that month.
Tennessee marks the fifth state.
Tesla Full Self-Driving gets outrageous insurance offer with insanely cheap rates
The discount rests on Lemonade’s strong belief in the safety of Tesla’s FSD system. The company cites Tesla’s data showing that FSD-driven miles are twice as safe as those driven manually, or associated with roughly a 50 percent crash reduction.
Lemonade Co-founder and President Shai Wininger has emphasized this distinction: “Traditional insurers treat a Tesla like any other car, and AI like any other driver. But a car that sees 360 degrees, never gets drowsy, and reacts in milliseconds can’t be compared to a human.”
He added that “Teslas driven with FSD are involved in far fewer accidents” and committed that as FSD software improves and becomes safer, Lemonade’s prices will drop further.
Tesla Full Self-Driving gets an offer to be insured for ‘almost free’
This approach leverages Lemonade’s existing pay-per-mile technology and AI-driven risk models, which analyze nuanced vehicle data including software version and sensor performance. The company expects the model to reward higher FSD usage with greater savings while supporting mixed households that include both Tesla and non-Tesla vehicles under one policy. Bundling with home, renters, or pet insurance can yield additional discounts.
As autonomous driving technology advances, Lemonade’s state-by-state expansion of usage-based pricing that directly reflects real-world safety data represents a notable shift in how insurers evaluate risk.
Tesla owners in the five available states – Arizona, Oregon, Indiana, Colorado, and now Tennessee – can obtain quotes quickly through the Lemonade app or website, potentially lowering the overall cost of ownership for vehicles equipped with advanced driver-assistance systems. Further states are expected as regulatory approvals progress.
Tesla has continued to flex the strength, rigidity, and robustness of its all-electric pickup, the Cybertruck. In fact, since 2019, Cybertruck’s ability to avoid dents, dings, and even gunfire has been one of the main selling points Tesla has used to attract buyers who are looking for a vehicle that can handle the most intense challenges.
But that does not mean Tesla is not still actively trying to make it even better.
In a new hardware update, Tesla has decided to change the material of the Cybertruck’s underbody panels from aluminum to carbon fiber, a move that aims to not only increase pricing efficiency but also improve strength.
RELATED:
Cybertruck Lead Engineer Wes Morrill confirmed the change was made to the Cybertruck recently after it was spotted by Coleton Guerin of Out of Spec. This particular trim level was a Cyberbeast, but it is being applied to all trims to keep supply chain efficiency high and have less variance across trim levels.
Morrill said that Tesla tested different materials for the underbody panel protection, and carbon fiber performed better than aluminum, which is what the company was using since its first deliveries in 2023.
Additionally, there are some efficiency improvements because Tesla can better form the areas around the bolts to keep underbody airflow cleaner than previously.
good eye – it’s a new material. Testing showed it to be more durable than the aluminum while being lower weight and cost. Also slight efficiency improvement since we can better form the areas around the bolts to keep the underbody airflow cleaner than what stamped aluminum allows
— Wes (@wmorrill3) July 30, 2026
Carbon fiber is traditionally lighter and more durable than aluminum, which is why it is such a popular material among luxury automakers, and EV makers will utilize some of the materials around battery packs to save weight.
This is the first instance of Tesla utilizing carbon fiber on the Cybertruck’s exterior to help with overall performance and strength. As previously mentioned, Tesla used aluminum to protect the underside of the body, but it is pretty typical for the company to continue making engineering changes that will improve the car in the future.
Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
Tesla Full Self-Driving insurance program with heavy discount expands
Tesla quietly made the Cybertruck even stronger
