Asia·Bhutan
Bhutan lake assessments distinguish estimated volume loss from a 73% surface-area decline
GASA, Bhutan —
| Score | Meaning | Major U.S. outlets that covered it |
|---|---|---|
| 10 | Fully overlooked ← this story | 0 of 13 outlets |
| 8 | Barely covered | 1 outlet |
| 6, 5 | Lightly covered | 2 outlets (6) · 3 outlets (5) |
| 4, 3 | Covered | 4 outlets (4) · 5 outlets (3) |
| 2, 1, 0 | Widely covered | 6–7 outlets (2) · 8–10 outlets (1) · 11–13 outlets (0) |
Provisional: One Bing News site-filtered query per outlet; title-reviewed candidates and search indexing are incomplete. Related coverage exists, especially Reuters on the Bhutan flood. This is not proof of absence or a full site-by-site audit.
Depth
Dig five layers into this story — from what happened to the full picture.
L1What happened
What happened: BBS’s satellite-analysis report puts the lower lake’s estimated volume loss at around 80%. The Hindu’s later report puts the affected lake’s surface-area loss at 73%, to 6.54 hectares.
L2Who’s affected
Who’s affected: Communities downstream of the glacial-lake system and authorities assessing post-flood risks. BBS reports that field verification was still needed before the precise trigger and further threat could be established.
L3Why it’s quiet
How we know: BBS quotes an ICIMOD specialist on water volume. The Hindu cites Suhora’s late-October satellite imagery and decade-long surface-area comparison. These are separate assessment chains, not two measurements of the same quantity.
L4Deeper impact
Deeper impact: The Hindu reports that an adjoining supraglacial lake remains larger than its 2016 extent despite shrinking after the outburst. BBS says substantial water remains in the upper lake and cautions that potential further risks require field assessment.
L5Full context
Full context: The Hindu dates the outburst to Oct. 29 and compares late-October imagery from 2016 through 2026. BBS describes a possible upper-lake contribution, not a proven flood trigger; no mechanism is asserted as established.
You’ve reached the bottom. Read the original reporting below.
Original reporting
Status history (2 events, ET)
- O-Score check: 10 (Fully overlooked) · 0 of 13 outlets counted
- Published
Story timeline
No pickup log yet. We haven’t logged an O-Score check or outlet coverage for this story, so there’s nothing to scrub through.
Trace it: 5 of 5 sourced claims on this page can be traced to a saved copy of the original report.
This is an OVERLOOKED summary of the reporting above. Facts and figures come from the linked sources. Everything here is a fact unless it is labelled otherwise. Support this work.
Alerts Get stories like this your way: email, a daily PDF paper, notifications, RSS, or alerts on topics you follow. Choose how →