Connect with us

News

SpaceX’s Crew Dragon abort test gets closer to launch with SuperDraco static fires

A pair of Crew Dragon's upgraded SuperDraco abort engines perform a static fire test. (SpaceX)

Published

on

SpaceX has posted a video showing the static fire test of a pod of Crew Dragon SuperDraco abort thrusters, indicating that the complex system has been successfully redesigned (“upgraded”) to fix the faults that caused a Dragon capsule to explode in April 2019.

This progress keeps SpaceX on track for two critical Crew Dragon milestones, both of which are now expected to occur sooner than later.

Published just a few hours prior, CNBC journalist Michael Sheetz reported that SpaceX is planning to static fire the Super Draco abort thrusters of Crew Dragon capsule C205 as early as November 2nd.

Capsule C205 – along with an expendable trunk – were reassigned to support Crew Dragon’s crucial In-Flight Abort (IFA) test after flight-proven capsule C201 was destroyed just prior to a SuperDraco static fire test on April 20th. Having just successfully completed Crew Dragon’s first uncrewed orbital launch, space station docking, and ocean recovery (Demo-1), the plan was to reuse C201 to perform the IFA test.

Crew Dragon C205 would support Demo-2 – the spacecraft’s first NASA astronaut launch – and C206 would support Post-Certification Mission 1 (PCM-1), meaning Dragon’s first operational delivery of astronauts to the ISS.

Crew Dragon capsule C205 and Falcon 9 booster B1046 arrived in Florida around October 3rd ahead of SpaceX’s critical In-Flight Abort (IFA) test. (SpaceX)
Excluding Falcon 9, all pieces of SpaceX’s first astronaut-rated Crew Dragon spacecraft are visible in this one frame: capsule C206, a heat shield, and what looks like a nearly finished trunk. (Teslarati – Pauline Acalin)

Instead, Crew Dragon C201 suffered a catastrophic explosion just prior to a SuperDraco static fire test at SpaceX’s Cape Canaveral Air Force Station (CCAFS) Landing Zone (LZ) facilities. Capsule C205 was diverted to support the In-Flight Abort, while C206 was moved up to support Demo-2. Had C201’s static fire been successful, SpaceX could have been ready to launch Crew Dragon’s IFA mission as early as May or June.

As Michael Sheetz reported, SpaceX now plans to perform a similar static fire test of the IFA Crew Dragon capsule as early as November 2nd. It’s unclear if this static fire would have been performed had C201 not exploded, but CNBC suggests that NASA and a number of other parties will be watching the results of this test closely.

SpaceX’s first spaceworthy Crew Dragon capsule prepares for its first Falcon 9-integrated static fire and a post-recovery test fire three months later. (SpaceX)

Whether that’s true or not, it’s unclear just how relevant a SuperDraco static fire of a factory-fresh Crew Dragon spacecraft (C205) is to C201’s failure. The latter spacecraft had completed months of testing (much of it fueled), spent a week in orbit, reentered Earth’s atmosphere, and splashed down in saltwater barely a month and a half prior to the fated test.

Regardless, it looks like SpaceX and NASA understandably want to perform a (relatively) similar static fire test to verify that – at a minimum – the Dragon capsule’s abort thrusters are in working order. As SpaceX’s static fire video illustrates, SuperDraco thrusters – as well as each integrated pair of engines – are all static fired in McGregor, Texas as part of routine acceptance testing. If all goes as planned during the November 2nd static fire, as well as the Falcon 9 rocket’s own static fire, Crew Dragon’s In-Flight Abort mission could launch as early as late-November.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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