SWOV's website provides the opportunity of carrying out analyses of the crash database yourself. In the following we will explain a number of definitions and the meaning of a number of variables.
What is generally referred to as the 'crash database', actually consists of three different databases: crashes, parties, and casualties.
Examples:
A motorist loses control of the vehicle and ends up in a meadow. He does not get injured.
A multiple collision ('pile-up') involving six cars and a lorry occurs on a motorway. The guardrail is also heavily damaged. The driver and one passenger of the second car are slightly injured, and one passenger of the sixth car is admitted to hospital because of internal bleeding.
In both cases there has only been one crash. In the first case there was one party involved (the car) with one driver and no casualties. In the second case there were eight parties involved: six cars, one lorry, and one guardrail, with seven drivers and three casualties. In each crash one or more parties can be involved, and each party can have no, one, or more casualties. Figure 1 below illustrates this schematically.

Figure 1. Structure of the crash database
The heterogeneity makes it difficult to analyze 'crashes' integrally. It already begins at the level of elementary analyzing techniques such as a table. How do you visualize in one and the same table a crash with 1 party and a crash with 20 parties and, per party, varying numbers of casualties? This is not possible, which is why crashes are analyzed at three different levels: by crash, by party, and by casualty.