10.6.5 — Dam Safety — maturity: live
Downstream Flood Risk Modelling
Using satellite-derived terrain, soil-moisture, rainfall and reservoir-state data to continuously update inundation models for populated areas downstream of dams.
When a dam fails, the downstream flood wave can kill thousands within hours — satellite-derived terrain, soil-moisture and rainfall data turn that threat into a manageable, continuously updated risk map.
A dam failure does not announce itself. By the time a crack propagates to breach or an overtopping event begins, emergency managers downstream may have minutes, not hours. Traditional flood modelling relies on static DEMs surveyed years ago, point rain gauges that miss convective cells, and reservoir telemetry that either fails during the same storm that threatens the structure or is never shared across agency boundaries. The result is evacuation orders that arrive too late, or not at all.
A constellation of small SAR and optical satellites, combined with GNSS-reflectometry and microwave radiometry payloads, closes every data gap simultaneously. Repeat-pass SAR at 3-5 day intervals keeps the terrain model current — catching new construction, reservoir sedimentation and floodplain encroachment that invalidates older DEMs. Soil-moisture retrievals at 1-3 km resolution, updated every 12-24 hours, set the antecedent conditions that determine how fast a flood pulse travels and how high it crests. Reservoir level from §10.6.1 and dam-wall deformation from §10.6.2 feed directly into the same hydraulic model as upstream boundary conditions, making the downstream risk picture a live, integrated output rather than a periodic desktop exercise.
The operational outcome is an always-on inundation forecast that emergency operations centres can interrogate at any time, with automated alert tiers keyed to modelled water-surface elevations at named populated nodes. When the reservoir state crosses a threshold — rising faster than a calibrated rate, or deformation exceeding a limit — the hydraulic model re-runs at high resolution within minutes, pushes worst-case flood arrival times to local civil-defence networks, and logs the event for post-incident review. Nations that own this stack own the decision timeline; those that rent it discover, at the worst possible moment, that the vendor's processing queue is shared with fifty other subscribers.
Frequently asked
What satellites actually feed a downstream flood risk model?
Three complementary data streams are typically fused. SAR satellites (ICEYE, Sentinel-1, Capella) map inundation extent through cloud cover. Optical multispectral satellites (Sentinel-2, Planet SuperDove) classify land use and floodplain roughness. Radar altimeters and GNSS-reflectometry missions supply water-surface elevation for hydraulic model boundary conditions. The model itself — usually HEC-RAS 2D or LISFLOOD-FP — runs on ground infrastructure, ingesting all three streams.
Why shouldn't we simply buy this as a service from Planet, ICEYE or Spire?
Commercial providers will sell you imagery and, increasingly, processed flood-extent layers. What they cannot guarantee is priority tasking at 2 a.m. on the day your dam begins to move, when every other disaster-struck government is queuing for the same archive. A sovereign constellation with a dedicated ground segment means your tasking queue starts empty and your data pipeline is not throttled by another customer's SLA. It also means the flood model, calibration data and alerting thresholds remain inside your own classification boundary.
How much lead time can a satellite-fed model realistically deliver?
For a large storage dam with gradual overtopping, satellite-derived reservoir level trends (from altimetry or InSAR-tracked water surface) can flag elevated risk 12–72 hours ahead of a spillway event. For sudden structural breach, the warning window compresses to hours; the satellite contribution shifts from prediction to rapid damage mapping and evacuation route assessment. Combining catchment inflow forecasting (§10.6.4) with downstream routing extends actionable lead time the most.
What is the minimum constellation size for credible sovereign coverage?
For a mid-sized nation with 50–200 major dams, a constellation of 4–6 SAR microsatellites (100–300 kg class, S- or C-band) paired with 6–10 optical nanosatellites provides a 4–6 hour revisit over any catchment — sufficient to update a hydraulic model at operationally meaningful intervals. Spire's GNSS-RO payloads can be hosted as secondary missions to add precipitation-profile data at minimal incremental cost.
Can satellite data replace stream gauges and rain gauges for this application?
Not entirely, and anyone who claims otherwise is selling something. Satellite soil-moisture (SMOS, SMAP, Sentinel-1 derived) and precipitation estimates (GPM IMERG) dramatically improve spatial coverage, particularly in ungauged basins. However, they cannot yet match the temporal resolution or channel-specific accuracy of a well-maintained in-situ gauge network. The defensible architecture pairs satellite observations with a sparse but reliable ground network, using each to quality-control the other.
How does this connect to the ITU frequency regime — will our SAR constellation face interference issues?
SAR satellites operate in frequency bands allocated to Earth Exploration Satellite Service (EESS active) under ITU Radio Regulations. C-band (5.4 GHz) and X-band (9.6 GHz) are the most congested. Nations must coordinate with ITU-R under Resolution 750 and comply with ITU-R RS.1166 to protect co-frequency services. Early ITU filing — typically 2–3 years before launch — is essential; late filings risk interference disputes that can ground a constellation operationally.
What happens when the dam and the downstream population are in different countries?
Transboundary exposure is governed primarily by bilateral or multilateral water treaties and by UNECE Convention on the Protection and Use of Transboundary Watercourses (Helsinki Convention). Satellite data sharing is not automatically covered. The practical solution is for the upstream nation to operate the sensing capability and establish a formal data-sharing protocol — ideally with WMO facilitating under its Hydrological Observing System framework — so downstream governments receive processed risk products, not raw imagery they cannot interpret.
What accuracy benchmark should a government specify when procuring a satellite-fed flood model?
The industry reference is the NOAA National Weather Service AHPS standard: flood-extent predictions should achieve a Critical Success Index (CSI) ≥ 0.65 against post-event validation imagery for events with return periods above 1-in-50 years. For satellite-derived inundation mapping specifically, the UN-SPIDER recommended practice benchmark is 85% overall accuracy against reference flood masks. Both metrics should be written into any service or system procurement as verifiable acceptance criteria.