News
SpaceX Crew Dragon switches ports to make room for Boeing’s Starliner do-over
Update: For the second time, a SpaceX Crew Dragon spacecraft has successfully swapped International Space Station (ISS) docking ports in orbit – this time to make way for Boeing’s planned Starliner Orbital Test Flight do-over.
If Starliner’s second orbital flight test is more successful than the first, which failed almost immediately after launch, the Boeing spacecraft will launch no earlier than July 30th, rendezvous and dock with the ISS, and spend approximately five days at the station before attempting to return to Earth. Once Starliner departs, freeing up the forward docking port, SpaceX and NASA will likely have to perform a second Crew-2 port relocation, moving Dragon back to its original port to set the stage for the CRS-23 Cargo Dragon resupply mission scheduled in late August.
SpaceX and NASA are on track for the Crew-2 Dragon spacecraft currently docked to the International Space Station (ISS) to perform a “port relocation” maneuver early Wednesday, effectively opening the door for Boeing’s Starliner flight test do-over.
Scheduled to launch on a United Launch Alliance (ULA) Atlas V rocket no earlier than (NET) July 30th, Boeing’s Starliner will be flying for the first time since the spacecraft’s near-catastrophic Orbital Flight Test (OFT) debut in December 2019. During Starliner’s inaugural test flight, a combination of inept Boeing software development, shoddy quality control, and inexplicably lax NASA oversight allowed the spacecraft to launch with inoperable software.
As a result, things went wrong mere seconds after Atlas V – which performed nominally – deployed Starliner. Almost as simple as using the wrong clock, the first software fault – something that would have been instantly caught with even the most rudimentary integrated systems test – caused Starliner to think it was in a different part of the OFT mission and waste much of its fuel with thousands of unnecessary thruster firings.
Aside from pushing Starliner’s maneuvering thrusters beyond their design limits, those unplanned and unexpected misfirings also threw the spacecraft off course, obfuscating Boeing and NASA’s ability to communicate and command the spacecraft and troubleshoot the situation at hand. Eventually, the company regained control of Starliner, but not before it had burned through most of its propellant reserves – precluding plans for to rendezvous and dock with the ISS.
Less than three hours before reentry, Boeing also uncovered a separate thruster-related software issue that could have caused the Starliner capsule to lose stability and re-impact its expendable trunk section after separation.
Ultimately, with so many issues and a failure to gather any kind of data related to operations at and around the ISS, NASA thankfully forced Boeing to plan to repeat OFT with Orbital Flight Test 2 (OFT-2). Scheduled to launch in December 2020 as of the second half of that year, OFT-2 ultimately slipped – both for scheduling and technical reasons – to March, June, and finally July 30th, 2021.

More than 19 months after Starliner’s ill-fated debut, NASA and Boeing are now almost ready for the spacecraft’s critical do-over. For unknown reasons, though, NASA and/or Boeing apparently need (or prefer) Starliner to use a specific docking port – the same port SpaceX’s second operational Crew Dragon spacecraft is currently docked to. According to NASA and Boeing, Starliner needs to use that forward docking port because it has not been qualified for zenith docking, which is a bit more complex. As a result, SpaceX and NASA have scheduled a port relocation maneuver around 7am EDT (UTC-4) on Wednesday, July 21st.
SpaceX’s first relocation occurred in early April to prepare for the arrival of a second Crew Dragon later that month. When Crew-1 Dragon departed a few weeks after the maneuver, it would leave the station’s zenith (space-facing) port free for a Cargo Dragon 2 spacecraft scheduled to arrive around one month later. Due to the station’s geometry and port layout, only the zenith port allows its robotic Canadarm2 arm to unload unpressurized cargo from Dragon’s trunk.
Already at the forward port, the Crew-2 Dragon will thus be moving to the zenith port for Starliner’s brief 1-2 week stay at the ISS. However, as may have become clear, Crew Dragon will then have to re-relocate to the forward port for any future Cargo Dragon missions – one of which happens to be scheduled to launch with an important unpressurized payload as early as August 29th.
Regardless of why, it’s hard to ever complain about seeing Dragons fly. Tune in around 6:30 am EDT (10:30 UTC) to watch Crew Dragon C206 maneuver around an orbital space station.
News
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
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.
Tesla is sending out this email to New Jersey Tesla owners, warning them that NJ could block autonomous vehicles, and to take action.
“Proposed legislation moving through Trenton right now would impose restrictions so severe that true driverless deployment would remain illegal.… pic.twitter.com/2bmY646AUL
— Sawyer Merritt (@SawyerMerritt) June 16, 2026
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.
News
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
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.
Cybertruck
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
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.