‘84 Olympics ufo — Control Alt History

HIGH STRANGENESSWhere does one even begin to analyze this event? Well, for starters, I hate to break anyone’s bubble, but it’s highly doubtful that the spaceship or the alien were real. Hollywood producer David Wolper is the man credited with producing the ’84 ceremonies. In a 2009 article for The LA Times, he described in detail how they put together the finale featuring the UFO. Former Disney amusement ride designer Bob Gurr is credited with creating the UFO, and he described the process in a 2004 article. The story they tell is that the UFO was made in a factory in California, then suspended over the Rose Bowl by a cable attached to a military helicopter, which was difficult to see against the night sky. Their stories seem detailed enough to make this a believable explanation. Of course, you can take their words with a grain of salt, if you want to. People lie all the time. Especially Hollywood producers. And Disney is one of the shadiest companies in the world, so you’d be perfectly justified in being skeptical of what anyone associated with Disney says. So…you can believe them or not. There have been people over the years who’ve claimed the UFO was flying under its own power. But the explanations given by Wolper and Gurr are detailed enough to support the idea of the UFO being built in a factory, then carried by a helicopter as if hovered over the Rose Bowl. Oh, and about that alien. In a recent interview, basketball player (and tallest man in the USA) George Bell said that he was the person in the alien costume.

🔐 Cryptographic Verification

�� CONTENT HASHES: SHA-256: 78c0a171dffff06cc09939a878bc51a6d31e6a05d18a6bafab2eca6f3023579b BLAKE2b: f3126c54180eac6a600f5b91c2aad9e696cde1e76ad232934dabd29dab5d01dd MD5: 0c26082d4bf8a39d99f29056aeef673b �� TITLE HASHES: SHA-256: 75365e6c97030efbf362f13fa7f1b8df8614687a892678f480edec6c2711071e BLAKE2b: 897a318a72399a63bc30741231d35e3aa5a0aeaabde6b8df4f48fe1e0d6a6e84 MD5: dc9ad6fec8e4904d013f23c27c31b73a �� INTEGRITY HASHES: SHA-256: de6f41f2ad997517540171110e0a981ae800978fd590d48ff70231db03a9b35a BLAKE2b: ab4cced1806478d86a01f4956656fde5dde09bcb9de7dcf109037c9ce1947b8b MD5: fc3a943c0f74212e682337d702c5b097

Archived with ArcHive - Client-side cryptographic archival system