Helicoptered into New Zealand’s Southern Alps to volunteer track-cut our way back toward the coast, carrying a four-day pack and hand tools through hard, remote country. This was the first real trip with a crude SafeNotSafe prototype on me.
At home, the Whitcombe was not a neat line on a tourist map.
It was a sequence of signals from hard country: a helicopter flight into the mountains, a landing at Neave Hut, movement toward the Main Divide, a night in a tent outside a full hut, a side trip away from the main group, a remote hut, a river crossing, and finally the flight back out.
That is where structured check-ins matter. A normal message might say “all good”. A SafeNotSafe pulse gives more: where I was, when I sent it, whether I was moving or resting, what direction I was heading, and what home should understand from that moment.
The important thing was not constant contact. It was context.
The Whitcombe was the first trip I did with SafeNotSafe on me.
At that stage, it was not a polished app story. Starlink had just gone live, the prototype was crude, and the idea was still being dragged out of theory and into the real world.
The trip itself was not a typical hike. I was there with a small Permolat crew doing volunteer track maintenance. We drove from Christchurch to Hokitika, then helicoptered into the mountains near the Main Divide. From there, the job was to cut our way back down the Whitcombe Track and river gorge toward the coast.
On paper, the distances were not huge. In the body, they were enormous.
We were carrying four-day packs and cutting track with hand tools. The route was overgrown and rough: jagged rocks, boulders, river crossings, huge slips, caves, chasms, deadfall, steep sidling, slippery ravines, and a river that felt like it belonged to a much bigger, angrier landscape.
There were four of us, but I was not always with the group. On the first evening I went upstream from Neave Hut toward the rock arch near the Main Divide. On day two I left the main track and crossed toward Wilkinson Hut, staying solo in a remote place that very few people visit. Later, I rejoined the crew. On the final morning I was again working separately while the others went ahead.
That made the check-ins feel real very quickly.
They were not content. They were not performance. They were small signals sent from places where a little context mattered.
The first helicopter pulse said I was flying in. The next said I had landed. Later pulses showed when I had left the hut, when I had stopped, when I had crossed a river, when I was separated from the group, and when I was finally back at the trailhead.
That was the lesson of Whitcombe: in hard country, a simple pulse can carry a lot of weight.
Not because it makes the place safe. It does not. But because it gives the people at home something better than silence.
This trip proved that SafeNotSafe did not need perfect conditions to be useful. It was rough, early, and real. The prototype was basic, but the value was obvious: a few structured signals from hard country gave home more than a vague text ever could. It also proved that transport matters. A trip is not always just walking. Sometimes it starts with a helicopter, moves into track-cutting, splits into side routes, and ends with another flight out. The map needs to tell that story clearly.
This map shows selected SafeNotSafe pulses from a completed Whitcombe Track field trip in January 2025.
No. This is a curated public trip map from a completed trip. It should not be treated as live tracking or real-time rescue information.
The first and last legs of this trip involved helicopter transport. The map includes transport context so the route makes sense instead of presenting every pulse as if it happened on foot.
Because it was remote, physically demanding, and not always group-based. There were helicopter movements, river crossings, solo side trips, remote huts, and track-cutting work in hard terrain.
No. SafeNotSafe does not replace a PLB, emergency services, or good trip planning. It helps hikers keep home informed with simple status, location, time, and context.
Normal texts can work, but they are easy to make vague when tired, wet, cold, rushed, or out of coverage. SafeNotSafe keeps the important signal structured: status, location, time, movement, and the people who need to know.
Available in Canada, Australia, the USA, the UK, and New Zealand for worldwide use.
.svg)
Connecting Hikers with Home
