NASA have long been fond of telling the world that they are an open civilian agency. We have all heard this claim, and most have never had reason to doubt it. They have been caught being less than candid on more than one occasion. There is even an internal NASA document detailing how to avoid telling the truth to the public. (Hiding Space: NASA's tips for Avoiding Scrutiny, by Kate Doyle) This page has been removed from the internet. Link now dead...see for yourself.

Below is yet another example of NASA's policy of continuing secrecy on many levels. This document outlines the NASA plan for concealing evidence, and preventing eyewitness testimony, concerning any possible future accident (Known in bureaucratic circles as a contingency) aboard the International Space Station.

This plan goes so far as to post armed guards at the doors to the building, and to suspend rubbish collectiion.

If this supposedly open civilian agency will go to such lengths to cover up even a SUSPECTED contingency, what would they do with a UFO incident? Read the official document below for a picture of just how secretive NASA really is. These secrecy rules were implemented during the tragic loss of Space Shuttle Columbia on 1 February, 2003. I observed the procedure, and cannot see how keeping everything pertaining to the disaster from the eyes of the public does anyone any good. As the facts were meted out little by little over the ensuing months, one had to wonder how much of it was the actual truth.

JEFF CHALLENDER

• Official Management Notification
• ISS MER Manager notifies management ( same as suspected contingency)
• ISS MER Manager declares that the ISS MER Contingency Response Procedure is in effect using the ISS MER MGR 1 voice loop and the ISS ESR COORD
• ISS Safety will notify S&MA MMT representative
• ISS MER Manager will notify ISS FD that all official telephone notifications have been made and the MER is ready for phone intercept
• Sequestering personnel in BLD 30 or ESRs
• MER Manager will call security to post guards outside the doors of the MER
• No one will be allowed to leave or enter BLD 30 upon declaration of the contingency
• All phone calls in progress will be terminated without disclosing reason for termination
• No unofficial outside phone calls will be allowed unless authorized by MER MGR
• No external computer resources will be available
• All trash pickup will be terminated
• Record and collect data
• Print all relevant displays
• Log time of contingency and any request and transmittal of data
• Document on Flight Controller’s Log significant events, data observations, etc.
• Contingency Data Collection (CDC) Envelopes
• CDCs are prepared and stored behind the MER Manager’s console
• The MER Manager will distribute the CDCs to each console
• Each console will complete the checklist the CDC and fill in the forms
• The CDCs will be returned to the MER Manager to be impounded
• Leaving the MER
• No data may leave the MER
• Sign contingency Roster
• No ISS MER or ESR personnel will make any public statements concerning the contingency.
• All inquiries shall be referred to the Public Affairs Office

CDC Content
• ISS MER and ESR Support Position Console Configuration Form
• Inventory of Contingency Data
• ISS MER Facility Checklist
• ISS ESR Facility Checklist
• ISS/MER Contingency Roster
• Impounded Data Access/Removal Authorization

This was sent to me in the form of an MS Word document. It was obtained from a NASA employee who shall remain nameless for his/her protection.

This policy was followed to the letter on 1 February 2003 when the STS-107 Flight Director realized that he had a contingency on his hands when Columbia stopped communicating. Moments later, it was confirmed that Columbia was destroyed during the later stages of re-entry...