Did KSC Ban All Employee Photography? Update
|
|
Keith’s 12:32 PM note: I sent the following request to NASA HQ and KSC PAO:
“K. Scott Piel @spiel2001 who claims to be a “Software Engineer / TOSC @ NASA/KSC EGS/LCS – Amateur Photographer” refers to a new KSC policy that prohibits employees from any photography while on the job.
1. Has NASA KSC implemented a new policy wherein, according to Piel “employees are no longer permitted to photograph or share images from *any* operations cat KSC without authorization. Regardless of source. Photographing, or sharing images, from operations is grounds for termination.” (yes/no)?
2. If NASA KSC has implemented a new policy with regard to photography does it apply to contractor personnel only, NASA civil servants only, or both?
3. Can you provide me with a copy of the current NASA KSC policy with regard to photography – on-site – by KSC employees?”
Keith’s 1:14 PM update: NASA replied (very quickly BTW): “NASA does not have a new photo policy. All employees are required to follow federal and contractual requirements, which prevent the sharing of imagery that is export controlled and/or proprietary. I will circle back to you with the policy shortly.”
Keith’s 1:30 PM update: “As promised, I am including the language below from the Kennedy NASA Procedural Requirement that outlines KSC’s photography policy.”
“10.4 KSC Photography Policy
More below
10.4.1 Photography, including videography, is prohibited inside KSC Limited Areas and Exclusion Areas, and within NASA Critical Infrastructure Facilities, unless the photography meets at least one of the following exceptions:
a. The photographs are taken for official business. Photographs of SBU material/items will be encrypted prior to transmission and export control shall review and classify all such photographs prior to their release.
b. The photographs are taken by a member of the media operating under a properly badged escort in areas or at events that the CCS has approved.
c. The photographs are taken during an official tour conducted by a KSC Communication and Public Engagement escort with the prior approval of the CCS.
Note: KSC Limited Areas, Exclusion Areas, and NASA Critical Infrastructure Facilities include areas and facilities such as the Vehicle Assembly Building, Launch Control Center, Pad B, Multi-Payload Processing Facility, Launch Equipment Test Facility, Rotation Processing Surge Facility, Launch Abort System Facility, Payload Hazardous Servicing Facility, Space Station Processing Facility High Bay, Converter/Compressor Building, Kennedy Complex Control Center, Mobile Launcher, Kennedy Data Center, and Crawler Transporter.
10.4.2 Cell Phones and other devices with photography capability (personal or Government owned) are allowed in KSC Limited Areas, in Exclusion Areas, and within NASA Critical Infrastructure facilities, except as prohibited by other Center requirements (e.g. explosive, radio frequency, etc.) However, photography with such devices (including the use of photograph-sharing applications such as Snapchat or Instagram) is prohibited inside the area unless it meets at least one of the above exceptions.
10.4.3 Within other facilities on KSC and outdoor areas, photography of the following is prohibited:
a. KSC or CCAFS entry badges.
b. All Security Police activities and staffed entry control points without prior approval from the CCS.
c. Sensitive Compartmented Information Facilities.
d. Other areas as identified due to sensitive research, Sensitive But Unclassified information, or Export Control sensitivity (i.e., ITAR articles and services).
10.4.4 The following areas are under the control of external or third parties that have the authority to prohibit photography of their assets without their express written consent:
a. Commercial/private company operations (i.e., space vehicles, equipment, launch pads) without express written consent from the company.
b. All external and internal areas of CCAFS, with the exception of areas controlled by NASA, without the express written consent from the 45th Space Wing Commander or designee.
10.4.5 To report suspicious incidents or suspected prohibited photography, contact the Protective Services Control Center at 321-867-2121. Employees who learn of an unauthorized release of photographs or lost or stolen photography device containing photographs pertaining to KSC Limited Areas, Exclusion Areas, or NASA Critical Infrastructure Facilities, must immediately report the matter to the NASA Security Operations Center at 1-877-NASA-SEC (1-877-627-2732), and the KSC Protective Services Office at 321-867-7575.
Looks like Mr. Musk got upset at the leaked video of the recent rapid, unscheduled disassembly of the crew Dragon capsule.
True, but we also have not seen video of Starliner’s test that experienced an anomaly which reportedly leaked hypergolic propellants. These craft are commercial, so the detailed information about them and how they work is proprietary and owned by the company, not NASA.
The public have paid for most of the development of crewed spacecraft by SpaceX and Boeing. The public deserves il information and quickly. What happened and why. How are NASA and SpaceX responding.
Again, why aren’t you calling for the same from Boeing? They have not been very forthcoming with details either. This article is about the best I could find on the cause of Starliner’s propellant leaks:
Leaky valves on Boeing’s new spacecraft are increasing the risk that NASA astronauts could lose access to the space station
Dave Mosher Aug. 3, 2018, 8:16 AM
https://www.businessinsider…
From anove:
If anyone has a better source of details on the Starliner leak, I’d like to see it. I can’t find much more than the above somewhat vague explanation.
Someone at NASA upset about that low quality dragon capsule anomaly video?
Probably more SpaceX. But there are also implications on the NASA side too. In general, most work (aside from that released in publicity stuff) is supposed to be fairly well controlled. What happened to SpaceX with the leak could easily happen to them. Not to mention there’s the question of who leaked the video. Was it a SpaceX employee? Was it a contractor? Was it a NASA employee? There’s all sorts of control and rules involved here.
Looks like this is a reaction to the video of the Dragon2 Anomaly that was posted on Twitter.
https://www.orlandosentinel…
After video of SpaceX explosion leaked, NASA workers told they can be fired for sharing images
And the worst video ever, low resolution and frame rate. I know phones do better than that, it will be interesting to find the real story. Reminds me of Soviet Russia only released poor quality photo and film of their early space accomplishments. But also think what if this video was not posted, and people outside KSC wonder what that big boom and orange cloud of smoke is all about.
It looked to me like someone had video of the accident on his or her phone, and someone else used his or her own phone to video the first phone, instead of transferring the video (probably so it couldn’t be traced.) That explains the poor quality video and the weird countdown audio which seems to be running twice but several seconds apart (someone else was looking at another video nearby.)
Looks like K.Scott Piel is incorrect in stating this is “from this point forward”. NASA policy looks clear and documented to me. Little opportunity to take photographs as an employee or visitor. That’s what I would expect on a Federal installation, so I’m surprised by the Tweet.
We thought the video looked “unofficial”. But what if a guest takes a video/photo ? What if POTUS posts a pic ??
That’s the thing I mentioned in my comment. KSC is a tourist spot. All the bus tours go through the LC-39 area, and drive by the pads, and certain Air Force sites. Nobody is stopping them from taking pictures as they pass by something.
so tourists are allowed to take pictures (presumably the guides only show them unrestricted displays) or the fine print says “don’t” but no-one stops them (guides don’t want to disappoint guests) ?
The guides certainly don’t check to see how much magnification a tourist’s camera’s lens provides. And there are some good and reasonably compact telephoto lenses out there. I’m fairly sure some people would be surprised by how many restricted areas are observable with a telephoto lens from unrestricted areas.
It’s really going to depend on the situation here. Certainly the SpaceX leak wasn’t something that would be allowed under most circumstances. What about when the SpaceX rocket blew up on the pad though? Certainly that could be considered “operational”. I think certainly that most employees realize they can’t take pictures of closed off areas, places with classified info, or detailed documents. I think the real thing people are questioning is about the major public-ish type items, like launches.
The real question though is how does one define Operational? When an actual rocket launches from the pad, is that prohibited? What about taking pictures of a rocket out on the pad, or a rollout, or a picture of the exterior of the VAB. Many don’t realize that while KSC is an operations facility, it’s also a tourist site. Buses are taking people to the VAB exterior, near the pads and even to some Air Force sites, and can take the same pictures that most employees can. Will they be banned too?
I don’t think that any tourists will have access to “KSC Limited Areas and Exclusion Areas, and within NASA Critical Infrastructure Facilities”.
Not arguing with you on that. but the article states that ALL photography is banned for employees. If that’s the case, in theory just taking a picture of the outside of the VAB or taking a photo during a launch could be considered against the rules.
That’s the sort of generalization you often hear from managers. If pressed, I suspect the person in question would say he obviously didn’t mean ALL photographs, it was just shorthand for all photographs which violated policy. And that individual employees can’t make decisions about what violates privacy on their own, so all photographs have to be submitted to someone for review and approval. Or some similar nonsense. That’s why I prefer management directives to be public and/or in writing.