Article 4WVJJ Starliner’s timer was off—capsule thought engines were firing when they weren’t

Starliner’s timer was off—capsule thought engines were firing when they weren’t

by
Eric Berger
from Ars Technica - All content on (#4WVJJ)
  • Boeing-OFT-Dec-20-2019-9255-980x653.jpg

    An Atlas V rocket takes off from Cape Canaveral Air Force Station on Friday morning. [credit: Trevor Mahlmann ]

Right on schedule Friday morning, an Atlas V rocket launched the Starliner spacecraft into a planned suborbital trajectory. This is a critical mission for NASA and Boeing, as the company seeks to use this test flight to prove its capsule's readiness to launch humans into space next year.

After being released by the rocket, Starliner was supposed to use its Orbital Maneuvering and Attitude Control engines to provide the thrust needed to reach a stable orbit and begin the process of catching up to the International Space Station. But that did not happen.

During a post-launch news conference, NASA Administrator Jim Bridenstine explained that the mission elapsed timing system had an error in it, with the net effect that the spacecraft thought it was performing an orbital insertion burn, when in fact it was not. The on-board computer then expended a significant amount of propellant to maintain a precise attitude, thinking it had reached orbit.

Read 11 remaining paragraphs | Comments

index?i=OsZBTKZpJrw:O3MOa_pnTnc:V_sGLiPB index?i=OsZBTKZpJrw:O3MOa_pnTnc:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments