News
SpaceX to demonstrate weekly launch cadence: 3 launches in 14 days
LC-39A undergoing repairs and tests after the launch of CRS-11. (/r/SpaceX)
SpaceX is in the process of preparing to launch BulgariaSat-1, with the first attempt scheduled for Saturday, June 17th between 2:10 p.m and 4:10 p.m. EST. BulgariaSat-1 will be Bulgaria’s second satellite ever and will act as a telecommunications hub in geostationary orbit, around 30,000 miles above Earth.
Following a highly successful launch and docking of the eleventh cargo mission of its Dragon spacecraft, Launch Complex 39A has since undergone routine checks to verify its condition and has likely been lightly repaired. The static fire for the upcoming mission is scheduled as early as tomorrow. Both the static fire and launch were pushed back two days due to a 48 hour delay of the CRS-11 launch.
The launch of BulgariaSat-1 is already exceptional for several reasons. First and foremost, the Falcon 9 first stage to be used in the upcoming mission has already flown once before, assisting in the successful launch of Iridium’s first ten NEXT satellites in early January of this year. It will thus mark the second time SpaceX has truly reused a Falcon 9 first stage. There has even been a bit of circumstantial evidence that the choice to launch on a recovered F9 resulted in BulgariaSat-1 being moved ahead of Intelsat 35e, which is now scheduled for no earlier than July 1st. Regardless, another successful reuse will be a boon for a SpaceX in the throes of an unprecedentedly busy year of launches by once again demonstrating the viability of their program of reuse and thus hopefully swaying more customers to take the leap to reused rocket cores.
The second reason, as touched on above, is that BulgariaSat-1 will mark the beginning of a two week period in which SpaceX could potentially conduct three separate launches, two at Cape Canaveral and one at Vandenberg Air Force Base. If successful, this would demonstrate weekly single-vehicle launch cadence, something that has not been seen in the launch industry in quite some time. This weekly cadence, if successful, will demonstrate a maturing company that is truly preparing for extraordinary launch cadence. By using two pads, one in California and one in Florida, SpaceX will still be able to provide two weeks between launches in order to prepare each launch site for the next launch, while effectively launching once a week. While Vandenberg Air Force Base can only support polar orbit launches, LC-40 is currently deep into the process of being repaired and reactivated following the failure of a Falcon 9 late last year.
With LC-40 preparing for reactivation sometime in August or September, SpaceX will find themselves at long last with two viable all-purpose launch pads in very close proximity to each other. By staggering launches on each pad and continuing to maintain the two week pad turnaround time after launches, SpaceX could theoretically begin to sustain regular weekly launches as few as three months from now. A successful weekly cadence this month could reinforce that such a sequence of events is a possibility.
Iridium NEXT 1’s Falcon 9 first stage after recovery in the Pacific Ocean. (SpaceX)
SpaceX has long been working to rapidly increase its ability to launch frequently, and this year has been an exceptional example of several pieces fitting together. The company has begun to use an automated flight termination system, which will allow them to rely less upon the availability of Cape Canaveral’s Range Officers while crafting their manifest and launch schedules. Normally, the flight termination system in rockets is monitored by an actual team of people who have barely a few seconds to decide if rocket telemetry is less than nominal and prevent what is effectively a large missile from impacting populated areas. SpaceX has replaced this with an arguably much safer approach dependent upon their mature autonomous avionics systems, simply meaning that computers on board their rockets and spacecraft automatically analyze telemetry and control vehicle performance and guidance. SpaceX has been testing this system in a way that is almost identical to Tesla’s method of installing inert autonomy software that can learn without actually controlling the vehicle, and it is consequently only now being implemented after SpaceX and the Air Force have a high degree of confidence that it will outperform its human colleagues.
The ultimate goal of this automated flight termination system (AFTS), as well as many other significant changes to both the hardware of pads and vehicles, is to eventually allow SpaceX to accomplish Elon Musk’s long fabled and oft-ridiculed goal of 24-hour reusability, and thus 24-hour launch cadence. SpaceX and the USAF have both stated that AFTS alone will likely allow Cape Canaveral to support up to 48 launches a year. While shared between ULA and SpaceX, even 36 launches a year would effectively leave SpaceX with a shrinking launch manifest and significantly increased revenue and profit. This would speculatively allow them to more rapidly develop their pursuits of Mars, a vast constellation of broadband satellites, and more.
BulgariaSat-1 being prepared for launch. (SSL)
Nevertheless, this is all of course speculation and dependent upon many things going well. If SpaceX is able to successfully launch BulgariaSat-1 on June 17th, Iridium NEXT 2 on the 25th, and Intelsat 35e on July 1st, they will have successfully demonstrated the ability to support a weekly launch cadence and will have to do little more than wait for the availability of a second East coast pad to begin to take full advantage of it.
With ten launches scheduled between now and October and ten more launches scheduled between October and the end of December, it is guaranteed to be one incredible year for SpaceX and their fans.
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.
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.
Tesla urges New Jersey owners to oppose new bill that could block Robotaxi
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
