Connect with us

News

SpaceX preparing giant crane to assemble Starship’s first Florida launch tower

SpaceX has begun staging parts of a massive crane it needs to stack Starship's first Florida 'launch tower.' (@StarshipGazer)

Published

on

SpaceX has begun staging and assembling parts of a giant crane it will soon need to stack Starship’s first East Coast launch tower and install other major launch pad components.

The presence of the base of that crane at SpaceX’s NASA Kennedy Space Center (KSC) Launch Complex 39A was visually confirmed by NASASpaceflight.com photographers during a weekly aerial tour of the area on June 3rd. Four days later, Teslarati photographer Richard Angle observed more major crane components on their way to Pad 39A, including the crane’s cabin.

More likely than not, the crane SpaceX or its contractor has begun assembling at 39A is a Liebherr LR 11350, the same kind of crane the company used to assemble Starship’s first orbital launch site and tower in South Texas. In fact, given how few LR 11350s there are in existence, it’s entirely possible that it’s the exact same crane. Assembly of that crane began around April 2021 and took a month and a half, at which point it was finally ready to lift an extended boom long enough to assemble a tower almost 500 feet (~150 meters) tall.

Part of SpaceX’s massive LR 11350 crane is visible on the right. (NASASpaceflight – bocachicagal)

Pad 39A’s Starship launch tower is expected to be very similar to Starbase’s, although it will undoubtedly carry over numerous design changes thanks to lessons learned while building and outfitting the first tower. In fact, SpaceX has already assembled five of the nine individual sections that will eventually be stacked to form that tower, and one such change is already obvious. Instead of stacking each tower section as soon as its barebones framework is complete, SpaceX is taking a more methodical approach to its second launch tower. In an apparent attempt to limit the amount of work that needs to be done at Pad 39A itself, each of those segments is being thoroughly outfitted with secondary structures (ladders, doors, walkways, frames, raceways, etc.) before stacking.

SpaceX may even pre-install most of the thousands of feet of plumbing needed to connect a Starship to ground systems located around 90 meters (~300 ft) below it. Once stacked, each section – including all those partial propellant and gas lines – will still need to be joined together, but that process should be far easier than fully installing all the systems the tower needs to do its job. Outfitting Starbase’s launch tower, for example, took SpaceX around half a year and, to some extent, is still ongoing 11 months after the final stack. That likely explains why Starship’s 39A tower section assembly appears to be taking more time. With any luck, partially combining the outfitting and section assembly stages will significantly expedite final assembly, as far less work will need to be done at extreme heights or require a skyscraper-sized crane.

Advertisement
SpaceX’s Starship launch tower was stacked to its full height on July 28th. (@StarshipGazer)

Through Starbase, SpaceX has already demonstrated the ability to stack a Starship launch tower from its unoccupied concrete base to its final height of ~145 meters (~475 ft) in about two months flat. While SpaceX will have to slalom its way around Pad 39A’s busy launch manifest, there’s no reason to believe that Starship’s first Florida launch tower won’t be stacked at least as quickly.

Aside from the arrival of crane parts, SpaceX has also made great progress on the Starship launch site itself. In the last few weeks, the company appears to have completed several significant concrete pours on the tower base. SpaceX has also installed all six of the pedestal-like orbital launch mount’s legs after months of foundation work. Elsewhere at Cape Canaveral, a different team has made excellent progress assembling the massive donut-like platform that will sit on top of those legs. Due to its extreme weight (possibly around 300 metric tons, per Elon Musk’s comments on the Starbase mount), the same LR 11350 crane will also be needed for that major installation milestone.

Starbase’s orbital launch mount. Starship’s Florida mount has incorporated many design changes. (NASASpaceflight – bocachicagal)

Plenty of parts are still missing, of course. Four tower sections still need to be assembled. Starship’s first Florida launch tower will need its own set of two ‘chopstick’ arms for lifting and (maybe) catching Starship and Super Heavy, as well as a third swinging quick-disconnect arm to connect Starship to ground systems. Aside from delivering several new tanks, SpaceX has also made no apparent progress on adding a massive methane propellant farm to Pad 39A, and it’s possible that the pad’s oxygen farm will also need to be expanded. Propellant storage has proven to be a major headache for SpaceX at Starbase.

Nonetheless, SpaceX is making great progress on most of the most difficult parts of Starship’s first Florida launch site, and there’s a good chance that just like its launch mount, work on the pad’s tower arms is already underway somewhere offsite. A great deal of work remains to be done but SpaceX is still well on its way to launching Starships out of Kennedy Space Center in the not-too-distant future.

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