Not surprising. The radio problems are really suspicious. I mean, didn't they mount one on a plane and try to call the ground? You should be able to get about 100 km 62 miles before 40,000 ft goes over the horizon.
On Thu, Feb 27, 2020 at 9:04 PM Seymour J Metz <[email protected]> wrote: > > Surprising? After the gross negligence and stonewalling on the 737 max? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Mike Schwab [[email protected]] > Sent: Thursday, February 27, 2020 9:18 PM > To: [email protected] > Subject: OT Boeing flight software > > https://www.orlandosentinel.com/space/os-bz-boeing-safety-commercial-crew-20200226-bgvthodnjzgmlc36hsxcaopahu-story.html > > Boeing didn’t perform full end-to-end test of its astronaut capsule > before troubled mission, ‘surprising’ NASA safety panel. > > Critically, the panel learned early this month that Boeing did not > perform a full, end-to-end integrated test of Starliner in a Systems > Integration Lab with ULA’s Atlas V rocket. The test typically shows > how all the software systems during each component of the mission > would have responded with each other through every maneuver — and it > could potentially have caught the issues Boeing later experienced in > the mission. > > “It’s pretty exhaustive. You gotta do that,” said Christopher Saindon, > a former member who ended his tenure on the panel in mid-February. > “That was somewhat surprising to us on the panel. There were certainly > gaps in the test protocol.” > > > It was software that ultimately did fail Boeing when it flew Starliner > on a Dec. 20 mission intended to dock with the International Space > Station. The capsule’s internal clock was 11 hours ahead, causing it > to miss critical maneuvers and fly into the incorrect orbit. Then, > communication issues potentially caused by cell towers in the area > blocked Boeing from sending a command to rectify the orbit. Starliner, > the company determined, wasn’t going to be able to reach the space > station. > > But in the process of bringing it back down and re-checking its > software, the company caught yet another issue that could have caused > Starliner to collide with its service module when the two separated > prior to the capsule’s return to Earth. Teams were able to correct the > issue before to the capsule’s return on Dec. 22, but the multitude of > problems have led NASA to call for a full re-verification of Boeing’s > software — a process that will take analyzing about a million lines of > code. > > Software issues are also plaguing another arm of Boeing, which is > dealing with the fall out of problems with its 737 Max airplanes that > led to the deaths of 346 people and has grounded the planes. > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
