How many people died? Why counting disaster fatalities is harder than it looks

Counting disaster fatalities is a complex process that involves numerous challenges. To begin with, it is essential to identify the event itself and understand the causal pathway that led to the fatalities. For instance, during Typhoon Maysak in southern China in July 2026, heavy rainfall caused flooding, resulting in the breach of a reservoir embankment and flooding of a snake-breeding farm.

Around 800-900 snakes escaped, and at least one person died due to a snakebite. However, delays in accessing medical care contributed to the fatality.

While defining the event and causal pathway may seem straightforward, it is not always easy. Disaster databases often link deaths with a particular hazard event, including direct and indirect consequences. Consequently, a single fatality may occupy several positions in a causal chain, occupying different labels in varying interpretations.

For example, the same fatality may be categorized as a "snakebite death" in a health or mortality registry, a "reservoir breach consequence" in infrastructure analysis, a "rainfall-related death" or a "flood-related indirect death" in a disaster database. None of these labels are inherently incorrect, as each layer may legitimately produce a different label.

The difficulty does not end with defining the event and causal pathway. Disaster databases typically use the event as their basic unit of analysis, which can lead to confusion when hazards cascade or occur simultaneously. A tropical cyclone, for example, can generate heavy rainfall, flooding, landslides, infrastructure failures, and secondary impacts. A single fatality may result from various links in that chain.

Thus, counting disaster fatalities is far more complicated than it may initially appear. It requires careful consideration of the event itself, the causal pathways leading to fatalities, and the challenges associated with defining and interpreting data.