Skip to content

Well Rounded Washington Cacher (Fizzy Challenge) Mystery Cache

Hidden : 6/20/2007
Difficulty:
5 out of 5
Terrain:
5 out of 5

Size: Size:   regular (regular)

Join now to view geocache location details. It's free!

Watch

How Geocaching Works

Related Web Page

Please note Use of geocaching.com services is subject to the terms and conditions in our disclaimer.

Geocache Description:


The cache is NOT at the posted coordinates.

There are specific requirements that must be completed before you may log this cache. Make sure you read the page carefully as it contains important information pertaining to the finding and logging of this cache. The requirements are different than those required for the original Fizzy Challenge, GC11E8N.

GC11E8N – Well Rounded Cacher (The Fizzy Challenge), the original Fizzy Challenge cache, was placed in California by Kealia to honor the cacher FizzyMagic, who has given much to the “local caching community” better know as the San Francisco Bay area. Challenge caches are one of my favorites types of caches – we’ve done a few and always found them to be worthwhile ventures. When I learned of this one, I knew that Washington State had to have its own. This one was placed with the permission and assistance of Kealia. My thanks to him for his help and suggestions, not to mention the original concept; and my thanks to the local reviewers who were also most helpful.


Well Rounded Washington Cachers:

Cacher Requirements Complete Final Cache Logged
hydnsek August 7, 2007 August 7, 2007
MarcusArelius September 26, 2007 October 14, 2007
Prying Pandora August 2, 2008 August 8, 2008
ruck October 12, 2008 November 29, 2008
ohjoy! April 22, 2009 June 12, 2009
GrnXnham June 28, 2009 July 3, 2009
bolosky October 26, 2009 November 1, 2009
GeoEskimo July 8, 2010 July 9, 2010
steve & renee July 12, 2010 July 12, 2010
scorpio1537 July 23, 2010 July 23, 2010
twopeasinapod July 29, 2010 August 3, 2010
CJJIT July 29, 2010 July 30, 2010
K2D2 August 2, 2010 August 3, 2010
tango501 August 25, 2010 August 29, 2010
lamoracke August 28, 2010 August 30, 2010
Corvettekent September 1, 2010 September 3, 2010
GrievousAngel October 21, 2010 October 23, 2010
flip1 December 8, 2010 December 9, 2010
kat2 December 9, 2010 December 9, 2010
GravyMan April 8, 2011 May 22, 2011
Wazzzzu June 12, 2011 July 6, 2011
JustMike September 8, 2011 September 10, 2011
AndrewRJ September 18, 2011 July 13, 2014
jcacher15 August 1, 2012 October 27, 2012
rambudo October 7, 2012 October 11, 2012
benandjayme September 18, 2012 November 27, 2012
pioneer woman October 21, 2013 December 1, 2013
scareway July 19, 2014 July 19, 2014
majeda Sept 2, 2014 Sept 3, 2014
Frisky Biscuits Sept 7, 2014 Sept 14, 2014
Curious Joe Sept 28, 2014 October 8, 2014
rakis2 October 5, 2014 November 2, 2014
Baddog_777 October 17, 2015 November 15, 2015
crs98 November 14, 2015 November 15, 2015
Cool Cow Cachers July 17, 2015 January 23, 2016
crouchcrew July 20, 2016 August 3, 2016
Rock Chalk August 2, 2016 August 12, 2016
obarshay June 28, 2017 July 1, 2017
Krusen4Kache August 27, 2017 August 28, 2017
Muddy Teapot November 7, 2018 November 15, 2018
gsbarnes June 2, 2019 November 23, 2019
mmcash September 29, 2020 September 29, 2020
LFLibrarian August 2, 2021 August 6, 2022
philgeorge1 May 15, 2022 October 12, 2022
The Lime Cat August 13, 2023 August 13, 2023





To be able to log a find for this cache, you will need to first find at least one cache of every difficulty/terrain combination - 81 different combinations – in Washington State. Included in those Washington State finds must be at least one of each of the following cache types:

-- EarthCache
-- Project APE Cache
-- Event Cache
-- Traditional Cache
-- Cito Event
-- Unknown Cache
-- Letterbox Hybrid
-- Virtual Cache
-- Multi Cache
-- Webcam Cache
-- Wherigo Cache
-- Groundspeak HQ


The different cache types do count towards the 81, so if you find a 2.5/2.5 multi-cache, it fulfills both the cache type and D/T requirement. MEGA events and Locationless caches are specifically excluded and cannot be used to fulfill a needed D/T combination. However, a Project APE cache is required as Washington does currently have one of these rare caches. An Important Note: Please be aware that Washington State now has all of the 81 D/T combinations. All D/T combinations are now required.

Basic Rules:
  • Caches used to satisfy the requirements for this cache must come from Washington State only. If you live elsewhere and wish to log the final, the caches you use to satisfy the requirements for this challenge must be Washington State caches. Please do not ask me to waive this rule.
  • All prior cache finds do count. Your own hides will not apply towards the goal.
  • All finds except CITO and Event caches must be on caches that were published on or before May 3, 2010 to avoid dummy caches being listed just to meet the requirements of this cache. The exceptions may be (at the cache owner's discretion) caches published that satisfy a D/T combination that didn’t exist or were rare prior to the publication of this cache (see below for specific exceptions). Those exceptions may be added if there is adequate evidence that they are indeed the D/T combination stated. In the event that such a cache becomes allowed, the placer will not receive credit for the D/T combination of the stated cache. They will still be required to go elsewhere to satisfy that D/T rating if such a cache exists in the state. As of Feb 3, 2023 there is no longer a publication date requirement for the Washington Fizzy. It's outlived its usefulness. I reserve the right to reinstate it if people publish caches with false D/T combos just to get the Fizzy. Please don't.
  • No rating changes of existing caches will be accepted as counting towards the goal. Be aware that on occasion, a cache owner may adjust a cache's D/T rating based on feedback from finders or for some other legitimate reason. In that instance, the D/T rating that a cache has at the time a seeker of this cache submits his completed bookmark list is the D/T rating that will be used. Please recheck your D/T grid carefully before you submit your list.
  • Generally accepted Geocaching.com rules, guidelines and conditions for logging a cache find will apply. All caches used to satisfy the requirements for this challenge must be logged physically and online.
  • The caches must be listed on Geocaching.com only, and you must have personally (physically) found and logged each cache. Caches found on other caching sites will not be allowed.
  • Logging finds on caches you placed will not be allowed. Please be aware of the distinction between a cache placed by a cacher and a cache adopted by a cacher. Caches (finds) owned but not originally placed (adopted) by the owner may be used for the purposes of this challenge.
  • You may have others with you when you log the final, but only those who have fulfilled ALL criteria for this cache will be allowed to log it as a find.
  • Finds without appropriate back-up (see below) will be deleted.
  • This cache will not count as a 5/5 D/T. You must find another one before this one.
  • When in doubt ask -- we can discuss it or even seek guidance from others, but the final decision rests with the cache owner.

Dis-Allowed Caches: The following caches may not be used to satisfy a needed D/T for this cache. Those removed at the request of their respective owners were done so after serious discussion and consideration. If you have questions about those, you may contact either the cache owner or myself by e-mail. The are listed in order by GC number.
  • GCKFFG -- The Hardest Cache You'll Ever Do by ohjoy! -- removed at owner's request
  • GCV5EV -- Madame Defarge Takes Up Crochet by Hoppingcrow -- removed at owner's request
  • GCXBR6 -- Welcome Home Mike! by Dragonfly -- terrain level changes are made depending on water level at the cache site

Miscellaneous Notes:
  • August 15, 2007: A forum thread pertaining to this cache can be found here.
  • May 30, 2009: Rules concerning GC13YM7 have been removed as there is more than one of that D/T combination. Additionally, Caches that you have found, that you did not place, but that are currently owned by you through geocaching.com's adoption process may be used towards this challenge.
  • July 7, 2010: Several rules have changed. The cache publication cutoff date has been changed to May 3, 2010. All caches used to satisfy the requirements of this challenge must have been published on or before that date. Additionally, all 81 D/T combinations now exist in Washington State and are required to finish this challenge. Also, there are two additional icons required as part of the challenge -- a Wherigo cache and Groundspeak Headquarters.
  • August 3, 2010: Because we are nearing the end of my supply of coins for this cache, I'd like to make sure that it is understood that the final for this challenge must be found and logged before a coin can be awarded. Only the first 15 finishers are guaranteed to receive a coin. I have a very few in reserve being saved for unforeseen emergencies (I have actually had to use one.) but I will award them until I run out. I will post here and in the forum thread when I am out. I am considering a pathtag for future finishers.
  • August 30, 2010: Regarding event caches: Effective this date, regular type (mega, regular, special, ie 10 year) event caches with a D/T rating larger than 2/2 may not be used to satisfy a specific D/T rating. Such caches may be used to satisfy the event requirement only. Special type events such as a mega or the 10 year events may be used in place of a regular event to satisfy the event requirement. Additionally, when you attend a CITO event, you are expected to participate in the 'reason' for that type of event. Expect some fine tuning of this rule in the near future.
  • January 1, 2011: There are no further geocoins available to be awarded. :-(
  • October 13, 2011: The APE cache, now archived in this state, is no longer required for this cache.
  • August 16, 2021: 5/4 and 5/3.5 D/T combinations are no longer available in Washington in caches old enough to qualify. Therefore, for these two combinations only the cutoff date of publication is extended by 10 years to May 3, 2020. In addition, the APE cache has been unarchived and so is once again required.
  • February 3, 2023: Two rule changes today: the cache publication date requirement is removed (and will stay that way as long as people don't abuse it), and you don't have to wait for a signoff on your list (but you still have to post it).

Keeping track:
  • Create a bookmark list and keep track. A shared version of this will be required to claim a find.
  • Although not required, FizzyMagic's FindStats program can be helpful. (A download is required to use this program.) This is especially useful for gpx files generated by pocket queries, such as from bookmarked cache lists. Cachers who have finds in other states in addition to Washington may find this useful. FYI, as I played with this program, I found that files generated by GSAK did not work.
  • For GSAK users, try this macro. Although I haven't yet played with it, it appears that a GSAK database containing all of your Washington State finds could be used here. The use of GSAK and this macro is not required for this cache. Thanks to Allanon for the suggestion.
  • You are more than welcome to post notes and/or pictures of your progress here as you work towards the final.

To get (and keep!) credit for this find:
  • When you have found all of the required combinations, post a note to this cache page and include a link to your shared bookmark list showing all the caches that meet the requirements. Keep this bookmark list (and link) available to other cachers for a minimum of 3 months after completing the challenge.
  • For ten of the caches on your bookmark list, include what type (i.e., Traditional, Virtual, EarthCache) of cache it is in the comments section for that cache. Make sure each of the ten required cache types are included. Please do not do this for every cache on the list.
  • A minimum of 81 caches are needed on your bookmark list to be eligible to log the final. You may include more than the minimum required number of caches as it never hurts to exceed the minimum requirements, but please limit your list to 400 caches.
  • The C/O will not necessarily verify your list but reserves the right to audit it if he's bored (or suspicious).
  • Once verification has shown that you have successfully completed the challenge, you will be given permission to find and log the final.

About the final cache:
  • The D/T for the final is 3/4. Most of the short hike to this cache is on well-maintained trail. Once you have left that, the terrain rapidly deteriorates and a fair amount of care should be taken for the relatively short distance to the cache. Make sure you admire the nearby falls on the way to your find. (Take that as a strong suggestion.)
  • The attributes shown above pertain to the final cache.
  • It is difficult to get an accurate GPS reading. Several readings are available for your use, including bolosky's, GeoEskimo's and and a new version of the final coords, updated on 7/9/10. Those coords were averaged over 10-15 minutes, with the GPS reporting 28' accuracy.
  • Stay on the trail until you get to the first obvious and pronounced left turn, a bit past a 'flight' of milled log and dirt 'stairs'. At this point, you will turn right on a social trail towards the large creek.
  • Do not take the shortest route you can find to the cache. It's just plain not safe!
  • You will not need to cross the creek to find the cache.
  • The cache is a large Lock 'n' Lock.

To quote Kealia: "This should be fun and I'm counting on the honor system for sticking to the rules. . . . I will spot check the finds, but don't want to have to be the cache police and check every find. Please "play" fair and have a good time!"





    Additional Hints (No hints available.)