Key Evidence Disappears from Tesla Involved in Bizarre Crash, And Nobody Can Explain Who Took It
You're a taxi driver with 12 years of experience. One morning, you're backing into a parking spot in a quiet Norwegian square. Suddenly, without warning, your car lurches forward. It smashes through outdoor café seating. You panic. Then, seconds later, it happens again, this time rocketing to 90 km/h, launching off stone steps, and slamming into a kiosk.
You survive. Miraculously, nobody dies.
And then... the one piece of hardware that could prove what really happened inside your Tesla's brain simply... disappears.
That's not the opening of a cyber-thriller novel. It's exactly what happened in Bergen, Norway, and it raises questions every Tesla owner, EV enthusiast, and safety regulator should be paying attention to.
What Happened in Bergen?
In the early morning hours of May 13, 2023, a Tesla Model Y taxi crashed violently through Torgallmenningen, one of Bergen's busiest public squares. Dashcam footage (which you can still find online) shows something that defies easy explanation:
- The driver was reversing into a parking spot when the car suddenly accelerated forward
- It jumped the sidewalk and smashed through outdoor seating at Lille Bar
- After a brief pause, it accelerated again, hitting 90 km/h down a pedestrian street
- Two pedestrians fled into a supermarket to avoid being hit
- The car hit a monument base, launched up stone steps, and crashed into a Narvesen kiosk
Remarkably, no one was killed. Had this happened a few hours later, the square would have been packed with shoppers and tourists.
The driver, a 12-year taxi veteran who was sober and fully cooperative, said from day one that "something was wrong with the car." He was initially charged with negligent driving and lost his license. But in December 2024, Norwegian police dismissed the criminal case, stating they could not "establish with sufficient certainty that the traffic accident resulted from driver error, nor can technical malfunction be ruled out with certainty."
The driver was declared innocent.
But the mystery was just beginning.
The Data Gap and the Brake Light Mystery
Here's where things get... weird.
Tesla's Event Data Recorder (EDR) shows the accelerator pedal was pressed throughout both collisions. On the surface, that sounds like a classic case of "pedal misapplication", the driver hit the wrong pedal.
Except for one glaring contradiction: the brake lights were clearly illuminated during both collisions.
Norway's Road Authority attributed this to the car's automatic collision-avoidance braking system activating but being "overridden" by continued accelerator input. In other words: the car was trying to brake, but the accelerator signal overrode it.
But independent experts aren't so sure.
Simen Huse, one of only five authorized Bosch CDR tool operators in Norway, and researchers from Sintef (a respected research institute) argue that electronic malfunctions, software errors, or voltage spikes could produce the same accelerator signal in the data, without the driver ever pressing the pedal.
This is a big deal. If a software glitch can make it look like the driver was flooring it when they weren't... well, that changes everything.
Tesla claims it lacks six seconds of data from the interval between the first and second impacts. The company says the vehicle stopped uploading after the first collision.
Six missing seconds. Brake lights on. Accelerator signal present. And then...
The Vanished Network Card
Fast forward to when the vehicle was finally sent to independent data analyst Simen Huse for examination.
The car had been transported over 500 kilometers from Bergen's Road Administration facility to Huse's lab in Østfold. When Huse opened up the car, he said he "couldn't believe his eyes."
The dashboard area had been stripped. Multiple plastic fittings were removed. Loose screws scattered on the floor. Electrical connections in the ceiling area had been severed.
And most critically, the network card was completely gone from the main computer.
This isn't some random part. The network card is the exact component responsible for handling continuous data storage and transmission between the vehicle and Tesla's servers. It's the piece that would have stored or transmitted the data from those missing six seconds Tesla claims not to have.
No one has been able to explain who removed the card, or when.
The defense attorney, Torkjell Øvrebø, noted it's "highly unlikely" an experienced taxi driver would confuse accelerator and brake twice consecutively. He called for "a comprehensive independent investigation" and even suggested a police raid on Tesla's servers to recover the missing data.
Police have since announced they'll review their own investigation procedures. But the damage, and the evidence gap, may already be permanent.
A Pattern? The Florida Autopilot Crash Case
If this sounds like something out of a conspiracy theory... well, it's worth looking at what happened in Florida just last year.
In a fatal 2019 Autopilot crash case, Tesla told police and plaintiffs' attorneys that they did not have key crash data. For years, the company maintained this position.
Then a hacker, hired by the plaintiffs, found it.
Within three minutes of that Florida crash, the Tesla Model S had uploaded a "collision snapshot" (video, CAN-bus data, EDR data) to Tesla's servers. The car then deleted its local copy. Tesla was the only entity with access to that data.
When police asked for it, Tesla's own attorney told the investigating officer exactly what to write in his request letter, carefully wording it to exclude the collision snapshot. When police tried to extract data directly from the Autopilot computer at a Tesla service center, a Tesla technician claimed the data was "corrupted."
Forensic analysis later proved the data was intact, and had been accessed by Tesla that very same day.
A jury found Tesla 33% liable and ordered the company to pay over $240 million.
Now, I want to be clear: we don't know who removed the network card in the Norway case. The circumstances are suspicious, and the motive is obvious, but that's not proof.
What is clear is that a critical piece of evidence is missing, the investigation has been compromised, and Norwegian authorities need to take this far more seriously than they have so far.
What This Means for Tesla Owners
If you own a Tesla, or any modern connected vehicle, here's what you should take away from all this:
1. Your car knows more about a crash than you do.
Tesla vehicles continuously record and transmit data. In a serious incident, that data could prove whether a malfunction occurred, or point the finger at you.
2. That data might not be available to you.
Unlike a traditional car's black box, Tesla's data lives on their servers. You don't have direct access to it. And as the Florida case showed, getting it can be an uphill battle.
3. Documentation matters more than ever.
If you're ever involved in an incident, take photos, preserve dashcam footage (if you have it), and document everything. Don't assume the vehicle's data will tell the whole story, or that you'll be able to get it.
4. Independent investigation is essential.
Crash reconstruction should not rely solely on manufacturer-provided data. Independent experts who understand the vehicle's architecture, and its potential failure modes, need to be involved from the start.
What Norwegian Authorities Should Do Next
The Bergen case exposes a fundamental problem: who guards the guardians?
When a manufacturer controls the data, the hardware, and the narrative, investigations can be compromised, whether intentionally or through negligence.
Norwegian police have said they'll review their procedures. That's a start. But here's what really needs to happen:
- Forensic audit of the vehicle's data trail: Tesla's servers should be subpoenaed to determine what data was transmitted before and after the crash
- Chain of custody investigation: Who had access to the vehicle between the crash and Huse's examination?
- Independent technical review: Regulators need to work with experts who understand EV data architecture, not just rely on manufacturer interpretations
- Transparency requirements: Manufacturers should be required to provide raw, uninterpreted data to investigators and vehicle owners
The alternative is a system where the company that made the car gets to decide what evidence exists, and what doesn't.
The Bergen Tesla crash is more than just a strange news story. It's a cautionary tale about what happens when data ownership, hardware access, and crash investigation collide in the age of connected vehicles.
We may never know exactly what happened during those six missing seconds. The network card is gone. The data gap remains. And a taxi driver who insists "something was wrong with the car" will always wonder if the truth could have been found, if only the evidence hadn't disappeared.
What do you think? Have you experienced unexplained behavior in your Tesla or EV? Drop a comment below, I read every single one. And if you found this breakdown helpful, share it with someone who drives a connected vehicle. They need to know this stuff.
FAQs
Q: What happened to the Tesla in Norway?
A: A Tesla Model Y taxi crashed twice in Bergen in 2023, first into café seating, then into a kiosk at 90 km/h. The driver was cleared of wrongdoing, but the network card storing crash data later disappeared from the vehicle.
Q: Why is the missing network card important?
A: The network card handles continuous data storage and transmission to Tesla's servers. It would have contained data from six seconds Tesla claims it doesn't have, seconds when brake lights were on but the accelerator signal was active.
Q: Did Tesla remove the network card?
A: No one knows. The vehicle was transported 500 km to an independent lab, and when it arrived, the dashboard had been stripped and the card was gone. No one has claimed responsibility.
Q: Can Tesla delete crash data remotely?
A: Tesla vehicles can upload data to Tesla's servers and then delete local copies. In a Florida case, Tesla claimed it didn't have data that a hacker later recovered, showing the data existed on Tesla's servers all along.
Q: What should Tesla owners do after a crash?
A: Document everything, photos, videos, witness statements. Do not rely solely on Tesla's data. Consider hiring an independent expert who understands EV data systems.
Comments
Post a Comment