SpaceX’s “False Alarm” Encounter with an Unknown Object: An Analysis of the Latest FOIA Release from SPACECOM

In April 2021, during the Crew-2 mission’s historic journey to the International Space Station (ISS), SpaceX’s Crew Dragon capsule was briefly thought to be on a collision course with an unidentified object. NASA’s preliminary assessment categorized this event as a potential conjunction, prompting astronauts to suit up for extra safety. However, after a detailed investigation, it was labeled a false alarm, sparking intrigue about the nature of the incident and raising questions on the identification and tracking of space debris.

Now, newly released documents rom Space Command (SPACECOM), obtained through a Freedom of Information Act (FOIA) request originally filed by The Black Vault, offer a deeper insight into the complexity and urgency of this event. Communications between NASA officials, the U.S. Space Force, and SpaceX reveal the scramble to understand and respond to the potential hazard. The detailed internal emails and operational reports included in the release show that the initial warning stemmed from an analyst satellite that remained in the system after the Crew-2 capsule’s launch.

Further complicating matters, analysts had not fully briefed all crew members or relevant NASA personnel about the object, leading to confusion during the critical hours when the potential conjunction was reported. Due to this incomplete information, the Crew-2 capsule was mistaken for a separate object, which heightened the perceived danger of a collision. The result was a series of frantic communications where NASA directed SpaceX astronauts to suit up as a precautionary measure.

The newly declassified documents also highlight how the chain of communication failed to ensure timely and accurate information flow.

These documents are also heavily redacted, raising questions about why the Department of Defense (DoD) insists on keeping so much information confidential when the event was ultimately a false alarm. Rear Admiral William P. Pennington, USSPACECOM Chief of Staff, determined that these redactions fall under several exemptions, including classified national security information, proprietary data, pre-decisional communications, and personal privacy concerns. Still, the redactions evoke curiosity regarding the need for such secrecy in an incident supposedly rooted in a harmless miscommunication.

The redactions used are primarily FOIA exemptions (b)(4) and (b)(5). These exemptions provide the legal basis for withholding sensitive information, classified or not, but the sheer volume of redactions raises concerns about transparency and excessive secrecy.

Exemption (b)(4) protects “trade secrets and commercial or financial information obtained from a person and privileged or confidential.” In this case, the redaction is likely invoked to protect SpaceX’s proprietary data regarding spacecraft systems, operational protocols, and other sensitive technical information that could be exploited by competitors or adversaries.

Exemption (b)(5) covers “inter-agency or intra-agency memorandums or letters which would not be available by law to a party other than an agency in litigation with the agency.” Often referred to as the “deliberative process privilege,” it allows government agencies to keep internal discussions, draft documents, and advisory opinions private to encourage open dialogue and protect decision-making processes. This exemption applies to many internal communications regarding the investigation and the resulting Operational Review Board findings. While safeguarding the integrity of decision-making processes is essential, the extent of the redactions raises questions about over use of the exemption and the secrecy behind it. The public has a right to understand how government agencies manage such incidents to improve future transparency and accountability.

Additionally, one page was classified under Exemption (b)(1), which applies to information specifically authorized to be kept secret in the interest of national defense or foreign policy. This sole classified SECRET page likely contains national security information about space situational awareness operations that should remain confidential, and is largely withheld.

Also within the redacted sections, various emails and internal reports emphasize the significant pressure faced by personnel in charge of space traffic management. The 18th Space Control Squadron (18 SPCS) (now known as the 18th Space Defense Squadron) ordered an Operational Review Board (ORB) to investigate the false conjunction. The ORB’s findings pointed to a failure in crew changeover, inadequate analysis procedures, and a lack of comprehensive pre-mission planning. Steps have since been implemented to improve the accuracy of conjunction assessments and bolster communication between the U.S. Space Force, NASA, and SpaceX. These measures include revising internal procedures and increasing staff training to ensure effective identification of objects and thorough analysis of collision risks.

The FOIA-released documents shed light on an event that, though non-threatening, could have had more severe implications if mishandled. Ultimately, they highlight the urgency of enhancing collaboration among space agencies and improving the technologies and protocols required to safely navigate and operate in space.

But, why all the redactions?

###

Document Archive

On May 10, 2024, Space Command released more than 160 pages of material on the above incident.

SPACECOM Released Documents [168 Pages, 25.2MB]

 

 

 

 

 

 

---

 

Follow The Black Vault on Social Media: