It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: Eilasvaleleyn
a reply to: ZetaRediculian
Some people are "insane cynics." Either that or on someone's payroll. Be too cynical and new ideas will find it outrageously hard to penetrate your thick skull, be too open-minded and your brain will drip from your ears.
Then I shall not label them under broad terms. I shall simply call them as what they are, "Factually wrong."
Or will it finally be the death of Ufology?
Air Force B-52 encounter with a UFO
minotb52ufo.com...
originally posted by: Eilasvaleleyn
Oh, Blue Book was a scam. An absolute scam. Its purpose wasn't to find and reveal the truth behind UFO cases (though it did manage to do that for a few), its purpose was to obfuscate things as much as possible.
originally posted by: Eilasvaleleyn
Oh, Blue Book was a scam. An absolute scam. Its purpose wasn't to find and reveal the truth behind UFO cases (though it did manage to do that for a few), its purpose was to obfuscate things as much as possible.
originally posted by: Eilasvaleleyn
No, I mean, they intentionally shunted cases into sections where they didn't belong to cut down on the number of "unexplained" cases. Events with highly unsatisfactory explanations and so forth.
If you believe what a few of the people who worked on Blue Book have said, the most interesting things went to a higher level anyway.
Also, wasn't there are a department for UFO stuff before the cold war? Like, the 1930s.
originally posted by: Eilasvaleleyn
a reply to: skyeagle409
Russian spy plane.
originally posted by: Eilasvaleleyn
a reply to: ZetaRediculian
No, I'm sure the Russians would have been in mind. How was the Cold War going on around 1947 when Sign was started up? Did it even exist at that point?
Historians do not fully agree on the dates, but 1947–91 is common
DEPARTMENT OF THE AIR FORCE
HEADQUARTERS 341ST COMBAT SUPPORT GROUP (SAC)
MALMSTROM AIR FORCE BASE, MT 590402
REPLY TO
ATTN OF: BO 3 July 1967
SUBJECT: UFO Observations, Malmstrom AFB Area
to: Colonel James C. Manatt (lettered TDET/UFO)
HQ Foreign Technology Division (AFSC)
Wright-Patterson AFB, Ohio 45433
1. Reference TDET/UFO letter dated 30 June 1967 on above subject.
2. This office has no knowledge of equipment malfunctions and abnormalities in equipment during the period of reported UFO sightings. No validity can be established to the statement that a classified government experiment was in progress or that military and civilian personnel were requested not to discuss what they had seen.
3. A written report on the events that transpired during the alleged UFO reported landing on 24 March 1967, fully documents all findings by the investigating officer. A copy of this report was forwarded to your office on 3 April 1967.
4. If we can be of further assistance to you, please do not hesitate to write.
FOR THE COMMANDER
LEWIS D. CHASE, Lt Colonel, USAF
Chief, Operations Division
Robert Kaminski
The late Robert J. Kaminski, who headed the Boeing Company missile engineering team that investigated the case, says he was told by a Boeing–Air Force liaison that UFOs had indeed been sighted in the vicinity of the flight's launch silos at the time of the missile malfunctions. Kaminski unequivocally states that his team could find no prosaic cause for the failures.
www.cufon.org...
EXCERPTS FROM KAMINSKI’S LETTER TO JAMES KLOTZ
“Hi James,
I received your package of information on Tuesday January 28, 1997. After reviewing the information it sure revived memories concerning the Malmstrom AFB E-Flight investigation of which I was the Boeing in-house project engineer for the field team investigation. Per your request I have documented my direct involvement as I recall the event and give names and other information not previously covered in my book, "Lying Wonders."
As I previously mentioned to Bob Salas and others, I never submitted a final report from Boeing to the Air Force. A final report was generated but not submitted. This will become clear as you will see in my recollection noted below...
At the time of the incident, I was an engineer in the MIP/CNP (Material Improvement Project/Controlled Numbered Problem) group. This was a Logistics Engineering group. The group was contracted by the Air Force so that Boeing could respond to specific Air Force Minuteman Missiles problems that occurred in the field. The assignments came from the OOAMA Air Material Command. Our group was made up of a small unit of engineers that were knowledgeable of, and had worked on the Minuteman Missile program...
We were usually notified by our OOAMA Boeing contact (located at Hill AFB) when a request was coming in from the Air Force. Don Peterson, was our Boeing OOAMA contact...
...At the outset the team quickly noticed a lack of anything that would come close to explain why the event occurred. There were no significant failures, engineering data or findings that would explain how ten missiles were knocked off alert. This indeed turned out to be a rare event and not encountered before. The use of backup power systems and other technical system circuit operational redundancy strongly suggests that this kind of event is virtually impossible once the system was up and running and on line with other LCF's and LF's interconnectivity.
The only thing that even came close to a failure was that a transformer on a commercial power pole down the road from one of the sites was in the process of failing. It exhibited a intermittent transient type of failure that could have generated noise spikes on the power line. This in itself could not have caused the problem at E-Flight. The problem was reported to the local power company who took action to replace the transformer.
The team met with me to report their findings and it was decided that the final report would have nothing significant in it to explain what happened at E-Flight. In other words there was no technical explanation that could explain the event. The team went off to do the report. Meanwhile I was contacted by our representative at OOAMA (Don Peterson) and told by him that the incident was reported as being a UFO event--That a UFO was seen by some Airmen over the LCF at the time E-Flight went down.
Subsequently, we were notified a few days later that a stop work order was on the way from OOAMA to stop any further effort on this project. We stopped. We were also told that we were not to submit the final engineering report. This was most unusual since all of our work required review by the customer and the submittal of a final Engineering report to OOAMA.
Days later, I asked our Boeing OOAMA rep what was going on. His reply to me--off the record---was that the LCF capsule jockeys were suspected of causing the problem somehow by something they did to one of the digital racks in the LCF. The Air Force capsule officers apparently were quietly removed from their job as LCF officers. This part of the story can not be verified by me, as it was hearsay...
Sincerely Yours,
[Robert Kaminski]
Interview with Colonel Walter Figel, Oct. 20, 2008
Figel confirms that he had received a report from a security guard about a "large, round" UFO hovering over one of Echo Flight's missile silos, seconds after that missile failed.
www.theufochronicles.com...
Former Minuteman Electro-Mechanical Technician, Henry Barlow
Barlow further said that he and other members of the 341st Missile Maintenance Squadron had observed UFOs on several occasions, both prior to and following the Echo incident, while working in Malmstrom's missile field during 1966–67.
www.theufochronicles.com...