Why was Gemini VIII terminated after recovering from the OAMS thruster failure?Was quarantine continued after Apollo 11?Why did the rendezvous attempt fail on Gemini 4?What was mylar used for on the Apollo Command Module space craft? Why is it gold after returning from space?Why didn't Gemini, Apollo or STS use solar panels?Why were ejection seats used in Project Gemini instead of a tower escape system?Where can I find flight manuals (not familiarization manuals) from Project Gemini?Was the Saturn V only going at 1.1km/s after the first stage?How were the Flight Journals of the Apollo missions originally transcribed/recorded?Why did rendezvous on Gemini 4 fail so badly?Agena docking and RCS Brakes in First Man

Bash Read: Reading comma separated list, last element is missed

On a piano, are the effects of holding notes and the sustain pedal the same for a single chord?

Find the 3D region containing the origin bounded by given planes

How to convince boss to spend notice period on documentation instead of new projects

Better than Rembrandt

How to fix "webpack Dev Server Invalid Options" in Vuejs

What does this 'x' mean on the stem of the voice's note, above the notehead?

How does the probability of events change if an event does not occur

Parse a C++14 integer literal

Can a Warforged have a ranged weapon affixed to them like an armblade?

Can 2 light bulbs of 120V in series be used on 230V AC?

Hotel booking: Why is Agoda much cheaper than booking.com?

Behavior of __LINE__ when used in a macro

Was Tyrion always a poor strategist?

Managing heat dissipation in a magic wand

How could the B-29 bomber back up under its own power?

Why were early aviators' trousers flared at the thigh?

How can sister protect herself from impulse purchases with a credit card?

Have I found a major security issue with login

Can a problematic AL DM/organizer prevent me from running a separatate AL-legal game at the same store?

What should I wear to go and sign an employment contract?

Is being an extrovert a necessary condition to be a manager?

Have the writers and actors of Game Of Thrones responded to its poor reception?

Precedent for disabled Kings



Why was Gemini VIII terminated after recovering from the OAMS thruster failure?


Was quarantine continued after Apollo 11?Why did the rendezvous attempt fail on Gemini 4?What was mylar used for on the Apollo Command Module space craft? Why is it gold after returning from space?Why didn't Gemini, Apollo or STS use solar panels?Why were ejection seats used in Project Gemini instead of a tower escape system?Where can I find flight manuals (not familiarization manuals) from Project Gemini?Was the Saturn V only going at 1.1km/s after the first stage?How were the Flight Journals of the Apollo missions originally transcribed/recorded?Why did rendezvous on Gemini 4 fail so badly?Agena docking and RCS Brakes in First Man













10












$begingroup$


This NASA source states that the mission was terminated after Neil Armstrong used 75% of the RCS propellent to cancel the rotation from the OAMS thruster failure. If the mission had enough RCS left to have a safe re-entry and policy was to not use the RCS until the end of the mission anyways, why did they not attempt to dock again and complete the mission?



As a second question, if they had not undocked from Agena and had used the RCS to recover anyways, would they have still terminated the mission?










share|improve this question









$endgroup$
















    10












    $begingroup$


    This NASA source states that the mission was terminated after Neil Armstrong used 75% of the RCS propellent to cancel the rotation from the OAMS thruster failure. If the mission had enough RCS left to have a safe re-entry and policy was to not use the RCS until the end of the mission anyways, why did they not attempt to dock again and complete the mission?



    As a second question, if they had not undocked from Agena and had used the RCS to recover anyways, would they have still terminated the mission?










    share|improve this question









    $endgroup$














      10












      10








      10





      $begingroup$


      This NASA source states that the mission was terminated after Neil Armstrong used 75% of the RCS propellent to cancel the rotation from the OAMS thruster failure. If the mission had enough RCS left to have a safe re-entry and policy was to not use the RCS until the end of the mission anyways, why did they not attempt to dock again and complete the mission?



      As a second question, if they had not undocked from Agena and had used the RCS to recover anyways, would they have still terminated the mission?










      share|improve this question









      $endgroup$




      This NASA source states that the mission was terminated after Neil Armstrong used 75% of the RCS propellent to cancel the rotation from the OAMS thruster failure. If the mission had enough RCS left to have a safe re-entry and policy was to not use the RCS until the end of the mission anyways, why did they not attempt to dock again and complete the mission?



      As a second question, if they had not undocked from Agena and had used the RCS to recover anyways, would they have still terminated the mission?







      crewed-spaceflight apollo-program project-gemini






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 6 at 17:05









      kikjezrouskikjezrous

      1535




      1535




















          1 Answer
          1






          active

          oldest

          votes


















          19












          $begingroup$

          I haven't been able to find the Gemini rules online. But we can infer what they stated based on comments in the Gemini VIII post flight report.




          MCC-H made the decision for early mission termination. This
          decision was based on data which showed RCS propellant remaining in
          both rings to be less than half the amount loaded. Also, both rings
          of the RCS had been activated and significant propellant had been
          used. Mission rules required termina­tion of the mission under
          these conditions.




          So the situation was:



          • Primary attitude control system failed and unusable.

          • Backup attitude control systems have been activated early and
            significant propellant has been used.

          This is what we would have called in Shuttle a "zero fault tolerant" situation. In other words, if anything else bad had happened to the RCS, the crew would have died. When the mission rules were written, they must have stated that this type of situation called for early mission termination.



          The truly interesting thing about this situation is that the flight director followed the mission rules, terminated the mission early, and it ended his career as a flight director.



          As Wayne Hale writes:




          NASA management found out about the situation after the crew was in
          the ocean. According to the legend, Hodge did not take the time to
          pick up the phone and call the Program Manager, the Center Director,
          or even his boss, the Chief of the Flight Director office. The
          situation was stable, and even though waiting around was not
          necessarily a good thing, there was no reason that a couple of hours
          delay would have significantly increased the crew risk. Upper
          management was severely out of sorts with Blue Flight because they
          were not called in to review a critical action that really could have
          waited, despite what the Flight Rules called for.



          Bottom line: John Hodge never served as Flight Director in Mission
          Control again.




          Which is why we sarcastically referred to the Flight Rules as "Flight Guidelines".



          There are only two ways to mess up in Mission Control: following the Flight Rules, or not following the Flight Rules.



          Update: Hale goes on to say




          But that is not the point of the fable. The moral of the story for all
          rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time
          that a critical action can reasonably be delayed for even a few
          minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight
          Rules say. After all, it’s just your career on the line.




          Note: the linked Post Flight Mission Report is a terrific reference on this mission. Highly recommended.






          share|improve this answer











          $endgroup$








          • 14




            $begingroup$
            Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
            $endgroup$
            – Saiboogu
            May 6 at 17:27






          • 3




            $begingroup$
            Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
            $endgroup$
            – Organic Marble
            May 6 at 17:29






          • 1




            $begingroup$
            Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
            $endgroup$
            – Digger
            May 7 at 15:57







          • 1




            $begingroup$
            Brilliant and comprehensive answer. Thank you so much!
            $endgroup$
            – kikjezrous
            May 7 at 19:30











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "508"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f35975%2fwhy-was-gemini-viii-terminated-after-recovering-from-the-oams-thruster-failure%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          19












          $begingroup$

          I haven't been able to find the Gemini rules online. But we can infer what they stated based on comments in the Gemini VIII post flight report.




          MCC-H made the decision for early mission termination. This
          decision was based on data which showed RCS propellant remaining in
          both rings to be less than half the amount loaded. Also, both rings
          of the RCS had been activated and significant propellant had been
          used. Mission rules required termina­tion of the mission under
          these conditions.




          So the situation was:



          • Primary attitude control system failed and unusable.

          • Backup attitude control systems have been activated early and
            significant propellant has been used.

          This is what we would have called in Shuttle a "zero fault tolerant" situation. In other words, if anything else bad had happened to the RCS, the crew would have died. When the mission rules were written, they must have stated that this type of situation called for early mission termination.



          The truly interesting thing about this situation is that the flight director followed the mission rules, terminated the mission early, and it ended his career as a flight director.



          As Wayne Hale writes:




          NASA management found out about the situation after the crew was in
          the ocean. According to the legend, Hodge did not take the time to
          pick up the phone and call the Program Manager, the Center Director,
          or even his boss, the Chief of the Flight Director office. The
          situation was stable, and even though waiting around was not
          necessarily a good thing, there was no reason that a couple of hours
          delay would have significantly increased the crew risk. Upper
          management was severely out of sorts with Blue Flight because they
          were not called in to review a critical action that really could have
          waited, despite what the Flight Rules called for.



          Bottom line: John Hodge never served as Flight Director in Mission
          Control again.




          Which is why we sarcastically referred to the Flight Rules as "Flight Guidelines".



          There are only two ways to mess up in Mission Control: following the Flight Rules, or not following the Flight Rules.



          Update: Hale goes on to say




          But that is not the point of the fable. The moral of the story for all
          rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time
          that a critical action can reasonably be delayed for even a few
          minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight
          Rules say. After all, it’s just your career on the line.




          Note: the linked Post Flight Mission Report is a terrific reference on this mission. Highly recommended.






          share|improve this answer











          $endgroup$








          • 14




            $begingroup$
            Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
            $endgroup$
            – Saiboogu
            May 6 at 17:27






          • 3




            $begingroup$
            Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
            $endgroup$
            – Organic Marble
            May 6 at 17:29






          • 1




            $begingroup$
            Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
            $endgroup$
            – Digger
            May 7 at 15:57







          • 1




            $begingroup$
            Brilliant and comprehensive answer. Thank you so much!
            $endgroup$
            – kikjezrous
            May 7 at 19:30















          19












          $begingroup$

          I haven't been able to find the Gemini rules online. But we can infer what they stated based on comments in the Gemini VIII post flight report.




          MCC-H made the decision for early mission termination. This
          decision was based on data which showed RCS propellant remaining in
          both rings to be less than half the amount loaded. Also, both rings
          of the RCS had been activated and significant propellant had been
          used. Mission rules required termina­tion of the mission under
          these conditions.




          So the situation was:



          • Primary attitude control system failed and unusable.

          • Backup attitude control systems have been activated early and
            significant propellant has been used.

          This is what we would have called in Shuttle a "zero fault tolerant" situation. In other words, if anything else bad had happened to the RCS, the crew would have died. When the mission rules were written, they must have stated that this type of situation called for early mission termination.



          The truly interesting thing about this situation is that the flight director followed the mission rules, terminated the mission early, and it ended his career as a flight director.



          As Wayne Hale writes:




          NASA management found out about the situation after the crew was in
          the ocean. According to the legend, Hodge did not take the time to
          pick up the phone and call the Program Manager, the Center Director,
          or even his boss, the Chief of the Flight Director office. The
          situation was stable, and even though waiting around was not
          necessarily a good thing, there was no reason that a couple of hours
          delay would have significantly increased the crew risk. Upper
          management was severely out of sorts with Blue Flight because they
          were not called in to review a critical action that really could have
          waited, despite what the Flight Rules called for.



          Bottom line: John Hodge never served as Flight Director in Mission
          Control again.




          Which is why we sarcastically referred to the Flight Rules as "Flight Guidelines".



          There are only two ways to mess up in Mission Control: following the Flight Rules, or not following the Flight Rules.



          Update: Hale goes on to say




          But that is not the point of the fable. The moral of the story for all
          rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time
          that a critical action can reasonably be delayed for even a few
          minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight
          Rules say. After all, it’s just your career on the line.




          Note: the linked Post Flight Mission Report is a terrific reference on this mission. Highly recommended.






          share|improve this answer











          $endgroup$








          • 14




            $begingroup$
            Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
            $endgroup$
            – Saiboogu
            May 6 at 17:27






          • 3




            $begingroup$
            Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
            $endgroup$
            – Organic Marble
            May 6 at 17:29






          • 1




            $begingroup$
            Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
            $endgroup$
            – Digger
            May 7 at 15:57







          • 1




            $begingroup$
            Brilliant and comprehensive answer. Thank you so much!
            $endgroup$
            – kikjezrous
            May 7 at 19:30













          19












          19








          19





          $begingroup$

          I haven't been able to find the Gemini rules online. But we can infer what they stated based on comments in the Gemini VIII post flight report.




          MCC-H made the decision for early mission termination. This
          decision was based on data which showed RCS propellant remaining in
          both rings to be less than half the amount loaded. Also, both rings
          of the RCS had been activated and significant propellant had been
          used. Mission rules required termina­tion of the mission under
          these conditions.




          So the situation was:



          • Primary attitude control system failed and unusable.

          • Backup attitude control systems have been activated early and
            significant propellant has been used.

          This is what we would have called in Shuttle a "zero fault tolerant" situation. In other words, if anything else bad had happened to the RCS, the crew would have died. When the mission rules were written, they must have stated that this type of situation called for early mission termination.



          The truly interesting thing about this situation is that the flight director followed the mission rules, terminated the mission early, and it ended his career as a flight director.



          As Wayne Hale writes:




          NASA management found out about the situation after the crew was in
          the ocean. According to the legend, Hodge did not take the time to
          pick up the phone and call the Program Manager, the Center Director,
          or even his boss, the Chief of the Flight Director office. The
          situation was stable, and even though waiting around was not
          necessarily a good thing, there was no reason that a couple of hours
          delay would have significantly increased the crew risk. Upper
          management was severely out of sorts with Blue Flight because they
          were not called in to review a critical action that really could have
          waited, despite what the Flight Rules called for.



          Bottom line: John Hodge never served as Flight Director in Mission
          Control again.




          Which is why we sarcastically referred to the Flight Rules as "Flight Guidelines".



          There are only two ways to mess up in Mission Control: following the Flight Rules, or not following the Flight Rules.



          Update: Hale goes on to say




          But that is not the point of the fable. The moral of the story for all
          rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time
          that a critical action can reasonably be delayed for even a few
          minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight
          Rules say. After all, it’s just your career on the line.




          Note: the linked Post Flight Mission Report is a terrific reference on this mission. Highly recommended.






          share|improve this answer











          $endgroup$



          I haven't been able to find the Gemini rules online. But we can infer what they stated based on comments in the Gemini VIII post flight report.




          MCC-H made the decision for early mission termination. This
          decision was based on data which showed RCS propellant remaining in
          both rings to be less than half the amount loaded. Also, both rings
          of the RCS had been activated and significant propellant had been
          used. Mission rules required termina­tion of the mission under
          these conditions.




          So the situation was:



          • Primary attitude control system failed and unusable.

          • Backup attitude control systems have been activated early and
            significant propellant has been used.

          This is what we would have called in Shuttle a "zero fault tolerant" situation. In other words, if anything else bad had happened to the RCS, the crew would have died. When the mission rules were written, they must have stated that this type of situation called for early mission termination.



          The truly interesting thing about this situation is that the flight director followed the mission rules, terminated the mission early, and it ended his career as a flight director.



          As Wayne Hale writes:




          NASA management found out about the situation after the crew was in
          the ocean. According to the legend, Hodge did not take the time to
          pick up the phone and call the Program Manager, the Center Director,
          or even his boss, the Chief of the Flight Director office. The
          situation was stable, and even though waiting around was not
          necessarily a good thing, there was no reason that a couple of hours
          delay would have significantly increased the crew risk. Upper
          management was severely out of sorts with Blue Flight because they
          were not called in to review a critical action that really could have
          waited, despite what the Flight Rules called for.



          Bottom line: John Hodge never served as Flight Director in Mission
          Control again.




          Which is why we sarcastically referred to the Flight Rules as "Flight Guidelines".



          There are only two ways to mess up in Mission Control: following the Flight Rules, or not following the Flight Rules.



          Update: Hale goes on to say




          But that is not the point of the fable. The moral of the story for all
          rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time
          that a critical action can reasonably be delayed for even a few
          minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight
          Rules say. After all, it’s just your career on the line.




          Note: the linked Post Flight Mission Report is a terrific reference on this mission. Highly recommended.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 6 at 21:51

























          answered May 6 at 17:25









          Organic MarbleOrganic Marble

          63.8k4173268




          63.8k4173268







          • 14




            $begingroup$
            Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
            $endgroup$
            – Saiboogu
            May 6 at 17:27






          • 3




            $begingroup$
            Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
            $endgroup$
            – Organic Marble
            May 6 at 17:29






          • 1




            $begingroup$
            Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
            $endgroup$
            – Digger
            May 7 at 15:57







          • 1




            $begingroup$
            Brilliant and comprehensive answer. Thank you so much!
            $endgroup$
            – kikjezrous
            May 7 at 19:30












          • 14




            $begingroup$
            Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
            $endgroup$
            – Saiboogu
            May 6 at 17:27






          • 3




            $begingroup$
            Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
            $endgroup$
            – Organic Marble
            May 6 at 17:29






          • 1




            $begingroup$
            Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
            $endgroup$
            – Digger
            May 7 at 15:57







          • 1




            $begingroup$
            Brilliant and comprehensive answer. Thank you so much!
            $endgroup$
            – kikjezrous
            May 7 at 19:30







          14




          14




          $begingroup$
          Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
          $endgroup$
          – Saiboogu
          May 6 at 17:27




          $begingroup$
          Reading the second half of this is a bit painful. It's no wonder they had the later organization safety issues, with precedents like that being set. There should be no punishment for following flight safety rules to 'failsafe.'
          $endgroup$
          – Saiboogu
          May 6 at 17:27




          3




          3




          $begingroup$
          Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
          $endgroup$
          – Organic Marble
          May 6 at 17:29




          $begingroup$
          Agreed, (and I do not defend their actions) but management was angry because they were not informed more than because the rules were followed. Hale goes on to say "But that is not the point of the fable. The moral of the story for all rookie Flight Directors is ALWAYS INVOLVE YOUR MANAGEMENT. Any time that a critical action can reasonably be delayed for even a few minutes GET ON THE PHONE WITH THE BOSS. No matter what the Flight Rules say. After all, it’s just your career on the line."
          $endgroup$
          – Organic Marble
          May 6 at 17:29




          1




          1




          $begingroup$
          Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
          $endgroup$
          – Digger
          May 7 at 15:57





          $begingroup$
          Another reason to keep your boss in the loop: I learned, early and painfully, in my military career, that ALL negative developments, personal or professional, were to be reported ASAP to your immediate superior. Perhaps the primary rationale to this unwritten rule was to protect said superior in the likely event that she gets questions about the precipitating event (most likely from her boss) - she would then want to be able to answer said questions instead of being "blindsided." In the NASA case, said superior is likely being protected against press inquiries...
          $endgroup$
          – Digger
          May 7 at 15:57





          1




          1




          $begingroup$
          Brilliant and comprehensive answer. Thank you so much!
          $endgroup$
          – kikjezrous
          May 7 at 19:30




          $begingroup$
          Brilliant and comprehensive answer. Thank you so much!
          $endgroup$
          – kikjezrous
          May 7 at 19:30

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Space Exploration Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          Use MathJax to format equations. MathJax reference.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fspace.stackexchange.com%2fquestions%2f35975%2fwhy-was-gemini-viii-terminated-after-recovering-from-the-oams-thruster-failure%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

          Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

          Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020