Giant nuclear cover-up? Explosions, military helicopters filmed near elevated radiation zone at border of Indiana and Michiganby Ethan A. Huff, staff writer
(NaturalNews) June 6, 2012, was a very strange day for northern Indiana and southern Michigan, where a series of strange explosions and a subsequent nuclear radiation spike left local residents combing for answers. And though there are still many missing pieces to the puzzle, it has become clear that some type of nuclear cover-up is taking place in the region, which is further evidenced by numerous eyewitness accounts of intense shaking and loud booms, audio recordings of inexplicable explosions, and pictures of unmarked aircraft flying during and after the incident.
It all began when separate radiation monitoring stations -- a privately-owned Radiation Network station near South Bend, Ind., and a U.S. Environmental Protection Agency (EPA) RadNet station near Fort Wayne, Ind. -- detected extremely high levels of nuclear radiation around the same time between June 6 and June 7. Both stations reportedly began to give radiation readings ranging as high as 7,139 counts per minute (CPM), when a normal reading is typically between five and 60 CPM.
You can view a screenshot of the Radiation Network reading, which was later pulled, here: http://www.naturalnews.com/images/Map-US-Radiation-Meters.jpg
As you can see, the South Bend reading shows a shockingly high 7,034 CPM radiation level, which the group later said was incorrect and the result of an "equipment malfunction" (http://www.radiationnetwork.com/Message.htm). But the EPA's RadNet station, which is located about 90 miles away from Radiation Network's South Bend station, also showed elevated radiation levels around the exact same time and on the same day, which leads to more questions about what is really going on here.
RadNet's data has also since been pulled, which is highly suspicious. But if you visit the RadNet Query page (https://cdxnode64.epa.gov/radnet-public/query.do), you can pull up the data yourself from the archive. Simply input "Beta Gross Count Rate (CPM)" in the Selected Parameters box, select Fort Wayne as the Fixed Monitor Location, and select June 6 as the Time Range Criteria.
What you will see are radiation readings that peak as high as 182 CPM around noon on June 6, and suddenly drop to 18 CPM a little more than an hour later. According to the EPA, any CPM level above 100 is high enough to trigger an alert, and yet no official alert was ever issued. In fact, neither the EPA nor anyone else in the government or mainstream media even mentioned the incident, which is now being disregarded as coincidental equipment errors.
Similar high readings were also output by Black Cat Systems, another radiation level tracking site (http://www.youtube.com/watch?v=AwsVLmfZsxk). According to Radiation Network, some of its own stations feed information to Black Cat, which could explain similar incorrect radiation readings being displayed. However, Radiation Network has not confirmed whether or not its South Bend station is one of the readings shared by Black Cat.
Eyewitness accounts indicate strange activity taking place during nuclear anomalyBut the real question here, regardless of the potential Black Cat link, is how could two separate radiation stations nearly 100 miles apart both have equipment errors on the same day around the same time? And what about all the other strange activity that reportedly took place the day of the "faulty" readings, including the deployment of U.S. Department of Homeland Security (DHS) "hazmat" fleets that had allegedly not been moved in years, but that suddenly disappeared?
According to a Reddit reader whose eyewitness account was confirmed by various other readers, a large fleet of DHS emergency response trucks disappeared on June 6 from a parking lot where they had remained unmoved for years. The missing trucks were allegedly emblazoned with a U.S. Federal Emergency Management Agency's (FEMA) National Incident Management System (NIMS) logo, which suggests that a major emergency had occurred that required immediate attention (http://www.infowars.com).
A series of loud explosions that began more than a week prior to the high radiation readings were also reported throughout the region, which adds another element of mystery to this whole situation. WWMT Newschannel 3 ran a report in late May about the occurrence of a "loud explosion like thunder" that resulted in intense shaking felt throughout several Michigan counties. The rumbling was so loud and intense that one local man thought something had exploded inside his house (http://www.youtube.com/watch?v=3oKj_ptBOUE).
In the days that followed, other area residents also reported hearing strange "boom" sounds, and some even reported seeing unmarked helicopters, A-10 Thunderbolts, which are sometimes referred to as the "world's deadliest aircraft," and various other military aircraft and personnel moving in and out of the area (http://naturalsociety.com).
One man who tried to investigate the source of another unidentified explosion further north in Michigan was actually arrested after trying to question the Executive Secretary at the Alpena Combat Readiness Training Center, a year-round National Guard training and exercise facility (http://www.youtube.com/watch?v=AAphZIusdTo).
Some have suggested that either earthquakes or mining operations are potentially to blame for all the strange events. But according to the U.S. Geological Survey (USGS) data, there have been no registered earthquakes detected in the southern Michigan or northern Indiana areas during the time frame in which the numerous large blasts, the intense ground shaking, and the nuclear incident occurred. And many area residents say the explosions and shaking they experienced are unlike anything they have ever experienced before.
So the situation in Michigan continues to remain a mystery that nobody in the mainstream media or government is willing to address, let alone try to solve. Should any further details emerge, NaturalNews will present them for our readers to consider and investigate.
Sources for this article include: