As already described, I drove up to the scene of the accident without accelerating. This is possible with my vehicle in Drive Mode B with the creep function. Excerpt from the manual:
This explains why the car moved forward even though no accelerator pedal was pressed. At the same time, it also shows that the processes coming from the drivetrain or the driver assistance systems are not mapped in any way in the accident data memory. This is where I see a significant gap in the ability to clarify accidents.
The values in the event data recorder
Shortly before the collision, the value of the accelerator pedal first goes to 30%, then to 90% and then 100%. This means that I should have mixed up the pedals for 1.5 seconds at an extremely slow speed. At the same time, the car hardly accelerated at all during this time, even though it has 150 kW. These values also have a lot in common with the other accidents. In all cases, the value 100% occurred exactly once at the time of the accident. Not twice, not even 97%, exactly 100% at the last entry. And why 100% only after 1.5 seconds, when I have mixed up the pedals and pressed them fully? With 30% of the wrong pedal you realize your mistake and there would have been 1 second left.
The accident data memory explicitly does not store the acceleration values set by the driver assistance systems but, according to the manufacturer, only the values requested by the driver via the accelerator pedal.
Extraordinary values
We now have accident data memories for 4 vehicles, one of which had a different previous owner who was involved in several accidents, so that we have a total of 9 accident data memory entries. Each of the other accidents has values in a one-step resolution. In my case, where the brake did not respond, the recorded positions of the accelerator pedal position are in a resolution with increments of 10. This is actually far too unnatural for a driver to only achieve values in increments of 10.
In contrast, entries 30 – 90 – 100
