apollo experience report post flight testing of command modules

8/8/2019 Apollo Experience Report Post Flight Testing of Command Modules

1/17

APOLLO EXPERIENCE REPORT =POSTFLIGHT TESTINGOF COlMlMAND MODULESby Dol~aldT. Humz'ltunLyndon B. Johnson Space CenterHouston, Texas 77058N A T I O N A L A ER O NA U T IC S A N D SPA CE A D M I N I ST R A T I O N W A SH I N G T O N , 0. C 0 SEPTEMBER 1973


2/17

. -1 Report No. f 2 Governmeqt Accession No 1 3 ReciDien?s ca-loq usI INASA T N D - 7 4 3 5

5 !%f?&&%er 1973. Title and SubtitieAPOLLO EXPERIENCE REPORTPOSTFLIGHT TESTING OF COMMAND MODULES 6. Performing Organization Code

7. Author(sJ 8. Performing organization Report No,Donald T. Hamilton, jsc JSC S-36510. Worh Unit No.

9.Perfwming Organization Name and Address 914-11-00-00-72Lyndm B. J o h w n Space Center 1 1 . Contract or Grant No.Houston, Texas 77058

13. Type of Report and Period CoveredTechnical Note2. Sponsoring Agency Name and Address

National Aeronautics and Space AdministrationWashington, D.C. 20546 1 14. Soonsoring Agency Cn+=II15. Supplementary NotesThe JSC Director waived the use of the International System of U n i t s (SI) fo r this ApolloExperience Report because, in hi s judgment, the use of SI Units would impair the usefulness

of the report o r result in excessive cost.~

16. AbstractVarious phases of the postflight testing of the command modules used in the Apollo Programare presented. The specific tasks to be accomplished by the task force recovery teams, theNational Aeronautics and Space Administration Lyndon B. Johnson Space Center, (formerlythe Manned Spacecraft Center) and the cognizant contractors/subcontrctors a re outlined.The means and methods used in postflight testing and how such activities evolved during theApollo Prog ram and were tailored to meet specific tes t requirements a r e described. Actiontaken to resol ve or minimize problems o r anomalies discovered during the flight, thepostflight te st phase, or mission evaluation is discussed.

!7 . Key Words (Suggested by Author!s! Postretrie\r& 18. Distribution StarementPreplanned Test s .Recovery iMission-Anomaly Tests * Baseline

Postflight Te sts * Deactivation* Delta-Baseline * Isolation/QuarantineApollo Spacecraft Hardware Utilization Request

None 1 None 119. Security Classif, !of t h i s report) 1 20. Securitv Classif. (o f this page) I 21. NO. of Pagesj l ? Foreign,$5.25I 22. PriceDomestic, $2.75For sale by he National Techniwi Information Service, Springfield, Virginia 22151


3/17

APOLLO EXPER IENCE REPORTPOSTFLIGHT TESTING OF COMMAN D MODULES

By D o n a l d T. H a m i l t o nLyndon B. Johnson Space CenterS U M M A R Y

Postflight testing was per formed on each Apollo command module. The te stactiviti es we re divided into two genera l types: preplanned tests and mission-anoma,]tests. Preplanned test activiti es included inspections, reco rdin g of configuration, andthe remova l of consumables, data, and equipment. Anomaly testing consis ted of tes tsrequired in orde r to investigate and reso lve flight anomalies. A s pa rt of the missionevaluation effort, postflight testing had to be completed as quickly as possible to allowany required correct ive action to be accomplished without delaying subsequent flights.Postflight testing during the initial series of Apollo flights req uir ed an excessiveamount of time to conduct the tests and to furnish the test results to the mission evalua-tion team. Remedial action was taken, resu lting in the expediting of postflight testingand timely completion of the mission evaluation t a s k s .

INT RODUCT IONPostflight test-ng of the command modules during the Apollo Progra m was inte-grate d with the mission evaluation effort. Most of the testing was accomplished by the

contrac tor and subcontracto rs; however, certain postflight testing activities were per-form ed before shipment of t h e command module (CM) to the contractor facility. Tasksaccomplished on boa rd the r ecovery ship included the inspection and removal of stowedequipment, samples, and data. After off-loading from the recovery ship, the commandmodule was taken to a deactivation site, whe re the pyrotechnic devices were inactivatedand the residual propellants were removed from the reaction control system. Afterthe early lunar-landing missions, which required isolation of the crew and the commandmodule, the command module was held in quarantine at the NASA Lyndon B. JohnsonSpace Cen ter (JSC), orm er ly the Manned Spacecraft Cen ter (MSC), for a prescribedperiod before shipment to the contractor facility . Each asp ec t of pcstflight test ing isdiscussed in this report.

PO STFL I GHT TEST REQU I REMENTSBefore each mission, a Postflight Tes t Requirements Document was prepared.In this document, the activ itie s to be accomplished at vari ous locations during L le post-flight test phase w ere defined. The requirements were derived from the experience


4/17

c

gained from previous flights and fr om the r esu lts of a survey conducted before eachmission to dete rmine the specif ic pro gra m needs of the command module subsystemspecialists..Tasks to be performed that were not specif ied in the Postflight T est Requirements

Document wer e authorized by issuing a n approved Apollo Spacecraft Hardware Utiliza-tion Request (ASHUR) (fig. 1). Before e ach flight, a consolidated ASHUR was p repared

- ~~APOLLO S P AC E CR A FT H AR OW ARE U T I L I Z A T I O N R E Q U E S T

i r b c t c n & f t ~um818 l 1 1 1 1U (1 1 I l f l c I l o I 1 1 U I 1 Y m I l I'IC - 109 l o pF7aster Evcnt Sequencc Controller (MESC)~ Y 1 l l l l To verify the proper operation of the redundant time delay circuits in the MESC,erial number 063596330 BBA.

1 1 1 1 1 f 1 C I t l 0 1The S/C - 109 MESC, serial number 063596330 BBA, contained National Semicon-Iiictor Corporation transistors of the same lot that failed in the S/C - 112 DC seisor.lue t> the system series rediindanc,~ bench functional test must be run to verify that tl'lixht sequencer cmponents are still operating.

_ _ _ _ _ ~l I I C 8 l P 1 l O l_. emove the MESC. ME 301-0567-0023, erial number 063596330 3BA from spacecraft 109CM.!. Ship to the MESC vendor, Autonetics, and run the functional acceptance test.I. Remove tiwe delays which contain the National Semiconductor Corporation transistors(2N2907A).1. Perform leak checks and open transistors. Inspect for contamination, corrosion, andadeqiiate bonds to leads. This may be done at Autonetics with transistor representa-tives present or at transistor vendor.

1 0 I1 1 C C O U P L I 1 1 I O :I: c o m 1 1 c 1 1 0 8 l l I t Y 1H. Peck 213-922-3016 nd H. RodeN R 0 KS C WA S VENDOR 213-922-3743

0 AE C 0 WSC, 0 OTHER f l u 1 1 B 1 1 P 0 1 1 1 1 0 1 I 1 1110.111bnded Storage

T I P I O f I C 1 1 0 8

C O S T C L I W T TEST REWESTiutonetics , Anaheim. Californiat a w t i i n 1'1 I o l l I m l l I r l o m l I 1 1 1E8 8 0 FLIGHT REUSE REOUEST7-3 -1l

C M l i l I r L r y 0111 0 D I S P O S I T I O N R E O U E S T

WSC FORM 1148 ( R E V F E B 6 8 ) (Prsvioua mditima are obaolets),

Figure 1. - Apollo Spacecraft Hardware Utilization Request fo r postflight testing.2


5/17

to specify the disposition of the ite ms stowed in the command module. The ASHURdirected the r ecovery team to remove cer tain it ems while the command module w a s onboard the recovery ship and to retu rn these items by couri er to the MSC. In theASHUR, it was als o directed that various items be removed at the MSC (in the case ofthe th ree lunar landing mis sions fo r which biological isolation of the command modulewas required) and at the contractor facility. Postflight anomaly testing was directedand autho rized by an ASHUR. The Apollo Spacecraft Hardware Utilization Requestswere prepared as soon as the test requirements could be identified by the missionevaluation team and then were forwarded either to the spacec raft contractor or to theresponsible MSC organization.

P O S T F L IG H T T ES T A C T I V I T I E SRecovery and Deact ivation O pera t ions

following1.2.3.4.5.6.7.a.9.10.11.12.1 3 .

The pr imar y activity of the recovery team w a s the preparation of the commandmodule fo r ret urn to the MSC o r to the contractor facility. This activity includedphotographing the command module exte rior and inte rio r, documenting observationsand inspect ions, verifying elect ric al shutdown of the command module, and removingand expediting the r et urn of data and specif ied equipment (fig. 2). Normally, the

' tasks are performed on board the recovery ship.Wash down the exter ior of the command module with fres h waterObtain microbial samples from int erior s urfa cesInspect in teri or and exter ior visuallyPhotograph in terior and exteri orRecord panel readings and switch positionsVerify sys tem powerdownSample potable and was te waterInspect couch support strutsInspect recovery aids fo r prope r deploymentObtain samples of any liquids found on cabin aft bulkheadStow very high frequency (vhf) antennas and flashing lightRemove uprighting bags (if deployed)Perf orm radiation survey

3


6/17


7/17

1Before each mission, postretri eval procedures were prepared f or use by therecove ry team. These procedures were based on the Postflight Test RequirementsDocument. During the accomplishment of the postretrieval procedures on board therecovery ship, a representative o i the mission evaluation team was ava ilable in theMission Control Center to answer questions from the recovery team. The recoveryteam reporte d significant findings and problems to the mission evaluation team andper formed additional activit ies when requested to do so by the evaluation teamrepresentative.

.

During the initial series of recovery operations, the reporting of post ret rievaloperations and observations w a s not sufficiently comprehensive, and information wasnot being made available to the mission evaluation team as quickly as was desired.A f t e r discussions between represen tat ives of the mission evaluation team and the re-covery team, the following procedures were es tablished to res olve the problem. Therecovery t eam provided information, as soon as possible, based on a preflight-prepared list of questions that were of immediate inte res t to the mission evaluationteam. An annotated, post ret rieval procedures document and other data from the r e -covery ship were re turned by cou ri er to the MSC, and copies of this document weremade available to the mission evaluation team.

C o n t r a c t o r O p e r a t io n sMost postflight testing w a s performed by the s pacecr sf t contractor and subcon-tractors.

ducted th ree types of postflight tests: basel ine, delta-baseline, and anomaly tests.Baseline tests were specified in the basic contract and wer e per form ed on each com-mand module, rega rd le ss of the type of mission. The delta-baseline tests were addi-tional test s that were not specified in the basic contract. These tests were peculiar toa particular mission and w e r e neces sary to evaluate specific asp ect s of spacecraft pe r-formance. The delta -baseline tests were identified in the Postflight Test RequirementsDocument, and the contractor was given a contract-change authorization to per formthese tests on each spacecraft.

For the initial series of developmental Apollo mis sions , the contractor con-

The delta-baseline tests were eliminated as the Apollo Prog ram progre ssed, andthe contract was modified to reduce the bas eline-test requirements. The extent of thereduction can be se en by comparing the lists of baseline and delta-baseline tests thatwe re scheduled for the Apollo AS-202 and Apollo 12 missions. These listings ar e con-tained in the appendix. After the delta-baseline tests were eliminated as postflighttest requirements, the pr ima ry purpose of the Postflight Tes t Requirements Documentwas to specify requ iremen ts to be fulfilled by the recovery and deactivation teams(although the contrac tor baseline- te st requirements were still included as genera l in-formation). The anomaly tests required for the invest igation and resolution of mission .anomal ies took precedence Over the baseline tests .

Before each mission, the contractor prepared a schedule of tests and activi ties .(exclusive of anomaly testing) to be accomplished afte r re tur n of the command module.

-ltPostretrievaltw a s the te rm used to indicate that phase of recovery operationsimmediately after recovery of the crewmen and the command module.


8/17

Toward the end of a mission and during the postflight evaluation period , Apollo Space-craft Hardware Utilization Requests were p repared to specify anomaly tests. These- were forwarded t o the contractor, who maintained a daily updated schedule of all r e -quired tests. Changes to the contrac tor test schedule reflected the rel ative priority ofall te st s and ensured that any test conducted to investigate an anomalous condition didnot disturb other anomalous conditions tha t would be investigated at a later time.

The postflight test period at the cont ractor facility extended fr om 30 to 90 days,depending on the number and magnitude of the anomaly tests. One to thre e work shiftspe r day were used, as nece ssar y, to expedite the testing and to provide test data to beused to support the subsequent mission. Spacecraft modifications resulting fromanomalies had to be identif ied quickly to avoid delaying of subsequent flights. Duringthe postflight test period, the contractor was r equired to submit daily sta tus reports.The report s contained a description of work accomplished, re su lt s obtained, and activ-ity projected fo r the next day. Within 2 weeks after completion of each test, the con-tr ac to r was requir ed to submit an Engineering Summary Report. This repor tconstituted the closeout documentation fo r the ASHUR that establi shed the requir ementsfor a par ticu lar test . Copies of the Engineering Summary Report wer e given to theappropriate me mbe rs of the miss ion evaluation team for review and concurrence.

The postflight test ing at the contractor facility included spacecra ft -componentfunctional tests and integrated s yste ms tests. The spac ecra ft automatic -checkoutequipment w a s not used fo r postflight testing because the requ ired postflight testingw a s not as extensive as the preflight checkout. In general , malfunction analyses ofelectronic assembl ies and sy stem components were per for med by the component manu-fac tur ers. The anomaly tests performed on the command module were described inthe individual mission reports. A l l spacecr aft activities were accomplished in accord-ance with quality -assurance pr ocedures. Discrepancies found during postflight testingwere documented on Post Test Nonconformance Records (fig. 3) and wer e processed inaccordance with reliability and quality -as sura nce procedures.

A major problem ear ly in the postflight testing prog ram was that, as a resu lt oflow prioriti es, the time requir ed for processing Apollo Spacecraft Hardware UtilizationRequests, performing tests, and providing the res ul ts to the mission evaluation teamw a s longer than was desirab le. In par ticula r, the contractor had not ar ran ged withthe subcontractors for expediting postflight malfunction analysi s. The problem wasresolved satisfactorily by issuing contract changes, which resu lted in the con tracto rplacing greate r emphasis on postflight testing. The assignment of a re sident NASAengineer to the postflight testing facility was a significant contribution to the establi sh-men t of an opera tion that suppor ted the postflight testing functions adequately.

6


9/17

APPROVAL OF DISPC51TIONnESlGN MANAGER DATE

Figure 3. - Pos t Test Nonconformance Record.M a n n e d S p a c e cr af t C e n t e r O p e r a t i o n s

Postflight testing at the MSC cons isted mainly of evaluating cr ew equipment.Essentially, all equipment stowed in the CM w a s returned to the MSC. The tests per-formed at the MSC or by the equipment contractors included ana lysi s of ha rdware per-formance and investigation of flight problems.

After deactivation operations, the command modules used fo r the Apollo 11, 12,and 14 lunar-landing missions were transported to the MSC and we re placed in quaran;tine in the Lunar Receiving Laboratory (fig. 4) for a pre scr ibed period before beingreturned to the contr actor facili ty for postflight testing. The norm al quarantine pe-riod fo r lunar ma terial w as approximately 45 days; however, the CM could be releasedat t h e same time as the crewmen (21 days after l u n a r lift-off) i f the CM interior wassterilized. The Apollo 11 CM w a s sterilized to make available a maximum of timefor postflight testing at the contractor facility before the scheduled flight of Apollo 12.Based on Apollo 11 experience, the time required for the postflight testing after anormal lunar-landing mission did not warran t a ste rili zat ion effort fo r the Apollo 12

7


10/17

Figure 4 . - Apollo 11 spacecra ft in quarantine at the Lunar Receiving Laboratory.and 14 missions, and these command modules were held in quarantine fo r the full timerequired for lunar material. However, the capability for CM sterilization wa s avail-able if a seri ous missio n anomaly required expeditious retu rn of the Apollo 12 and14 command modules to the contracto r facility fo r testing. The postflight activitie sconducted in the Lunar Receiving Laboratory on the Apollo 11, 12, and 14 commandmodules ar e presented in table I.


11/17

TABLE I. - POSTFLIGHT TEST ACTIVITIES CONDUCTEDINLUNARRECEMNGLABORATORY

~ ~~~

Apollo 11 command module1.2.3.4.5.

6.

7.8.9.

10.11.

12.

13.

14.

15.

16.

17.18.

19.

Photograph e xteri orPerfor m radiation surveyRemove command module umbilicalClean window e xte rio rsConnect ground-support equipmentto exterior test pointsPlace command module behindbiological barrierOpen hatchRecord displays and controlsRemove all stowed equipmentPerform bus isolation checkConnect ground -support equipment

to interior test pointsDrain waste and potable wat ersystems

formaldehydeFill water sy st em s with aqueous

Close hatch and charge cabin withgaseous formaldehyde

Purge cabin of gaseous formalde-hyde after a minimum of 24 hours

Drain aqueous formaldehyde fromwater systemsFlush water systemsVacuum-clean cabin to recoverlunar materialShip command module to con-tractor facility

Apollo 12 and 1 4 command modules1. Photograph exterior2. Perfor m radiation survey3. Pl ace command module behind bio-logical barrie r4. Open hatch5. Record displays and controls6. Remove carbon dioxide ab so rb er s7. Remove data stora ge equipment

tape8. Remove pyrotechnic bat ter ies9. Remove other equipment as re-qu ir ed by ASHUR' s

10. Secure command module and quar-antine area fo r 4 5 - to 60-dayperiod

11. Open biological barrier followingquarantine period12. Open hatch and unstow commandmodule in accordance with

consolidated ASHUR13. Vacuum-clean cabin to recoverlunar material14. Ship command module to the con-

tra cto r facility

9


12/17

All flight equipment returned to the MSC after a mission w a s placed in bondedthe responsible MSC elements for the release of i tems that requi red postflight testing.Then, the necessary testing was accomplished, and the res ult s were reported to themission evaluation team. To illustra te the typical testing performed at the MSC aftera mission, the following Apollo 1 2 tests ar e listed.

. storage. Necessary Apollo Spacecraft Hardware Utilization Requests were prepared by

1. Calibrate experiment S-158 camera system2. Perform failure analysis of color television camer a system3. Per for m radiochemical analysis of CM thermal coating4. Analyze recovered parachutes5. Calibrate and analyze radiation-measuring equipment6. Perform analys is of forward-heat -shield lanyard7. Per form functional tests of biomedical instrumentation8. Conduct anomaly testing of miss ion clock9. Per form preinstallation acceptance tests of lightweight headsets

10. Evaluate inflight exer ci se r11. Conduct anomaly testing of voice recorder12. Examine windows for meteoro id damage13. Calibrate 70-millimeter camer as1 4 . Disassemble and perform analysi s of water sys tem gas -separator car trid ges15. Calibrate and perform analys is of 1 6-millimeter data acquisition camerasystem16. Perfo rm functional tests of vhf/amplitude modulation transceiver, audiocen ter , and digital ranging generator17. Inspect lunar -surface core tubes18. Perform radiographic analysi s of eutecti c-temperature senso rs for lunar -sample -return containers19. Perform analysis of lunar-dust contamination on space sui ts20. Perform functional test of survival rad io


13/17

21. Evaluate lunar hammer22. Conduct stowage tests on fecal bags23. Disassemble and inspect suit- and cabin-pressure transducersSome of these tasks were performed both before and aft er the Apollo 1 2 flight.Follow-on posfflight testing of selected equipment was performed by the contractoror vendors (or both).

CONCLUDING REMARKSPostflight testing was altered to support the postflight testing program as theApollo Prog ram evolved. Test s needed to support the development phases were elimi-nated as the Apollo P rogr am became operational. Subsequent testing w a s orientedtoward anomaly investigations. Te st requir ements w e r e reviewed and rev ised con-stantly throughout the program to maintain maximum effectiveness. Although early in

the program postflight testing was not expedited to the degree necessary to precludepossible adverse effects on ensuing flight schedules, these difficulties were resolvedsatisfactorily. In general, the Apollo postflight test program was well oriented andfulfilled its intended purpose.

Lyndon B. Johnson Space Cente rNational Aeronautics and Space AdministrationHouston, Texas, July 2, 1973914-11-00- 00- 72


14/17

A P P E N D I XBA SE LINE AN D DELTA-BA SELI NE PO STFLIGHT TEST1 NG

AS-202 MISSIONBa se l i e T e s ts

The following baseline tests will be performed on the AS-202 mission commandmodule.1. Perform a visual inspection of the crew compartment, aft heat shield, for-

ward deck areas, window surfaces, reaction control system nozzle extensions, ventoutle ts, umbilical, and any damaged o r unusual -appearing areas.2. Photograph all internal and external areas of the command module. Photo-graph damaged and unusual-appearing areas in detail.3. Verify t h a t all pyrotechnic devices were safed upon re ceip t of commandmodule at the contr actor facility. Remove all unfired pyrotechnic devices, conductbridgewire re sist ance checks, and ship the pyrotechnics to the Manned SpacecraftCenter (MSC) for analysis.4. Sample command module react ion control sys tem fuel and oxidizer sys temsand decontaminate, i f requi red, to obtain a safe tolerance level.5 . Remove aft heat shield to gain acces s to the heat-shield instrumentation.Heat-shield coring will be accomplished in accordance wi th NASA let ters 4475MA,dated March 28 , 1966 , and 1267MA, dated October 20 , 1965 .6 . Remove heat shield and inner side crew hatches; reco rd torque requir ed tounlatch. Visually inspect the latch mechanism and lubrica tion of the hatch mechanisms,and determine i f damage occurred during the mission to the following hatches.

a. Forward pres sur e hatchb. Side acc es s ablative hatch

c. Side acc ess pr ess ur e hatch7 . Visual ly inspect, record , and photograph the positions of all circuit breakers,switches, and dials on the display and control panels.8. Remove al l batteries and inv ert ers, and perform load checks.9. Remove environmental control syst em water/glycol, waste water, and potablewater samples for analysis.


15/17

10. Remove lithium hydroxide cart ridges and ship to the subcontractor fo r anal-ys is. Remove both cartridges from the carbon dioxide canister, and place each sepa-rately in a clean plastic package. Pr io r to removal, the canister shall be inspectedfo r evidence of cartridge crumbling and dusting.

-

11. Remove crew-compartment-heat-shield windows and ship to the contractorfo r analysis. The windows shall be tested in accordance with NASA letter 3639M,dated March 11, 1966.

12. Remove reaction contro l system engines and ac ce ss panels.13. Conduct a visual str uctu ral damage survey.

Delta-Baseline TestsThe following delta-baseline tests will be performed on the AS-202 missioncommand module.1. Perform a bladder and engine-valve leak check on the reaction control system,and record resu lts at the deactivation area.2. Inspect and photograph the astrosextant passive t he rmal protection sys tem.Remove all parts of the system, and assess any damage.3. Perf orm uprighting sys tem checkout in accordance with specificationMA0201 -3122.4. Perform detailed inspection and analysis of the ear th landing subsys tem.5 . Per form leak check on the burs t diaphragms of the reaction control systemrelief valves, and inspect the 1/4 inch helium-isolation valves for contamination.6. Perform a complete functional redundancy test on the mission controlprogramer.7 . Inspect the heat-shield ca lorimeters and pre ssur e se nsors. Remove 2 inch-

diameter core s containing each calorimeter and pressu re sens or from the heat shieldand inspect.


16/17

8. Perform the following measurements on the unified S-band communication. subsystem.a. Output power measurements , high-power modeb. Downlink radio -frequency -spect rum photographs with data as to calibra-tion of spectrum ana lyzer

(1) One with carrier only on uplink(2) One with pseudorandom noise lunar code on uplink

c. Transponder threshold sensitivity9. The high-frequency antenna, if undamaged during the command module re-covery, shall undergo testing, including voltage standing wave r ati o and impedance,

and the re sul ts compared with measureme nts made before the flight.10. The carbon dioxide sens or in the environmental control sys tem shall beremoved from the command module and forwarded to the MSC.11. Determine cause of below -specification per for mance of the environmentalcontrol sys tem water/glycol pump package.12. The 16 heat-shield-pressu re measu remen ts shall be checked for calibration,repeatability, and hysteresis caused by the preflight shift in calibration.

APOLLO 12 MISSIONBa s e l i n e T e s ts

The following basel ine t es ts w i l l be per for med on the Apollo 1 2 mission commandmodule.1. Conduct a visual structural and wiring damage survey.2. Perform a visual inspection of the crew compartment, hatches, thermal pro-tection system, forward deck ar ea s, window surfa ces , reaction control system nozzleextensions, vent outlets, umbilical, and any damaged o r unusual-appearing areas. In

addition, visually inspect the circuit brea ker s, switches, and dials on the display andcontrol panels.3 . Photograph all inte rnal and exte rnal a r eas of the command module. Damagedand unusual -appearing a r eas w i l l be photographed in detail.4 . Remove all pyrotechnic devices.5. Sample command module reaction control sys tem fuel and oxidizer sy stemsand decontaminate, if required, to obtain a safe tolerance level.


17/17

6. Remove aft and crew compartment heat shields, and arrest corrosion.7 . Remove all bat ter ies and place in cold storage.8. Remove two samples from each environmental control fluid system; retain

at the contr actor facility fo r analysis. Drain, purge, and dry all environmental con-tr ol system fluid systems. Measure the amount of potable and waste water removed.9. Remove the entry monitor syste m scr oll assembly and forward to the con-tracto r f or removal of the scroll. The scr oll shall be reproduced and two copies for -warded to the MSC fo r the attention of the Test Division.

10. Make the command module available for the MSC personnel to clean theheat-shield windows and to perform a micrometeoroid survey.be removed fo r this task. The windows will not

Delta-Baseline TestsNo delta-baseline tests a r e required on the Apollo 1 2 mission command module.

NASA-Langley, 1973 1 S-365 15

apollo experience report post flight testing of command modules

Documents