Tb Placed In Unapproved Cache

[+RAC 'N' T-BO]

Hi all.

 

I hope someone can help us.

 

We own a TB (TBHPWT) Ferdinand The Fire Bear, which we started in the UK. The TB found it's way to Latvia where it was placed in a cache that went on to be not approved so the TB is stuck in it. Is there a way the owner of this cache can appeal against a decision not to approve it?

 

Hope to hear from you all soon

 

Tim and Rachel

[+Renegade Knight]

The owner of the cache can also remove the bug and send it's on it's way. That's the right thing to do.

[+The Leprechauns]

RK has the correct answer. When it's really sad is when the cache was denied because it was hidden by someone who was on holiday, and cannot easily return to pick up their trash. In those cases, the volunteer cache reviewer may be able to help out, by whispering a set of coordinates to a local geocacher and hinting that a stranded travel bug might be there.

 

Latvia has its own volunteer cache reviewer, who also has good English skills, so language should not be an issue.

[+RAC 'N' T-BO]

How would I get in contact with the reviewer from latvia ? Maybe then I may get some joy. Can you help at all please ?

 

Tim and Rachel

[+Renegade Knight]

How would I get in contact with the reviewer from latvia ? Maybe then I may get some joy. Can you help at all please ?

 

Tim and Rachel

You have to ask in the forums since GC.com doesn't keep a list of who reviews where. I'll lay odds keystone has already given them a head up.

[+fauxSteve]

Actually, it looks like the unapproved cache isn't in Latvia, but in Tajikistan. Now that's a jump! Best of luck finding a local cacher considering there aren't any active caches in that country right now. It looks like you need to track down the approver for central Asia.

[Keystone]

I looked at the cache, which was quite properly archived by erik88l-r on the grounds that it was hidden beyond the owner's maintainable distance. It's a 5/5 cache on top of a mountain, and the next nearest cache is 75 miles away. Not a good place for a travel bug, and I'm not sure what might be done by way of a rescue mission. Here in the US we are often able to enlist the owner of a nearby cache to investigate matters like this.

[+Rick618]

Seems like the thing to do would be to reactivate the cache with a BIG note on the page asking the next cacher to remove the container and tb. Archive after the tb and geo-litter are removed.

[+welch]

Seems like the thing to do would be to reactivate the cache with a BIG note on the page asking the next cacher to remove the container and tb. Archive after the tb and geo-litter are removed.

that would get this one removed, (it would violate the 3mo permance thing) but more important would it cause more caches like it? Just put 'please remove after finding' and its ok??

There have been suggestions of 'limited life' caches in the past, and that didn't become an option then. I don't recall the exact reasoing, but I doubt it would fly now.