Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Saturday July 27, @10:49PM   Printer-friendly

Arthur T Knackerbracket has processed the following story:

Twenty-five years ago, Space Shuttle Columbia launched the Chandra X-ray observatory and nearly ended in catastrophe. As the then-ascent flight director John Shannon observed: "Yikes. We don't need another one of those."

Space Shuttle Columbia was launched from Kennedy Space Center's LC-39B on the morning of July 23, 1999. Two previous launch attempts, on July 20 and 22, were scrubbed because of a faulty sensor and bad weather.

The launch was third time lucky in more ways than one.

Unknown to the Shuttle's crew and flight controllers, Columbia contained several flaws – as do all vehicles – some of which were about to make their presence felt during the launch phase of the mission. A bit of wiring within the payload bay had chafed against a burred screw head, a single gold-plated pin was slightly loose in a deactivated Liquid Oxygen (LOX) post in the main injector of the right engine, and the main center engine had a slight bias in pressure measurements on its B channel that would only show when the engine reached full throttle.

Oh, and there was a slightly loose connection on a hydraulic pressure sensor on the right solid rocket booster (SRB).

The team was blissfully unaware of any of this.

The countdown progressed normally, and by T-3 seconds, all the engines were up and running and operating at 100 percent power.

A former Shuttle flight director, Wayne Hale, described the subsequent events: "Exactly when it happened is not clear, but on the right engine, the gold-plated pin from LOX post 32 in row 13 came shooting out. Just like a bullet, it went through the narrow part of the converging nozzle and flew out into the nozzle extension."

This could have been disastrous – the LOX post had been pinned for a reason and could have failed and let LOX flow into the engine, resulting in explosion. "Failure of the LOX post was considered a CRIT 1 failure – loss of vehicle and crew 'promptly,'" Hale wrote.

Or the nozzle extension could have failed. Another CRIT 1 failure. According to Hale, it had been calculated that if five adjacent cooling tubes in the nozzle extension were split, there would not be enough cooling and a burn through would occur. As it was, only three tubes were breached as the bullet-shaped LOX pin hit the side of the right nozzle extension.

The immediate effect was a hydrogen leak from the nozzle. It was not huge, but enough for the engine's controller to increase the oxidizer flow, increasing the turbine temperature approximately halfway to the point where an engine would be automatically shut down.

It took the booster officer and his team around a minute to realize something was amiss with the engine – not for want of attention but because they had their hands full with another problem. Remember that loose SRB connection? It resulted in an alarm on the console. There were two hydraulic systems on each SRB. If both failed, the SRB would not be steerable. Another sudden CRIT 1 failure.

And then there was that chafed wire and the potential short circuit. As the Shuttle lifted off, the commander, Eileen Collins, called "Fuel Cell PH."

Hale wrote that the call indicated that one of the fuel cells might be failing: "It's the Kaboom Case, Flight." However, although the master alarm onboard Columbia was wailing, the fuel cell had not actually failed. Instead, one of the AC buses had shorted out. The affected part of the circuit had been automatically shut down, and the erroneous alarm was caused by suddenly unpowered instrumentation.

One effect of the short was a loss of power to the Space Shuttle Main Engine (SSME) controllers.

According to Hale: "The A computer on the Center SSME lost power, never to be recovered. The B computer (DCU B) immediately took control and the engine ran on normally."

Except it wasn't running normally. The A channel pressure transducer dropped offline, meaning that the B computer only had the B transducer, which was reading slightly high – in this case, 12 psi high. Automatically, the B computer throttled back the center engine. Not hugely, but enough to partially offset the shortfall of LOX caused by the nozzle leak on the right engine.

The engine had lost its B computer, but the A computer continued working, and the engine, with the leak, carried on running.

"How lucky we were," Hale said. "Instead of being 200 or more fps short at MECO, possibly leading to an abort landing or requiring two tons of OMS propellant to make up, we wound up being only 15 fps short, well within the capability of the OMS budget."

The mission itself was successful, and the Chandra X-ray observatory, which is now on NASA's budget chopping block, was deployed. Columbia's next mission would be STS-109 to service the Hubble Space Telescope.

As for the issues seen during the launch, NASA noted that the wiring problem was likely caused by workers "inadvertently stepping on it," and the problem had likely been there since Columbia was manufactured. And the pin? Apparently, it had never passed any acceptance testing. STS-93 was the last flight of that generation of SSMEs.

"The next upgrade to the SSMEs was to build a more robust channel wall nozzle extension," Hale said. "The shuttle program ended before that was done."

While Shannon's "yikes" will go down in spaceflight history, we'll leave the last word to Hale.

"Be prepared. Spacecraft are complex and can fail in complex ways. Never, ever let your guard down. Practice for disaster all the time.

"And remember: Murphy does not play by the rules."


Original Submission

 
This discussion was created by janrinok (52) for logged-in users only, but now has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
  • (Score: 2) by aafcac on Saturday July 27, @11:25PM (1 child)

    by aafcac (17646) on Saturday July 27, @11:25PM (#1365948)

    This happened years later. Iirc it was 2003.

    • (Score: 2) by aafcac on Sunday July 28, @12:34AM

      by aafcac (17646) on Sunday July 28, @12:34AM (#1365952)

      I see that I misread that. It's rather unfortunate of a confidence to be the same shuttle.

  • (Score: 4, Informative) by janrinok on Sunday July 28, @03:12AM (6 children)

    by janrinok (52) Subscriber Badge on Sunday July 28, @03:12AM (#1365964) Journal

    This story was published on Fri 26 Jul 2024 09:33 UTC. It is not old news. It has been released by NASA to help explain the current problems being experienced by the crew currently waiting on the ISS to return to earth.

    People have been complacent and now believe that space travel is routine and no longer includes any risks. This story is intended I presume to illustrate that such a perception is wrong. It is offered under the random topic - we are not trying to compete with various news agencies to provide up-to-minute news. That is not the purpose of this site.

    --
    I am not interested in knowing who people are or where they live. My interest starts and stops at our servers.
    • (Score: 5, Insightful) by Reziac on Sunday July 28, @05:18AM (3 children)

      by Reziac (2489) on Sunday July 28, @05:18AM (#1365974) Homepage

      I don't care if it's old news or not, I hadn't heard about it, so interesting.

      And I wonder about needless complexity, considering what private outfits are managing with far fewer resources.

      --
      And there is no Alkibiades to come back and save us from ourselves.
      • (Score: 3, Interesting) by PiMuNu on Sunday July 28, @08:32AM (2 children)

        by PiMuNu (3823) on Sunday July 28, @08:32AM (#1365979)

        It's interesting to juxtapose also against this falcon9 failure:

        https://www.theregister.com/2024/07/26/spacex_falcon_9_flight/ [theregister.com]

        If I understand correctly, this is same rocket design that SpaceX uses to launch humans - thus with bad luck this failure mode could have led to cooked astronauts.

        • (Score: 3, Interesting) by khallow on Monday July 29, @02:26AM (1 child)

          by khallow (3766) Subscriber Badge on Monday July 29, @02:26AM (#1366089) Journal

          If I understand correctly, this is same rocket design that SpaceX uses to launch humans - thus with bad luck this failure mode could have led to cooked astronauts.

          In the above story there is also a big reliability enhancement. Because the Falcon 9 gets used for so many unmanned flights, failure modes that NASA would miss, until they killed someone, can be explored in unmanned flights that don't kill someone. Bad luck still happens, but odds are much better per flight.

    • (Score: 1, Insightful) by Anonymous Coward on Monday July 29, @01:37PM (1 child)

      by Anonymous Coward on Monday July 29, @01:37PM (#1366157)
      Space travel is routine when people rarely clap on the take off and landings, and instead complain about the inflight entertainment and/or food... 😉
      • (Score: 2) by janrinok on Monday July 29, @02:50PM

        by janrinok (52) Subscriber Badge on Monday July 29, @02:50PM (#1366170) Journal

        That seems to be a US thing - people in Europe do not usually clap when aircraft take-off or land. That's what aircraft are supposed to do. Here they tend to complain when aircraft don't take off or land on time, or even not take off at all.

        Do Americans also applaud when trains or buses operate on time?

        But your point is well taken. :)

        --
        I am not interested in knowing who people are or where they live. My interest starts and stops at our servers.
  • (Score: 2) by RedGreen on Sunday July 28, @12:16PM (3 children)

    by RedGreen (888) on Sunday July 28, @12:16PM (#1365994)

    So what is news about that, almost thirty ago they did due to their incompetence. Then years later another seven dead from the same incompetence the shuttles were always a crap shoot on their launch. With only luck the design flaws did not kill everyone who went up in one every time they was sent up. Now they try so whatever washing it would be called to try and gloss over yet another episode of incompetence trapping some more people on the international space station. This oh space is so hard narrative they try to use to justify this latest bad decision of theirs is just plain disgusting. They had the choice of sending a well tested and proven module instead they rolled the dice with people lives one more time. Except they have not killed anyone off with this blunder, yet.

    --
    "I modded down, down, down, and the flames went higher." -- Sven Olsen
    • (Score: 5, Insightful) by janrinok on Sunday July 28, @03:01PM (1 child)

      by janrinok (52) Subscriber Badge on Sunday July 28, @03:01PM (#1366000) Journal

      Why does it have to be news?

      Several people have commented that they enjoyed reading it. It was posted under the 'Random' topic so the connection is not quite so strong to current STEM.

      We cannot produce discussions that will entertain everyone every time. If you wish to provide a more interesting topic for discussion then please do so.

      --
      I am not interested in knowing who people are or where they live. My interest starts and stops at our servers.
      • (Score: 3, Insightful) by RedGreen on Sunday July 28, @03:21PM

        by RedGreen (888) on Sunday July 28, @03:21PM (#1366003)

        "We cannot produce discussions that will entertain everyone every time."

        I commented on the sympathy they go for with the article and the how they are so hard done by slant, like everyone these days it seems. They knew exactly what they were doing with the risks they took launching that garbage before the problems were sorted with the module. Now they get to live with the consequences. If you do not like my comments on articles you are free to read others.

        --
        "I modded down, down, down, and the flames went higher." -- Sven Olsen
    • (Score: 3, Interesting) by JoeMerchant on Monday July 29, @02:37AM

      by JoeMerchant (3937) on Monday July 29, @02:37AM (#1366090)

      The news is that they have been effectively suppressing this story for decades. NASA is portrayed as a highly transparent agency, but stories like this serve to calibrate that perception, just like the mad dash to the Colombia wreckage to find "classified" materials that may have survived the crash. "Stay away!!! It might be highly TOXIC!!! And report it immediately if you suspect you found anything. Penalties for non-compliance are severe."

      --
      🌻🌻 [google.com]
(1)