{"id":37700,"date":"2020-02-29T00:16:20","date_gmt":"2020-02-28T16:16:20","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/boeing-provides-update-path-forward-for-starliner\/"},"modified":"2020-02-29T00:16:20","modified_gmt":"2020-02-28T16:16:20","slug":"boeing-provides-update-path-forward-for-starliner","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/boeing-provides-update-path-forward-for-starliner\/","title":{"rendered":"Boeing provides update, path forward for Starliner"},"content":{"rendered":"<p>Just over two months after the truncated Orbital Flight Test of their Starliner crew capsule, Boeing officials have provided an in-depth overview of the issues faced on the flight.<\/p>\n<p>The update, held on Friday, 28 February, also provided information on the path forward for Starliner, including the on-going software audit, closing process escapes and software testing gaps, as well as work with NASA to determine the future flight schedule.<\/p>\n<p>NASA will ultimately be the one to decide what kind of flight Starliner will fly next and when that next flight will occur, but John Mulholland, Vice President and Program Manager for Boeing\u2019s Commercial Crew Program, confirmed there is room on United Launch Alliance\u2019s busy Atlas V schedule this year for another Starliner flight.<\/p>\n<p>However, Mr. Mulholland advised cautioned on pinning down exactly when Starliner\u2019s next flight will happen, saying that until the final recommendations from the Independent Review Team are received (next week), until Boeing\u2019s internal audit of the software and processes that lead to the in-flight issues not being discovered prior to flight are completed, and until Boeing can implement new requirements and rules for software verification and validation, there cannot be a realistic discussion of when Starliner will return to flight.<\/p>\n<p>Of note, Mr. Mulholland reiterated \u2014 as he has throughout the last two months \u2014 that the Atlas V rocket performed flawlessly on the Orbital Flight Test launch on 20 December 2019 from the Cape Canaveral Air Force Station, Florida.<\/p>\n<\/p>\n<p><iframe title=\"Starliner OFT Atlas V Launch LIVE Dec 19 2019\" src=\"https:\/\/www.youtube.com\/embed\/cpdIs2nn2cM?start=3764&amp;feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" allowfullscreen=\"\" name=\"fitvid0\" data-gtm-yt-inspected-14=\"true\" data-gtm-yt-inspected-21=\"true\"><\/iframe><\/p>\n<p>The Atlas V dropped Starliner off in the planned sub-orbital trajectory and is not in any way to blame for the issues faced after Starliner separated from the top of the Centaur upper stage.<\/p>\n<p><b>What went right:<\/b><\/p>\n<p>SpaceX launch tickets<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>Space Shuttle models<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>NASA educational resources<path d=\"M7.59009 18.59L9.00009 20L17.0001 12L9.00009 4L7.59009 5.41L14.1701 12\" style=\"animation: initial !important; background: initial !important; border: 0px !important; box-shadow: none !important; color: inherit !important; cursor: inherit !important; direction: inherit !important; display: inline !important; fill: currentcolor !important; filter: initial !important; float: none !important; margin: 0px !important; opacity: initial !important; outline: 0px !important; overflow: initial !important; padding: 0px !important; stroke: initial !important; transform: initial !important; vertical-align: initial !important; visibility: inherit !important;\"><\/path>\n<p>     (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n<p>While much attention has been rightly paid to the issues encountered on Starliner\u2019s debut, less focus has been given to the 80%+ of the mission that went perfectly.<\/p>\n<p>Of note, numerous Starliner systems performed better than pre-flight predictions, including the craft\u2019s critical Environmental Control and Life Support Systems, its thruster systems, and its avionics cooling systems (used when the radiators on the Service Module are unavailable during pre-launch, launch, and reentry\/landing operations).<\/p>\n<p>The craft\u2019s Thermal Protection System \u2014 more commonly called a heat shield \u2014 also performed above predictions.<\/p>\n<p>The same is true for the solar panels on the base of the Service Module and Starliner\u2019s associated power systems \u2014 which actually provided more power than predicted.<\/p>\n<p>In fact, some of these systems performed so well together that the conservative operating guidelines in place on the Orbital Flight Test can be relaxed going forward, providing additional efficiency to the craft.<\/p>\n<p>Additionally, while not used to dock to Station, Starliner\u2019s NASA Docking System also underwent a near-complete checkout during the two-day free-flight, with Mr. Mulholland noting \u201cwe know we have good control of the docking system.\u201d<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" aria-describedby=\"caption-attachment-64706\" class=\"size-full wp-image-64706\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1.jpg\" alt=\"\" width=\"1200\" height=\"807\" srcset=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1.jpg 1200w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1-350x235.jpg 350w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1-520x350.jpg 520w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1-768x516.jpg 768w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2020\/01\/OFT-landing-3-1200x807-1-1170x787.jpg 1170w\" sizes=\"(max-width: 1200px) 100vw, 1200px\"><\/p>\n<p id=\"caption-attachment-64706\" class=\"wp-caption-text\">Teams process the Starliner vehicle after landing. Credit: NASA<\/p>\n<p>In specific regard to Starliner\u2019s thruster system, Boeing talked in-depth about the stress put on the thrusters to operate outside their normal envelope.<\/p>\n<p>After Starliner didn\u2019t perform the Orbital Insertion burn (because of the Mission Elapsed Timer software anomaly) when intended, the spacecraft had to perform a \u201cvery inefficient three-axis prolonged thruster burn to get Starliner into a stable orbit,\u201d related Mr. Mulholland.<\/p>\n<p>This necessitated burning the thrusters far longer than the nominal mission plan, which introduced \u201cfalse positive\u201d overheat signatures.<\/p>\n<p>These \u201cfalse positives\u201d were not unexpected once the system was put through this inefficient three-axis burn.<\/p>\n<p>The thruster systems were shut down out of caution after the three-axis burn got Starliner into a power-positive and stable orbit, and teams with thruster experience from the Shuttle-era then investigated the \u201cfalse positives\u201d and worked to bring each thruster back online.<\/p>\n<p>All but one thruster was successfully returned to service, and all that were brought back functioned perfectly for the rest of the mission \u2014 save one very minor issue with an attitude control thruster\u2019s nitrogen pressurization valve that failed to close during reentry.<\/p>\n<p>This valve closure issue was not a flight or safety concern, but Boeing has pulled the affected thruster to determine why the valve didn\u2019t close.<\/p>\n<p><iframe id=\"twitter-widget-1\" scrolling=\"no\" frameborder=\"0\" allowtransparency=\"true\" allowfullscreen=\"true\" class=\"\" style=\"position: static; visibility: visible; width: 0px; height: 0px; display: block; flex-grow: 1;\" title=\"X Post\" src=\"https:\/\/platform.twitter.com\/embed\/Tweet.html?creatorScreenName=NASASpaceflight&amp;dnt=true&amp;embedId=twitter-widget-1&amp;features=eyJ0ZndfdGltZWxpbmVfbGlzdCI6eyJidWNrZXQiOltdLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X2ZvbGxvd2VyX2NvdW50X3N1bnNldCI6eyJidWNrZXQiOnRydWUsInZlcnNpb24iOm51bGx9LCJ0ZndfdHdlZXRfZWRpdF9iYWNrZW5kIjp7ImJ1Y2tldCI6Im9uIiwidmVyc2lvbiI6bnVsbH0sInRmd19yZWZzcmNfc2Vzc2lvbiI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfZm9zbnJfc29mdF9pbnRlcnZlbnRpb25zX2VuYWJsZWQiOnsiYnVja2V0Ijoib24iLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X21peGVkX21lZGlhXzE1ODk3Ijp7ImJ1Y2tldCI6InRyZWF0bWVudCIsInZlcnNpb24iOm51bGx9LCJ0ZndfZXhwZXJpbWVudHNfY29va2llX2V4cGlyYXRpb24iOnsiYnVja2V0IjoxMjA5NjAwLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X3Nob3dfYmlyZHdhdGNoX3Bpdm90c19lbmFibGVkIjp7ImJ1Y2tldCI6Im9uIiwidmVyc2lvbiI6bnVsbH0sInRmd19kdXBsaWNhdGVfc2NyaWJlc190b19zZXR0aW5ncyI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfdXNlX3Byb2ZpbGVfaW1hZ2Vfc2hhcGVfZW5hYmxlZCI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfdmlkZW9faGxzX2R5bmFtaWNfbWFuaWZlc3RzXzE1MDgyIjp7ImJ1Y2tldCI6InRydWVfYml0cmF0ZSIsInZlcnNpb24iOm51bGx9LCJ0ZndfbGVnYWN5X3RpbWVsaW5lX3N1bnNldCI6eyJidWNrZXQiOnRydWUsInZlcnNpb24iOm51bGx9LCJ0ZndfdHdlZXRfZWRpdF9mcm9udGVuZCI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9fQ%3D%3D&amp;frame=false&amp;hideCard=false&amp;hideThread=false&amp;id=1233043953756311554&amp;lang=en&amp;origin=https%3A%2F%2Fwww.nasaspaceflight.com%2F2020%2F02%2Fboeing-update-path-forward-starliner%2F&amp;sessionId=fd0c6158d293baef2631662fd54a47a69a73ce6e&amp;siteScreenName=NASASpaceflight&amp;theme=light&amp;widgetsVersion=6a3ad42b224df%3A1778106238597&amp;width=550px\" data-gtm-yt-inspected-14=\"true\" data-gtm-yt-inspected-21=\"true\" data-tweet-id=\"1233043953756311554\"><\/iframe><\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\" data-twitter-extracted-i1783499082734586997=\"true\">\n<p lang=\"en\" dir=\"ltr\">Yesterday- launch training in the Boeing Mission Simulator- feeling comfortable in our suits.  Go #Starliner! @BoeingSpace @Commercial_Crew  #NASA pic.twitter.com\/oXtgQgTAi7<\/p>\n<p>\u2014 Col. Mike Fincke (@AstroIronMike) February 27, 2020<\/p>\n<\/blockquote>\n<p>The landing itself was within 182 meters (200 yards) of the pinpoint center of the landing zone, and landing loads were \u201cbenign, below prediction, and three times lower than NASA requirements,\u201d noted Mr. Mulholland.<\/p>\n<p>Parachute performance was also baseline normal.<\/p>\n<p>Moreover, all post-flight data reviews \u2014 a separate set of reviews from the on-going software audit and Independent Review Team action\/review items \u2014 are now complete.<\/p>\n<p>Speaking of the data review, Mr. Mulholland noted that the Orbital Flight Test capsule had been cleared to continue post-mission processing and flight turn-around efforts.<\/p>\n<h4 class=\"widget-title penci-border-arrow\">See Also<\/h4>\n<ul>\n<li>Starliner OFT UPDATES<\/li>\n<li>Starliner\/CST-100 Forum<\/li>\n<li>L2&nbsp;Commercial Crew<\/li>\n<li>Click here to Join L2<\/li>\n<\/ul>\n<p>\u201cBy and large, the vehicle hardware is in outstanding shape after the mission,\u201d said Mr. Mulholland, who praised the technicians and engineers who built Starliner and are now in charge of turning this capsule around for its next flight.<\/p>\n<p>The next capsule (Spacecraft #2) to fly is the one originally earmarked for the Crew Flight Test.&nbsp; It is currently in the hazardous production area of the Commercial Crew and Cargo Processing Facility at the Kennedy Space Center undergoing proof and leak tests.<\/p>\n<p>What kind of mission this capsule will fly \u2014 a repeat of the uncrewed Orbital Flight Test or the Crew Flight Test \u2014 is not yet known.<\/p>\n<p>NASA will brief the public on the results of the Independent Review Team report on Friday, 6 March at 11:00 EST (16:00 UTC).&nbsp; Boeing officials cautioned that NASA might not be ready to make an announcement at that briefing as to whether a reflight of the Orbital Flight Test will be required.<\/p>\n<p><b>The path forward:&nbsp;<\/b><\/p>\n<p>In all, Mr. Mulholland was appreciative of the interim recommendations provided to Boeing by the Independent Review Team, noting that those detailed, preliminary recs \u2014 including investigative and review steps \u2014 have allowed the team to start moving out and strengthening the robustness of the team, the systems, and the processes to ensure safe flights of Starliner.<\/p>\n<\/p>\n<p><iframe title=\"OFT-1 Starliner landing\" src=\"https:\/\/www.youtube.com\/embed\/-cnzuFloDtM?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" allowfullscreen=\"\" name=\"fitvid1\" data-gtm-yt-inspected-14=\"true\" data-gtm-yt-inspected-21=\"true\"><\/iframe><\/p>\n<p>A key step already outlined by the Independent Review Team is the need to improve System Engineering and Integration disciplines.<\/p>\n<p>Some of those improvements have already been implemented \u2014 such as Boeing conducting on-site visits, reviews, and relationship-strengthening discussions with its various suppliers.<\/p>\n<p>But there is still a great deal of work ahead on the software side of things.<\/p>\n<p>\u201cWe need to go look at the software testing process for formal qualification,\u201d noted Mr. Mulholland.&nbsp; \u201cWe\u2019ve already completed an audit on the high and medium logic areas to compare to software testing to identify gaps, and we\u2019ve identified those areas where we did and did not test the software.<\/p>\n<p>\u201cWe\u2019re looking for other anomalies, too, that might need to be fixed.&nbsp; So far, we haven\u2019t found any, but the overall software audit continues.\u201d<\/p>\n<p>Mr. Mulholland pledged that if any more software issues are found in testing, Boeing will reveal those issues and their fixes; moreover, he expects to be able to provide an answer to that within the next month or so.<\/p>\n<p>Mulholland also addressed tough and repeated questions as to why a complete end-to-end test of Starliner\u2019s software, a test that would have caught the two issues that plagued the craft on the Orbital Flight Test, was not performed.<\/p>\n<p>In short, he said that teams used a common industry practice of breaking up prolonged software qualification tests into chunks and tested each of those chunks independently.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-64551\" class=\"size-full wp-image-64551\" src=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit.png\" alt=\"\" width=\"4000\" height=\"2400\" srcset=\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit.png 4000w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit-350x210.png 350w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit-583x350.png 583w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit-768x461.png 768w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit-1920x1152.png 1920w, https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2019\/12\/Starliner-with-DEC-8-edit-1170x702.png 1170w\" sizes=\"(max-width: 4000px) 100vw, 4000px\"><\/p>\n<p id=\"caption-attachment-64551\" class=\"wp-caption-text\">Rendering of aeroskirt jettison as dual-engine Centaur launches Starliner to its initial suborbital trajectory \u2013 via Mack Crawford for NSF\/L2<\/p>\n<p>For Starliner, this resulted in one chunk being the countdown and launch, stopping just after spacecraft separation from the Atlas V\u2019s Centaur upper stage.<\/p>\n<p>The second chunk picked up thereafter and ran through the critical Orbit Insertion burn.<\/p>\n<p>The issue here is that because the countdown\/launch software test chunk stopped before the Orbital Insertion burn, the test was unable to verify that the correct Mission Elapsed Time was pulled by Starliner from the Atlas V rocket.<\/p>\n<p>Had the test actually proceeded through the Orbit Insertion burn, it would have caught the Mission Elapsed Timer issue and permitted teams to correct it on the ground before flight.<\/p>\n<p>(The Mission Elapsed Timer issue was traced to the software pulling the mission time from the Atlas V before terminal count and then not pulling it a second time once the terminal count started\u2026 leading to the timer being off by 11 hours.)<\/p>\n<p>To this end, Boeing will now perform a multi-day launch-to-docking end-to-end software test for missions going forward.<\/p>\n<p>Conversely, the second software issue \u2014 the jet mapping issue that would have resulted in Starliner\u2019s Service Module not being able to fire its thrusters to perform a critical evasive burn to get itself away from the Crew Module after Service Module\/Crew Module separation following deorbit burn \u2014 was not caught because the emulator used to verify this part of the software code was legacy from other Boeing programs, not Starliner, and was not updated with the correct jet mapping software for Starliner.<\/p>\n<p><iframe id=\"twitter-widget-2\" scrolling=\"no\" frameborder=\"0\" allowtransparency=\"true\" allowfullscreen=\"true\" class=\"\" style=\"position: static; visibility: visible; width: 0px; height: 0px; display: block; flex-grow: 1;\" title=\"X Post\" src=\"https:\/\/platform.twitter.com\/embed\/Tweet.html?creatorScreenName=NASASpaceflight&amp;dnt=true&amp;embedId=twitter-widget-2&amp;features=eyJ0ZndfdGltZWxpbmVfbGlzdCI6eyJidWNrZXQiOltdLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X2ZvbGxvd2VyX2NvdW50X3N1bnNldCI6eyJidWNrZXQiOnRydWUsInZlcnNpb24iOm51bGx9LCJ0ZndfdHdlZXRfZWRpdF9iYWNrZW5kIjp7ImJ1Y2tldCI6Im9uIiwidmVyc2lvbiI6bnVsbH0sInRmd19yZWZzcmNfc2Vzc2lvbiI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfZm9zbnJfc29mdF9pbnRlcnZlbnRpb25zX2VuYWJsZWQiOnsiYnVja2V0Ijoib24iLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X21peGVkX21lZGlhXzE1ODk3Ijp7ImJ1Y2tldCI6InRyZWF0bWVudCIsInZlcnNpb24iOm51bGx9LCJ0ZndfZXhwZXJpbWVudHNfY29va2llX2V4cGlyYXRpb24iOnsiYnVja2V0IjoxMjA5NjAwLCJ2ZXJzaW9uIjpudWxsfSwidGZ3X3Nob3dfYmlyZHdhdGNoX3Bpdm90c19lbmFibGVkIjp7ImJ1Y2tldCI6Im9uIiwidmVyc2lvbiI6bnVsbH0sInRmd19kdXBsaWNhdGVfc2NyaWJlc190b19zZXR0aW5ncyI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfdXNlX3Byb2ZpbGVfaW1hZ2Vfc2hhcGVfZW5hYmxlZCI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9LCJ0ZndfdmlkZW9faGxzX2R5bmFtaWNfbWFuaWZlc3RzXzE1MDgyIjp7ImJ1Y2tldCI6InRydWVfYml0cmF0ZSIsInZlcnNpb24iOm51bGx9LCJ0ZndfbGVnYWN5X3RpbWVsaW5lX3N1bnNldCI6eyJidWNrZXQiOnRydWUsInZlcnNpb24iOm51bGx9LCJ0ZndfdHdlZXRfZWRpdF9mcm9udGVuZCI6eyJidWNrZXQiOiJvbiIsInZlcnNpb24iOm51bGx9fQ%3D%3D&amp;frame=false&amp;hideCard=false&amp;hideThread=false&amp;id=1231944998192631809&amp;lang=en&amp;origin=https%3A%2F%2Fwww.nasaspaceflight.com%2F2020%2F02%2Fboeing-update-path-forward-starliner%2F&amp;sessionId=fd0c6158d293baef2631662fd54a47a69a73ce6e&amp;siteScreenName=NASASpaceflight&amp;theme=light&amp;widgetsVersion=6a3ad42b224df%3A1778106238597&amp;width=550px\" data-gtm-yt-inspected-14=\"true\" data-gtm-yt-inspected-21=\"true\" data-tweet-id=\"1231944998192631809\"><\/iframe><\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\" data-twitter-extracted-i1783499082734586997=\"true\">\n<p lang=\"en\" dir=\"ltr\">Training and development day!  Practicing getting to the launch pad from the suit room at Kennedy Space Center.  Riding @BoeingSpace \u2018s Astro Van II with @Astro_Ferg and @AstroDuke . Our backup crew, Barry Wilmore is with us too.  #NASA #Commercial_Crew pic.twitter.com\/poCqruobOY<\/p>\n<p>\u2014 Col. Mike Fincke (@AstroIronMike) February 24, 2020<\/p>\n<\/blockquote>\n<p>The piece of hardware that had the correct Starliner Service Module jet mapping software code \u2014 and was marked to perform this software qualification \u2014 was pulled from the test and sent to New Mexico for the Service Module hot fire engine test instead.<\/p>\n<p>The substituted emulator was then not updated with the correct jet mapping software code.<\/p>\n<p>When the jet mapping software verification test was re-run on the ground with the hardware that had the correct software coding \u2014 done while Orbital Flight Test was preparing for deorbit, reentry, and landing \u2014 the issue was discovered and the correct code was transmitting up to Starliner to avoid what NASA classed as a \u201cLoss Of Vehicle\u201d situation.<\/p>\n<p>Speaking to this, Mr. Mulholland noted that Boeing has and is updating all software testing procedures to not only include checklists for the software but also all of the specific hardware needed for such qualification tests to ensure there is never a hardware\/emulator mismatch again.<\/p>\n<p>\u201cGoing forward, we\u2019re going to define what hardware is needed to make sure it\u2019s there for the qualification testing,\u201d said Mr. Mulholland.<\/p>\n<p>Additionally, Boeing will now perform a full-duration undocking-to-landing integrated software tests to ensure this issue does not repeat on future missions.<\/p>\n<p>Moreover, increased discipline and requirements will be added to all review and approval processes for software testing sequences going forward.<\/p>\n<p>Mr. Mulholland also stated that Starliner teams have begun sharing the results of the software testing lessons learned \u2014 including the identified weak point in \u201cchunk testing\u201d \u2014 to other departments and divisions within Boeing and has also shared the results with outside companies and the space industry as well.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Just over two months after the truncated Orbital Flight Test of their Starliner crew capsule, Boeing officials have provided an in-depth overview of the issues faced on the flight. The update, held on Friday, 28 February, also provided information on the path forward for Starliner, including the on-going software audit, closing process escapes and software [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":37701,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[670,524,1306],"class_list":["post-37700","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-boeing","tag-commercial-crew","tag-starliner"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/37700"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=37700"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/37700\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/37701"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=37700"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=37700"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=37700"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}