[ad_1]
\n<\/p>\n
After yesterday\u2019s launch of the first crewed Starliner mission was scrubbed<\/a>, NASA, Boeing and ULA made the decision to wait a few days before making another attempt. Starliner was scheduled to finally lift off on Saturday afternoon after a series of delays, but this attempt was aborted due to a last-minute issue with a ground computer system that plays a key role in launching the rocket. While NASA and partners discussed possibly flying today following their assessment of the issue, they\u2019ve decided to hold off until the next opportunities, either on June 5 or 6.<\/p>\n Saturday\u2019s launch wasn\u2019t scrubbed due to a problem with the Starliner craft itself, but because an automatic hold was issued by the ground launch sequencer for a then-unknown reason. In a press conference later on Saturday, Tory Bruno, president and CEO of ULA explained that it came down to a problem in verifying the launch sequencer\u2019s redundancy. There are three large computers in this system, all of which are the same so it\u2019s \u201ctriple redundant,\u201d Bruno said. During the system health check in the minutes before launch, one of the computers came up slow, triggering an automatic hold.<\/p>\n NASA<\/a> said the decision to forgo today\u2019s launch attempt was made in order to \u201cgive the team additional time to assess a ground support equipment issue.\u201d The launch window opens again on June 5, but no target liftoff time has been announced just yet. If Starliner doesn\u2019t fly by June 6, it\u2019ll be set back by at least another 10 days, ArsTechnica<\/em><\/a> reports, as the ULA team will need to swap out the Atlas V rocket\u2019s batteries.<\/p>\n<\/div>\n