Connect with us

News

SpaceX delays Starlink doubleheader

Published

on

Update: To “allow additional time for pre-launch checkouts,” SpaceX has delayed Starlink 2-6 from January 30th to 8:15 am PST (16:15 UTC), January 31st and Starlink 5-3 from February 1st to February 2nd.

A pair of SpaceX Falcon 9 rockets are on track to round out the first month of 2023 and kick off the second with a Starlink double-header.

“To complete pre-launch checkouts,” SpaceX delayed its last launch of the month by 24 hours. The first Falcon 9 rocket will launch Starlink 2-6 and a D-Orbit rideshare payload no earlier than 8:29 am PST (16:29 UTC) on Monday, January 30th. The mission will lift off from SpaceX’s Vandenberg Space Force Base (VSFB) SLC-4E pad and head southeast, skirting the California and Mexico coast. In case of bad weather or a minor technical issue, a backup window is available at 12:31 pm PST.

As few as 35.5 or 39.5 hours later, a second Falcon 9 rocket will lift off from SpaceX’s Florida-based NASA Kennedy Space Center LC-39A pad around 3:02 am EST (08:02 UTC) on Tuesday, February 1st.

Advertisement

Starlink 2-6

Kicking off the pair, Starlink 2-6 will be SpaceX’s ninth Starlink rideshare mission since the company began manifesting third-party payloads on its internet satellite launches in June 2020. Falcon 9 will launch the mission’s main payload – a batch of 49 Starlink V1.5 satellites – to a semi-polar orbit that will see them cross Earth’s equator at an angle of 70 degrees. Ordinarily, the mission would carry 51 Starlinks, but SpaceX has removed a pair of satellites to make room for Italian space logistics company D-Orbit’s ION SCV009 spacecraft.

ION weighs around 160 kilograms (350 lb) on its own and is roughly the size of a large oven. D-Orbit designed the spacecraft to host fixed payloads and deploy rideshare satellites in orbit. It also has a propulsion system that allows it to provide “last-mile delivery services,” offering rideshare customers the ability to tweak the orbit their satellite ends up in. Space tugs like ION aim to give satellite owners some of the benefits of a dedicated rocket launch (custom orbit selection in particular) while retaining most of the cost savings rideshare launches enable.

A render of a D-Orbit ION vehicle.

After reaching orbit, Falcon 9 will deploy ION first, use thrusters to spin itself end over end, and then release all 49 Starlink satellites simultaneously. The spinning stage’s centrifugal force causes the satellite stack to naturally spread out within several hours. The satellites then use reaction wheels to stabilize their orientation, deploy solar panels to begin charging their batteries, and eventually use ion thrusters to climb to operational orbits.

ION SCV009 will attempt to test a new satellite separation system built by EBAD and demonstrate its ability to operate in very low Earth orbit (VLEO). The spacecraft will potentially lower itself to an altitude of 270 kilometers (170 mi).

Starlink 5-3

Starlink 5-3 will carry no rideshare payloads and will likely be nearly identical to Starlink 5-2, which SpaceX successfully launched on January 26th. The latest mission’s stack of 56 Starlink V1.5 satellites weighed 17.4 tons and was the heaviest payload SpaceX has ever launched. Starlink 5-3 is targeting the same orbit and will likely also carry 56 satellites.

Advertisement

Pad 39A last supported SpaceX’s fifth Falcon Heavy launch on January 15th and has been quickly converted back to its single-core Falcon 9 configuration for Starlink 5-3. After the Starlink mission, Pad 39A has at least two Dragon spacecraft launches scheduled before SpaceX will need to convert it back to a triple-booster configuration for Falcon Heavy’s sixth launch.

SpaceX is scheduled to launch Crew Dragon’s Crew-6 astronaut transport mission no earlier than February 26th, and Cargo Dragon’s Spx-27 cargo delivery mission on March 11th. Falcon Heavy is scheduled to launch the giant ViaSat-3 communications satellite no earlier than March 24th.

Tune in below around 8:25 am PST (16:25 UTC) to watch SpaceX Starlink 2-6 launch live.

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

News

Apple is developing the missing link for Tesla to get CarPlay: report

Published

on

Credit: Michał Gapiński/YouTube

A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.

Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.

A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.

CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.

Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:

The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.

Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.

This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.

Continue Reading