Connect with us

News

SpaceX says Starship Mk1 will test ‘skydiver’ landing before the end of 2019

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

Published

on

A senior SpaceX director says that the Starship Mk1 prototype could lift off for the first time before the end of 2019, a flight debut SpaceX hopes will successfully demonstrate the next-generation spacecraft’s exotic ‘skydiver’ landing method.

SpaceX is in the late stages of building the first full-scale Starship prototypes, known as Mk1 (situated in Boca Chica, Texas) and Mk2 (Cocoa, Florida). The Texas-based Mk1 prototype is by far the furthest along and featured prominently at CEO Elon Musk’s Starship update presentation on September 28th, having been stacked to its final height of ~50m (165 ft) for the first time just days prior.

It’s clear now that more than a little showmanship was involved in the work that lead up to Starship Mk1’s unveiling. Within a week or two of the event, SpaceX technicians had separated Starship’s nose and tail sections, removed all three Raptor engines, and uninstalled the ship’s wings and canards, among other things.

Starship Mk1’s nose and tail sections were separated on October 1st. (NASASpaceflight – bocachicagal)
Starship Mk1’s Raptor engines were removed and shipped to McGregor, TX or Hawthorne, CA on October 5th and 6th. (NASASpaceflight – bocachicagal)
Both Starship body flaps were removed on October 9th. (NASASpaceflight – bocachicagal)
Starship Mk1’s canards were removed on October 11th. (NASASpaceflight – bocachicagal)

Aside from the nose and tail section demate and removal of flaps, canards, and Raptors, the aero covers that were briefly attached to Starship’s exterior (raceways, canards, flaps, legs) were also removed. One raceway cover may or may not have been a casualty of high winds but all of the above hardware was carefully stored on the ground surrounding Starship Mk1 and is clearly meant to be installed more permanently in the coming weeks.

Nevertheless, Starship Mk1 obviously has a decent ways to go before it can be seriously considered flight-ready. On a positive note, aside from several days spent undressing Starship, SpaceX’s South Texas team (and others traveling from Florida and California) have been working 24/7 in the weeks since Musk’s presentation.

The last two weeks of Starship Mk1 activity have centered around installing the numerous crucial bits and pieces the rocket will need to function. This has included thousands of feet of power cables, avionics wiring, and propellant feed and transfer pipes; industrial-scale power controllers and flight computers, and much more.

Advertisement
A panorama of Starship Mk1’s business end and tank section. Recent work has focused on outfitting Mk1 with an array of wiring and piping, much of which is visible here. (NASASpaceflight – bocachicagal)

The sheer quantity and range of sizes of piping being installed on Starship Mk1 all but confirms that the rocket will be a high-fidelity prototype capable of testing a wide range of capabilities related to autogenous pressurization and Raptor engine ignition. The mirrored presence of three sets of smaller pipes on the vehicle’s raceway (essentially a utility corridor) is a strong sign that Raptor and Starship’s smaller header tanks and COPVs (located in Mk1’s nose section) are closely related.

Some of the excess hot gas produced by Raptor may be tapped to supply COPVs that can then be used to reignite the engines in-flight. More likely, the small pipes are more of a one-way feed line from Starship’s header tanks to its Raptor engines and – as Musk has indicated – the cryogenic liquid propellant in those header tanks will be gasified with electric heaters or gas generators.

Most recently, SpaceX technicians have been focused on installing Starship Mk1’s colossal flap hinges and leg mounts, all made out of thick steel plates. (NASASpaceflight – bocachicagal)

Starship gymnastics

Given all of the above, close followers were already readily aware of the fact that Starship Mk1 needed some significant work done before it would be ready for flight. On October 22nd, SpaceX Senior Director Gary Henry confirmed these suspicions, indicating that Starship Mk1’s 20 km (12 mi) flight test debut was now scheduled no earlier than two months from now (December 2019).

According to CEO Elon Musk and other SpaceX engineers, that 20 km flight debut is designed to prove that Starship’s radical new approach to flight and landing is viable. Musk has repeatedly described that Starship will in no way be an actual space plane and has stated that its ‘wings’ and ‘canards’ are not intended to be airfoils or wings. Instead, Starship will reenter Earth’s atmosphere, slow its horizontal velocity to near-zero, and proceed to free-fall straight down, using its fore and aft flaps to control its trajectory in the same way that skydivers use their body and limbs.

This bizarre approach will be capped off with an aggressive landing maneuver in which Starship will ignite its engines, wildly thrust-vector and swerve to cancel out the horizontal velocity imparted by that sideways ignition, and land vertically on Earth (or Mars). In theory, this strategy will radically reduce the amount of fuel Starship needs to land in atmospheres, but it’s far removed from anything SpaceX has attempted with Falcon 9 and Starship Mk1’s first flight will hopefully prove it to be a viable solution.

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