QUOTE (Waspie_Dwarf @ Apr 29 2008, 08:17 PM)

Ok, it's 2 days since MID asked his question, so I'm going to have a crack at it. Here goes:
Apollo 12, struck by lightning around 37 seconds after launch causing a drop out of the instrumentation and a loss of telemetry for a few seconds.
Apollo 14: difficulty in docking the CM to the LM on the way out (no LM would sure have been a show stopper). Also The LM, Antares, needed a software upgrade after a faulty switch repeatedly gave the computer an abort command after separation from the CM. The software patch cause the LM radar to fail to lock on the lunar surface.
Apollo 16: Mission shortened by a day and Lunar landing attempt delayed and nearly cancelled as a result of a problem with the CSM main engine gimbal system.
How's that MID?
As I suspected, the ever-astute Waspie Dwarf has scored a 100% on the quiz!
Correct, absolutely.
Most people don't realize that these were all tense moments during these flights, and were mission threatening. These things were all chew-on-your-knuckles kind of problems.
Apollo 12's lightning strike actually had management and some controllers considering that perhaps the circuitry to deploy the parachutes might have been damaged by the lightning strike, which of course would mean death to Conrad, Bean, and Gordon. The notion was never mentioned to the crew, and when they were given a GO for TLI, it was done knowing that the possibility that they might die upon re-entry was present. However, the general consensus was, "What's the difference? We can't fix it, and if we re-enter now and they die...it's no different than if they re-enter after they execute their mission and die." Thus, they were given a GO. The flip side of that coin was that calling them out of Earth orbit because of a possibility that couldn't be verified, and having good chute deploy would've meant the waste of a 400 million dollar flight.
The unspoken worry of Apollo 12, which fortunately, resulted in the right call.
Apollo 14's docking difficulty was resolved by essentially ramming the LM with the CM. That was a show-stopper indeed if they couldn't get docked. And those abort commands in the LM PNGS would've triggered an abort during powered descent if the program was initiated. The software fix eliminated the possibilty of PNGS initiating an abort, and would require AGS to execute an abort. Again, it was mission control doing their jobs...and a tense potentially mission ending anomaly.
That Apollo 16 wait was a long, depressing thing. I actually thought there was a real possibility of having to scrap a perfectly good LM landing. It took a long time, but folks all over the country resolved it.
Some of the "perfection" of Apollo illustrated.
Anyway, Waspie: your question!