Connect with us

News

European spacecraft converge on the US for rides on SpaceX rockets

Published

on

Thanks in large part to delays suffered by Arianespace’s next-generation Ariane 6 rocket, a small fleet of European satellites are simultaneously converging on the United States to hitch rides into orbit with SpaceX.

SpaceX launching European payloads is nothing new. The company has occasionally launched spacecraft built in Europe for European space agencies or companies, but the combination is exceedingly rare. For several reasons, however, what was once alien is beginning to become commonplace, and that fact is about to be made even clearer over the remainder of 2022.

SpaceX kicked off a string of six or seven launches of spacecraft built by or for Europe on October 15th. Over the weekend, the company’s workhorse Falcon 9 rocket – 70 meters (230 ft) tall, 3.7 meters (12 ft) wide, and capable of producing up to 770 tons (1.7M lbf) of thrust at liftoff – successfully launched the Hotbird 13F communications satellite into a geostationary transfer orbit (GTO) for the French satcom company Eutelsat.

Hotbird 13F is the first of three Eutelsat satellites the company secretly agreed to launch on SpaceX rockets. Hours after its twin’s launch, Hotbird 13G arrived in Florida in a custom Airbus Beluga XL transport jet (its first visit to the US since 2009) and will soon begin preparing for its own ride on a SpaceX rocket as early as November 2022. Eutelsat 10B, also on track to launch on a Falcon 9 rocket sometime in November, likely left France for Florida on an oceangoing Arianespace ship on October 12th.

Advertisement

Normally, selecting the launch provider for communication satellites that cost eight or nine figures is accompanied by a press release and plenty of celebration. That the European Space Agency, Eutelsat, Airbus, and Thales Alenia said next to nothing until the last moment says a lot about how all parties involved really feel about transferring three of their satellites onto SpaceX rockets. Originally, all three were intended to launch on Arianespace’s rockets: Eutelsat 10B on one of the last Ariane 5s and Hotbird 13F and 13G on one of the first Ariane 6s.

It’s not entirely clear why Ariane 5 wasn’t able to launch Eutelsat 10B, but it’s unsurprising that partners ESA, Thales Alenia, Airbus, and Eutelsat decided to move Hotbird 13F and 13G to Falcon 9. The Ariane 6 rocket meant to launch both satellites simultaneously is years behind schedule, and its launch debut recently slipped even further from late 2022 to sometime in 2023. Originally scheduled to debut in mid-2020, it’s now possible – if not likely – that Ariane 6 won’t be ready to launch until the second half of next year (or even later).

Thanks to those delays, the new rocket will enter the scene with a very busy 2023 and 2024 manifest packed with high-value institutional and commercial payloads from all across Europe. In other words, a pair of semi-commercial communications satellites like Hotbird 13F/13G could have easily been forced to wait for a year or more to launch on Ariane 6. Adding insult to injury, Hotbird 13F and 13G are the first two satellites built under the joint European Space Agency and Airbus Eurostar Neo program, and will now be flying on an American rocket built by a company that is almost singlehandedly responsible for ending a golden era of competitive European launch services.

With confidence in Ariane 6’s debut timing lower than ever, a NASA official recently revealed that ESA is even studying the possibility of launching Euclid – a next-generation two-ton space telescope – on SpaceX’s Falcon 9. Euclid was originally scheduled to launch on one of Arianespace’s Russian-built Soyuz 2.1 rockets (or Ariane 6) in mid-2022. That contract was signed in 2020, six years after Russian President Vladimir Putin reminded the world of his instability, recklessness, and brutality by illegally and unofficially invading Ukraine. In February 2022, after months of obvious buildup, Russia doubled down on its Ukraine offensive with an openly genocidal full-scale invasion. In the aftermath, it kidnapped a batch of European OneWeb satellites, requisitioned a Soyuz rocket the company had already paid for, kneecapped a joint European-Russian Mars mission, and (while mostly mutual) revoked its support of European Soyuz launches.

Advertisement

That has effectively removed Russia as a serious option for European launches or collarboration, leaving several European missions and companies in limbo. Britain’s OneWeb, for example, had an exclusive contract with Russia to launch its entire low Earth orbit (LEO) internet satellite constellation on up to 21 Soyuz rockets. After losing $230 million in the process, the company was forced to abruptly shift gears, and is now on track to launch its first batch of satellites since early 2022 on an Indian SLV-3 rocket. One of at least two SpaceX Falcon 9 missions could follow as early as December 2022. Unless Ariane 6 aces its launch debut in the near future, many more European payloads could find themselves in similar positions in 2023 and 2024.

Meanwhile, several other European-made payloads are preparing for Falcon 9 launches. While these payloads have been assigned to SpaceX rockets from the start, they still demonstrate just how big of a bite the US startup has taken out of the European launch industry. Most recently, the joint NASA-ESA-CSA Surface Water and Ocean Topography (SWOT) spacecraft was flown from France to California on October 17th. Falcon 9 will launch SWOT from the California coast as early as December 2022.

Soon, Japanese startup ispace’s first HAKUTO-R Moon lander – largely assembled, tested, and propellant by France’s ArianeGroup – will be transported from Germany to Florida for a November 2022 SpaceX launch. Germany’s second and third SARah radar satellites could head to the US shortly for a Falcon 9 launch tentatively scheduled as early as the final days of 2022 or early 2023. Finally, SpaceX could complete its first OneWeb launch around the same time.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

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.

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.

Continue Reading

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

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.”

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.

Continue Reading

News

Apple is developing the missing link for Tesla to get CarPlay: report

Published

on

Credit: Michał Gapiński/YouTube

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.

Continue Reading