Onderzoek mobiele apparaten

Gewiste Whatsapp, sms, call-logs, GPS, TomTom

Bel direct:
088 - 12 11 11 1

Real life case

 

A decrypted TomTom triplog was used to do some measurements to calculate speed and distance just before a traffic accident happened. In this real life case, there was a driver who was not driving to fast and was in time to hit the breaks.
He should have been able to avoid a collision, but he was hit by a car behind hem, which made him hit the car in front of him.

Total distance of the route we took is 613.54 meters.

Timeframe is 2012-04-01 16:12:00 to 16:12:29. (16:12:29 is the last point in motion, after that you can see a lot of “ pins” more or less on the same spot  (probably a 4 by 4 meter range where al gps-fixes are found.)


If Google earth gives us good information we can calculate that the speed on this part was an average of: 613,54 meter / 29 seconds = 21,156 meter/second = 76,163 Km / h.

That is way beyond the speed limit of 110km/h at that location (but still an avarage)

 

 

 

 

 

If we take the last seconds before the crash:

 

16:12:19  94,68  km/h
16:12:20  88,92  km/h
16:12:21  79,2    km/h
16:12:22  66,96  km/h
16:12:23  51,84  km/h
16:12:24  36,0    km/h
16:12:25  25,2    km/h
16:12:26  10,8    km/h
16:12:27    7,2    km/h
16:12:28  25,2    km/h (speed goes up. The car got hit from behind)
16:12:29  14,4    km/h
16:12:30   

 

(measurements where made by pointing out in google earth, so not very accurate. We are still looking for a way to convert a triplog.kml file into a file with good speed and distance-calculations)

You can open the actual triplog.kml file in google maps here.

 

Or you can download it as a .KML file