Back
Science

Artemis II Mission Reports Pre-Launch Safety Investigation, In-Flight Computer, and Waste System Issues

View source

Pre-Launch System Investigation

Approximately one hour before the launch window opened for the Artemis II mission, a "no-go" status was briefly declared.

Approximately one hour before the launch window opened for the Artemis II mission, a "no-go" status was briefly declared. This was initiated to investigate an issue concerning the flight termination system, a safety feature of the mission. The issue was subsequently resolved, and the mission proceeded with its launch.

In-Flight Computer System Malfunction

During the first day of the mission, approximately seven hours into the flight, Mission Commander Reid Wiseman reported difficulties accessing email on his Personal Computing Device (PCD).

During the first day of the mission, approximately seven hours into the flight, Mission Commander Reid Wiseman reported difficulties accessing email on his Personal Computing Device (PCD). Wiseman stated that two Microsoft Outlook applications on his PCD were non-functional and requested technical assistance from NASA Mission Control in Houston.

The device, referred to as Optimus and also identified as PCD 1, is an MS Surface Pro used by the crew for internet access, tracking mission timelines, and managing tasks and communications.

Mission Control confirmed they would remotely access Wiseman's system. Following the remote access, Mission Control later informed Wiseman that remote access to his PCD 1 was complete and the issue was resolved, with the system appearing offline as expected.

Universal Waste Management System Issue

Mission specialist Christina Koch reported a problem with the Orion capsule's Universal Waste Management System. Specifically, she identified a jammed fan within the toilet system.

Mission specialist Christina Koch reported a problem with the Orion capsule's Universal Waste Management System. Specifically, she identified a jammed fan within the toilet system. NASA spokesperson Gary Jordan stated that ground teams were developing instructions for the crew to address and clear the fan to restore the system's functionality.

Agency Responses

Inquiries regarding the email outage were directed to NASA and Microsoft by outlets including WIRED and Business Insider. A Microsoft Outlook press representative indicated that information from the company might become available at a later time. NASA had not yet provided an official response regarding the incident.

Historical Context

A notable incident occurred in 1962 when the NASA Mariner 1 spacecraft was destroyed shortly after launch. This was attributed to a guidance system failure stemming from a single missing character or hyphen in its handwritten code...

Some reports included historical context regarding software issues in space missions. A notable incident occurred in 1962 when the NASA Mariner 1 spacecraft was destroyed shortly after launch.

This was attributed to a guidance system failure stemming from a single missing character or hyphen in its handwritten code, which caused the Atlas Agena rocket to deviate from its intended course. The mission failure was estimated to cost $18.5 million at the time, an amount exceeding $200 million in today's value.