Newly launched audio reveals the short scramble the Expedition 66 crew undertook to get to security following an anti-satellite check on Monday (Nov. 15).
A Russian impactor was deliberately smashed right into a defunct Soviet satellite, Cosmos 1408, inflicting a cloud of particles that got here unexpectedly near the International Space Station early that morning.
The audio contains a dialog between NASA astronaut and flight engineer Mark Vande Hei, who’s on his second long-term length flight in space.
“Sorry for the early call,” the unnamed floor controller says; it in all probability was a fellow astronaut, as capcoms (capsule communicators) are typically tasked with such duties. “We were recently informed of a satellite breakup,” the controller continues, “and need to have you start reviewing the safe haven procedure.”
Within seconds, Vande Hei calmly returns the decision and repeats again the directions that floor management provides, to verify the directions and be sure that he heard them accurately. (This is normal working process amongst astronauts and Mission Control throughout emergencies, to verify directions are understood.)
The audio reveals that the crew was requested to implement “safe haven procedures,” together with shifting to their return spacecraft and shutting hatches to radial modules on the station. These hatches included Columbus, Kibo, the Permanent Multipurpose Module (aka Nauka), Bigelow Expandable Activity Module and Quest Joint Airlock, NASA said in a statement.
Later within the audio, the crew is suggested on what to do if a chunk of particles hits the SpaceX Crew Dragon, which is the return craft for 4 of the seven crewmembers. Mission Control advises that if the spacecraft is hit, to return first to the ISS to await additional directions, which Vande Hei confirms.
The crew took shelter twice throughout the Monday morning occasion, which was later condemned by each the U.S. State Department and NASA administrator Bill Nelson, who stated there will likely be a considerable further threat to exploration in low Earth orbit. Both Roscosmos and the Russian authorities, conversely, have denied that the incident posed threat to the ISS.
Follow Elizabeth Howell on Twitter @howellspace. Follow us on Twitter @Spacedotcom and on Facebook.