News
[UPDATE] Tesla Model S Struck By Lightning While Charging
A Model S disabled by lightning while charging must wait at least one day for Tesla technicians to figure out what went wrong and restore it to service.
UPDATED June 6
It’s been a week since Sarah Day’s Model S got struck by lightning while she was at a SuperCharger facility. So far, she reports Tesla really has no idea what happened to her car, but the technicians at the local Tesla Service Center have been kept busy trying to repair it.
She understands the battery has been removed and sent off to the factory in California, where Tesla engineers “are almost giddy to get their hands on it,” she says. Apparently this is a first of its kind event and the company is putting every effort into trying to understand what happened. Sarah has been told that there may be an official announcement from Tesla when they get it all figured out.
In the meantime, she says “All eyes are on Columbus.” The incident occurred in Ohio, not Georgia as I originally thought. She has asked to be provided with a full technical analysis of what happened to her car and what it will take to fix it when that information becomes available.
For now, there seems to be no correlation between the lightning strike and the fact that her car was charging at the time. It seems Sarah was just unlucky that the lightning came so close. It may be cool to be the center of attention at Tesla headquarters for a little while, but I think by now she would prefer to have her car back so she can get on with her life.
Original post
A Model S struck by lightning while charging will have to wait at least one day for Tesla technicians to bring it back to life and figure out what happened. Sarah Day was charging her Tesla Model S at a Supercharger location near Columbus, Georgia [Edit: The location of the event occurred at Columbus, OH and not Columbus, GA as originally published] on Sunday morning when a lightning bolt hit very close by. Her first indication that something was wrong came when her BlackVue dash cam lost power. Here’s how she describes what happened next:
“I heard the crash, and just a second or two after about 9 errors popped up on the dashboard. Some of them were low charge warnings, saying it would disable some functions. Others were on how the car needs to be serviced. I was also getting that the car can’t be charged, and that the 12 volt battery is low.
“After the storm died down I got out of the car. The charging port wasn’t lit up, and when I tried to remove the cable it wouldn’t come out. I still had most of the functions in the car, including the touchscreen. The other car that was charging just a couple stalls down from me was completely fine and drove away, though I didn’t get to talk to that owner afterwards.”
Sarah called Tesla but had trouble getting through due to high call volume. The company agreed to send a tow truck, but before it got there, the 12 volt battery failed and the touchscreen shut down. When the tow driver arrived, he attempted to charge up the battery but it took two attempts before the touchscreen came back to life. Even then, the charging cable still would not disconnect from the car. Sarah couldn’t get the sunroof to close, either.
Since the car couldn’t be towed with the charging cable connected, Sarah had to leave her car at the Supercharger station with the sunroof partially open. There was nothing more she could do until the local Tesla service station opened for business on Monday morning.
Although Sarah wasn’t happy about her car being disabled, she can’t say enough good things about Tesla service and support people who took her phone calls.
“Tesla customer service was amazing. They were very responsive, and offered to rent me a car from enterprise so I could come home. I said I would rather stay with the car for a couple days to see how it all played out. I am from Atlanta and I was visiting a friend in Columbus, and I didn’t want to be that far away from the car in case of any issues.
“They offered to put me up in a hotel for a night, and also to get me a taxi or Uber ride. I decided I’d just stay with my friend, but they sent the Uber driver over for me. Also, the service center in Marietta, GA has been in contact with me to see how things are going. I know them pretty well, as well as one of the technicians. They have been incredibly helpful and supportive, though they can’t really do anything from there.”
The local Tesla service center will send a technician Monday morning to get the charging cable disconnected and bring the car in to be checked over. Sarah was told that each Supercharger has multiple relays and sensors to protect the cars from surges. At this point, she has no explanation for why her car was disabled, but expects a full report on Monday. She has complete confidence in Tesla service personal to identify the problem and get her car functioning properly again.
“They usually are pretty thorough with their descriptions of what went wrong. I’m hoping that it’s something simple. The technician in Marietta says the car may have sensed the large external voltage spike and disconnected everything as a safety precaution, but I don’t know if that would cause the charging port to malfunction.”
Thanks to Sarah Day for sharing with us details of her experience while she was in the middle of being stranded far from home. We will update this report when more information becomes available.
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.
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.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
