Newspaper article The Christian Science Monitor

Walking the Amazon

Newspaper article The Christian Science Monitor

Walking the Amazon

Article excerpt

When Ed Stafford was a teenager, his taste for adventure was a bit unconventional. I have always thrived on danger and adrenaline and sneaking out of my boarding house armed with a wire saw and industrial bolt cutters to cause havoc seemed to be my main outlet at the time, Stafford recalls in Walking the Amazon.

Breaking and entering isnt a great way to pass the time (beyond its anti-social aspects, its pretty much against the law), so Stafford looked for pursuits that would keep him from spending his life in an office or jail. He joined the British Army and served for four years. He then came home and asked himself: What would be the ultimate expedition I could ever conceive of doing?

The answer, of course, is the title of his gripping memoir, which recounts the 2-1/2 years that Stafford spent walking the entire length of South Americas longest river, securing himself a spot in the Guinness World Records.

20 banned books that may surprise you

Beyond the sentient threats within the area (jaguars, snakes, piranhas, electric eels, wary indigenous tribes), he had to negotiate harsh terrain that ranged from steep high cliffs to flooded lowlands. And the path he was following from Peru to Colombia and on to Brazil cut through the worlds largest narcotics- producing areas.

No one in the world of expeditions ... could be convinced that it was in fact possible to walk the entire length of the river, Stafford wrote. He was 31 when he began the trip with his friend Luke Collyer, then 35. After securing sponsorship money to help raise awareness of ecological threats to the Amazon region (The selfish and non-selfish goals werent just compatible; they ended up being essential to each other), Stafford set out for Peru in April 2008 with Collyer, a veteran climber and kayaker. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.