Showing posts with label Nuclear. Show all posts
Showing posts with label Nuclear. Show all posts

Monday, March 27, 2017

UFO Reported Over Cooper Nuclear Station, Declassified Documents Reveal

Bookmark and Share

UFO Over Cooper Nuclear Station - Nuclear Regulatory Commission (NRC) (Pg 2)

Background

     According to the U.S. Nuclear Regulatory Commission (NRC):

The U.S. Nuclear Regulatory Commission (NRC) was created as an independent agency by Congress in 1974 to ensure the safe use of radioactive materials for beneficial civilian purposes while protecting people and the environment. The NRC regulates commercial nuclear power plants and other uses of nuclear materials, such as in nuclear medicine, through licensing, inspection and enforcement of its requirements.
John Greenewald
By John Greenewald
The Black Vault
3-23-17

Over the years, many UFO reports have surfaced regarding unidentified craft being seen over sensitive nuclear installations. It only makes sense, that the NRC would be a prime target under the Freedom of Information Act (FOIA) for documents relating to the phenomena.

The documents were received relatively quickly. They were requested by The Black Vault on February 27, 2017, and were declassified and released to me on March 23, 2017.

Most surprising, there is new information never-before-seen within these records. It is revealed that a former security guard of the Cooper Nuclear Station witnessed a UFO sometime between the years 1986 and 1989. The report described the UFO encounter as the following:
While posted at the intake structure one night, he observed an “unidentified flying object” fly down the Missouri River about 150 feet in the air and hover in front of the intake. He observed it for a few moments and then contacted a fellow security officer who also observed it (he could not recall the individual’s name exactly but his first name was [REDACTED] and his last name was either [REDACTED ]. After they together observed the UFO, it turned and went back up the river and did not come back that shift. He and the other officer shared their observation with their peers who did not believe them.

The next evening he again was posted at the intake and observed the UFO return again. This time he didn’t call anyone until the UFO had traversed into the protected area and hovered above the protected area just north of the Reactor Building. He said it was roughly triangular in shape with a circle of rotating lights on the bottom. He could not hear any propulsion noise from the UFO. He believes that it was roughly 1/3 the size of the Reactor Building. Once the UFO hovered in the protected area. He called the security break room and most of the officers on shift observed the UFO.
Interestingly, after the report was taken by the NRC, the documents were compiled and sent to Cooper Nuclear Station in 2010. Although no formal response was requested, Cooper Nuclear Station was told only to tell employees there that were on a “need to know” basis.

The declassified records also include reports submitted by the public to the NRC about UFO activity, and even alien technology. The NRC gave the standard response to all of the letters sent in, that the NRC mission did not include the topics they were writing about.

The declassified documents can be seen here, in their entirety. They are unedited and appear exactly how they were received by The Black Vault from the NRC.

Monday, June 03, 2013

Reprise: UFO Activated Nuclear Missiles at Minot AFB Says One Retired Launch Officer


Bookmark and Share

Launch in Progress

By Robert Hastings
www.ufohastings.com
© Copyright 2008 - 2013

Retired U.S. Air Force Captain David H. Schuur--whose dramatic testimony about a UFO temporarily activating his nuclear missiles at Minot AFB, North Dakota, in 1966--died on May 31, 2013. Schuur's tape recorded statements during his interview with UFOs and Nukes researcher Robert Hastings were published here in 2009 and are presented again below.

     Of all the interviews I’ve conducted with former or retired ICBM launch officers over the past three decades, this was perhaps the most disturbing. According to the source, David H. Schuur, a UFO had apparently activated the launch sequence in most of his Minuteman missiles.

In August 2007, Schuur told me, “I saw your request for information in the [June 2007] Association of Air Force Missileers Newsletter. I was involved in a UFO incident at Minot AFB in the mid-1960s. I had read your earlier article [in the September 2002 AAFM Newsletter] but was hesitant to respond.” I asked Schuur why he had been hesitant. He replied, “Well, we were basically told, way back when, that it was classified information and, you know, it didn’t happen and don’t discuss it. I guess I was still operating on that idea when I saw your first article.”

Schuur had obviously had a change of heart. He continued, “Anyway, I was a Minuteman missile crewmember in the 455th/91st Strategic Missile Wing at Minot from December 1963 through November 1967. I was a 1st Lieutenant during that period and the deputy commander that night. Since the incident occurred some 40 years ago, my memories are a bit foggy but, based on who my commander was at the time, I would say it occurred between July 1965 and July 1967.”

I asked Schuur if he could narrow the time-frame during which the incident occurred, by associating it with another event. He replied, “Not really, but my sense is that the incident occurred toward the end of my duty in the [missile] field, so it was probably during 1966, or ’67. I was pulling alert in the Echo [Launch Control] Capsule and was at the console at the time, probably early in the morning when the commander was sleeping. I know I was at Echo because that’s where I pulled almost all of my alert duty. My crew commander at the time has died. He was a Lieutenant Colonel at Minot, in his 50s—he was in the reserves, an old Korea veteran, who was recalled to duty in the early 1960s.”

“As far as the incident, here’s my best recollection of it: Alpha capsule, which was east of us, reported on PAS—the Primary Alerting System—that their security personnel were observing a large, bright object hovering over some of their missile sites. It was moving from missile to missile. I think the Alpha missile crew also reported that they were receiving ‘spurious indicators’ on their missile control console, but I’m not certain about that. I know that a few minutes later our capsule had spurious indicators—anomalous readings—from some of our missiles.”

I asked Schuur to explain PAS. He said, “It was an open line between SAC headquarters and the wing command posts. There was a speaker in each launch capsule and when the command posts issued a directive, or whatever, we were able to hear it. When Alpha had their UFO sightings, they alerted the command post, at which time the command post called SAC headquarters. So, when the report of the sightings went out, we all heard it on PAS.”

Schuur continued, “But it wasn’t just Alpha and Echo. Over the next hour or so—I don’t recall exactly how long it was—all of the flights reported that their [Security Alert Teams] were observing a UFO near their facilities. The path of the object could be followed as it passed over each flight area by the reports on the PAS. The object moved over the entire wing from the southeast to the northwest, following the layout of the wing.”

Schuur elaborated, “All of them—Bravo Flight, Charlie, Delta, right on down the line to Oscar—were reporting sightings of this object. Minot’s missile field is laid out like the letter ‘C’. Alpha is located southeast of the base, and the other flights—Bravo, Charlie and so forth—were south, southwest, west, northwest, then north of Minot. Oscar, the last flight, is at the top of the ‘C’, north of the base. The object—as far as I know, it was only one object—came across Alpha Flight, then moved all the way around the flights and ended up at Oscar. We could hear that on PAS. At Echo, it didn’t come close to the Launch Control Facility, it just visited the LFs (silos), then passed onto the next flight.”

“As far as our flight, Echo, a few minutes after hearing the report from Alpha, I received a call from topside security that a large bright light—actually, a large, bright object would be more accurate—was in the sky, to the east of the launch control facility. When the guard called down, he may have used the term ‘UFO’ but I don’t recall. He didn’t describe it’s shape or altitude because it was too far away. It never got close enough to the LCF to see any detail. At its closest, it was two, three, maybe four miles away from us, near one of the missile sites.”

Schuur continued, “However, when the object passed over our flight, we started receiving many spurious indications on our console. The object was apparently sending some kind of signals into each missile. Not every missile got checked [out] by the object, but there were several that did. Maybe six, seven, or eight. Maybe all ten got checked, but I don’t think so. As this thing was passing over each missile site, we would start getting erratic indications on that particular missile. After a few seconds, everything reset back to normal. But then the next missile showed spurious indicators, so the object had apparently moved on to that one, and did the same thing to it. Then on to the next one, and so on. It was as if the object was scanning each missile, one by one. The Inner Security and Outer Security [alarms were triggered] but we got those all the time, for one reason or another. However, on this particular night, we had to activate the ‘Inhibit’ switch because we got ‘Launch in Progress’ indicators! After a few minutes, the UFO passed to the northwest of us and all indicators reset to normal.”

I wanted to be certain about what I had just been told. I asked Schuur, “So, if you get a Launch in Progress indicator, does that mean the launch sequence has been triggered—that the missile is preparing to launch?” Schuur replied, “That means the missile has received a launch signal. When that happens, we get an indication in the capsule that a launch command has been received by that missile. If that happens, without proper authority, you flip what’s called an “Inhibit” switch, to delay the launch for a given period of time. If an Inhibit command comes in from another launch capsule, that shuts down the launch totally. But if that second command doesn’t come in, the missile will wait for a specified period of time and then launch automatically at the end of that expired period—theoretically. Of course, that night, we had all kinds of other indicators coming on from each missile so, in that situation, the launch probably would have aborted itself. I honestly don’t know.”

I asked Schuur if the Launch in Progress indicator had ever been triggered on any other occasion, either before or after the UFO incident, while he was on alert duty. He replied, “No, never.”

I asked Schuur if he had heard about missile maintenance teams having to replace components or whole systems in the affected missiles—the ones that generated the spurious readings. He replied, “No, if that happened, I never heard about it.”

Schuur said, “Upon returning to the base the next day, my commander and I were met by the operations officer. He just said, ‘Nothing happened, nothing to discuss, goodbye.’ Our logs and tapes were turned in. Every capsule had a 24-hour tape that, as I recall, recorded the communications that went over the PAS system, so all the reports would have been on that tape. But we were essentially told that nothing had happened that night and to discuss it no further. It was a non-event. We were never debriefed, by OSI or anyone else. We just went home. Most of the returning missile crews drove back to the base from their facilities, so they all arrived at different times. There was no group debriefing that I know of. I never heard another thing about the incident.”

I asked Schuur, “I know that you were given no feedback from your superiors, but what is your personal assessment of the event?” He replied, “Oh, I think something was up there, uh, scanning the missiles, seeing what was going on. Some kind of a scanning process.” I asked Schuur whether he thought the launch activation had been incidental or deliberate. He seemed surprised by my question and said, “I think that the scanning just set it off. It set all kinds of things off, we were getting all sorts of indicators. There were some kind of signals being sent [from the UFO] to the missile that inadvertently triggered the launch activation, but I don’t think it was deliberate. I hope not! That would have been—.” Schuur didn’t finish this sentence. His voice broke and he heaved a deep sigh. Apparently, the thought that those aboard the UFO might have deliberately attempted to launch his nuclear missiles that night had caused him to pause—and probably shudder—over 40 years later.

I obviously accept Schuur’s report as credible, but am of course attempting to locate other former members of his squadron who are willing to corroborate it. As Schuur candidly admitted, after reading my first article in the September 2002 AAFM newsletter, he waited some five years before approaching me. It was only after my second published request for information from former/retired USAF missileers, that he decided to unburden himself. This hesitant response is not atypical. Many of my former missile launch officer sources have not readily or easily divulged their UFO experiences to me, for one reason or another.

Importantly, to my knowledge, Schuur’s testimony represents the only credible report on record of a UFO temporarily activating a U.S. nuclear missile. However, there is one other reliable report of such an activation—in the Soviet Union. That incident will be discussed at length in a later chapter.
* From the book UFOs and Nukes by Robert Hastings
* Available only at www.ufohastings.com (after July 18, 2008)

Wednesday, January 09, 2013

Declassified Government Documentary On Atmospheric Nuclear Weapons Testing: Operation Dominic - Johnston Island (Pt 2) | VIDEO

Bookmark and Share

Operation Dominic Documentary 2 (Still From Video)





See Also:

Declassified Government Documentary On Atmospheric Nuclear Weapons Testing: Operation Dominic (Pt 1) | VIDEO

Blast From H-Bomb Reaches 400 Miles into Space; Causes Communication Blackout | Operation Fishbowl (7-10-1962)

UFO Activity at Nuclear Weapons Sites:
An Overview



SHARE YOUR UFO EXPERIENCE

Declassified Government Documentary On Atmospheric Nuclear Weapons Testing: Operation Dominic (Pt 1) | VIDEO


Bookmark and Share

Operation Dominic Documentary Video





See Also:

Blast From H-Bomb Reaches 400 Miles into Space; Causes Communication Blackout | Operation Fishbowl (7-10-1962)

Nuclear Security Helicopters Testing Radiation Levels Above DC Area

UFO Activity at Nuclear Weapons Sites:
An Overview



SHARE YOUR UFO EXPERIENCE

Monday, October 31, 2011

Two Former World War II Fighter Pilots Report UFO Experiences at the Hanford Plutonium Production Plant in 1945

Bookmark and Share


By Robert Hastings
www.ufohastings.com
10-31-11

     When World War II ended, in September 1945, Clarence R. “Bud” Clem was a Lieutenant Junior Grade (Lt. jg) in the U.S. Naval Reserves, serving as an F6F Hellcat fighter pilot assigned to Air Group 50 aboard the U.S.S. Cowpens CVL-25. In an email, Clem told me, “[After the Japanese surrendered,] the Cowpens was the first aircraft carrier to arrive in Tokyo Bay and I was with the first flight to land at Yokasuka Naval Air Station (NAS) that day.”

However, nearly a year earlier, the Hellcat squadron had been based at NAS Klamath Falls, Oregon. “[During that same period] our group was deployed to NAS Pasco, Washington for ground support training in March 1945.” Clem wrote, “The Hanford Ordnance Works was just across the Columbia River from Pasco and designated TOP SECRET. We experienced an unknown object over the Hanford site in March/April, 1945. I did not fly after the object, as two members of our squadron did, but I did assist in trying to determine what was going on. I am 84 [years-old] and I do not know if any other members of our squadron are still alive who could add more information. If you have any information about our experience, I would like to see what the official report stated.”

The plutonium produced by Hanford was used in the first atomic bomb test, conducted in the New Mexico desert on July 16, 1945, as well as in the bomb dropped on Nagasaki, on August 9, 1945.

I wrote to Clem, saying that I didn’t have any official reports relating to the incident. I then asked for more details. Clem responded:
One night, shortly after the evening meal, the officers were gathered at the Officers Club for relaxation when the duty officer at the tower called our commander with a request. Lt. Commander Richard Brown took the call, as the Captain was in conference. Ensign C.T. Neal and I were with Brown and he asked us if we would volunteer to go with him to the flight line for possible duty. We both agreed and a jeep was waiting at the door to take us to the flight line. We learned that an unknown ‘bogey’ was over the Hanford Ordnance Works, according to the radar operator located on an auxiliary field just across the Columbia River from Hanford reservation.

We had been instructed upon arrival that the Hanford Ordnance Works was Top Secret and NO flights over any part were permitted...We did not know about the radar, but the duty officer stated that something was in the sky over the area and wanted someone to investigate. A plane was [already] armed and warmed-up on the tarmac. Brown stated he would go and Neal was to stand-by in another plane, in case of trouble. I was to join the [controller] in the tower and communicate info from radar to the pilots.

Brown quickly found the object, a bright ball of fire, and took chase. But he could not close, even with water injection that gave a quick boost in speed. The object headed out NW towards Seattle and was quickly lost by radar. Brown returned to base and we three retired to the club, still shaking and wondering what we had encountered.

Memory does not recall details of two similar experiences—I think Neal was to take the next chase—but the object disappeared before he got airborne. I was assigned to fly the entire [Hanford] reservation at low altitude (200 feet or so) to give the radar operator the blind spots [caused by the terrain]…

The third, and last attempt on our part to ‘catch’ and identify the object came just shortly before we returned to Klamath Falls, and then on to California and Hawaii, before joining the 7th Fleet in combat. I do not know if any other incidents occurred after we left Washington. None of the above information was mentioned in the ‘history’ of our squadron but I wonder what is on record at NAS Pasco.1
I asked Clem, “During the first incident, how long did it take for the aircraft to get to Hanford?” He replied, “Not long. An aircraft was always ready to fly on short notice to intercept the Japanese incendiary balloons. If you’ve read the history of that project, and the concern the balloons caused, it would have been logical to intercept them before they could reach Hanford.”

I asked Clem if the pilot on the first night, Lt. Commander Brown, had described the object in detail, either over the radio or back at the Officers Club. Clem replied, “He just said it was so bright that you could hardly look directly at it. As he closed on it, it took off to the northwest at a high rate of speed. No maneuvers really, just a straight-line course.”

Other questions to Clem added few details. He later sent me his military records which revealed that the fighter squadron was actually at Pasco from January 9 to February 15, 1945, not during March and April, as he had first indicated.

But Bud Clem’s account is not unique. Another former World War II fighter pilot, Rolan D. Powell, states that he too was involved in a UFO intercept attempt at the Hanford plant, possibly in July 1945. That incident was first mentioned in a self-published book by Byron D. Varner, an aviation cadet during World War II whose naval career included a 13-year stint as a Navy Public Affairs Officer.

Upon learning of Powell’s report, Walt Andrus, former International Director of the Mutual UFO Network (MUFON), located and interviewed him. According to a short article available at nicap.org, Powell told Andrus that while he was unaware of the whereabouts of the other five aviators who had been involved in the action, and did not even remember their full names, they had nevertheless belonged to a squadron of 12 veteran fighter pilots who had survived combat in the Pacific as members of Air Group 3, while assigned to the U.S.S. Yorktown CV-10.

According to the article:
Powell estimated that the event took place six weeks before the Japanese surrendered on September 2, 1945, which puts the sighting in the middle of July 1945.
Powell told Andrus that six F6F [aircraft] made visual contact with the object, [which was] described as the size of three aircraft carriers side-by-side, oval shaped, very streamlined, like a stretched-out egg, and pinkish in color. Powell reported that some kind of vapor was being emitted around the outside edges from portholes or vents. He speculated that the vapor was being discharged to form a cloud for disguise. The object was observed at noon in a clear sky at an estimated altitude of 65,000 feet.

The F6Fs went up as high as 42,000 feet, well above their rated ceiling of 37,000 feet, but could not reach the large object, which hovered above the Hanford nuclear reactor for an additional 20 minutes, before going straight up as the six Hellcats gave up the intercept.2
A rather dramatic account, to say the least! Hopefully, at least some of the other members of Powell’s squadron who participated in this action can be located and interviewed. Efforts are currently underway to do just that.

In any case, given Bud Clem’s recent report to me, it now appears likely that UFO surveillance at America’s nuclear weapons sites began at least several months prior to the successful test of the first atomic bomb, in the New Mexico desert, on July 16, 1945. Moreover, if Rolan Powell’s estimate of the date of his encounter at Hanford is reasonably accurate, the event he describes would have occurred around the time of the test. (That said, Bud Clem’s initial estimate of his squadron’s presence at the Pasco NAS was off by some two months, perhaps not unreasonably, given that the reported incident occurred over 60 years ago. Similarly, Powell’s estimate of the time-frame for his own experience may be somewhat inaccurate as well.)

References
1. Bud Clem to Robert Hastings, personal communication, April 2, 2009

2. http://www.nicap.org/ncp/ncp-hanford45.htm

Saturday, June 18, 2011

FUKUSHIMA NEWS | Scientific Experts Believe Japan's Nuclear Disaster To Be Far Worse Than Governments Are Revealing To The Public.

Fukushima
Bookmark and Share

By Aljazeera
5-16-11

     "Fukushima is the biggest industrial catastrophe in the history of mankind," Arnold Gundersen, a former nuclear industry senior vice president, told Al Jazeera.

Japan's 9.0 earthquake on March 11 caused a massive tsunami that crippled the cooling systems at the Tokyo Electric Power Company's (TEPCO) nuclear plant in Fukushima, Japan. It also led to hydrogen explosions and reactor meltdowns that forced evacuations of those living within a 20km radius of the plant.

Gundersen, a licensed reactor operator with 39 years of nuclear power engineering experience, managing and coordinating projects at 70 nuclear power plants around the US, says the Fukushima nuclear plant likely has more exposed reactor cores than commonly believed. . . .

. . . TEPCO has been spraying water on several of the reactors and fuel cores, but this has led to even greater problems, such as radiation being emitted into the air in steam and evaporated sea water - as well as generating hundreds of thousands of tons of highly radioactive sea water that has to be disposed of.

"The problem is how to keep it cool," says Gundersen. "They are pouring in water and the question is what are they going to do with the waste that comes out of that system, because it is going to contain plutonium and uranium. Where do you put the water?" . . .

. . . Why have alarms not been sounded about radiation exposure in the US? . . .

Saturday, April 02, 2011

RADIATION FALLOUT NEWS | BERKELEY CA - Radiation Has Been Detected in Milk and Rainwater

Radiation Rain



By John Upton
www.baycitizen.org
4-1-11

     Radiation from Japan rained on Berkeley during recent storms at levels that exceeded drinking water standards by 181 times and has been detected in multiple milk samples, but the U.S. government has still not published any official data on nuclear fallout here from the Fukushima disaster.

Dangers from radiation that is wafting over the United States from the Fukushima power plant disaster and falling with rain have been downplayed by government officials and others, who say its impacts are so fleeting and minor as to be negligible.

Thursday, March 31, 2011

BREAKING NEWS | Radiation Network: "Questions Continue To Pour In About The Relatively High Readings In Colorado"

Radiation Network Map



By The Radiation Network
3-31-11

     Update: 3/31/11, 4:50 AM: Questions continue to pour in about the relatively high readings in Colorado. Up to this point, we have noted that some of the Monitoring Stations in Colorado are at high altitude where the lesser atmospheric shielding of cosmic radiation leads to a higher background count. But something else happened on the evening of March 29th which caused an elevated reading at a station in Evergreen, Colorado.

Monday, March 28, 2011

BREAKING NEWS | Radiation Alert in Huntsville, Alabama Most Likely a False Alarm

Radiation Map



By www.radiationnetwork.com
3-28-11

     Update: 3/28/11, 8:40 A.M. Here is follow up on the Radiation Alert from this morning. The Monitoring Station in question is located in Huntsville, Alabama. It triggered alerts based on radiation levels averaging in the 100 to 150 CPM range. We tried to reach the station through a number of different means, including via the Chat forum available from within the Radiation Network, but to no avail. So after a half hour or so, we contacted the Huntsville Fire Department and recommended they take independent radiation readings in the vicinity of the Monitoring Station.