---
title: "Dutch Forensic Lab Hacks a Tesla, Finds Crash Data Automaker Didn’t Share"
description: "Dutch investigators \"reverse engineered\" data logs from a Tesla involved in a rear-end crash."
date: "2021-10-22"
modified: "2021-10-22"
authors:
  - name: "Peter Holderith"
    job_title: "Contributor"
    link: "https://www.thedrive.com/authors/peter-holderith"
url: "https://www.thedrive.com/tech/42834/dutch-forensic-lab-hacks-a-tesla-finds-crash-data-automaker-didnt-share"
categories:
  - "Car Tech"
  - "Electric Vehicles"
  - "News"
  - "News by Brand"
  - "Tesla News"
tags:
  - "Electric Vehicle"
  - "Tesla"
---

# Dutch Forensic Lab Hacks a Tesla, Finds Crash Data Automaker Didn’t Share

![](<https://www.thedrive.com/wp-content/uploads/images-by-url-td/content/2021/10/tesla-autopilot-dutch-find-tesla-hiding-data-lead.jpg>)
*\<em\>www.thedrive.com</em>*

A collision involving an [Autopilot](<https://www.thedrive.com/tech/42736/feds-order-tesla-to-justify-ota-updates-instead-of-recalling-cars>)-engaged Tesla in the Netherlands has snowballed into something of much more significance. What started as one of the California automaker's vehicles rear-ending another car with its advanced adaptive cruise control system activated, according to authorities, has turned into the Dutch government's forensics lab cracking into the car's black box. What did it find? Allegedly, more than Tesla had been sharing before.

According to a story first reported by [*Reuters*](<https://www.reuters.com/business/autos-transportation/dutch-forensic-lab-says-it-has-decoded-teslas-driving-data-2021-10-21/>), the Netherlands Forensic Institute has discovered that Teslas carry a great deal more data about conditions leading up to crashes than has been previously disclosed. And it took some cracking to get there.

The [NFI's decryption](<https://www.forensischinstituut.nl/actueel/nieuws/2021/10/21/opgeslagen-data-in-autos-bevatten-een-schat-aan-informatie-voor-strafrechtelijke-onderzoeken>) hinged on a collision where a driver reportedly had Autopilot engaged in heavy traffic, according to *Reuters*. But because the driver was supposedly following too closely behind another car, neither the driver nor the Tesla could stop in time when the lead car braked suddenly. The Tesla *did* warn the driver to take back control, the NFI found, but there just wasn't enough time.

Investigators "reverse engineered" data logs from the vehicle and claimed that although Tesla had been providing them with the information they requested previously, the [California company](<https://www.thedrive.com/news/42810/tesla-cybertruck-prototype-spotted-with-first-updates-since-its-reveal>) wasn't necessarily being totally transparent, *Reuters* reported. The NFI told the outlet that it found "far more data than investigators had previously been aware of."

Despite the automaker complying with requests for data from the Dutch government, it also "left out a lot of data that could have proven useful."

![message-editor%2F1634841715010-teslaautopilotdutchfindteslahidingdata.jpg](<https://www.thedrive.com/wp-content/uploads/content-b/message-editor/1634841715010-teslaautopilotdutchfindteslahidingdata.jpg>)
**Tesla**

"Tesla... only supplies a specific subset of signals, only the ones requested, for a specific timeframe," *Reuters* reported, quoting an NFI report, "whereas the log files contain all the recorded signals."

*The Drive* reached out to Tesla with a request for comment and will update this story if we hear back, however it's worth noting that Tesla no longer has a communications department and doesn't respond to media inquiries.

It's unclear what sort of data Tesla originally provided to the Dutch investigators, however, *Reuters* reported that if a Tesla gets in a crash, the vehicle's owner [can request data from the automaker](<https://www.thedrive.com/tech/8895/tesla-uses-autopilot-data-to-defend-itself-but-what-about-driver-privacy>) to help clarify what happened.

The NFI said it was able to decrypt data from all current Tesla production models—although it did not specifically state which Tesla model was involved in the collision—and that these findings were shared at a conference of the European Association for Accident Research.

Tesla doesn't disclose what or the scope of data it's shared with law enforcement and government agencies in the past when collisions such as these have occurred, especially when Autopilot might've been involved. Secondhand reporting by police [has previously shown](<https://www.thedrive.com/news/20912/cause-of-tesla-autopilot-crash-into-fire-truck-cause-determined-report>) the California company's willingness to provide information about Autopilot engagement durations, steering wheel contact, and braking data (sometimes when [a warrant or two gets involved](<https://www.thedrive.com/tech/40250/elon-musk-denies-autopilot-use-in-fatal-tesla-crash-as-feds-investigate-police-seek-warrant-for-data>)). However, the Dutch report claims that, in this case, Tesla was not showing its entire hand.

And it's a case where a government entity is taking matters into its own hands—via "[hacking](<https://www.theverge.com/2021/10/21/22738747/tesla-driving-data-hack-dutch-investigators-autopilot>)," as *The Verge* described it—when it feels a tech company isn't being forthright. With more and more cars coming equipped with advanced safety technology, more and more authorities could demand these data logs in the event of collisions. It's possible that what the NFI did could become standard procedure in certain places.

*Got a tip or question for the author? You can reach them here**: peter@thedrive.com.*

## Author
Peter Holderith is a former staff writer for The Drive. He enjoys covering the regular news cycle, writing reviews, and hunting down long features on obscure pieces of automotive history.

### Author social links  
[LinkedIn](<https://www.linkedin.com/in/peter-h-5ba447192/>)  
[Twitter](<https://twitter.com/_baldtires>)