News
SpaceX’s partial Falcon 9 landing failure could delay next West Coast launch
According to statements made by the Canadian Space Agency (CSA) and media outlet CBC, the launch of the agency’s next-generation Radarsat Constellation Mission (RCM) – a trio of Earth observation satellites weighing >4200 kg (9300 lbs) – has been “postponed … indefinitely” as a consequence of SpaceX’s first failed Falcon 9 booster landing since 2016.
Offering a rare glimpse into some of the extensive planning that goes on behind the scenes to make commercial rocket launches happen, CSA has indicated that the booster it planned to launch on – Falcon 9 B1050 – suffered an untimely (partial) demise during a recovery attempt shortly after successfully launching the CRS-16 Cargo Dragon mission on December 5th, 2018. While the booster shockingly was returned to dry land mostly intact after landing in the Atlantic, SpaceX and CSA must now settle on a different Falcon 9 to launch the mission.
A problem with a SpaceX booster rocket has postponed the launch of a $1 billion Canadian satellite program indefinitely. https://t.co/45qirdId5j @DeanBeeby
— CBC News (@CBCNews) January 15, 2019
Goldilocks and the Falcon boosters
While it doesn’t look like there are only three possible rocket options for the Radarsat constellation and SpaceX to choose from, the situation of picking a new booster this late in the launch flow is far less simple than it might initially seem. First and foremost, SpaceX likely needs to do its best to accommodate the preferences of customers CSA and MDA (MacDonald, Dettwiler and Associates Ltd.) regardless of how disruptive they may be. Originally targeted for sometime in November 2018, RCM’s launch slipped several months to the second half of February 2019 due to what CSA described as “higher priority missions [for]the US Government and a backlog of launches from…Vandenberg” late last year.
While that alone does not point directly towards any obvious explanations, CBC reporter Dean Beeby’s implication that the mission’s launch is now “postponed…indefinitely” offers a hint of an answer, although it could also be manufactured hyperbole where there actually is none. If CSA actually indicated that the launch is now postponed indefinitely, the only clear explanation for a launch delay greater than a month or so as a result of Falcon 9 B1050’s unplanned unavailability would lie in some unique aspect of that particular Falcon 9 booster.
-
Although each rocket SpaceX builds can be quite different from each other in terms of general quirks and bugs, the only obvious difference between B1050 and any other flight-proven Falcon 9 booster in SpaceX’s fleet was its low-energy CRS-16 trajectory, something that would have enabled a uniquely gentle reentry and landing shortly after launch. In other words, likely out of heaps of caution and conservatism if it is the case, customers CSA and MDA may have requested (or contractually demanded) that SpaceX launch the Radarsat constellation on a flight-proven Falcon 9 with as little wear and tear as possible, in which case B1050 would have been hard to beat.
“Unfortunately, the landing of [Falcon 9 B1050] was unsuccessful, preventing SpaceX from recuperating the reusable components for the launch of RCM. We continue to work closely with MDA and SpaceX to confirm a launch date for RCM.” – Spokesperson Audrey Barbier, Canadian Space Agency (CSA), 01/15/2019
If the customers remained steadfast in their (speculated) request for a gently-used flight-proven Falcon 9 even after B1050’s partial landing failure, the next most comparable booster would be Falcon 9 B1051 after launching the first orbital Crew Dragon mission sometime no earlier than (NET) February 2019. Aside from B1051, there will be no obvious booster alternative available for at least several months after Crew Dragon’s launch debut, unless NASA requests that its next contracted Cargo Dragon mission (CRS-17) launch on a new Falcon 9 rocket in March 2019.
Engines stabilized rocket spin just in time, enabling an intact landing in water! Ships en route to rescue Falcon. pic.twitter.com/O3h8eCgGJ7
— Elon Musk (@elonmusk) December 5, 2018
Warmer…
If a less lightly-used booster becomes an option for CSA/MDA, there are immediately multiple clear options available as long as SpaceX is will to accept possible delays to subsequent launches to quickly reassign a flight-proven Falcon 9. Falcon 9 B1046 – the first SpaceX rocket ever to launch three orbital-class missions – is being refurbished at SpaceX’s Hawthorne, California facilities a few hundred miles south of Vandenberg. B1047 completed its second successful launch in November 2018 and is being refurbished – along with the twice-flown B1048 – in Cape Canaveral, Florida. Finally, Falcon 9 B1049 completed its second successful launch just days ago (January 11th) and is being processed off of drone ship Just Read The Instructions (JRTI) at this very moment.
B1047 or B1048 have likely been assigned to the imminent NET February 18th launch of Indonesian commsat PSN-6 and SpaceIL’s Beresheet Moon lander, meaning that the best possible option for Radarsat – short of swallowing months of additional delays – is a decision between B1047/B1048 or B1046, with B1049 also a candidate if a slip into March or April is an option. Still, all of those options would require Canada and MDA to fly on a Falcon 9’s third (or fourth) launch, perhaps an unacceptable compromise or perceived risk for certain customers.
-
- Falcon 9 B1046 is processed in Port of LA shortly after its third successful launch and landing, December 2018. (Pauline Acalin)
-
- Falcon 9 B1047 is pictured here beneath an upper stage and satellite Es’hail-2 prior to its second launch. (Tom Cross)
-
- Falcon 9 B1048 landed at LZ-4 after its second launch and is now being refurbished on the opposite coast. (SpaceX)
-
Meanwhile, schedule pressures have meant that SpaceX is pushing as hard as possible to prepare three new Block 5 Falcon Heavy boosters for the giant rocket’s second and third launches, scheduled as early as March and April 2019. While unconfirmed, it appears that SpaceX may have chosen to manufacture all three of those boosters one after the other, meaning that the company’s Hawthorne factory would have been primarily focused on delivering those rockets for at least 2-3 months start to finish. In short, it does not appear that there is or will be an unflown Falcon 9 booster available for Radarsat anytime soon.
Whether the customers wait for a new booster to be produced, wait for Crew Dragon’s first launch to wrap up, or accept being the third or fourth launch of a well-scorched Falcon 9, RCM’s next published launch target should offer a hint as to how CSA, MDA, and SpaceX ultimately decided to respond to Falcon 9 B1050’s dip in the Atlantic OCean.
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
