Sentinel-1 radar recorded the Nepal slope speeding up in the weeks before it collapsed
The creep was about 10 millimetres a month, far too slow to trip any threshold set in advance. Manoochehr Shirzaei's preliminary read is that nobody was screening for the change in its rate.
The Scientist · Science desk
What happened
- A high-altitude collapse of rock and ice near the Nepal-Tibet border on 26 August set off a flash flood that has killed more than 1,000 people, with more than 4,000 still listed as missing.
- Manoochehr Shirzaei, a geophysicist at Virginia Tech, and colleagues went back through European Space Agency Sentinel-1 radar covering 8 January to 18 August, the final pass a week before the failure.
- Shirzaei's own yardstick is that glaciers travel roughly 10 to 200 metres a year, so a slope that creeps steadily and slowly for years is not on its own a sign of trouble.
- The analysis indicates that the rock and ice near the potential failure zone were accelerating, a rate change Shirzaei treats as more informative than the speed itself.
- The warning systems that do exist in the region are built for glacial-lake outburst floods rather than for forecasting a catastrophic glacier-and-rock collapse.
Why it matters
- What it limits constraint A deformation signal this small surfaces only when a researcher reanalyses the archive after the event, because routine systems are not designed to examine thousands of glaciers and unstable slopes for subtle change.
- What's now possible capability The measurements were already being collected and are already public, so a standing watchlist of accelerating slopes is buildable from data that nobody is currently reading that way.
- Who's exposed exposure The origin sits at or across an international border, which puts any future alert through a handoff between two governments before it can reach the communities downstream.
- Who has to decide decision Hazard funders face a split: more instruments at lakes already flagged as dangerous, or a regional deformation-screening layer wired into flood and avalanche models.
Ten millimetres a month, the velocity Shirzaei's group measured near the apparent collapse area [5], comes to 0.12 metres a year, which is between 0.06 and 1.2 percent of the glacier speeds he uses as a yardstick [20]. Across the full radar window, steady movement at that rate accumulates about seven centimetres [21]. Any speed threshold set in advance, over a region containing thousands of moving slopes, would have to sit far above that to be usable at all.
In his account to Nature, what the imagery suggests is that the section of glacier and the rock beneath it had been accelerating for weeks [2], and the analysis places the change in rate in the days immediately before the failure [7]. Shirzaei is not just asking how fast the slope was moving; he is asking whether that speed was changing, and it is the change he treats as evidence about the state of the system.
Acceleration is not a clock. Shirzaei is direct about it. The signal alone would not have said collapse imminent, evacuate now; the most it would have bought is the area being flagged as a hotspot warranting closer attention [8]. He also calls the analysis preliminary, with post-event imagery still to be compared and other explanations still to be excluded [9]. What the finding does support, though, is narrower and still troubling: the precursor sat in a Sentinel-1 archive [4] that nobody was reading for this class of failure, because a high glacier-and-rock system failing on its own is not the trigger these systems are built around, unlike heavy rain or a rising glacial lake [10].
The event fell between two designs. At Cirenmaco in Tibet, researchers instrumented lake level, ice and rock collapses and downstream runoff, with real-time transmission over satellite and mobile links to catch precursors and warn communities below [15]. Nepal's Khumbu systems use water-level sensors, weather stations and automatic sirens [16]. Both are addressed to a particular lake already known to be dangerous. A high-elevation glacier-rock system with no lake beneath it has no place in that architecture [14], and the terrain above it carries no continuous ground instruments that could give it one [11]. What is needed, Shirzaei told Nature, is detection aimed at collapses that carry cascade risk into landslides and downstream flooding [18].
One small note on the timeline, since precision is cheap here: the last radar pass is given as 18 August and the collapse as 26 August, which is eight calendar days, not the seven stated [19].
The origin sequence is still unresolved, and it matters for any detector's design, because a rockslide that dragged the glacier downhill and a glacier that failed first and destabilised the rock are not the same target [3]. Meanwhile the arithmetic above points at one design choice already: screening on speed would have excluded this slope, and screening on acceleration keeps the slow movers in the net. Whether that yields a list short enough for anyone to act on is what the preliminary work cannot yet say.
What to watch
- Whether the post-event image comparison confirms the acceleration or attributes it to something else; the finding stays preliminary until the alternatives are excluded.
- How the 4,000-plus still listed as missing resolve, which sets whether this event is counted at 1,000 dead or above 5,000.
- Any agency putting budget into sweeping archive radar for accelerating slopes rather than adding instruments at lakes already known to be dangerous.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+15
- Incentives
- Not scored
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
A high-altitude collapse of rock and ice on 26 August triggered a catastrophic flash flood near the Nepal-Tibet border that has so far claimed more than 1,000 lives, with more than 4,000 people still missing.
- [2]
Manoochehr Shirzaei says satellite images from just days before the disaster suggest that a section of the glacier and the rocks it sat on top of were accelerating in the weeks before the collapse, a concerning sign of an unstable system.
- [3]
The precise sequence of events remains unclear: the disaster might have begun with a massive rockslide that dragged part of the glacier downhill, or the glacier might have failed first, causing rocks to destabilize into a landslide.
- [4]
Shirzaei, a geophysicist at Virginia Tech, and colleagues analysed radar data from the European Space Agency's Sentinel-1 satellites acquired between 8 January and 18 August; the last observation was only seven days before the disaster.
- [5]
The team detected evidence that the glacier-rock system was slowly moving downhill near the apparent collapse area, with velocities reaching roughly 10 millimetres per month.
- [6]
Shirzaei notes that glaciers can move at speeds of roughly 10 to 200 metres per year, so a slope moving steadily at 10 mm a month for years might not seem particularly alarming.
- [7]
The analysis also indicates acceleration of rock and ice near the potential failure zone; acceleration matters more than velocity because it suggests the rate of slope deformation was changing in the days leading up to the disaster.
- [8]
Shirzaei says the exact timing of the collapse was hard to forecast and that the acceleration alone would not have told them 'collapse imminent, evacuate now'; had the signals been identified beforehand, the area could have been flagged as a hotspot warranting closer attention and monitoring.
- [9]
The results are still preliminary; the team is comparing the deformation pattern with images of the site after the event and needs to rule out other possibilities.
- [10]
The event was particularly difficult to anticipate because it appears to have originated in the sudden failure of a high-elevation glacier-rock system rather than a more routinely monitored trigger such as extreme rainfall or the gradual rise of water in a known glacial lake.
- [11]
High-mountain areas of this kind are remote, difficult to access and generally lack continuous monitoring with ground-based instrumentation.
- [12]
Many glaciers and rock slopes move continuously without collapsing, and most existing monitoring systems are not designed to routinely examine thousands of glaciers and unstable mountain slopes for subtle changes in deformation.
- [13]
The region where the cascade originated is close to, or across, the Nepal-Tibet border, so effective warning alerts depend on rapid sharing of observations and hazard information between countries.
- [14]
Most existing warning systems focus on glacial-lake outburst floods rather than directly forecasting catastrophic glacier-rock collapses.
- [15]
At Cirenmaco glacial lake in Tibet, researchers developed a system that monitors lake level, ice and rock collapses and downstream runoff among other variables, transmitting information in real time through satellite and mobile communications to identify precursor events and issue warnings for downstream communities.
- [16]
Systems in Nepal's Khumbu region incorporate water-level sensors, weather stations and automatic sirens for glacial-lake hazards.
- [17]
What is still largely missing, according to Shirzaei, is a regional satellite-based system that routinely searches for accelerating glacier and rock-slope deformation and then connects that information directly to downstream flood and avalanche modelling.
- [18]
Shirzaei told Nature that such an event is difficult to predict using existing monitoring techniques, and that what is needed are systems able to detect glacier and rock collapses that pose cascade risks and can result in landslides and downstream flooding.
- [19]
18 August to 26 August is eight calendar days, one more than the seven days stated as the gap between the last radar observation and the disaster.
- [20]
A creep rate of 10 mm per month equals 120 mm, or 0.12 m, per year, which is 1.2 percent of 10 m per year and 0.06 percent of 200 m per year.
- [21]
The 8 January to 18 August observation window spans about 222 days, roughly 7.3 months, over which constant creep at 10 mm per month totals about 73 mm, under 8 cm.
- [22]
If the more than 4,000 missing were counted among the dead, the toll would exceed 5,000, roughly five times the confirmed figure of more than 1,000.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
2 independent publishers whose own reporting we read for this story.
- discovermagazine.comSatellite Radar Detected a Himalayan Slope Accelerating Weeks Before Nepal's Catastrophic Flood
1 article · September 3, 2026
- nature.comSatellite images before Nepal disaster showed warning signs
1 article · September 1, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.