News
SpaceX’s next West Coast Falcon 9 landing could be decided by baby seals
SpaceX and the Canadian Space Agency (CSA) have – at long last – officially announced a launch date for the Radarsat Constellation Mission (RCM), a ~$1B trio of Earth observation satellites.
Delayed from November, February, March, and May, RCM is now scheduled to launch on a flight-proven Falcon 9 booster from California’s Vandenberg Air Force Base (VAFB) no earlier than June 11th. The three flight-ready spacecraft were shipped from Canada in September 2018 and have now been awaiting launch in a Southern California storage facility for more than half a year. The blame for such an egregious delay can be largely placed on SpaceX, but CSA and launch customer Maxar Technologies are also partially responsible. On a lighter note, the location of RCM’s subsequent Falcon 9 landing might end up being decided by seal pupping – baby harbor seals, in other words.
Although RCM’s slip from 2018 to 2019 remains unexplained, the mission’s journey from mid-February to mid-June is a different story. Still, next to nothing is publicly known about the process SpaceX launch customers go through after contracts have been signed, particularly with respect to how Falcon boosters are assigned to missions. This is further stymied by the fact that – to date – the ~$1 billion RCM is probably the most valuable payload SpaceX has ever attempted to launch, making it a clear outlier. But, as they say, “damn the epistemological torpedoes!”
Rocket logistics hell
RCM’s logistical hell and ~6 months of delays began on December 5th, 2018 when Falcon 9 Block 5 booster B1050 – having just completed its inaugural launch debut – experienced a hydraulic pump failure. The first of its kind, B1050’s pump failure killed grid fin control authority and forced the booster to abort into the Atlantic Ocean, where it somehow pulled off a landing soft enough to leave the rocket almost entirely intact. Even more surprisingly, B1050 was safely towed back to port, lifted onto dry land, and shipped off to one of SpaceX’s many Florida hangars for inspection.
Despite its near-miraculous survival, B1050 was immediately removed from SpaceX’s fleet of flightworthy boosters. Set to become the least flight-proven flight-proven Block 5 booster yet after supporting a low-energy Cargo Dragon mission, SpaceX and CSA/Maxar had apparently reached an agreement to launch RCM on B1050.2. Despite the availability of other boosters at the time, all available cores had completed two launches (B1046, 47, and 48) or were assigned to a second launch in the near-term (B1049). This is the only rational explanation for the delays that followed.
B1049 completed its second launch in mid-January 2019 and has since floated around various SpaceX facilities while waiting for its third mission. Had CSA/Maxar been okay with a twice-flown Falcon 9, B1049 could have likely supported RCM’s launch as early as March or April. Instead, the customer – as was apparently their right – concluded that being a booster’s third launch would be an unacceptable risk, whereas launching on a once-flown booster was acceptable. The only possible solution to those demands was to manifest RCM on Falcon 9 B1051, assigned to Crew Dragon’s launch debut.
Quite possibly the worst booster one could pick for schedule preservation, Crew Dragon’s launch debut slipped – to the surprise of very few – from January to February and finally to March 3rd. B1051 launched, landed without issue, and returned to Port Canaveral a few days later, where it was transported to Pad 39A for refurbishment. The relatively gently-used booster required a bit less than 8 weeks of inspection and refurbishment before being packaged and shipped to California near the end of April (see above). By now, B1051 is likely safely inside SpaceX’s SLC-4E integration hangar, preparing for upper stage integration and a routine pre-launch static fire test.
In short, an untimely Falcon 9 anomaly and customer preferences conspired to delay the launch of Canada’s Radarsat Constellation Mission by nearly four months, from February 18th to June 11th. With any luck, the mission’s flow will be issue-free and suffer no additional delays.
FCC launch communications licenses currently show that SpaceX plans to return Falcon 9 B1051 to the launch site (RTLS) after launch, rather than landing aboard drone ship Just Read The Instructions (JRTI). With a total launch mass likely around 5000 kg (11,000 lb), Falcon 9 should easily be able to manage a RTLS recovery. However, SpaceX’s West Coast LZ-4 use permit prevents the company from landing rockets at the pad during harbor seal pupping season, typically March thru June. The sonic booms and noise generated during Falcon 9’s spectacular landings might end up stressing endangered harbor seals, potentially causing parents to abandon their seal pups in confusion. As such, JRTI may be forced to get some exercise after spending almost five months in port. Anything for the baby seals!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has scaled back driver monitoring to be less naggy with the latest version of the Full Self-Driving (Supervised) suite, which is version 14.3.3.
The latest version is already earning praise from owners, who are reporting that the suite is far less invasive when it comes to keeping drivers from taking their eyes off the road. The first to mention it was notable Tesla community member on X known as Zack, or BLKMDL3.
14.3.3 nags less too https://t.co/IuiWzuYO6O
— Elon Musk (@elonmusk) May 18, 2026
Musk confirmed that v14.3.3 was made to nag drivers significantly less, something that Tesla has worked toward in the past and has said with previous versions that it is less likely to push drivers to look ahead, at least after looking away for a few seconds.
This refinement aligns with Tesla’s ongoing push toward unsupervised FSD. The update also brings faster Actual Smart Summon (now up to 8 mph), reliable “Hey Grok” voice commands, richer visualizations, smoother Mad Max acceleration, and an intervention streak counter that rewards consistent use. Reviewers describe the drive as more human-like and confident, with fewer twitches or unnecessary maneuvers.
Musk has repeatedly signaled this direction. In late 2025, he stated that FSD would allow phone use “depending on context of surrounding traffic,” noting safety data would justify relaxing rules so drivers could text in low-risk scenarios like stop-and-go traffic.
We tested this, and even still, the cell phone monitoring really seems to be less active in terms of alerting drivers:
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Earlier, ahead of v14, Musk promised the system would “nag the driver much less” once safety metrics improved.
In 2023, he confirmed the steering wheel torque nag would be “gradually reduced, proportionate to improved safety,” shifting reliance to the cabin camera. Subsequent updates like v13.2.9 and v12.4 further loosened monitoring, cracking down on workarounds while easing legitimate distractions.
These steps reflect Tesla’s data-driven approach: FSD’s safety record—reportedly averaging millions of miles per crash—now outpaces human drivers in many scenarios, giving the company confidence to dial back interventions. Reduced nags improve usability and trust, encouraging more drivers to rely on the system rather than disengaging out of frustration.
However, there are certainly still some concerns. In many states, it is illegal to handle a cell phone in any way, requiring the use of hands-free devices. In Pennsylvania, it is illegal to use your cell phone at stop lights, which is definitely a step further than using it while the car is actively in motion.
v14.3.3 represents tangible progress. Making FSD less adversarial and more seamless is definitely a step forward, but drivers need to be aware of the dangers of distracted driving. FSD is extremely capable, but it is in no way fully autonomous, nor does its performance warrant owners to take their attention off the road.
Tesla has officially expanded its Full Self-Driving (FSD) suite in Europe once again, as it will now be offered to customer vehicles in Lithuania, marking a significant milestone as the second European Union country to offer the system.
Tesla confirmed FSD’s rollout in Lithuania this morning:
FSD Supervised now rolling out to Teslas in Lithuania 🇱🇹!
Making European roads safer, one by one pic.twitter.com/Uuj0bNG7pP
— Tesla Europe, Middle East & Africa (@teslaeurope) May 20, 2026
Tesla showed several clips of Full Self-Driving navigation in Lithuania to mark the announcement, while Lithuanian Transport Minister Juras Taminskas highlighted the system’s potential to assist with lane-keeping, speed adjustment, and traffic tasks on longer drives, while emphasizing that drivers must stay alert and ready to intervene.
Just a few weeks ago, Tesla officially entered Europe with Full Self-Driving in the Netherlands. The expansion of FSD on the continent is now officially underway.
Full Self-Driving’s European Journey
Europe has long posed one of the toughest regulatory challenges for Tesla’s autonomy ambitions due to stringent safety standards under the United Nations Economic Commission for Europe (UNECE) framework, particularly UN Regulation 171 for Driver Control Assistance Systems.
The Netherlands’ RDW authority granted the pioneering approval after over 18 months of rigorous testing, including 1.6 million kilometers on European roads and extensive data submissions.
This approval enables mutual recognition across the EU, allowing other member states to adopt it nationally without full re-testing. Lithuania quickly leveraged this mechanism, becoming the second adopter. Tesla positions FSD Supervised as a tool to incrementally improve road safety, with the company claiming it reduces incidents when used properly.
Bottlenecks slowing broader European deployment include fragmented national regulations, varying levels of regulatory skepticism, and requirements for robust driver monitoring. Some EU officials have raised concerns about performance in adverse conditions like icy roads or speeding scenarios, alongside frustrations over Tesla’s public advocacy approach.
Additional hurdles involve data privacy, liability frameworks, and the need for EU-wide harmonization. While countries like Belgium appear to be fast-tracking adoption, larger markets such as Germany, France, and Italy are expected to follow in the coming months, with potential EU-wide progress targeted for later in 2026.
Tesla Full Self-Driving Across the World
As of May, Full Self-Driving (Supervised) is available in approximately ten countries.
In North America, it has been live for years in the United States, Canada, Mexico, and Puerto Rico. Asia-Pacific additions include Australia, New Zealand, and South Korea, while China utilizes what Tesla calls “City Autopilot.” In Europe, the Netherlands and now Lithuania join the list, with more countries mulling the possibility of also approving FSD.
Tesla offers FSD via monthly subscriptions (around €99 in Europe) or one-time purchases (with deadlines approaching in many markets), shifting toward recurring revenue models. Today is the final day Europeans will be able to purchase the suite outright.
This expansion underscores Tesla’s push for global autonomy, starting with supervised and building toward greater capabilities. With Lithuania now online, momentum is building across Europe, though regulatory caution will continue shaping the pace. Owners in approved regions report smoother highway and urban driving, but the system remains Level 2, which requires human oversight.
Elon Musk
Tesla ditches India after years of broken promises
Tesla has ditched its plans to build a factory in India after years of failed negotiations.
Tesla’s long-running effort to establish a manufacturing presence in India is officially over. India’s Minister of Heavy Industries H.D. Kumaraswamy confirmed on May 19, 2026 that Tesla has informed authorities it will not proceed with a manufacturing facility in the country.
Tesla first signaled serious interest in India around 2021, when it began hiring local staff and lobbying the Indian government for lower import tariffs. The ask was straightforward: reduce duties enough for Tesla to test the market with imported vehicles before committing capital to a local factory. India’s position was equally firm, with an ask of Tesla to commit to manufacturing first, then receive tariff relief. Neither side moved, and the talks quietly collapsed.
Tesla to open first India experience center in Mumbai on July 15
India had offered a policy that would reduce import duties from 110% down to 15% on EVs priced above $35,000, provided companies committed at least $500 million toward local manufacturing investment within three years. Tesla declined to participate. The tariff standoff was only part of the problem. Analysts pointed to significant gaps in India’s local supply chain, inadequate industrial infrastructure, and a mismatch between Tesla’s premium pricing and the purchasing power of India’s automotive market as additional factors that made the investment difficult to justify.
First signs of an unraveling relationship came in April 2024, when Musk abruptly cancelled a planned trip to India where he was set to meet Prime Minister Modi and announce Tesla’s market entry. By July 2024, Fortune reported that Tesla executives had stopped contacting Indian government officials entirely. The government at that point understood Tesla had capital constraints and no plans to invest.
The more fundamental issue is that Tesla’s existing factories are currently operating at approximately 60% capacity, making a commitment to building new manufacturing capacity in a new market difficult to defend to investors. Tesla will continue selling imported Model Y vehicles through its existing showrooms in Mumbai, Delhi, Gurugram, and Bengaluru, but local production is no longer part of the plan.
Tesla scales back driver monitoring with latest Full Self-Driving release
Tesla Full Self-Driving expands in Europe, entering its second country
