Showing posts with label Minot AFB. Show all posts
Showing posts with label Minot AFB. Show all posts

Saturday, November 30, 2024

UFO Lands Near Minuteman Missile Base – Strike Team Deployed! (1966)

UFO Lands Near Minuteman Missile Base – F-106 Interceptor Scrambled - www.theufochronicles.com

Shaw, Chester A. Jr., Major, USAF, Base Director of Operations.

Comments: Capt Smith (Missile Combat Crew Commander) on duty at Missile Site (MIKE FLT) sixty (60) feet underground indicated that radio transmission was being interrupted by static, this static was accompanied by the UFO coming close to Missile Site (MIKE FLT). When UFO climbed, static stopped.


     The UFO appeared to be S.E. of MIKE 6, range undetermined. At 0512z, UFO climbed for altitude after hovering for 15 minutes. South Radar base gave altitude as 100,000 feet, N.W. of Minot AFB, NDak. At this time a strike team reported UFO descending, checked with Radar Site they also verified this.
By Major Chester Shaw
USAF
8-30-1966

The UFO then began to swoop and dive. It then appeared to land 10 to 15 miles South of MIKE 6. "MIKE 6" Missile Site Control sent a strike team to check. When the team was about 10 miles from the landing sight [sic], static disrupted radio contact with them. Five (5) to eight (8) minutes later, the glow diminished and the UFO took off.

Another UFO was visually sighted and confirmed by radar. The one that was first sighted passed beneath the second. Radar also confirmed this. The first, made for altitude toward the North and the second seemed to disappear with a glow of red. A3C SEDOVIC at South Radar base confirmed this also.

At 0619Z, two and one half (2 1/2) hours after first sighting, an F-106 interceptor was sent up. No contact or sighting was established. The Control Tower asked Aircraft Commander of a KC-135 which was flying in the local area to check the area. He reported nothing. The Radar Site picked up an echo on radar which on checking was the KC-135. No other sightings. At 0645z discontinued search for UFO.

Tuesday, April 30, 2024

Alarming Correlation: Unexplained UFO Sightings Near Nuclear Weapons Sites, Facilities

Alarming Correlation: UFO Sightings and Nuclear Weapons, Technology - www.theufochronicles.com



     An article at The Hill explores "interactions between UFOs and ultra-sensitive U.S. nuclear assets [that] date back nearly eight decades." The author, Marik von Rennenkampff, highlights several instances throughout history, here is a sampling below:
By The UFO Chronicles
4-27-24

• The Green Fireballs Phenomenon: Beginning in 1948 airline pilots began reporting sightings of "green fireballs." The subject of aerial phenomenon was classified secret, and the 4th Army approached Dr. Lincoln LaPaz, an American astronomer from the University of New Mexico and a pioneer in the study of meteors for assistance. In a secret meeting at Los Alamos in February of 1949, LaPaz stated for the record that, "Nothing like this to my knowledge, has ever been observed in the case of meteorite drops."

• UFO Incident at Kirtland Air Force Base 1957: "On Nov. 4, 1957, two control tower operators with more than 20 years of combined experience said they watched from a remarkably close range as an elongated wingless and engineless object descended slowly over the runway and hovered over the base’s nuclear weapons storage area."

• The Socorro Incident - 1964: On April 24, 1964 in Socorro, New Mexico, local police officer, Lonnie Zamora reported seeing "an egg-shaped flying object land" and he "saw two occupants who alighted after it landed ...." This incident was investigated by local authorities, the FBI, the Air Force and civilian UFO groups. To date the case remains unresolved.

As noted by Rennenkampff: "this extraordinary encounter took place in the vicinity of the Trinity Site, where the first nuclear weapon was detonated in July 1945."

• UFOs Over Nuke Missile Fields 1966/1967: "On August 25, 1966, an Air Force officer in charge of a missile crew in North Dakota [Minot AFB Missile Field] suddenly found that his radio transmission was being interrupted by static. At the time, he was sheltered in a concrete capsule 60 feet below the ground. While he was trying to clear up the problem, other Air Force personnel on the surface reported seeing a UFO- an unidentified flying object - high in the sky. It had a bright red light, and it appeared to be alternately climbing and descending. Simultaneously, a radar crew on the ground picked up the UFO at 100,000 feet.

When the UFO climbed, the static stopped," stated the report made by the base's director of operations. "The UFO began to swoop and dive. It then appeared to land ten to fifteen miles south of the area. Missile-site control sent a strike team [well-armed Air Force guards] to check. When the team was about ten miles from the landing site, static disrupted radio contact with them. Five to eight minutes later the glow diminished, and the UFO took off. Another UFO was visually sighted and confirmed by radar. The one that was first sighted passed beneath the second. Radar also confirmed this. The first made for altitude toward the north, and the second seemed to disappear with the glow of red. This incident, which was not picked up by the press, is typical of the puzzling cases ..."–J. Allen Hynek

"In March 1967, all ten of the 'Minuteman I' missiles [Malmstrom AFB] under my control were disabled while an oval shaped UFO hovered at close range over the front gate of my launch control center in Montana. I was sworn to secrecy about this incident until 1994 when the U.S. Air Force declassified a similar incident at the request of my investigator, Jim Klotz under the Freedom of Information Act (FOIA). At that time, I believed the declassified incident of ‘Echo Flight’ to be the one in which I was involved. As a result of receiving declassified documents from AF records about the Echo incident, I began to publicly disclose what I recalled."–Robert Salas

• The Rendlesham/Bentwaters UFO - 1980: "Early in the morning of 27 Dec 80 (approximately 0300l), two USAF security police patrolmen saw unusual lights outside the back gate at RAF Woodbridge. Thinking an aircraft might have crashed or been forced down, they called for permission to go outside the gate to investigate. The on duty flight chief responded and allowed three patrolmen to proceed on foot. The individuals reported seeing a strange glowing object in the forest. The object was described as being metallic in appearance and triangular in shape, approximately two to three meters across the base and approximately two meters high. It illuminated the entire forest with a white light. The object itself had a pulsing red light on top and a bank(s) of blue lights underneath, it maneuvered through the trees and disappeared. At this time the animals on a nearby farm went into a frenzy. The object was briefly sighted approximately an hour later near the back gate."–Charles Halt

Wednesday, March 31, 2021

UFO Lands Near Missile Base; Affects Radio Transmissions - Strike Team Dispatched!

Saucer Drawing Carpio Grano Missle Field (Minot) 8-24-1966


     Capt. Smith (Missile Combat Crew Commander) on duty at Missile Site (MIKE Flt) sixty (60) feet underground indicated that radio transmission was being interrupted by static, this static was accompanied by the UFO coming close to the Missile Site
By Air Force
HQ Minot AFB
8-30-1966
(MIKE Flt). When UFO climbed, static stopped. The UFO appeared to be S.E. of MIKE 6, range undetermined. At 0512Z, UFO climbed for altitude after hovering for 15 minutes. South radar base gave altitude at 100,000 feet, N.W. of Minot AFB, NDak. At this time a Strike Team reported UFO descending, checked with Radar Site, they also verified this. The UFO then began to swoop and dive. It then appeared to land 10 to 15 miles South of MIKE 6. "MIKE 6" Missile Site Control sent a Strike Team to check. When the team was about 10 miles from the landing site, static disrupted radio contact with them. Five (5) to eight (8) minutes later, the glow diminished and the UFO took off. Another UFO was visually sighted and confirmed by radar. The one that was first sighted passed beneath the second. Radar also confirmed this. The first, made for altitude towards the North and the second seemed to disappear with the glow of red. A3C SEDOVIC at the South Radar base confirmed this also. At 0619Z, two and one half (2 1/2) hours after the first sighting, and F-106 interceptor was sent up. No contact or sighting was established. The Control Tower asked the Aircraft Commander of the KC-135 which was flying in the local area to check the area. He reported nothing. The Radar Site picked up an echo on radar which on checking was the KC-135. No other sightings. At 0645Z discontinued search for UFO.

Tuesday, October 17, 2017

New Witness To UFO Incursion at Nuke Missile Complex, Tom Delonge's New Gig and The Media

Bookmark and Share

UFO Sighted By B-52

Still looks like rain

     Sports writer Mic Huber and I worked together for 10 years at the Herald-Tribune here in Sarasota. Different shifts, different departments, which meant we didn’t see each other all that much. Small talk, mostly, much of it focused on the whereabouts of an elusive relentlessly self-deprecating mutual friend. We got a lot of mileage out of you, David, so thanks for that, wherever you are.

At his voluntary-buyout farewell office party early this year, Mic retraced the steps that led him to his long run in Sarasota. What made him appreciate Florida was his Air Force hitch in North Dakota.

By Billy Cox
De Void
10-13-17
The winters were so grim he applied for a transfer to Vietnam during the height of the war. Uncle Sam sent him to Germany instead.

Anyhow, during his sayonara to the newsroom, Mic mentioned something about how he’d been on duty when he got sucked into a UFO incident, an experience that impressed him so deeply he saw fit to bring it up during impromptu remarks to colleagues nearly half a century later. But it was a small fleeting recollection and he didn’t linger there.

Mic still freelances, and a few months later I pulled him aside one afternoon and asked for more details. I couldn’t help but smile as he rattled off words like Minot Air Force Base, 1968, B-52, radar, radio interference, security breach, etc., etc. Mic isn’t a UFO geek, he doesn’t follow this stuff, so he was unaware of just how significant this incident was, in terms of evidence. At the end of his recollection, Mic repeated another phrase that actually made me laugh out loud because I’d heard it so many times before. He said he’d been debriefed by an Air Force colonel, his testimony had been tape-recorded, and that the officer left him on this note: “This didn’t happen.”

In fact, I’d just ordered a book called It Never Happened,written by a USAF veteran who’d been stationed at the same outpost, Minot, just two years earlier, 1966. Same general idea, though – unauthorized UFO activity over a Strategic Air Command base armed with nuclear missiles. No trifling matter. I suggested Mic take a peek at the www.minotb52ufo.com website, an impressively detailed reconstruction of that sliver of history he’d been a party to in the wee hours of Oct. 24, 1968. Researcher Tom Tulien had constructed an underappreciated narrative packed with veteran eyewitness testimony, the Strategic Air Command’s own documents, and assessments from technical analysts. I thought maybe he could test his memory against the record.

Mic dropped in a few weeks later. He’d been to the site, and he was jazzed. The details – everything he remembered about what happened lined up. Everything. He was in air operations that night, he’d heard it all.

Mic’s job was to know the flight plans of everything in the immediate sky to make sure nobody bumped into each other; sometimes, civilian neighbors near the base made inquiries about other things they’d seen. “We did get some UFO reports, probably a lotta farmers who were drunk,” he conceded. “But this was completely different. It lasted such a long time, and I guess that’s what made it stick with me.”

Shortly after 2 a.m., maintenance and security teams outside the remotely spaced launch control facilities – each of which housed Minuteman nukes – began noticing at least one, maybe more, large bright glowing object in the sky. It or they changed colors, white to amber to green. It or they went high, dipped behind treelines, reversed course on a dime. Air traffic control alerted a B-52 returning from a training mission to a bright glowing bogey off its 1 o’clock position as it executed a 180-degree turn for its final approach. The UFO wheeled with it and maintained its distance, at a rigid three miles. But as the bomber completed the turn, within a three-second sweep of the radar, the object pounced to within a mile. For the next 10 seconds, the plane’s two radios fuzzed out, even as an onboard camera took sequential photos of the radarscope recording the UFO when it changed positions.

Moments later, ATC diverted the plane to get a visual on a UFO reported on or near the ground. One pilot spotted it immediately, some 10 miles away and below, comparing it to “a miniature sun.” As they banked above it, another crew member described it as metallic, smooth, egg-shaped, a “dull reddish color like molten steel.” Once again, the ground briefly lost radio contact with the B-52, which landed at 4:40 a.m. But additional sightings trickled in for nearly an hour afterwards.

“I was on the phone with the guy who called it in from the missile site,” Mic recalled. He was monitoring comm chatter when the radios blinked out, and he remembers how the object looked on radar. “The return was more intense than a C-135 during refueling.” He saw the B-52 team when they returned – “they were visibly shaken” – and got a look at their subsequent illustrations of the object(s). After Mic’s shift ended, he was interrogated about what he’d heard and seen, this Thing That Never Happened. Obliged to say something, anything, official investigators concluded that Minot AFB personnel — these defenders of the world’s most destructive weapons — had simply been confused by Vega, Sirius, ball-lighting plasmas, a combination of all three, whatever.

Incidentally, It Never Happened involved an even spookier case. In 1966, writes (Ret.) Capt. David Schindele, launch operators lost control of as many as 10 nuclear-packed missiles when their power blinked off during apparent UFO surveillance. Which means Mic Huber has a lot of company. UFOS and Nukes author Robert Hastings has gotten more than 150 veterans to go on record about a phenomenon’s apparent fascination with our nuclear armaments. No telling how many more eyewitnesses who were told to shut up are out there.

But even if each and every one of these guys stepped up tomorrow to share what they knew, it wouldn’t make any difference. Events over the last year have only reinforced how deeply into denial and aggressive ignorance our culture has descended. In spite of that, amid turdstorms of truly fake news, some of the most diligent investigative political journalism I’ve ever read is unfolding right now, daily. Downright heroic, in some cases. And yet, American journalism is no match for The Great Taboo. Because most of the people who dare to own it tend to lack, umm, conventional pedigrees.

Tom Delonge
Wednesday, for instance, classic example: Former Blink-182 frontman Tom DeLonge sparked what will be, if traditional patterns hold, a quick-hit flurry of sensational headlines. The details are posted at To The Stars Academy of Arts & Science and — once again — are straight out of left field. DeLonge is the California punk-pop rocker whose self-parodying music videos — dancing around in brief undies, licking coin-operated viewfinders, bored on the commode, babes weeping with desire — were so convincing during the Blink days you just wanted to punch the smirk off his face.

And yet, as early as 2015, DeLonge was telling “Us” magazine he was in contact with heavy-hitting government types he hoped to coax out of the shadows to address the UFO conundrum head-on. It was easy enough to blow him off until, late in the 2016 campaign, WikiLeaks (or somebody) hacked the emails of Hillary Clinton’s campaign director John Podesta, which showed DeLonge was indeed in the loop with a couple of two-star USAF generals and an advanced projects director for Lockheed Martin. And even then, who knew, maybe they were just big fans of “Enema of the State” and “Take Off Your Pants and Jacket.”

Then came Wednesday. Lo and behold, there was DeLonge, introducing business partners in a half-hour video presentation designed to drum up crowd-sourcing to support something called To The Stars Academy. Its stated purpose was, with the UFO mystery at its core, to provide “gifted researchers the freedom to explore exotic science and technologies with the infrastructure and resources to rapidly transition them to products that can change the world.” And whoa, get a load of their cred:
Deputy Assistant Secretary of Defense for Intelligence; Senior Intelligence Service, CIA Directorate of Operations; Lockheed Martin “Skunk Works” Advanced Systems Director; director of scientific research programs for the Defense Department, the CIA and the DIA; a counterintelligence agent who ran an “aerospace threat identification program” out of the Pentagon. The jewel of this narrative was relayed by Chris Mellon, the former SecDef assistant. He discussed an hours-long incident in 2004 involving the aircraft carrier USS Nimitz, F-18 jet fighters, a UFO that seemed “to defy the laws of physics,” and footage of the whole thing. Captured by gun cameras. Plus infrared images. Property of the U.S. government.
Holy cow. This could be huge. Just like Hillary Clinton’s UFO remarks last year on the campaign trail could’ve been huge. Just like the half-dozen USAF veterans who testified in 2010 at the National Press Club to UFO activity over American nuclear bases could’ve been huge. Just like the MUFON 2008 radar analysis of UFO and jet fighter activity that caught the Air Force in a lie could’ve been huge. Just like CIA image-doctor Chase Brandon’s revelations about finding Roswell ET documents in the Agency’s archives could’ve been huge.

But this stuff can only be huge if the press is interested enough to dig, to background these guys, to pursue every lead and put it out there. What we’ll probably get instead is a convulsion of wry headlines, some “the truth is out there/out of this world” segues, maybe even some cursory reporting, but it’ll all wander off soon enough. Whatever followups occur will be tepid and of little consequence, or at least without the persistence essential to stoking public interest. And without public interest, this ship doesn’t sail. Or at least not very far.

And that’s one of the reasons De Void has been dormant for so long. Ultimately, this space started sounding futile and whiney. The only reason for this posting is to send one more shoutout to all the Mic Hubers, to all you folks who saw and may still be seeing crazy airborne stuff snooping around the most dangerous weapons in the history of warfare. This is news. Just because the media doesn’t think so, that doesn’t mean you’re crazy.

Unfortunately, yes, you do live in a superpower nation that has degenerated into an absolutely certifiable full-tilt nuthouse. But it’s not your fault.

Friday, November 01, 2013

’68 UFO Run-In at ND Air Force Base Still Unresolved

Bookmark and Share

UFO As Seen From B-52 Over Minot Nuke Missle Fields

Nuke Missile Launch facility Personnel Witness UFOs at Minot AFB Missile Field 10-24-1968
- click on image(s) to enlarge -

By Dave Olson
www.inforum.com
10-31-13

     A routine bomber flight in the pre-dawn hours of Oct. 24, 1968, turned unforgettable for navigator Patrick McCaslin.

McCaslin and his B-52 crewmates were practicing maneuvers in the skies above Minot, N.D., when officials at the nearby Air Force base radioed a request.

“The tower called and said, ‘Could you guys keep your eyes open for anything unusual?’ ’’ said McCaslin, recalling that flight four decades ago.

“We asked, ‘What are we looking for?’

“They said, ‘You’ll know it if you see it,’ ’’ McCaslin said.

“This is a dim memory,” he added, “but I think one of the pilots said, ‘Are the missile crews seeing things again?’ ’’

McCaslin’s first move was to focus the plane’s radar into a narrow, high-intensity beam.

“I saw a (radar) return off to our right; it was faint on the first sweep and then it was very strong on the next sweep,” he said.

When McCaslin informed the pilots about the contact, they replied they couldn’t see anything because of cloud cover, but asked him to keep them apprised of what the object did.

What it did, McCaslin said, was move faster than anything he had ever clocked on radar.

“From one sweep (of the radar) to the next, it came from three miles to one mile,” he said. “Later, we computed the closure speed at 3,000 miles an hour.”

From there, it only got stranger. . . .

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, May 08, 2013

Air Force Sidelines 17 ICBM Officers After Unpublicized Failings

Bookmark and Share

Titan II Launched

By ROBERT BURNS
The Huffington Post
5-8-13

      WASHINGTON — The Air Force stripped an unprecedented 17 officers of their authority to control – and, if necessary, launch – nuclear missiles after a string of unpublicized failings, including a remarkably dim review of their unit's launch skills. The group's deputy commander said it is suffering "rot" within its ranks.

"We are, in fact, in a crisis right now," the commander, Lt. Col. Jay Folds, wrote in an internal email obtained by The Associated Press and confirmed by the Air Force.

Asked about this at a Senate hearing Wednesday, Air Force Secretary Michael Donley, the service's top official, explained the problem by stressing that launch control officers are relatively junior in rank – lieutenants and captains – and need to be reminded continually of the importance of "this awesome responsibility" for which they have been trained.

Donley said commanders must "ride herd" on the launch crews, and he said the Minot revelation shows that the Air Force has strengthened its inspection system. He said he is confident that the nuclear missile force is secure.

Sen. Richard Durbin, chairman of the Senate Appropriations defense subcommittee, expressed outrage, saying the AP report revealed a problem that "could not be more troubling." . . .