66-FM1-59 |
Dec 05 1966 |
Spacecraft computer program requirements for AS-207/208, AS-503, and AS-504 |
2 |
66-FM1-60 |
May 16 1966 |
Comments on the AS-207/208 Preliminary Spacecraft Reference Trajectory |
2 |
66-FM1-64 |
May 27 1966 |
CSM orbit determination using the LEM radar |
2 |
66-FM1-68 |
May 31 1966 |
Apollo spacecraft computer program development newsletter |
7 |
66-FM1-70 |
Jun 02 1966 |
Spacecraft computer program status report |
2 |
66-FM1-75 |
Jun 13 1966 |
Apollo spacecraft computer programs--or, a bucket of worms |
7 |
66-FM1-78 |
Jul 01 1966 |
Another Apollo spacecraft computer program status report |
7 |
66-FM1-83 |
Jun 11 1966 |
Apollo rendezvous guidance computer program options |
2 |
66-FM1-84 |
Jul 11 1966 |
Capability to do orbit navigation in earth orbit will not be implemented for AS-207 or AS-504 |
2 |
66-FM1-85 |
Jul 08 1966 |
Determination of relative CSM orbit |
2 |
66-FM1-86 |
Jul 08 1966 |
No special program available for targeting the CSM plane change in lunar orbit |
2 |
66-FM1-89 |
Jul 11 1966 |
LEM radar angle bias correction |
2 |
66-FM1-94 |
Jul 18 1966 |
Rendezvous terminal phase guidance program in the Apollo spacecraft computer |
2 |
66-FM1-95 |
Jul 21 1966 |
AS-204 computer program status |
7 |
66-FM1-100 |
Aug 30 1966 |
Notes regarding the AS-207/208 Guidance Systems Operations Plan (GSOP) meeting with MIT |
2 |
66-FM1-103 |
Aug 30 1966 |
Automatic rendezvous braking maneuver |
2 |
66-FM1-104 |
Sep 02 1966 |
Status of the lunar module "quick return" guidance capability |
2 |
66-FM1-107 |
Sep 19 1966 |
Alternate rendezvous technique - mission planning status |
2 |
66-FM1-108 |
Sep 20 1966 |
Spacecraft computer program status for AS-501 |
7 |
66-FM1-109 |
Sep 21 1966 |
Mission rules needed for use with AGC self-check |
2 |
66-FM1-110 |
Sep 21 1966 |
LGC computer requirements to provide DPS backup of SPS |
2 |
66-FM1-111 |
Sep 21 1966 |
Rendezvous search modes of various types |
2 |
66-FM1-112 |
Sep 21 1966 |
Apollo rendezvous navigation data edit is too complicated |
2 |
66-FM1-113 |
Sep 21 1966 |
There are differences in the descent guidance programs on AS-503 and AS-504 |
2 |
66-FM1-114 |
Sep 22 1966 |
Apollo spacecraft guidance navigation modes currently planned for AS-$03 and AS-504 |
2 |
66-FM1-115 |
Sep 27 1966 |
LGC program development for the AS-278B |
2 |
66-FM1-118 |
Oct 04 1966 |
No extra memory for the Apollo Spacecraft Computer |
2 |
66-FM1-123 |
Oct 11 1966 |
Procedure for obtaining Apollo Spacecraft Computer Program schedule information |
2 |
66-FM1-124 |
Oct 11 1966 |
Program Development Plans are coming!! |
2 |
66-FM1-129 |
Oct 12 1966 |
Cursory definition of Spacecraft Computer Program capabilities currently planned for AS-503 and AS-504 |
2 |
66-FM1-130 |
Oct 12 1966 |
Altitude and velocity limits imposed by the spacecraft computer program on the AS-503 mission |
2 |
66-FM1-131 |
Oct 10 1966 |
More on Program Development |
2 |
66-FM1-132 |
Oct 14 1966 |
LGC program requirements and mission constraints on alternate mission AS-278B |
2 |
66-FM1-133 |
Oct 14 1966 |
AS-206 LGC program status |
2 |
66-FM1-135 |
Oct 17 1966 |
Verification of LGC when powered-up in space |
2 |
66-FM1-136 |
Oct 17 1966 |
Apollo Spacecraft Computer Program Schedule |
2 |
66-FM1-137 |
Oct 17 1966 |
Another AGC program development report |
2 |
66-FM1-141 |
Nov 03 1966 |
AGC program for AS-501/502 - Final status report |
2 |
66-FM1-142 |
Nov 01 1966 |
In which some items of interest regarding the AS-206 LGC program status are discussed |
2 |
66-FM1-148 |
Nov 14 1966 |
AGS program status for AS-278 |
2 |
66-FM1-151 |
Nov 14 1966 |
Ground rules for MIT man loading for AGC programming |
2 |
66-FM1-168 |
Nov 25 1966 |
Small program change needed in the AS-501/502 AGC program |
2 |
66-FM1-169 |
Nov 28 1966 |
LGC program status for AS-206 |
2 |
66-FM1-170 |
Nov 28 1966 |
More interesting things about our work with MIT |
2 |
66-FM1-188 |
Dec 22 1966 |
DAP initialization simplification |
2 |
66-FM1-189 |
Dec 22 1966 |
We've bit the bullet on GRR |
2 |
66-FM1-191 |
Dec 22 1966 |
MIT's digital computers are saturated until the IBM 360 becomes operational |
2 |