Spaceflight

A Youtuber called Ellie in Space claims that a NASA source sent her the following message. It was in response to a question about when NASA knew that the Boe-CFT mission's Starliner vehicle would not be able to undock and return to Earth autonomously without being reconfigured.

So if you want to know when??? Well always, but it wasn't a reasonable consideration to retain the unmanned Starliner capsule software to work in the manned version of the capsule as a contingency. Would you call that a mistake?? Maybe, but let's think about the need to really ever plan to send folks up to space and leave them there with no way to fly home... they would always chose to risk the ride vs having no way home.

No one really considered this very unique and dynamic situation would happen.

Background

I believe this issue was first brought to light by Eric Berger.

Regardless, sources described the process to update the software on Starliner as "non-trivial" and "significant," and that it could take up to four weeks. This is what is driving the delay to launch Crew 9 later next month.

A couple of days later, NASA held a press teleconference in which they emphasized that what was needed was merely a "data load", not a software change. But they indicated timelines that do seem consistent with the "up to four weeks" claim by Berger's source.

My questions

Aren't there several realistic scenarios where you'd want to undock a crew vehicle, without its crew (or at least without them being in a fit state to operate the vehicle), in less than 4 weeeks?

Can Crew Dragon do it? Soyuz?

The upper stage from a Chinese rocket that launched a batch of Internet satellites Tuesday has broken apart in space, creating a debris field of at least 700 objects in one of the most heavily-trafficked zones in low-Earth orbit. US Space Command, which tracks objects in orbit with a network of radars and optical sensors, confirmed the rocket breakup Thursday. Space Command initially said the event created more than 300 pieces of trackable debris. The military's ground-based radars are capable of tracking objects larger than 10 centimeters (4 inches). Later Thursday, LeoLabs, a commercial space situational awareness company, said its radars detected at least 700 objects attributed to the Chinese rocket. The number of debris fragments could rise to more than 900, LeoLabs said. The culprit is the second stage of China's Long March 6A rocket, which lifted off Tuesday with the first batch of 18 satellites for a planned Chinese megaconstellation that could eventually number thousands of spacecraft. The Long March 6A's second stage apparently disintegrated after placing its payload of 18 satellites into a polar orbit.

Space Command said in a statement it has "observed no immediate threats" and "continues to conduct routine conjunction assessments to support the safety and sustainability of the space domain." According to LeoLabs, radar data indicated the rocket broke apart at an altitude of 503 miles (810 kilometers) at approximately 4:10 pm EDT (20:10 UTC) on Tuesday, around 13-and-a-half hours after it lifted off from northern China. At this altitude, it will take decades or centuries for the wispy effect of aerodynamic drag to pull the debris back into the atmosphere. As the objects drift lower, their orbits will cross paths with SpaceX's Starlink Internet satellites, the International Space Station and other crew spacecraft, and thousands more pieces of orbital debris, putting commercial and government satellites at risk of collision.

The Cygnus spacecraft has completed two delta velocity burns, and it remains on track for a capture by the space station’s robotic arm slated for 3:10 a.m. on Tuesday, Aug. 6. The spacecraft is in a safe trajectory, and all other systems are operating normally.

Shortly after launch on Sunday, the spacecraft performed as designed by cancelling a scheduled engine burn due to a slightly low initial pressure reading flagged by the Cygnus onboard detection system. Engineers at Northrop Grumman’s mission control center in Dulles, Virginia evaluated the pressure reading, confirmed it was acceptable and re-worked the burn plan to arrive at the space station on the originally planned schedule.