Quantifying the long-term evolution of glacial lakes and the impact of the 2024 Thame, Nepal outburst flood event using remote sensing
This study utilizes remote sensing to analyze the 2024 Thame, Nepal GLOF event, revealing a rare cascading breach between two glacial lakes that caused significant downstream destruction and arguing for a shift in hazard assessment frameworks from size-based prioritization to consequence-based, catchment-scale evaluations that include smaller, high-risk water bodies.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine the high mountains of Nepal as a giant, melting ice cream cone. As the climate warms, the ice cream (glaciers) shrinks, leaving behind sticky puddles of water trapped in the dirt and rocks (moraines). Scientists call these puddles "glacial lakes." For a long time, experts have been playing a game of "spot the danger," but they've mostly been looking for the big puddles, ignoring the tiny ones because they seem too small to matter.
That was the big mistake the authors of this paper are pointing out. They investigated a scary event that happened in August 2024 in a place called Thame, Nepal, and they found that the "tiny" lakes were actually the troublemakers.
The "Domino Effect" Disaster
Think of the lakes in this valley like a row of dominoes. The main culprit was a small lake called GL5. Before the disaster, this lake was growing like a balloon. Between 2015 and 2024, it exploded in size, getting 12 times bigger than it started, growing from a tiny 0.008 km² to a massive 0.1 km². It was expanding at a rate of 18% every single year!
On that fateful day in 2024, the dam holding back GL5 (a wall of rocks and dirt) finally gave way. But here is the twist: GL5 didn't just flood the valley; it hit the next lake in line, GL4, like a giant wave hitting a second dam. This caused GL4 to burst open too.
The authors call this a "cascading outburst." It's like if you knocked over a small cup of water that splashed onto a second cup, causing that one to spill too. The result was a "compound outburst"—a flood that was way more powerful than either lake could have created on its own. This specific type of chain-reaction flood is something scientists have rarely seen directly in this part of the world.
The "Small" Lakes That Weren't
Before this event, many safety checklists ignored lakes smaller than 0.1 km². The lakes that caused the trouble in Thame were all in that "ignored" size range (between 0.04 and 0.1 km²). The authors argue that this "size-based" rule is broken. Just because a lake is small doesn't mean it's safe. If it's connected to other lakes or sitting in a steep valley, it can be just as dangerous as a giant one.
The Aftermath: A River of Mud
When the two lakes burst, they sent a high-speed river of water and rocks racing down the mountain. The terrain helped the flood get even worse. The valley squeezed the water into a narrow bottleneck near a place called Thyangbo, which acted like a nozzle on a garden hose, speeding the water up even more.
By the time this muddy torrent hit Thame village, it was a wide, destructive wave, about 400 meters wide. It didn't just splash; it tore through the village.
- It destroyed 36 households, a school, a clinic, lodges, a bridge, and a hydropower pipeline intake.
- It wiped out 10 hectares of farmland (that's about 14 soccer fields worth of crops).
- The total estimated economic loss was 4.13 million USD.
The flood was so powerful it actually changed the shape of the land. The river shifted its path, creating a new channel that split the village in two, and left behind a V-shaped pattern of destruction.
What the Authors Are Sure Of (and What They're Not)
The authors are very sure about the numbers they measured using satellite photos. They tracked the lakes from 1989 all the way to 2025 using different types of cameras in space, from old, blurry ones to super-sharp new ones. They confirmed that GL5 grew 12 times its original size and that the flood destroyed 36 homes along with the critical infrastructure listed above. They are also sure that the "cascading" nature of the event (one lake hitting the next) made the disaster much worse than a single lake burst would have been.
However, when it comes to why the dam broke, they are a bit more cautious. They suggest that the rapid growth of the lake put too much pressure on the dam, and a small rockslide might have been the final push. They also note that the summer monsoon rains in 2024 were very heavy, which might have helped weaken the dam, but they can't say for certain exactly how much the rain contributed versus the rockslide. They suggest that we need better weather stations right in the mountains to know for sure next time.
The Big Lesson
The main takeaway is that we can't just look at how big a lake is to decide if it's dangerous. We have to look at the whole picture: Is it connected to other lakes? Is the valley steep? Are there people living downstream? The authors argue that we need to stop ignoring the "small" lakes and start treating every catchment as a connected system. If we don't, we might miss the next "domino" that could knock over a whole village.
Fortunately, in this specific 2024 event, no one died because the flood happened during the day when people were awake and could run to safety. But the damage to the land and the community's wallet was severe, serving as a loud warning that the rules of glacial safety need to change.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.