Apollo Experience Report Flight Planning For Manned Space Operations - Nasa
4&A4zAPOLLO EXPERIENCE REPORTFLIGHT PLANNING FORMANNED SPACE OPERATIONS-by John W. OWeill, J. B. Cotter, and T. W. HollowayManned Spacecrafi CenterHouston, Texas 77058N A T I O N A L AERONAUTICS A N D SPACE ADMINISTRATIONW A S H I N G T O N , D. C.SEPTEMBER 1972
Ii. Repait NG.NASA Tl4' 0-0973 2 Government Accession No.I .3. Recipient's Catalog No.'5. Report Date4. Title and SubtitleSeptember 1972.--APOLLOEXPERIENCEREPORTFLIGHT PLANNING FOR MANNED SPACE OPERATIONS-6. Performing Organization Code 8. Performing Organization Report No.7. Authork)John W. O'Neill, J. B. Cotter, a n d T . W. Holloway, MSCMSC S-31910. Work Unit No.9. Performing Organization Name and Address914- 80-23-96-7211. Contract or Grant No.Manned Spacecraft CenterHouston, Texas 7705813. Type of Report and Period CoveredTechnical Note12. Sponsoring Agency Name and AddressNational Aeronautics and Space AdministrationWashington, D.C. 2054614. Sponsoring AgencyCode15. Supplementary NotesThe MSC Director waived the use of the International System of Units (SI) for:his Apollo Experience Report, because, in his judgment, use of SI Units would impair the usefulnessIf the report o r result in excessive cost.16. AbstractThe history of flight planning for manned space missions is outlined, and descriptions and examplesof the variol;s c d z t i m z r yphases nf f!ight data documents from Project Mercury to the ApolloProgram are included. Emphasis is given to the Apollo flight plan. Timeline format and contentare discussed in relationship to the manner in which they are affected by the types of flight plans.and various constraints. 18. Distribution Statement17. Key Words (Suggested by Authods) )Apollo ProgramCrew- Activity Scheduling' Flight Planning' Timeline''19. Security Classif. (of this report)None*]None22. Rice'21. NO. of Pages20. Security Classif. ( f this page)I5 O nFor sale by the National Technical Information Service. Springfield. Virginia 22151I 3.00
CONTENTSPageSection.INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .BACKGROUND O F FLIGHT PLANNING FOR MANNED SPACE MISSIONS . . . .Purpose of Flight Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Evolution of Flight Plans Through the Apollo Program . . . . . . . . . . . . .APOLLO 12 FLIGHT PLAN SAMPLES AND DESCRIPTION . . . . . . . . . . . .Introductory and Administrative Infor mation . . . . . . . . . . . . . . . . . .Detailed Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Selected Supporting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . .FLIGHT PLAN SCHEDULES AND DATA REQUIREMENTS . . . . . . . . . . . .Factors Affecting Flight Plan Development Schedules . . . . . . . . . . . . .SUMMARYData Requirements.Abbreviated Timeline as a Worksheet . . . . . . . . . . . . . . . . . . . . . .Detailed Timeline Format and Content . . . . . . . . . . . . . . . . . . . . .Final Abbreviated Timeline . . . . . . . . . . . . . . . . . . . . . . . . . . .DEVELOPMENT O F THE FLIGHT PLAN TIMELINE CONTENTInteraction of Detailed Flight Planning. Trajectory Refinement.Procedures Development. and Crew Training . . . . . . . .REAL-TIME OPERATIONS IN THE MISSION CONTROL CENTER . . . . . . . .CONTINGENCY AND ALTERNATE FLIGHT PLAN DEVELOPMENT . . . . . . .Contingency Flight Plan Development . . . . . . . . . . . . . . . . . . . . . .Alternate Flight Plan Development . . . . . . . . . . . . . . . . . . . . . . .iii1133711111722262628293030323234353539
SectionPage.Candidate Change Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . .Flight Plan Configuration-Control P r o c e s s . . . . . . . . . . . . . . . . . .CONCLUDING REMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .FLIGHT PLAN CHANGE CONTROL.iv39404042
FIGURESFigure1234567891011Page.Flight planning information utilization . . . . . . . . . . . . . . . . .Excerpt from detailed timeline of Mercury M flight plan . . . . . . .Excerpt f r o m detailed timeline of Gemini XI1 flight plan . . . . . . .Partial abbreviations listing from Apollo 12 final flight plan . . . . .Symbology description inchded in Apollo 12 final flight plan . . , .Technical evolution of flight plan and flight data fileExcerpt f r o m the notes section of Apollo 12 finalflight p l a n . . . . . . . . . . . . . . . . . . . . . .Lithium hydroxide canister change schedule f r o m Apollo 12final flight plan . . . . . . . . . . . . . . . . . . . . . . . . .45810121315.16Excerpt f r o m mission requirements reference chart of Apollo 12final flight plan . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Excerpt f r o m earth-orbital detailed timeline of Apollo 12final flight plan . . . . . . . . . . . . . . . . . . . . . . .18.19Excerpt f r o m TLC period of Apollo 12 final flight plandetailed timeline . . . . . . . . . . . . . . . . . . . .12Excerpt f r o m Apollo 12 final flight plan detailed timeline coveringsimultaneous operation of two vehicles in lunar orbit . . . . . .13Example of graphical presentation of spacecraft- maneuvering data inApollo 12 final flight plan . . . . . . . . . . . . . . . . . . . . .20.2114Graphical presentation of landmark- tracking information f r o mApollo 12 final flight plan . . . . . . . . . . . . . . . . . . . .15Summary of s e r v i c e propulsion system predicted propellant usagef r o m Apollo 12 final flight plan . . . . . . . . . . . . . . . . .2316Excerpt f r o m abbreviated timeline of Apollo 12 final flight plan.2417Alternate mission 1 summary flight plan for Apollo 12 CSM2518Contingency flight plan breakdown36.a22.V
PageFigure.,.,.,.19Typical Apollo mission contingency flight plan format3820Apollo operations change-control boards a t MSC.41
ACRONYMSAOSacquisition of signalASP0Apollo Spacecraft P r o g r a m OfficeCCBConfiguration Cont r o 1 BoardCPCBCrew Procedures Change BoardCSMcommand- service modulec . s. t.central standard timeDO1descent orbit insertionEVAextravehicular activityFA0flight activities officerGETground elapsed timeiM!!Lnar mndl-lleLO1lunar orbit insertionLOSloss of signalMCCMission Control CenterMCC-HMission Control Center, HoustonMCC-1midcourse correction 1MOCRMission Operations Control RoomMSCManned Spacecraft CenterMSFNManned Space Flight NetworkPTCpassive thermal controlR&Dr e s e a r c h and developmentRCSreaction control systemRE FSMMATreference stable member matrixS -IVBSaturn IVB (third) stagevii
SPSservice propulsion systemTD&Etransposition, docking, and extractionTECtransearth coastTEItrans earth in j e c tionTIGtime of ignitionTLCtranslunar coastTLItranslunar injectionviii
APOLLO EXPERl ENCE REPORTFLIGHT PLANNING FOR MANNED SPACE OPERATIONSBy J o h n W. O'Neill, J. 6. Cotter,a n d T. W. HollowayManned Spacecraft CenterSUMMARYThe purpose of a flight plan is to organize the activities of a mission in a logical,efficient, and safe manner. During the premission phase, flight plans a r e developed tosupport hardware definition, to support the integration of the crew and vehicle, and toprovide a basis for crew training and mission simulations. During a mission, the flight hming team- suppnrts the Flight Director by monitoring flight plan activities, anticipating problems necessitating the preparation of alternate plans, monitoring overallcrew procedures, and modifying the procedures when necessary.Flight planning has greatly increased in complexity f r o m previous programs to thepresent missions of the Apollo Program. Using the Apollo 12 final flight plan as an example, this report describes the present state of the flight planning a r t in detail. Thediscussion is oriented around a three-way division of the flight plan: introductory information, timeline, and supporting data. The timeline format and content a r e discussed, and the elements affecting the timeline a r e described.Flight plan development and scheduling of crew activities a r e discussed. Factorsthat affect scheduling include mission type, launch frequency, crew training and simulations, and flight plan correlation to other onboard data. The interplay of these and otherfactors are described, and the effect on flight planning data requirements is outlined.One section of this report is devoted to contingency and alternate flight plans.Contingency flight plans include timelines for situations in which some mission objectives a r e abandoned to avoid violation of the mission rules. Alternate flight plans aredesigned f o r u s e on nonnominal launch dates.INTRODU CT IONIt has long been accepted that any major project should have a documented plancovering what is to be done, how, when, by whom, the cost, the foreseeable problems,and the alternative solutions to these problems. The plan is the means by which theroles and responsibilities a r e communicated to the project participants; it is the
yardstick by which performance is measured. In recent y e a r s , the concept of planninghas been expanded and incorporated as a basic element of s y s t e m s engineering. J u s tas the entire integrated systems assembly and the interrelated requirements and constraints must be considered in the purely technical functions of s y s t e m s analysis, design, development, and testing, the planning of the project a l s o must cover the completerange of activities necessary to reach the s y s t e m s development goal.The actual execution of a manned space flight certainly must be ranked as one ofthe largest and most complex projects ever undertaken; and the need f o r a documentedplan is even more critical because of the complex goals, resources, and constraintsthat must be interrelated. The flight plan for a manned mission, therefore, must bedesigned t o fulfill all the listed planning requirements in regard to the mission personnel and resources. The questions answered in the flight plan are described in the following paragraphs.What is to be done? What’are the mission objectives and what are all the crewand ground-control activities required to perform these objectives ?How ? What a r e the safest, most efficient, and most potentially successful crewand ground procedures for accomplishing the objectives and all prerequisite activities ?When? What a r e the durations of these activities, and what is the most logicaland effective sequence that ensures adequate time for all critical activities ?By whom? What is the procedural relationship of the flight crew and groundsupport function? What are the proper division and interaction of the onboard tasksamong the crew, taking into account the constraints of the vehicle and spaceenvironment ?At what cost ? What is the most efficient and safest way to execute the mission int e r m s of all consumables and resources, such as propellants, electrical power, lifesupport water and oxygen, photographic film, and crew and mission time available?What are the foreseeable problems and alternative solutions ? What effects accruef r o m possible inflight hardware problems or slips in the launch schedule, and what a r ethe new o r revised flight plans that will maximize what is to be gained f r o m the a l t e r nate or contingency mission?The discussion that follows t r a c e s the evolution of flight planning f r o m the f i r s tmanned flights through the f i r s t two Apollo lunar- landing missions. The development,change control, and real-time updating of the flight plans are discussed, and the importance of crew training and mission simulations in validating and modifying the flightplan is illustrated.The changing relationship between the flight plan and other documentation used bythe crew h a s had a major impact on the flight plan purpose and content. This relationship and the associated changes are presented whenever unique insight is t o be gained.This document was prepared by the Flight Planning Branch of the Crew Proced u r e s Division, Flight Crew Operations Directorate, NASA Manned Spacecraft Center.Cofittribdting zGihGi*sfi*oiiithe Flight Planning Branch were W. M. Anderson, J. H. Bin,2
D. D. Durychj R, E. Ferguson? S. H. Gardner, G. E. Gentry, T. A. Guillory, J. N.Leech, E. B. Pippert, J. W. Fadcliff, L. J. Riche, J. V. Rivers: C. L. Stough, andMajor G. M. Colton, USAF. Acknowledgment is a l s o made to R. J. Rogers of TRWInc., Houston Operations, f o r his contribution to the section on Apollo flight plan formats and samples. J. N. Leech and H. E. Moos, Jr., co-op students f r o m PurdueUniversity, assisted in the final editing process.BACKGROUND OF FLIGHT PLANNING FOR MANNED SPACE MISSIONSPurpose of Flight PlansAs the objectives of a flight a r e determined, the flight plan is the means of operational implementation. Using known systems constraints, crew constraints, and operational requirements, the flight planner schedules the crew activities and the major crewand ground-control interfaces.This scheduling function is necessary in the premission phase t o support development of total operations plans, and it continues through the real-time mission operationto accommodate any necessary changes resulting from actual mission events. Reference flight plans for advanced-program missions can s e r v e as systems-design inputsand evaluation toois.The role of flight plans in premission support. - During the premission phase,flight plans are developed to support hardware definition and proper integration of crewcapability into the vehicle design. Flight plans also provide the basis for crew trainingand mission simulations as the program moves into the flight phase.During the mission conceptualization phase, general flight plan studies are oftenconducted to a s s i s t in establishing a realistic program definition and basic program objectives. As the program moves into the hardware design phase, more detailed flightplanning is initiated to verify the operational compatibility of proposed spacecraft s y s t e m designs with mission objectives, to introduce the operational knowledge gained fromprevious programs into the systems design, and to a s s u r e that adequate operating flexibility is provided by the hardware. Studies based on design-reference flight plans include (1) the u s e of hardware for backup and alternate missions, (2) the u s e of hardwaref o r emergency situations, (3) proposed experiment-payload analyses, including estimates of crew time available for experimentation, (4) the effects of trajectory and pointing requirements upon the flight plan, and (5) detailed timelines for u s e in consumablesanalyses.Throughout the hardware design process, the flight plan studies a l s o support detailed crew-integration efforts. The fundamental goal of crew integration is to u s e maneffectively in the space environment. The f o u r basic crew-integration functions a r e(1) determining the operational adequacy of vehicle systems and of the monitoring andcontrol capability required by the crew, (2) identifying and analyzing inflight operations,(3) optimizing the technical and scientific return f r o m missions and the probability ofmission s u c c e s s through application of the capabilities of the crew, and (4) planning andconducting flight crew training. Because the flight plan is the outline of crew activities,it is a most useful tool in all these a r e a s .3
Where vehicle-systems operational constraints a r e not compatible with the totalmission system (the integrated crew-vehicle/ground-control system), these conflictsa r e evaluated for vehicle impact and crew -operations impact. When the crew operations a r e found to be unacceptable, a recommendation f o r design change is made. Thecontext of the recommended design change reflects the minimum hardware change thatis compatible with a safe and sufficient flight activity definition. The latter will havebeen evaluated against the total flight plan and the associated constraints. In somec a s e s of unacceptable crew operations, the hardware -change impact may be extensiverelative to schedules or funds. If the requirement for the flight activity still exists, acomplex compromise must be reached to resolvethe requirement. In this case, the flight planbecomes the focal point of evaluating the alterGeneral datanatives in crew operations, flight operations,and flight definition.Mission objectivesAfter the hardware is developed, the flightplan, a s a means of integrating subsystem p r o cedural s t e p s into flight activity definitions,becomes a primary reference in vehicleintegrated-test design. In many respects, processing of data elements to generate the flightplan is essentially the same systems -engineeringapproach used to generate a detailed t e s t objective. Preliminary versions of lunar -missionflight plans were used extensively in developingthe test plans for the Apollo command-servicemodule (CSM) and lunar module (LM) full-scalethermal t e s t s in the Space Environmental Simulation Laboratory at the NASA Manned Spacecraft Center (MSC).Mission environment dataSystems and engineering dataFlight experience dataOperational constraints1[ent- of basic crew integration dataISimulationsSubsystem proceduresMission operations proceduresSpecialized navigation products1Applied crew integration dataThe evolution of the flight plan and flightdata file on the basis of functional data isshown in figure 1. These data elements do notnecessarily correspond to published documentsbut reflect types of information considered increw integration and flight planning. Followingthe evolution from top to bottom, it can be seenthat each data category is dependent on the p r e ceding category. Further, each data elementwithin a category has independent goals a s s o c i ated with it. The flight planning data-processinggoals are delineated in figure 2.Systems temporal dataIntegrated crew operationsFI iqht definitionIntegrated proceduresFlight plan1Onboard dataFlight data fileIIFigure 1. - Technical evolution offlight plan and flight data file.
IGenera! dataThe use and evaluation of flight Dlansin crew training ana mission simulaiioiis. The first r e a l t e s t of the flight- -plan comeswhen the crew uses it, o r portions thereof,in vehicle simulators and other trainingexercises. The,,, flight planning becomesa n even more iterative process. Crewtraining is the basic laboratory for determining the feasibility of not only the detailed procedures but also the various flighiplan phases.Flight planningoperations at the following c crewintaration dataI11Flight planningWhen the crew has progressed fromsystems training to mission training, theIFliaht Dlanninapreliminary flight plan becomes the guide.i n view ul mlsjion thjectives. !o:-u!a!e !ime-sqx?nce? flightA s the crew trains, the flight planner r e ceives feedback from the crew on the continuity, the o r d e r , and the feasibility ofdifferent p a r t s of the flight plan. DuringFlight planningthis phase, the flight planner must workDocument crewperations information necessary to accomplish thewith the crew to make s u r e that they under;li’hPkI 0111s other items of the fliaht data fllP.stand some operational constraints thatmay not he obvinus, For example: comIOnbcdrd dataImunications with the ground a r e requiredf o r some engineering tests and experimentsFigure 2. - Flight planning informationThis requirement may mean that the test o rutilization.experiment cannot be performed at the optimum time, based on crew workload, butmust be scheduled at a time when a MannedSpace Flight Network (MSFN) station will have contact with the spacecraft. On theApollo 14 mission, the bistatic radar test required not only ground control and monitoring but a l s o specific ground-tracking stations for the processing of data. Also, a p a r tof the flight plan often may seem logical on paper, but a more logical sequence will become apparent when the crew performs the sequence during training exercises.t11IInitial time allocations for activities in the flight plan a r e based on experienceand judgment; but, when the activity is performed in the simulator o r other trainingfacility, the crew may find that the time allotted is more or i e s s than what is required.With this information, the flight planner can add o r delete activities of lower priorityo r reschedule initial events i f necessary and possible, Some scheduled activities arefound to be very difficult or impossible to perform when the crew simulates the activity.The flight planner must either modify the activity so it can be performed o r delete itfrom the flight plan.The final preflight tests of the flight plan a r e the integrated simulations involvingthe crew i n the spacecraft simulators and the ground controllers in the Mission ControlCenter (MCC). Integrated simulations demonstrate how rapidly the ground can r e a c t tocrew problems and how well the ground can provide normally required data. By thetime the integrated simulations a r e reached in the training cycle, the crew has trainedwith the flight plan for a sufficient period of time ir, reveal the major modifications required. The flight plan should be refined to such a point that no major changes in the5
crew timeline sequence of activities result from the integrated simulations. The flightplan is, however, polished to final form as a result of integrated simulations.Flight experience has proven that, unless a major or persistent systems problem occurs, the portions of the mission that are simulated with the crew and the groundcontrollers a r e retained as they were planned. However, many of the interactions ofactivities cannot be determined preflight and, because simulation time is limited andcostly, the crew cannot train for all portions of the mission. The flight planner mustextrapolate from whatever data he can glean from simulations of other portions of themission.Real-time flight planning support. - During a mission, the flight planning andcrew procedures team, headed by the Flight Activities Officer (FAO), supports theFlight Director by monitoring flight plan activities as they a r e performed; by anticipating flight plan problem areas and supervising the preparation of alternate plans; andby monitoring and modifying, as required, overall crew procedures. The flight planning and procedures team also provides attitude information for activities other thanmajor propulsion-system burns. In addition, the F A 0 and his team coordinate miscellaneous scientific inputs into the flight plan. Working with other flight controllers, theF A 0 coordinates procedural changes or new systems tests and schedules them in theflight plan.As spacecraft-systems problems occur, the F A 0 directs the reordering of thecrew activities so the higher priority objectives can be accomplished. The consumables must be monitored, and, if a consumables redline is reached o r approached, a c tivities a r e deleted to allow completion of major objectives. Some problems requirenot only rescheduling of activities but also reworking of mission procedures. The F A 0and his procedures team modify the procedures and provide them to the other flightcontrollers for review. After all flight controllers have agreed on the proposed procedure of flight plan changes, the F A 0 prepares an update to be read to the crew.As indicated by the references to the F A 0 team, real-time flight plan support requires more than one person. The F A 0 is located in the main control room, the M i s sion Operation Control Room (MOCR). Personnel in the MOCR receive detailed supportf r o m many mission-operations personnel located in various staff support rooms. TheFlight Activities Officer's Staff Support Room is manned by other flight planners, selected experiments personnel, procedures experts, navigation experts, simulator instructors, and specialized clerical personnel. The flight planners assist the F A 0 infollowing the mission and monitoring the activities. They suggest operational alternatives, support the preparation of flight plan updates, and assist in tracking the consumables. The experiment-support personnel calculate the attitudes required to supportmission activities, coordinate photographic requirements and procedures, provideMSFN-acquisition times and landmark-crossing times, and act as the interface withthe ground computers f o r any flight plan support.Before the mission, the crew trains daily in the simulators. The simulator instructors, by working with and training the crew, have an excellent opportunity to obs e r v e in detail the individual and collective manner in which the crew executes themission procedures. Therefore, the instructors are most qualified at monitoring thecrew procedures during the mission. Another important capability results if experienced simulator operators a r e available when major procedural changes are proposed6
in real time. When time allows, the instructors can use the MSC simulators to checkthe procedure changes chirhg the m i s s i m befme upcbting the prncedure to the crew.Evolution of Flight Plans Through the Apollo ProgramFlight planning, in parallel with the spacecraft and program objectives, has inc r e a s e d in complexity because of the growth in mission duration and s; x e c r a f t capability and the increase in the number, complexity, and sophistication of the objectivesand vehicle systems.The flight plans of the early manned missions are considerably different f r o mthose of the present, mainly because of the difference in the length of the missions.The short missions of Project Mercury made it more efficient to include in the flightplan, in checklist form, all the details required to accomplish the various objectives.Sample pages of a Project Mercury flight plan a r e shown in figure 3.In the Gemini Program, the number of objectives increased as a function of thelonger duration of the missions and the increase in the capability of the spacecraft.Some objectives were scientific in nature and others were operational evaluations designed t o develop techniques that would be used in the Apollo Program. Constraints,such as trajectory o r s y s t e m s requirements, had to be met, thus resulting in the necessity of performing the objectives over the United States or in the South Atlantic anomalywhere the Van Allen radiation belt phenomenon is encountered, o r the necessity that thespacecraft be powered up f o r attitude information. Still other objectives were constrained by the number of crewmen available, because the staggered sleep cycle (inwhich one crewman slept while the other monitored) was used on several of the Geminimissions. Also, the type of activity that could be performed without awakening a sleeping crewman restricted the objectives that could be accomplished during these periods.Because the Gemini missions were much longer than those of Project Mercuryand had many more objectives, the job of scheduling the objectives and showing enoughdetail in the flight plan to accomplish the objectives became more complex. The nece s s a r y information was too voluminous to be included conveniently in the flight planitself; therefore, an integrated flight plan and flight data file (crew onboard data) syst e m w a s developed. The details of activities such as rendezvous, vehicle activation,o r extravehicular activity (EVA) were included in a checklist separate f r o m the flightplan. On Gemini missions, the flight plan itself indicated when, not how, an activitywas to be performed (fig. 4).The Apollo flight plans evolved into much more detailed documents than either theMercury or Gemini flight plans (although procedural data were still c a r r i e d in thechecklists), primarily because, at certain times, two manned vehicles were involved.This increase in the number of vehicles led to an increase in the number of operationaland s y s t e m s constraints to be considered in scheduling activities. In addition, the complexity of tfie Apollo missions required more detail to assist the crewman in performing7
0Hr:Min00 : 10to00 : 15Cap Sep 330Sec. C h e c k l i s tC o n t r o l SystemsCheck(As required)A-Complete Cap Sep 330 Sec. c h e c k l i s tCheck MP and FBW-NormalReturn t o ASCS O r b i t00:14C Y 1 AOSA-TV camera - ONReport s t a t u s of s y s t e m sGyro s w i t c h - FREE(Ts 5 s e c . c h e c k )(ASCS O r b i t )-00 :21C Y 1 LOS(ASCS O r b i t )A-TV camera00 : 31ZZB(ASCS O r b i t )A-Gyrc s w i t c h - SLAVEReadout f u e l and 0 q u a n t i t i e s200 : 40Short StatusReport(ASCS O r b i tA-Short s t a t u s r e p o r t00:50MUC AOS(ASCS O r b i tA-Blood p r e s s u r eMUC-Emergency v o i c e checkSend end r e s t command f o r check0Off-00:5 8Muc LOS(ASCS O r b i tA-S-band beacon01:05Long S t a t u sReport(ASCS O r b i tA-Long s t a t u s r e p o r t01:10CTN AOS(ASCS O r b i tA-Oral t emperat w e01:27GYM AOS(ASCS O r b i t )A-Give s t a t u sGYM-Give GO-NO GO d e c i s i o nA-TV camera01:282-1 RetrosequencePoint(ASCS O r b i t )01:34MCC AOS(ASCS O r b i t )-GROUND COMMANDONSecond O r b i t0A p r i l 1 5 , 1963Figure 3 .-3-Revision A- Excerpt from detailed timeline of Mercury M flight plan.
0,r :Min0Power Down(Drift)A--ASCS C o n t r o lSELECTCage GyrosPower Down ASCS b u sTV cameraOFFTape r e c o r d e r - PROGRAM-:4 1Twin F a l l V i c t o r yA-C-band beacon-GROUND COMMANDLOS(Drift): 48C Y 1 AOS(Drift)A-TV camera-ON: 54C Y 1 LOS(Drift)A-TV camera-OFF:05ZZB(Drift)A-Readout f u e l and O2 q u a n t i t i e s: 15S h o r t S t a t u s Report(Drift)A-Short s t a t u s report i n t o tapere c o r d e r:25MUC("riftA-Blood p r e s s u r eExerciseBlood p r e s s u r e!: 35Long S t a t u s Report(Drift)A-Long s t a t u s r e p o r t i n t o t a p erecorder:00CAL(Drift)A-Tape r e c o r d e r - CONTINUOUSPower up ASCS Bus: 07MCC AOSA-TV camer
By John W. O'Neill, J. 6. Cotter, and T. W. Holloway Manned Spacecraft Center SUMMARY The purpose of a flight plan is to organize the activities of a mission in a logical, efficient, and safe manner. During the premission phase, flight plans are developed to support hardware definition, to support the integration of the crew and vehicle, and to .
Jan 22, 2020 · Apollo 1050 Apollo 1500 Apollo 1550ETL Apollo 1650 Apollo 1650ETL Apollo 3500ETL Apollo 3600ETL Apollo 633 Control Board Apollo 634 Control Board Apollo 635 Apollo 636 Apollo 7000ETL Apollo 835 Apollo 836 Aprimatic ALZO 55 with Control board T230 A
APOLLO Page 2. APOLLO STAGES (OLD & NEW!)Currently, Apollo Presents takes place primarily on two stages: The Apollo Main stage - A 1,500-seat, state-of-the-art Theater; and The Apollo Soundstage - A flexible, intimate space with audience capacity of up to 175. However, 2020 will bring the Apollo’s o
Speakers, Dim, and Mono functions as well as input and output metering capabilities. Expands Your System Thanks to Apollo Expanded software, users of Thunderbolt-equipped Apollo Twin, Apollo 8, Apollo 8p, and Apollo 16 audio interfaces can combine up to four Apollos and six total UAD-2 devices — adding I/O and DSP as your studio grows.
complete hardware-related details about one specific Apollo model. Included are detailed descriptions of all hardware features, controls, connectors, and specifications. Note: Each hardware manual contains the unique Apollo model in the file name. Apollo Software Manual The Apollo Software Manual is the companion guide to the Apollo hardware .
Apollo std. Apollo lg dia." PTC3 Performance 4 "2 2 OT-Bass 2 2 TH-others" "Trophy Plus Vensura " Cyclone Bay Pro II HR Titan 4 "Ballistic XL Apollo 4 Blade" TRO4 Reliance Turbo 1 "Laser II Vengeance " "SSP Viper " Advantage II New Saturn "Ballistic Apollo std. Apollo
a paragraph table of contents - title section 1 : introduction section 2: summary 2.1 general 2.2 apollo-saturn 201 mission 2.3 apollo-saturn mll mission 2.4 apollo reliability and quality assurance program section 3: apollo-saturn 201 mission 3.1 general 3.2 s-igrrs’i’a -- 3.3 s-ivb-201 stage 3.4 s-iu-201 stage 3.5 spacecraft 009 3.6 3.7 mission re liability analysis
Earth, NASA took several months to investigate and make necessary changes. This delayed the launch of Apollo 14. Also delaying the mission was a decision to move Apollo 14’s target to the original Apollo 13 landing site, Fra Mauro. This changed the mission plan and training regimen for the Apollo 14 crew.
Marketing Materials 39-41 Lesson Plans & Activities 42-50 NGSS Film Tie-ins 51-53 . COMPUTING POWER in your cell phone than the entire computing power for the Apollo 11 program. Technology . Build a promotion for Apollo 10 around the Peanuts cartoon! Apollo 9 - March 3, 1969 Apollo 10 - May 18, 1969 . Charlie Brown & Snoopy
