Re: [Az-Geocaching] Hazard of putting a travel bug in a high…

Top Page
Attachments:
Message as email
+ (text/plain)
+ (text/html)
Delete this message
Reply to this message
Author: Tim Giron
Date:  
To: listserv
Subject: Re: [Az-Geocaching] Hazard of putting a travel bug in a highly exposed cache
Actually, looking at the logs, it appears that two teams were there
at the same time and cross-swapped bugs through the cache. One of
them just hasn't logged picking up the bug, yet, so I think Stephanie
is currently out of danger.

Tim
Team AZFastFeet

>One of my travel bugs, established in honor of WNBA player
><http://www.geocaching.com/track/track_detail.asp?ID=6792>Stephanie
>McCarty, was placed in a
><http://www.geocaching.com/seek/cache_details.asp?ID=32295>geocache
>last night that the most recent cache finder reports as being
>"exposed". Other finders of this cache also report that this cache
>is not well hidden. I will offer a cautionary warning about putting
>a travel bug in an exposed cache that is likely to be found by
>accident.
>
>There is a chance that the cache could be accidentally found and
>removed, with the travel bug inside, before the next geocacher finds
>it. This happened at the
><http://www.geocaching.com/seek/cache_details.asp?ID=11072>Park and
>Cache cache in Mesa. A
><http://www.geocaching.com/profile/default.asp?A=28369>geocacher put
>the
><http://www.geocaching.com/track/track_detail.asp?ID=2958>Boothia
>travel bug in it on June 9, and the cache (with travel bug inside)
>was apparently nabbed by a park employee before the next geocacher
>attempted to find it on June 13. Thus, this travel bug appears to
>be gone for good.
>
> Ken (a.k.a. Highpointer)