During the 501 operation apparently there was no question as to whether state vector updates would be sent. But I gather there may have been some question as to how important they are. This will probably just add to the confusion, but I thought I might redistribute the attached memos written last January which stated…
Category: Apollo missions
State Vector Update Criteria for AS-501
Because of the decision to utilize the AS-502 Apollo Guidance Computer programs for the AS-501 mission, the mission was designed and developed on the premise that the state vector updates __would__ be made. ���������� this, the situation exists that a __perfect__ launch vehicle spacecraft combination __without__ guidance or propulsion errors of any kind will land…
State vector update situation for AS-501 and AS-502
The AS-501 and 502 missions have been designed to update the state vector (position and velocity) in the Apollo Guidance Computer (AGC) with a state vector from the Manned Spaceflight Tracking Network (MSFN) prior to the Saturn (S-IVB) out-of-orbit burn and again prior to the second Spacecraft Propulsion System (SPS) burn. If these updates are…
Lunar orbit revolution counter for C’
This may seem like a trivial matter – however, before any confusion arises let’s firmly establish the means of identifying revolutions in lunar orbit by number. Specifically, unless there’s some good reason for choosing another way:…
“D” mission launch window is nice
This note is in follow-up to our “D” mission launch window discussion during our Tuesday morning meeting. Essentially, the situation is as I understood it to be at that time. Real time procedures can be and are being established to provide a launch window about two and threequarters hours long by using the earlier propulsion…
Rendezvous meeting reminder
This note is to remind you of our Rendezvous meetings on January 3, 1968. In the morning we hope to discuss Rendezvous on the “C” mission starting at 9:00 a.m. and in the afternoon Rendezvous on the “D” mission starting about 1:00pm….
D Rendezvous Open Items, Action Items or whatever you call them
I’ve reviewed my notes of the D Rendezvous meetings over the last couple of months and have found the following open/action items. I guess most, if not all, are being worked on. But time grows short and so I’m sending this list around to make sure of it. If you know of others, please give…
Some assumptions about Spacecraft 101 retrofire and reenty procedures
We have recently held several small Trajectory Control Data Priority Working Group meetings dealing with Spacecraft 101 retrofire and reentry. The results are being documented to show how the various guidance and navigation data sources will be compared to one another and used during the mission. During these discussions a couple of basic assumptions have…