Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have an unclarity with this situation.

How much of him being a hero is a coincidence? Did he refuse to sign the previous launches? Did NASA have reasons to believe that the launch could be successful? How much of a role does probability play here. I mean if someone literally tells you something isn't safe, especially the person who made it, you can't tell him it will work. There is somekind of bias here.



Of course there's bias. If he had rubber-stamped it there would be no story to tell.

His decision would have been questioned after the fact, he would defer to information from levels below, and this would recurse until responsibility had dissipated beyond and any personal attribution. The same pattern happens in every org, every day (to decisions of mostly lesser affect).

The key point—at least from my read—were the follow up actions to highlight where information was intentionally ignored, prevent that dispersion of responsibility, and ensure it didn't happen again.


> the follow up actions to highlight where information was intentionally ignored, prevent that dispersion of responsibility, and ensure it didn't happen again.

Unfortunately, while that specific problem did not happen again, the general cultural changes that were supposed to happen had been lost 15 years later. The loss of Columbia in 2003 was due to the same kind of poor decision making and problem solving process that was involved in the loss of Challenger.


The article is a bit weird, he refused to sign a form inside a private company. But the private company presented a signed form to NASA (signed by higher-up’s).

So NASA probably didn’t look closely into the engineering, in particular when launch is tomorrow.


> NASA probably didn’t look closely into the engineering

Yes, they did. NASA had been told by Thiokol the previous summer about the O-ring issue and that it could cause the loss of the Shuttle--and ignored the recommendation to ground the Shuttle until the issue was fixed. The night before the launch there was a conference call where the Thiokol engineers recommended not launching. Detailed engineering information was presented on that call--and it was information that had already been presented to NASA previously. NASA knew the engineering information and recommendation. They chose to ignore it.


I got to hear him recount the story, and yeah the article is weird.

The form he talked about was one that, if not signed, would mean that the launch would not happen. I can't remember if it was an internal form or not, but it doesn't really matter in that context.

Since NASA needed that form signed, he was under intense pressure to actually sign it both by NASA and his company. Someone else from the company not on site signed it.


The challenger disaster was a case study when I was in school: The important lesson is about human psychology, and why it's important to not speak up when something is dangerous.

Basically, the "powers that be" wanted the launch and overruled the concerns of the engineers. They forced the launch against better judgement.

(Think of the, "Oh, that nerd is always complaining, I'm going to ignore them because they aren't important," attitude.)


> How much of him being a hero is a coincidence?

None. He knew the right thing to do and did it despite extreme pressure.

> Did he refuse to sign the previous launches?

I don't know about him personally, but Thiokol, at the behest of McDonald and other engineers, had sent a formal letter to NASA the previous summer warning about the O-ring issue and stating explicitly that an O-ring failure could lead to loss of vehicle and loss of life.

> Did NASA have reasons to believe that the launch could be successful?

Not valid ones, no. The launch took place because managers, at both NASA and Thiokol, ignored valid engineering recommendations. But more than that, NASA had already been ignoring, since the previous summer, valid engineering recommendations to ground the Shuttle until the O-ring issue was understood and fixed.


To be completely honest I think you are somewhat naive. I have seen organizations push through decisions, which were obviously bad, in fact nearly everyone on the lower levels agreed that the goal of the decision was unachievable. But of course that didn't stop the organization.

> I mean if someone literally tells you something isn't safe, especially the person who made it, you can't tell him it will work.

You literally can.


Given that the other risk he cited, of ice damaging the heat shield tiles, is exactly what led to the loss of Columbia, I'd say he has an excellent grasp of the risks.


Something can work and not be safe at the same time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: