{"id":43507,"date":"2025-12-24T00:51:24","date_gmt":"2025-12-23T16:51:24","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/safety-panel-says-nasa-should-have-taken-starliner-incident-more-seriously\/"},"modified":"2025-12-24T00:51:24","modified_gmt":"2025-12-23T16:51:24","slug":"safety-panel-says-nasa-should-have-taken-starliner-incident-more-seriously","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/safety-panel-says-nasa-should-have-taken-starliner-incident-more-seriously\/","title":{"rendered":"Safety panel says NASA should have taken Starliner incident more seriously"},"content":{"rendered":"

For the better part of two months last year, most of us had no idea how serious the problems were with Boeing\u2019s Starliner spacecraft docked at the International Space Station. A safety advisory panel found this uncertainty also filtered through NASA\u2019s workforce.<\/p>\n

On its first Crew Test Flight, Boeing\u2019s Starliner delivered NASA astronauts Butch Wilmore and Suni Williams to the space station in June 2024. They were the first people to fly to space on a Starliner spacecraft after more than a decade of development and setbacks. The astronauts expected to stay at the ISS for one or two weeks, but ended up remaining in orbit for nine months after NASA officials determined it was too risky to return them to Earth in the Boeing-built crew capsule. Wilmore and Williams flew back to Earth last March on a SpaceX Dragon spacecraft.<\/p>\n

The Starliner capsule was beset by problems with its maneuvering thrusters and pernicious helium leaks on its 27-hour trip from the launch pad to the ISS. For a short time, Starliner commander Wilmore lost his ability to control the movements of his spacecraft as it moved in for docking at the station in June 2024. Engineers determined that some of the thrusters were overheating and eventually recovered most of their function, allowing Starliner to dock with the ISS.<\/p>\n

\u201cThere was concern in real time that without recovery of some control, neither a docking nor a deorbit could be controllable, and that could have led to loss of vehicle and crew,\u201d said Charlie Precourt, a former space shuttle commander and now a member of NASA\u2019s Aerospace Safety Advisory Panel (ASAP). \u201cGiven the severity of this anomaly, NASA wisely and correctly used the safe haven of the ISS to conduct testing and engineering on the ground to analyze the various recovery options.\u201d<\/p>\n

Confusion and uncertainty<\/h2>\n

Throughout that summer, managers from NASA and Boeing repeatedly stated that the spacecraft was safe to bring Wilmore and Williams home if the station needed to be evacuated in an emergency. But officials on the ground ordered extensive testing to understand the root of the problems. Buried behind the headlines, there was a real chance NASA managers would decide\u2014as they ultimately did\u2014not to put astronauts on Boeing\u2019s crew capsule when it was time to depart the ISS.<\/p>\n

,<\/p>\n

Precourt said officials from Boeing and NASA\u2019s Commercial Crew Program, which oversees the agency\u2019s Starliner contract, \u201cwere signaling return on Starliner was the expected outcome\u201d for Wilmore and Williams. \u201cOther NASA entities in the decision process were not in concurrence,\u201d Precourt continued. \u201cAs a result, there was significant stress on the workforce, with many believing the sole objective was to determine a means by which we could enable crew return on the Starliner.\u201d<\/p>\n

It would have been better, Precourt and other panel members said Friday, if NASA made a formal declaration of an in-flight \u201cmishap\u201d or \u201chigh visibility close call\u201d soon after the Starliner spacecraft\u2019s troubled rendezvous with the ISS. Such a declaration would have elevated responsibility for the investigation to NASA\u2019s safety office.<\/p>\n

\u201cThe ASAP finding is the lack of a declared in-flight mishap or high visibility close call contributed to an extensive, excessive \u2026 period of time where risk ownership and the decision-making authority were unclear,\u201d Precourt said.<\/p>\n

\n

\"\"<\/p>\n

Boeing\u2019s Starliner spacecraft backs away from the International Space Station on September 6, 2024, without its crew.<\/p>\n

Credit:
\n NASA<\/p>\n<\/figure>\n

NASA procedural requirements stipulate that the agency should declare a mishap in the event of an injury, destruction of property, or mission failure. A high visibility close call is an incident senior NASA leaders \u201cjudge to possess a high degree of programmatic impact or public, media, or political interest, including, but are not limited to, mishaps and close calls that impact flight hardware, flight software, or completion of critical mission milestones.\u201d<\/p>\n

This is familiar territory for the Starliner program. NASA declared a high-visibility close call following Starliner\u2019s first unpiloted test flight after it failed to reach the space station in 2019. Before then, NASA used the designation after the near-drowning of astronaut Luca Parmitano on a spacewalk in 2013.<\/p>\n

The designation formally initiates an internal process within NASA\u2019s safety office to launch an investigation and serves as a way to document and retain lessons learned for future programs. \u201cProcedurally, investigation reports are tied to anomaly declaration, so they gain an official status in NASA records,\u201d Precourt said. \u201cCertainly, this particular anomaly deserves to be right up front and center for quite some time.\u201d<\/p>\n

,<\/p>\n

Invoking the designation also ensures an independent investigation detached from the teams involved in the incident itself, according to retired Air Force Lt. Gen. Susan Helms, chair of the safety panel. \u201cWe just, I think, are advocates of safety investigation best practices, and that clearly is one of the top best practices,\u201d Helms said.<\/p>\n

Another member of the safety panel, Mark Sirangelo, said NASA should formally declare mishaps and close calls as soon as possible. \u201cIt allows for the investigative team to be starting to be formed a lot sooner, which makes them more effective and makes the results quicker for everyone,\u201d Sirangelo said.<\/p>\n

In the case of last year\u2019s Starliner test flight, NASA\u2019s decision not to declare a mishap or close call created confusion within the agency, safety officials said.<\/p>\n

A few weeks into the Starliner test flight last year, the manager of NASA\u2019s Commercial Crew Program, Steve Stich, told reporters the agency\u2019s plan was \u201cto continue to return [the astronauts] on Starliner and return them home at the right time.\u201d Mark Nappi, then Boeing\u2019s Starliner program manager, regularly appeared to downplay the seriousness of the thruster issues during press conferences throughout Starliner\u2019s nearly three-month mission.<\/p>\n

\u201cSpecifically, there\u2019s a significant difference, philosophically, between we will work toward proving the Starliner is safe for crew return, versus a philosophy of Starliner is no-go for return, and the primary path is on an alternate vehicle, such as Dragon or Soyuz, unless and until we learn how to ensure the on-orbit failures won\u2019t recur on entry with the Starliner,\u201d Precourt said.<\/p>\n

\u201cThe latter would have been the more appropriate direction,\u201d he said. \u201cHowever, there were many stakeholders that believed the direction was the former approach. This ambiguity continued throughout the summer months, while engineers and managers pursued multiple test protocols in the Starliner propulsion systems, undoubtedly affecting the workforce.\u201d<\/p>\n

After months of testing and analysis, NASA officials were unsure if the thruster problems would recur on Starliner\u2019s flight home. They decided in August 2024 to return the spacecraft to the ground without the astronauts, and the capsule safely landed in New Mexico the following month. The next Starliner flight will carry only cargo to the ISS.<\/p>\n

The safety panel recommended that NASA review its criteria and processes to ensure the language is \u201cunambiguous\u201d in requiring the agency to declare an in-flight mishap or a high-visibility close call for any event involving NASA personnel \u201cthat leads to an impact on crew or spacecraft safety.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"

For the better part of two months last year, most of us had no idea how serious the problems were with Boeing\u2019s Starliner spacecraft docked at the International Space Station. A safety advisory panel found this uncertainty also filtered through NASA\u2019s workforce. On its first Crew Test Flight, Boeing\u2019s Starliner delivered NASA astronauts Butch Wilmore […]<\/p>\n","protected":false},"author":1,"featured_media":43508,"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":[],"class_list":["post-43507","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/43507"}],"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=43507"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/43507\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/43508"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=43507"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=43507"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=43507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}