Satellite debris forces space stop crew to take shelter

A satellite breakup resulting in a “cloud” of debris prompted the seven-member crew of the International Space stop to seal hatches and take shelter in their Crew Dragon and Soyuz spacecraft early Monday, officials said.

Flight controllers in Houston woke up the crew to inform them of the possible close encounter, or “conjunction.”

“stop on space-to-ground 2 for an early wakeup,” mission control called. “We were recently informed of a satellite breakup and need to have you guys start reviewing the safe haven procedure.”

The International Space stop


The crew was told to close hatches between the U.S. and Russian segments and to seal off modules extending radially from the lab’e long axis, which includes the European Space Agency’s Columbus module, Japan’s Kibo, the U.S. Quest airlock and NASA’s peacefulness module.

“Because of the character of the satellite breakup, we expect that we would see this risk every 90 minutes,” mission control radioed. “And while the teams on the ground are analyzing the situation, we expect we could be staying in the config with the radial hatches closed for up to a day.”

After sheltering in their respective spacecraft during the initial close approach period, the crew members were cleared to return to the stop’s interior and reopen hatches between the U.S. and Russian segments. The U.S. crew was allowed to briefly open side-hatches as needed between possible encounters.

“Thanks for a crazy but well-coordinated day,” astronaut Mark Vande Hei said during an end-of-day planning conference with flight controllers in Houston. “We really appreciate all the situational awareness you gave us. And it was certainly a great way to bond as a crew starting off in our very first work day in space!”

Vande Hei and Soyuz MS-19/65S crewmates Anton Shkaplerov and Pyotr Dubrov were joined last Thursday by four fresh crew members who arrived aboard a SpaceX Crew Dragon ferry ship.

“We really appreciate you guys’ patience,” mission control replied to Vande Hei. “It’s a crazy way to start a mission, we definitely understand, and you guys were troopers by all this. We really appreciate it.”

Said Vande Hei: “We’re looking forward to a calmer day tomorrow.”

The origin of the debris is not however confirmed, but U.K.-based Seradata, which operates the commercial SpaceTrak satellite database, reported the breakup may have involved Cosmos 1408, a long-retired Russian electronic eavesdropping spacecraft in polar orbit.

The company tweeted that a Russian anti-satellite test may have been conducted, although that could not be closest confirmed.

“ASAT missile strike now suspected,” the company tweeted. “Seradata SpaceTrak database orbital data had Cosmos 1408 in a 487 x 461 km orbit — a bit higher than ISS but not much. The ASAT strike on Cosmos 1408 would cause some debris to be fired below it … threatening ISS with a crossing debris cloud.”

In an email, Air Force Major Annmarie Annicelli said U.S. Space Command “is aware of a debris-generating event in outer space. We are actively working to characterize the debris field and will continue to ensure all space-faring nations have the information necessary to maneuver satellites if impacted.”

She said Space Command is working with the State Department and NASA concerning the reports “and will provide an update in the near future.”

U.S. radar systems regularly track objects in low-Earth orbit and compute possible close approaches between spacecraft, prioritizing piloted vehicles like the space stop.

Depending on how close to the lab a piece of debris is expected to pass, the crew can be asked to take shelter in their respective spacecraft, ready to make a quick return-to-Earth in case of an impact.

During Monday’s encounter, Shkaplerov, Dubrov and Vande Hei protected in place in their Soyuz MS-19/65S spacecraft. The newly arrived Crew Dragon astronauts — Raja Chari, Thomas Marshburn, Kayla Barron and Matthias Maurer — protected in their “Endurance” capsule at the forward end of the space stop.

Click: See details

Leave a Reply