Sunday, 3 May 2009

Series of Fortunate Events - The Penultimate Peril - GC1K1X0

This was the second cache of the day whilst out on our first caching expedition with the whole family (sarahjones65, CathyMay and RiggyRob). We um'ed and ah'ed about doing this cache as we'd hadn't done any of the others in the series and we hadn't brought the Lemony Snicket books with us.

But, as we were passing by our our way to Cable Bay and the cache near the Burial Chamber there, we decided to give it a go - it would be a nice walk anyway. We parked at the recommended place and then set off for a walk around the lake. Cathy soon met up with some of the local horses and couldn't resist stroking one as it set about eating the fence.

The clue required us to know how many bells ring to summon the concierge - we didn't know, so we guessed and tried all the possible permutations as numbers for the co-ordinates. Our first guess would have taken us straight into the middle of the lake - so that one was quickly rejected! As we walked along on a beautiful sunny afternoon, Sarah came up with something that looked liked a possibility. We were on for it ...

On our way we came across a number of items mentioned in the hint, and we felt bound to search each of them, even though the projected co-ordinates were still some way off. When we got to what we thought was GZ we scrambled up the rocks and it took a good look round and numerous gorse prickles before Sarah eventually found it. She was really pleased.

Because we hadn't really expected to find this cache, I'd left our caching bag in the car, so we had nothing to leave. So we just signed the log, replaced the cache and set off to finish the circular route around the lake. We never did see the hotel's reflection in the lake.

Thanks for bringing us out to a really nice location today, and yes it was a really 'fortunate event' for us - we wouldn't have stopped here if it wasn't for this cache.


Check out this cache here: A Series of Fortunate Events - The Penultimate Peril at www.geocaching.com.

No comments:

Post a Comment