Re-posted with Permission from: Copyright 2011-3011 Chase Kyla Hunter & Alternative News Report, All Rights Reserved. All re-posts must leave all content, author, blog name, original URL location & copyright stamp intact. Love this news blog? Shop here & support it!
The NASA Red X question has been answered. It was not NASA who answered it, but YT user BooTubeDude, lol. Here’s the video explanation.
Earlier I reported…
NASA continues to assure and re-assure Americans and the world that all is well in our skies and that Comet Elenin will definitely NOT hit the earth and that we are all safe; no harm will come from Comet Elenin’s passage. Meanwhile, back at the ranch, they have created a “preparedness video” for their own staff which I posted earlier this year, and now comes the colossal RED X. At the end of the video which reports on this odd marking, the YT reporter displays three letters:
I second that emotion.
This news has been reported on Above Top Secret just recently but I have been traveling and just found the terribly ominous and bothersome video today. Watch the video below and do a Google search just exactly as the video instructs. I did it in less than 2 minutes. You will be given a link which is second in the search results, which when clicked, asks if you would like to see the results displayed in Google Earth. [ You have to have Google Earth downloaded as a free app and on your HD to have it open in Google Earth to display the kml file search result which is circled below. ]
Is this huge ominous red X a pre-determined speculative “strike zone” for Comet Elenin? The search results come up in a Comet Elenin search.
Would NASA care to explain to the nation and the world what they know, and possibly avoid a permanent loss of the nation’s trust as well as their credibility as a taxpayer funded government institution for science and astronomy? Our national interest here is clearly at stake. Citizen journalists want to know:
Make a direct donation to this news blog here. Thanks! I really appreciate your support.
Error: Twitter did not respond. Please wait a few minutes and refresh this page.