Connect with us

News

SpaceX CEO Elon Musk lays out Starship’s path to orbit with sights set on 2020 debut

Starship heads to orbit atop a Super Heavy booster. (SpaceX)

Published

on

Speaking on September 28th, SpaceX CEO Elon Musk sketched out a fairly detailed picture of Starship’s path to orbit, from the first flight of the first full-scale prototype to the spacecraft’s inaugural orbital launch atop a Super Heavy booster.

Incredibly, Musk was persistent with claims that he has challenged SpaceX’s Starship teams to conduct the next-generation rocket’s first orbital launch within six months, drawing a line in the sand around April 1st, 2020 (?). How, then, does the SpaceX CEO foresee the next year or so playing out?

A whole lotta ‘Ships

As is the company’s signature, Musk confirmed that the Starship development program will continue to be highly distributed, hardware-rich, and focused on an iterative and continuous process of learning by doing. Starhopper is perhaps the best emblem of this methodology, defying almost every conceivable aerospace industry norm to successfully build and repeatedly fly what was essentially a rocket built outside by water tower welders.

Starhopper may have scarcely been meant to fly at all, serving almost entirely as a proof of concept and learning experience, but Musk strongly suggested that future Starship prototypes will replicate its highly iterative, learning-on-the-job approach to development. In short, much like SpaceX has nearly completed Starship Mk1 (and Mk2) from scratch in less than six months, SpaceX’s development strategy involves building a lot of Starship prototypes as quickly as possible.

Specifically, Elon Musk stated – in his opinion – that SpaceX will likely attempt its first orbital Starship-Super Heavy launch immediately after Starship Mk1’s first flight attempt, a suborbital launch to ~20 km (12.5 mi). Assuming that test – far more critical than any of Starhopper’s travails – is successful, the very next Starship flight could be an orbital launch attempt.

Starship Mk1 is pictured here on September 27th, less than half a day after technicians stacked the prototype’s two halves. (Teslarati – Eric Ralph)

First and foremost, Musk was pretty clear that the rough schedule he laid out was a “stream of consciousness”. Indeed, the eccentric CEO contradicted (or updated) himself over the course of answering the same question, stating that “[SpaceX] would fly to orbit with [Starship] Mk3” before saying that that it would actually be “Mk4 or Mk5”. Musk is still undoubtedly set on announcing gobsmackingly ambitious schedules for his projects, but it’s worth noting just how serious he seemed while discussing Starship’s development timeline.

He noted that SpaceX will likely “have [Starship] Mk2 built within a couple of months – or less”, referring to the second prototype currently in the late stages of integration at the company’s similar Cocoa, FL facilities. Additionally, Musk indicated that Starship Mk3 – yet to begin construction in Boca Chica – could be finished as few three months from now (around the start of 2020), with Starship Mk4 – to be built in Florida – could be just one to two months behind (NET Feb/March 2020). Correcting his previous statement, whether intentional or not, Musk also added that SpaceX’s first orbital Starship launch attempt would likely involve either the Mk4 or Mk5 prototype and occur “less than six months from now”.

As a slight consolation to the eyewateringly ambitious timeline he laid out, Musk qualified his “six months to orbit” target by acknowledging that it would only be achievable “provided the rate of design and manufacturing improvement continues to be exponential”. If that remains the case, as he believes it has been over the last six or so months, then SpaceX could be ready for the first orbital Starship launch attempt as few as 6-9 months from now – sometime in the first half of 2020.

Advertisement

A lot will undoubtedly have to go very right for that to remain anywhere within the realm of plausibility. This includes the rapid maturation of Starship’s Raptor engine and vacuum-optimized variant, the successful completion of Starship Mk1’s 20km flight test, the assembly and static fire of the first Super Heavy booster(s), the construction of brand new orbital launch facilities, and the FAA’s approval of all aforementioned flight operations.

Needless to say, the odds are heavily stacked against Musk’s goal of reaching orbit within six months. There is undoubtedly a chance that SpaceX can pull it off, even if success would essentially involve constructing a bridge while driving off a cliff. However, the most important thing to note is that even if Elon Musk is a factor of 1.5, 2, 3, or even 4 times off and Starship reaches orbit for the first time 12 or 18 or 24 months from now, it will still have been an incredibly brisk period of development for a rocket as large, high-performance, and ambitious as Starship/Super Heavy.

It should also be made clear that, while it’s utterly beyond the present capabilities of NASA and other space agencies/companies of the 21st century, Saturn V went from paper to its first orbital launch in just five years. Depending on how one perceives Starship development, it could be said that SpaceX began development – particularly marked by Raptor engine prototype testing – as early as 2016. Suffice it to say that it’s far from impossible that Starship’s first orbital launch will happen next year, even if the challenges SpaceX faces are immense.

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

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 urges New Jersey owners to oppose new bill that could block Robotaxi

Published

on

Credit: Grok

Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.

The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.

According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.

Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.

The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.

In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.

Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.

In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.

Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.

Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.

This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.

As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.

Continue Reading

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