This forum is for discussion about content found on https://apolloinrealtime.org 

Very little of the thousands of hours of Mission Control audio on the website has been heard or documented. As you find moments of interest, post them here for discussion.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MadDogBV

Pages: 1 2 3 [4] 5 6 ... 8
46
What's happened is CONTROL and TELMU have blended together onto CONTROL's loop, and unfortunately there's about a 1-second delay between both transmissions so that's why it sounds like there is an echo. The TELMU channel on the website is nonfunctional at least during this phase on the mission. I think later on, they begin to separate out.

Quote
I thought Glynn was just about ready to lose it when INCO said there would be a 2-minute data loss for some reconfiguration and it took 20 minutes or more. INCO even on the FLIGHT loop just after the accident is interesting to listen to, as the controller is incredibly laconic and calm but one can tell a lot is going on behind the scenes.

There was indeed a lot of off-radio chatter that you didn't hear on the tapes. ;D Lunney has TELMU (Merlin Merritt) in his ear both on and off the loops begging him to get the power load reduced, and the flight dynamics people are champing at the bit to get the spacecraft on free return, so Lunney is impatient to get good comm established with the crew. It's very clear on even the FLIGHT loop that he has a difficult time hiding his anger over the comm being lost for a long period of time. Throughout the INCO loop during that incident, you can hear Ed Fendell make remarks like "I have to fight the flight director off -- here he comes" and "I've got a monkey on my back now" and "you guys have really done me in", which would seem to indicate he got chewed out off the loops.

A similar incident happens toward the end of the mission when the CM (now separated from the service module) is performing its final alignment prior to LM sep and re-entry. INCO (Tom Hanchett) struggles to establish comm and data with Odyssey during a phase of the mission when GUIDO (Ken Russell) and YAW (Bill Pressley) are in a hurry to uplink commands, losing data four or five times in the process. Gene Kranz, as steely as they come, has a better time concealing his anger than Glynn Lunney, but even he lets out an audible sigh of irritation over the loops after they break lock for the third time. "INCO, what's your problem?" When they have an opportunity to go back on high bitrate after downgrading to low to lock on solid, Kranz refuses INCO's request to do so, having lost faith in the stability of the comm.

It's important to note that Fendell and Hanchett are very competent men, having been involved in the space program for years even through the Mercury and Gemini days. The procedures, however, are only as good as the training that they receive. So when the flight controllers write up the mission operations report at the end of Apollo 13, both INCO and PROCEDURES will openly slam the poor quality of the sims as far as communication failures are concerned:

Quote from: Apollo 13 Mission Operations Report, Page I-5
A number of attempted communications failures have been incorrectly simulated such as an attempt to fail the entire USB downlink but failing to inhibit the crews downlink voice. These mistakes provide INCO negative training in resolving communications anomalies as well as causing the Flight Director to lose some confidence in INCO."

As far as the spliced INCO/PROCEDURES loop -- I'll upload them on Google Drive and share a link at the next most opportune time!

47
Hi there,

Yep, it's a known bug and not associated with a device, because some of the tapes "blended" together as a result of a wander effect. Ben Feist explained in a separate thread as follows:

Quote
Hi everyone. Yes, unfortunately that track was not digitized on the original playback. We plan to run the tape through one more time in order to capture it properly this time.

As for the audio being mixed up at various parts of the mission, yes, you're not going crazy, this is happening. We believe the old tape machine isn't properly tracking the tape, causing it to wander across channels. There is a pending fix for this but again, will take time. The best thing to do right now is to check the adjacent channels if you think you're hearing the wrong channel.

It's a shame, because those tapes are some of the most important during the entire incident. The scramble that took place in the LM SSR backrooms in order to quickly pull up, tweak, and then send out procedures to activate the LM, as well as to work on subsequent powerdown profiles, is one of the most significant achievements in mission control in the entire space program.

The NETWORK tape is also affected and is noticeably blank although there is a NETWORK on duty.

Best way I found to listen to INCO was actually to download the INCO and PROCEDURES tapes from Archive.org in John Stoll's MOCR collection, and then splice them together in GoldWave/Audacity so that INCO was on the left speaker and PROCEDURES was on the right speaker. The two positions, despite being nominally different, actually worked in concert with each other in order to interface with MSFN and maintain uplink/downlink with the spacecraft. This is evident during the accident as well.

48
General Discussion / Re: Some help with OCR radio transcripts?
« on: June 29, 2023, 08:55:30 am »
This is good stuff. If you want help editing any of the transcripts (such as to account for some of the astronaut-specific jargon that the CAPCOMs or crew use), let me know. I've been a pretty big contributor to the Apollo 13 lore and have listened to a lot of the MOCR tapes for various different positions. There's some great snippets and transmissions in those as well.

49
Relatively self-explanatory.

Link: https://apolloinrealtime.org/13/?t=068:58:18&ch=5

50
Yeah, I considered that possibility, and upon reflection, that makes the most sense. Thanks for that explanation.

Edit: Actually as I think about it, it could go either way. Neil and the GNC folks are discussing the availability of seats and consoles in the Vehicle Systems SSR.

Looking over the Flight Controller Assignments PDF that I saved to my PDF, the SSR has about 4 positions and 21 officers for the CSM working over three shifts (so 7 officers a shift), and it also has over 18 different officers and 10 different positions for the BSE (Booster). It's more than likely, given how important the re-entry is, that the Booster officers will want to come back into the SSR room to listen in on the recovery operations. So the Booster consoles might indeed be first-come first-serve as Neil said, particularly with Milt Windler's warning hanging over everyone's head.

51
Sounds like that's actually Milt Windler on the Flight director loop. Time and again he has to be the bad guy on this mission.  ;D

At about 131:06:50 on the RETRO loop there's a funny conversation about how the AGC (it's not Jack Garman, not sure who it is) officer plans to watch it at home instead.

Here's another neat addendum to that. On the GNC loop, one of the flight controllers offers up the CSM SSR for people who want to celebrate the splashdown. Then Neil Hutchinson from SPAN provides his input on that, offering a very candid and unflattering appraisal of the BOOSTER officers. Link: https://apolloinrealtime.org/13/?t=131:07:50&ch=18

52
Apollo 13 Moments of Interest / 058:40:27 Steve Bales takes charge
« on: April 14, 2023, 03:32:04 pm »
I know Naraht will appreciate this. The entire GUIDO-R loop around this area is great to listen to, as it shows GUIDO #3 (out of 4 or 5 crowded around the console) Steve Bales taking command trying to solve the integration problem in the LM. His preferred option is to send MIT vectors to run on their hybrid since the LM is (assumed to be) not able to navigate in deep space. Jack Garman, the AGC expert, has meanwhile been trying to convince Steve to upload a state vector. This leads to Bales eventually asking flatly: "Are we wrong doing what I say we're going to do?"

Link: https://apolloinrealtime.org/13/?t=058:40:27&ch=22

One thing of note: Jack does warn Steve against depending on the hybrid to work for them due to difficulty bringing it up. This ends up being prescient as later on, when trying to do the free return burn at 61:30 GET, they're unable to get the hybrid to churn out a run in time, despite repeated prodding from GUIDO Gary Renick, Jack, and Steve. This forces Gary to use his own professional judgment to assure Lunney to go ahead with the burn.

53
Awesome! I'm glad to see that this recording had a lot of historical significance.

54
It's evident that mission controllers are informed that all of their conversations over the loops are being recorded for posterity and public record, so they keep their dialogue as muted as possible. Still, things occasionally slip through...

This might be considered slightly NSFW... I would make sure your headphones are plugged in.

Link: https://apolloinrealtime.org/13/?t=041:02:42&ch=17

55
NETWORK Ron DiCosmo gives PROCEDURES Jim Fucci a briefing on the current state of Parkes (the 210ft radio telescope otherwise known as "The Big Dish"), and the inability to get LM data.

Link: https://apolloinrealtime.org/13/?t=058:26:57&ch=5

56
As CAPCOM Joe Kerwin reads up the preliminary entry PAD to the crew, Deke Slayton - sitting to his left - makes a check-in call to Mary Haise, who is greatly relieved to hear that things are going well on board Aquarius and Oydssey as they make their final trek towards Earth.

Link: https://apolloinrealtime.org/13/?t=138:41:10&ch=14

57
Jack Swigert is attempting to activate the CMC in the freezing-cold command module, which is more than essential to allow the crew of Apollo 13 to do a proper re-entry. He mentions over the loops that he's unable to get the computer to go into standby. As GUIDO Ken Russell troubleshoots the problem with Jack Garman in the backroom, Garman almost flippantly remarks that this particular computer has a history of having trouble with going into standby. Not something that anyone wants to hear at this particular phase of the mission when everything is already in a critical state.

Link: https://apolloinrealtime.org/13/?t=138:19:41&ch=21

Edit: One particularly humorous (in hindsight) remark towards the end of the conversation is "You can always come up by powering down and powering up the computer again." How many times have we heard this when dealing with tech support in the 21st century? ;D

58
Sleep period for day 3 of the mission, in the wee hours of the morning at 07:52AM CST. It starts out with the EPS reaching out to Dumis to ask the name of a specific Houston Oilers football player (Jerry LeVias), followed by some brief conversations about baseball and basketball, a cake that Dumis brought in, and the local girls (note that Dumis is married, and this is also mentioned on the loops). This is about as lazy and desultory as conversations on the MOCR loops ever get.

Link: https://apolloinrealtime.org/13/?t=040:39:15&ch=17

59
Future FLIGHT director Neil Hutchinson, currently stationed at SPAN for CSM operations during Apollo 13, requested data from EECOM John Aaron earlier for a TCE problem with fuel cell 3. John ran the playbacks needed, but in doing so, did not set up a dedicated chart recorder to provide SPAN with their own copy of the data. As a result, they were forced to copy the strip chart recording with a Xerox machine, something that's not easy to do when the paper is a bit over 70 inches long. Neil voices his frustrations to John with the hopes that he will correct this issue in the future.

Yes, even the best steely-eyed EECOMs can make mistakes!

Link: https://apolloinrealtime.org/13/?t=036:33:56&ch=17

Supplemental: About 45 minutes prior to that, Neil asked for the TCE data from John, which led to the above episode taking place in the first place.

Link: https://apolloinrealtime.org/13/?t=035:54:44&ch=17

60
Apollo 13 Moments of Interest / Re: 056:01:53 Comedy night with RECOVERY
« on: January 13, 2023, 09:29:57 am »
It really is. And it conjures up a bizarre mental picture - looking at the tank pressures chart as they slowly slide down, watching the transcript on the left as the crew and the MOCR come to the realization that something is going really wrong, and yet all the while, an almost haunting rendition of "Raindrops Keep Falling On My Head" plays in the background on the RECOVERY loop.

Pages: 1 2 3 [4] 5 6 ... 8