4:47 AM
@ErinAnne unexpected because apparently they decided to change landing sites after the critical design review. The original site *didn't* have craters/topography like their new site did, and they didn't do due diligence afterwards, apparently
https://spacenews.com/software-problem-blamed-for-ispace-lunar-lander-crash/
> A factor in the crash, he said, was a change in landing sites made after the mission completed its critical design review in February 2021. The mission was originally to land in Lacus Somniorum, a basaltic plain with few craters. That change, he suggested, was not sufficiently tested before launch.
>
> The company changed the landing site “to maximize the benefit of the mission,” he said, for both the company and its payload customers. “This is a payload transportation business, and we need to maximize the paylo…
> A factor in the crash, he said, was a change in landing sites made after the mission completed its critical design review in February 2021. The mission was originally to land in Lacus Somniorum, a basaltic plain with few craters. That change, he suggested, was not sufficiently tested before launch.
>
> The company changed the landing site “to maximize the benefit of the mission,” he said, for both the company and its payload customers. “This is a payload transportation business, and we need to maximize the paylo…
5 hours later…
9:23 AM
I kind of don't like the message in the end of the Scott Manley video and somewhat in the ispace announcement that the problem is software, rather than specifically navigation
they got bit by a standard filtering technique that they applied without really thinking through what the filter would need to accept and reject
4 hours later…
1:22 PM
Probably as usual - QA (simulator test) issue.
Boeing's 2nd Starliner software glitch.
Issues during the Orbital Flight Test (OFT) mission, particularly when it comes to the spacecraft's software. Along with the previously disclosed error with Starliner's onboard timer, a second software issue could have potentially led to a slight but problematic collision of two of the spacecraft's components, investigators determined.
Boeing's 2nd Starliner software glitch.
Issues during the Orbital Flight Test (OFT) mission, particularly when it comes to the spacecraft's software. Along with the previously disclosed error with Starliner's onboard timer, a second software issue could have potentially led to a slight but problematic collision of two of the spacecraft's components, investigators determined.
5 hours later…
6:07 PM
@ErinAnne moreover, it’s really kind of a project management failure. From the sounds of it, with the original plan, the software and hardware would’ve been sufficient. It was only after making changes late in the game without doing due diligence that caused the issues
1 hour later…
« first day (3601 days earlier) ← previous day next day → last day (341 days later) »