New reports of footprint finds have surfaced. Images and links to videos.
October 18th: Monster Mash and TX Bigfoot
You can’t go wrong with the choices you have for this special day.
What Would You Put In A Bigfoot Display?
Okay, this is your chance to sound off on what you want to see on display in a new developing Bigfoot exhibit. What are your ideas for two new glass museum cases here at the International Cryptozoology Museum? Lots of images.
Should Homin Replace Bigfoot?
Time for a change? What do you think? Should we follow the Russians? Ivan T. Sanderson, in the 1960s, tried to convince everyone to use “Oh-Mah.” Grover Krantz wanted people to employ the term “Sasquatch” instead of “Bigfoot.” Is there a movement afoot for change?
This Date in Bigfoot History: October 5, 1958
Don’t miss this significant milestone! What pivotal event happened on this day, 50 years ago? Images.
Crowd Cheers Bigfoot Banned Book Reading
The Daily Egyptian publishes their article mentioning Shelley Cox’s reading of my burned book. Here are her highlights from being there. Photo of the demonstration.
October 1958: Bigfoot’s 50th Anniversary!
It has been five decades since the first broad-based use of the term “Bigfoot” was used, and began to replace “Sasquatch” to describe large, hairy, bipedal hominoids in the Pacific Northwest of North America. This article tries to unravel this month’s 1958 incidents. Images.
Siblings in Cryptozoology
Who are the brothers and sisters in the field? How many brothers, how many sisters, how many siblings have found themselves together within cryptozoology or nearly so, in linked investigations or overlapping strangeness? Images.
Used Cryptozoology Books
Most of these are used, some are new, and all are available directly from Arcturus, not from me. I thought some readers who don’t have these titles might be interested in this new list, just published today.
Mass Monster Mash: Coming October 18th!
Halloween is coming soon, but this will happen first. Poster image.
Follow CryptoZooNews
Not Found
The resource could not be found.