<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://digitalprojects.uah.edu/items?output=omeka-xml&amp;page=8&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-13T01:38:39+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>8</pageNumber>
      <perPage>20</perPage>
      <totalResults>8242</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10399" public="1" featured="0">
    <fileContainer>
      <file fileId="9103">
        <src>https://digitalprojects.uah.edu/files/original/20/10399/Skyrwritermay1669_121310160610.pdf</src>
        <authentication>076c90a2744af488938110e4b4ace376</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="156007">
                <text>Skyrwritermay1669_121310160610.pdf</text>
              </elementText>
              <elementText elementTextId="156008">
                <text>spc_stnv_000805</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156009">
                <text>"All systems 'go' for liftoff  of Apollo 10."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156010">
                <text>News article detailing that the final preparations for the lift-off of the Apollo rocket have been completed.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156011">
                <text>Elliott, J. S.</text>
              </elementText>
              <elementText elementTextId="156012">
                <text>North American Rockwell Corporation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156013">
                <text>1969-05-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156014">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156015">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="156016">
                <text>Aerospace industries</text>
              </elementText>
              <elementText elementTextId="156017">
                <text>Periodicals</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156018">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="156019">
                <text>News Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="156020">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="156021">
                <text>Box 31, Folder 34</text>
              </elementText>
              <elementText elementTextId="210209">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156023">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156024">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="156025">
                <text>spc_stnv_000800_000824</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156026">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18117</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3311" public="1" featured="0">
    <fileContainer>
      <file fileId="2555">
        <src>https://digitalprojects.uah.edu/files/original/76/3311/loc_burw_-105.pdf</src>
        <authentication>3d384ee284760a803ffe6b84815ade28</authentication>
      </file>
    </fileContainer>
    <collection collectionId="76">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="28299">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="28300">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="133718">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/145" target="_blank" rel="noreferrer noopener"&gt;View the Burwell Family Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="133721">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3332" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1943-1944&lt;/a&gt;</text>
                </elementText>
                <elementText elementTextId="133722">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3333" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1944-1945&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="90">
              <name>Provenance</name>
              <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
              <elementTextContainer>
                <elementText elementTextId="133723">
                  <text>Materials donated and digitized by Dudley Burwell</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="65152">
                <text>loc_burw_000105</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65153">
                <text>"Allotment Discontinuance-Notice Upon Discharge or Release from Active Duty&#13;
".</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65154">
                <text>Goldsmith, Jack</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65155">
                <text>2/18/1946</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="65156">
                <text>1940-1941</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65157">
                <text>Burwell, Edwin D., Jr.</text>
              </elementText>
              <elementText elementTextId="65158">
                <text>United States. Army</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65159">
                <text>Forms (Documents)</text>
              </elementText>
              <elementText elementTextId="65160">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="65161">
                <text>Burwell Family Collection</text>
              </elementText>
              <elementText elementTextId="206668">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65163">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65164">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="65165">
                <text>loc_burw_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10434" public="1" featured="0">
    <fileContainer>
      <file fileId="9117">
        <src>https://digitalprojects.uah.edu/files/original/20/10434/scan0017rev_080107122437.jpg</src>
        <authentication>714043e292e924b02f314ce1b1b8be86</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="156733">
                <text>scan0017rev_080107122437.jpg</text>
              </elementText>
              <elementText elementTextId="156734">
                <text>spc_stnv_000790</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156735">
                <text>"Alloy designation" Table.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156736">
                <text>8 x 10 inch black and white photograph that displays a table of two elements and their molecular makeup.  Table includes the alloy of LA-141 and LAZ-933.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156737">
                <text>George C. Marshall Space Flight Center. Propulsion &amp; Vehicle Engineering Laboratory.Metallurgical Analysis Section.  Materials Division, Metallic Materials Branch.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156738">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156739">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="156740">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="156741">
                <text>Liquid propellant rockets--Materials</text>
              </elementText>
              <elementText elementTextId="156742">
                <text>Space vehicles--Materials</text>
              </elementText>
              <elementText elementTextId="156743">
                <text>Alloys</text>
              </elementText>
              <elementText elementTextId="156744">
                <text>Spacecraft construction materials</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156745">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="156746">
                <text>Photographs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="156747">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210244">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="70">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="156749">
                <text>Is referenced by:  Materials in space exploration.;  Is part of: Envelope - Photos Accompanied C. E. Cataldo paper "Materials in space exploration".</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156750">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156751">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="156752">
                <text>spc_stnv_000775_000799</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1143" public="1" featured="0">
    <fileContainer>
      <file fileId="990">
        <src>https://digitalprojects.uah.edu/files/original/20/1143/spc_stnv_000059.pdf</src>
        <authentication>beba84b6e41e32c88a0b78d7553b40ee</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177277">
                    <text>:;x,

Douglas Paper 3172

SATURN H:STORY DGC~.JMENT
Univcisit-y of Alcbens Re-nrlrch institute
History of Science &amp; Technology G r o q

Date

----------

Doc.

No.

--------

ALTITUDE SIMULATION I N SATURN SIV STAGE TESTING
Prepared By:
D . D . HOFFERTH
Branch Chief
Field Development Engineering
Sacramento Test Center
Sacramento, California

E. L. WILSON
Branch Chief
Space Propulsion Branch
Missile &amp; Space Systems Division
Huntington Beach, California

A . L.

POLANSKY
Design Engineer

Space Propulsion Branch
Sacramento ~ e s Center
t
Sacramento, California
Presented To:
Society of Automotive Engineers

DDUGLAS /M/SS/LE &amp;: SPACE SYSTEMS D/V/S/UN

/

�ABSTRACT
Altitude Simulation i n Saturn SIV Stage Testing

The Douglas Aircraft Company has been invoived i n testing
the Saturn SIV stage at the Sacramento Test Center for the
past two years. The propulsion system for the SIV stage consists
of six (6) Pratt &amp; Whitney Aircraft Company rocket engines
0

which are designed specifically for high altitude start and
operation.

During static firing tests of this engine a t sea

level, a steam jet ejector in combination with a diffuser,
are used to simulate altitude conditions,

The intent of this

paper i s to examine the performance of this altitude simulation system, and to discuss problems encountered i n making
i t operational.

�The Douglas Aircraft Company has been involved i n testing the Saturn

S I V stage a t the Sacramento Test Center for the past two years. The SIV i s
an upper stage of the National Aeronautics and Space Administration's Saturn
Space Vehicle.

A later version of the Saturn Space Vehicle i s programmed to

launch an Apollo to the moon.

The propulsion system for the SIV stage consists

o f six (6) Pratt 8, Whitney Aircraft Company RLIOA-3 rocket engines capable
of generating a total of 90,000 pounds thrust a t as titude (Figure 1).

These

engines were designed specifically for high altitude start and operation and,
therefore, require an altitude simulation system to permit sea level static
testing.

The normal starting altitude of the Pratt &amp; Whitney

RLlOA-3 engine,

when used as part of the SIV stage, i s approximately 240,000 feet, where the
expected absolute pressure i s

0.17 psia.

I t i s not required that this low a pressure be obtained for sea level
testing, however, The engine requires sufficient pressure drop between the
liquid oxygen pump inlet and the combustion chamber to attain a pre-start flow
o f liquid oxygen.

This flow must be sufficient to cool the pump so that stall free

acceleration and mainstage operation can be achieved.

The time interval required,

as w e l l as the quality and quantity of liquid oxygen required, had to be established
during static testing.

Even more basic, however, i s the requirement that the high

expansion ratio (40: 1) thrust chamber bell be operated without flow separation.

If the engine were operated a t sea level back pressures, separation would occur,
,

w i t h attendant structural and performance degradation.

The engine bell construction

�The Douglas Aircraft Company has been involved i n testing the Saturn
SIV stage at the Sacramento Test Center for the past two years.

The SIV i s

an upper stage of the National Aeronautics and Space Administration's Saturn
Space Vehicle.

A later version of the Saturn Space Vehicle i s programmed to

launch an Apollo to the moon. The propulsion system for the SIV stage consists
of six (6) Pratt &amp; Whitney Aircraft Company RLIOA-3 rocket engines capable
of generating a total of 90,000 pounds thrust at altitude (Figure 1).

These

engines were designed specifically for high altitude start and operation and,
therefore, require an altitude simulation system to permit sea level static
testing.

The normal starting altitude of the Pratt &amp; Whitney RLlOA-3 engine,

when used as part of the SIV stage, i s approximately 4240,000 feet, where the
expected absolute pressure i s 0.17 psia.

It i s not required that this low a pressure be obtained for sea level
testing, however.

The engine requires sufficIant pressure drop between the

liquid oxygen pump inlet and the combustion chamber to attain a pre-start flow
of liquid oxygen.

This flow must be sufficient to cool the pump so that stall free

acceleration and mainstage operation can be achieved.

The time interval required,

as well as the quality and quantity of liquid oxygen required, had to be established
during static testing.

Even more basic, however, i s the requirement that the high

expansion ratio (40:l) thrust chamber bell be operated without flow separation.

If the engine were operated at sea level back pressures, separation would occur,
,

with attendant structural and performance degradation.

The engine bell construction

�was intended for altitude operation and thus not designed to withstand the

high

loads which would be encountered i n sea level operation.
The total altitude simulation system u t i l i z e d i n the

SIV stage static testing

(1) the diffusers, (2) the eiectors, (3) the

i s comprised of four elements:

accumulators, and (4) the steam boilers and 'feed water system (Figure 2).
The diffusers are attached to each of the six engines w i t h a flexible
seal, and are closed a t the opposite end by blow-off doors.

In this configuration

they serve as a vacuum chamber to provide low ambient pressures (less than 0.9

psis) i n

the forty-five (45) second period up to and including engine ignition.

By controlling the engine exhaust gas flow through internal geometry, the
diffusers also sustain the required absolute pressure a t the engine bell e x i t
after the engine start transient.

The diffusers are approximately thirty-five (35)

feet long, and are of double w a l l construction to provide for water cooling.
The wal I s are fabricated from low carbon steel and are spaced one-fourth inch
apart to accommodate a cooling water flow rate of approximately 3100 gallons
per minute per diffuser.
Each diffuser i s connected to a two stage steam jet ejector system w i t h a
thirty.(30) inch vacuum line.

A pneumatically operated butterfly valve i s

installed i n this vacuum line to permit isolation of the eiectors from the diffusers.
The i n i t i a l purpose of this isolation was twofold:

(1) to prevent hot gases from

the diffuser being sucked through the eiectors just after engine ignition, and

(2) to prevent aspiration of a i r through the ejector and into the lower end of the
diffuser during normal engine operation, where after-burning would cause high

�temperatures and resultant damage to the diffusers.

...

These butterfly valves

were also found to be of value in the sequencing of ejector operation with
respect to the diffuser during the initiation of vacuum pumping.
Each stage of the two stage ejector i s thirty (30) feet long, and they
are assembled together i n a vertical array on the front of the test stand
(Figure 3).

The first stage suction chamber i s at the level of the diffuser

vacuum line.

Steam reaches the second stage ejector without intervening

valves between them and the constant pressure steam regulators.

The first

stage steam lines were provided with intervening three-inch valves to permit
delaying the entrance of steam into the first stage ejectors until the second stage
had established a partial vacuum throughout the system.

I t was learned early i n

testing of the altitude system, however, that this delay was not necessary
inasmuch as no significant change i n vacuum pull-down characteristics were
encountered with simultaneous admission of steam to both ejector stages.

Mani-

folding for delivery of steam to both stages of the ejectors i s supplied through .
an eighteen (18) inch steam line from the constant pressure regulators i n the
accumulator area.
Two thirty thousand (30,000) gallon capacity steam accumulators serve
as storage vessels for the steam energy used to power the ejectors.

These vessels

are half-filled with water, and when charged, hold heat i n this water a t 406'~.

he

upper half of each accumulator contains steam a t 406'~ and 250 psig pressure.

To insure optimum performance of the eiectors, motive steam i s supplied from the
accumulators a t a constant pressure.

his 'is accomplished by the use of constant

�pressure regulators (one for each accumulator), which maintain 135 psia at the
ejector nozzles.

The regulators are of the twelve (12) inch, 90' angle valve

type, and are commanded open and closed by the automatic SIV stage firing
sequence.

The actual opening travel of the regulating valve i s controlled by

high pressure water from the accumulators.

This controlling water i s regulated

as a function of the pressure i n the eighteen (18) inch steam line.

The opening

travel of the poppet i n the constant pressure regulators then increases as the
accumulator pressure falls off during a test run.

A boiler of 250 BHP capacity i s used to produce 8625 pounds per hour of
dry and saturated steam a t 250 psig for charging the steam accumulators.
'

The

process of charging the accumulators requires approximately twelve (12) hours.
The "packageu boiler i s o i l fired, and i s automatically actuated with boiler
steam pressure. The normal supporting systems for operation of a steam boiler
are part of this complex area, which includes the feedwater system, deaemtor,
blow down tank, and o i l storage tank.
The design specifications for the steam supply system and ejectors of the
altitude simulation system were established as a function of the Pratt &amp; Whitney
RLIOA-3 engine.chilldown flow rates during the period prior to engine ignition.
The internal convergent-divergent geometry of the diffusers was established using
the parameters of engine combustion products flow during firing operation to
assure a sustained pressure of 3.0 psia or less at the engine bell exit.
The Pratt &amp; Whitney RLlOA-3 engine utilizes liquid oxygen and liquid
hydrogen as propellants.

Since both of these propellants have very low boiling

�temperatures (-297'

and -423O~, respectively), each pump must be chilled to

essentially its respective liquid boiling point to assure that at engine ignition
liquid w i l l be present at the pump inlet and not gas, since gas would cause
pump cavitation.

To accomplish adequate chilldown of' the liquid hydrogen

pump a t sea level requires forty-five seconds of time, during which gaseous
hydrogen i s 'dumped into a stand vent system, and carried off to a burn stack.
During the last ten (10) seconds of this forty-five (45) second period, the liquid
oxygen pump i s simultaneously being chilled down, and dumping approximately
2.0 pounds per second of first gaseous and then as chilldown proceeds, liquid
oxygen into each diffuser.

These gases must be carried out'bf each diffuser

while continuously maintaining a pressure of 0.9 psia or less. The low pressure
i n the diffusers during chilldown i s required to provide the proper pressure drop
between the engine pump inlet and the engine combustion chamber or diffuser
to assure the

chilldown propellant flow rates.

Operation of the altitude simulation system i n conjunction with the Pratt
&amp;,Whitney engine starting sequence was of such critical nature that control of
the system was integrated into an automatic engine firing logic. As i s shown
on Figure 4, the base for the timing of logic events was established with time

T=O occuring at engine start command. A t T-60 seconds or fifteen (15) seconds
prior to initiation of the firing logic, the manually switched sequence of starting
three (3) electric motor-driven water pumps and opening of the deflector plate
water: valve i s started.

This timing assures full water flow through the cooling

water jacket of the diffusers, as well as full water flow for deflector plate

�cooling by engine start command.

The automatic engine f i r i n g logic i s

initiated a t the beginning of LH chilldown which i s forty-five (45) seconds
2
prior to engine ignition, or

T-45 seconds. Simultaneous w i t h LH2 chilldown

initiation, both the constant pressure regula toss and the first stage ejector
steam valves are opened to begin the vacuum pumping action w i t h the diffuser
butterfly valves closed.

Ten

(10) seconds later, a t T-35 seconds, the diffuser

butterfly valves are opened, and the diffusers are evacuated to approximately

0.5 psia by pumping action from the operating ejectors. To provide feedback
information to the automatic engine firing logic that the altitude simulation
system i s functioning properly, specifically that the differserapressure i s a t
or below 2 . 5 psia, pressure switches set to pick up a t 2.5 psia are installed
on each diffuser.

The picked-up talkback i s required from a l l six of the

diffuser pressure switches by

T-10 seconds to enable the logic signal commanding

the start of the liquid oxygen pump chilldown.

I f these talkbacks are not a l l

received, a hold i s automatically imposed i n the logic.

The d i f f i c u l t y must then

be isolated and corrected before a recycle of the sequence can be performed.
At

T-0 seconds the logic signal for engine ignition i s given, and the first stage

ejector steam valves are closed.

After successful engine start i s achieved a t

approximately T+2.4 seconds, as indicated by proper signals from each of the
engines, the altitude simulation system i s automatically shut down by simultaneously
closing the constant pressure regulators, and the diffuser butterfly valves.
steam jet ejector system no longer operating, a pressure of less than

With the

1.0 psia (3.0 psia

maximum allowable) i s sustained a t the engine bell e x i t until engine cutoff, by the
pressure physics of engine exhaust gas flow controlled by internal diffuser geometry

�The actual data for diffuser operation during the acceptance firing of
the f i f t h Saturn stage, the

SIV-5 Vehicle, at Sacramento (Figure 5) shows

typical performance values.

As can be seen, approximately five (5) seconds

after the butterfly valves were opened
than

-

by

T-30 seconds, a pressure of less

1.0 psia had been achieved i n each diffuser. This pressure was held constant

until engine ignition, a t which point the diffuser pressure began to increase as
the engines proceeded through their normal start transient and engine combustion
chamber pressure increased.

The pressure increase continued until

T+2.0 seconds,

when i t changed slope sharply, and caused the diffuser blow-off doors to be carried
The pressure returned immediately then to less then 1 .O psia, and was rut-

away.

tained a t this value until engine cutoff occurred at T+477.5 seconds. With engine
cutoff, the pressure i n each of the diffusers returned to ambient within one (1)
second.
Having discussed i n general terms the hardware elements of the altitude
simulation system, and having reviewed typical performance data of the system as
gathered during Saturn SIV-5 Vehicle firing, i t i s appropriate that some of the
problems encountered i n achieving the present level of performance be discussed.

As i t was. stated earlier, constant pressure regulators were installed a t each
accumulator, to provide steam a t

135 psia to the ejectors for optimum performance

of the ejectors i n vacuum pumping.

Since the total duration of the steam eiector

system operation for each test was only f i f t y (50) seconds, severe dynamic demands
were,imposed on the constant pressure regulating system.

Because of the mass of the

moving elements i n the twelve (12) inch, 90' globe valves, which were the regulating

�devices i n the steam line, time restrictions had to be imposed on opening and
closing speed.

This mass also caused overshoot difficulties which would not

have been a problem i n an "on the line" system which was the application for
which these regulators were designed.
To understand the specific difficulty and how i t was corrected i t i s
necessary to examine the elements of the constant pressure regulating system
(Figure 6).

For simplicity only one system i s shown, although i t was duplicated

for each accumulator.

The constant pressure regulator was operated i n its

opening cycle by a regulated, constant bleed, wafer system which sensed the
pressure i n the eighteen (18) inch steam line as its controlling function.
water was obtained from the bottom of the accumulator.

The

The force of water

on the opening side of the constant pressure regulator actuating piston was
counterbalanced by a controlled source of gaseous nitrogen.
On command from the automatic engine firing logic, at T-45 seconds,
for steam to be supplied to the ejectors, an electrical signal caused the
shutoff valve i n the water regulating system to open.

This permitted high

pressure water to reach the opening side of the actuator on the constant
pressure regulator, driving i t 'open, and a t the same time compressing the
gaseous nitrogen on the upper side of the actuating piston.

The pressure

increase i n the eighteen (18) inch steam line was sensed and fed back to
the water regulator which began to close down the water shutoff valve, and
thence the water flow to the opening side of the actuator.

Thus the constant

pressure regulator reached that position which would supply steam to the
ejectors a t 135 psia

.

�1

I n the original installation cooling coils were provided i n the water line to
the water regulator to assure that high pressure water without entrapped steam would
be available for motive force at the actuating piston of the constant pressure regulator.
I t was quicltly discovered, however, that the change i n pressure a t the regulated
water shutoff valve caused the water to flash to steam.

This condition caused the
\

constant pressure regulator to be driven f u l l cycle open to closed and back to
open, and rendered the water regulating system ineffective i n establishing a
constant steam pressure.
To assure that cool water was always available to the regulating system, a
one hundred (1 00) gal Ion water tank was added downstream .of the cooling coils.

This f i x worked effectively and permitted additional testing of this system which
established that the response of the constant pressure regulator to i n i t i a l overshoot
was too slow.

Specifically, the range of pressure during the overshoot was 180

psia to 200 psia, and the time from the open command signal until stable pressure
was achieved was approximately sixty (6C) seconds. Since only forth-five (45)
seconds of steam system operation were required, this system transient was
unacceptable.

The d i f f i c u l t y was f i n a l l y traced to excess volume i n the water

regulating system, which caused excessive time for the water to be bled off and,
therefore, slow response of the constant pressure regulator to the overshoot.
When the volume of the water system was reduced by short coupling the elements
of that system to the constant pressure regulator, this problem was solved and acceptable
performance was .achieved.
system i s shown i n Figure

7

A composite of typical data from the altitude simulation
Note that the magnitude o f overshoot i s approximately

�170 psia

- not significantly changed from the 180 to 200 psia level - but that

stable pressure regulation i n the eighteen (18) inch steam line i s achieved w i t h i n
thirty (30) seconds of the open command.
During the i n i t i a l static tests of the Saturn

SIV Vehicle a t the Sacramento

Test Center, an aluminum blow-off door was used as the closure on the diffusers.

This door weighed approximately one-hundred and twenty (120) pounds, and was
held i n place a t the lower end of the diffuser by four (4), four hundred (400)
pound pull magnets.

The blow-off doors remained i n place on the diffusers

prior to engine start, and were then ejected from the diffusers at engine start
as the chamber pressure increased.

Because of the force w i t h which the doors

were ejected, some damage was always sustained as they contacted w i t h the test
stand flame deflector plate.

Experience quickly established that the aluminum

doors could usual l y be repaired for use a second time, but that repair beyond this
point was not practical.

The high usage rate of aluminum doors, and high i n i t i a l

cost coupled w i t h the cost involved i n the repair operation, created the incentive
for fabrication of fiberglass doors.
Testing o f a blow-off door fabricated of fiberglass, quickly established
clear advantages of this product over the one fabricated of aluminum:

(1) the

fiberglass door weighed less than one-half as much as the aluminum door (53 pounds
compared to 120 pounds) and offered considerable advantage i n handling the doors
for installation, and (2) fiberglass construction resulted i n doors which were
flexible and

liable enough to absorb impact w i t h

sustaining damage.

the flame deflector plate without

The combination of light weight and f l e x i b i l i t y o f the fiber-

glass doors was manifested i n l i t t l e damage being incurred by the doors w i t h

�each use and established a high reuse factor.

This reuse factor coupled w i t h

lower i n i t i a l costs and lower repair cost, as compared w i t h the aluminum door,
permitted a savings of several thousand dollars i n the Saturn

SIV program.

Before and during the early portions of the hot firing program, i t was found
that some of the diffuser doors would occasionally blow off upon activation of
the altitude simulation system.

This w w l d result i n the i n a b i l i t y to draw a

vacuum i n those diffusers affected and thereby cause an automatic cutoff.

It

was first thought that flame deflector plate water flow was washing the doors
o f f and the operating sequence was changed to assure a t least partial vacuum
prior to achieving f u l l deflector plate water flow.

The

persisted however,

and several additional factors were evaluated.
4

I t was found that i n i t i a t i o n of steam flow i n the ejector generated a
momentary but very slight overpressure i n the diffusers, which could contribute
to door blow-off

.

By starting the steam blow-down w i t h butterfly valves closed,

this surge was prevented from entering the lower ( ~ l e n u m )section of the diffusers
immediately above the doors.
The most direct cause of door loss was attributed to the accumulation o f
water i n the steam supply lines.

The i n i t i a l design incorporated preheat valves

that permitted a small quantity of steam to bypass the constant pressure regulating
valves for the purpose of conditioning the lines downstream.

i t was intended that

this would reduce condensation during the i n i t i a t i o n of steam flow t o the eiectors.
Unfortunately, the preheat steam condensed into large accumulations of water,
and i n i t i a l main steam flow carried this water to the ejectors w i t h attendant

�water hammer loads i n the lines, ejectors, and diffusers.

Preheat was eliminated

- 9 .

very early i n the test program, but the water "slugging" problem persisted, although
i t was less severe.

The entrained water would cause violent shock loads i n the

ejectors as i t turned corners and eventually went through the elector nozzles,
and these loads were transmitted to the diffuser through the connecting thirty (30)
inch ducts with sufficient force to actually shake the doors off.

The addition of

drains to the system a t a l l low points, and particularly immediately upstream
and downstream of the constant pressure regulating valves solved this problem.
The condensation occurring during initial flow of steam into cold lines was less
severe than anticipated.

With the incorporation of procedures for draining

water which had accumulated a t a l l low points i n the steam lines to the ejectors,
and changing of the logic sequence to open the butterfly valves after steam
flow was well established i n the eiectors, operation of the altitude simulation
system became very re1iable.
The double-walled diffuser construction, mentioned earlier, i s shown i n
Figure 8.

The inner wall i s one piece, 5/16 inch thick, extending from the

engine exit to the plenum section (Section #8). The plenum i s separable
from the rest of the diffuser and incorporates a section of water-cooled 30-inch
vacuum line.

Spacer rings of 1/4 inch square cross section are welded to the

inner wall every six (6) inches.

The rings are not'ched to permit some longitudinal

equalization of water flow and to permit a i r and/or vapor to be vented.

The

outer'shell i s two pieces, each welded to one of the end flanges of the inner
wall.

A slip joint gland seal midway along the diffuser permits each half of

the outer she1l to move freely i n the axial direction, thus preventing buckling

�loads on the inner w a l l during the expansion caused by heat generated during
a static firing.
outer shell.

Water i s introduced into the annvlus through holes i n the

The i n l e t and outlet water manifolds are essentially identical,

half-round sections of pipe covering the holes and having flanged connectors
t o the test stand water distribution manifolds.
Initially, no attempt a t controlling the vertical distribution of water
flow was made.

Water temperature was monitored a t one point i n the final

discharge line from each diffuser, and a single diffuser was instrumented a t
each water discharge point to establish a profile of temperature along the
length of the diffuser.

The first two static firings, of 10 and 14 seconds duration,

were insufficient i n duration to establish a temperature profile a t the cooling
water discharge ports.

The third firing was aborted a t 28.5 seconds because

of what was then considered an excessive water discharge temperature of 165'~.
Although no physical damage occurred, orifices were instal led i n the outlet
flanges of the upper sections of the diffuses tcs force more of the flow through
the lower sections.

The allowable water discharge temperature was raised from

1 6 5 ' ~ to 1 9 0 ' ~ and static firings of 62, 41, and 7 seconds were accomplished
w i t h no overheat evidenced.

The first f u l l duration

420 second firing, the

seventh static firing, resulted i n extensive damage to the plenum section of the
diffusers, even though the maximwm allowable water temperature was not
exceeded.

I t was determined that local boiling or trapped a i r near the water

outlet o f the lower section of the diffusers restricted water flow sufficiently
t o permit hot spots to develop to the point that the inner liner became plastic
and bulged inward.

Metal flow occurred a t the bulge i n each diffuser, and i n

�one case was of sufficient magnitude to cause the bulge to rupture, The exit
water manifolds were removed from each diffuser and additional holes drilled
through the outer wall to reduce restriction to water flow. Vent holes to
eliminate air traps at the upper end of each section were also added i n the
outer wall.

The orifices were changed i n a19 the outlet flanges i n an attempt

to distribute water flow such that a constant tempemture rise would be obtafned
across each diffuser section,

The discharge water from the previously damaged

lower section was diverted from the collection manifolds feeding the deflector
plate, and used to cob1 the bellows section i n the 30 inch duct connecting the
diffusers to the steam iniectors.

The next full duration firing resulted I n a small

bubble i n Section # 1 of Diffuser Number 2, and the respective outlet orifice
was enlarged for a l l six (6) diffusers, Subsequent full dumtlon firing tests on
both the battleship test vehicle, and four (4) fltght vehicles were performed with
no further difficulties encountered i n cooling of the diffusers.
The altitude simulation system described i n this paper has been used to
accomplish some thirty-one (31) static firing tests.

Each of these tests involved

the functioning of a set of steam ejectors and diffusers for each of the six engines
utilized on the Saturn SIV sta$e.

In this sense, one hundred and eighty-six (186)

operational cycles were accomplished i n simulating altitude conditions for an
engine firing.

While problems were encountered i n making the total a! titude

simulation system functional, they were solved quickly a? the beginning of the
staticatestingprogram. The performance of the system i n achieving the low
pressures required, and i n achieving them with a high level of reliability has
been we1l estdbl ished as very satisfactory.

����FIGURE 4

I

I

-7 -6 -5 -4 -3 -2 -1

I

i i i i i i i i i i

-30 -20 -10 -9 -8

I

I

8 +l +2 +f +4 +S

I

I

I

I

I

I

I

I

i

I

1

I

+s 4-7+8 +1+1@ 4-9+$O+t)+t) +@
i i i i i i i 1 i I
1

SATURN S-IV GROUND TEST START SEQUENCE
i

EXPANDED TIME SCALE (SECONDS) -60 -50-40

WATER VALVE OPEN

DEFLECTOR WATER PUMPS 1-2-3
DEFLECTOR PLATE
STATIC FIRING AUTO SEQUENCE
1ST STAGE STEAM EJECTORS ON
2ND STAGE STEAM UECTORS ON

DIFFUSER PRESS.
MONITOR SWITCHES ENABLED

LH2 PRESTART VALVES OPEN
LOX PRESTART VALVES OPEN
ENGINE IGNITERS ON
ENGINE START VALVES W E N
ENGINE PRESSURE QK

�5

SATURN SIV-5 ENGINE DIFFUSER OPERATION

PRESSURE aLGUMVOiWS
f CO)ISTAfdl
i1STSTUXEJETOR
VALVES OPEN

�FIGURE 6

FROM

PNEUMATIC VALVE

REGULATOR

SOLENOID VALVE

HAND VALVE

NCHECK VALVE

-

CONSTANT PRESSURE REGaBMTGq CONTROL SYSTEM

WATER SHUTOFF &amp;
MWUUTING VALVE

CONSTANT WATER

(

&amp;

�PRESSURE-PSIA

�DIFFUSER W A E R
8)

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20072">
                <text>spc_stnv_000059</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20073">
                <text>"Altitude Simulation in Saturn SIV Space Testing."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20074">
                <text>This paper was presented to the Society of Automotive Engineers.  The abstract reads, "The Douglas Aircraft Company has been involved in testing the Saturn SIV stage at the Sacramento Test Center for the past two years.  The propulsion system for the SIV stage consists of six (6) Pratt &amp; Whitney Aircraft Company rocket engines which are designed specifically for high altitude start and operation.  During static firing tests of this engine at sea level, a steam jet ejector in combination with a diffuser, are used to simulate altitude conditions.  The intent of this paper is to examine the performance of this altitude simulation system,  and to discuss problems encountered in making it operational."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20075">
                <text>Hofferth, D. D.</text>
              </elementText>
              <elementText elementTextId="20076">
                <text>Polansky, A. L.</text>
              </elementText>
              <elementText elementTextId="20077">
                <text>Wilson, E. L.</text>
              </elementText>
              <elementText elementTextId="20078">
                <text>Douglas Aircraft Company. Missile and Space Systems Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20079">
                <text>1965-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20080">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20081">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20082">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
              <elementText elementTextId="20083">
                <text>Saturn S-4 stage</text>
              </elementText>
              <elementText elementTextId="20084">
                <text>Altitude simulation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20085">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20086">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20087">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20088">
                <text>Box 12, Folder 60</text>
              </elementText>
              <elementText elementTextId="205810">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20090">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20091">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20092">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8517" public="1" featured="0">
    <fileContainer>
      <file fileId="7435">
        <src>https://digitalprojects.uah.edu/files/original/125/8517/r04c03-14.pdf</src>
        <authentication>676c1cb82167ad218a7a5beff05f6589</authentication>
      </file>
    </fileContainer>
    <collection collectionId="125">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="137621">
                  <text>Series 04, Subseries C: Alabama History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="137622">
                  <text>Series 04, Subseries C: Alabama History</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="137853">
                <text>r04c03-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="137854">
                <text>Series 4, Subseries C, Box 3, Folder 14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137855">
                <text>"America's First Frontier Railroad" Paper by McCanless, George F. Jr</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137856">
                <text>Miscellaneous Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="137857">
                <text>r04c-211007</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1145" public="1" featured="0">
    <fileContainer>
      <file fileId="992">
        <src>https://digitalprojects.uah.edu/files/original/20/1145/spc_stnv_000061.pdf</src>
        <authentication>271b6a70fbb7b29e2196d2c74298e1b7</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177279">
                    <text>I

John F.
Space Center
N A T I O N A L A E R O N A U T I C S A N D SPACE A D M I N I S T R A T I O N

KM HISTORY DOCUP
ity of Aiabama Researcl
QF Science 6 Technolc _

-LI-..-----D=N~.--------

-

AMERICA'S
SPACEPORT

�"The story of man's achievement thrmgh30ut history has
been the story of his victory over the forces of nature. In
that continuing story, our generation has been given the opportunity to write the grandest chapter of them all. It i s on
our schedule, in oar plm, and in our determination to put
men 092 the moon before 2370."
President Lyndon

B. Johnson

sept.n, 1966

�W E L-COME...
,

.
'

.&amp;

.

Welcome to the John F.
Kennedy Space Center, NASA.
This i s the major launch
base from which manned and unmanned spacecraft explore the
environment beyond the Earth's
atmosphere, reaching out to the
Moon, the Sun and the planets.
Thousands of dedicated engineers, scientists, technicians
and support personnel, members
of an integrated GovernmentIndustry
team,
have created
these facilities.
The Center's
superb launch team has achieved
many "firsts" i n man's conquest
of space.
These accomplishments represent an important
phase of the Nation's effort to
achieve and maintain preeminence i n space research and
exploration.
I trust you w i l l share our
pride i n the unique environment
of the launch center and the historic work being carried on here.

John

F.

Kurt H. Debus, Director
Kennedy Space Center,
NASA

�MISSION
John F. Kennedy Space Center i s the major
NASA launch organization for manned and un:
manned space missions.
As the lead center within NASA for the development of launch philosophy, procedures, technology and facilities, Kennedy Space Center launches
Apollo space vehicles; unmanned lunar, planetary and interplanetary spacecraft; and scientific, meteorological and communications satellites.
The mission encompasses planning and directing:
Preflight Preparations
Vehicle Integration
Test and Checkout of Launch Vehicles,
Spacecraft and Foci liti es
Coordination of Range Requirements
Countdown and Launch Operations
Supporting t h i s primary mission are a host of
technical and administrative activities. These include design engineering; testing, assembly and
checkout of launch vehicles and spacecraft; launch
operations; and purchasing and contracting.
The national Spaceport i s the site from which
American astronauts w i l l be launched on lunar exploration missions before the end o f the decade.
The A i r Force Eastern Test Range, part o f the
Air Force Systems Command, operates and maintains the largest missile proving ground i n the free
The Test
world, one that spans 10,000 miles.
Range's mission i s to provide launch f a c i l i t i e s
and support services for launching missiles and
spacecraft, and gather useful data from the flights.
The Range supports NASA-sponsored launches for
the peaceful exploration of space.

�The

National

Aeronautics

and

Space Administration was established
October 1, 1958. T h i s was 12 months
after the launch o f Sputnik 1, the f i r s t
man-made Earth satellite, and n i n e
months after the launch o f Explorer 1,
the f i r s t United States satellite.
The maior focus o f NASA's launch
operations has centered on Cape Kennedy, formerly Cape Canaveral, Florida.
The antecedents of these a c t i v i t i e s
date back to t h e years f o l l o w i n g World
War II when the War Department selected the s i t e as a t e s t i n g area for longrange guided missiles. T h i s s p i t o f
land i u t t i n g into the A t l a n t i c Ocean
wos selected because o f the chain o f
islands stretching southeastward t o
Ascension Island which could accommodate tracking stations to measure
the f l i g h t of research and development
vehicles.
The s i t e was formally approved J u l y 8, 1947.
Soon afterward, Congress author i z e d the acquisition and construction
o f the A t l a n t i c M i s s i l e Range, now the
Eastern T e s t Range. A s a Department
o f Defense facility, the range was assigned to the A i r Force for management.
Subsequently, the range was
extended t o the Indian Ocean, a distance o f more than 10,000 miles. The
Army and Navy have a l s o u t i l i z e d the
range f a c i l i t i e s i n the development o f

rocket-powered weapons systems.
As the NASA program got underway, the Cape became the headquarters
of the Launch Operations Center, later
renamed the John F. Kennedy Space
Center, NASA.
In late 1964, the Kennedy Space
Center was relocated on adiacent Merr i t t Island. The s i t e occupies some
Here, foci l i t i e s have
88,000 acres.
been installed t o accommodate enormously powerful space vehicles t o
carry man to the Moon and back, and
to undertake even more challenging
missions i n the vast reaches o f the
universe.
By noteworthy coincidence, the
Spaceport has an unusual heritage.
Numerous Indian burial mounds and
middens (refuse piles) have been discovered on NASA property. Researchers have removed artifacts dating back
to the time of Christ. Elsewhere, part i c u l a r l y along the beaches, traces
have been found of early Spanish
activity.
Dr. Charles Fairbanks of the University of Florida has pointed out:
'This was one of the areas where
Western c i v i l i z a t i o n came to the New
World, and now it i s the area from
which our c i v i l i z a t i o n w i l l go forth to
other worlds."

�LAUNCH
VEHICLES

T h e United States space program
depends on the $ability o f scientists
and engineers t o provide the means
for propelling useful pay loads i n t o
Earth orbit and into the farther reaches
of space. For t h i s task, launch vehic l e s of varying sizes and capabilities
are necessary.
The f l i g h t path chosen for a payload determines what performance i s
required of the particular launch vehicle. Obviously, it would be impractical
to use our most powerful launch vehicle, the Saturn V, t o orbit a small,
lightweight group o f s c i e n t i f i c satellites, or to r i s k failure of a mission by
placing too much weight on a launch
vehicle of any size.
For these reasons, NASA has developed a family o f r e l i a b l e launch

�vehicles of different sizes, shapes and
capabilities. The objective has been
to develop the smallest number of vehicles consistent with the f u l l scope of
the space program.
Launch vehicles employed for
space missions i n the recent past
evolved principally from basic military
systems developed and tested during
the previous decade.
Technological
exchange between military and scient i f i c projects continues to benefit the
national space program.
The f i r s t United States satellite
was orbited by an Army-developed
Jupiter-C missile.
Delta, the workhorse of NASA's unmanned spacecraft
program, employs components developed by the A i r Force and Navy. Modi-

SATURN I

fied Army/Air Force developed Redstone and Atlas boosters were utilized
for the Mercury program, this country's
i n i t i a l manned space flight effort. The
Gemini launch vehicle was a modified

Air

Force Titan II booster. Centaur,
the world's f i r s t space launch vehicle
to be powered by liquid hydrogen fuel,
and the highly successful Ranger and
Mariner space probes were boosted into
space by modified Air Force Atlas
vehicles.
The Saturn family of heavy launch
vehicles, which was developed by
NASA expressly for the peaceful exploration of space, evolved from technology acquired during the Army's
early Redstone, Jupiter and Juno miss i l e development programs.

A P O L L O / U P R A T E D SATURN

�MANNED
SPACE FLIGHT
For thousands of years man has
dreamed of the day when he would explore the vast universe that surrounds
his tiny planet. This aspiration has
stemmed from his fundamental thirst
for knowledge and his readiness to
accept the challenge of the unknown.
When Orville Wright made the first
powered flight in 1903 at a speed of
31 miles per hour, the significance of
his achievement was barely recognized.
Yet, in l i t t l e more than half a century
following that historic event at Kitty
Hawk, man' has succeeded i n orbiting
the Earth at speeds measured in thousands of miles per hour. Now, he i s
literally reaching for the Moon as the
first stop on the way to exploration of
the solar system and the infinite
reaches of interstellar space beyond.
The achievements in space since
the first satellites were launched have

paled to insignificance when compared
with future proiects. Only i n the light
of what he has already accomplished
can man look ahead with the almost
certain knowledge that he eventually
w i l l realize his age-old dream of exploring the universe.
Viewed in terms of time and distance, the challenge of space exploration seems insurmountable.
Yet, a
review of the technological accomplishments of the 20th century indicates
that what appears as impossible i s
merely difficult.
The exploration of space i s following the pattern by which flight
within the atmosphere was mastered.
Each new development provides a
platform from which to take the next
step, and each step i s an increment of
scientific knowledge and technological
skill.

��MERCCJRY
Project Mercury, the first of the
manned space flight programs, was
organized October 5, 1958, and successfully executed i n less than five
years.
The primary objectives of Proiect
Mercury were:
To place a manned spacecraft
i n orbital flight around the
Earth.
To investigate man's performance capabilities and his abili t y to function in the environment of space.
To recover, safely, both man
and spacecraft.
Project Mercury demonstrated that
the high-gravity forces of launch and
reentry, and weightlessness in orbit for
as much as 34 hours, did not impair
man's ability to control a spacecraft.
I t proved that man not only augments
the automated spacecraft controls, but
also can conduct scientific observations and experiments.

-

Moreover, Project Mercury proved

that man can respond to and record the
unexpected, a faculty beyond the capability of a machine which can be programmed only to deal with what i s
known or expected. In addition, the
Mercury flights confirmed that man can
consume food and beverages and perform other normal functions while i n a
weightless
environment.
Finally,
Mercury laid a sound foundation for
the technology of manned space flight.
The Mercury spacecraft, a one-man,
bell-shaped vehicle, 9.5 feet high and
6 feet across at its reentry heat shield
base, weighed approximately 4,000
pounds at liftoff and 2,400 pounds at
recovery.
The launch vehicle for the Mercury
suborbital missions was a modified
Redstone rocket generating 78,000
pounds of thrust at liftoff. A modified
Atlas rocket whose three engines produced 367,000 pounds thrust was employed for Mercury orbital flights.
Complexes 56 and 14 at Cape Kennedy
were utilized for the Mercury missions.

�GEMINI

&amp;mini was %he Lntermdiate step
tawutd ~ h i c n r i n gB manpad lwsw land#
ing, bridgina the afIigjhtexp4ilcnce
k w e m tke S ~ W T - ~ Q ~
missions andhe lang durdflm mirsions
of Apollo.
Major obitctives achieved during
the p r ~ r a m
included d*mons+ration that
man can perform effectively during extended periods i n spoce, both within
and outside the p~oiectivaenviron.men+
of a spacecraft, development crf r m dezwus and doeking techniques, and
parfelttan of controlled rsenTry and
landing procedures.
The Gemin i progrm provided fhe
first American demonstratim of arbi tal
rendezvous
a skill which must be
devdeped to land Amsriean exploxers
on the Meon and is camduct the adwnced ventures of the future.
The welaan Gemini spaeemafr
was also a bll-shaped vehicle; however, it was almost twice as heavy, SQ
perceht larger and contained 50 per-

wmq

-

cccn? more valume than the Mercury
saw&amp;crafit.
The tatsneh vehicle empleyed i n
the C m i n i prepram was the modified
Air Force Titan tl rocket which devdoped a thrust of 430,000 pounds at
liftoff.
The o v ~ ~ length
l t
af the
Gmttni-Titan ll spa&amp;@vehicle was 109
h t , Gemini flights wwe launched
from Complex 19 at Cope Kennedyelr,
The t a r p t vahicls fos thq Gemini
r.(tndezvuur ond docking misrims was
B d i f i e d Agena-D vehicle with (J fwwad moun~edtarget docking adapter,
which provldedtb connecting point far
mwting wjth the &amp;mini srraaecrdt.
The Agena-a, with a multiple restwt capability, had a rated thrust o f
appmxim&amp;aly 16,W pcrunds. it was'
launched an an Atlas Standard Launch
Vehicle which generates about 390,000
pounds of thrust. Gemini Aflas/Agena
t a r p t vehiefrs had an avarall length
of 104 fret. They were lounched from
Complex 14 at Cape Kennedy.

�r

'.

Tf
sign-

FJ,,F3Jh
.
\

'

..

�fir.-+.-

Apollo i s the largest and most
complex of the manned spoce flight
programs. Its goal i s to land American
astronauts on the Moon and return them
safely to Earth.
The astronauts w i l l travel to the
Moon in the three-man Apollo spacecraft. Weighing 45 tons, the spacecraft
consists of three sections - a command
module, a service module and a lunar
module.
The command module may-be likened to the crew compartmentof a commercial jet airliner. It i s designed so
that thrse men can eat, sleep and work
in it without wearing pressure suits.
Of the three modules, only the command
module w i l l return to Earth. Thus, it i s
constructed to withstand the tremendous
deceleration forces and intense heating
caused by reentry into the Earth's
atmosphere,
The service module contains supplies, fuel and a rocket engine so
the astronauts can maneuver their
craft into and out of lunar orbit and
alter their course and speed in space.

&gt;

l-.

k
1

The lunar module i s designed to
carry two men from lunar orbit to the
Moon's surface for exploration and
and then back into lunar orbit for rendezvous with the command and service
modules.
After the crew transfers
back to the command module, the lunar
module i s jettisoned and left in lunar
orbit.
Providingthe muscle for theApollo
program i s the Saturn family of heavy
launch vehicles. The first of these to
be flight tested by the Kennedy Space
Center was the Saturn I. Developing
1.5million pounds of thrust at liftoff,
theSaturn I demonstrated the feasibility

,

.- . .
=

r

d

of clustered rocket boosters and qualified vehicle guidance and control systems. It also tested the structure and
design of the Apollo command and
service modules, physical compatibility
of the launch vehicle and spacecraft
and iettisoning of the Apollo launch
escape system. Additionally, Saturn I
vehicles orbited large Pegasus micrometeoroid detection satellites to monitor the frequency of micrometeoroids
and to determine if they would be a
hazard to manned space flights.
Currently, uprated Saturn flight
programs are underway at Kennedy
Space Center. W i t h the greater power
of the uprated Saturn, a l l three modules of the Apollo spacecraft are
launched into Earth orbit.
Initially,
the flights are unmanned. Soon, uprated Saturn vehicles w i l l launch three
astronauts on Earth orbital missions
up to 14 days in duration.
Lunar missions w i l l use the enormous power of the Saturn V launch
vehicle. Together with the three modules of the Apollo spacecraft, the
Saturn V stands 364 feet, weighs about
6 million pounds at launch and develops 7.5 million pounds of thrust at
liftoff.
Development of the Saturn vehicles
i s the responsibility of the Marshall
Space
Flight Center,
Huntsville,
Alabama.
The Manned Spacecraft
Center, Houston, Texas, has responsi bility for Apollo spacecraft development, training of the flight crews and
conducting the flight missions. Assembly, checkout and launch of the ApolloSaturn space vehicles are conducted
at Cape Kennedy and at the Nation's
Spaceport by Kennedy Space Center.

�1

;,I
'

'.

5'

-

SATELLITES
AND
SPACE -.
PROBES .-...

�Unmanned spacecraft are making
important contributions to man's knowledge ahout the world in which he lives
and the universe around him. Much of
this knowledge i s derived from the
growing family of scientific satellites
and space probes launched by Kennedy
Space Center.
Explorer satellites have mapped
the Earth's magnetic field and have
pioneered i n gaining new knowledge of
the Earth's shape and mass distribution. Explorer I, this country's first
satellitewhich was launched from Cape
Kennedy on January 31,1958, discovered that the Earth was partially surrounded by a belt of deadly radiation, subsequent1y named the Van Allen Radiation Region.
Other satellites have furnished
information on micrometeoroids,temperatures in space, radiation and magnetic
fields, upper atmospheric conditions,
solar activity and other phenomena.
Meteorological
satellites have
achieved the most significant advances
in weather forecasting since the invention of the barometer over three
centuries ago. T I ROS satellites, the
first of a series of orbiting "weathermen," were launched from Cape Kennedy Complex 17 by Delta vehicles
beginning i n April 1960. These satellites returned well over a million cloud:over photographs of the Earth's surrace.
Starting
in 1966, operational
ueather satellites were launched for
the Environmental Science Services
Admini stration by Kennedy Space
Center personnel. Placed into polar
3rbit from the Western Test Range in
Ealiforn ia, these satellites photograph
cloud cover and transmit pictures to
weather stations akound the world.
This type of fast, accurate weather
reporting coupled with long-range weather prediction can be worth untold
millions of dollars to agriculture,
business and industry.
Communications satellites such
as Echo, Telstar, Relay, Syncom and
Early Bird, launched on Delta vehicles
trom Cape Kennedy's Complex 17, are
shrinking the distances between continents, and are leading to better under-

standing among the world's people.
Exploration of the Moon's surface
and environment by unmanned space
probes i s essential to obtain data for
manned lunar landings. This type of
information i s also important i n yielding clues to the origin of the Moon, the
solar system and perhaps even the
universe.
Rangers 7, 8 and 9 returned thousands of close-up pictures of the Moaj
before smashing into the lunar surfac+:
On June 2, 1966, the Surveyor I space&amp;
craft, the first of a series of instryk
mented soft-landers, settled gently
onto the lunar surface and transmitted
thousands of detailed photographs ba*
to Earth. Other Surveyor soft-landers
are making detailed examinations of
the Moon's physical phenomena and
surface composition. These spacecraft
are launched by Atladcentaur vehicles
from Cape Kennedy Complex 36.
Lunar Orbiter spacecraft, circling
the Moon in low orbit, have photographed with amazing clarity wide
areas of the lunar landscape. Launched
from Complex 13 at Cape Kennedy, the
Lunar Orbiter missions have provided
significant data on potential landing
sites for Apollo astronauts.
Investigations of other planets of
the solar system are conducted by
unmanned Mariner spacecraft. On December 14, 1962, Mariner 2 became the
first spacecraft to scan another planet
at close range as i t passed within
21,600 miles of Venus.
Mariner 4,
after an eight-month iourney, passed
.
within 6,000 miles of Mars on July 14,
1965.
Instrument observation of the
plahet yielded invaluable clues to
scientists seeking clues to the possibility of life on Mars. Mariner spacecraft are launched by Atlas/Agena vehicles from Cape Kennedy Complexes
12 and 13.
Goddard Space Flight Center manages NASA's unmanned scientific,,
meteorological and communications
satellite programs. Unmanned lunar, planetary and interplanetary programs
are managed by Jet Propulsion Laboratory.
Launch operations for these
programs are conducted by the Kennedy
Space Center.

�LAUNCH COMPLEX 39
Launch Complex 39, the nation's
f i ~ s toperational spaceport, ranks as
one of history's great engineering
achievements. Developed and operated
by the Kennedy Space Center, the immense facility is designed to accommodate the massive Apollo/Saturn V
space vehicle which w i l l carry American astronauts to the Moon.
Complex39 reflects a new approach
to launch operations. In contrast to the
launch facilities presently utilized at
Cape Kennedy, Complex 39 permits a
high launch rate, economy of operation

.

..

and superior flexibility. This new approach, known as the 'mobile concept,"
provides for assembly and checkout of
the Apollo/Saturn V vehicle in the controlled environment of a building, i t s
subsequent transfer to a distant launch
siteand launch with a minimum of time
on the launch ad.
The maior components of Complex
39 include:
the Vehicle Assembly
Building, where the space vehicle i s
assembled and tested; the Launch
Control Center, which houses display,
monitoring and control equipment for

�checkout and launch operations; the
Mobile Launcher, upon which the space
vehicle i s erected for checkout, transfer and launch and which provides internal access to the vehicle and spacecraft during testing; the Transporter,
which transfers the space vehicle and
Mobile Launcher to the launch site;
the Crawlerway, a specially prepared
roadway over which the Transporter
travels to deliver the Apollo/Saturn V
to the launch site; the Mobile Service
Structure, which provides external access to the vehicle and spacecraft at
the launch site; and the launch site,
from which the space vehicle i s launched on Earth orbital and lunar missions.
The Vehicle Assembly Building
provides a startling contrast to the low
Merritt Island landscape. Covering 8
acres of ground, the Vehicle Assembly
Building conslsts of two major working
areas: a 525-foot-high high bay area
and a 210-foot-high low bay area.
The- high bay contains four vehicle
assembly and checkout bays, each capable of accomrnodoting a fully ossembled, heavy-class space vehicle. The
low bay contains eight preparation
and p heck out cells for the upper stages
of the SacturnV vehicle.
Vehicle stages are shipped by barge
from fabricatian centers to a turning basin near the Vehicle Assembly Bui lding,
off-loaded onto special carriers and
transported to the building. The first
stage i s towed to the high bay area and
erected on the Mobile Launcher. Four
holddown-support arms on the Mobile
Launcher platform secure the booster
in place. Work
are positioned
around the booster for inspection and
testing. Concurrently, upper stages of
the Saturn V are delivered to the low
bay cells, inspected, and tested.
When testing of the individwal
stages i s completed, the upper stages
are prepared for mating and moved to the
high bay area. A l l components of the
space vehicle, including the Apollo
spacecraft, ore assembled vertically
in the high bay area. The fully assembled space vehicle then undergoes

final integrated checkout and simulated
flight tests.
Located adjacent to the Vehicle
Assembly Building and connected to
the high bay area by an enclosed
bridge i s the Launch Control Center.
All phases of launch operations at
Complex 39 are controlled from this
four-story concrete structure.
The first floor of the Launch Control Center contains offices, a dispensary and a cafeteria. The second floor
is allocated to telemetry, measuring and
checkout systems for use during stage
and vehicle assembly in the Vehicle
Assembly Building, and for launch operations at the launch site.
Four firing rooms occupy the third
floor
one for each high bay in the
Vehicle Assembly Building.
These
rooms contain control, monitoring and
display equipmentreqwired fw automatic
vehicle checkout and launch. Each firing room i s supported by a computer
room, which is a key element in the
automatic checkout and launch sequence.
The Mobile Launcher, the key to
launch operations at Cemplex 39, actuallyperforms a dual function. It serves
as an assembly
within the
Vehicle Assembly Building and as a
launch ~ l a t f o r mand umbilical tower at
the launch site located several miles
away.
The Mobile Launcher i s a 446-foothigh structure with a base platform
measuring 25 feet high, 160 feet long
and 135 feet wide. I t weighs 10.6 million pounds. Whether in the Vehicle
Assembly Building, at the launch site,

-

�or in its parking area, theM~bileLauncher ir positioned on six 22-foot-high
steel pedestals.
Nine swing arms extend from the
Mobile Launcher's tower. The three astronauts wi ll enter the Apol lo spacecraftvia the top swing arm. These arms
are dei~igrrrrdto swing rapidly away
from the vehicle during launch, Besides
carrying vital umbilical lines prapellant, pneumatic, electrical, data link
to the space vehicle, the swing apms
also permit a catwalk access to the
vehicle during tfaa final ~ h a s eof countdown.
The ApolloAaturn V i s p s i t i m e d
on the Mobile Launcher and secured by
f a r suppart and holddown arms. At
the pad these arms hold the vehicla
during thrust buildup of ths engines. A
45-square-foot spcning in the k s e plotform permits passage of engine exhausts
at ignition. Three Mebile Launchers
have been corrsttuctrd at Complex 39.
A tracked vehicle hnewn as the
Trclnsporfer moves thc 36-stsry Apol lo/
Saturn V space vehicle and Mobile
Launcher horn the Vehicle Assembly
Building to the launch site. Two Trans-

-

-

are stutioned a t Camplex 39.
"Ihe Transporter i s similar to ma-

porters

chines used in strip mining operations.
Weighing app~aximately6 mi Illan ponds,
it i s 131 feet long and 114 M w?&amp;.
Its height is adjustabls froa aQ to 26
feet. The vehicle moves on. h r J~ltlLletracked crawlers, e s h 10 %a&amp; high and
40 feet long. Each shwe &amp;
~ m l c r
track weighs atrout a tat. ffrwa W Q $?
shws on each h a c k B F F ~l
~ ~ t 1 1of 8
tracks on the c n t h A t a l s .
Two main Civet d i m 1 engines provide 5,500 hnrsepwe-r. T* aher diesels gsnerah 2,t 30 h w ~ p ~ w e
farr
Ievk-ling, iackhg, rtew~tlsg, Il@ng,
verrtiloting and sfsctrsnia syat%ns.
Aurilimty plmimature pmvide power to
the Mabila L W W RwG h~ carried by
the Trurrhparter.
Fn optaatian, the Jranspwter s l ips
under the Mabile Lwncher while inside
the Vehicle Assembly Building, Its 16
hydraulic i a ~ k s
rulsctheMobila Launcher, with the spaee vehicle aboard, from
support pdestals, The leaded Tranoporter then backs out of the Vehicle
Assembly Building and transfers the
11.5-million-pound-load 3.5 mil&amp; te the

�launch site.
The Transporter has a speed of 1
mile per hour when fwlly loaded and
twice that when unloaded. It can negotiate curves of 500 feet mean radius.
A leveling system provides the capability to maintain the entire load i n
level position during *he transfer operation.
The combined weight of the Transporter, the Mobile Launcher m d the
Apollo/Saturn V exceeds 17 million
~ o u n d sa t the time of transfer from the
Vehicle Assembly Building to the
launch site. To accommodate fhis load,
a specially constructed Crawlerway was
prepared.
The Crawlerway extends from the
Vehicle Assembly Building to the
launch site, and consists of twa 40foot-wide lanes separated by a SOfoot-wide median strip.
The overall
width of the roadway i s 130 feet or
about equal to an eight-lane parkway.
Unsuitable material was removed
from the roadbed before beginning construction of the Crawlerway. The area
than was compacted with hydraulic fill
and selected material s, topped with
crushed graded lirnerock, paved w ith asphalt, sealed and covered with gravel,
forming a roadbed approximately 7 feet
thick. From eight to twelve thousand
pounds-pet-square-foot in surface prossures are exerted on the Crawlerway;
this i s equivalent to a stress of 40 iet-

liners landing at the same time on a
runway.
The Mobile Service Structure i s a
402-foot-high tower which weighs 12
million pounds. The structure contains
five service platforms that provide circular access to the space vehicle for
final servicing at the launch site. The
two lower platforms can be adiusted up
and down the vehicle, while the three
upper platforms have a fixed elevation.
Like the Mobile Launcher, the Mobile Service Structure i s transported to
the launch site by the Transporter. I t
is removed from the pad a few hours
prior to launch and returned to its parking area.
Two launch sites are located at
Complex 39, three and one-half miles
from the Vehicle Assembly Building.
Each site i s an eight-sided polygon
measuring 3,000 feet across.
The maior elements of the launch
iites include the launch pads; storage
tanks for liquid oxygen, liquid hydrogen
and RP-1 propellants; gas compressor
facilities; and associated umbilical
connection lines necessary for launching the space vehicle.
The launch pad itself i s a reinforced concrete hardsite measuring 390
feet by 325 feet. Top elevation of the
pad is 48 feet above sea level, sufficient distance for the rocket's engine
nozzles to rest above a 700,000-pound
flame deflector.

�INDUSTRIAL AREA
The lndustrial Area of the Kennedy
Space Center i s located 5 miles south
of Launch Complex 39. The area was
planned so that a l l functions not required at the launch complexes could be
grouped for ease of administration and
efficient operations. Here, the administrators, scientists, engineers and
technicians plan and accomplish many
of the detailed operations associated
with prelaunch testing and preparing
space vehicles for a mission.
The Headquarters building i s the
admin istrative center for spaceport
operations. Dr. Kurt H. Debus, Director
of the Kennedy Space Center, and his
immediate staff maintain offices on the
top floors. Procurement, program management, legal and other support functions occupy lower floors.
The largest structure i n the Industrial Area i s the Manned Spacecraft Operations building. This facility i s used
for modification, assembly and nonhazardous checkout of Apollo spacecraft. It also provides astronaut quarters and medical facilities, spacecraft
automatic testing stations and complete

supporting laboratories.
Following systems testing and
Apollo service module static firing,
Apol lo spacecraft are delivered t o this
building for integrated systems testing.
Here, individual spacecraft modules
undergo acceptance testing and integrated systems and altitude chamber
testing. Two 50-foot altitude chambers
environmentally test Apol lo spacecraft
in conditions simulating altitudes up to
250,000 feet. Space-suited astronauts
participate i n these simulated flight
tests.
The Information Systems facility
i s the hub of thespaceport's instrumentation and data processing operations.
It provides instrumentation to receive,
monitor, process, display and record
information received from the space
vehicle during test, launch and flight.
The lndustrial Area contains special laboratories and testing facilities
for the hazardous checkout operations
associated with spacecraft pyrotechnic
devices and toxic fluids.
Among the other maior f a c i l i t i e s
located i n the lndustrial Area are:

�-

Flight Crew Training Building
this foci li t y provides an environment where astronauts and flight
controllers
under the direction
of Manned Spacecraft Center
personnel
can practice for
manned Apollo space missions.
actual Apollo spacecratt and
creates nearly complete realism
for simulated missions.
For
about three weeks prior to a mission, astronauts go through makebelieve flights and cope with
purposely contrived emergency
situations.

-

-

-

L i f e Support Test
this facility
i s used for high-pressure testing
and liquid oxygen supply testing
of environmental control systems.
FluidTestSupport this facility
i s a single-story structure housing laboratories, shops and service areas to support the entire
test area.
Critical component
lesting of spacecraft fluid test
[systems are conducted i n the
laboratories which maintain special clean-room conditions.
Hypergolic Test
this facility
i s used to test and check out
stabilization and attitude control
systems, orbital maneuvering systems and reentry control systems
for spacecraft. Hypergotic fluids
utilized i n these systems are
especially hazardous since they
ignite upon contact with each
other.
Cryogenic Test
this facility
i s used for checking the cryogenic systems of spacecraft.
Cryogenic fluids are supercooled.
An example would be liquid hydrogen which must be maintained
a t a temperature of 423 degrees
below zero.
Pyrotechnic Installation
this
ten-story-high facility i s used
to install spacecraft pyrotechnic

-

-

-

-

devices and to statically weigh
and balance the spacecraft i n i t s
mission configuration to determine its center of gravity. The
facility i s also used for optical
alignments of critical components
of the guidance and navigation
systems, as well as acceleration
tests on dynamic fixtures.
Ordnance Storage
this facility
provides remote, safe storage for
solid fuel motors, pyrotechnic
devices and aligned launch escape towers.
RF Systems ~ e s t this facility
i s used to adiust, test and check
out spacecraft rendezvous apparatus and procedures in a simulated free space condition. Transmitting antenna height, elevation,
squint and azimuth angles and
transmitter frequency are remotely
controlled from an operator's console.

-

-

Additional support structures in the
Industrial Area include cafeteria, warehouses, fire station, security offices,
utilities and occupational health fac i l i ties.

�CAPE
KENNEDY FACILITIES
Stretching northward along the Atlantic Ocean are the famous launch complexes of
Cape Kennedy. The Cape i s managed by the U. S. Air Force for theDepartment of D e fense and designated as Station 1 of the Eastern Test Range which reaches 10,000 miles
to the Indian Ocean. The U. S. Army, Navy and Air Force have used the Cape's f a c i l ities for missile development programs. Since the advent of the national space program in 1958, however, the area has also been u t i l i z e d by NASA as a launch s'ite for
space vehicles. In the foreground are the two pads of Launch Complex 36 from which
Surveyor spacecraft are launched toward the Moon.

�Ten manned space missions were launched
from Complex 19 during the highly successfu!
Gemini program. Here, the Gemini 12 vehicle,
the final flight i n the program, i s readied for
launch.
At the right i s the erector which i s
employed i n servicing the space vehicle. Prior
to launch, the erector i s lowered t o the ground.
The umbilical tower on the left carries electri
call communications and propellant lines to the
rocket. lt remains attached t o the vehicle until
liftoff.

-

A t Launch Complex 34, one of two Saturn
launch sites on Cape Kennedy, the 300-foottall service structure encloses an uprated Saturn
launch vehicle.
Unlike the erector used at
Complex 19, this structure moves back from the
launch ready vehicle on rails. At nearby Complex 37, another Saturn launch site, a similar
structure serves two launch pads that are connected by rails.
From these sites, astronauts
w i l l be launched on Earth orbital missions i n
- . the three man Apollo spacecraft.

-

1

,

,.This view of Launch Complex 37 shows the
service structure in an open position with an
rated Saturn launch, vehicle on the pad. To
afford launch crews access to the rocket, the
service structure closer around the Saturn. The
platforms, which can be seen i n the photograph,
provide work levels at various stages of the configuration. This unmanned Saturn, AS- 203, was
successfully launched July 5, 1W6. The mission was an orbital flight t o examine the effects
of weightlessness on the liquid hydrogen fuel of
the second stage.
For this reason, i t was
equipped with a nose cone instead of an Apollo
spacecraft.
Blockhouse personnel of the Kennedy Space
Center's Government- industry launch team follows liftoff of uprated Saturn AS-20-3 on television monitors inside Complex 37 launch control center.
Seated at a console and pointing
(front center) i s Dr. Kurt H. Debus, Director of
the Kennedy Space Center. Manning the peri
scope directly behind Dr. Debus i s the Marshall
Space Flight Center Director, Dr. Wernher von
Braun.
The launch control center i s located
approximately 1,200 feet from the launch pad.
Constructed of heavy reinforced concrete, the
two story, dome shaped structure can withstand
blast pressures of 2, 188 pounds per square inch.

-

-

-

�THE HUMAN ELEMENT

�The John F. Kennedy Space
Center i s many things. It i s the tremendous power of space vehicles
carrying precious cargoes o f men and
equipment; i t i s s c i e n t i f i c progress i n
it i s material and hardwareaction;
some minute and delicate, some huge
and powerful-in
various stages o f
being born and growing up; i t i s a l l
these
and more. The John F.
Kennedy Space Center i s also people.
From N e w York City; Nashville,
Tennessee; Dallas, Texas; San Jose,
California-virtual ly from a l l over the
United States-these people, representing a l l racial and ethnic backgrounds
and professions and skills, have been
molded into one o f the greatest teams
ever assembled for a peacetime endeavor.
More than 24,000 strong and representing the b e s t launch talent i n
government and industry, t h i s team
devotes i t s s k i l l s and talents to the
United States' goal o f space preeminence. Additionally, thousands of
Air Force Eastern T e s t Range personnel and A i r Force-associated con-

...

tractor personnel are providing v i t a l
range and mission support to NASA
activities.
Because the continuing progress

of the space program i s dependent
upon the total, coordinated efforts of
many people, no task i s inconsequential, no job t r i v i a l and no individual
unimportant. Each success hinges on
the premise that the people involved
w i l l do the best iob they know how to
do a t a l l times.
The entire space program i s varied
and complex, as are the s k i l l s required
to successfully accomplish the iob.
Welders, radio technicians, doctors o f
medicine, engineers, scientists, mechanics,
tinsmiths, writers,
photographers, truck drivers, policemena l l these and more are employed. T h i s
i s but a fragment of the whole.
As each day expands the scope
and technology o f space activities, the
need for people who can cope w i t h and
contribute to the growth of the space
program also expands. People are the
most important asset o f the program.

�PRIVATE INDUSTRY

�BUDGET
Research and Development of Ground-Support
Equipment and Instrumentation
Construction of Facil-

$ 37,876,000

ities

FACTS
&amp; FIGURES
MANPOWER
Federal Service Personnel
Support Contractor Personnel
Stage Contractor Personnel
Corps of Engineers Personnel
(C of E)
Construction Workers
NASA and NASA Related
Manpower-July 1, 1967

$339,800,000

Administrative Operations
Total Budget Estimate
(Fiscal Year 1967)

$ 93,620,000

$47 1,296,000

-

GOVERNMENT INDUSTRY TEAM
AT KENNEDY SPACE CENTER

CONTRACTORS

CONTRACTORS

�8

PUBLIC BUS TOURS
Daily bus tours of the Kennedy Space Center
and Cape Kennedy are available to the public.
Tours originate near the Center's Gate 3 , adjacent
to U. S. Hwy. 1.
The tour route includes the industrial and
launch a r e a s of the Kennedy Space Center and
Cape Kennedy Air Force Station, with s t o p s for
photography and a v i s i t to the Vehicle Assembly
Building.
Nominal f e e s are charged for the tour.
Tour information and reservations may be
obtained by writing NASA Tours, P o s t Office
Box 21222, Kennedy Space Center, Florida 32899.

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20113">
                <text>spc_stnv_000061</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20114">
                <text>"America's Spaceport."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="20115">
                <text>KSC-601</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20116">
                <text>Guide to John F. Kennedy Space Center, including an introduction from Center director Kurt Debus.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20117">
                <text>John F. Kennedy Space Center</text>
              </elementText>
              <elementText elementTextId="20118">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20119">
                <text>1967-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20120">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20121">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20122">
                <text>John F. Kennedy Space Center</text>
              </elementText>
              <elementText elementTextId="20123">
                <text>Launch complexes (Astronautics)</text>
              </elementText>
              <elementText elementTextId="20124">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
              <elementText elementTextId="20125">
                <text>Astronautics--United States</text>
              </elementText>
              <elementText elementTextId="20126">
                <text>Outer space--Exploration</text>
              </elementText>
              <elementText elementTextId="20127">
                <text>Aeronautics--United States</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20128">
                <text>Pamphlets</text>
              </elementText>
              <elementText elementTextId="20129">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20130">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20131">
                <text>Box 36, Folder 103</text>
              </elementText>
              <elementText elementTextId="205812">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20133">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20134">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20135">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1144" public="1" featured="0">
    <fileContainer>
      <file fileId="991">
        <src>https://digitalprojects.uah.edu/files/original/20/1144/spc_stnv_000060.pdf</src>
        <authentication>d62b3e42d82eaccd92efb30379a91002</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177278">
                    <text>,

- -&gt;

*
I

NATIONAL AERO;x.'AUTICS AND SPACE ADMINIS~RATIONI
WO 9-41 5 5
VJAjl-I,:r'GTON, D.C. 20546
TELS' WO 3-6925

1

L3&lt;

J

1

-

-.

GSLil
G

, ' .

Y-

7- f i F-u*-.

*.-.

3
.

r z

(ACCESSION NL'hrtCR)

.

3

1 1

&gt;
C

f
4

9;ili

L
&lt;
( N A S A C R OR

TMX

OR A D N U M U E R )

Address
by
James E. Webb, A d m i n i s t r a t o r
N a t i o n a l Aeronautics and Space A d m i n i s t r a t i o n

i

I

J

I n v e n t o r s ' Congress and Space Symg?osiuin
L i t t l e Rock, Arkansas
October 30, 1964

I,, '

,/

G e r i c a n Procrress and Goals i n Space
\

I t i s h e a r t e n i n g t o p a r t i c i p a t e i n a meeting l i k e

t h i s , one i n which i n v e n t o r s , i n d u s t r i a l r e p r e s e n t a t i v e s ,
and members of t h e S t a t e government cone t o g e t h e r t o
exchange i d e a s .

Such a c t i v i t i e s cannot f a i l t o spur

expanding c r e a t i v e e f f o r t and more d i v e r s i f i e d i n d u s t r i a l
p r o d u c t i o n i n t h i s s t a t e and r e g i o n .
I a m e s p e c i a l l y p l e a s e d t o d i s c u s s t h e N a t i o n a l Space

Program b e f o r e t h i s group t o n i g h t ,

A s p e r s o n s concerned

w i t h i n v e n t i o n and development, you w i l l be e s p e c i a l l y
I

i n t e r e s t e d i n t h e space program, i t s s i g n i f i c a n c e t o t h e
n a t i o n ' s p o s i t i o n of world l e a d e r s h i p , and i t s r e l a t i o n s h i p

�to t h e growth of America

i n a n age merked by e x p l o s i o n s of

knowledge i n a wide v a r i e t y of s c i e n t i f i c and t e c h n i c a l f i e l d s .
Much of t h e p r o g r e s s of t h e world h a s bccn based upon
t h o s e c r e a t i o n s of hard work and i n s p i r a t i o n which w e c a l l
inventions,
times.

T h i s i s no l e s s t r u e today than in e a r l i e r

L e t m e i l l u s t r a t e by . k f e r e n c e t o t h e steam engine,

a source of power on e a r t h , and t o t h e r o c k e t engine, t h e
source o f power i n space,

I t was James Watt who developed

t h e f i r s t r e a l l y s u c c e s s f u l steam engine i n 1774, pursuing'
a s a l o n e l y i n d i v i d u a l a c r e a t i v e idea.

T h i s engine embodied

t h e e s s e n t i a l f e a t u r e s of t h e modern steam engine.

Watt's

engine provided t h e power f o r t h e I n d u s t r i a l Revolution; it
l e d t o r a i l r o a d s , t o steam-operated m i l l s and f a c t o r i e s , t o
steaniboats and s h i p s f o r r i v e r and ocean commerce.

The work o f D r . Robert H. Goddard w i t h p r i m i t i v e

,

liquid-powered r o c k e t s i n t h e 1 9 2 0 ' s and 1930's i n Massachusetts
and New Mexico was i n t h e same p a t t e r n a s W a t t ' s work,

His

was no l e s s a n i n d i v i d u a l achievement, c a r r i e d o u t under
d i s c o u r a g i n g circumstances.
r o c k e t i n 1926

--

The f l i g h t of Goddard's f i r s t

a t o t a l of 184 f e e t i n two and one h a l f seconds

--

�-3-

was one of t h e major e v e n t s l e a d i n g t o t h e f a n t a s t i c speed

of about 25,000 m i l e s p e r hour f o r t o d a y ' s Venus and Mars
probes t o d i s t a n c e s of m i l l i o n s of m i l e s i n t o deep space,
and u l t i m a t e l y w i l l e n a b l e men t o e x p l o r e t h e moon and p l a n e t s .
The power of c r e a t i v e i d e a s such a s D r . Goddard's and
t h e a b i l i t i e s and w i l l i n g n e s s of men t o c a r r y them t o f r u i t i o n
have been among t h e p r i n c i p a l a s s e t s of t h e United S t a t e s s i n c e
i t s foundation.

The r e v o l u t i o n a r y changes t h a t a r e t a k i n g p l a c e

i n s c i e n t i f i c and t e c h n o l o g i c a l p e r s p e c t i v e s through t h e mastery

of s p a c e open v a s t new realms f o r t h e c r e a t i v e a c t of i n v e n t i o n ,
and f o r t h e t r a n s l a t i o n of i n v e n t i o n t o p r a c t i c a l use.

We must

t a k e advantage of t h i s new s i t u a t i o n .
As t h e N a t i o n a l Space Program moves i n t o i t s s e v e n t h y e a r ,

t h e United S t a t e s has reached t h e halfway p o i n t i n a broadb a s e d , a c c e l e r a t e d program f o r t h e p r e s e n t decade, a program
t h a t w a s planned and h a s been c a r r i e d forward by t h r e e
Adninistratiocs.

L e t me b r i e f l y d i s c u s s w i t h you some of t h e

major achievements and plans of t h i s program:

o

Manned s p a c e c r a f t f ~ cra r r y i n g crews i n n e a r - e a r t h o r b i t s

of long d u r a t i o n , f o r i n v e s t i g a t i n g space outwsrd a q u a r t e r of
a m i l l i o n m i l e s from t h e e a r t h , and f o r t a k i n g a s t r o n a u t s t o
e x p l o r e t h e moon and t o r e t u r n them s a f e l y home.

�--

?dvanced, highly instrcmented, c n n ~ a n n e d s p z c e c r a f t

,,,,l..r.atically progranxned
--

-,,,,h

or remotely c o n t r o l l e d b y r a d i o from

f o r m i s s i o n s m i l l i o n s of m i l e s deep i n space, i n c l u d i n g

.

,-..,ftto examine t h e p l a n e t s e l e c t r o n i c a l l y , b y photography,

*.

?
.,

t o transmit t h e information t o e a r t h s t a t i o n s .
One

.:;.:t

0 2 t h e s e extremely d i f f i c u l t f e a t s w i l l b e a t t e m p t e d

nonth, d u r i n g a 30-day p e r i o d f o l l o w i n g Novefier 4.

NASA

launch two 570-pound Mariner s p a c e c r a f t t o f l y by t h e
? l a n e t Mars, j u s t a.s Nariner I1 f l e w b y Venus a b o u t two y e a r s
a;o.

Tne c h i e f d i f f e r e n c e , and it i s a b i g one, i s t h a t Venus

x i s 3 6 m i l l i o n m i l e s d i s t a n t from e a r t h and Mars w i l l b e

1 5 0 r n i l l i ~ nmiles.

about

The Venus voyage took a l i t t l e over t h r e e

months; t h e Mars f l i g h t w i l l r e q u i r e almost e i g h t and one-half

Each of t h e s p a c e c r a f t
apart

-- w i l l

--

which w i l l b e launched a few days

c a r r y i n s t r u m e n t s f o r e i g h t s c i e n t i f i c experiments;

s i x of t h e s e a r e designed t o measure r a d i a t i o n , magnetic f i e l d s ,
and 'micrometeorites i n i n t e r p l a n e t a r y space and near Mars.

If

a l l ' g o e s w e l l , a t e l e v i s i o n camera aboard each c r a f t w i l l t a k e
up t o 22 s t i l l photographs of Mars, and a s p e c i a l d e v i c e t o

determine t h e c h a r a c t e r i s t i c s of t h e &amp;YIartianatmospheric p r e s s u r e

'"ill be t u r n e d on.
L

~ o r i e sa r e achieved,

The t e l e v i s i o n p i c t u r e s , i f planned t r a j e c should be comparable i n d e t a i l w i t h photo-

�graphs of t h e moon t a k e n by t h e b e s t e a r t h - b a s e d t e l e s c o p e s ,

These first p i c p e e r i n g m i s s i o n s c a n ~ o tprove or d . i s p r s v e
t h e e x i s t e n c e of l i f e on K a r s , b u t t h e y can, i f s u c c e s s f u l ,
i n c r e a s e o u r knowledge of t h e p r o b a b i l i t i e s .
We have had
t~ /'success w i t h a s e r i e s of weather s a t k l l i t e s which have
photographed from high above thousands of cloud p a t t e r n s ,
i n d i c a t i n g p r e v a i l i n g weather f r o n t movements.

These s a t e l l i t e s

i n c l u d e s o f a r e i g h t s f t h e T i r o s s e r i e s and one of t h e Nimbus
series,

I n a d d i t i o n t o cloud photos from t h e sunward s i d e of

t h e e a r t h , some of t h e weather s a t e l l i t e s , n o t a b l y Nimbus, have
employed i n f r a - r e d s e n s o r s t o map weather p a t t e r n s a t n i g h t .
I n s t z l l e d on some of N A S A ' s e a r l i e s t s a t e l l i t e s were f o r e r u n n e r s of t h e i n s t r u m e n t s which have achieved such h i g h d e g r e e s

a€ s u c c e s s f o r T i r o s and Nin-ibus,
e

We have r e f l e c t e d o f f t h e g i a n t , aluminized Echo

b a l l o o n - s a t e l l i t e thousands of r a d i o , r a d i o - t e l e p h o n e ,
f a c s i m i l e , and o t h e r e l e c t r o n i c s i g n a l s

--

photo-

c l e a r messages

between p o i n t s thousands of m i l e s a p a r t on t h e e a r t h ' s s u r f a c e ,

Echo i s a " p a s s i v e u s a t e l l i t e , a n o r b i t i n g " m i r r o r i n t h e sky"
for electronic signals.

e

T e l s t a r , Relay, and Syncom a r e America's " a c t i v e n

comunications s a t e l l i t e s .

That i s , t h e y p i c k up from e a r t h

s t a t i o n s s i g n a l s s f t h e r a d i o o r t e l e v i s i o n t y p e s , r e c o r d them

�-6-

,,i 3 a g n e t i c

t a p e s , t h e n r e t r a n s n i t t o distant p o i n t ? c n t h e q l c b e ,

l n Syncon we have t h e f i r s t s o - c a l l e d

"stationary" s a t e l l i t e s

which, s i n c e t h e y o r b i t a t 2 2 , 3 0 0 m i l e s above t h e e a r t h , hover
aSove t h e same s p o t .
s

Our o r b i t i n g ~ b s e r v a t o r i e sof s e v e r a l t y p e s n o t o n l y

study t h e e a r t h from above i t s atmosphere, a s we91 a s t h e
sun and t h e s t a r s , b u t a l s o measure s o l a r and cosmic r a d i a t i o n
and t h e f o r c e s of g r a v i t a t i o n and magnetism n e a r t h e e a r t h and
t o v a s t d i s t a n c e s ~ u itn space,
@

We a r e b u i l d i n g r e l i a b l e and v e r s a t i l e r o c k e t e n g i n e s

t h a t w i l l develop tremendous t h r u s t s , r a n g i n g from 1.5 m i l l i o n
pounds f o r S a t u r n I t o 7,5 m i l l i o n pounds f o r t h e S a t u r n V,
These g i a n t pawer e n g i n e s w i l l b e c a p a b l e of c a r r y i n g o u t
missions i n s p a c e r e q u i r e d by t h e n a t i o n a l i n t e r e s t s d u r i n g t h e
p r e s e n t decade and perhaps f o r a longer p e r i o d .

o

The n l t i o n a l space program has e s t a b l i s h e d a world-

wide t r a c k i n g and d a t a a c q u i s i t i o n network,
0

We have b u i l t and a r e b u i l d i n g o t h e r l a r g e ground

f a c i l i t i e s f o r f a b r i c s t i n g , t e s t i n g , l a u n c h i n g , and c o n t r o l l i x g
t h e new r o c k e t s and s p a c e c r a f t

--

f a c i l i t i e s t h a t w i l l be b a s i c

n a t i o n a l a s s e t s f o r many y e a r s t o come,

a

NASA r e s e a r c h and development c e n t e r s , s t a f f e d w i t h s k i l l e d

�1

and experienced p e r s o n n e l , a r e s t u d y i n g what t h e United S t a t e s
r e q u i r e s i n spzce and what i t can accon~?li.cii, A t t h e sarce
time t h e s e p e r s o n n e l work with i n d u s t r y , where more t h a n 90
p e r c e n t of t h e NASA funds a r e s p e n t , i n t h e p r o d u c t i o n of
t h e r o c k e t s , s p a c e c r a f t , and o t h e r equipment,
o

W e have augmented t h e n a t i o n ' s r e s e a r c h c a p a b i l i t i e s

i n our u n i v e r s i t i e s by means of t r a i n i n g g r a n t s , f a c i l i t i e s
g r a n t s , and r e s e a r c h g r a n t s and c o n t r a c t s .

o

The program h a s founded an i n d u s t r i a l b a s e t h a t c a n

meet any n a t i o n a l needs i n space t h a t may develop, and many
r e q u i r e m e n t s on earth.
I t i s important t o n o t e t h a t NASA works v e r y c l o s e l y w i t h
t h e A i r Force i n manned space f l i g h t ,

The Gemini two-man

s p a c e c r a f t w i l l s e r v e t h e A i r Force a s a key element i n i t s
,Qnned

O r b i t i n g L a b o r a t o r y prognam.

The t o t a l NASA e f f o r t

c o n t r i b u t e s technology, s c i e n t i f i c d e s c r i p t i o n of i t s s p a c e
envirosment, and o p e r a t i o n a l e x p e r i e n c e t o a wide v a r i e t y of
d e f e n s e projects.

The Department of Defense, i n t u r n , s h a r e s

a p p l i c a b l e knowledge from i t s m i l i t 3 r y p r o j e c t s with NASA,

This

exchange i s a n i n t e g r a l p a r t of t h e concept of a n a t i o n a l space
progrm
These a r e t h e n ? t i o n a l r e s o u r c e s a n d f a c i l i t i e s which t h e
space program i s c r e a t i n g and p r ~ v i n go u t ,

They a r e of key

importance t o the p r e c e n t s t r e n g t h and t o tka f u t u r e of t h e
United S t a t e s ,

�The present r.39.e of EASA in aerona!-iticaland space

research is a continuation and extension of that occupied.
by its predecessor agency, the National Advisory Committee

for ~eronautics, For more than 40 years, this civilian agency
supgl.ied the basic scientific knowledge and technological
development required to undergird our national requirements
in aeronautics, both civil and military, and enabled the
nation to assumeunquestiomlik supremacy in the air.

Today,

NASA is conducting research and development in support of

every agency of the government which has, or may encounter,
the need for operational activity in space.

This includes

the Weather Bureau in meteorological satellite operations, the
Communications Satellite Corporation, and the Department of
Defense.
Ma:l's

experience in space is limited, and all of the

potential requiremezts and opportunities which it presents
cannot yet be forsseen, But it is evident that they are there,
And it is evident that not only we, bwt the Soviet Union and

many other nations, also know they are there and intend to
exploit them to enhance both their prestige and their power;
Tha recent Soviet VosXh3d flight, during which three men

�o r b i t e d t h e e a r t h i n a single s p a c e m f t , w a s a s i g n i f i c a n t
space accomplishment, and a convincing demonstration t h a t t h e
Russians i n t e n d t o p r e s s forward i n manned s p a c e f l i g h t a c t i v i t y .
A t t h i s s t a g e i n t h e space e f f o r t , t h e S o v i e t Union

c o n t i n u e s t o e n j o y t h e advantage i n o p e r a t i o n a l r o c k e t power
t h a t i t h a s h e l d s i n c e t h e o u t s e t of t h e Space Age.
c a t c h i n g up.

But we a r e

The 1 . 5 m i l l i o n pound t h r u s t S a t u r n I launch

v e h i c l e , a l r e a d y s u c c e s s f u l l y f l i g h t t e s t e d on seven o c c a s i o n s ,
c a p a b l e of p l a c i n g 38,700 pounds i n e a r t h o r b i t .

The

S a t u r n V, now under development, w i l l g e n e r a t e 7.5 m i l l i o n
.

.

pounds of t h r u s t and p l a c e 240,000 pounds i n t o e a r t h o r b i t , and

it w i l l a l s o launch our e x p l o r e r s t o t h e moon.
Let me add a

arm-d

about t h e Apollo program, which h a s

l u n a r e x p l o r a t i o n a s one of i t s g o a l s .

I t i s imoortant t h a t

e v e r y ~ m e r i c a nr e c o q n i z e t h a t t h e fundamental o b j e c t i v e of t h e
Apollo program, and of t h e e n t i r e n a t i o n a l s p a c e e f f o r t ,
pre-eminence i n s p a c e , and n o t t h e achievement of any s i n g l e
s p e c i f i c goal.

To a c h i e v e space l e a d e r s h i p , t h e n a t i o n must

d e v e l o p t h e f a c i l i t i e s , t h e technology, t h e s c i e n t i f i c
knowledge and t h e a b i l i t y t o o p e r a t e i n s p a c e a s we have

�l e a r n e d t o o p e r a t e on t h e l a n d , s e a , and i n t h e a i r .
I t i s e s t i m a t e d t h a t 90 p e r c e n t of t h e e x p e n d i t u r e s

b e i n g made i n t h e Apollo program would be r e q u i r e d t o a c h i e v e
pre-eminence i n s p a c e , even i f we had no i n t e n t i o n of going
t o t h e moon.

Moreover, y e a r s of o r d e r l y e x p e r i m e n t a l f l i g h t

w i l l be conducted i n o r b i t near t h e e a r t h , b e f o r e t h e f i r s t
a s t r o n a u t s set o f f f o r t h e moon.

We w i l l l e a r n t o maneuver

i n s p a c e , t o j o i n s p a c e c r a f t i n o r b i t , t o f l y o u t a t w i l l and

return a t w i l l .

Although one o b j e c t i v e i s t h e moon, t h e

n a t i o n w i l l accumulate some 5,000 man h o u r s of f l i g h t i n
n e a r - e a r t h o r b i t b e f o r e t h e f i r s t a t t e m p t i s made t o launch
Apollo t o t h e moon.

That i s almost 100 t i m e s t h e e x p e r i e n c e

i n e a r t h o r b i t which was accumulated by a l l of our a s t r o n a u t s
d u r i n g a l l o f the f l i g h t s i n t h e Mercury program.
The i m p l i c a t i o n s of t h i s e x p e r i e n c e , and t h e a c q u i s i t i ~ n

of t h i s o p e r a k i o n a l s k i l l f o r b o t h c i v i l i a n s p a c e programs

and t h o s e o f t h e Department of Defense, a r e a p p a r e n t ,
The United S t a t e s space program h a s y i e l d e d f o r t h i s
n a t i o n one s i g n i f i c a n t b e n e f i t which t h e Russians have n o t
been a b l e t o g a i n from t h e i r s e c r e t space a c t i v i t y .

It h a s

�becorns a s i g n i f i c a n t force E c r i n t e r n a t ions: 2 0 - o ~ ~t ri oa n
between t h e U n i t e d S t a t e s and o t h e r n a t i o n s of t h e w o r l d ,
and s t r e n g t h e n e d o u r t i e s n o t o n l y w i t h o u r F r e e \j?orld
a l l i e s , b u t w i t h many o f t h e ercerging n a t i o n s .
NASA c u r r e n t l y h a s 2 2 o p e r a t i o n a l

t r a c k i n g and d a t a

a c q u i s i t i o n s t a t i o n s l o c a t e d i n 1 8 d i f f e r e n t counizries,
with t h r e e additional locations a g r e e d u p n b u t not y e t
operational.

Such s t a t i o n s r e 2 r e s e n t c o m o n e f f o r t s and

c e n t e r s f o r c o n t i n u e d growth of u n d e r s t a n d i n g and c o - o p e r a t i o n .
Three i n t e r n a t i o n a l s a t e l l i t e s which w e r e c o n c e i v e d ,
d e s i g n e d , f i n a n c e d and e n g i n e e r e d abroad

--

A r i e l I and I1

f o r t h e B r i t i s h and A l o u e t t e I f o r t h e Canadians

been l a u n c h e d by NASA.

--

have

Additional s a t e l l i t e launchings a r e

s c h e d u l e d f o r b o t h of these c o u n t r i e s a s w e l l a s f o r t h e
F r e n c h , I t a l i a n s and t h a European S2ace R e s e a r c h O r g a n i z a t i o n .
N i n e French and B r i t i s h e x p e r i m e n t s a r e scheduleii f o r i n -

c l u s i o n on NASA s a t e l l i t e s which w i l l be l a u n c h e d over t h e
n e x t few y e a r s

.

NASA h a s c a r r i e d o u t 65 c o - o p e r a t i v e

l a u n c h i n g s of

sounding r o c k e t s w i t h 11 c o u n t r i e s , and c u r r e n t l y has

�,greements w l t h t h r e e a d d i t i o n a l c o u n t r i e s f o r such p r o j e c t s .

I n a d d i t i o n , 41 c o u n t r i e s a r c now p a r t i c i p a t i n g i n N A S F ' S
m e t e o r o l o g i c a l s a t e l l i t e p r o j e c t s , c o n d u c t i n g s p e c i a l sbs e r v a t i o n s of l o c a l w e a t h e r c o n d i t i o n s a t t h e i r own e x p e n s e
which a r e s y n c h r o n i z e d w i t h the p a s s e s o f U . S. w e a t h e r
satellites.

Seven c o u n t r i e s have a l r e a d y b u i l t e x p e n s i v e

ground t e r m i n a l s and conductzd t e s t t r a n s m i s s i o n s i n connect i o n w i t h o u r communications s a t e l l i t e program, and a g r e e ments have been r e a c h e d w i t h f o u r o t h e r c o u n t r i e s .

You a r e

a l l f a m i l i a r , I am s u r e , w i t h t h e c o - o p e r a t i v e a r r a n g e m e n t s
rsached w i t h Japan providing f o r d i r e c t t e l e v i s i o n coverage
of t h e Olympic Games v i a t h e Syncom s a t e l l i t e .
I n t e r n a t i o n a l p e r s o n n e l exchanges, which p r o v i d e f o r
d i r e c t c o n t a c t s between s c i e n t i f i c and t e c h n i c a l p e r s o n n e l ,
c o n t r i b u t e i m p o r t a n t l y t o a l l o f t h e above c o - o p e r a t i v e
efforts.

Under t h e XASA f e l l o w s h i p program, t h e s p o n s o r i n g

c o u n t r y pays for t h e t r a v e l and s u b s i s t e n c e o f i t s t r a i n e e s .
T h i s r e q u i r e r e n t f o r investment on t h e p a r t of t h e p a r t i c i pating country assures careful consideration of t h e personnel
s e l e c t e d and t h e i r f u t u r e u t i l i z a t i o n when t h e y r e t u r n .
C o s t s o f i n s t r u c t i o n a r d borne by XASA.

�A t the

present time, t h e r e a r e 9 2 I n t e r n a t i o n a l

Research E z s s o c i a t e s i n NASA c e n t e r s , 44 I n t e r n a t i o n a l
Graduate ?ello-v?s i n U. S. U n i v e r s i t i e s , and 176 f o r e i g n
t e c h n i c a l t r a i n e e s a t NASA c e n t e r s i n s u p p o r t of c o - o p e r a t i v e
p r o j e c t s and ground f a c i l i t y o p e r a t i o n s ,

I n addition t o the

formal exchanges, EASA and i t s c e n t e r s are h o s t s t o numerous
foreign v i s i t o r s ,

U p t o J u l y 1 of t h i s y e a r , t h e r e had been

8 , 4 0 0 such v i s i t o r s from 95 c o u n t r i e s ; 1,900 d u r i n g t h e l a s t
s i x months.
T h e s p a c e program i s producing new s c i e n t i f i c knowledge

w i t h wide i m p l i c a t i o n s f o r p r a c t i c a l use.

A n o f f i c i a l of

t h e Westinghouse A i r Brake Company was quoted t h i s week
t h a t "Space r e s e a r c h i s c r e a t i n g a ' t e r r i f i c
f a l l o u t ' of b a s i c knowledge which o l d e r i n d u s t r i e s a r e t r y ing t o u t i l i z e , "

I n a d d i t i o n , t h e ailvances i n technology r e q u i r e d t o
b u i l d , launch and o s e r a t e t h e b o o s t e r s and s p a c e c r a f t are
p r o v i d i n g t h e base f o r much of t h e technology of t h e f u t u r e :
i n materials,

i n e l e c t r o n i c s , i n processing, i n r e l i a b i l i t y ,

and i n v i r t u a l l y e-7ery f i e l d of technology,

�AS

of S e p t e n b e r 1, 1 9 6 4 , EASA had r e c e i v e d from a l l

s o u r c e s 3 , 5 1 9 d i s c l o s u r e s of i n v e n t i o n s b e l i e v e d t o p o s s e s s
patentable novelty.

TWOthousand two hundred and f o r t y of

t h e s e were r e c e i v e d from c o n t r a c t o r s and 1 , 2 7 9 from N A S A ' s
own employees.

Of t h i s t o t a l , 2 , 1 1 1 d i s c l o s u r e s have been

placed i n the inactive f i l e s ,

One thousand f o u r hundred

and e i g h t d i s c l o s u r e s were a c t i v e a s o f September 1.

Of

t h e s e , 508 a r e t h e s u b j e c t s of p a t e n t a p p l i c a t i o n s .
One of NASA's own i n v e n t o r s i s Mrs. B a r b a r a Lunde.
T h i s a t t r a c t i v e 26-year-old

aerospace engineer-housewife

works a t o u r Goddard Space F l i g h t C e n t e r , i n Maryland,

just o u t s i d e Washington,

Mrs. Lunde h a s two p a t e n t a p p l i c a -

t i o n s b e i n g c o n s i d e r e d b y t h e P a t e n t O f f i c e and h a s d i s c l o s e d
f o u r more f o r c o n s i d e r a t i o n .

Her i n v e n t i o n s i n c l u d e two

v a l v e s , f o r s p a c e c r a f t , :.~hich have no moving p a r t s ,
Tomorrow, M r . Breene Kerr w i l l t e l l you i n d e t a i l of
t h e NASA Technology U t i l i z a t i o n grogram d e s i g n e d t o make a l l
o f t h e s e advances q u i c k l y a v a i l a b l e t h r o u g h o u t t h e K a t i o n ,
I u r g e you t o t a k e f u l l advantage of t h i s program i n A r k a n s a s .

I t i s o f major i m ~ o r t a n c et o your economic f u t u r e .

Bear i n

�,ind

t h a t it t o o k 112 years t o d e v e l o p photography t o a n
d e g r e e , 56 y e a r s t o d e v e l o p t h e t e l e p h o n e , 35 y e a r s

t o p e r f e c t t h e r a d i o , 15 years t o develop r a d a r .

Television

took 12 y e a r s , t h e a t o m i c bomb s i x and t h e t r a n s i s t o r f i v e .
I n t h i s c o n n e c t i o n , it i s of s i g n i f i c a n c e t o t h e S t a t e
of Arkansas t h a t a major p a r t of t h e n a t i o n ' s s p a c e i n s t a l l a -

t i o n s a r e a l r e a d y f u n c t i o n i n g t o t h e s o u t h and e a s t of your
State.
I r e f e r t o what h a s been c a l l e d t h e S o u t h e r n C r e s c e n t

of t h e s p a c e program.
The f i r s t o f t h e s e i s t h e Cape Kennedy complex, t h e
major s i t e f o r t h e l a u n c h i n g of o u r l a r g e r o c k e t s .

This i s

a permanent i n s t a l l a t i o n , a major e l e m e n t i n t h e n a t i o n ' s
c a p a c i t y t o go i n t o s p a c e .

It is already a large f a c i l i t y

and i s b e i n g expanded g r e a t l y t o accommodate t h e l a r g e
S a t u r n r o c k e t s which w i l l c a r r y o u r a s t r o n a u t s t o t h e moon.
To g i v e you some i d e a o f t h e s c o p e o f t h i s u n d e r t a k i n g :
d u r i n g t h e p a s t t h r e e F i s c a l Years some 700 m i l l i o n d o l l a r s
was a p p r o p r i a t e d f o r c o n s t r u c t i o n of NASA f a c i l i t i e s a t
Cape Kennedy.

�The second p a r t of t h i s development i s t h e M a r s h a l l
Space F l i g h t C e n t e r a t H u n t s v i l l e , Alabama.

There some 6 , 5 0 0

p e o p l e a r e a t work, p r i m a r i l y engaged i n b u i l d i n g t h e f i r s t
of t h e g r e a t S a t u r n r o c k e t s , w i t h t o t a l o p e r a t i n g c o s t s f o r
t h e c u r r e n t F i s c a l Year o f over 100 m i l l i o n d o l l a r s , and w i t h
a c o n s t r u c t i o n program a b o u t a t h i r d a s l a r g e .
The t h i r d p a r t i s found i n a complex a t Michoud,
L o u i s i a n a , and i n n e a r b y s o u t h e r n M i s s i s s i p p i .

A t Michoud,

a World War I1 a i r c r a f t p l a n t , a l r e a d y owned by t h e
Government, i s b e i n g used t o b u i l d t h e f i r s t s t a g e s of t h e
S a t u r n I-B and S a t u r n V r o c k e t s ,
persons.

I t employs o v e r 1 1 , 0 0 0

Not f a r from Michoud i s b e i n g c o n s t r u c t e d t h e

M i s s i s s i p p i T e s t F a c i l i t y , where t h e S a t u r n r o c k e t s w i l l b e
checked o u t and t e s t e d t h o r o u g h l y .

I n t i m e , some 3 , 3 0 0

s c i e n t i s t s , e n g i n e e r s , and t e c h n i c i a n s and s u p p o r t w o r k e r s
w i l l b e a t work a t t h i s massive f a c i l i t y .

The l a s t p a r t i s a t Houston, where t h e Manned S p a c e c r a f t
Center i s being constructed.

This, l i k e t h e o t h e r s t h a t I

have c i t e d , i s a permanent i n s t a l l a t i o n d e s i g n e d t o be t h e
c e n t e r f o r a l l o f o u r e f f o r t s t o s e n d man i n t o s p a c e .

�c u r r e n t l y , t h ~ r ea r e mar@ "Lha.11

4,000 p n o p l ~eit .sror!r a t the

Houston C e n t e r , and q u i t e l i k e l y t h i s number will i n c r e a s e

in t h e f u t u r e .
One o f t h e c e n t r a l f a c t s about t h i s g r e a t complex of
space a c t i v i t i e s t h a t I have d e s c r i b e d i s t h e p o s s i b i l i t y
t h a t many v a r i e d research, developmant and p r o d u c t i o n
activities w i l l gravitate in t h i s direction.

T h i s i s made

l i k e l y by r e a s o n s of economics and of convenience.
By and l a r g e , t h e s e w i l l be a c t i v i t i e s t h a t r e q u i r e

heavy c o n t r i b u t i o n s from s c i e n c e and technology, and
Arkansas and t h e o t h e r s t a t e s of t h e South a r e now i n a
p o s i t i o n t o g e t r e a d y t o t a k e f u l l advantage of the p r o s p e c t .

Arkansas must b e a b l e t o advance i n such a r e a s a s e l e c t r o n i c s ,
i n t h e development and use of new m a t e r i a l s , i n medical
r e s e a r c h r e l a t e d t o t h e s e v e r e r e q u i r e m e n t s of s p a c e , and
the like.

I t must n o t only make p r o v i s i o n s f o r s u i t a b l e

working art! l i v i n g c o n d i t i o n s f o r s c i e n t i s t s and e n g i n e e r s ,
it must a l s o be f a r - s i g h t e d i n t r a i n i n g i t s people a s

t e c h n i c i a n s and s k i l l e d workmen, f o r t h e s e are a s e s s e n t i a l

i n t h i s k i n d of a c t i v i t y a s t h e s c i e n t i s t s and e n g i n e e r s .

�I n conclcsion, I w o u l d l i k ? t o emphasize that -just as
t h s devslopment of t h e autornobil*: and the a i r c r a f t i n d u s t r i z s

r e s u l t e d i n a g r e a t e r and s t r o n ~ e rn a t i o n a l economy acd
provi3ed nevv j o b s f o r m i l l i o r . ~ , o u r v e n t u r e i n t o s p a c e i s
s t i m u l a t i n g t e c h n o l o g y and s p u r r i n g o u r economy toward new
and g r e a t e r h e i g h t s .

Furthe?more, o u r s p a c e prograni i s

enhancing t h e n a t i o n ' s c d u c s ? i o n a l s t a n d a r d s a t a t i m e when
the ray.id advance of t e c h r . c _ i s g i c a l achievement makes even
g r e a t e r demands upon e d u c a t i n n .
Faen w e add the w i l l and t h e d e t e r m i n a t i o n o f Americans,

a s i n d i v i d u a l s and a s a p e o &gt; l e , and t h e i n g e n u i t y of o u r

government-industry-v1niver5ity complex, w e have a program
f o r t h e s u c c e s s f ~ le x p l o r a t i o n of s p a c e f o r t h e b e t t e r m e n t
of a l l mankind.

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20093">
                <text>spc_stnv_000060</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20094">
                <text>"American Progress and Goals in Space," address by James E. Webb.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20095">
                <text>This address was given by James E. Webb, Administrator, National Aeronautics and Space Administration, at the Inventors' Congress and Space Symposium, Little Rock, Arkansas.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20096">
                <text>Webb, James E. (James Edwin), 1906-1992</text>
              </elementText>
              <elementText elementTextId="20097">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20098">
                <text>1964-10-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20099">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20100">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20101">
                <text>Astronautics and state--United States</text>
              </elementText>
              <elementText elementTextId="20102">
                <text>Space race</text>
              </elementText>
              <elementText elementTextId="20103">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20104">
                <text>Speeches</text>
              </elementText>
              <elementText elementTextId="20105">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20106">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20107">
                <text>Box 12, Folder 32</text>
              </elementText>
              <elementText elementTextId="205811">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="70">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="20109">
                <text>NASA News</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20110">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20111">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20112">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13794" public="1" featured="0">
    <fileContainer>
      <file fileId="10423">
        <src>https://digitalprojects.uah.edu/files/original/193/13794/Defense_Billboard_124_001.pdf</src>
        <authentication>84605ef7fc39c9448964800815d77560</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197480">
                    <text>American Forces Information Service • Department of Defense
601 N.Fairfax Street Suite 312.• Alexandria. VA 223H-2007 •(7031428-0283, DSN 328-0283

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="193">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="194954">
                  <text>Defense Billboard Posters</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="195400">
                <text>Defense_Billboard_124</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195401">
                <text>"Amphetimines; Get nowhere fast"</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="195402">
                <text>D2.9:D36/2/No.124</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195403">
                <text>Man going crazy taking a pill</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195404">
                <text>Department of Defense</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195405">
                <text>1998-04-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="195406">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195407">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="195408">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="195409">
                <text>Amphetamine abuse</text>
              </elementText>
              <elementText elementTextId="195410">
                <text>Drug addiction</text>
              </elementText>
              <elementText elementTextId="195411">
                <text>Dogs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195412">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="195413">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="195414">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="195415">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="195416">
                <text>Case 1, Drawer 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195417">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195418">
                <text>This material may be protected&#13;
under U. S. Copyright Law (Title 17,&#13;
U.S. Code) which governs the&#13;
making of photocopies or&#13;
reproductions of copyrighted&#13;
materials. You may use the digitized&#13;
material for private study,&#13;
scholarship, or research. Though&#13;
the University of Alabama in&#13;
Huntsville Archives and Special&#13;
Collections has physical ownership&#13;
of the material in its collections, in&#13;
some cases we may not own the&#13;
copyright to the material. It is the&#13;
patron's obligation to determine&#13;
and satisfy copyright restrictions&#13;
when publishing or otherwise&#13;
distributing materials found in our&#13;
collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="195419">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1215" public="1" featured="0">
    <fileContainer>
      <file fileId="1062">
        <src>https://digitalprojects.uah.edu/files/original/9/1215/spc_dann_000211.mp4</src>
        <authentication>f1b1f5917bf9dd586637639766bdacb8</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="59">
                  <text>Konrad Dannenberg Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="41832">
                  <text>Konrad Dannenberg Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="205164">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/99"&gt;View the Konrad Dannenberg Collection finding aid on ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="21622">
                <text>spc_dann_000211</text>
              </elementText>
              <elementText elementTextId="21623">
                <text>MC_43_095</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21624">
                <text>"An afternoon walk thru the farm."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21625">
                <text>Konrad and Ingeborg Dannenberg visit Alma's farmhouse. Shown are clips of George playing in the grass and others walking around the farm. Fall 1967.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21626">
                <text>Dannenberg, Konrad</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21627">
                <text>1967-09-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="21628">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21629">
                <text>Dannenberg, Konrad</text>
              </elementText>
              <elementText elementTextId="21630">
                <text>Family vacations</text>
              </elementText>
              <elementText elementTextId="21631">
                <text>German Americans</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21632">
                <text>8 mm (photographic film size)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21633">
                <text>Home movies</text>
              </elementText>
              <elementText elementTextId="21634">
                <text>Moving Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="21635">
                <text>Konrad Dannenberg Collection</text>
              </elementText>
              <elementText elementTextId="205878">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="90">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="21638">
                <text>Donated by Klaus Dannenberg. Digitized for the 2019-2020 CLIR Recordings at Risk grant.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21639">
                <text>de</text>
              </elementText>
              <elementText elementTextId="21640">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21641">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="21642">
                <text>clir_grant_film_metadata_01</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10969" public="1" featured="0">
    <fileContainer>
      <file fileId="9447">
        <src>https://digitalprojects.uah.edu/files/original/20/10969/Iterguidscheitsappllunaland_081407120855.pdf</src>
        <authentication>aec119c87f8e9f99cfeb0abe4e897df7</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="167195">
                <text>Iterguidscheitsappllunaland.pdf</text>
              </elementText>
              <elementText elementTextId="167196">
                <text>spc_stnv_000348</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167197">
                <text>"An Iterative Guidance Scheme and Its Application to Lunar Landing."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="167198">
                <text>TN D-2869</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167199">
                <text>A guidance scheme for vehicle flight from lunar orbit to a prescribed point on a spherical, non-rotating moon is presented. The equations of motion have been simplified only to perm it a closed solution for the thrust magnitude and thrust direction. The trajectory computations them selves are made under more realistic and accurate assumptions and are not included.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167200">
                <text>Horn, Helmut J.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167201">
                <text>1965-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="167202">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167203">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="167204">
                <text>Lunar landing</text>
              </elementText>
              <elementText elementTextId="167205">
                <text>Spacecraft guidance</text>
              </elementText>
              <elementText elementTextId="167206">
                <text>Space vehicles--Guidance systems</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167207">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="167208">
                <text>Guidence Schemes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="167209">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="167210">
                <text>Box 14, Folder 22</text>
              </elementText>
              <elementText elementTextId="210661">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167212">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="167213">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="167214">
                <text>spc_stnv_000325_000349</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="167215">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17169"&gt; View this item in ArchivesSpace. &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1146" public="1" featured="0">
    <fileContainer>
      <file fileId="993">
        <src>https://digitalprojects.uah.edu/files/original/20/1146/spc_stnv_000062.pdf</src>
        <authentication>8efd923cf171c8ba40ec870024c5ba75</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177280">
                    <text>ANALOG SIMULATION 0

STAGE

PROPULSION SYSTEM DYNAMIC CHARACTERISTICS

J. W. L e h n e r
Senior E n g i n e e r
C h r y s l e r C o r p o r a t i o n Huntsville Ope r a t i o n s

�Analog Simulation of Saturn S-IB Stage
Propulsion System Dynamic Characteristics

ABSTRACT
The purpose of this paper is to present the
the development of an analog computer model to
sion system dynamic characteristics.
tions a r e included.

employed in
stage propulassump-

INTRODUCTION
The propulsion model was developed to investigate the possibility of sustained
ongitudinal oscillations occurring a t any time during f i r s t stage powered
. It was designed to be used in conjunction with a dynamic struce propulsion system feed back (closed-loop) behavior. This phenomenon occurs when propellant tank fluid pressure perturbations (transmitted through
the propulsion system) a r e sufficient to be amplified by propulsion system/structure
interaction.
The propulsion system to be described is defined as the fluid-mechanical
components from the propellant tank bottoms through the H-1 engines. This system is
composed of eight engines (four non-gimbaled inboard engines and four gimbaled outboard engines) and sixteen feed lines (two per engine). However, only one feed lineengine system is simulated and used a s representative. It is presented in two parts,
feed lines and engine, to best project the methods and logic involved.
Schematics a r e presented which illustrate the physical characteristics of each
system. Numerical designations a r e assigned to each liquid-mechanical line segment
interface and power generating subsystem location. The resulting system subdivisions
a r e modeled individually using their respective numerical designations as the subs criptive nomenclature for model formulation.
Analytical and empirical methods a r e used to describe each subsystem. The
lumped parameter technique is used to define fluid dynamic and turbine-turbopump
dynamic characteristics. Characteristic equations simulate pump, turbine and combustion chamber steady state performance. Other specially derived techniques (not
developed in this paper) a r e used to describe line elasticity and combustion chamber
pressure time delays. These equations a r e then combined, in the manner illustrated
in logic diagrams, to form dynamic math models of the feed lines (LOX and fuel) and
engine .
System peculiarities such a s pump inlet cavitation compliance, pump dynamic
gain, feed line fluid-structure interconnect and combustion chamber pressure delay
were investigated in separate special studies to determine their influence on system

�response. These studies were performed using test methods in conjunction with
computer model studies. The results were inconclusive; however, assumptions were
made that reduced the effect of the resulting model deficiencies. These assumptions
a r e delineated in the following system descriptions.

Method of Fluid-Mechanic System Analysis
The fluid-mechanical systems to be described a r e subdivided into individual
line segments of a size less than a 30 cps one-quarter wave length to allow for an
acceptable frequency response range of 0-30 cps . The location of each segment was
dictated by simulation requirements . Their dynamic properties, inertance (I),
capacitance (C) and resistance (R), were individually lumped a s illustrated in Figure 1
to permit the following treatment.
Fluid inertance, that property of fluids which resists acceleration, appears
in the general flow equation which expresses fluid flowrate ( W - lb/sec) a s a function
of inertance ( I - sec2/in2) and the pressure differential [ (pi-p0-&amp;) - lb/in2 1
available for fluid acceleration:

Inertance is calculated using line (segment) length (L - inches), line cross-sectional
a r e a (A - in2) and the gravity constant ( g = 386.4 in/sec2) a s follows:

A fluid flowing through a container will experience a pressure drop due to
resistance resulting from fluid viscosity and/or momentum losses. The effect of this
resistance (R - sec/in2) is reflected in the following equation:

where the resistance is calculated from known flow conditions by:

Capacitance is that property of a fluid-mechanical system which accounts for
system elasticity. This t e r m is a function of both fluid and container (line) elasticity.
However, in most cases for this model, line influence is insignificant. The effect on
system behavior is characterized by the following ecpation:

�where the capacitance (C - in2) is calculated using container volume (V - in3), fluid
specific weight (Q - 1b/in3) and fluid-mechanical system effective bulk modulus
(
- lb/in2) a s follows :

teff

The term geff includes the effect of line elasticity and is determined as a
function of fluid bulk modulus ( p ) , line diameter (D = inches), line thickness ( t - inches)
and line modulus of elasticity (E - lb/in2) by:

It was necessary in some cases to use effective values of inertance and capacitance due to varying segment (line) geometry. These values were calculated by dividing
the segment into smaller parts , calculating the values of the respective parameters,
and then combining these by the following equations to arrive at an effective magnitude:

Equations 1-3 were combined for computer programming in the manner illus trated in Figure 2, to form a single segment model.

System Description
1)

Feed Line Simulation

The feed lines, illustrated in Figure 3 as typical, a r e subject to a wide range
of dynamic disturbances. All significant disturbances a r e expected to originate as
pressure perturbations at the tank bottom. However, the complex construction (gimbal
joints, expansion joint and bends) of the line exposes the fluids to various other dis turbances initiated by line motion. A four segment model, illustrated in Figure 4 ,
was developed to investigate the effects of these nebulous disturbances.
Propellant cavitation exists for some distance upstream of the pump. The
degree of cavitation is dependent on pump and propellant operating conditions and is
influenced by line geometry. Its effect on fluid dynamic behavior is that of a soft
complex non-linear spring. This effect is simplified for simulation by assuming the
cavitation bubbles to be localized at the pump inlet as a single bubble with constant
linear spring characteristics. This is accomplished with capacitance C4-5 shown
in Figure 4.

�Line Segment

7
Capacitance

\-- Resistance
Following Segment
Line Segment Analogy

Figure 1

!

i

Typical Line Segment

Figure 2

Single Element Simulation

Tank Sump

YimbdJoint
FmiZir:-i

-Prevalve

I

I ----------L

Expansion Joint

I

L
Figure 3

Typical Propellant Feed Line

Simulation
I
- - Pump
- - - - - - - - -J
Figure 4

Typical Feed Line Simulation

�The values used for C4-5 establish feed line resonances and correspondingly
equal propulsion system resonances. This condition is illustrated in Figure 11 for a
feed line resonant frequency of 15 cps.

2)

Engine Simulation

The H-1 rocket engine system schematic, Figure 5, illustrates the numerical
designation assigned to each liquid-mechanical segment interface and power generating
subsystem (thrust chamber, etc.) location, as well as other essential engine characteristics. The system subdivisions were modeled individually using their respective
numerical designation a s the subscriptive nomenclature for model formulation.
As illustrated, the engine propellant flow subsystem is subdivided into LOX
segments L5-6, L6-7, L8-9 and L7-10 and fuel segments F5-6, F6-7, F7-8, F8-8',
F8 ' -9 and F7 -10. These segments, with the exception of L5-6 and 5'5-6 (the LOX and
fuel turbopumps), a r e modeled using the lumped parameter technique described previously. The models a r e then combined in the manner illustrated in Figure 7 where
the inertance characteristic is represented by:

and the capacitance by:

to provide the necessary flow and pressure conditions for the combustion chambers
(thrust and gas generator) and pump descriptions.
The LOX and fuel turbopumps a r e simulated using equations derived from H-1
engine nominal steady state performance characteristic curves typically illustrated
in Figure 8 . These equations do not account for pump performance variation due to
perturbations in inlet conditions, but a r e sufficient since such variations a r e considered small as compared to the normal operating level. The equations a r e of
polynominal second order form and satisfactorily approximate the performance characteristics where pump pressure head (AP)is a function of pump flowrate @ - lb/sec)
and pump speed (&amp; - rpm) a s follows :

The shaft torque required to maintain the flow conditions of equation 8 is:

�where pump efficiencies (LOX and fuel) (Eff) vary only a small amount and are usually
assumed constant. Q is an empirical constant used to adjust the equation to any
necessary condition. Equation 8 is used to derive A P L ~ and
- ~ APF5+ and equation 9
defines T L and
~ T L .~
Combustion chamber characteristics a r e derived from chamber geometry and
combustion products in the form of characteristic exhaust gas velocity (C*) . This
term (C*) defines a relationship between pressure, flowrate and mixture ratio a s illustrated by Figure 9 and the general rocket engine relationship

in which injector end combustion pressure (PI - psi) is a function of C*, total flowrate
- lb/sec), chamber throat area (4- in2) and the gravitational constant (g - in/sec2).
Steps were taken to reduce the algebraic content of the defining relationships to a minimum for analog application. In the case of the thrust chamber at a nominal mixture
ratio of 2.33 pressure is predominantly a function of total propellant flowrate, and has
only a minute response to expected mixture ratio changes about the nominal. For
these reasons, thrust chamber steady state pressure is adequately defined by the
following linear relationship:

NT

P'g

=

f@g)

=

K67g

(11)

where K is an empirical constant and may be determined simply by

Gas generator combustion performance is a strong function of both mixture
ratio and total flowrate. The gas generator operates fuel rich in a region (MR, = .342)
well below the stoichiometric mixture ratio. As is apparent from a study of the C*
curve trend, this operating condition causes the gas generator (GG) to be exceptionally
sensitive to ratio changes. Consequently, a performance perturbation (about a
nominal) model of the GG was developed to enhance analog computer accuracy. The
resulting equations are:

6).

The subscript N designates nominal values of mixture ratio (MR) and flowrate
Subscripts L and F represent LOX and fuel, respectively, and their omission represents a combined o r total value.

Combustion delay time and chamber pressure lag time a r e simply represented

�by a pure time delay:

and a first order lag:

and a r e incorporated into equations 11 and 12 to simulate essential combustion dynamic
behavior as follows :

Values of T l and 7 a r e determined from propellant, chamber and operating
characteristics. A constant value of '7
l is used and is calculated at nominal operating
conditions a s :

where Vol is chamber volume (in3), At is the chamber exit throat area (in3) and vn is
the nominal gas exit velocity. A special study was performed to determine the value
of -y .
Turbine operating performance is a function of inlet and outlet gas characteristics and of turbopump speed. Exit gas behavior is assumed constant for dynamic
turbine operation. Turbine inlet gas characteristics, pressure, temperature, weight
flowrate and inlet gas velocity a r e defined as functions of chamber flowrate and
mixture ratio to simplify the expression for turbine torque perturbation (nTlO). These
characteristics a r e combined with turbine hardware characteristics and turbopump
speed perturbations (&amp;N6) to give :

Included in the above equation is power lost due to gearbox resistance. Turbine torque is used along with total turbopump required torque p6)to define turbopump
speed perturbations a s :

�where 110, 6 is the combined inertance property of the turbopump, gearbox and turbine,
and T6 is determined from:

Total turbopump speed is defined as:

Engine thrust is determined from the general rocket engine relationship:

Chamber throat area (Ag - in2) and thrust coefficient (CFg) a r e assumed constant.
The individual engine equations were integrated in the manner illustrated in
Figure 7, to establish the engine dynamic model.

3

Propulsion System Simulation

The three models were then combined a s shown in Figure 6 and programmed
on an analog computer to produce single engine results which a r e graphically illustrated in Figures 10 and 11, as gain (dbs) versus frequency. These results were
obtained to establish the individual effects of the LOX and fuel feed lines resonant conditions on propulsion response. This was accomplished by sinusoidally perturbing,
separately, the LOX and fuel feed line inlets while systematically varying their respective resonant frequencies.
Propulsion system total thrust (FT) is determined by the relationship

which describes inphase engine operation, a desired worse case condition.
A more detailed description of the individual equations, along with special
derivations of combustion pressure delay (T,7')and effective fluid bulk modulus
(peff) a r e presented in Chrysler Technical Report No. HSM-R181.

�Fuel (RP-1)

LOX

Figure 5. 200K H-1 Engine Schematic

,

A P ~ l

LOX
Feed
Line

{-r
PL5

WLS

APF~/

,

&gt;

H-1
Engine
Model

----

1

::ast

IB

'

___+

Typical

System
Engine

--

Figure 6 . Propulsion System Simulation

��Volumetric Flow Rate (GPM)
I

2400

.

3000

L

4000

Figure 8 . LOX Pump Developed Head Versus
Volumetric Flow Rate and Speed
*Extracted from Rocketdyne Technical Manual No. R-1352P-3

0

r
Q)

G

ic^

2.
h
.r(
c1

8
$

4

0

3

m

.r(

k

a,
+-,
0

;

&amp;

U

Mixture Ratio (MR)
1

2.0

#

2.2

I

2.4

Figure 9. Characteristic Velocity Versus Injector End
Chamber Pressure and Mixture Ratio

1

2.6

��</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20136">
                <text>spc_stnv_000062</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20137">
                <text>"Analog Simulation of Saturn S-IB Stage Propulsion System Dynamic Characteristics."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20138">
                <text>This copy has handwritten notes that change the title to read, "Analog Simulation of Uprated Saturn I Stage Propulsion System Dynamic Characteristics." The abstract notes, "The purpose of this paper is to present the techniques and logic employed in the development of an analog computer model to simulate Saturn IV first stage propulsion system dynamic characteristics.  Restraints, problem areas, and major assumptions are included."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20139">
                <text>Lehner, J. W.</text>
              </elementText>
              <elementText elementTextId="20140">
                <text>Chrysler Corporation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20141">
                <text>1966-11-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20142">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20143">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20144">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="20145">
                <text>Electric analog computers</text>
              </elementText>
              <elementText elementTextId="20146">
                <text>Analog computer simulation</text>
              </elementText>
              <elementText elementTextId="20147">
                <text>Analog computers</text>
              </elementText>
              <elementText elementTextId="20148">
                <text>Spacecraft propulsion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20149">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20150">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20151">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20152">
                <text>Box 19, Folder 29</text>
              </elementText>
              <elementText elementTextId="205813">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20154">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20155">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20156">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1147" public="1" featured="0">
    <fileContainer>
      <file fileId="994">
        <src>https://digitalprojects.uah.edu/files/original/20/1147/spc_stnv_000063.pdf</src>
        <authentication>4f6b05a7994bd629cc076c96c8443e3d</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177281">
                    <text>SATURY UlSTORY DOCUMENT
University of Alabama Research Institute
Histofy OF Science &amp; Techrloloyy Group

--

Date - - - - - . - - - - DOC NO. - - -"ANALYSIS AND PROJECTIONS O F S P A C E VEHICLE
AUTOMATIC CHECKOUT ANC L 4UNCH"

by
C. R. Vedane
T e c h n i c a l S y s t e m s Office
G e o r g e C. M a r s h a l l Space Flight C e n t e r
Huntsville. 41a b a m a

-I

b
1

INTRODUCTION
At t h e t i m e t h e d e c i s i o n w a s m a d e t o apply a u t o m a t i c techniques t o
t h e p r o c e s s of checking out and launching a S a t u r n v e h i c l e , t h e t o t a l
o p e r a t i o n w a s u n d e r m a n u a l c o n t r o l . C o n s i d e r a b l e a d v a n c e s have been
m a d e i n t h e t r a n s i t i o n f r o m m a n u a l t o c o m p u t e r c o n t r o l . The purpose
of t h i s p a p e r i s t o p r e s e n t a projection of the i m p r o v e m e n t s t h a t m u s t
be m a d e b e f o r e m a x i m u m benefits c a n be obtained f r o m t h e a u t o m a t i o n
e f f o r t . A brief d e s c r i p t i o n i s given of t y p i c a l checkout o p e r a t i o n s and
of t h e evolution of h a r d w a r e . With t h i s a s background, a n a n a l y s i s i s
m a d e of t h e i m p l e m e n t a t i o n p r o b l e m s e x p e r i e n c e d in a u t o m a t i o n ; and
f i n a l l y , f r o m t h i s a n a l y s i s p r o j e c t i o n s a r e d e r i v e d and s t a t e d .
CHECKOUT OPER 4TIONS
As s t a t e d above, t h i s s e c t i o n p r e s e n t s a brief d e s c r i p t i o n of t h e
t e s t i n g o p e r a t i o n . No a t t e m p t i s m a d e t o d e s c r i b e a l l of the i n t r i c a c i e s
of t h e t a s k s i n c e t h i s i s not t h e t h e m e of t h e p a p e r . The p u r p o s e i s t o
e x p o s e t h e r e a d e r t o the p a r a m e t e r s which m u s t be c o n t r o l l e d and
m o n i t o r e d , plus provide a g e n e r a l u n d e r s t a n d i n g of t h e n a t u r e of t h e
o p e r a t i o n . T h i s i s n e c e s s a r y f o r the r e a d e r t o u n d e r s t a n d t h e h a r d w a r e r e q u i r e m e n t s and s u b s e q u e n t a n a l y s i s s e c t i o n .
F i g u r e 1 i s u s e d t o a i d t h e a c c o m p l i s h m e n t of t h i s objective. It
d o e s not r e p r e s e n t a n y s p e c i f i c t e s t p r o g r a m ( s u c h a s post-manufacturing
c h e c k o u t , s t a t i c f i r i n g , e t c . ) but p r e s e n t s the g e n e r a l s t r u c t u r e of a l l
t e s t o p e r a t i o n s . P r e s e n t e d a r e t h e v a r i o u s s y s t e m s t e s t s which a r e
gene r a l l y p e r f o r m e d c o n c u r r e n t l y , followed by t y p i c a l combined s y s t e m s
tests.
T h e following d i s c u s s i o n w i l l d e s c r i b e t h e t y p e s of s i g n a l s involved a n d g r o s s l y t h e i r a r r a n g e m e n t .

�T h e n e t w o r k s a r e u s u a l l y defined a s t h e c i r c u i t r y w h i c h c o n t r o l s ,
m o n i t o r s , a n d s u p p l i e s power t o t h e v a r i o u s black boxes u s e d i n t h e
vehicle. In performing control functions, this c i r c u i t r y usually applies
o r r e m o v e s d . c . v o l t a g e t o o r f r o m t h o s e b l a c k boxes a c c o r d i n g t o
p a r t i c u l a r s e q u e n c e a n d / o r s e t of l o g i c . In doing s o , i t a c c o m p l i s h e s
s u c h o p e r a t i o n s a s ; s t a r t , cutoff a n d s a f i n g , m a l f u n c t i o n d e t e c t i o n ,
s e p a r a t i o n , d e s t r u c t , e t c . T h e m o n i t o r i n g f u n c t i o n c o n s i s t s of providing
high r e s o l u t i o n , r e l i a b l e , r e a l - t i m e i n f o r m a t i o n t o t h e g r o u n d s y s t e m s
and personnel. This information, a s with the control functions, i s u s u a l l y i n t h e f o r m of 2 8 v o l t s i g n a l s w h i c h a r e n e i t h e r on o r off. E a c h
of t h e c i r c u i t s m u s t be v e r i f i e d t o i n s u r e t h a t e a c h c o m p o n e n t w i l l p e r f o r m i t s intended function without interfering with other c i r c u i t s .
D u r i n g t h e t e s t s of t h e o t h e r s y s t e m s , d i f f e r e n t t y p e s of s i g n a l s
a r c e n c o u n t e r e d . T h e g u i d a n c e a n d c o n t r o l c h e c k s r e q u i r e being a b l e
to apply simulated e r r o r signals to the stabilized nlatform, r a t e gyros,
c o n t r o l a c c e l e r o m e t e r s a n d o t h e r e r r o r s e n s i n g d e v i c e s . The r e s p o n s e
f r o m these devices m u s t b e m e a s u r e d simultaneously with the application
of t h e s t i m u l i t o c h e c k t h e c a l i b r a t i o n . In m o s t c a s e s t h e s e s i g n a l s a r e
a n a l o g , c o n s i s t i n g of v a r i o u s v o l t a g e s a n d f r e q u e n c i e s ; c o m m u n i c a t i o n
w i t h t h e c o m p u t e r i s v i a a d i g i t a l l i n k , r e p r e s e n t i n g a n o t h e r t y p e of
s i g n a l . In i t s v e r i f i c a t i o n v a r i o u s d i a g n o s t i c r o u t i n e s m u s t be p e r f o r m e d , plus v e r i f y i n g t h e i n t e r f a c i n g of t h i s e q u i p m e n t w i t h t h e o t h e r
f u n c t i o n a l e l e m e n t s of t h e g u i d a n c e a n d c o n t r o l s y s t e m s . T h i s r e q u i r e s
the capability to handle, i n s o m e c a s e s , the s a m e analog p a r a m e t e r s
a s previously mentioned and i n other c a s e s , d i s c r e t e signals which
o p e r a t e v a r i o u s c o m p o n e n t s on t h e v e h i c l e v i a t h e s w i t c h s e l e c t o r .
T e s t i n g of t h e i n s t r u m e n t a t i o n a n d R F ( r a d i o f r e q u e n c y ) s y s t e m s
r e p r e s e n t s t i l l a n o t h e r t y p e of o p e r a t i o n . V e r i f i c a t i o n of t h e TM ( t e l e m e n t r y ) p a c k a g e s r e q u i r e s o s c i l l a t o r a d j u s t m e n t , p o w e r output c h e c k s ,
etc. ; and the R F packages requires frequency interrogation, 4GC checks
plus VSWR on a l l a n t e n n a e . As f a r a s t h e p a r a m e t e r s a r e c o n c e r n e d
on t h e input t o t h e T M p a c k a g e , t h e y a r e not a n y d i f f e r e n t (with t h e e x c e p t i o n of v i b r a t i o n m e a s u r e m e n t s ) i n t y p e t h a n e n c o u n t e r e d i n t h e o t h e r
s y s t e m s . The differences a r e in the acquisition and processing methods
T h e p r i m a r y function of t h e i n s t r u m e n t a t i o n s y s t e m i s t o m o n i t o r t h e
p e r f o r m a n c e of t h e o t h e r s y s t e m s . T h e r e f o r e , t h e v e r i f i c a t i o n m u s t
be a c c o m p l i s h e d d u r i n g t h e t e s t i n g of t h e s e s y s t e m s . C o n s e q u e n t l y ,
a highly i n t e g r a t e d a n d c o o r d i n a t e d o p e r a t i o n i s n e c e s s a r y .

�Testing the mechanical s y s t e m s requires the capability t o control
D r e s s u r e t o the v a r i o u s pneumatic and propellant s y s t e m s , verify
e n g i n e s , both m e c h a n i c a l l y a n d e l e c t r i c a l l y , e t c . The p a r a m e t e r s i n volved i n s u c h a n o p e r a t i o n r u n t h e g a m u t . An a d d i t i o n a l a t t r i b u t e of
t h i s o p e r a t i o n i s s a f e t y , t h u s r e q u i r i n g continuous m o n i t o r i n g of c e r t a i n
parameters.
In t h e c o m b i n e d s y s t e m s t e s t s , t h e o p e r a t i o n c h a n g e s f r o m p a r a l l e l
t o s e r i e s . With e x c e p t i o n of a c t u a l l y loading p r o p e l l a n t s , no new p a r a m e t e r s a r e i n v o l v e d ; h o w e v e r , t h e whole n a t u r e of t h e o p e r a t i o n c h a n g e s .
The specific s y s t e m s t e s t s have the p r i m a r y objective t o verify the int e r n a l f u n c t i o n s of e a c h s y s t e m . The p r i m a r y o b j e c t i v e of t h e c o m b i n e d
s y s t e m s t e s t s i s t o a s s u r e t h a t t h e r e a r e no i n t e r f a c i n g p r o b l e m s a m o n g
t h e s y s t e m s . E a c h of t h e c o m b i n e d s y s t e m s t e s t s h a s d i f f e r e n t o b j e c t i v e s , but t h e c o m m o n a s p e c t i s t h a t a l l of t h e s y s t e m s a r e o p e r a t i n g i n
a n itt egrated fashion. This requires that the total operational sequence
be p r e - p l a n n e d a n d t h a t e a c h s y s t e m e n g i n e e r h a v e t h e c a p a b i l i t y t o
know t h e p e r f o r m a n c e of h i s s y s t e m .
MANUAL HARDW ARE REQUIRED
T u r n i n g t o t h e GSE r e q u i r e d t o p e r f o r m t h e m a n u a l t e s t i n g o p e r a t i o n ,
F i g u r e 2 r e p r e s e n t s a typical testing complex. The figure depicts the w a y i n w h i c h t h e G S E i s o r g a n i z e d , by s y s t e m s , a n d t h e v a r i o u s t y p e s
of s i g n a l s d e s c r i b e d p r e v i o u s l y . I n g e n e r a l , t h e f i g u r e i s p r e t t y s e l f e x p l a n a t o r y . E a c h t e s t e n g i n e e r c o n t r o l s h i s s y s t e m v i a p a n e l s equipped
with switches f o r s t i m u l i a n d m e t e r s and lights for r e s p o n s e monitoring.
H o w e v e r , t h e o p e r a t i o n involving t h e i n s t r u m e n t a t i o n s y s t e m m a y r e .
q u i r e e l a b o r a t i o n . T o i n s u r e t h e c a l i b r a t i o n of t h e m e a s u r e m e n t s , i t i s
f i r s t n e c e s s a r y t o c h e c k f r o m t h e t r a n s d u c e r t h r o u g h t h e s i g n a l conditioni n g , w h i c h i s a c c o m p l i s h e d by obtaining a h a r d w i r e r e c o r d i n g . T h e
m e a s u r e m e n t i s then switched to the telemetry s y s t e m and a recording
i s o b t a i n e d v i a R F link. T h e s e r e c o r d i n g s a r e t h e n c o m p a r e d t o i n s u r e
a c c u r a c i e s of t h e T M s y s t e m .
l
T h e a n i m a t i o n p o r t i o n of t h e f i g u r e d e p i c t s how t h e t e s t i n g o p e r a t i o n
i s coordinated and conducted. E a c h s y s t e m engineer i s responsible for
h i s s y s t e m s w i t h t h e t o t a l o p e r a t i o n being d i r e c t e d by a t e s t c o n d u c t o r .
REASONS F O R AUTOMATION
It m i g h t s e e m a p p r o p r i a t e a n d helpful a t t h i s point t o a s k t h e q u e s t i o n
"If t h e h a r d w a r e n e c e s s a r y t o a c c o m p l i s h t h e job i s a v a i l a b l e , why

�develop complex digital equipment t o automate the proces s t ' ? The
basic r e a s o n s a r e found in the design concept and m i s s i o n r e q u i r e m e n t s
of the S a t u r n v e h i c l e s . F r o m the d e s i g n viewpoint, the concept is a
staging a p p r o a c h with e a c h s t a g e being developed a t a different location
i n t h e United S t a t e s . F r o m a m i s s i o n viewpoint the s a m e basic vehicle
m u s t be a b l e t o a c c o m p l i s h varying m i s s i o n s with v a r y i n g launch r a t e s .
T o provide the capability t o i n t e g r a t e t h e s e s t a g e s into a launch vehicle
a t t h e launch s i t e and provide the n e c e s s a r y m i s s i o n flexibility a n onboard c o m p u t e r s e e m e d t o be the a n s w e r .
In addition, the data r e q u i r e m e n t s t o v e r i f y a s t a g e w e r e becoming
quite voluminous. T h e r e a r e two c o n s i d e r a t i o n s to this point. F i r s t ,
i s t k d a t a n e c e s s a r y on a r e a l - t i m e b a s i s during the t e s t i n g operation.
Second, i s the d a t a that needs t o be analyzed, but t h i s a n a l y s i s c a n be
p e r f o r m e d a f t e r the t e s t i s completed. F i g u r e 2 shows the t e s t engineeF
a s t h e m e a n s of accomplishing the data a n a l y s i s i n a r e a l - t i m e situation
As t h e s y s t e m s become l a r g e r and m o r e complex, m o r e people a r e
involved. This i n c r e a s e s the complexity of the coordination n e c e s s a r y
t o a c c o m p l i s h the t e s t i n g operation. 4 c o m p u t e r has the capability to
monitor a l l of t h e data points, c o m p a r e the a c c u r a c i e s , i s s u e subs e q u e n t c o m m a n d s , a n d c o o r d i n a t e t h e p e r f o r m a n c e of l a r g e t e s t s
than the e n g i n e e r s involved. S i m i l a r l y , t h e magnitude of the off-line
data a n a l y s i s t a s k i n c r e a s e d , which a c o m p u t e r c a n p e r f o r m much
faster.
In the data gathering and p r o c e s s i n g , t h e r e a r e s o m e r e a l advantag e s t o be gained f r o m automation concerning a c c u r a c y and repeatibility.
If a t e s t p r o c e d u r e i s c o n v e r t e d t o a n a u t o m a t i c p r o g r a m , t h i s t e s t
will be p e r f o r m e d i n t h e s a m e m a n n e r e a c h t i m e i t i s run. Consequently,
the d a t a d e s c r i b i n g the p e r f o r m a n c e of the s y s t e m should be r e p e a t a b l e .
4 1 ~ 0 ,i t was planned that the s a m e t e s t p r o g r a m could be p e r f o r m e d a t
d i f f e r e n t t e s t l o c a t i o n s , s u c h a s t h e f a c t o r y checkout and s t a t i c t e s t
l o c a t i o n s . However, t h i s objective has not m a t e r i a l i z e d t o the d e g r e e
initially planned. This l a r g e l y i s a r e s u l t of GSE and s t a g e configuration
differences.
Another advantage i s t h a t a higher d e g r e e of a c c u r a c y i s obtained
through g r e a t e r s e n s i t i v i t y of the m e a s u r i n g d e v i c e s . This i s evidenced
i n m e a s u r i n g analog p a r a m e t e r s and i n timing the bi-level s i g n a l s .
4nother advantage of significance i s the s h o r t t i m e r e q u i r e d to
p e r f o r m a t e s t provided no a n o m a l i e s o c c u r r e d . This has p a r t i c u l a r
payoffs by being a b l e t o p e r f o r m l a t e c h e c k s of a s y s t e m p r i o r t o
s t a t i c f i r i n g o r a n a c t u a l launch.
4

�AUTOMATION HARDWARE CCPJCEPT
T h e p o s t - m a n u f a c t u r i n g c h e c k o u t of a S a t u r n s t a g e p r o v i d e d t h e
f i r s t a p p l i c a t i o n of a u t o m a t i c t e c h n i q u e s a n d a r e s t i l l i n u s e . I n h e r e n t
in the application w e r e s o m e c o n s t r a i n t s which proved t o have f a r - r e a c h ing i m p a c t s . C o n s o l i d a t e d a n d r e d u c e d t o t h e b a s i c e l e m e n t s , t h e s e
c o n s t r a i n t s w e r e : ( 1 ) no s c h e d u l e i m p a c t t o t h e p r o g r a m , a n d ( 2 ) no
l a r g e r e d e s i g n e f f o r t t o t h e s t a g e a n d GSE. T h e f i r s t c o n s t r a i n t m e a n t
t h a t t h e a d a p t i o n of a u t o m a t i c e q u i p m e n t t o t h e m a n u a l e q u i p m e n t would
b c a c c o m p l i s h e d on a n o - i n t e r f e r e n c e b a s i s . T h e s e c o n d c o n s t r a i n t
m e a n t t h a t t h e a u t o m a t i c e q u i p m e n t a n d t e c h n i q u e s would be d e s i g n e d t o
i n t e r f a c e w i t h t h e GSE a n d not w i t h t h e v e h i c l e s y s t e m s .
F i g u r e 3 d e m o n s t r a t e s t h i s point a n d i s u s e d t o p o r t r a y t h e s y s t e m
w h i c h h a s b e e n i m p l e m e n t e d . I t c o n s i s t s of a t h r e e g e n e r a l p u r p o s e
c o m p u t e r complex with r e m o t e satellite t e s t stations. 4 p r i m a r y a s s e t
of t h i s s y s t e m i s i t s f l e x i b i l i t y p r o v i d e d t h r o u g h t h e u s e of t h r e e individ u a l c o m p u t e r s . T h e c o n s t r a i n t s of no p r o g r a m i m p a c t m a g n i f i e d t h e
i m p o r t a n c e of t h i s f l e x i b i l i t y . It a l l o w e d one c o m p u t e r t o be v e r i f y i n g
t h e i n t e r f a c e w i t h t h e p e r i p h e r y e q u i p m e n t a n d developing u t i l i t y p r o g r a m s w h i l e t h e o t h e r two c o m p u t e r s c o u l d be v e r i f y i n g t h e t e s t s t a t i o n
i n t e r f a c e s and developing t e s t p r o g r a m s .
A f t e r t h e v e r i f i c a t i o n of t h e a u t o m a t i o n s y s t e m a n d d u r i n g t h e s t a g e
t e s t i n g o p e r a t i o n s , a l l of t h e c o m p u t e r s w e r e u s e d s i m u l t a n e o u s l y only
d u r i n g t h e o v e r a l l s y s t e m s t e s t s . C o n s e q u e n t l y , a t l e a s t one c o m p u t e r
w a s a v a i l a b l e f o r debugging p r o g r a m s t o be u s e d i n f u t u r e t e s t s .
E a c h t e s t s t a t i o n w a s g i v e n t h e c a p a b i l i t y t o a c c e p t a n d output
d i s c r e t e a n d a n a l o g s i g n a l s . T h e d e g r e e of c a p a b i l i t y f o r e a c h type
d e p e n d e d upon t h e s t a g e s y s t e m f o r w h i c h t h e s t a t i o n w a s d e s i g n e d .
Man-machine interfacing with e a c h t e s t station w a s provided through
a f l e x o - w r i t e r . T h i s a l l o w e d t h e t e s t e n g i n e e r t o o p e r a t e a l l of t h e
i n p u t / o u t p u t c a p a b i l i t y of t h e t e s t s t a t i o n m a n u a l l y . I n a d d i t i o n , t h e
e x e c u t i v e p r o g r a m w a s d e s i g n e d t o allow h i m t o c a l l u p p r o g r a m s f r o m
t h e c e n t r a l c o m p u t e r c o m p l e x . O n c e a p r o g r a m w a s o n - l i n e , i t could
be s i n g l e s t e p p e d o r r u n c o m p l e t e l y a u t o m a t i c . C o m m u n i c a t i o n between the central computer complex and the t e s t stations was via a
distribution m a t r i x which allowed any c o m p u t e r t o work with any t e s t
station.

�As r e f e r e n c e d p r e v i o u s l y , t h e a m o u n t of d a t a w h i c h w a s n e c e s s a r y
t o r e c o r d a n d a n a l y z e w a s g e t t i n g unwieldly. T o be a b l e t o handle t h e
d i s c r e t e b i - l e v e l t y p e s i g n a l s , a CEE ( d i g i t a l e v e n t s e v a l u a t o r ) w a s
developed.
T h i s d e v i c e h a s t h e c a p a b i l i t y t o a c c e p t a c h a n g e of s t a g e ,
r e c o r d t h e t i m e a n d i d e n t i f i c a t i o n a n d output a r e c o r d on t a p e o r p r i n t e r .
C a p a b i l i t y i s p r o v i d e d by s o f t w a r e f o r r e a l - t i m e o r off-line e v a l u a t i o n .
As c a n be o b s e r v e d by c o m p a r i n g F i g u r e s 2 a n d 3 , s o m e m o d i f i c a t i o n s w e r e m a d e t o t h e GSE t o a l l o w c o n t r o l a n d m o n i t o r i n g of t h e
s t a g e s y s t e m s . B e c a u s e of t h e c o n s t r a i n t of no l a r g e r e d e s i g n e f f o r t ,
t h e m o d i f i c a t i o n s w e r e e n g i n e e r e d u s i n g t h e g u i d e l i n e s of providing
a c c e s s t o the existing m a n u a l control and monitoring functions. In
the e l e c t r i c a l a r e a s , this w a s relatively e a s y since the s t a g e s have
a l w a y s b e e n c o n t r o l l e d a n d m o n i t o r e d by r e m o t e t e c h n i q u e s . T h e r e f o r e , i n t h e g e n e r a l c a s e , i t w a s a m a t t e r of " t e e i n g " t h e s e f u n c t i o n s
i n a blockhouse d i s t r i b u t o r a n d c o n n e c t i n g t h e m t o t h e a p p r o p r i a t e
t e s t station.
A u t o m a t i o n of t h e i n s t r u m e n t a t i o n s y s t e m t e s t i n g o p e r a t i o n r e q u i r e d
a s o m e w h a t d i f f e r e n t a p p r o a c h . I n F i g u r e 3 , t h e p r o b l e m of gaining
a c c e s s t o r e c o r d t h e m e a s u r e m e n t s b e t w e e n t h e s i g n a l conditioning and
t h e T M p a c k a g e w a s a m a t t e r of "teeing" t h e m e a s u r e m e n t a n d c o n n e c t ing t o the r e c o r d e r and Instrumentation T e s t Station. However, t o
a c c o m p l i s h t h e c o m p a r i n g of h a r d w i r e r e c o r d i n g w i t h t h e T M r e c o r d
r e q u i r e d digitizing the information the T M ground station received.
T h i s w a s a c c o m p l i s h e d by d e s i g n i n g e q u i p m e n t t o a c c e p t t h e TM s i g n a l s
a t t h e d i s c r i m e n a t o r s and d e c o m m u t a t o r s , digitize t h e s e m e a s u r e m e n t s
and i n t e r f a c e t h e m with the Instrumentation T e s t Station. P r o g r a m s
w e r e p r o v i d e d t o do t h e c o m p a r i s o n a n d p r i n t t h e r e s u l t s on t h e f l e x o writer.
About t h i s t i m e , a n o t h e r m e t h o d of a c c o m p l i s h i n g t h e s a m e t e c h n i q u e s u s i n g o n - b o a r d e q u i p m e n t w a s being d e v e l o p e d . T h i s m e t h o d
h a s c o m e t o be known a s DDAS ( D i g i t a l Data A c q u i s i t i o n S y s t e m ) a n d
h a s r e p l a c e d t h e e a r l i e r t e c h n i q u e i n m o s t c a s e s . T h e a d v a n t a g e s of
converting the m e a s u r e m e n t s t o digital f o r m on the s t a g e i s the reducti o n of n o i s e p r o b l e m s a n d l e s s g r o u n d e q u i p m e n t i s r e q u i r e d . L e s s
s u s c e p t i b i l i t y t o n o i s e i s a c h i e v e d by having l e s s w i r e l e n g t h b e t w e e n
t h e m e a s u r e m e n t a n d t h e A / D c o n v e r t e r (analog t o d i g i t a l ) . L e s s
e q u i p m e n t i s a c h i e v e d by e l i m i n a t i n g a n d / o r r e d u c i n g t h e need f o r g r o u n d
recorders.

�F i g u r e 3 does not depict one piece of equipment used in the e a r l y
phases of automating i n s t r u m e n t a t i o n checkout. This w a s a p r e s s u r e
balance s y s t e m u s e d t o a p p l y a known p r e s s u r e s t i m u l i t o the p r e s s u r e
t r a n s d u c e r , thus providing a b a s i s f o r c o m p a r i n g t h e r e c o r d i n g taken
a t t h e s i g n a l conditioner output. I n c r e a s e d quality and reliability of
t h e t r a n s d u c e r and the implementation of t h e R 4CS (Remote Automatic
C a l i b r a t i o n S y s t e m ) h a s deleted t h e n e c e s s i t y for t h i s technique. The
RACS provide f o r a two-point c a l i b r a t i o n check of the a m p l i f i e r by
being a b l e t o apply a known signal a t the high and low end of a n a m p l i f i e r
r a n g e . The t r a n s d u c e r provides a t h i r d point by m e a s u r i n g the a m b i e n t
conditions of t h e s y s t e m which i t i s monitoring.
In t h e m e c h a n i c a l s y s t e m s , much m o r e modification w a s n e c e s s a r y
t o obtain c o m p l e t e r e m o t e a u t o m a t i c control. As mentioned previously,
the m e c h a n i c a l checkout o p e r a t i o n w a s neither r e m o t e l y o r automatically
c o n t r o l l e d . G e n e r a l l y , p r e s s u r e s w e r e s e t up by using hand valves and
hand l o a d e r s and w e r e m o n i t o r e d by a l o c a l gauge. To achieve r e m o t e
c o n t r o l r e q u i r e d t h e addition of solenoid o r m o t o r d r i v e n l o a d e r s f o r
venting loading p r e s s u r e s f o r shut-down, t r a n s d u c e r s t o provide r e a d i n g s
a t r e m o t e locations and s o m e s e l f - d i a g n o s t i c capability i n c a s e of
a b n o r m a l conditions.
Space will not p e r m i t t h e d e s c r i p t i o n of the a u t o m a t i c s y s t e m s
t h a t a r e now u s e d i n the S a t u r n I B and S a t u r n V P r o g r a m s . The s y s t e m s now u s e d , with one exception, employ a single c o m p u t e r r a t h e r
t h a n a m u l t i - c o m p u t e r a s the c e n t r a l c o m p u t e r complex. In one p a r t i c u l a r application of t h e c e n t r a l c o m p u t e r complex s y s t e m a l l of t h e
input/output capability i n c o r p o r a t e d i n the t e s t s t a t i o n h a s been integrated.
IMPLEMENTATION ANALYSIS
So f a r , this paper has been devoted t o a d e s c r i p t i o n of the testing
o p e r a t i o n , the h a r d w a r e and h a r d w a r e changes n e c e s s a r y t o convert t h i s
o p e r a t i o n f r o m m a n u a l t o automatic. The next phase will p r e s e n t a n
a n a l y s i s of t h e p r o b l e m s e n c o u n t e r e d during t h e implementation phase.
T h e s e p r o b l e m s c a n be grouped into t h r e e c a t e g o r i e s :
(1)
(2)
(3)

Hardware
Software
People

�T h e r e a d e r w i l l note i m m e d i a t e l y t h a t t h e s e a r e v e r y g e n e r a l c a t e g o r i e s ; t h e r e f o r e , the s p e c i f i c s within m u s t be f r a m e d .
Hardware
In t h e h a r d w a r e c a t e g o r y , i n c o m p a t i b i l i t y p r o b l e m s w e r e e n c o u n t e r e d within t h e a u t o m a t i o n e q u i p m e n t i t s e l f ; t h e r e w e r e i n c o m patibility p r o b l e m s e n c o u n t e r e d w i t h t h e s i g n a l functions which the
e q u i p m e n t w a s d e s i g n e d t o handle. T h e r e w e r e o t h e r p r o b l e m s conc e r n i n g t h e c a p a b i l i t y of the e q u i p m e n t t o m a n a g e t h e o p e r a t i o n a l
r e q u i r e m e n t s . T h e s o l u t i o n t o t h e s e p r o b l e m s h a s brought a b o u t a
c o n s i d e r a b l : a m o u n t of a d v a n c e s i n h a r d w a r e d e s i g n and t e c h n i q u e s .
T h e r e i s a b a s i c s y s t e m p r o b l e m t h a t b e c o m e s evident a f t e r the
automation equipment i s interfaced and i s performing a testing o p e r ation. This problem was alluded t o in the discussion concerning the
c o n s t r a i n t s i m p o s e d i n t h e i n i t i a l a p p l i c a t i o n of a u t o m a t i c t e c h n i q u e s .
It w a s pointed out t h a t t h e r e w a s t o be no m a j o r r e d e s i g n e f f o r t of the
v e h i c l e . T h i s r e s u l t e d i n t h e a u t o m a t i o n e q u i p m e n t being i n t e r f a c e d
w i t h t h e GSE r a t h e r t h a n t h e s t a g e s y s t e m s . H e r e i n l i e s t h e s y s t e m
p r o b l e m . T h e e f f e c t being not a r e d u c t i o n of g r o u n d s u p p o r t equipm e n t ; but i n s t e a d a n a d d i t i o n of a u t o m a t i o n e q u i p m e n t t o p e r f o r m the
c o m m u n i c a t i o n a n d i n t e g r a t i o n t a s k t h a t the m a n w a s doing.
With t h e c o n c e p t of i n t e r f a c i n g t h e 110 (input-output) of t h e c o m p u t e r
t o t h e GSE, t h e GSE i s c o n s i d e r e d t o be t h e d e c i s i o n making d e v i c e .
T h e c o m p u t e r i s c o n s i d e r e d only a m e a n s of c o m m u n i c a t i n g the s t a t u s
of t h e GSE a n d v e h i c l e t o t h e e n g i n e e r s . T h i s c o n c e p t f a i l s t o u s e one
of t h e s t r o n g a s s e t s of t h e c o m p u t e r ; t h i s i s i t s c a p a b i l i t y t o g a t h e r
d a t a a n d m a k e s u b s e q u e n t d e c i s i o n s . A continuance of t h i s philosophy
w i l l i n c r e a s e t h e s i z e a n d c o m p l e x i t y of t h e h a r d w a r e and s o f t w a r e
system.
Another way of d e s c r i b i n g t h e s a m e p r o b l e m i s by taking a r a t h e r
a n t h r o p o m o r p h i c view of t h e v e h i c l e a n d GSE. T h e method of c o m m u n i c a t i o n of a c o m p u t e r i s a d i g i t a l language. With the e x c e p t i o n of t h e
o n - b o a r d c o m p u t e r s a n d t h e DDAS (which c o n c e r n s only r e s p o n s e s ) t h e
v e h i c l e u n d e r s t a n d s only d i s c r e t e a n d a n a l o g language. T h e r e f o r e , t h e
m a j o r p u r p o s e of t h e e l e c t r i c a l GSE i s t o be a n i n t e r p r e t e r between t h e
c o m p u t e r a n d the v e h i c l e . I t b e c o m e s a p p a r e n t t h e n t h a t s t e p s need t o
be t a k e n t o g e t t h e v e h i c l e t o c o m m u n i c a t e i n a language m o r e c l o s e l y
a l i g n e d w i t h t h e c o m p u t e r language. T h e two e x c e p t i o n s r e f e r r e d t o

�above r e p r e s e n t s t e p s i n this d i r e c t i o n s i n c e both communicate via
digital links. By expanding t h e i r u s e provides the key f o r a c c o m p l i s h ing the additional s t e p s n e c e s s a r y . The w r i t e r w i s h e s t o make v e r y
e x p l i c i t , a t t h i s point, that the above logic i s u s e d t o e s t a b l i s h a longr a n g e goal. T h e r e a r e many i n c r e m e n t a l s t e p s n e c e s s a r y before that
goal c a n be r e a c h e d . Also, t h e r e a r e many t r a d e - o f f s concerning
complexity which m u s t be m a d e between the vehicle and t h e ground
equipment. T o r e a c h this goal, t h e following actions need t o be taken:
(1) I n c r e a s e d r e l i a n c e on DDAS.
r e l i a b i l i t y and handling techniques .

This will r e q u i r e i m p r o v e d

(2) R e a s s e s s t h e balance of complexity between the vehicle
and GSE. In o r d e r t o achieve l a r g e reductions of e l e c t r i c a l GSE, i t
would be profitable t o allow m o r e complexity on-board the vehicle.
( 3 ) E l i m i n a t e the need f o r t o t a l checkout capability a t the
launch o p e r a t i o n s . T h i s c a n be achieved by delivering t o the launch
o p e r a t i o n s totally configured and v e r i f i e d s t a g e s .
(4) Review the interlocking r e q u i r e m e n t s , using t h e guiclel i n e of allowing t h e c o m p u t e r t o m a k e t h e decision.

(5) Develop m e a n s of controlling vehicle s y s t e m s through the
u s e of o n - b o a r d techniques a n d / o r expanded u s e of p r e s e n t c a p a b i l i t i e s .
By being a b l e t o c o n t r o l t h e vehicles through u s e of on-board s y s t e m s ,
a r e d u c t i o n i n t h e i n t e r f a c e points between the vehicle and GSE i s gained.
If the n u m b e r of the i n t e r f a c e points i s r e d u c e d , two i m p a c t s a r e a
consequence. F i r s t , t h e r e i s a g e n e r a l reduction of GSE, s i m p l y bec a u s e t h e r e a r e l e s s functions t o be handled. Second, t h e r e i s l e s s
possibility of a change i n the vehicle causing a subsequent change i n
t h e GSE. An e x a m p l e of this i s i n the way the DDAS p e r f o r m s . S e v e r a l
hundred m e a s u r e m e n t s m a y input t o the DDAS, but the output i s a single
wave t r a i n . T h e r e f o r e , many m e a s u r e m e n t changes c a n be m a d e with
the only e f f e c t t o t h e GSE being a change t o the m e a s u r e m e n t a d d r e s s
in the CDAS wave t r a i n . This type of change c a n be accepted by a
change in the s o f t w a r e .
Software
Providing a s o f t w a r e s y s t e m to i m p l e m e n t the automation of thc,
checkout and launch o p e r a t i o n s h a s been and continues to be one of the
m o s t challenging a s p e c t s of the automation endeavor.

�T h e d i s c u s s i o n c o n c e r n i n g t h e n a t u r e of t h e t e s t i n g o p e r a t i o n
pointed out t h e v a r i e t y of s i g n a l s involved a n d t h e d i f f e r e n t t y p e s of
t e s t s c o n d u c t e d . T o c r e a t e a s o f t w a r e s y s t e m t o m a n a g e t h i s t y p e of
o p e r a t i o n r e q u i r e s a t r e m e n d o u s a m o u n t of c a p a b i l i t y a n d f l e x i b i l i t y .
I n doing a n a n a l y s i s of t h e d i f f i c u l t i e s t h a t w e r e e n c o u n t e r e d , e a c h
s e e m e d t o be r o o t e d t o a v e r y b a s i c a n d f u n d a m e n t a l point; t h a t of being
a b l e t o d e s c r i b e a l l of t h e r e q u i r e m e n t s of t h e job. Of c o u r s e , t h i s i s
a n e s s e n t i a l i n g r e d i e n t i n a n y t a s k . But, i t r e a f f i r m s t h e point t h a t t h e
b e s t s p e n t t i m e i n a n y new e n d e a v o r i s t h a t s p e n t i n d e s c r i b i n g t h e t a s k
a n d planning i t s i m p l e m e n t a t i o n .
T h e p r o b l e m s t h e t e s t e n g i n e e r e n c o u n t e r e d i n providing s y s t e m s
t e s t r e q u i r e m e n t s t o t h e p r o g r a m m e r w e r e d i r e c t m a n i f e s t a t i o n s of t h e
a b o v e point. P r i o r t o a u t o m a t i o n , t h e e n g i n e e r h a d n e v e r b e e n r e q u i r e d
t o d e s c r i b e i n h i s t e s t p r o c e d u r e s a l l of t h e s t e p s , w i t h t h e e x p e c t e d
r e s p o n s e s a n d l i m i t s , t o t h e d e t a i l r e q u i r e d by a c o m p u t e r p r o g r a m .
O t h e r d i f f i c u l t i e s w e r e e n c o u n t e r e d i n d e t e r m i n i n g t h e a m o u n t of
c a p a b i l i t y and f l e x i b i l i t y r e q u i r e d i n t h e e x e c u t i v e p r o g r a m . I n o r d e r
t o d e v e l o p a n e x e c u t i v e p r o g r a m , d e c i s i o n s h a v e t o be m a d e c o n c e r n ing m a n - m a c h i n e r e l a t i o n s h i p s , o n - l i n e o r off-line c o m p i l a t i o n , m e m o r y
c a p a b i l i t y a n d i n p u t / o u t p u t r e q u i r e m e n t s t o n a m e a few. T h e s e d e c i s i o n s
m u s t be m a d e a s e a r l y a s p o s s i b l e s i n c e c h a n g e s t o t h e s e i t e m s w i l l
cause m a j o r impact to the executive p r o g r a m development.
The language the t e s t engineer should u s e i n writing the t e s t i s
p r o b a b l y t h e m o s t c o m p l e x a n d c o n t r o v e r s i a l i s s u e . P a r t of t h e
d i f f e r e n c e of opinion i s a r e s u l t of t h e t y p e of s y s t e m being a u t o m a t e d .
F o r example, to monitor the instrumentation s y s t e m m a y require a
p r o g r a m t o c o n t i n u o u s l y s c a n a g r o u p of m e a s u r e m e n t s . T h i s r e q u i r e s
a c o m p l e t e l y d i f f e r e n t t y p e of p r o g r a m t h a n one t o c h e c k o u t t h e cutoff
circuitry.
The f o r m e r c a s e requires a p r o g r a m t o perform a monitoring
function continuously with v e r y little man-machine interfacing. A
machine language p r o g r a m i s probably best suited f o r t h e s e needs.
T o p e r f o r m a c h e c k of t h e cutoff r e q u i r e s i s s u i n g h i - l e v e l s i g n a l s a n d
m o n i t o r i n g f o r c o r r e c t r e s p o n s e s on a s t e p by s t e p b a s i s . T h e r e i s
m o r e man-machine interfacing concerning display requirements,
c a p a b i l i t y t o c h a n g e t h e c o u r s e of t h e t e s t and s a f e t y c o n d i t i o n s . A
m a c h i n e l a n g u a g e p r o g r a m d o e s n ' t p r o v i d e t h e f l e x i b i l i t y , plus t h e t e s t
e n g i n e e r l o s e s h i s knowledge of t h e p r o g r a m i n m a c h i n e l a n g u a g e d o c u mentation.

10

�It i s t h e w r i t e r s opinion t h a t t h e s e a r c h f o r a c o m m o n l a n g u a g e
(defined a s one l a n g u a g e i n w h i c h a l l t e s t p r o g r a m s a r e w r i t t e n ) i s t h e
w r o n g a p p r o a c h . T h e w r i t e r f e e l s t h a t t h e l a n g u a g e u s e d should be
d e t e r m i n e d by s u c h c r i t e r i a a s : ( 1 ) t h e n u m b e r of d e c i s i o n s t h e
e n g i n e e r s m a y h a v e t o m a k e d u r i n g t h e o p e r a t i o n , (2) t h e r e p e t i v e n e s s of t h e o p e r a t i o n , ( 3 ) t h e s a f e t y c o n s i d e r a t i o n s , (4) t h e d i s p l a y
r e q u i r e m e n t s , e t c . All of t h e a b o v e c r i t e r i a a r e c o n c e r n e d w i t h d e t e r m i n ing t h e t y p e of o p e r a t i o n t h a t i s t o be p e r f o r m e d . T h i s i s r e a l l y t h e k e y
in d e t e r m i n i n g the language best suited f o r the t e s t p r o g r a m . A language
f o r p e r f o r m i n g c o m b i n e d s y s t e m s t e s t s c a n be d e v e l o p e d w h i c h XT i l l
c o n t r o l t h e t o t a l o p e r a t i o n a n d a l s o allow t h e a p p r o p r i a t e s u b l a n g u a g e
t o be u s e d .
Of t h e c r i t e r i a u s e d t o d e v e l o p a s o f t w a r e l a n g u a g e , b e i n g c a p a b l e
of a c c e p t i n g c h a n g e s i s c l o s e t o being t h e m o s t i m p o r t a n t . The S a t u r n
h a r d w a r e (vehicle and GSE) w e r e designed with m i s s i o n flexibility in
mind. Mission flexibility o r a n y flexibility f o r that m a t t e r i s synonymous
w i t h c h a n g e s . T h e r e f o r e , a s u s t a i n e d l e v e l of c h a n g e s c a n be e x p e c t e d
f o r t h e d u r a t i o n of t h e p r o g r a m . T h e c h a l l e n g e i s t o d e s i g n h a r d w a r e
and s o f t w a r e s y s t e m s that will a c c e p t changes with m i n i m u m impact.
I m p a c t i n t w o w a y s : (1) t u r n a r o u n d t i m e a n d ( 2 ) t o t a l c o s t ( d o c u m e n t ation, time, manpower).
S o f t w a r e s y s t e m s m u s t be v e r i f i e d p r i o r t o t h e i r u s e i n t h e o n - l i n e
hardware system. The techniques used for the verification activities
m u s t be planned e a r l y . T h e r e a r e m a n y c o s t v s . d e g r e e of v e r i f i c a t i o n t r a d e - o f f s t h a t m u s t be m a d e . T h a t i s , f o r a g i v e n p r o g r a m
t h e r e i s a r a n g e of v e r i f i c a t i o n t e c h n i q u e s t h a t c a n be u s e d . T h e y r a n g e
f r o m using another software p r o g r a m t o using duplicate h a r d w a r e .
Running t h e p r o g r a m o n d u p l i c a t e h a r d w a r e w i l l p r o d u c e t h e m a x i m u m
c o n f i d e n c e t h a t t h e g i v e n p r o g r a m i s v e r i f i e d . But, i n g e n e r a l , i t i s
a l s o t h e m o s t e x p e n s i v e . F o r t h e v e r i f i c a t i o n of a t o t a l s o f t n a r e s y s t e m
t h i s t e c h n i q u e i s n e c e s s a r y . F o r c o m p o n e n t s of t h e s y s t e m a l e s s e r
d e g r e e of c o n f i d e n c e c a n p o s s i b l y be a c c e p t e d a n d s u b s e q u e n t l y a l e s s
c o s t l y m e t h o d u s e d . What m e t h o d i s u s e d s h o u l d be planned c o n c u r r e n t l y
w i t h t h e i n i t i a l d e s i g n of t h e s y s t e m . T h e n e c e s s i t y f o r t h i s i s q u i t e
obvious b e c a u s e of t h e t i m e r e q u i r e d t o d e v e l o p t h e v e r i f i c a t i o n p r o g r a m s
a n d / o r h a r d w a r e . 4 1 ~ 0 ,a n y c h a n g e s i n plans f r o m a n o r i g i n a l v e r i f i cation concept will cause serious schedule impacts.
P r o b a b l y t h e g r e a t e s t m i s c a l c u l a t i o n i n t h e g e n e r a t i o n of a s o f t w a r e
s y s t e m w a s t h e t i m e r e q u i r e d . T h e difficulty e n c o u n t e r e d i n t h e

�g e n e r a t i o n of the s y s t e m s r e q u i r e m e n t s w a s a contributor t o this t i m e .
Independent of this i s the t i m e r e q u i r e d t o c r e a t e , document and v e r i f y
a p r o g r a m . P r e v i o u s t o automation the t e s t p r o c e d u r e s w e r e g e n e r a t e d
f r o m s y s t e m s r e q u i r e m e n t s , but they could be g e n e r a t e d s h o r t l y p r i o r
to running the t e s t . With t h e advent of m o r e complex s y s t e m s and
automation t h i s i s no l o n g e r possible. The optimum solution would be to
develop a l l of t h e h a r d w a r e e a r l y enough t o allow adequate t i m e f o r
s o f t w a r e development. T h i s optimum solution cannot be obtained i n a
c o n c u r r e n t p r o g r a m s o techniques m u s t be developed to t r a n s f e r s y s t e m s r e q u i r e m e n t s t o s o f t w a r e p e r s o n n e l c o n c u r r e n t with h a r d w a r e
development.
E x p e r i e n c e t o date h a s brought the r e a l i z a t i o n that a t o t a l softw a r e s y s t e m h a s t o be developed i n t h e s a m e m a n n e r a s a h a r d w a r e
s y s t e m . F i g u r e 4 depicts a software s y s t e m which i s r e p r e s e n t a t i v e
of a type t h a t i s n e c e s s a r y f o r the launch o p e r a t i o n s . The m a j o r decisions
c o n c e r n i n g t h e components of t h i s s y s t e m have been d i s c u s s e d above.
Once t h e s e d e c i s i o n s have been r e a c h e d and the r e l a t i o n s h i p among the
components e s t a b l i s h e d , they should c o m e under a configuration management s c h e m e . T h i s will i n s u r e the c o n t r o l of any i n t e r f a c e impacting
c h a n g e s . A s e r i o u s d e t e r e n t t o a n automation effort i s t h e lack of u n d e r standing of the c a p a b i l i t i e s and limitations of the s o f t w a r e s y s t e m s .
Putting the s o f t w a r e s y s t e m u n d e r a configurationmanagement s c h e m e
enhances i t s understanding, because it f o r c e s the s o f t w a r e t o be t r e a t e d
a s a s y s t e m with a l l of t h e accompanying documentation. To f u r t h e r
a c c e l e r a t e the understanding p r o c e s s t r a i n i n g s e s s i o n s should be conducted explaining t h e design and o p e r a t i o n of the s y s t e m .
People
L a s t , but m o s t i m p o r t a n t i s t h e people problem. This c a t e g o r y
i s probably t h e m o s t complex a s w e l l a s being the m o s t i m p o r t a n t . The
w r i t e r i s not s u r e that t h e r e a r e any distinct c h a r a c t e r i s t i c s t h a t can be
d e s c r i b e d i n a n explicit, independent fashion. However, t h e r e a r e a
couple which s e e m t o be basic and c a n be d e s c r i b e d .
F i r s t , t h e r e i s i n a n y new endeavor a knowledge-time p a r a m e t e r .
That i s , a t t h e initiation of a n activity t h e r e i s a lack of knowledge of
how that a c t i v i t y c a n be a c c o m p l i s h e d , but a s t i m e proceeds this knowledge b e c o m e s a v a i l a b l e . The p r o b l e m i s t o develop the communication
methods ( i n t e r m s of organization and information t r a n s f e r ) t o apply t h i s
knowledge effectively t o a l l r e q u i r ing a c t i v i t i e s . In the c a s e of automating

�S a t u r n I s t a g e t e s t i n g , t h e r e w a s a n u n d e r s t a n d i n g of t h e c h e c k o u t
o p e r a t i o n a s i t w a s being p e r f o r m e d m a n u a l l y . T h e r e w a s not a
t h o r o u g h u n d e r s t a n d i n g of e a c h h a r d w a r e , s o f t w a r e a n d o p e r a t i o n
r e q u i r e m e n t , n o r o r how t h e s e r e q u i r e m e n t s s h o u l d be fulfilled t o
a c h i e v e t h e a u t o m a t i o n job. A s s t a t e d a b o v e , t h e r e i s nothing unique
a b o u t t h i s s i t u a t i o n . I t a p p l i e s t o a n y new e f f o r t . T h e a s p e c t i n t h e
S a t u r n p r o g r a m which m a k e s this m o r e impacting i s the time element.
By e x a m i n i n g t h e k n o w l e d g e - t i m e r e l a t i o n s h i p d e s c r i b e d i n F i g u r e
5 i t c a n be s e e n t h a t t h e a u t o m a t i o n s y s t e m c o n c e p t , w h i c h w a s t o s e t
t h e pace f o r the S a t u r n I B and V p r o g r a m s , w a s f o r m e d p r i m a r i l y
f r o m t h e a c c u m u l a t e d e x p e r i e n c e of only one S a t u r n s t a g e . B e f o r e t h e
f u l l c o m p l i m e n t of e q u i p m e n t w a s o p e r a t i o n a l a y e a r a n d a half w a s
c o n s u m e d . A s o n e m i g h t e x p e c t , knowledge of how t o d o t h e job
a c c u m u l a t e d d u r i n g t h a t t i m e c a u s i n g h a r d w a r e , s o f t w a r e and o r g a n izational changes.
T o t a k e this relationship and expand i t over the total S a t u r n I B and
V p r o g r a m s , t h e p r o b l e m i s g r e a t l y i n c r e a s e d . It c a n be s e e n f r o m
F i g u r e 5 t h a t t h e i n i t i a l c o n c e p t s w e r e being d e v e l o p e d t o p e r f o r m
factory checkout, static testing and launch operations - engrossing
nine d i f f e r e n t l o c a t i o n s , f i v e s t a g e c o n t r a c t o r s , a n d two NASA C e n t e r s .
Very little actual experience, i n proportion to the total program, exi s t e d a t t h a t t i m e . I m p l e m e n t a t i o n of t h e s e c o n c e p t s r e q u i r e d a p p r o x i m a t e l y t h r e e y e a r s . During t h e s e t h r e e y e a r s much experience w a s
gained, thus considerably a l t e r i n g the concepts that w e r e f i r s t applied.
The second characteristic concerns the attitude toward automating
the testing operations. Unfavorable attitudes concerning automation
h a v e g e n e r a l l y r e s u l t e d f r o m a l a c k of u n d e r s t a n d i n g of t h e long r a n g e
n e e d s a n d b e n e f i t s . T h e s e a t t i t u d e s involved, of c o u r s e , v a r y w i t h i n
t h e knowledge-tim:: r e l a t i o n s h i p . I n t h e S a t u r n - A p ~ l l op r o g r a v t h r e e
o r four y e a r s a r e required for the launch site personnel t o acquire the
s a m e a m o u n t of e x p e r i e n c e a s t h o s e involved i n t h e i n i t i a l d e s i g n and
c h e c k o u t o p e r a t i o n s . F u r t h e r , t h i s t i m e i n v o l v e s t h o u s a n d s of people
w i t h d i f f e r e n t d i s c i p l i n e s a n d b a c k g r o u n d s . T h e r e f o r e , if t h e l a s t
o p e r a t i o n i s t o t a k e a d v a n t a g e of t h e e x p e r i e n c e a n d knowledge g a i n e d
p r e v i o u s l y , t h e p r o c e s s of a c c u m u l a t i n g a n d c o m m u n i c a t i n g t h i s e x p e r i e n c e m u s t be a c c e l e r a t e d .

�PROJECTIONS AND CONCLUSIONS
B e f o r e t h e m a x i m u m benefits c a n be r e a p e d f r o m a u t o m a t i c t e c h niques s e v e r a l a d v a n c e s need t o be m a d e . The f i r s t a n d f o r e m o s t a r e
i n t h e people c a t e g o r y .
F i r s t of a l l , g o a l s need t o be e s t a b l i s h e d and p r o c l a i m e d . T h e s e
g o a l s m u s t be i n t e r m s of f u t u r e conditions f o r which a u t o m a t i c t e c h niques a r e t h e only a n s w e r . In t h e S a t u r n p r o g r a m , g r o u p s of people
have r e s i s t e d a u t o m a t i o n on t h e b a s i s t h a t the i m m e d i a t e job, with
w h i c h they w e r e c o n c e r n e d , could be done b e t t e r t h e old way. The
l o n g e r r a n g e needs should be d e s c r i b e d and explained.

A r e c e n t s u r v e y of t h e S a t u r n - A p o l l o P r o g r a m d i s c l o s e d that t h e
only functions t h a t h a d n ' t been a u t o m a t e d , a t one location o r a n o t h e r ,
w e r e l e a k c h e c k s , a m p l i f i e r c a l i b r a t i o n and s o m e monitoring of
c r i t i c a l functions. Of t h e s e , i t would be a w a s t e of money t o a u t o m a t e
l e a k c h e c k s and s o f t w a r e techniques have been developed t o e l i m i n a t e
t h e need f o r a m p l i f i e r c a l i b r a t i o n . S o t h e p r o b l e m i s not technology,
but u n d e r standing a n d a t t i t u d e s .
T r a i n i n g i s a n a c t i v i t y t h a t n e e d s t o be e x p l o r e d . It i s probably
t h e only way i n which t h e l e a r n i n g c u r v e c a n be i m p r o v e d . As d i s c u s s e d
p r e v i o u s l y , t h i s i s a v e r y s e r i o u s a s p e c t i n the S a t u r n - A p o l l o p r o g r a m
w i t h i t s t i m e s p a n between t h e beginning a n d the end of the t e s t i n g
o p e r a t i o n . A l s o , t r a i n i n g c a n be u s e d t o e r a s e a t t i t u d e p r o b l e m s .
In t h e h a r d w a r e a r e a s e v e r y s t e p which w i l l allow the vehicle t o be
m o r e autonomous should be t a k e n . T h i s w i l l have the effects of r e d u c ing t h e GSE and r e l i e v i n g s o m e of the s o f t w a r e b u r d e n s . To i t e r a t e
s o m e of t h e points d i s c u s s e d p r e v i o u s l y , t h e review of interlocking
r e q u i r e m e n t s , d e v e l o p m e n t of g r e a t e r r e l i a n c e on DDAS and developm e n t of o n - b o a r d s y s t e m s provide t h e g r e a t e s t potential. B e f o r e the
l a t t e r c a n be i m p l e m e n t e d i n t h e m a i n s t r e a m , t e s t a r e a s need t o be
provided t o d e v e l o p t h e c h a n g e s . T h i s would a l s o allow t h e p e r s o n n e l
t o gain confidence u n d e r r e a l i s t i c conditions, thus aiding t h e i m p l e m e n t ation process.
The m a j o r point t h a t n e e d s t o be m a d e i n the s o f t w a r e a r e a i s t h a t
i t needs t o be t r e a t e d a s a s y s t e m . Also, i t should be t r e a t e d on an
e q u a l b a s i s a s t h e h a r d w a r e . In t h e S a t u r n - A p o l l o P r o g r a m t h i s m e a n s

�a t r i a n g u l a r s i t u a t i o n of v e h i c l e , G S E and s o f t w a r e . No change should
bc m a d e t o one without c o n s i d e r i n g t h e effect of the other. T o i m p l e m e n t
t h i s r e q u i r e s t h a t t h e r e be c o n c u r r e n c y among a l l t h r e e f r o m t h e initial
concept t h r o u g h the l a s t launching. Of c o u r s e , t h i s adds complexity t o
t h e t o t a l p r o g r a m , but not n e a r a s much a s would be i f this w a s not
recognized.

-

P r o j e c t i n g outside t h e t h e m e of t h i s p a p e r , t h e r e i s one l a s t point
t h a t should be e x a m i n e d . T h a t i s t h a t t h e checkout and launch i s only
one f a c e t of t h e Saturn-Apollo P r o g r a m . Since they a r e the l a s t
a c t i v i t i e s a l l o t h e r a c t i v i t i e s s u p p o r t t h e m . T h e r e f o r e , if f a s t e r , m o r e
effective techniques a r e applied t o t h e s e a c t i v i t i e s t h e s a m e techniques
need t o be applied t o t h e supporting a c t i v i t i e s . An e x a m p l e of t h i s i s
i n a t e s t p r o g r a m which s e n d s a s t i m u l i t o the vehicle t h e n i n t e r r o g a t e s
a d a t a t a p e f o r the p r o p e r r e s p o n s e d a t a . The d a t a t a p e i s t o be supplied
by e n g i n e e r i n g containing a l l of the p a r a m e t e r s and t h e i r l i m i t s . Howe v e r , if e n g i n e e r i n g i s n ' t g e a r e d t o s u p p o r t t h i s type of o p e r a t i o n , the
d a t a t a p e w i l l n e v e r be a v a i l a b l e on s c h e d u l e nor w i l l change capability
e x i s t . T h i s s o r t of supporting r e q u i r e m e n t s r e p r e s e n t s a whole field
t h a t m u s t be e x p l o r e d and i n t e g r a t e d into t h e t o t a l job.

�W I -

= w
=
&gt;
C3

��INSTRUMENTATION
TEST STATION
PERIPHERY EQUIP

TEST STATION

RELAY LOGIC
ANALOG GEN

FIGURE 3
AUTOMATED CHECttOUT OPERATI ON

�MAN-MACH INE

FIGURE 4
SOFTWARE SYSTEM

IN PUT-OUT PUT

�DEFINITION O F

DEFINITION 0

FIGURE 5

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20157">
                <text>spc_stnv_000063</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20158">
                <text>"Analysis and Projections of Space Vehicle Automatic Checkout and Launch."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20159">
                <text>Vedane, C. R.</text>
              </elementText>
              <elementText elementTextId="20160">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20161">
                <text>1966-10-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20162">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20163">
                <text>Saturn project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20164">
                <text>Automatic test equipment</text>
              </elementText>
              <elementText elementTextId="20165">
                <text>Rockets (Aeronautics)--Launching</text>
              </elementText>
              <elementText elementTextId="20166">
                <text>Space vehicle checkout program</text>
              </elementText>
              <elementText elementTextId="20167">
                <text>Launching</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20168">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20169">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20170">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20171">
                <text>Box 19, Folder 17</text>
              </elementText>
              <elementText elementTextId="205814">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20173">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20174">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20175">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3317" public="1" featured="0">
    <fileContainer>
      <file fileId="2456">
        <src>https://digitalprojects.uah.edu/files/original/76/3317/loc_burw_-113_114.pdf</src>
        <authentication>d94db60196b2bc3134f24a35b8f62e47</authentication>
      </file>
    </fileContainer>
    <collection collectionId="76">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="28299">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="28300">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="133718">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/145" target="_blank" rel="noreferrer noopener"&gt;View the Burwell Family Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="133721">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3332" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1943-1944&lt;/a&gt;</text>
                </elementText>
                <elementText elementTextId="133722">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3333" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1944-1945&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="90">
              <name>Provenance</name>
              <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
              <elementTextContainer>
                <elementText elementTextId="133723">
                  <text>Materials donated and digitized by Dudley Burwell</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="65231">
                <text>loc_burw_000113_000114</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65232">
                <text>"Annex #1 to accompany March Order No. 1".</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65233">
                <text>This annex discusses the schedules, vehicle use, and uniforms for March Order Number 1.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65234">
                <text>Phillips, Thomas M.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65235">
                <text>7/20/1949</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="65236">
                <text>1940-1947</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65237">
                <text>Alabama. Army National Guard</text>
              </elementText>
              <elementText elementTextId="65238">
                <text>United States. Army. Engineer Combat Group, 1169th</text>
              </elementText>
              <elementText elementTextId="65239">
                <text>Fort Benning (Ga.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65240">
                <text>Orders (military records)</text>
              </elementText>
              <elementText elementTextId="65241">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="65242">
                <text>Burwell Family Collection</text>
              </elementText>
              <elementText elementTextId="206673">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65244">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65245">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="65246">
                <text>loc_burw_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3318" public="1" featured="0">
    <fileContainer>
      <file fileId="2457">
        <src>https://digitalprojects.uah.edu/files/original/76/3318/loc_burw_-115_119.pdf</src>
        <authentication>c8dbd8173b90e5f60bd158db930bef7a</authentication>
      </file>
    </fileContainer>
    <collection collectionId="76">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="28299">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="28300">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="133718">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/145" target="_blank" rel="noreferrer noopener"&gt;View the Burwell Family Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="133721">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3332" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1943-1944&lt;/a&gt;</text>
                </elementText>
                <elementText elementTextId="133722">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3333" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1944-1945&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="90">
              <name>Provenance</name>
              <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
              <elementTextContainer>
                <elementText elementTextId="133723">
                  <text>Materials donated and digitized by Dudley Burwell</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="65247">
                <text>loc_burw_000115, loc_burw_000119</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65248">
                <text>"Annex No. 2-March Tables".</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65249">
                <text>These tables show March Units Numbers one through four with their miles, time, and units.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65250">
                <text>7/18/1949</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="65251">
                <text>1940-1948</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65252">
                <text>Alabama. Army National Guard</text>
              </elementText>
              <elementText elementTextId="65253">
                <text>United States. Army. Engineer Combat Group, 1169th</text>
              </elementText>
              <elementText elementTextId="65254">
                <text>Fort Benning (Ga.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65255">
                <text>Charts</text>
              </elementText>
              <elementText elementTextId="65256">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="65257">
                <text>Burwell Family Collection</text>
              </elementText>
              <elementText elementTextId="206674">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65259">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65260">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="65261">
                <text>loc_burw_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10569" public="1" featured="0">
    <fileContainer>
      <file fileId="9644">
        <src>https://digitalprojects.uah.edu/files/original/20/10569/Satannprorep_030408114318.pdf</src>
        <authentication>80981e36b427a0f066c60b2b154062d4</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="159419">
                <text>Satannprorep_030408114318.pdf</text>
              </elementText>
              <elementText elementTextId="159420">
                <text>spc_stnv_000681</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159421">
                <text>"Annual progress report :1966-1967."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159422">
                <text>The Annual Progress Report from July 1st, 1966 through June 30thm 1967.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159423">
                <text>The Boeing Company Launch Systems Branch, Space Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159424">
                <text>1967-07-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="159425">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159426">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="159427">
                <text>Saturn S-1C stage</text>
              </elementText>
              <elementText elementTextId="159428">
                <text>Project management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159429">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="159430">
                <text>Progress Reports</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="159431">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210333">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159433">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159434">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="159435">
                <text>spc_stnv_000675_000699</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1151" public="1" featured="0">
    <fileContainer>
      <file fileId="998">
        <src>https://digitalprojects.uah.edu/files/original/20/1151/spc_stnv_000067.pdf</src>
        <authentication>6d546011779bd6bc44167875ef38a8c8</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177285">
                    <text>SATURN MISTORY DO~"llj--~
Univer"h/ OF Aigbama R~~catch Instikg
'"t0.y of Science E bChnD,ogy
Dak--

THE I

~
1

I REPORT
L
OF

THE !

--_------- Doc

'OW

--- ---_

�.....................
...........................
..............................

I

I

To Our Stockholders
2
The Foundaflotl
4
Mission Suppart ........................ 4
bearch
6
EIechnigs ............................. 7
Infomation Sciences
.18
Structural and Mechanid Systems ....... .19
Architecture and Facilities Engineering ... .21

...................

t h e Future

..............................22
..............
...................

Brown Engineering Facilities
.23
Officers and Directors
.24
Financial Information ........... Center Pages

.............
.............
........
Cash Wow per share (I). . . . . . . . .
Dividends paid . . . . . . . . . . .
Total daties and wages . . . . . . . .
Net addhiom to buildings, leasehold
irnprovements,and equipment . . . . .
Net J e a .
Net h o m e
Net income per share (1)

........

Total sbckhoIders' equity
Wotking capital
Number of stockholders of remrd
Number of employees

...........
.....
.........

(I
Computed
)
on total shares outstandng at close of year 1965
(2) Restated for pooling of interest

Received long-term mission support contracts.

Built large electronic ground support systems for Saturn program.
Acquired Electro-Mechanisms, Inc., a New England electronics manufacturer.
Began construction on electronics manufacturing plant at Lewis burg, Tennessee.

Established Information Sciences, Inc., in key southeastern cities.

De ;EMan fhe wmvw we the SIX a m of
sc&amp;vfiy wrrenNy being pursW by Brown Enghee'ring. The subject of' each prcture Is
shown w i n in$@ ,the repart t a g h e r with
an expkna#Ofl eaphon.

�TO OUR
STOCKHOLDERS

The year 1965 marked an important 12
months far Brown Engineering Company. I n c ~ a s e dsales and earnings were
accompanid by other significant events
that promise to profoundly affect
Brawn's future.
For the fgth straight year, the corn
pany's safes and earnings Increased
over those of the previous 12 months.
Sales in 1965 tabled $45,302,418. Net
earnings, reachjng the $1 million mark
for the fiat time, were $1,134,484, ar

This compares with
earnings d
$924,641, or $1.24 per share, in 1954.

$1.52por share.

safes of $42,3W,754and

Long-term contracts having a poten-

In addition to his res 6ibltEties as pfesident
and chafrrnan of the
at emwe EngInesring Company, Milton K. Cummfngs 1s act/%?in
community, state, and natfonal affaffs.

�tial value of more than $1M million
were awarded the company to provide
technical suppart ta the National Aeronautics and Space Administration's
George C. Marshall Space Flight Center. The latest awards replaced a m m ber of short-term contracts Brown held
with this key NASA installation, and offered the company a solid eeonornic
base far the next five years.
Brown expanded its markets and capabilities, especially in electronics and
information systems, through smaller
firms as subsidiaries, new equipment,
and facilities. Brown acquired Electro-

Mechanisms, Inc., a New EngEahd elec- 3,mO employees, highest employment
tronics firm, and established Infarma- in the company's history, and locations
tion Sciences, I nc., in Atlanta, Georgia, in Jx states. We believe the events of
to prov'rde management and computer "165 will strongly influence the future
services. In addition, the company en- success of Brown, Our long-term contered an option to purchase T ram-Data, tracts, along with our expanded mpaInc,, a Huntsville electronics firm.
bilities and markets, give us a solid
Construction was begun in 1965 on a foundation for growth.
manufacturing plant at tewisburg, TenWe are grateful to the many permns
nessee, to house a part of the com- - customers, stockholders, and empany's growing electronics operations, ployees - who made 1965 s ~ &amp; a sigand a highly advanced computer was nificant period in Brown's history. Their
installed in Brown's data pracesslng continuing interests in our company
give us every reason to look to the fulaboratory at Huntsville.
At year's end, Brown had more than ture with great confidence.

Milton K. Cumrnings
Chairman and president

��space and defense deeply involved
Brown in programs of the National
Aeronautics nnd Space Administration
and the Army during 4965. The company made significant contributions to
these agencies toward the development of large space boosters for space
expIoration
defense.

and

modern missiles

for

In '1965, Brown received new longterm contracts to support programs of
the ~ a r s h a l lSpace Flight Center. The
awards included prime contracts to support the Propulsion and Vehicle Engineering Laboratory and the Research
Projects Laboratory at the center, as
well as subcontracts to support the Test
Laboratory and the Quality and Reliabi lity Assurance Laboratory. These contracts represent potential sales of more
than $100 million for Brown over a

five-year period. Since these are awardfee type contracts, under which the
company's fee is governed by the quality of i t s performance, Brown has the
opportunity to real ire greater profits
than it did from former mission support
agreernenk

the study of materials used in the v e
hicles. Brown also contributed to such
advanced projectsas preliminary studies
for manned orbital vehicles and tightweight surface vehicles for lunar exploration.

As the prime contractar to the Propulsion and Vehicle Engineering Laboratory, Brown provides technical support to MSFC's mission to develop Saturn space boosters far America's moon
program. The company has technical
and professional personnel of almost
every scientific discipline assigned to
this task. Their work includes such activities as the analysis of the Saturn vehicle's structure, engines, and propulsion systems; the integration of major
systems that are necessary to form the
complete vehicle; the evaluation of r e
lated ground support equipment; and

MSFC's Quality and Reliability Laboratory included the development and aperatian of an automated information
storage and retrieval system which provides reliability data on parts and materials used in the Apollo space program. Known as the Apolla Parts Information Center (APIC), this system is
ab te to automaticajly answer the
queries of ather NASA centers and industries associated with the space program. The highly sophisticated system
is particularly advantageous to today's
widespread, but fast moving,space program, because it accepts inquiries 24

Brown's significant contAbutions to

7% ddatrnifle the mdian of fuaf lh the h k s
is beyand #e MI &amp;
ih'e esifh's ~ a v Brow? deveIcp? a unique
methad Tor d f m v ethg thts condr D ~ by
I kmng
me fluH float En amtkr. HHeae, a Hue
Ifqtrid, floafin in a red flrrfd, !s Wb~atedto
s h o ~resmrJm w b t might ~e p m in
the ,fuel tank a' 9 miffg kr#W whlcle.
of a space v'ehi'efewhim It

�hours a day and

tranmiu

or r-ives

text?phot~gnph$,and drawtna;s over a

world-wide network.
In Suppart of the MSPC Test L h m bry, Brown test$ .components and subsystems far qaGe v&amp;icles and related
ground supp,rrt equipment by evaluatIng their r e d o n in hasrile mimmen&amp;. Addithnallp, the ~ompanyde
sign5 faciIitia for testi% en@&amp;
and
bgaste35, and

designs and buitds spe-

cial fixtures that a r ~us&amp;

in

w&amp;-

mental t@Tirlg.
Brow&lt;nYsrole in the space proairam at
the Ma&amp;all $pace Flight Cmtw also
murrnpas pwjeas that lie beyond
,tudafi's Apnlb moon missfon. As the
prime soure for m h n t d suppart ta
MSFC's Research Projem Letboramry;

the mmpat~yIs a prWia1 parkkipant'
in scientific programs assocbtd with
mads wrrt.irtut#g invstigatians o# the
universe after he reachathe moan.

a r c h and &amp;velupment auppo&amp; w a

provided b r inettiat ,~idarrc~.
ahd ~ m trd .equi~mmtfor a VTQL ~ v d d
Wffand landinid 9ikmft-

ltESEARCH ri The seIeEtSan of @to
q p oj NASA's R e m d h~ i e &amp; tabo-q
at -the NASA / b
lZ
a
r
W Spwe
FIEght Center IhWCl ef1ecYs s
~
!y an oar increased c q ~ b i f i t 3 e li'n
~ this
parea tn additinn to p ~ m g . a s i s I s ~ ~ e
potted the A m y Materiel ~pmrrtmd's to this MSN= function, Brown's BEN i b % Praft. Office In the deielop- s
d ~aft3tb.Biti~
were also d h c t d
meht of Pcmerid5 anti-missile missile md
a c c o m p l i € a t of sdew
system through the perforfia'nce of en- tifir: sftrdles for other NASA o t g a b
#neering, Wi,
and ahalpis t a 8 b tionst the A m y , and Navy, as we11 as
Under a cunmct from the Army Mi+ #he dwekymM of new products and
sile Cammand, %a rompmy dweloped tedtnolqies for the company,
a guidance and control spterrt for a
with MSFC*$ REnew anti-tank . n b s i l ~In a d j t i ~ n ,re- Under the con=

The company made signif iamt cotrtributlona in 1965 ta the Atmy's dwelapc
merit of m i a l e and aircraftpa -1 t as
an automat&amp; zystern far stouing.andre
trhvlng m$ineering data. Bro,wn s ~

*

�Exampfa af muM-layer cfrcuR baa&amp; and
nnfed w&amp;Rn develcrw and manuktured
gy Bawn ~ngkseringand its ruhsidia@, Elecfro-Mechanisms, Cktu/try shown above is part

of Wernefw egujpment used fo trmsmff vltal

dab back to Earth from Saturn space vehlclm.

�of flexible printed cabling a d multilayer circuit baa&amp; was acquired as a
subsidiary. A joint venture was effected
with another company specializing k
data acquisiaon systems, A new division, to be housed in a modern plant
a€ Lewisburg, Tennessee, was created to
continue the company" telemetry and
instrumentafion operations. Advances
were made in the field of micmcircuitry, new products were introduced,
and other products were improved to
take advantage of new market putentials and advancing techndogins.

last, Firrther, Ef the computer should
FaiI completely, the DCE's control panel
allows vehicle checkout te be performed manually, avoiding the enormous ms,t af an aborted mIssian. The
DCE is capable of receiving and processing command signals controlling
up ta 21116 discrete function's within
the vehicle. To accomplish this gigantic
feat requires approximately 13,000 electronic module assernbtia wwithin each
of the nine DCE systems currently being hui lt.

The DDAS receives data transm ftted
from the Saturn vehicle, decodes it, and
presenb it for evaluation. The cornplexity of this equipment is indicated by the
fact that 103 major racks of equipment

Brawn continues to be the largest supplier of telemetry and i nstrumen-tatian
equipment for the Saturn program, not
only to NASA, but to many of NASA's
prime contracQrs as well. Thew incl ude No~th American Aviation, Boeing, Dauglas, IBM, and General dectric.
Plans are underway to add a line of industrial and commercial talemetry
equipment fe the aerospace and defense units Brawn builds. Telemetry
equipment has appIicatians fur remote
monitoring in process cuntrol, biomedicine, petrateurn, and chemical in-

dustries.

Perhaps the mest significant contributions to Brown's diversification in elmtronics are the subsidiary acquisltians
are required.
and facility expansions that took place
Other contracts awarded to Brown in 1965,
Engineering during 1965 include one
The acquisition of Flectro-Meckanwith the Air Farce's Rome Air Develop- isms, Int., finalized in 1965, has pravan
ment Center and one with NASA's to be an extremely good investment,
Langtey Research Center. The Rome This young, dynamic, and profitable
contract is Brown's first major research subsidiary has increased its grass sales
contract with the Air Force and calls from $500,000 in 1964 to almost $3
The DCE, designed by Brown under an for the company to investigate the fun- million in 1965. Electro-Mechanisms
earlier contract, incorporates a high de- damental limitations of negativeresis- has facilities in Methuen, Massachusetts,
gree of reliability through the use af tance semi-conductor devices used in and Nashua, New Hampshire, and is
triple-redundant voter circuitry. This communications systems, The Langley currently seeking new plant locations
feature allow$ the DCE to continue to contract fe for design, development, far future expansion of its printed cirfunction in the event one of fie signals and manufacture of an aircraft-tu-air- cuit cabling and multi-layer circuit
from the Saturn Ground Computer is craft ranging and altimeter system.
boards.

To link Saturn Y space vehicles to au-

tomated checkout equipment, Brawn is
building discrete control equipment
(DCE) and a digltal data acquisition
system (DDASI for checkout and monitoring functions before and during the
launching of these vehicles. The relationship of this equipment to NAmSA's
Apollo program (moon mission) is depicted on the facing page.

ContmI Ewlpwnt
IDCEI systems are shown herre w parts of the
Saturn Ground Computer System, Also shown
Is IP Digital Data Aqdsitlotr System (DDASI,
being brrllt by Brawn under mntract b General Electric. A fonctlanal d@scr/ptEonof thesystms follews: (!) W L X E is kccased
at the Launcher Umbi11wlTower (&amp;LET) fu aubmat!calfy translate cwmnands from the Bturn Gmnd Corn utet Into discrete control
tunet~ons !or veRicie d m m t (automstic
made). The- WE may also be opemted /n ft8
manud mode $0 rnwlrrally r'nftlateconiF'o1 funcbans through a control pane) located dthes on
the DCE itself (local mandmadel or UP bc 7
miles away f r e p t s manual mdBI. 121 The
DDAS recervas stma&amp; Pam the Saturn vehIek
Which indicate the varl~useven&amp; &amp;king p/ace
In the vehfcie duflng performance of uehTcYe
checkout. T b m signals are tmns!atd fnta d&amp;ifat language by the DbAS and relayed to the
Saturn Ground Cornpuh far evdmtid~,The
DDAS mmtlnues to mcelve data after rehkk
launch through t e l m wur'p~~~ent.
~
133 The
Two of h w d s DIscreie

Saturn G m n d Compuw at f
h LUT is canneefed b ern )dentical eompuhr at the Launch
Cantfol Center (LCCl so that the en the operation of the LW mmpmr /$ du Itcaw In the
LCC carnplmv 141 A second D&amp; is located sf
the LCC and ls connecW to the LCC m p o f e r
In the same wa that the flat DCE E
s cannested to the
computer, Thus, since hofh
DCPs are funMming In fha same manner and
receiviq idwEia1 inputs, the outputs are
Ilkewlse ident/cat, 151 An hd!Wor panel Is
ccmneeted to tha output ind df the secorPd
DCE In the same way that the W r n vehtcle
is connmed to the first WE. Slncs the outputs of bofh EE's are Idenikal, the Indicator
panel can be made to Ino'rcate an or all of
fie contra/ fmctim baing a p p d t o ~ l vee
h/&amp;. Thus, pednrmance df th&amp; entire grdund
checkout flocedure, fakM place at the LUT,
ten be m i t o &amp; af the l&amp;,before and after
/aurrch. In add~Yion, all nr any pari pf the

LX

checkout procedure can bs mtr&amp;fI&amp; manualy through tha first DCE3

&amp;of

panel.

���B R W N ENGINEERING COMPANY, IVC., AND SUBSIDlARlES
Y e m ended Bembm-31, I=, a d kmhr *I, 19#

-I965

.

,\

lS4

I

!

.

I

~e~era~'and:ad&amp;ni~trafjve
expense

:

. . . . . . .

INCOME FROM QPERATIUNS

Other deductions;
tnt~restmpmw . . .
0th expmm - net .

.

. . . . . . . . .

INCUMZ BEFORE TAXES ON INCOME
T a a on inmme - Note C:

Federalincgmehat~s . . . . . . . . . . . .
State i n m e t a x e

. . . . . . . . . . . . .
TOTAL T A X B QN INCOME

NET INCOME
Add retained earning

at bqginming wf year

. . . . . . .

2,003,337

$ 3i137,315
W u a ~ $ 5 1 7dividends paid - $.XI
a ahare in 1965, and 1964
146,352
RETAtNEDEARNING5ATEND OF YEAR
$2,991,263
Deprecktisn and a m r t i z a i o n inciwded above:

Year ended Dwernbw 31,1965 - $938,m.
Year ended Chcmbw 31,1964- $ W , J 1 5 .

!3emates to .amdidaid financial state man^.

. . . . . . . .

Warking capital at begrnntngof yeat
Addilms:
Cash fun&amp; p W d &amp; by operatiatd~:

Werinramc

. . . . . . . . . . . . . ~ @;$
.

Prmkion for depredaQanand amortleation of
pmpmty, plant,equiprnmf, ad kmhald

irnprravemenQ . . . . . . . . . . .
Amortkatian ~f rnimltmenus quiprnmt a d
y he* ~;ro.n-&amp;
expenses
I n m in~Iang-mrm debt . . . . . . . . . .
5ak ef Eammm 5tuc.lc under employee slack aptiopla

m,$%

. . . . . . .

Oducticrns:

Cash $ivkhn&amp; paid . . . . . . . . . . .

Net additions t . property,
~
plant, equipment, and
teamhold impravmen&amp;
M d I n r m c in maher mn-currant
Working capital at end of year . . . . . . . . .

.

.

..

.

4

m*
. %'
-&amp;##
-

?

&gt;

,'

-

�����A joint venture with Trans-Data, hcWd Another addition occurring in 1965
may scrgn r ~ ~ uinl tB m d s acqukition was tha &amp;tabfishhentof n micrclcfrcuit
of this Huntsvj IIe-based company. laboratory in the WunBville facility:
Trans-Data, Inz., has qecialized =pa- Mlc~o:oelectronicpackaging tech iques
Mities in the dpign and development now being developed will be used to
af ground-based data acqsluhitlan sys- develop a transmitter that will send up
tem.
to 50 channels of data, The unique
Lewisburg, lenn~ssae,b the site of asp%!&amp; of this trahsmftter is that jjt will
anather expandon of Brawn" elmren- be only one inch In diameter by five
ia capabilities A new manufacturtng irr&amp;es long, and will transmit data from
plant b being built on a 30-aae sit&amp; in with in the shaft of a rotating turbine.
kwi3burg's new i n d ~ t r i a lpark. The
plant will allow Brown to maintain its
position as a principal supplier of te-

New electronic products develaped in
lemetry and Instrumentation equipment 1964 by Brown include a "sslder-lwb
far the space program and will m m Ing" machine for applying proterrlve
the additional floor space requirements solder a a t h g s to printed-drcult boards
Fdr the M r e emergence of the com- for wttmeIy high-reliability applimtians. This machine represents s siftpany i n t ~cgntmercial markets.

nificmt advance in the state of the art,
hwaus i-t cah decr&amp;a~eproduction
time ahd costs o w previous methods.
Weml ac-w
items have been
developed far the Brow- clwed-circuit
tele-vEs4an canara. These Include an
optleal pan/tilt/zoorn .device which enables an operator to vary the camera's
field of view f m a remote lmation
whik the camera itself remains stationary. The camem has also undergone tedesi~n.As a result, it can be
bui tt more ecanomfally ahd offers improved reliability, performance, maintainability, and flexibility. Additianally,

Brown camera can be modified so
that it wjll be sensitive to infrared light
far detedtion of hydrogen flm. It is expected that this modification will find
the

a/seaming igmlsnt e m f l y lnstaited
P"
"iIte" facjtlty t~ mwrt pewrfitm m t e r s &amp;ecfly I n b m a W I e 'Y,pe

O

a Drqwn% Wuntw

enk&amp; md mlerufilmrecords. This &amp;v!ce can
five different type fonts at the rate 6f
2;aod &amp;MWS per SWM,

�widespread applications in both government and commercial areas. Strobe
lighting is also being used in conjunction w i t h the camera, lending t o a variety of "exploring" applications: inspection of caves, drilled holes, and
buried pipe lines.

ing used in two major airborne navigation projects. Brown's BECON connector line has n o w been expanded t o 29
bas~ctypes, four of which were added
in 1965. In addition, Brown makes 1 2
types of custom-designed BECON connectors for special applications.

Another product improvement is the
adaptation of the company's BECON
printed-circuit connectors as microcircuit carriers. An outstanding feature of
these connectors is that the microcircuits are held t o the carrier b y spring
clips instead of solder, facilitating considerably the replacement of circuit
elements. This approach is currently be-

INFORMATION SCIENCES / Brown's
capabilities in computer sciences increased significantly in 1965. A whollyo w n e d subsidiary, l n f o r m a t i o n Sciences, Inc., was established in Atlanta.
A n I B M 360 computer and a Philco
6000 optical scanner were installed at
the Huntsville facility, A centralized information-dissemination system was de-

veloped for shipboard helicopter maintenance. A n d several extremely complex computer simulation models were
developed for the U.S. Army and NASA,
including an analysis of the saturation
probability of a defensive missile syst e m and a detailed analysis o f a
wheeled vehicle operating over the
surface of the moon.
Information Sciences, Inc., Brown's new
subsidiary, is presently providing data
processing services, automated engineering and management services, and
technical publications services t o aircraft, aerospace, defense, and commercial customers, including many small

Disc storage unit of IBM 360, Model 40, computer, recently installed at Brown's computer
facility. This disc system offers several operating advantages over magnetic tape.

�businesses throughout the Southeast.
Since this subsidiary was established in
Atlanta, Georgia, only last July, employment has more than doubled and
branch offices have been established
in four Southeastern cities: Huntsville,
Birmingham, and Montgomery, Alabama, and Merritt Island, Florida.
In order to better serve this market, an
IBM 360, Model 40, computer was installed. In support of i t s program to develop an automated engineering data
system for the U. S. Army, Brown installed an advanced optical scanner
that directly converts typed words and
numerals to computer symbols and

transcribes them on magnetic tape.
This sophisticated technique virtually
eliminates the time-consuming chore
of keypunching information before
placing i t on tape.

mission and closed-circuit television to
bring the needed information to the
particular shop.

Brown also developed a method for
the automatic writing of military speUnder a contract with the U. S. Army, cifications by computer, and a comBrown designed and developed an in- puter simulation program for evaluating
formation-dissemination system for use the mobility performance of wheeled
in a floating aircraft maintenance fa- vehicles on the moon's surface is becility for offshore maintenance and re- ing investigated by Brown for NASA.
pair of helicopters. This system allows
any of the various shops aboard ship to STRUCTURAL AND MECHANICAL SYSquickly obtain maintenance and repair TEMS / Over the years Brown has esinformation from a central data storage tablished and expanded specialized
unit. Brown's system, which i s micro- fabrication and testing capabilities to
film oriented, utilizes facsimile trans- support the company's intimate role

Test fixture in Brown Engineering's Test Laboratory for dynamic testing of rocket engine
gimbals. Gimbal under test is for engine used
in third stage of Saturn V space vehicle.

��I

'

1
,

1

services being provided t o NASA, the
U. S. Navy, industry, municipal governments, and private citizens.

to partrcipate In the manufacture and
testrng of grant arms rt desrgned t o support service Irnes gorng from ground
equrpment t o the Saturn vehicles. Brown
also evaluated the relrability of electrical, mechanrcal, hydraulic, and pneumatic components for the Saturn
ground support equrpment, and the
company burlt and ~nstalledelectronrc
instrumentatron equrpment for handlrng hazardous lrqurd propellants used
In space vehicles.

Reed-Mullrns and Associates, Brown's
architects-engrneers, desrgned a new
Federal Offrce Burldrng and Court
House In Tuscaloosa, Alabama. The
modern three-story structure wrll feature a penthouse and wrll contain approxrl~lately63,000 square feet of floor
space

ARCHITECTURE AND FACILITIES ENGINEERING / During 1965, Brown continued t o expand its capabilities in architecture and facilities engineering, with

Brown's Facilrties Engrneerrng Department performed work on a turbrne engrne test facilrty for the U. S. Navy,
completed design and construction

Herbert Johnson Towers, a recently completed
apartment building for the aged, was designed
by Brown's Reed-Mullins and Associates. This
eight-story structure is conveniently located
near several of Huntsville's shopping centers
and incorporates many unrque convenrences,
particularly suitable to its residents.

drawings for Brown's new test facility,
and desrgned a thermal rnsulation test
facilrty and a mobrle acoustrc research
laboratory for NASA's George C. Marshall Space Flrght Center (MSFC). The
m o b ~ l eacoustrc research laboratory 1s
an easrly-movable acoustic test facility
for exposlng large test specrmens,
werghrng up to 30,000 pounds, to the
tremendous nolse levels produced by a
Saturn V booster whrle ~t is b e ~ n gtest
fired Brown helped develop comprehenslve master plans for MSFC facrlrtres
rn Huntsv~lle,Alabama, and Michoud,
Loursrana, covering such Items as rarlI oads, utr lrtres, roadways, drarnage, securrty, and crvrl defense.

�THE FUTURE

upon the recommendation of the
board of directors, a Curparate Development and Planning Committee was
organized to examine the future p a l s
of the company and to apply its talents
te the solution of problems vital ta
Bruwn's continued growth and development, This committee has developed
an aggrasive plan for growth that includes sales and profit goals and acquisition plans for Brown. Further, a Future
Programs Office was established to enhance the company's opportunities for
participating in new government and
industry research and development
programs and to broaden Brawn's participation in existing programs.
In the future, Brown expects to cornmand a major rota in significant new
developments on earth, as well as outer
spare. Aggresive goals for sales, earnings, market expansion, and technaIogical advances are a part ad this course.
Such goals are considered realistic, be
cause Brown's interests over the next
decade parallel the demands and problems America's growing population and
prusperity are expected to creak.
Brown believes that it is In a strong
position to make important contributions to future space developments, because of the amciation the company
has with today's moon program in its
work for NASA
The company looks forward to increased partidpation in missile devafupment programsfor the Army, a5 well
as the research and develupment t a s k
sf other branches of the military,
Brown also expects to be one of the
companies that will contribute solu-

tions to America's mass transporntian
problems an earth. It believes that the
same technologies that will carry man
from earth to h e maan can be applied
to get man from his home to his office.
The company's expanding electronim
capabilities promise to give Brown a
significant share of the rapid growth

market far large special-purpose systems, special packaging devices, microcircuitry, and closed-circuit television,
Brown expects to be a prominent
competitor far the virtually unlimited
information retrieval and computer
m i c e market. Through a subsidiary,
the company has already made a position fur itself in this commercial field.
As department stores, warehouses, utilities, and others turn to computers to
serve their gruwlng l i n e af customers,
Brown's future is expected to spiral upward in this a m . Laset. research, carried on by the company for several
year% is expected to bring about significant applications for this exotic light
source in medicine and industry. Spccialized design, engineering, manufacturing, and testing capabilitis within
the same complex has put Brown irl an
excellent position to participate in the
development of major systems.

The company's corrtribution~in the

farm of modern hospitals, libraries, industrial plants, and other public buildings are expected to be recognized as
enginears and architects are chosen for
the future development of the nation's
communities.

The company looks to this future with
optimism and enthusiasm.

�BROUln E161nEERllRG FACILITIES
ELECTRO-MECHANISMS, INC.
ACi

. - ..ISLAND, FLA.

�OFFICERS1 From the top,
Milton K. Cummings, President

Joseph C. Moquin, Executive Vice President
Robert B. Anderson, Senior Vice President
WiIliam A. Giardini, Vice President
Raymond C. Watson, Jt.,Vice President
lack W. Hendrix, Vice President of Administration
William 1. Vernon, Secretary and Treasurer

DIRECTORS
Milton K. Cummings, Chairman
Robert B. Anderson
William A. Giardini

Elliot Coldstein
Thomas D. johnson
M. H. Lanier, jr.
H. E. Monroe
JosephC. Moquin
Sidney IG Tally
Kenneth I. Thornhill
William 1. Vernon

D~im,
copy, art, photagraphy,
24

and printing by I s m n En~lneeringCompany

��</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20232">
                <text>spc_stnv_000067</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20233">
                <text>"Annual Report of Brown Engineering Company, Inc. For the Year Ended December 31, 1965."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20234">
                <text>Brown Engineering Co.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20235">
                <text>1966-02-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20236">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20237">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20238">
                <text>Aerospace industries--United States--Periodicals</text>
              </elementText>
              <elementText elementTextId="20239">
                <text>Brown Engineering Co.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20240">
                <text>Annual reports</text>
              </elementText>
              <elementText elementTextId="20241">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20242">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="205818">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20244">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20245">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20246">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13796" public="1" featured="0">
    <fileContainer>
      <file fileId="10425">
        <src>https://digitalprojects.uah.edu/files/original/193/13796/Defense_Billboard_126_001.pdf</src>
        <authentication>74bb228e0d2922e0d99c80e6146f423e</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197482">
                    <text>B I L L B O A R D 126

See your voting officer
American Forces Information Service • Department of Defense
601N. FairfaxStreet Suite 312.• Alexandria. VA 22314-2007 • (703) 42*0283, DSN 328-0283

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="193">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="194954">
                  <text>Defense Billboard Posters</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="195440">
                <text>Defense_Billboard_126</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195441">
                <text>"Any way you cut it...you hold the winning hand (See your voting officer)"</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="195442">
                <text>D2.9:D36/2/No.126</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195443">
                <text>Military uniform holding cards with words vote and register</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195444">
                <text>Department of Defense</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195445">
                <text>1998-07-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="195446">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195447">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="195448">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="195449">
                <text>Voter registration</text>
              </elementText>
              <elementText elementTextId="195450">
                <text>Playing cards</text>
              </elementText>
              <elementText elementTextId="195451">
                <text>Puns</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195452">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="195453">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="195454">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="195455">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="195456">
                <text>Case 1, Drawer 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195457">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195458">
                <text>This material may be protected&#13;
under U. S. Copyright Law (Title 17,&#13;
U.S. Code) which governs the&#13;
making of photocopies or&#13;
reproductions of copyrighted&#13;
materials. You may use the digitized&#13;
material for private study,&#13;
scholarship, or research. Though&#13;
the University of Alabama in&#13;
Huntsville Archives and Special&#13;
Collections has physical ownership&#13;
of the material in its collections, in&#13;
some cases we may not own the&#13;
copyright to the material. It is the&#13;
patron's obligation to determine&#13;
and satisfy copyright restrictions&#13;
when publishing or otherwise&#13;
distributing materials found in our&#13;
collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="195459">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2306" public="1" featured="0">
    <fileContainer>
      <file fileId="3973">
        <src>https://digitalprojects.uah.edu/files/original/20/2306/spc_stnv_000078.pdf</src>
        <authentication>caeccc01f22dd0f69d6603d64ccefc37</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="45822">
                <text>spc_stnv_000078</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45824">
                <text>"Apollo - LEM Docking Drogue Assembly Static Structural Test."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="45825">
                <text>SID 67-318</text>
              </elementText>
              <elementText elementTextId="45826">
                <text>TR 332015A</text>
              </elementText>
              <elementText elementTextId="45827">
                <text> CTR 02332015</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45828">
                <text>This document contains the tests and test results from structural tests performed on the Apollo LEM docking drogue assembly between January 11, 1967 and February 15, 1967. The document contains various graphs, diagrams, and images pertaining to the tests.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45829">
                <text>North American Aviation, Incorporated. Space and Information Systems Division.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45830">
                <text>Apollo lunar experiment module</text>
              </elementText>
              <elementText elementTextId="45831">
                <text> Loads (Mechanics)</text>
              </elementText>
              <elementText elementTextId="45832">
                <text>Project Apollo (U.S.)</text>
              </elementText>
              <elementText elementTextId="45833">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="45834">
                <text> Spacecraft docking</text>
              </elementText>
              <elementText elementTextId="45835">
                <text>Static tests</text>
              </elementText>
              <elementText elementTextId="45836">
                <text>Towed bodies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="45837">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="45838">
                <text>Box 21, Folder 27</text>
              </elementText>
              <elementText elementTextId="206397">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45839">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45840">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="45841">
                <text>spc_stnv_000075_000118</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="45842">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17654</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="90148">
                <text>1967-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="90149">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="90150">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="90151">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="90152">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10411" public="1" featured="0">
    <fileContainer>
      <file fileId="9091">
        <src>https://digitalprojects.uah.edu/files/original/20/10411/Skywritermay2369_121310160336.pdf</src>
        <authentication>c9b809c5bff5f4dd2408b92c8983205c</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="156254">
                <text>Skywritermay2369_121310160336.pdf</text>
              </elementText>
              <elementText elementTextId="156255">
                <text>spc_stnv_000817</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156256">
                <text>"Apollo 10 crew ready for return from space."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156257">
                <text>News article detailing the Apollo 10 crew's preparations to return to Earth from lunar orbit.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156258">
                <text>Elliott, J. S.</text>
              </elementText>
              <elementText elementTextId="156259">
                <text>North American Rockwell Corporation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156260">
                <text>1969-05-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156261">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156262">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="156263">
                <text>Periodicals</text>
              </elementText>
              <elementText elementTextId="156264">
                <text>Aerospace industries</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156265">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="156266">
                <text>News Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="156267">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="156268">
                <text>Box 31, Folder 37</text>
              </elementText>
              <elementText elementTextId="210221">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156270">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156271">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="156272">
                <text>spc_stnv_000800_000824</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156273">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18120</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10412" public="1" featured="0">
    <fileContainer>
      <file fileId="9090">
        <src>https://digitalprojects.uah.edu/files/original/20/10412/Skywritermay969_121310160912.pdf</src>
        <authentication>6068df58b824f3de5c07c85af6c19d9a</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="156274">
                <text>Skywritermay969_121310160912.pdf</text>
              </elementText>
              <elementText elementTextId="156275">
                <text>spc_stnv_000818</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156276">
                <text>"Apollo 10 in spotlight as CDDT is completed."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156277">
                <text>News article detailing the attention Apollo 10 is getting after its successful countdown demonstration test (CDDT).</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156278">
                <text>Elliott, J. S.</text>
              </elementText>
              <elementText elementTextId="156279">
                <text>North American Rockwell Corporation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156280">
                <text>1969-05-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156281">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156282">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="156283">
                <text>Periodicals</text>
              </elementText>
              <elementText elementTextId="156284">
                <text>Aerospace industries</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156285">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="156286">
                <text>News Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="156287">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="156288">
                <text>Box 31, Folder 31</text>
              </elementText>
              <elementText elementTextId="210222">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156290">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156291">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="156292">
                <text>spc_stnv_000800_000824</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="156293">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18114</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
