This forum is for discussion about content found on 

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 ... 5 6 [7] 8
General Discussion / Re: Way to skip gaps in audio?
« on: March 30, 2021, 01:48:40 pm »
One thing I've done mostly as a side hobby is downloaded the audio files for the loops directly from the NASA Audio Collection on, ran a noise removal algorithm in GoldWave to get rid of the warbling noise in the background produced by the tapes, and then a silence removal to get rid of the gaps. The result is a relatively seamless track that can be listened to through a multimedia player like VLC or AIMP. I could produce a step-by-step guide for doing this if need be.

Of course, this is not the same thing as skipping the files directly through the website, but I can imagine that being a general pain to program in.

Pretty self-explanatory. He's not explicitly identified as Jay, but the voice is unmistakably his. I haven't monitored the FIDO loops to determine if Jay was chatting to the backroom prior to this, though I gather there were multiple FIDO's and GUIDO's working the consoles after the accident occurred. He's not heard from again on the FLIGHT loop until Lunney's second shift at around 089 hours or so.


Edit: He was actually on the FIDO loops a good while prior to this, to talk to SELECT specifically. Jay wanted to sort out some confusion regarding tracking requirements after Bill Boone scared the hell out of them by suggesting they might not have the transponder beacon for more than an hour at most.

Short but sweet one here. In his first shift in the MOCR as CAPCOM after the explosion, Joe Kerwin tells the crew to commence the planned yaw maneuver. Problem is the crew can't hear him.

I suspect Kerwin probably didn't get much sleep after the accident.  ;D

Isolated Flight Director Loop:

INCO Ed Fendell puts through the idea to FLIGHT Glynn Lunney about saving power in the LM by turning off the power amplifier for the comm unit. It wasn't but a few hours ago that a test procedure also initiated by Fendell to bring up TM caused a significant loss of comm, so Lunney is quick to remind him of this. Thankfully, Fendell is undeterred.


If you listen to the start of the FLIGHT loop of the Kranz shift just prior to the accident, then go all the way to the end, you'll notice there is discussion about how to manage the SHe problem on board the LM, in case the pressures are too high. It even gets to the point where Kranz has a meeting with the LM guys and some folks in SPAN on what steps need to be taken if the SHe pressures are too high, requiring the AFD to take over in the interim.

By the time Kranz returns, Haise has already entered the LM and has reported a nominal SHe pressure.

EECOM Sy Liebergot laughs about the amount of time and effort that went into creating a plan, and how it all turned out to be for nothing. The sense of relief and elation throughout the MOCR (at one point requiring Kranz to bark at the controllers to "keep the chatter down") is especially ironic given what happens an hour later.



Five hours prior to "the problem" on Apollo 13, an interesting conversation between White FLIGHT, PROCEDURES and NETWORK. Kranz expresses his frustration about a new ASPO policy that on-site tapes at remote locations be shipped to Houston after 24 hours. Of course, this has no actual bearing on the disaster and ends up becoming a moot point shortly after the tank explosion.


Lunney gets into it with his flight controllers. Shortly after the disaster and the mental strain of the course-correction burn, Lunney is trying to get the crew into some semblance of PTC. However, SPAN is trying to come up with a new PTC procedure, which is causing delays in the process at a time when management of power and consumables is a priority. FLIGHT becomes progressively annoyed by this.

(Unfortunately, the TELMU/CONTROL loop is drowned out by the noise of the comm, otherwise I'd post that also.)

I love it when Lunney gets testy with the flight controllers too - which is just about all the time, usually. He tends to be polite with the CAPCOM though, probably because they're astronauts and ultimately his voice link between the ground and the spacecraft.

I particularly enjoyed a sequence of the flight director loop (one that wasn't in the original 8 hours posted to YouTube, but came immediately after the free-return course correction burn at ~62 hours), where he was trying to come up with a PTC procedure but SPAN was making him wait for a preferred procedure of their own.

"I'm not getting anybody to come out and agree with me, so I guess we're about to press on here with what we're gonna do... And I'm getting tired of waiting... -forced laughter-"

Best part about that is when he effectively pulls rank and says he was there "when we did it on Apollo 10".


INCO Ed Fendell expresses his (rather understandable) frustrations with the PROCEDURES and TRACK officers after an attempt to establish tracking with the LM results in a lengthy loss of comm, which in turn results in flight director Glynn Lunney getting rather testy at INCO.

Most of the INCO channel around here (starting at 59:45:00) is worth listening to, to get an inside look at the comm disaster that took place, by way of the conversations between INCO, TRACK, and the Honeysuckle and Goldstone tracking stations. Although they do come up with a workaround, the poor INCO officer does spend the next several minutes lamenting the trouble that this new procedure got him into.  :)

Astronauts are a very tight fraternity and they do rib each other from time to time. There probably would have been an uproar if the joke came from Glynn Lunney or Gene Kranz.  ;)

Thanks! I was listening to the Trench loops and wondering who that voice was.

That does surprise me! The book "Apollo: The Race To The Moon" implies that the MOCR has several direct lines to the major plants (McDonnell Douglas, North American, Grumman, etc.) with staffed engineers who will pick up around the clock. Perhaps those lines are closed or they're only available to the FOD personnel.


EECOM's ECS cries out that the "surge tank's gotta come on" because the manifold pressure is dropping down to 27 Psi, putting the crew in danger, followed up by EPS gravely warning Clint Burton that a battery should be put on main A due to the O2 tank pressure dropping. This occurs amidst a heated argument between FLIGHT, GUIDO, CONTROL, and TELMU about whether or not the crew should do a P52 to align the LEM with the CSM.

General Discussion / Apollo 13 TELMU audio loop blank?
« on: March 15, 2020, 07:47:00 pm »
The TELMU audio loop for Apollo 13 during the time of the crisis (e.g. at the beginning of Lunney's shift in the MOCR at the roughly 57-hour mark) seems to be totally blank. I find this a bit hard to believe since at this point TELMU is extremely active in making sure Aquarius gets powered up to support the crew. Is this an error, or was the TELMU audio loop actually blank at this point in the mission?

Pages: 1 ... 5 6 [7] 8