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.
The dark side of space disaster theories
www.thespacereview.com...
by James Oberg
The Space Review
Monday, January 21, 2008
When he was an active 'rocket scientist', Oberg had a 22-year career as a space engineer in Houston, where he specialized in NASA space shuttle operations for orbital rendezvous, as a contractor employee.
Newsgroups: alt.alien.visitors
Subject: OTHER gov't UFO secrets
From: [email protected]
Date: 26 Apr 1997 14:15:43 GMT
Open letter to CSETI:
I applaud CSETI's efforts to strip away the "government secrets prosecution" barrier to the disclosure of people's stories about UFO experiences and I fully support the call for a government declaration that all legal constraints against disclosure be dissolved. I've always felt that claims of fear of such prosecution as an excuse by people not to "go public" was often merely a gimmick not to have to take responsibility for the authenticity of such stories, since as far as I've been able to tell -- and through OMNI's "Project Open Book" we searched far and wide for examples -- nobody has ever been arrested or charged -- much less convicted and sentenced -- for actually doing so.
But don't stop merely with legalizing disclosure of all -- if any -- government secrets about "real UFOs". I believe there is a far more valuable body of "secrets" that will help understand the decades of UFO phenomena that the world has experienced. This deals with government-related activities which directly or indirectly led to public perceptions that UFOs might be real when they weren't. Sometimes these actions were carefully orchestrated in advance, sometimes they were localized impromptu ad hoc damage- limitation tactics. But from my own experience, they seem to have played a tremendous and widely unappreciated role in inciting and enflaming public interests in UFOs while deflecting public attention from real highly-classified government activities.
I'm referring to situations where government representatives -- officials, military officers, any employees -- used "UFO" as a convenient camouflage for other official classified activities (such as retrieval of crashed aircraft or nuclear weapons or other objects), or used artificial "UFO stories" (in oral, written, photographic, film, etc.) form as "tracers" in studying the function of security safeguards and personnel psychological responses, or used "UFO" as an excuse (either intended or accidental) to cover-up improper, forbidden, or diplomatically delicate activities (such as aviation incidents involving dangerous accidental or deliberate close passes or intercepts of civilian airliners, or overseas excursions of agents on intelligence missions where deflection of local perceptions was useful, or to conceal from the country of origin the possession of foreign military hardware), or played pranks and jokes on intended or accidental targets, or any other activity that the government -- or any part of it -- wanted to keep hidden, knowing that having it thought of as "UFO-related" would consign it to the never-never- land of myth and nuttiness, thus keeping mainstream media attention to a minimum. And it's worked!!
Please include such "UFO secrets" in your list of disclosure demands, and ask that any government personnel involved in the use (or misuse and abuse) of such practices be immune from any government prosecution for the actions which led them to take such measures. Once such immunity is verifiably granted, I have my own list of people who have privately talked to me over the years and who were involved in government activities leading to a number of well-known "UFO cases", which can be released and which can help understand where and how much of today's UFO mythology originated.
This is a serious proposal deserving of serious consideration, and promises immensely fruitful results.
Originally posted by johnlear
Now with all due respect Jim when you say you were a 'rocket scientist' this implies that you designed rockets. Did you design rockets for NASA? And if so, which rockets did you design?
Actually, my first Mission Control certification was at the OMS/RCS console, call sign 'PROP' (for propulsion). Those are the 44 rocket thrusters that steer the Orbiter and the two bigger ones that change its orbit as needed. I flew STS-1 and STS-2 at this position (in 1981), then was promoted to lead the group designing 'formation flying' procedures.
But -- by golly! -- those were real rocket engines!!
1979-1981: McDonnell Douglas Technical Services Corporation employee in NASA-JSC Mission Control Center, supporting the Space Shuttle's on-board propulsion systems (OMS/RCS, or Orbital Maneuvering System and Reaction Control System). Supported STS-1 launch on console in MCC as the "Prop Consumables" officer; supported STS-2 as "Prop Consumables" planning lead.
Military Service:
Distinguished Military Graduate, AFROTC, 1966;
Air Force Weapons Laboratory, Kirtland AFB, 1970-2;
DoD Computer Institute, Washington, DC, 1972-5, instructor;
NASA Johnson Space Center, Houston, 1975-8, on loan to NASA.
1975-7: USAF Captain, detailed to NASA-JSC Software Division, Houston, wrote requirements documents for shuttle's flight software & Spacelab computers.
Originally posted by JimO
John, this is all a silly diversion.
Originally posted by ArMaP
I agree, but it shows how easy it is to make a silly diversion when we do not stick to the subject.
Originally posted by zorgon
Why? are not your credentials in this issue as open to scrutiny as Ken Johnston's?
I mean with all the claims made on both sides I for one am interested in who is telling the truth and who is 'ego inflating'
Originally posted by john lear
That blows me out of the saddle. I read that part in your resume and I thought you were the gas boy, or refueler or something like that.
Since I 'wrote the books' on crew procedures for rendezvous and proximity operations, as well as a number of mission specific annexes for particularly unique shuttle flights, I spent a lot of time there -- and don't recall ever running into any tourists.
1990-1994: Located, collected, selected & annotated documents for "History of Orbital Rendezvous" reference book and training manual, 400 pages.
1986-1991: Mission Operations Division, Orbital Rendezvous Procedures team. Wrote flight crew procedures handbook (400 pages), identified by MCC Director as "a model for others to follow". Wrote MCC console handbook (300 pages) for entire rendezvous guidance and procedures MCC team.
1990-1994: Located, collected, selected & annotated documents for "History of Orbital Rendezvous" reference book and training manual, 400 pages.
1986-1991: Mission Operations Division, Orbital Rendezvous Procedures team. Wrote flight crew procedures handbook (400 pages), identified by MCC Director as "a model for others to follow". Wrote MCC console handbook (300 pages) for entire rendezvous guidance and procedures MCC team.