How a 500-Engineer WhatsApp Group Guided Nepal’s Trishuli Tunnel Rescues

After a glacier collapse unleashed a destructive flood through Nepal’s Trishuli valley on August 26, 2026, rescuers faced a basic but urgent problem: the hydropower tunnels they needed to search had been buried, flooded and altered by mud and debris. A pre-existing WhatsApp group, expanded to more than 500 engineers, former plant workers, officials and other specialists, became a remote technical support network for the teams on the ground. 10

Turning scattered expertise into search decisions

The group gave responders access to information that was difficult or impossible to recover at devastated sites. Members shared layout drawings and details of hydropower facilities, including the Chilime project, when rescuers needed to understand where tunnels and access routes had been before the flood. 10

That information was useful because an underground rescue is not simply an excavation job. Teams needed to judge where a buried entrance might be, which passages or cavities could still exist, and where machinery could work without worsening already unstable conditions. Former employees’ familiarity with the plants and information about missing workers helped add operational context to the drawings. 10

In practice, the messaging group functioned as a fast way to connect field crews with people who knew the infrastructure: a request for a plan or site detail could be answered by an engineer or former worker who was not physically present in the valley. The group worked alongside—not instead of—rescue personnel, heavy equipment and aircraft. 10

Why tunnel plans mattered

Flood debris had cut off and reshaped access to multiple hydropower sites. Thick mud, damaged infrastructure and debris-filled tunnels made it hard for teams to reach workers believed to be underground. 9

Rescuers used technical guidance while considering where to clear debris, how to approach blocked sections and where oxygen might be sent through pipes toward potential voids. The objective was to convert incomplete evidence—plans, remembered site conditions and reports of workers’ likely locations—into safer, more targeted attempts to reach survivors. 10

The limits were severe. Plans describe the facility before a disaster; they cannot show exactly how a massive debris flow has changed a tunnel after the fact. That meant every search decision still had to be validated by conditions at the site.

The Upper Trishuli 3A rescue sustained hope

On September 4, nine days after the flood, rescuers pulled two workers alive from a tunnel linked to the Upper Trishuli 3A hydropower project. The rescue was a powerful indication that protected spaces inside the damaged underground network could, in some cases, remain survivable. 8

It also reinforced the reason for continuing targeted searches elsewhere. At least 900 people were believed trapped in tunnels associated with six hydropower projects, according to officials and rescue workers cited by Reuters. 7 Other reporting described searches at sites including Chilime and Rasuwagadhi, where teams were still confronting obstructed underground infrastructure and uncertain survival prospects. 10

A communications tool with a narrow but important role

The WhatsApp group did not make the disaster less destructive or guarantee that trapped people could be reached. Its value was more specific: it pooled institutional memory and engineering records quickly enough to inform life-or-death choices in a rapidly changing rescue operation.

The flood itself followed the collapse of ice, rock and mud in the Himalayan border region. Early accounts said the disaster killed more than 1,200 people and left thousands missing; the figures were still evolving as rescue and recovery operations continued. 78 In that setting, a simple messaging platform became a practical coordination layer—helping ground crews ask better questions about what lay beneath the debris, and where a search still had a chance.