In the Face of Disaster: How and When to Travel Responsibly

✈️ The moment I chose to stay

When the earthquake hit near Pokhara at 11:02 a.m. on October 23, I was already on the bus—halfway up the winding road to Jomsom, Nepal. My phone buzzed with alerts: "Moderate tremor felt in Kaski and Myagdi districts." Within minutes, landslides blocked the route behind us. No evacuation order came. No official guidance appeared. Just silence—and then, quietly, a decision: I would not turn back. Not because it was safe, but because abandoning my hosts mid-crisis felt more dangerous than staying. This is how and when we travel in the face of disaster—not with certainty, but with calibrated attention, local reciprocity, and layered risk assessment. What follows isn’t advice on whether to go, but how to discern what kind of presence matters most when infrastructure fails, forecasts falter, and maps become unreliable.

🌍 The setup: Why Pokhara, why then?

I’d booked the trip six weeks earlier—a solo trekking loop through the Annapurna foothills, budgeted at $32/day including homestay, meals, and local transport. I chose late October deliberately: post-monsoon clarity, pre-winter chill, and lower tourist density meant better access to family-run lodges and more candid conversations with guides. My itinerary wasn’t ambitious—no high-altitude passes, no remote valleys—but grounded in rhythm: walk mornings, rest afternoons, share tea with elders, map routes using offline OSMAnd maps downloaded weeks prior. I carried a satellite messenger (Garmin inReach Mini 2), two power banks, iodine tablets, and a laminated list of Nepali emergency numbers—not as a shield, but as tools to reduce friction if things slowed down.

Pokhara itself was calm that week. Lakeside cafes hummed with backpackers ordering momos and filtering water at communal taps. I’d spent three days acclimating, walking the Phewa Lake perimeter, checking bus departure boards at Prithvi Chowk, and confirming with the Sarangkot Community Homestay Cooperative that their Jomsom-bound jeep left every other morning at 6:30 a.m.—cash only, no online booking, no reservation system. Their ledger was a notebook bound in duct tape. That’s where I signed my name, paid NPR 850, and received a hand-drawn slip with a smile and the words: "We leave when full. You are number seven."

🌧️ The turning point: When the ground moved—and everything else stopped

The bus wasn’t a bus—it was a repurposed Isuzu cargo van with bench seats bolted to the floor. We climbed past Siding, past Ghandruk’s stone stairways, past the first landslide scar where red earth still bled onto asphalt. At 11:02 a.m., the vehicle shuddered—not like potholes or curves, but like a deep breath held too long. A low groan rose from the mountain. Then silence. Birds stopped singing. Dust drifted sideways, not down.

No one shouted. No alarms sounded. The driver killed the engine. He stepped out, squinted up the valley, and lit a cigarette. Behind us, a man with a radio raised it to his ear, listened, lowered it, and said only: "No signal." We waited. Twenty minutes passed. Then thirty. A woman opened her bag and passed around boiled sweets—small, sticky, warm. Someone offered me a sip from their thermos: ginger tea, thick with sugar. No one panicked. But no one moved either.

By noon, word came—not from authorities, but from a porter walking downhill, his duffel slung over one shoulder: "Three slides between Beni and Baglung. Road closed. No buses tomorrow." My original plan had me returning to Pokhara via Beni on Day 5. Now that route was gone. My satellite device showed no SOS alert triggered—not by me, not by anyone nearby. I checked the Nepal Geological Survey’s real-time seismic portal on my offline browser cache: magnitude 5.3, depth 10 km, epicenter 22 km northwest of Pokhara. Not catastrophic—but enough to fracture old trails, shift riverbeds, and unmoor assumptions about reliability.

🤝 The discovery: Who stays when systems fail?

We didn’t turn back. Instead, the driver negotiated with a local farmer whose tractor could navigate the first slide’s bypass path—a narrow goat track skirting loose scree. It took two hours to cover five kilometers. No GPS worked there. The farmer guided us by memory, pointing to a bent rhododendron branch, then to a faded blue paint mark on a boulder. At the next village—Thasang—we stopped. Not because we had to, but because the farmer insisted: "You drink. You rest. We wait for news."

That’s where I met Laxmi, 68, who ran the village’s only teahouse. Her roof had cracked during the tremor, but she’d patched it with tarps and bamboo laths before dawn. She served us salted butter tea in chipped enamel cups, her hands steady despite tremors in her left wrist—"From the ’91 quake," she said, smiling. She didn’t ask if I was scared. She asked if I’d seen the new irrigation ditch dug last monsoon. She asked if I knew how to tell when a landslide might come again: "Listen for falling stones at night. Watch where goats won’t graze. Smell the air—wet clay means water rising underground."

Over the next two days, I learned what “disaster response” looked like without NGOs or apps: neighbors clearing debris with hoes and ropes, children carrying water from the spring upstream (the pipe had burst), elders mapping damaged houses on a chalkboard hung outside the schoolhouse. No one spoke of “tourism loss.” They spoke of harvest delays, of delayed medicine deliveries, of which trails needed rerouting before the winter snows set in. I helped carry firewood. I copied names into the damage log. I listened—not to pitch recovery stories, but to understand what resilience actually sounded like: low, practical, collective, and utterly unmarketable.

🚋 The journey continues: Rewriting the route, not the purpose

By Day 3, the road to Jomsom remained impassable—but the trail to Marpha, a high-altitude apple-growing village, was passable. A local guide named Raju offered to lead us on foot. He didn’t charge per kilometer. He charged NPR 1,200 for three days—including shared meals, a sleeping mat, and his uncle’s spare room. He carried extra rice, iodine tablets, and a small first-aid kit he’d assembled himself. When I asked why he’d taken the job mid-crisis, he shrugged: "People still need to move. And I know these paths. If I don’t guide, who will?"

We walked 18 km that day—up switchbacks carved into cliff faces, across suspension bridges strung with prayer flags fraying in the wind. Rain fell lightly, cold and persistent. Raju stopped often—not to point at views, but to inspect trail anchors, test rock stability with his boot, check drainage channels choked with leaves. He taught me how to read trail conditions: moss on north-facing stones meant persistent dampness; fresh scree meant recent movement; bare roots exposed on slopes signaled erosion. These weren’t scenic details—they were operational intelligence.

At Marpha, electricity flickered on and off. The community health post had reopened, powered by a single solar panel. A volunteer nurse trained in basic trauma care was triaging minor injuries. She told me they’d treated six landslide-related injuries in four days—all non-fatal, all treated with supplies donated by neighboring villages, not international aid. "Help comes later," she said, wiping her glasses. "What keeps people alive now is knowing each other’s names—and where the clean water is."

🌅 Reflection: What “traveling in the face of disaster” actually means

I used to think responsible travel meant avoiding risk—choosing stable countries, checking travel advisories, buying comprehensive insurance. That trip dismantled that idea. Risk avoidance is passive. Risk engagement—calibrated, informed, reciprocal—is active. Traveling in the face of disaster isn’t about bravery or recklessness. It’s about recognizing that crises aren’t binary events (“safe” vs. “unsafe”) but layered conditions: infrastructure failure, communication gaps, supply chain interruptions, shifting social priorities. And your presence, however brief, becomes part of that layering.

I stayed because leaving would have meant withdrawing support—from the homestay cooperative whose income relied on consistent guest flow, from the driver whose livelihood depended on functioning routes, from Laxmi’s teahouse, where every cup sold funded her grandson’s schoolbooks. My budget travel choices—staying local, paying cash, eating seasonal food—had quietly built interdependence long before the tremor hit. That interdependence didn’t erase danger. It just made my role clearer: not as a spectator of hardship, but as a temporary node in an existing network of mutual aid.

There’s no checklist for this. No algorithm can weigh the value of a shared meal against the statistical probability of aftershocks. But there are observable signals: Are local businesses open? Are public services operating—even minimally? Are residents moving with purpose, not paralysis? Those signs matter more than any advisory level. Because advisories reflect national capacity. Local reality reflects human continuity.

📝 Practical takeaways: What I carried forward

None of this was theoretical. Each insight emerged from friction—missed connections, language gaps, equipment failures. Here’s what stuck:

• 💡Local timing trumps calendar timing. I’d chosen late October for weather—but locals told me the safest window for high-elevation trails was actually mid-October to early November, when monsoon saturation had drained and frost hadn’t yet hardened the soil. Seasonal calendars mean little without ground-level validation.
• 🗺️Offline navigation requires layered verification. My OSMAnd map showed trails—but Raju corrected three segments based on recent washouts. Always cross-reference digital maps with physical markers (cairns, painted rocks, worn paths) and ask: "Has this path changed since last month?"
• ☕Teahouses are intelligence hubs. Laxmi’s teahouse wasn’t just shelter—it was where farmers exchanged landslide reports, where porters relayed road status, where teachers coordinated student evacuations. Paying for tea bought access to real-time, unfiltered context.
• 🚌Transport flexibility > schedule fidelity. Buses didn’t run on time—but shared jeeps, tractors, and walking groups did. I abandoned fixed timetables and adopted departure triggers: "Leave when the landslide crew clears the first bend," or "Go when the radio operator confirms the bridge is stable."
• 📸Documentation serves dual purposes. My photos of cracked walls and rerouted trails weren’t for Instagram—they were shared with the Sarangkot Cooperative’s WhatsApp group so they could update guest advisories. Ethical documentation means contributing data, not extracting aesthetics.

⭐ Conclusion: Travel as continuity, not interruption

I returned to Pokhara ten days later—not on a bus, but on foot, down the newly cleared Beni road, carrying a jar of Marpha apple jam and a notebook filled with trail corrections. The city felt unchanged: street vendors fried fish, tourists snapped selfies at Davis Falls, the lake shimmered under afternoon sun. But I wasn’t unchanged. I’d stopped seeing travel as a sequence of destinations—and started seeing it as participation in ongoing life. Disasters don’t pause human systems. They expose which ones are woven tight, and which are brittle. Traveling in their wake doesn’t require heroism. It requires humility, patience, and the willingness to ask—not "Is it safe to go?"—but "What does safety look like here, right now, and how can I align with it?"