News
SpaceX CEO Elon Musk posts uncut Raptor, drone videos of Starhopper’s flight test debut
Some two hours after Starhopper’s inaugural untethered flight, SpaceX CEO Elon Musk took to Twitter to post an uncut video showing the ungainly rocket’s launch and landing from the perspective of both a drone and Starhopper’s lone Raptor engine.
As noted by commenters, Starhopper’s first flight also marks perhaps an even more fascinating milestone: it’s technically the first launch ever of a full-flow staged-combustion (FFSC) rocket engine. Whether or not the development hell Raptor required is or was worth it to SpaceX, the company has become the first and only entity on Earth to develop and fly a FFSC engine, beating out the national space agencies of both the United States and Soviet Union, both of which built – but never flew – prototypes.
Instead of inexplicably shelving a mature prototype development and test program, SpaceX iterated through several subscale Raptor prototypes, test-fired the engines for more than 1200 seconds total, used that data to design and build full-scale Raptors, and finally sped into a hardware-rich test campaign with six (soon to be seven) new engines. After SpaceX settled on a full-flow staged-combustion cycle and methane/oxygen (methalox) propellant, Raptor conducted its first full-scale tests all the way back in 2014, performing preburner flow and ignition tests at NASA’s Stennis Space Center.
Two years and many additional subcomponent tests later, SpaceX successfully performed the inaugural static fire test of its first completed subscale Raptor, a huge milestone for any rocket engine. In the 12 months following its first static fire (September 2016), SpaceX performed dozens of static fire tests with several subscale engines, putting the new propulsion system through >1200 seconds of combined testing.
A year after that, SpaceX was still testing subscale engines but the first full-scale Raptor engine was just a few months away from completing assembly in Hawthorne and heading to McGregor to kick off full-scale static fire testing. Indeed, four months after CEO Elon Musk’s September 2018 update, Raptor serial number 01 (SN01) shipped to Texas in late January and successfully ignited for the first time on February 3rd. SpaceX’s finalized full-scale Raptor engine is designed to produce more than 2000 kN (450,000 lbf, 200 tons) of thrust at full-throttle.
Since that inaugural ignition, SpaceX’s propulsion team – perhaps to their detriment, under orders from Musk – pushed SN01 and several of its successors to their limits as quickly as possible, resulting in severe, irreparable damage in several cases. On the other hand, the no-holds-barred, ‘hardware-rich’ (i.e. destructive) test program has allowed SpaceX to relatively quickly solve several major bugs that prevented the engine from passing longer test fires.
Raptor SN05 was originally expected to support Starhopper’s first flight(s) but had to be passed up after suffering damage in one of its final June 2019 acceptance tests. Raptor SN06 became the first engine – likely thanks to tweaks afforded by data gathered from its failed brethren – to pass all of those acceptance tests, leading to its eventual installation on Starhopper in early July.
Raptor’s impressive development culminated on July 25th with the engine’s first untethered flight while attached to Starhopper, a 9m-diameter (30 ft) low-fidelity prototype that is more or less a mobile test stand for the next-generation SpaceX engine. Raptor is now the only FFSC engine in history that has powered a flight-capable vehicle’s launch and landing, even if said flight featured an apogee of just 20-30 meters (65-100 ft).
“In full-flow staged combustion (FFSC), even more complexity is added as all propellant that touches the engine must necessarily end up traveling through the main combustion chamber to eke every last ounce of thrust out of the finite propellant a rocket lifts off with. As such, FFSC engines can be about as efficient as the laws of physics allow any given chemical rocket engine to be, at the cost of exceptional complexity and brutally difficult development.“
SpaceX delays Starhopper’s first flight a few days despite Raptor preburner test success
For more on what exactly makes full-flow staged-combustion engines uniquely capable and challenging to develop, the subject has been covered at length in past Teslarati articles.
According to Musk, the next major challenge facing Starhopper and (presumably) Raptor SN06 is far more ambitious 200-meter (650 ft) hop and flight test that could happen as soon as the first half of August.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
The next thing I’ve noticed, and this might be controversial, is that Nav has gotten even worse.
I think that might actually be a good thing; Tesla seems to be adjusting it. They just need to adjust it the opposite way.
The car is taking extremely strange routes to very… https://t.co/UHg3tVfNA2
— TESLARATI (@Teslarati) June 16, 2026
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.
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.”
🚨 A Tesla Cybertruck, which is illegal to drive in the UK due to safety concerns, has been seized by police in Greater Manchester
“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… pic.twitter.com/cqhdPok3DM
— TESLARATI (@Teslarati) June 16, 2026
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.
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.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
