Skip to content

Landslide-Dam Failure

The two-stage natural-hazard cascade in which mass wasting dams a valley, impounds a lake, and later fails — releasing a downstream outburst flood usually larger than the landslide, because the unengineered barrier is itself the hazard's storage element.

Version
v3 · 2026-09-28 · History · 3 corrections
Domain-specific #
613
Domain group
Natural Sciences
Origin domain
Geology & Earth Sciences
Subdomain
Natural Hazards → Geology & Earth Sciences

Core Idea

A landslide-dam failure is the natural-hazard cascade in which a landslide, rockfall, or debris flow deposits material across a river valley, forming a temporary dam that impounds an upstream lake, which later fails and releases an outburst flood downstream. The distinctive is that a locally contained trigger creates a standing regional risk larger than itself. The barrier is unengineered — no spillway, heterogeneous debris, geotechnically unstable — and is itself the hazard's storage element.

How would you explain it like I'm…

The Rock-Pile Flood

Sometimes a hill slides down and blocks a river with a big pile of dirt and rocks. The water backs up into a lake behind it. The pile isn't strong like a real dam, so later it can break and a huge flood rushes down the valley, even bigger trouble than the slide was.

When Landslide Dams Burst

A landslide-dam failure happens in two steps. First, a landslide or rockfall dumps dirt and rocks across a river and blocks it, making a lake behind it. Later, that natural dam breaks and lets out a huge flood. The flood can be much bigger and reach much farther than the landslide itself. The dam is a jumble of loose rocks with no safe overflow channel, so it often fails within days or months, and nobody can tell exactly when. People may dig a channel to drain the lake slowly, watch the water level, and move people downstream out of danger.

Landslide-Dam Outburst Cascade

A landslide-dam failure is a hazard chain: a landslide, rockfall or debris flow blocks a river valley, the trapped water forms a lake, and the debris dam later fails and releases an outburst flood. The key idea is that a small, local event creates a lasting regional danger, and the eventual flood often reaches farther and carries more energy than the original slide. The dam is unengineered loose debris with no spillway, so many fail within days to months through overtopping, piping (water tunneling through) or slope collapse, but the exact timing is hard to predict. The dam itself stores the danger: removing it fast releases the water, but leaving it means it will fail anyway. So engineers dig controlled spillways, monitor the lake and evacuate downstream. Glacial-lake outburst floods follow the same pattern with moraine or ice dams.

 

A landslide-dam failure is a cross-scale hazard cascade. Mass wasting deposits debris across a valley, impounding a lake that later fails and releases a rapid outburst flood. The lifecycle is trigger, deposit, impoundment, failure mode, outburst. A contained trigger thus becomes a standing regional risk, and the downstream flood typically exceeds the landslide in energy and extent. The barrier is unengineered, poorly sorted and heterogeneous, and has no spillway. Its time-to-failure distribution is short, heavily right-skewed and hard to forecast. Historical analysis (Costa and Schuster, 1988) found that a substantial fraction fail within days to months, with overtopping, piping and slope collapse as the dominant modes. Conceptually, the barrier is the hazard's storage element: rapid removal releases the load, and inaction releases it anyway on a schedule that volume and geometry constrain but do not fix. Mitigation therefore uses controlled drawdown through excavated spillways, evacuation and exclusion zoning during the impoundment window, and lake-level monitoring. Glacial-lake outburst floods are the moraine- or ice-dam variant. The 2008 Tangjiashan barrier lake is the canonical modern case: it held over 100 million cubic metres and required weeks of excavation and the evacuation of 250,000 people.

Scope of Application

It lives within natural hazards and geomorphology, across debris-impoundment events regardless of what put the barrier in the valley.

  • Mountain-river barrier lakes (canonical) — earthquake- or rainfall-triggered avalanches, as at Tangjiashan (2008 Wenchuan).
  • Glacial-lake outburst floods (GLOFs) — moraine- or ice-dammed lakes in the Himalaya, Andes, Alaska.
  • Volcanic-debris dams — lahar deposits choking valleys after eruptions (Mount St. Helens, Pinatubo).
  • Ice jams and log jams — seasonal river impoundments producing the same behaviour at smaller scale.

Clarity

Naming the failure makes legible that a landslide need not be single-stage: the label binds formation and failure into one cascade, so a response clearing the slope but ignoring the lake has not closed the event — it has armed the larger one. The clarifying core is that the barrier is the hazard's storage element, which turns the paradoxical intervention problem into a race a practitioner can reason about: accumulation against barrier degradation.

Manages Complexity

Earthquake-dammed rivers, moraine-dammed glacial lakes, lahar deposits, and ice jams look like four hazard literatures. The concept collapses them onto one lifecycle — trigger, deposit, impoundment, failure mode, outburst — so the analyst reasons from a fixed sequence, not the trigger physics. A small parameter set (volume, geometry, failure mode) yields the one decision that matters: is there a drawdown window before natural failure, and can the population be cleared?

Abstract Reasoning

It licenses diagnostic reading of the standing secondary hazard and its failure mode from barrier composition; interventionist action on the storage element via controlled drawdown, exclusion zoning, and monitoring; boundary-drawing that separates storage-and-release from bare cascade, phase transition, or steady leakage; and prediction of a short right-skewed time-to-failure with the outburst arriving last and largest.

Knowledge Transfer

Within natural hazards the concept transfers as mechanism across all debris-impoundment events — the barrier-as-storage framing, the failure-mode triad, and the intervention menu carry intact, with the GLOF variant differing only in the deposit slot. Beyond that substrate, lifting it whole is analogy. But a genuine residue travels: the blockage-release dynamic (a barrier holding an accumulating load and releasing it discontinuously), recurring in volcanism, embolism, and pent-up demand — carried by the installed prime blockage-release dynamics, not the geomorphic concept.

Relationships to Other Abstractions

Local relationship map for Landslide-Dam FailureParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Landslide-Dam FailureDOMAINDomain-specific abstraction: Mass Wasting — includesMass WastingDOMAINPrime abstraction: Stress and Rupture — includesStress andRupturePRIMEPrime abstraction: Blockage Release Dynamics — is a kind ofBlockageRelease DynamicsPRIMEPrime abstraction: Cascade — is a kind ofCascadePRIME

Current abstraction Landslide-Dam Failure Domain-specific

Parents (4) — outgoing typed relations

  • Landslide-Dam Failure is a kind of Blockage Release Dynamics Prime

    Landslide-dam failure is the geomorphic specialization of blockage-release dynamics.

  • Landslide-Dam Failure is a kind of Cascade Prime

    Landslide-dam failure is a two-stage natural-hazard cascade.

  • Landslide-Dam Failure includes Mass Wasting Domain-specific

    Landslide-dam failure contains the mass-wasting event that creates its cross-valley barrier.

  • Landslide-Dam Failure includes Stress and Rupture Prime

    The impounded barrier stage contains load accumulation, threshold failure, and abrupt release.

Hierarchy paths (13) — routes to 8 parentless roots

Neighborhood in Abstraction Space

Landslide-Dam Failure sits in a sparse region of the domain-specific corpus (70th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25