Documents / Document

Apollo 11 Technical Crew Debriefing, Volume 1 (scan)

NASA via ibiblio · 1969-07-31 · 251 pages · text by OCR

This is Volume 1 of NASA's Apollo 11 Technical Crew Debriefing, dated July 31, 1969. The Mission Operations Branch of the Flight Crew Support Division at the Manned Spacecraft Center in Houston prepared it, and it was originally classified Confidential. In it Armstrong, Aldrin and Collins go phase by phase through suiting, launch, powered flight, Earth orbit and lunar surface activities. They comment on suit fit, vibration, checklists, lunar dust, footing and poor sleeping conditions in the lunar module. A section titled Visual Sightings appears in the table of contents.

  • p. 30 …It was impossible to read an effect on any indicator in the cockpit. COLLINS This is…
  • p. 38 …the expected altitude was 174 and we read 176. The EMS was 3.3 plus. ARMSTRONG…
  • p. 39 …There's no way that the EMS could read 99.1 at docking. As I recall…
  • p. 40 ## CONFIDENTIAL Then I thrusted minus X until the DELTA-V counter read minus 100.5. I…
  • p. 46 …Neil and I both read a memo put out by MPAD, saying that for some failure…
  • p. 50 …We gave daily dosimeter readings, which as far as I'm concerned fall in a sort…
  • p. 51 …COLLINS And the dosimeter we just gave them a once-a-day reading on that dosimeter…
  • p. 68 …When you read me the numbers, you didn't note that I read star number 2…
  • p. 79 …The cabin temperature (translunar) was slightly warmer than we would like it, although the gage readings…
  • p. 130 …We had good helium pressure and read that out to MSFN. We went through the RCS…
  • p. 132 …the AGS, and give you an erroneous reading so you wouldn't pass. In any case…
  • p. 134 …There is a bad amount of data that the ground reads up to you in that…
  • p. 151 …They did approach the maximum numbers with a reading of approximately 94. Anyway, they weren't…
  • p. 169 …with time as evidenced by successive LPD readings. FCOD REP. Do you recall when you proceeded…
  • p. 170 …again, although at the time we were reading relatively low tank pressures. I think the OX…
  • p. 172 …We read the sine and cosine out of AGS (and I'm sure they copied that…
  • p. 175 …we were going to launch, so we read through the remainder of the simulated countdown and…
  • p. 235 …same exercises such as pressure-integrity check, reading the cabin down, and configuring the ECS. I…
  • p. 236 …We used a sequence of marking that involved an onboard averaging of five successive cursive readings…
## CONFIDENTIAL

one you're concerned with. That's about the Y-axis; that was 0.1. I don't know whether the sine of that agrees at all with the approximation of 0.1 that we got in the Sun check. We didn't torque those angles. The ideal was to get a gravity direction and then to do a two-star alignment and look at the torquing angles after the two-star check which would then give an indication as to what the drift had been since the last alignment. The initial gravity alignment, combined with the two-star alignment, would produce a new location of the landing site. Had we landed straight ahead, my intent was to use Rigel in the left detent number 6 and Capella in the right detent. The 13-degree yaw moved Capella out of the right-rear detent, but Rigel was in good shape there. That's the one I used first. I then selected Navi in number 4 detent, the right rear, and that wasn't particularly satisfactory. It was quite dim and it took a good bit longer than I had hoped to get the marks on that. I can't comment particularly on the star-angle difference other than it was a little disappointing in that it was 00009. Torquing angles we have recorded, and we did torque. The latitude and longitude — we'd have to listen to the guidance people as to just what

## CONFIDENTIAL

About this file

Document, cited by the archive. The PDF is mirrored here; the original link is under it. The text was read from the page images by an OCR model; expect the odd misread word. 251 pages are in the text index: search them above, or from the library's search.