Boeing Orbital Flight Test

Instead of carrying astronauts, the flight carried an Anthropomorphic Test Device (ATD) wearing Boeing's custom flight suit. The ATD is named Rosie (aka "Rosie the Rocketeer"[5]), as a homage to all the women who helped contribute to the Starliner Program.[6] The capsule was weighted similarly to missions with astronauts onboard and carried approximately 270 kg (600 lb) of supplies and equipment including a plush toy of Snoopy and holiday presents for the Expedition 61 crew members. Due to the inability to dock with the ISS, this cargo was never delivered.

The first Atlas V N22, designated AV-080, launched the CST-100 Starliner spacecraft on an uncrewed test flight to the International Space Station. The capsule was intended to dock with the space station, then return to Earth to land in the Western United States after an orbital shakedown cruise ahead of Boeing Crewed Flight Test.

OFT is the first flight of an Atlas V without a payload fairing and its first flight with a dual-engine Centaur upper stage. The dual-engine Centaur utilizes two RL-10 and is required for Starliner flights in order to provide a launch trajectory that allows for a safe abort at any point in the mission.[7]

The mission launched successfully on 20 December 2019 at 11:36:43 UTC, but thirty-one minutes after launch the mission elapsed timer (MET) clock made an error. During a later press conference, it was revealed that MET was offset by 11 hours. When it became obvious that the maneuver did not happen, NASA and Boeing tried sending commands to get Starliner back on track, but the position of the spacecraft switching communications between two TDRS satellites delayed the orbital insertion burn. This delay resulted in an abnormal orbit and excessive fuel use. The decision was made to scratch the ISS rendezvous/docking since the spacecraft burned too much fuel to reach orbit even after Mission control center fixed the MET clock issue. NASA and Boeing officials placed the spacecraft in a different orbit and the entire flight plan had to be redone and the mission was reduced from eight days to three flight days.

By 11:40 UTC, the Starliner was in a "stable orbit", though orbital insertion was not nominal.[8] It was later confirmed that Starliner had placed itself into a 187 x 222 km orbit.[9]

By 13:55 UTC, mission control center had realized that docking with the ISS was precluded.[10] Despite not being able to dock and the MET anomaly, Jim Bridenstine stated during a press conference that "A lot of things went right. And this is in fact why we test".

Calypso in processing after returning to Earth.

On 22 December 2019, Starliner was cleared to reenter the Earth's atmosphere. After deorbiting, Starliner reentered the Earth's atmosphere, before successfully deploying all sets of parachutes. Starliner deployed airbags and successfully touched-down at White Sands Space Harbor at 12:58:53 UTC. Though the ISS rendezvous that was planned for the OFT did not happen, Jim Chilton, vice president for Boeing's space and launch division, estimated that Starliner has achieved over 60% of the flight objectives, and this could reach over 85% once all the data from the spacecraft is retrieved and analyzed.[11]

The spacecraft will later be reused on mission Boeing Starliner-1. Its commander, Sunita Williams, informally dubbed the spacecraft "Calypso" after the famed oceanographic research ship and its eponymous John Denver song.[12]

An issue with the spacecraft's Mission Elapsed Time (MET) clock occurred 31 minutes into flight. Due to intermittent space-to-ground communication issues flight controllers could not correct the issue.[13] This anomaly caused the spacecraft's Orbital Maneuvering Thrusters (OMT) to burn into an incorrect orbit causing too much propellant to be burned. This precluded a rendezvous and docking with the ISS.[14] The mission was reduced to just three days, with the spacecraft successfully landing at White Sands Space Harbor on 22 December 2019.[11]

After the mission, it was revealed that another critical software bug was found in flight, which could have resulted in the service module bumping back into Starliner after separation. The bug was fixed two hours before the capsule re-entered. Had the bug not been discovered and fixed, it may have damaged Starliner and prevented a safe landing.[15] Additionally, it was determined that had the first anomaly not occurred, the second would not have been detected.[16]

On 7 February 2020, NASA shared their preliminary findings about the Boeing OFT mission and discovered software problems with the Mission Elapsed Time (MET), which incorrectly polled time from the Atlas V booster nearly 11 hours prior to launch. Another software issue occurred within the Service Module (SM) Disposal Sequence, which incorrectly translated the SM disposal sequence into the SM Integrated Propulsion Controller (IPC). This could have made the service module crash into the capsule after separation, potentially leading to a catastrophic failure of the capsule. In addition, an Intermittent Space-to-Ground (S/G) forward link issue, which impeded the Flight Control team's ability to command and control the vehicle, was found. The current investigation was expected to last until end of February 2020, in addition a full-scale safety review was planned that would likely take months.[13][17]

On 6 March 2020, NASA gave an update on the anomalies.[18] They announced 61 corrective actions that addressed the MET and service module disposal software issues.[18][19] The mission was declared a "high visibility close call" as there were two times where the spacecraft could have been lost. NASA found factors internally that led to the anomalies such as the oversight over software.[20]

On 7 July 2020, NASA and Boeing announced the completion of the Space-to-Ground communication issue, marking the completion of the OFT review.[21] The number of corrective actions was increased to 80 from the March 2020 update.[22] 21 recommendations focused on a need for more testing and simulations; including the necessity to do full end to end tests prior to flights instead of testing in chunks as done in the OFT.[23] 10 recommendations were made to cover software requirements such that they have proper coverage to catch errors during testing. 35 of the recommendations surrounded improvements over process and operations such as including more reviews and use of experts. 7 recommendations covered software updates that addresses the three main anomalies that occurred during the flight. The final 7 included "Knowledge Capture" and Boeing organizational changes to enable better safety reporting. They also included hardware changes to filter out radio interference and others to address the communication issue.[24][25]

Internally within NASA the investigation found that the lack of oversight over Starliner software was from NASA's focus of resources on other high risk parts of the flight.[23] In addition, NASA may have had less oversight due to Boeing's traditional systems development style compared to SpaceX; NASA had increased their oversight of SpaceX due to their different working practices.[25] NASA made 6 recommendations internally to prevent similar occurrences in the future. This included the need for NASA to review and approve the contractors' "hazard verification tests plans" before the test.[24]

• Crew Dragon
• Crew Dragon Demo-1, SpaceX's first (uncrewed) orbital mission with Crew Dragon
• Crew Dragon Demo-2, SpaceX's second orbital and first crewed mission with Crew Dragon

• Official Webpage of the CST-100 Starliner
• NASA Live: Official Stream of NASA TV