UAH Archives, Special Collections, and Digital Initiatives

Browse Items (6320 total)

  • systrainman_071707122502.pdf

    Prepared through joint efforts of Personnel Department, Education and Development Branch, Systems Training Unit, Michoud Operations and Engineering Communications Department, Technical Information Branch, Applied Communications Engineering Section, Huntsville Operations.; This publication presents a brief descriptive summary of the Saturn IB vehicle and Chrysler's Corporation's accomplishments in the missiles and space field. The Saturn IB information presented herein is based on current plans for each of the stages. Although there may be design changes from vehicle to vehicle, the basic components, systems, and operating principles will remain similar to previous models.
  • systengrprop.pdf

    Page numbering is inconsistent; there are no pages numbered 14 - 17. Some pages have handwritten numbers, others have no numbers at all.; The print quality of many pages is poor. Discusses the definition and function of propulsion as well as how to most effectively employ it .
  • systdescforsatuvehicle_030807135800.pdf

    Missing pages iv, 3, 6 to 8. Photocopy of files containing sections of the project.
  • Systappl_122007135157.pdf

    The objective is to examine the technical requirements and feasibility of conducting orbital launch operations with systems now in the development phase. In order to maintain realistic constraints on the analysis, the Saturn S-IVB stage has been used as an example of present stage technology. The requirements, procedures and complexity of operations for orbital assembly and launch are discussed. The primary design requirement for orbital assembly and launch operations is increased orbital stay time (from hours to days or weeks).
  • survpropprob_060607132313.pdf

    Incomplete document. Displays errors in space-vehicle design as they relate to space travel.
  • survofsatustagtest.pdf

    This survey of the Saturn Stage Test and Checkout Computer Program Development contains a summary description of the systems developed for factory and static test of the stages of the SATURN IB and SATURN V Vehicles. The responsibilities of the MSFC and stage contractor organizations that are involved in test and checkout computer program development are briefly described. The test and checkout hardware and software (computer program) systems are given for each stage and for each site where tests are conducted. The systems and procedures that are used for program production verification, documentation, and change control required for the implementation of planned computer programs are included. Notes are included in the report to indicate what material is missing or incomplete. No attempt has been made to draw any conclusions regarding the automatic test and checkout systems being developed for each stage and the manner in which the efforts are organized, scheduled, and implemented. This document has been based on material provided by stage contractors and by components of MSFC through May 1, 1966. COMPUTER SYSTEMS SECTION. VEHICLE SYSTEMS INTEGRATION BRANCH. VEHICLE SYSTEMS CHECKOUT DIVISION.; SR-QUAL-66-3.
  • Suppmontprogrepo51966_091907130743.pdf

    Monthly progress report for the Propulsion Division, May 1st through May 31st
  • Suppmontprog0466_101707120811.pdf

    Monthly progress report for the Propulsion Division, April 1st through April 31st
  • Summofmajonasa_041309110826.pdf

    This is the first Quarterly Supplement to the October 1968 edition of GP 381, ''A Summary of Major NASA Launchings (Eastern Test Range and Western Test Range)." This Supplement covers the period from October 1 to December 31, 1968. Two additional Quarterly Supplements will be issued during 1969. Each of these will list those major NASA launchings occurring during the three-month period it covers. The basic publication will be revised and reissued, incorporating the information contained in the Supplements, as well as covering the final three-month period, subsequent to October 1, 1969. William A. Lockyer, Jr.
  • StruoftheNASA_052410122627.pdf

    Describes the structure and function of each part of the NASA Lunar Module
  • strucproblgspaceboos_071107101629.pdf

    Report discussing the flaws in having large rocket boosters.
  • StattestsatuV_091007125622.pdf

    Report after second Saturn V flight test.
  • statsmodforsaturn_012508122337.pdf

    This report presents the logic leading to a mathematical expression for mission availability. Mission availability is treated as the probability that the cumulative downtime occurring during a mission of given length will be less than the time constraint. This is opposed to more general approaches such as steady state or instantaneous availability or operating time versus real time. We intend to present a practical and usable mathematical model by deduction and demonstration. The development is based on exponentially distributed downtimes. Experience shows that certain systems follow exponential downtime distributions except near zero. This error is often so small that it may be neglected. A future report will present a downtime distribution which will account for this small error.
  • thehisofarmmisdev_121707120332.pdf

    Published as "Army Missile Development," Army Information Digest, XI. Establishes the development and history of weaponized rocket ordenance.
  • theeasofimpofthesafproatthemarspaflicen_071107091611.pdf

    Presented at the 19th Annual Federal Safety Conference, National Safety Congress, Chicago, Illinois. A rundown of the new safety protocols, chiefly favoring the letter 'E.'
  • thedevofaboncombulforsat_090707133327.pdf

    A Part of the development of the Saturn S-IV/S-IVB stage the Douglas Aircraft Company has pioneered in the development of the cryogenic common bulkhead. The term common bulkhead is derived from the design function of the bulkhead, which is to separate the two cryogenics, liquid hydrogen and liquid oxygen, in a single tank, thereby shortening the stage and eliminating the necessity for two separate bulkheads and the associated interstage structure. The common bulkhead is structurally adequate to withstand both the thermal and the pressure loads from both the hydrogen and the oxygen tanks, and it has sufficient insulation properties to prevent the liquid hydrogen from freezing the liquid oxygen. Another benefit from the common bulkhead is that it permits a reduction in the total length of the vehicle, thereby reducing the bending moments.
  • Thedeveofacheclangatol_110907113826.pdf

    ATOLL was developed to fulfill the requirements for a common computer language that could be used by the test engineers for launch and factory checkout. "ATOLL" is the abbreviated name for Acceptance, Test, Or Launch Language.
  • Testprocvalidbycompsimulation_071508150442.pdf

    Digital computer simulation of the Saturn I Instrument Unit electrical networks was accomplished using the Discrete Network Simulation programs. The schematics were analyzed and a logic model prepared which consisted of a series of Boolean equations. The test procedures, which are written in the Acceptance, Test, or Launch Language (ATOLL), consist of a sequential set of computer instructions for the RCA llOA checkout computer to control the operation of the electrical networks. The procedures also contain the predicted results for each operation. The driving functions for the simulation of the model are generated from the ATOLL test tape by the Input Generator Program. The time sequenced operation of the networks is indicatedby the output from the simulation program in addition to the number of times each component in the system changes state. The results of the simulation are compared to the test procedure predictions on the ATOLL tape by the Comparator Program and any differences are listed. The Comparator Program also lists any component which did not change state at least once.
  • Testoperorgachar_120408111035.pdf

    Organization Chart of the North American Rockwell Test Operations.
  • TestlabprogrepOCT_041808091527.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates October 1st through October 31st, 1967. Page 17 missing.
  • TestlabprogrepDEC_051408095158.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates December 1st through December 31st, 1967.
  • TEstlabprogrep3_032408084650.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates July 1st through July 31st, 1967.
  • TEstlabprogrep2_031008111252.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates August 1st through August 31st, 1967.
  • Testlaboprogrepomay121966tojune121966_110107111326.pdf

    Monthly rogress report for the test laboratory regarding the Saturn 1B program between Feburary and March
  • Testlaboprogfeb1966_083007095938.pdf

    Monthly rogress report for the test laboratory regarding the Saturn 1B program between Feburary and March
  • Testlabomontprog_011608112625.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates Febuary 1st through Febuary 31st, 1967.
  • Testlabmontprogrep_021108103845.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates April 1st through April 31st, 1967. Last page of document is missing.
  • TestlabmonproJUNE_032808134023.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates June 1st through June 31st, 1967.
  • Testlabmonprogrep_041008104724.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates September 1st through September 31st, 1967.
  • TestlabMON_JAN_062308120607.pdf

    Laboratory monthly progress report for the Saturn 1B program between dates January 1st through January 31st, 1968.
  • teslabprorepmar121966toapr121966_091407131635.pdf

    Monthly rogress report for the test laboratory regarding the Saturn 1B program between March and April.
  • telsysdesforsatveh_110907094526.pdf

    This paper discusses the data system requirements for large space vehicles and describes a flexible telemetry system design which is used on all stages of the Saturn IB and Saturn V vehicles. The basic vehicle telemetry design provides standard assembly building blocks forming a versatile catalogue of parts from which a stage telemetry subsystem may be assembled to meet almost any conceivable monitoring requirement. In addition to its inflight monitoring function, the telemetry subsystem also provides real time data acquisition for automatic vehicle checkout.
  • telmesinsreqforsII1andsII2_020408135342.pdf

    Photocopy of an inspection list requirements for S-II-1 and S-II-2.
  • telesystforsatus-istagdeve_032107081755.pdf

    The telemetry system used on the Saturn S-I stage for the transmission of vehicle test data is described. Multiplex and modulationtechniques such as PAM/FM/FM, SS/FM and PGM are used in the system. The diverse data requirements for developing the eight-engineliquid-fueled stage necessitated the use of a combination of severalmodulation techniques to efficiently handle the data. A cursory comparisonis made of the merits of each technique. Physical and electricalrequirements and characteristics of the system are outlined.
  • Teledire-1965.pdf

    Telephone directory belonging to the George C. Marshal Space Flight Center Mississippi Test Facility for October 1965.
  • Teldirgeocmarspaflcenmistesfac_091008121715.pdf

    Telephone directory belonging to the George C. Marshal Space Flight Center Mississippi Test Facility for 1968.
  • TechsurvABMA_111808164326.pdf

    Handwritten notes on the document.; Archive copy is a poor photocopy.
  • techrpts_051107091113.pdf

    Bibliography of technical reports from 1957-1963
  • uprsatIBquafilrepandrelmatfilsciforsatquafilrepno14_071007103243.pdf

    Film script reporting on how the Saturn 1 will be used and what its take-off process will look like
  • uprsatIBquafilrepandrelmatfilsciforsatquafilrepno13_071007102648.pdf

    Film script reporting on how the Saturn 1 will be used and what its take-off process will look like
Output Formats

atom, csv, dc-rdf, dcmes-xml, json, omeka-xml, rss2