<?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=4&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-12T22:05:00+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>4</pageNumber>
      <perPage>20</perPage>
      <totalResults>8242</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="11068" public="1" featured="0">
    <fileContainer>
      <file fileId="9558">
        <src>https://digitalprojects.uah.edu/files/original/20/11068/comparadvcoolingtech_071207135801.pdf</src>
        <authentication>aed6d60254d832a28574cea4645685fb</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="169238">
                <text>comparadvcoolingtech.pdf</text>
              </elementText>
              <elementText elementTextId="169239">
                <text>spc_stnv_000204</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169240">
                <text>"A Comparison of Advanced Cooling Techniques for Rocket Thrust Chambers".</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="169241">
                <text>1-65-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169242">
                <text>The document is a technical paper for Astronautics and Aerospace Engineering Magazine.The copy has handwritten notes that appear to be for revisions. The abstract states "In the early days of rocket propulsion, two primary methods were employed for cooling the walls of thrust chambers.  These were uncooled metal chambers where the heat sink capacity of the chamber and nozzle wall materials limited the operating duration, and regeneratively cooled chambers where one of the propellants was circulated in a cooling jacket which constituted the chamber wall.  Today, there are at least fourteen different methods with variations for cooling the combustion devices and nozzles of liquid propellant, solid propellant, and/or nuclear rocket propulsion engines.  It is the intent of this paper to examine these methods, to describe for each the useful range of operating conditions, as well as present and likely future applications, to define their limitations and associated problems.  Emphasis is primarily placed on liquid rocket engines."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169243">
                <text>Sutton, George P.</text>
              </elementText>
              <elementText elementTextId="169244">
                <text>Wagner, William R.</text>
              </elementText>
              <elementText elementTextId="169245">
                <text>Seader, J. D.</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="169246">
                <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="169247">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169248">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="169249">
                <text>Rocket engines</text>
              </elementText>
              <elementText elementTextId="169250">
                <text>Cooling</text>
              </elementText>
              <elementText elementTextId="169251">
                <text>Thrust chambers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169252">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="169253">
                <text>Essays</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="169254">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="169255">
                <text>Box 12, Folder 49</text>
              </elementText>
              <elementText elementTextId="210759">
                <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="169257">
                <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="169258">
                <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="169259">
                <text>spc_stnv_000200_000224</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="169260">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17066"&gt; View this item in ArchivesSpace &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1599" public="1" featured="0">
    <fileContainer>
      <file fileId="1572">
        <src>https://digitalprojects.uah.edu/files/original/78/1599/spc_horn_000087.pdf</src>
        <authentication>f1127dba270f437e1f27b5a6c711071f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="78">
      <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="32504">
                  <text>Helmut Horn Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="32505">
                  <text>Helmut Horn Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201613">
                  <text>Helmut Horn (June 24, 1912 to January 1, 1994) was a member of von Braun's Rocket Team.&#13;
&#13;
Helmut Horn earned an MS in engineering from the Institute of Technology, Darmstadt, in 1939. Shortly afterward, he began working at Peenemünde, where he stayed until 1945. He was brought over to Fort Bliss in United States on November 16 of the same year.&#13;
&#13;
Horn became a lecturer in Applied Mathematics at UAH in 1952. By 1965, he was employed at the Marshall Space Flight Center, and by 1969, he had become Assistant Director of the Aero-Astrodynamics Laboratory. "Later he served as deputy director of the Aero-Astrodynamics Laboratory" (Lundquist).&#13;
&#13;
Sources&#13;
&#13;
Lundquist, Charles. "Transplanted Rocket Pioneers," 2015.</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="205162">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/55"&gt;View the Helmut Horn 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="32555">
                <text>spc_horn_000087</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32556">
                <text>"A Comparison of an MIT Explicit Guidance Principle with MSFC Iterative Guidance."</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="32557">
                <text>Aero-Astrodynamics Internal Note 23-64</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32558">
                <text>From the summary: "Both [guidance] schemes steer toward a specified end point. The MIT scheme uses thrust to cancel out the effective gravity, a nonlinear term, which may be inefficient in certain cases. The MSFC scheme is more closely connected with calculus of variations and optimization theory in a reasonable degree of approximation."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32559">
                <text>Hart, Judson 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="32560">
                <text>1964-09-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="32561">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32562">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
              <elementText elementTextId="32563">
                <text>Massachusetts Institute of Technology</text>
              </elementText>
              <elementText elementTextId="32564">
                <text>Inertial guidance</text>
              </elementText>
              <elementText elementTextId="32565">
                <text>Spacecraft guidance</text>
              </elementText>
              <elementText elementTextId="32566">
                <text>Space flight</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32731">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="32732">
                <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="32733">
                <text>Helmut Horn Collection</text>
              </elementText>
              <elementText elementTextId="32734">
                <text>Box 1, Folder 2</text>
              </elementText>
              <elementText elementTextId="206252">
                <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="32736">
                <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="32737">
                <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="32738">
                <text>spc_horn_2020_04</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11158" public="1" featured="0">
    <fileContainer>
      <file fileId="9715">
        <src>https://digitalprojects.uah.edu/files/original/20/11158/compflowcont.pdf.pdf</src>
        <authentication>20bd0806b47e4b5378e9774a6b2f4d14</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="171116">
                <text>compflowcont.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171117">
                <text>"A comparison of four control systems proposed for Saturn V launch vehicles."</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="171118">
                <text>X-53572</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171119">
                <text>Presented are the results of a study comparing four proposed control systems for the first stage flight of Saturn V launch vehicles.  The primary basis of comparison is the effect on structural loads, using the bending moments at three stations as load indicators. Two of the systems sense only the vehicle attitude and attitude rate, while the other two systems also sense the lateral acceleration.  A yaw plane wind response analysis, including rigid body translation, rigid body rotation, four bending modes, five slosh modes, and a non ideal control  system, was performed. The winds used in the study were the Marshall synthetic profile and three selected Jimsphere-measured real wind profiles. Load relief obtained from the addition of accelerometer feedback in the control loop amounted to about 10 percent at maximum bending moment station. In view of predicted structural capabilities of the vehicle, this reduction in loads was not considered sufficient to offset the added complexity and the slight reduction in rigid body stability .</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171120">
                <text>Sumrall, Phil</text>
              </elementText>
              <elementText elementTextId="171121">
                <text>George C. Marshall Space Flight Center. Aero-Astrodynamics Laboratory</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="171122">
                <text>1967-02-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="171123">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171124">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="171125">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="171126">
                <text>Saturn 5 launch vehicles</text>
              </elementText>
              <elementText elementTextId="171127">
                <text>Testing</text>
              </elementText>
              <elementText elementTextId="171128">
                <text>Spacecraft control</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171129">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="171130">
                <text>Essays</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="171131">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="171132">
                <text>Box 20, Folder 36</text>
              </elementText>
              <elementText elementTextId="210848">
                <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="171134">
                <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="171135">
                <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="171136">
                <text>spc_stnv_000200_000224</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="171137">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17619"&gt; View this item in ArchivesSpace&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11153" public="1" featured="0">
    <fileContainer>
      <file fileId="9720">
        <src>https://digitalprojects.uah.edu/files/original/20/11153/Decaofspacprog.pdf.pdf</src>
        <authentication>e7f7b59fd4603f5127b2a0b6e63a5512</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="171018">
                <text>Decaofspacprog.pdf</text>
              </elementText>
              <elementText elementTextId="171019">
                <text>spc_stnv_000226</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171020">
                <text>"A decade of space progress, 1958 to 1968: General Electric Missile and Space Division offers a pictorial tribute to the National Aeronautics and Space Administration."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171021">
                <text>Excerpt from &lt;i&gt;G.E. Challenge&lt;/i&gt;, Fall (Sept.) 1968, pages 13 to 25.</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="171022">
                <text>1960-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="171023">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171024">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="171025">
                <text>Manned space flight</text>
              </elementText>
              <elementText elementTextId="171026">
                <text>Space flight</text>
              </elementText>
              <elementText elementTextId="171027">
                <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="171028">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="171029">
                <text>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="171030">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="171031">
                <text>Box 28, Folder 5</text>
              </elementText>
              <elementText elementTextId="210843">
                <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="171033">
                <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="171034">
                <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="171035">
                <text>spc_stnv_000225_000249</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="171036">
                <text>&lt;a href=" http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17947 "&gt; View this item in ArchivesSpace &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="182572">
                <text>General Electric Company</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11045" public="1" featured="0">
    <fileContainer>
      <file fileId="9674">
        <src>https://digitalprojects.uah.edu/files/original/20/11045/descst124m.pdf.pdf</src>
        <authentication>12f223234438dcb6a4da383a09f1224b</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="168738">
                <text>descst124m.pdf NO ADDITIONAL FILE - SAME AS BELOW RECORD</text>
              </elementText>
              <elementText elementTextId="168739">
                <text>spc_stnv_000230</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168740">
                <text>"A Description of the ST 124-M Inertial Stabilized Platform and its Application to the Saturn V Launch Vehicle."</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="168741">
                <text>7511-64-R11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168742">
                <text>This report is a description of the ST124-M inertial stabilized platform system and its application to the Saturn V launch vehicle.  It is a summary report providing the system concept and not a theoretical presentation.  Mathematical equations were included only where necessary to describe the equipment; however, the detail derivations supporting these equations were not presented since this was not the theme of the paper.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168743">
                <text>O'Connor, B. J.</text>
              </elementText>
              <elementText elementTextId="168744">
                <text>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="168745">
                <text>1964-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="168746">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168747">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="168748">
                <text>Inertial platform</text>
              </elementText>
              <elementText elementTextId="168749">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="168750">
                <text>Inertial guidance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168751">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="168752">
                <text>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="168753">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="168754">
                <text>Box 11, Folder 27</text>
              </elementText>
              <elementText elementTextId="210736">
                <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="168756">
                <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="168757">
                <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="168758">
                <text>spc_stnv_000225_000249</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="168759">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16992"&gt; View this item in ArchivesSpace &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11155" public="1" featured="0">
    <fileContainer>
      <file fileId="9718">
        <src>https://digitalprojects.uah.edu/files/original/20/11155/descst124minerstab.pdf.pdf</src>
        <authentication>498c9649b1614c1582ca1dff9290294c</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="171058">
                <text>descst124minerstab.pdf</text>
              </elementText>
              <elementText elementTextId="171059">
                <text>spc_stnv_000231</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171060">
                <text>"A description of the ST-124M inertial stabilized platform and its application to the Saturn V launch vehicle."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171061">
                <text>This report is a description of the ST-124M inertial stabilized platform system and its application to the Saturn V launch vehicle.  It is a summary report providing the system concept, and not a theoretical presentation.  Mathematical equations were included only where necessary to describe the equipment;  however, the detailed derivations supporting these equations were not presented since this was not the theme of the paper.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171062">
                <text>O'Connor, B. 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="171063">
                <text>1964-06-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="171064">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171065">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="171066">
                <text>Inertial guidance</text>
              </elementText>
              <elementText elementTextId="171067">
                <text>Inertial platform</text>
              </elementText>
              <elementText elementTextId="171068">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="171069">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="171070">
                <text>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="171071">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="171072">
                <text>Box 11, Folder 38</text>
              </elementText>
              <elementText elementTextId="210845">
                <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="171074">
                <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="171075">
                <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="171076">
                <text>spc_stnv_000225_000249</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="171077">
                <text>&lt;a href=" http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17003"&gt; View this item in ArchivesSpace &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="981" public="1" featured="0">
    <fileContainer>
      <file fileId="822">
        <src>https://digitalprojects.uah.edu/files/original/20/981/spc_stnv_000034.pdf</src>
        <authentication>69f79604363ff3e971b9fd365d1f7444</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177209">
                    <text>//

*'

A DISCUSSION

OF THE LUNAR LANDING PROBLEM

F r e d E, Digesu

As trionic s Division
Marshall Space Flight Center, NASA
Huntsville , Alabama

To be presented at the
AIAA Guidance % Control Conference

Massachusetts Institute of Technoi-3gy
Cambridge, Massachusetts
f ~ u ~ u s12
t - 14, 1963\

�A DISCUSSION OF THE LUNAR LANDING P R O B L E M

Serious talk concerning placing srsrnet5ing 01-1 the moo2 beg2.n
same s i x to eight years ago with an A", F a r c e 71hqrdlanding" project
b a s e d u p o n a Thur missile f i r s t stage. The landing g e a r of this probe
w a s a metal spike which was to be driven E ~ t ot 5 e lunar surface, and
t b e designation "hardlanding" was qu'L',e ~ppro7rtatefop t h e anticipated impact shock of s e v e r a l hundred g - a v f t i ~ s . B e c a u s e of limited
payload capability the concept was, of nsceseity, v e r y simple. A
direct ascent ballistic injection w a s envisaged with the yayloa d stage
spun u p to stabilize it in an inertially -fixed o m - i e ~ t a t b immediately
n
after injection. The inertial direction wa,z ',?ken such that t%e spike
would be parallel to the lunar local vertical at !mpzct. SEiortly before
impact, a retrorocket, ignited by timer, wag to remove the major
portion of t h e descent velocity. Error ana.lyse:le 2,nd assessment of
the probability of impact with no possibility for midcour a e correction
showed that "fly-by" would be the mere e x r e d i e ~ method
t
of e x p r e s s k g
the mission abj ectives. Indeed, similar p - o y o s z !..+ by t h e Army based
upon a Jupiter missile first stage claimed cnly E near miss possibility.
T h e s e studies and proposals bore f r u i t in the Pir.dqeer s e r i e s of lunar
probes, which, despite their enfcrc ed adberenc e ?r&gt;simplicity and thus
its inherent high reliability, met with ratlcer lirnLted success.

W e are still talking about landing on t h e mcc-I and while the overwhelming concensus is that it is well within the state of the art, somehow we haven't quite a.ccomplished the f.12 t a5 y e t .

So when I say "state of the a r t " wkat. E r e a ily mean t s lT3tateof
the study'? since we have yet to demonr;t;ra.te f r n ,=.!.l
ity
f! with a piece of
hardware,

�Studies now exist, t o varying d e g r e e s of depth, for many modes of
l u n a r landing. A s i d e from the Atlas -Agena boosted Ranger and the
A t l a s -Centaur boosted S u r v e y o r , the interest in these s t u d i e s seems to
be centered around the Saturn boosted class of vehicles, the Apollo
mission, and the various unrna.nraed Ixnders ~ ~ o p o s easd s u p p o r t of and
to augment such landings. Thus w e a r e begicr~ingt o look at lunar
payload capabilities of t 5 e 3 t o 4 thousznd Ibs of t h e Saturn I B , the
L E M t r u c k capability of from 6 to 8 thousand I b s . , and the Saturn V
Lunar Logistic vehicle capability of 2rour.d 31! t:"louse.ndr: Ibs . on the
rncon. Of course, landed pa ylo2.d weight w o u l d ~ r c b a b l ynot be a fzix
way to d e s c r i b e the lunar excursion modu1.e in t\r! Ano!lo mode, but
the total L E M weight of around 2 5 t;housand pound..; is typical of tl?e
class of landers with which these s t u d i ~ zd e a l .

.

H e r e then, i s the real break-through. W e a y e coming to the
paint where we have the weight lifting capability for the i n s t r u m e n t a tion and the power supplies needed f o r a somewIlat m o r e cornfortable
design margin f o r the mission r e q u i r e m e n t s . The c e e d f o r microminiturizatiwn and minute power r,or,sumptiox is no longer acute and
can he traded far r e l i a b i l i t y , longer rar_g.=,arid firwif.~ra c r u r ? , ry,
Of c o u r s e , this pre-supposes the d e v ~ l o p m e z tof fuel rel1.s t o s u p ~ l y
this power and it could well be s a i d t5at this is a pzcing item. Parenf.hetical2y I might mention that the developmert of radio-isotope power
supplies ma.y well be the pacing item for int;e-t.::;~.nzt;.,sy m i s . s i a n ~ .
It is difficult to place the l a n d e ~ r 3into b:::,?s: cat cgcries other than
the obvious one of manned and u n r n a n ~ e d . However, suSdivi5ions caxl
be made under these two categories Z.-i a ~ a u g h l y~ a . r z 1 3ed manner,
These subdivisions would be along the I l s e : ~c f tk:e c.;"+rationa,l requirements a ~ the
d apriori knowledge as signed t o tv:e i n ~ . f ~ u m e ntion..
ta
W h i l e no s i n g l e factor in itself determiner, t17e c~ve?x!I system, its
components a n d degree of complexity c8.n 5 e nl-rlwn t n be influenced
s t r o n g l y by:
a.) The proposed flight profile
b) The location at whickr the nzvig~.bir&gt;nalfunction is ~ e r f o r r n e d
(an bozr d or on ground)

�c J The constraints upon the vehicle velocity at lunar touchdowa
d ) The d e s i r e d versatility in landing site selection
3 ) The d e s i r e d location accuracy in t h e landing
It will be found that g e n e r a l l y the manned missions wi1.1 contain the
m o r e complete and extensive s e t of equipments. T h i s a t e m s from the
fact that

I ) Man has a g r e a t e r capability f o r reliability using a larger
variety of ins trnrnentation, and
2 ) The tendency is to l e a n tow2rd making ths manned vehicle a:$
self sufficient as is possible.
In pursuing these points, consider the block diagram of F i g u r e 1
which is general enough t o apply to any mission. Indeed, it contains
the elements for any form of guidance since it is capable of either
dead-r eckoning o r of positioning navigation. The trade -off in the
various subdivisions cited previously will determine the degree of
completeness of the block diagram f o a3y
~ specffic mission, .7.s w e l l
a.s the componexlt complexity and charact~,r!~t:,cs.
First consider the flight profile. At earth's end, it is customary
to use a parking orbit of f r o m up t o several o r b i t s far A70110 d o w n t~
one o r b i t or less f o x unmanned miasions such a s R a n g e r , Surveyor,
cr t h Saturn
~
V Lunar Logistic vehicle. P u r e i n e r t i d injection h a s
b e e n shown to be well within the midcourse ca~rection'vel.ocitybudget
for t h e one orbit or l e s s c a s e s , I whereas updating of the inertial
system by nnboard or ground bxs ed tracking may ba r e q u i r e d fox the
longer orbital stay times.

At t h e lunar end, the approach to the landing s i t e can be either
direct as in the Ranger and the Surveyor, or through ~ p ' S ? i3.3
t in the
A20110 a.nd the Lunar Logistic vehicle,

In reviewing the implementation of these missions profiles, it
b e c o m e s clear that the key factor in t h e design of the guidance equipment is location (on the vehicle or on t h e ground) of the t h r e e
guidance functions of:

�1. Navigation (that is, the determination of the vehicle positionvelocity state vector)
2 . Computation of the r e q u i r e d maneuver to r e a c h the desired

final state vector
3. Supervision and measurement of the c5enge in the vehicle
state vector throughout the maneuver.

The time in which each of t h e s e functions must be performed is a
f o u r t h and heavily influencing factor upon the guidasce hardware.
It is with the midcourse phase of t h e lunar t r n n s i - t that we begin
clur review since this paper is concerned with t h e guidance problems
confronting the spacecraft.

For a ground-based navigational s y s t e m , items 1 and 2 a r e e a r t h based while i t e m 3 remains as an onboard function. A functional
diagram of such a system i s illustrated in Figure 2 .
Two angles, rela.tive range and/cr rznge rzte, a r e measured t o t h e
spacecraft. Computations on these measured qulintities determine
s p x e c r a f t position and velocity. Prediction of t 5 e future s t a t e of the
vehicle is obtained by solving the equations of motion. Computations of the required maneuver to meet d e s i r e d end conditions of velocity and position a r e m a d e and t r a n s m i t t e d t o t h e spacecraft f o r execution. Onboard i n e r t i a l equipment super-vises and measures the
maneuver.

This concept I e a d s to the greatest simplificatien of t h e onboard
system. It is only necessary that t h e r e be a. kcown m i e n t a t i o n of the
guidance coordinates aboard the vehicle. S h r t t e r m (in the o r d e r of
minutes or hours) stabilization of these a x ~ siz don- by gyroscppes;
however, since gyroscopes a r e subject to random d r i f t s (to a g r e a t e r
or l e s s e r d e g r e e , depending u p n the quality of the g y r o ) , long t e r m
(in the order of days) stabilizatioxl of the guidiance coordinate a x i s is
done by optical means. The optical
devices deptcted in the block diag r a m of Figure 1 s e r v e t o supervise the a l i g n m e ~ tof the inertia.]
j.nstrumentation, but this is a unique function f o r tSe ground-bas ed

�navigation s c h e m e we are discussing. The onboard computer in such
a system can be a relatively simple device, consisting of little m o r e
than a program s e q u e n c e r ,
Most c e r t a i n l y capable of doing the e a r t h - b a s e d tracking and
cavigation 505 a r e thq stations of the Deep Space I ~ ~ t r u m e n f - , z t i o a
Facility of the J e t P r o p u l s i o n ~ a b o r a t o r ~ . 'Tte6e a r e ins?zl!ations
located at 120 d e g r e e i n t e r v a l s a r o u n d the w o ~ l din Goldstone, California, Woomera, Australia, and Johanneahurg, Sout? Africa; each
,s ta,tion t ~ a c kwith an 85-foot dish antenna an4 wit;$ a quoted a n g l e
t r a c k i n g accuracy of 0.01. to 0.02 d e g r e e s , a ?Erg? r a t e accuracy in
the o r d e r of
0.2 m/s, and a ranging a c c u r a c y cf f30 m e t e r s , when
incas-porated.

*

The concept of onboard navigation places a much stiffer r e q u i r e ment upon the guidance Instrumentation. Along with supervising t ? ~
mientation of the i n e r t i a l measur ernent unit, the optical devices
must p e r f o r m the additional duties of mea.surtng a n g l q s and distances
cf c e l e s t i a l bodies. The guidance computer m u s t r e r f o r m the f u q c tions of computing position from th.-s e rnea.:.rilred q u a z t i t i e s , ~ r e d i c t i n g
t h e l a t e r s t a t e vector, and calculating t h mar?.t?uver r e q u i r e d to meet
d e s i r e d end conditions,

F o r the m i d c o u r s e phase, the m e a s u r e r n e n t ~a r e all angular measurements ( d i s t a n c e must be taken by a tadinmetric measurernenta
since u s e of onboard radar ranging is prohib;.ttve in power r e q u i r e d ) ,
and the long distances involved a c t t o give l a r g e po3ition uncertainties
£ O P even small angular measurement e r r or. HQWever, a rriitigxting
c i r c u m s t a n c e is that the times i ~ v o l v e dare 30r4 6 0 that a. n u m b e r nf
measurements can be made and the data i r ~ m
t h e s e can be at?-tistical ly pxoces s e d ("'smoothed") to give smaller pos it!.on uncertain tie^
T h e r e a r e mamy smoothing techniques d i s c u s s e d in t % e 1litera.ture, s u c h
as c u r v e fitting by least squares, weighted l e a s t squares, minimum
variance, a n d the Schmidt- Kalrnan technique3 nf o?tirnal f i l t e r i n g

.

.

4.

This l a t t e r technique with work by Batti?, w'here he d e r i v e s
the optimum plane in which to make the measurement and where each

�can be a single m e a s u r e m e n t , is the onboard midcourse navigation
s c h e m e planned for Apollo. To e a s e t h e load on the airborne computer,
l i n e a r i z e d forms of t h e nonlinear motion equations and the measurem e n t c o o r d i n a t e s are i m p l e m e n t e d by using the first order terms of a
Taylor series expansion about a reference t r a j e c t c z - y .

- -

For example,'the equations used f o r predicting future state,

f r o m present s t a t +e ,

,I:[

takes t h e form: 5

A4
W h e r e t h e Ai are 3 x 3 s u b m a t r i c e s of partial derivatives evaluated
along t h e r e f e r e n c e t r a j e c t o r y . At lunar end, the planned a p p r o a c h e s
t o the landing s i t e ( d i r e c t o r through o r b i t l , the t h r u s t t o weight r a t i o
of the spacecraft, a n d the accuracy with which the end points m u s t be
met influence the system characteristics. M e a s u r e m e n t s from t h e
spacecraft t o the lunar target become mandatory t o determine it:,
relative position and velocity t o within a c c u r a . e i e s r e q u i r e d by cons t r a i n t s upon t h e t r a j e c t o r y endpoints. F o r the Ranger d i r e c t c a s e ,
where a h a r d landing is permissible, w h e r e t h e direction of t h e
velocity vector at touchdown is allowed to deviate 5 y 4 5 degrees f r o m
the vertical, and w h e r e no specification SF; made ur,on t h e l o c a t i o n of the
landing s i t e , the landing s e n s o r is a radar p r o x i m i t y fuse. H o w e v e r ,
even in this case, the dispersion volume a t r e t s o ignition r e q u i r e s that
a.t least one m i d c o u r s e guidance c o ~ r e c t i o nbe made. For t h e soft
landing Surveyor, the c o n s t r a i n t upon t h e direction of the velocity v e c t o r
at touchdown r e q u i r e s determina.tion of all cornponerzta of t h e velccity
vector relative to t h e lunar s u r f a x e as an additinna.1 meaqurement.
The flight profile for the landing t l r o u g h lunar orbit is shown in
F i g u r e 3 . F i r s t t h e r e is t h e brake t o lunar. orbit, then a d e s c e n t kick,
an approach braking, a v e r n i e r , a hover (for FL manned Apollo L F M ) ,
and the touchdown.

�The brake to lunar orbit will usually be a long burn during which
pitch s t e e r i n g according t o some guidance law m u s t be performed. Studies show6 that it is possible t o control the plane of the lunar
orbit b y choice of the trans it injection parameters at e a r t h end; thus
a large plane change will probably not be 2. requirement on the lu3ar
o r b i t b r a k e maneuver. Prior t o the braking burn, alignment of the onboard i n e r t i a l equipment f o r supervising the maneuver m u s t be done
with reference t o a lunar -fixed coordinate s y s t e m . This can be done
directly with a lunar horizon s e n s o r o r indirectly with a s u n and stzr
s e n s o r and a knowledge of the reIative position of the spacecraft and
moon. The accuracy with which the brake lo lunar orbit must be
accomplished is dictated by the altitude at which this orbit is to be
established. Navigational and execution inaccuracies will c a u s e a
decrease in peris elenurn altitude. The accuracy required of the xlavigztional s y s t e m can be inferred from the fact that initial condition
e r r o r s at the beginning of the brake of 1 m/s in velocity, or of 0. 1 5
d e g r e e s i n the velocity direction, o r of 1 km in altitude would
each lead t o an ellipse with a n altitude error of 5 k m at periselenurn
over a desired 185 krn c i r c u l a r orbit.
O n c e the spacecraft is in orbit, naviga.tior_ must be done to establ i s h its ephemeris relative to the lunar coordinate s y s t e m . The s a m e
techniques u s e d for midcourse can be used h e r e , with the same
implications in the hardware.
Descent from lunar o r b i t is accomplished i2 a n u m b e r of ways.
T h e r e v a r y from a descent kick which puts the ~ p a . c e c r a f into
t
a
Hohrnann t r a n s f e r , with approach braking initiated at p e r i a p s i . ~ ,t o t h e
Apollo L E M descent kick into the equi-period ell i p s e , with approach
braking a l s o initiated a t periapsis, to a conti~.uousburr:. down f r o m
the parking orbit.

In Figure 4 are plotted some representative landing t,rajectories
f o r the Saturn V Lunar Logistic vehicle and f o r the Apclllo L E M , t h e
1ower altitudes being the periaps e s of the previously mentioned descent
ellipses. It is well t o note h o w initial thrust to weight r a t i o , F/WQ,
affects the r e q u i r e d m e a s u r i n g range (the lower the F / w ~ ,the g r e a t e r the
distance of the ignition paint).

�The F/WO and t h e altitude can combine s o that the landing point is
out of sight below the horizon at ignition. If this is the case the ignition point m u s t be determined by navigational methods which have been
discussed previously, but which s u f f e r from the fact that t h e vehicle
state vector r e l a t i v e to the landing site must b e a r r i v e d at through
indirect measurements and eornputation~. The i ~ a u h
e e r e i z whether:
a ) The landing m u s t be a soft one on a smooth a r e a within a
relatively small radius of a specific loca.ticrx, or
b ) The landing m u s t be a soft one cn a smooth area but the
touchdown location is relatively immat.eria1.

The first case is a two point bounda.ry value ~ r o b l e mthat has a
unique solution for the case of minimum fuel. Errors in knowledge of
the initial conditions l e a d t o w a r d over expenditure of fuel. Since
surface d i s t a n c e t r a v e l e d is not a dependent quaqtity in t h e second c a s e ,
the requirement upon the na.vigation syn tern is c o y r e ~ p o n d i n g l yeased.

In Figure 5 a r e plotted s o m e of t h e n a . v i g a t i o ~ a lstate parameters
of the vehicle relative to a specific landing point f o the
~ a9prnaeh
braking trajectories g i v e n in F i g u r e 4. Methcds for Implementing
these measurements range from radar tracking of a beacon a t the
t o doppler aided television or optical sightings of
point in
the landing point from the vehicle,
Once the components of the vehicle relative s t a t e vector are
determined, the guidance function of computation of the t h r u s t m a n euver t o meet desired end points must be done. Here a.gain we czn
find a wealth of material on the ~ u b j e a t p ,in t h e l i t e s a t u r e . This i~
called the "guidance logic" and u s u a l l y takes the fcrm of a functional
r e l a t i o n s h i p t o be maintained between t h e vehicle s t a t e v e c t o r a n d t%e
direction a n d magnitude of the t h r u s t vector. TI-:&lt;;.
guidxnc.e logic
relationship i s usually derived from the p o i n t of view of constraining
the vehicle to some "minimum energy" p-7 th for t h e d e s c e n t . The
computational p r o c e s s e s r e q u i r e d r ~ x ~ g
from
e
exylic:t solutfon cf the
equations of motion (sometimes in linearized farm) t o a. simple
comparison and enforcement of the measured t ~ z j e l = t o r ydata t o conf o r m to p r e e t o r e d data for a precomjmted standikrd descent.

�The type and processing of the m e a s u r e d data., the computer
carnplexity, and the fuel expenditure in reaching desired end conditians
from perturbed initial conditions all enter into the arguments in the
implementation of this phase of the trajectory.

The v e r n i e r , h o v e r , and touchdown part of the lazding profile will
now be b r i e f l y discussed.
The purpose of these phase^ ir; t o in:iure ;i ,;oft and stable landing
on a smooth l u n a r surface. The definiticn of "emcrotEaM is usually
obtained after a lively discussion between the vehicle: de,&lt;i g n e r , the
propulsion people, and the guidance sy3tem e n ~ i n n e r ,with ~ e r h a p sa
l u n a r surface "expert" included to make t h e s u b j e c t e v e n more
interesting.

It is readily apparent-that the sinking velocity a t touchdown
directly influences the a i z : ~ of the landing gear. Engine throttle ability
becomes a requirement for a very soft toucFldown or % hover capability,
the throttle range being a function of the velocity d i p i ~ e r ~ i o r ,at
:3 vern?er
altitude, the v e r n i e r guidance fogir, ar.d the 3p7i;lir a f t ma 3 5
touch-.
down.
It is found, however, that vehicle staSi1:ty (i. e . , r e s i s t a n c e to
toppling) i s a c r i t i c a l factor for t h e l a r g e r s &gt; a c e c r ?3. Tho stability
cf the vehicle a t lunar touchdown is a functia? of t h e lzgding p e a r
s p r e a d and the induced ti2ping moment.
Thi,q t i p ~ i n gmoment resuZ t s from su?fa,:e roughne 5 rj (toul d e r a,
craters, e t c . ), the slope of the r u r f a r e , the :lur-E7s.c-e friction, a n d the
vehicle l a t e r a l velocity at touchdown. Loweriag the vehicle center of
gravity increa.3 e s vehicle stability, but unfortunately t5is a l o has the
effect of decreasing the engine swivel con,rcl ziomer,t a r m .

T h e r e i s thus a definite lower limit f o r the c m t e r of gravity
position. Increasing the landing g:ay s ~ r e a bd. ~ ' , n p?; on packaging,
manipulation (extens ion, e tc. 1, a ~ weigkt
d
~ ? c t ? e m ; : : . Deer ea,sing the
landing l a t e r a l velocity dispersion ircrea:&gt;e z the dernaad;.; upon the
m e a s u r e m e n t of this quantity. 7

�A proposed solution to this m e a s u r e m e n t p r o b l e m is the u s e of a
3 b e a m doppler radar velocity sensor a s shown i n F i g u r e 6. An unknown in t h i s solution is the lunar dust effect. T h e altitude at which
the dust cloud r a i s e d by the engine begins to render radar ineffective
is open t o c o n t r o v e r s y , but certainly it i.5 sornet:eLing ot3.e;. th3.n z e r o .
Thus the actual landing will be done on i ~ e r t i a m
l e m o r y with initial
conditions s e t into the i n e r t i a l equipment from the last r ~ . d a rfix.
R a d a r e r r o r s enter a s initial condition e r r c r s into the i n e r t i a l equipment. Since these e r r o r s thus become time function:, the higher the
East radar fix, the m o r e the dead recknnicg e r r c : a c c r u e m e n t , and the
greater the touchdown dispe-rsion.
Obstacle identification and avoidance during d e s c e n t b e c o m e s a
requirement if a landing at s o m e unexplored location :s d e s i r e d .
Inclusion of television in the guidance is offered E;- a s o l u t i n n t o t5is
problem. The television loop could be c l o ~ e deit5er directly on the
vehicle o r through an earth cornrnunicationa link.

Consideration of l u n a r ascent z ~ l de r t h z e t u r n i ? , for the
moment, of i n t e r e s t only in t h e m a a n ~ dl u n a r l i + ~ A i n g. = w e ,tlzrzt i,;,
i n t h e Apollo m i s s i o n . H e r e the additional functiors cf lunar o-Sit
rendezvous and earth r e -entry m u s t be d e s i g n e e into the gutda.nce
system. Earth return from l u n a r landing is e a s i l y a, subject f o r
another paper and will not be t r e a t e d h e r e .

�REFERENCES

1.

N e i g h b o r s , A l i c e K . ; Cole, John W . : a n d D a n i ~ 1 ,Fred: ' E r r o r
Analysis of Saturn Guidance Hardware a x Applied to a Lunar
Mission, " N A S A ( M S F C ) MTP-ASTR-A-63 - 4 , M a r c h 13, 1963. ( C )

2.

Noton, Cutting, and Barnes: "Analysis of Ra:"io C o m m a n d MidC o u r s e Guidance,
J P L Technical Memo N o . 32 -25. September 8,
1960.

3.

S m i t h , G e r a l d L . , Schmidt, Stanley F., and M c C e e , L e o n a r d A . :
tlApplication of S t a t i s t i c a l Filter Theory t o t h e Optimal Es timation of P o s i t i o n and Velocity qn Board a Circumlunar Vehicle, ' I
NASA TR R-135, October 9 , 1962.

4.

B a t t i n , Richard H. : "A Statistical Optimizing Navigation P r o c e dure for Space Flight, I ' Massachusetts f ~ s t i t u t eof Technology,
ARS NO. 2461 - 6 2 .

5. McLean, John D. , S c h m i d t , Stanley F . , and McGee, Leonard A . :
"Optimal F i l t e r i n g and Linear P r e d i c t i o n Applied to a Midcour s e
Navigation S y s t e m for the Circumlunar M i ; q ~ i o n", NASA T N D- 12C8,
M a r c h 15. 1962.

6.

Hoelker, R . F. and B r a u d , N. J. : "Survey and Classification of
E a r t h - M o o n T r a j e c t o r i e s Based on Newly Dtqcovered P r c p e r t i e ~ ",
NASA (MSFC) MTP-AERO-63-39, M a y 2 0 , 1963.

7.

Marshall Space F l i g h t Center: " L u n a r Logistic System,
(MSFC) MTP-M-63-1, March 15, 1963.

NASA

�.,, ,.,..- . _ . .- = , . ._ ,.,...:.

...*

.

I

.

:

.

.,

.,

.

,

,, ,

,- .

,

.

,

.

, ,,

I

, .,

������</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="17689">
                <text>spc_stnv_000034</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17690">
                <text>"A Discussion of the Lunar Landing Problem."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17691">
                <text>Digesu worked in the Astrionics Division of MSFC. This paper was presented at the AIAA Guidance &amp; Control Conference, Massachusetts Institute of Technology, Cambridge, Massachusetts, August 12-14, 1963.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17692">
                <text>Digesu, Fred E.</text>
              </elementText>
              <elementText elementTextId="17693">
                <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="17694">
                <text>1963-08-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="17695">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17696">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="17697">
                <text>Space flight to the moon</text>
              </elementText>
              <elementText elementTextId="17698">
                <text>Lunar landing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17699">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="17700">
                <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="17701">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="17702">
                <text>Box 9, Folder 25</text>
              </elementText>
              <elementText elementTextId="205743">
                <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="17704">
                <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="17705">
                <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="17706">
                <text>spc_stnv_000027_000050</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13856" public="1" featured="0">
    <fileContainer>
      <file fileId="10377">
        <src>https://digitalprojects.uah.edu/files/original/193/13856/Defense_Billboard_60_001.pdf</src>
        <authentication>8a50c07b8d2e00fc8da3e6c4387ed495</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197434">
                    <text>�</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="196632">
                <text>Defense_Billboard_60</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196633">
                <text>"A DWI Conviction Can Bring a Social Life to a Screeching Halt...But It's a Great Way to Save Lives"</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="196634">
                <text>D2.9:D36/2/No.60</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196635">
                <text>Bike parked in parking lot with man visible through window</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196636">
                <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="196637">
                <text>1993-02-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="196638">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196639">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="196640">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="196641">
                <text>Drunk driving</text>
              </elementText>
              <elementText elementTextId="196642">
                <text>Bicycles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196643">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="196644">
                <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="196645">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="196646">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="196647">
                <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="196648">
                <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="196649">
                <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="196650">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8496" public="1" featured="0">
    <fileContainer>
      <file fileId="7414">
        <src>https://digitalprojects.uah.edu/files/original/125/8496/r04c04-03.pdf</src>
        <authentication>da84b5bd8342bc6800f62f4311e8e6b6</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="137731">
                <text>r04c04-03</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="137732">
                <text>Series 4, Subseries C, Box 4, Folder 3</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137733">
                <text>"A Future for Virginia's Past" by the Virginia Department of Historical Resources, 1988</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="137734">
                <text>r04c-211007</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1138" public="1" featured="0">
    <fileContainer>
      <file fileId="985">
        <src>https://digitalprojects.uah.edu/files/original/20/1138/spc_stnv_000054.pdf</src>
        <authentication>2c71d16aefa23ff5b7d8c14e3e4197de</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177272">
                    <text>PRESENTED AT TtiE FOURTII INTERNhTlONAL CONFEREI!CE ON FLU!D SEALING HELD I N CONJUNCTION WITH ~ M ~ . 2 4AS1.E
t h AlJNUAL MEETING
IN PIIILE.DELPII!A, MAY 5-9.1969: This paper is thc literary prcpcrty of t l ~ eSociety indicated on the first page. Thc press may summarize frecly from
this manuscript after presentation, citing source; however, publicstion of material constituting more than 2006 of tile manuscript shall bc construed as
a violation of t l ~ cSoricty's rights and subject to appro2riatc I g a l actiori. Manuscripts not to be published by thc Society will bc releascd,in wri!irig for
'publica:lon by otlicr sources. Statcxcnts and opiriions advanced in papcrs arc uridcrstood to be individual expressions of tho author(s) arid not those
'
of t3e Scciety.

AVAILABLE. FROFA: AMEltiCAN SOCIEl-Y OF LUCRICATION CNCINECRS. 838 DUSSE tIICIl\'~A\', PARK ItIDGE, ILl.li&lt;OlS COOGC

�MfALTER J. CIESLII:
Pesco Products, Gedford, Ohio

Tlzc object o j t1z.c leaorit clisctissccl in this yapcr was to
dceelop a rclinblc helitrtn. 60.9 sllnjt scal for rise in an
electric motor-driool, licitlid osygeiz pump on a space
uellicle. Tllc dcvclo~~mcnt
e.orl coocred tests on ttco
basically diflerent jnce scal designs, one raith an atfncllecl
carbon jacc and ille olllcr tvitll o floating lal,$fted carbon jaca Scocral tclloi~stiibration da~npingcleviccs orlcl
unriotrs seal material coinbitzafioru tacre in ticsf iga fcd.

.

hcliuili seal for use in an eIcctric motor driven liquid
oxygcn pump for a n~anncclspacevchicle was tllc objective
of tliis investigation.
PUfAP DESIGN

Elcctric motel--driven, liquid oxygen pumps can be
dcsigndd. with a floodccl, canncd, or scalccl motor. Shaft
scals arc not required in the first t\vo typcs of units, but
oiic or more arc ncccssary with tllc scalcd type motor.
Tlic lattcr type of unit is discussed llcrc togctllcr with
thc tcst work concluclcd in developing a satisfactory
sllah scd.
From the clcsign stanclpoint, thc flooded motor unit is
t l ~ clnost sinlplc. All motor cotnpo~lcnts opcrate in
dircct coritact \\pith the punipccl fluicl and no seals are
rcquirccl. But, from a safcty standpoint; this dcsign could
bc thc most hazardous. IVhilc all matcrials arc sclcctccl
for compatibility \vitll liquicl oxygct~,co~libi.lstionis still
possiblc undcr ccrlaiti conclitiol~s.For instance, in a
si~nulatcdshort circuit test of a motor stator siibmcrgccl
in liquid oxygen, the electrical iiisulalion, part of the
colq~crwindings,'and iron stator Inminations were burncd
away, as slio\vn in Fig. 1. Coinbustion of thcsc matcrials
was tcrniinatccl only wlicn tlic supply of oxygcn was
exhaustccl.
.:
In thc canmcl rtlotor dcsign, usually only thc stator
laininations, windings ancl lcads arc hcrmctically scalcd
witliin a stainless-stccl slicll, thiis l&gt;rcvcntingdircct contact with tlic liquicl osygcn. 111c rotor, howcvcr, is
nor~nallystill submcrgccl clircctly in thc licluicl. In this
dcsign tlic safcty aspccts of t l ~ cstator with its elcctrical
insulation arc itnprovccl.' I.To\vcvcr, t l ~ cprcscncc of t l ~ c .
slainlcss slccl slator sl~cllit1 t l ~ cmotor air gap rccluccs
thc molor clricicnr:y and iticrcascs tlic inolor opcraling
currcn t.
For t l ~ cifnit c;isci~xscdItcrc thc rccluirccl ciirrcnt was
incrcasccl 1 y approsiiiintcly 20 pcrccnt \vhcn a canncd
stator clcsig~lwas tcslccl. This figurc worilcl 11c ftirtl~cr
incrcasccl if llic rolor \\.as also cannccl. ' ,

INTRODUCTION

Liquid ohygcn is one of thc tnorc aclivc cryogenic
fluids. Unclcr propcr conditions.it \\.ill react with tllc
colnnlon coinbustible matcrials, and undcr ccrtaiu conclitions,, such as aclclccl energy input, it will rcact with
mclallic construction materials. l'his is an important
consiclcration in tlic dcsign of cquipmc~ltfor usc in
liquid oxygen applications. It is cspccially important in
the design of rotating macliiucry, for cxainplc eleclric
niotor-drivcn pumps. In this type of equiymcnt the rcsultaut encrgy input cluc i0.a possihlc electrical overload
or mechanical sllock may bc sufiicicnt to initiate a mild
rcaciion or cvcn a violent detonation.
Elcctric motor-clrivcn liquicl oxygen pumps havc
oieratcd succcssfiilly, undcr norn~alconditions, with all
parts complctcly submcrgcd and wcttccl by liqiiicl oxygcii.
13ut in applicatioos which may prescnt a possiblc hazard
to human lifc, tllc safcty aspccts can bc enhanced by
aclditional clcsign precautions. In tlic elcctric rilotor
arc
drivcn ptnnp for instance, evcn thougli all ~n;~terials
sclcctccl for lnaxi~iiiilncornpal ibili ty with liq~iiilosygii~,
thc motor can bc cncloscd in a hcliiun gas incrtccl containcr. A dcsign of this typc, of coursc, will rcqliirc
roiatilig shaft scals. Illc sclcction and testing of a stiital&gt;ld

.

.

9rcscntcd.ul lhc Fourt:i In1crna:ionol ~orafc;enceon Fluid Sco!ing
h ~ l in
d conjunction with I:ie 1969 ASLE Annuol hlcc!ing irr
Pliilodcl;~l~io,Pa. This papcr sponsored by flle An~criconSocicly
OF hlccllonicol Engineers.

.

..
.263

.

�flange 10 incllcs in dialnctcr. lirciglit of t l ~ cunit is .
splxosimatcly 15 pounds.
On [he space v'clliclc the unit is fliinge Inounlccl'in a
bottom opening of a liquid osygcn supply lank ar~c1,'cxccpt for the outsidc face of the flange, is totally sub-.
rncrgcd in licluicl oxygen at -2'37°F.This cryogcnic
cooling pcrlnits a lnotor dcsign of smaller size and
\wight and of improvcd cficiency due, to the rctli~ccd
coppcr losses in thc stator windings. Normally, the moior
cavity is incrted wit11 hclium gas at a prcssrlrc of 11
, I:roximatcly 50 psig, but this prcssurc can go as high as.80 .
psig, which is limitcd by the motor cavity rclief valve.

,

SEAL CONSTRUCTION

Fig. I-Elcclric

~ o t o Slator
;

Aller Sirnutoted Short Circuit Test in Liquid
'

Oxygen.

In the sealed motor dcsign all motor parts opcrate
within a housing incrted with prcssurized hclium gas.
This dcsign prcscllts a minimtun safcty hazarcl. An cxample ,of this clcsign is shown in Fig. 2. This is an clcctric motor drivcn licluid oxygen pump unit for use on a
space vehicle. 11ie hclium prcssurizccl motor is separated
from tlic pumpcd fluid by a heliuln seal and a liquid
oxygen scal opcrating in a back-to-back arrangemcnt with
a comnlon ovcrboard vent betwccn them.
I l l e pump unit is clrivcn by a one horscpowcr clcctric
motor o ~ c r a t i n gat 11,000 rpln from a three-phase A.C.,
400 IIz, po\vcr s o ~ u c ca t a supply voltage of approximately 40 17.R.hl.S. lin'c-td-line. Thc unit is approximately
12" long, 4" in clian~ctcrand has an intcgral mounting

Because of the cryogcnic opcrating environment,
elastomcric sealing clcmcnts are not usable. Thercfore,.
an all metal wcldcd bello\vs.seal dcsign is cmploycd as
shown in Fig. 3. This is a cartridge type seal which is
shrink fittcd directly into the aluminum pump housing.
Static scaling is providcd by the seal caltriclgc shrink fit
in the pump housing and by tlle metallic bellows.
A loose or unattached carbon face picce is usccl with
this seal. The back side of the carl~onface piece is lapfittcd to the bellows end platc to provide an cffcctive
static seal at this point. The'clynamic or opcrating surface of thc carbon face is of the gas face typc consisting
of two concentric lands. l l l e inncr land is continuo~a
and performs the pl.cssurc scaling function, wl~ilcthe
outcr is a scgmcntcd bcaring land \vI~ichscrvcs to rcduce
seal facc pressure. Rotation of the carbon face picce is
prcvclltcd by slots, in the O.D. of the carbon face, \vhich
engage with radial kcys located in the I.D. of the scal
cartridge.
Compnrcd to a scal having an integral typc calbon face
piece, the loose facc piccc typc seal 11s thc following
aclvant agcs:

.

1. Seal face distortion due to differential thermal contraction of scal matcrinls is minimized.
2. Vibration damping is achievcd by friction bct\vcen
the face picce and keys.

l'he carbon facc picce opcratcs against a rot:iing ring
clampcd axially on the sllaft and statically scalccl to the
shaft by aluminum compression gaskcts.

V q WrUd Te

brbonN=*\

Fig. 2-Liquid

Oxygen Pump Will1 klc,liu~~i
lncrfcd Motor.

Fig. 3-llcliuni

.

Bellows Seal \Vil!,

I kaI

%I1 LD.

Loorc Carbon Fate.

�Scal

materials arc as follo\\,s:

lcakagc thcn slo\\;ly dccays to so~iicratc bct\vccn tllc

Scal cnrtrirlgc including bcllows-71s Staiulcss Stccl
-P5N carbon .
Carbon f;~ccpiccc
Rotating ring
-]lard cliro~nc
.. . on 440C Stainless
Stccl (Anncalcd)
l l i c 400 scrics stainless stccl is l~scclin prefercncc to'a
300 scrics bccause of its higher Lllcrnial conductivity. Thc
chrome plate tl~ickncssis 0.0015-0.005" as platccl and
0.001" minimun~aflcr lapping.

SEAL CHARACTERISTICS
Significant scal cliaracteristics are listcd in Table 1.
Tlle scal face prcssure of 10 psi consists of 7.5 psi
duc to bellows spring pressure and 2.5 psi resulting from
the 5596 scal hydraulic overbalance at 50 psig hclium
gas opcrating pressure. l l e ma.\imum a l l o ~ a b l cseal
friction torque of 10 oz. in. is governed by thc motor
torquc remaining after all othcr pump rcquirenlcnts have
bccn satisfied. I t &amp; influenced to a large extent by [lie
noto or starting currcnt lililit \vhicIi govclns tlie motor
torque capability.
The maximum pcr~nissiblcseal leakage ratc is 25
stanclard cd)ic inclies pcr minutc (SCIXI) of hclium gas
a t a motor cavity prcssurc of approximately 50 psig.
Actual scal lcakngc expericnccd during testing is about 2
SCIhl dynamically and 20 SCIhI statically, i.e., with tlic
unit non-operating. It is interesting Lo note that the
clynamic leakage is much lo~vcrtlian thc static Icakagc.
Tlic transition from the dynamic to thc static lcakagc
rate takcs place in apPr~si~natcly
10 to 40 seconds a f c r
tlic pump has come to rcst following powcr shut-olf. The
seal lcakagc incrcascs to the pcak static valuc at which
it remains for a pcriod of 30 seconds to 3 ~ninutes.Thc

TA~I.E
I-IIELIUhI

SEAL CIIARACTElXISTICS

1. Scal Operating Spcccl, RPII
2. ,Surface Spccd, ft/rnin.
3. P-V Factor, PSI' Ft/XIin.
4. Opcratiiig h1cdiu111
5. Prcssurc, PSI11

11,000

5

2300
23.600
.I~cliu~n
Gas
50-80

-297

6. l'cmpcraturc, "F

7. Scal 1)cflcction (installed), Inch
8. Axial Load, Lbs.
9. Ikcc Arca, in2: Scaling Land
Ilcaring Land
10. IIydraulic Ovcrbalancc, 9L
11. kace I'rcssurc (Total), PSI
12. Frictiori Torquc (Xluxir~ium),oz in.
13. Friction 111'
14. Facc I'Iittl~css,I1cli\111l
Light Bands
15. . Run-Out (Ilotating I:acc), l'.I.lt., illcli

,

.040-.050
2.5
0.19
0.14
55
.Id
I0
0.10
1-2
0.0005

ski clyna~nicand ~ n a x i ~ n ustatic
~ n rates. Tl~isclinrncteristic is rcpcat~1,leon sticccssivc pump tcsts.
l l i c 1 ~ 1 n iunit
p opcrating lifc rcquirc~ncntis 10 1iou1.s
wllich is nmde up of duty cyclcs each consisting of 20
minutcs of opcratiun follo~vcclby a soak timc of not lcss
than 5 minutcs. \\'car ratcs of scal C O I I I ~ ) O I I C I ~ ~cspcriS
enccd during tcst i1.e as follows:
P5N Carbon Face Piece
Chrome Plate on Rotating Ring

0.00005 in./hr
0.000025 in./lir

.

'

. Ilicsc \%?carrates wcre detcrniincd from three tcsts
with a total run timc of approximately 30 hours. The
ratcs indicate that tlic scal \vill easily surpass the rcquired life requirement.

Numcrous tcsts were pcrformed to dcvelop a scal combination that would meet the rcquired life, leakage, and
torquc requirements. Thc tcsts werc conductcdon scvcral
scal dcsign variations and on various con~binationsof seal
face and mating ring materials. I'ariations in scal facc unit
loading werc accomplisllcd by varying tlic bellows spring
load, seal facc \vidtIi, and hydraulic overbalance. For tcst
purposes, thc scals werc installed in tlie LO2 pun111 prcviously discussed.
The tcsts wcre pcrfor~ncdwith the unit subn~crgcdin
liquicl oxygcn and with thc motor cavity incrtccl with
helium gas at prcssurcs fro111 5 to 130 psig. Tlic tcsts
consisted of rcpeatccl opcrating cycles of 20 millutes cluration. Aftcr each operating cycle, tlic electrical power to
tlie unit was shut off and the unit was allowed to soak
for a minimum of fivc minutes before restart. Static scal
lcakage \!.as measurccl bcforc and aftcr every run, ancl
dynamic lcakagc during each run.

SEAL CONFIGURATIONS TESTED

liyo basically dilferent types of bcllows scals wcre
tcstcd wit11 the dcsign variations shown in Fig. 4 and
Tablc 2. Initial tcsts were pcrformcd with a scal having
an-intcgral carbon facc prcss fittcd in an encl plate weldcd .
to tlic scal bcllo\\~s.1,atcr tests wcrc donc with a scal
having a scparatc unattached floating carbon nose piccc
statically scalccl to thc bello111s end plate by a lappcd fit
as previously dcscribcd.
A bcllowvs scal will] an intcgral car1)on facc ancl no
vibration d:ir~lpcrwas tcsicd first. I~sccssivclcakagc, carbon wcar and chipping of thc carbon filcc at thc O.D.
ancl premature bclloti7s failurc were cspcricncccl wit11 this
scal. Af(er rcmoval fl'om thc pulnp, tlie scal was sul)jcctccl to vibration tcsts at aml)icnt tcnlpcr;~tt~rc
and
founcl to have a bronc1 nntural rcsonnut frequency rangc,
wliicll inclr~clcclthc unit operating spccd. An attcmpt \vas
maclc to shift Ll~isrcsona~itfrcqi~cricyband Ly cllnnging
the 1ir1rnl)crof bcllows convoli~tionsto 7 and also to I 1
from tlic original 9 convolutions. Thcsc cllruigcs did not

�swsrrn IIICCRU
VlORlIlGN I r ' W i R TIE

w1h~504ILQ r t c a

XAL COIFIGUUIIOY

SEU W I ~ HmAnNc cuaon nee A
m

Fig. 4-Seal

Configurations Tesfed.

prove cffcctive, so a vibration clamper spring \\:as aclclcd
to the scal.
l'hc vibration danlper consistcd of a flat steel spring
encircling the bcllows O.D.al&gt;prosinnatcly at the ~ n i d point of its axial Icngth. The spring applied a distri-

TABLE
2-SEAL
VIBRATION
DAB~PER

butcd forcc acting radially inward at the bello\vs 0.11.
This was a fingcr typc spring with lhc fingers cslc~iding
o~itiilardmncl rcaqling against the 1.11. of the scnl casc.
A vibriition tcst of illis seal at aml)icnt teii1pcl;tture
indicatcd that this spring was not vcry cffcctive in clunnping out vibration. Close visual examination of the seal
rcvcalcd that thcrc 'was vcry littlc physical interaction
bctween tlic spring and tlie bcllo\vs. llnis was confirmed
by' the prcscnce of very little hystcrcsis in the load
versus dcflcction calibration of this scal pc;fornncd a t
room tcmpcrature.
The scal design \\.as tlnen furthcr moclilicd to include an
adclitional spring acting around the O.D.of the seal nose
rctaincr plate w l ~ i c lis~ wclclcd to the bcllows. Vibration
tests of this seal indicatcd no natural resonhnce in the
operating spccd mnge. IIowevcr, operatiorla1 tests of the
scal within the unit still rcsultcd in excessive leakage
and chipping of the carl~onnose at the facc 0.13. A load
versus deflection calibration df this scal exhibited a very
widc liystcrcsis. This iilay have camcd hanging up of the
carbon nose rclativc to the mating ring with the consequent poor performance.
A round wire damper spring of approximately square
,configuration was installed in the scal acting betwcen tlle
scal nose retainer O.D.and the scal case I.D. This spring
provcd cffcctive in damping the seal when it was subjcctcd to a vibration tcst at rQoln temperature. An ol&gt;cra:
tional test of the seal \ililhin the unit shoivcd the leakage.
to be within acceptable limits. But addition of the round

VIBR;\TIOX AND LEAKAGE CIIAMCTERISTICS
RESOS,\NT
FREQUEXCY
O F I)ELI.O\VS
sE.4~-.'
(ROOMTE~IPEIIATURE)
,

Seal with Integral CnrLo~ifice Piece
None
173 to 190 Ilz

~ A ~ A N ; S

Excessive lcnkage, premature

bcllo\i~sfailurc,.rcsonant fi-cqucncy rangc includcs operating spccd of 183 cps.

'

Fingcr Spring at XlidPoint of Dcllows O.D.
Finger Spiing at
Bcllows Slid-Point &amp;
at Carbon Face 0.1).
Round IVire at Carbon Face 0.D.
Inhcrcnt in Dcsign

120 to 205 112
Nonc bctwcen
20-SO0 IIz
560 1Iz

153 to 205 ITz
wit11 ,lo torsional
lo:1d.
Nonc bciwccn 20SO0 IIz with a
t&amp;sionnl load
of S oz. in. applicd to thc
cnr1)on.

Excessive Leakage, Insuficicnt
Damping
Exccssivc L,cakagc, I righ
IIystcrcsis Calibration Curve
Low Lcakagc and Adcquatc
Damping

Low 1-cakagc and Adcq~latc

Dariq&gt;i~ig.
Prictiori damping
ariscs Lctwccn thc slots at
thc ca~.l,onface 0.11. and
thc keys at the scnl casc I.D.

�wirc diunpcr spring incrcasccl tlic scal spriiig r:itc and ~ila'dc
Under tliis conclit ion, ass~i~ili~lg
a tri:uigular I~ydraulicface
inslilliution witliin t l ~ cpurnp fi~irlycritical. For a scal . prcssurc distril~utiot~,
50 percent of tlic scal facc arca is
load of 2.5 Ibs. the scal liad to LC installed with an inioutside and 50 ycrccnt is i~~sidc
thc bcllo\vs mcan cKectial clctlcclioi~of 0.010 to 0.012 inch. Furtl~crirnprovctive dinmctcr. Such a scal is said to have ail ovcrl)alancc
mcnt \\'as, tl~cr~forc,
coi~sidcredclcsirable.
of 50 pcrccnt. %Ilc ;naul cfTectivc or cquivalcnt piston
A basically dilfcrcnt type of bcllo\\s scal was tcstcd ncst.
diameter is npprosimalcly equal to the average gcomctThis scal employccl a scparatc u~lattacllcdcarbon fitc6
ric diameter of the. bellows. In a scal with a 70 pcrccnt
piccc scaled statically to the bcllowvs end plate l?y' a
overbalance, 70 percent of tlic scal facc area is outside
lapped fit. NO addccl vibrittion damping devices wcrc rcof tlie incan cffectivc diamctcr. In tliis scal, tlie total facc
.
quircd with this scal. Leakagc and wcar were rcpcatcdly
pressurc consists of tlic pressure due to the spring load
within acceptable limits. nccausc of a lower scal spring
ancl 70 pcrccnt minus 50 percent or 20 pcrccnt of the
rate, installed scal dcflcctio~lis approsi~natcly0.040 to
scal operating prcssurc. Theorctically, hydraulic scal over0.050 inch for a.seal loacl of 2.5 Ibs. making installation
balance should not be necessary, but practically it comnon-critical. This scal is prcsc~ltlybch~gused in production
pcnsatcs for scal facc mccl~a~~ical
and thermal distortiorls
liquid oxygen pumps. At approximately 50 psig helium
and manufacturing impcrfcctions in facc flatness. \lrhcn
pressure static Icakagc of this seal is fro1113 to 20 SCIhl
the scal must operate ovcr a range of prcssurcs, it must
and dynamic Icakagc is about 2 SCIM.
be hyclraulically ovcrbalanccd suficicntly to keep the
leakage within acceptable liillits at the highest pressure.
During the devcloplnent tests, the scal bellows spring
SEAL FACE PRESSURE
loads were variccl froin approsi~llatelyseven to two pounds,
. .
scal I~yclraulicovcrbalancc from 70 to 46 per cent, and
One of the more important seal pararnetcrs is tllc facc
seal face arcas.fr01110.10 to 0.39 squarc inches. This reprcssurc. Statically, it is duc to the bcllo~vsspring load
suiltcd in seal facc pressures from 40 to 10 psi.
and hydraulic unbalancc. During seal operation, hyclrodyThe highcr values of seal spring load and ovcrbalance
namic loads ancl therinal dislortions also affect thc facc
producccl higher facc prcssurcs. Thc highcr facc prespressurc.
sures resulted in low initial lcakage, but presented conThe spring load must bc adequate to enable the seal
siclcrable wear ancl friction torque problems, and cvcntufacc to follow, ancl to maintain contact with, the scal
ally Iiigll leakagc duc to seal face scoring. At tlic other
rotating ring wit11 its inherent out-of-squarcncss. \Vhcn a
scal facc load extreme, wvhile wear and friction torque
scal is to be operalee1 at a single pressurc only, the spring
were lo\\ very little scaling was achieved. At ovcrbalload alonc could bc uscd, \vitll a liydraulically balanced
anccs of 50 pcr ccnt or Icss, scal lcakage was very erratic.
scal, to achic've acceptable scal performance.
Best over-all results wcrc oblainccl with a seal spring
In a ' hydraulically balancccl seal tllc hyclraulic forces
load of 2.5 Ibs., an ovcrbalance of 55 per ccnt, and a
tcnding to load and unload tllc seal face arc equal and
resultant seal face pressurc of 10 psi. Seal Icakagc, frictllc facc prcssurc is due to the bcllo\vs spring load only.
tion torque and facc wcar wcrc within acceptable limits.

3-PROPEI~TIES
O F SEAL h.lATERIt\IS
TAI~LE

BTU-IN

~IATERIAI.

F0 - El'

UECU
.
,

TIIEIL\IAL
ESP~~SSION EIARDSESS
In./ln./FO @ 70°F
Goor

1000
261 (Rc 22)
251 (Sc 20)
2200 to 2.100

~uriistcn
- Carbidc (KSO1)
(Nickel Ililldcr)

.'

'

I

'

(Bcrrylco 25)
P5N
(Purc Carbon Co.)
G39.
(U. S; Crap!\itc Co.)
P2003
(Purc Carl)on Co.)

Sclcroscopc 100
220 approx.

Sclcroscopc SO

�TABLE4-SUMMARY

OF SEAL TEST RESULTS
Wear Rate

Seal
face
herial

Rotating
Ring
hlaterial

Intcgral Carbon Face Typc Scul
1
C39 Carbon Chrome on
30.1
2
Chro~ncon

3
4
"

5

P2003
Carbon

S

P5S
Carbon

9

.

'

1

10
11
12

I.
.

13
14

Tungsten
Diselenide
Silver
Tefon

'

5

Over
Balance

Face
'Area
Inch2

'

%

Run
Time
Hr
Min

Xone

3.2

70

0.18

20

4

1
3

Seal
Face
In./Hr

Rota:ing
Ring
In./Hr

Seal
Operating
Press.
psig

Leakage
Std In.3/Min.
Static
Dynamic

0.004

(1)

5

'

01

(2)

(1)

.

40

0.00015

(2)

40
5
130

0.000S

0.010

,130

. 36

130

225

130

Light wear, erratic seal, high leakage
P2003 carbon is hygroscopic and not
suitable for cryogenic use.
High leakage

1.8

70

0.18

18

Round
Wire
Round
IVire

2.6 '

70

0.18

41

1.3

55

0.18

17

2

27

Chrome i n .
440C
P2003
,
CnrSon
P5S
Carbon

Round
\Yire
Round
Wire
Round
Wire

2.6

70

0.18

41

4

00

(2)

(2)

3.1

70

0.18

44

4

30

(1)

(1)

130

54

36

1.8

46

0.10

13

8

05

(2) .

130

320

220

P5S Carbon'

Round
Wirc
Round
Wire
Round
Wire
Round
Wire

2.0

55.

0.13

22

1

32

0.0043

0.012

130

87

44

. 1.7.
.

50

0.11

16

15

47

0.00008

(1)

,130

81

30

3.2 .

50

0.18

18

2

16

0.0014

(2)

5
130

4.9

50

28

1

55

0.0011

0.000008

130

3
33
590
25

15
33
170
100

130
95

270
,200"

130

'

,

.

Rzhr~nxs

44

Xone

'

'

(2)

.

.

Heavy transfer film. high torque, wear
. and leakage
I-Iigh leakage. seal lift off

150
4200
%I 1300
35
22

.

High wear

30

Very high rotating ring wear, early
seal failure

.

.

.

Very high wear pnd high,torque

C!:romc on
440C
'
Aluminum
OsiJc LA-2
C!:romiurn 3
Carbide
LC-:c
. S!iicon
Carbide

2 Flat
Spring

Chrome on
440C

Round
Wire

Chrome on
440C

Round
Wire

300

Sort material, low mechanical strength,
very high leakage

Inherent
In Design

20

High seal torque, restart impossible

I

3

Floating Carbon Face Type Seal
&gt;IYlOii
Chrome on
1'
I
44OC

4

Spring
Load'
Lbs.

440C
P2003
Carbon
P5S
Carbon

1:.

7

Damper
Spring
5 ~ e

Total
Face
Press.
psi

P5S Carbon Chrome on
RECU
Tungsten
Carbidc

,

lnheren t
In Design

.

3.7
3.6

55 ..

. .. .

50

-

.

0.18

. 0.16,
0.18

31

'

21

'

2
I6

50
40

0.0005
0.0003

(2)
'.

0.000003

5

330

.

.

260
60

Damper spring ma!$tnctioned
Good wear and leakage
Selective wear caused conical projcctions and high \wear and high leakage
Selective wcnr caused conical projections and high wear and high leakage
.
'

300

'
,

10
2

Very high wear, erratic and high leakage (rough surfaces)
Low mechanical s:rength, dimensional
instability. high leakage and wear

High torque a: operating pressure
Unit started at lowcr pressure
High torque and high leakage

2

Leakage was not significantly better
than present design
Leakage was 5 sci~nfor first four hours,
then increased to 20 scim

2

Low wear, low and repeatable Icakagc

�I~~ATERIALS
TESTED

.

'

TO~rlioi~iiizc
scal distortion and conscilocnt Icaliagc, it
is clesirablc to use ~natcrialsl~nvitlg,as ncarly as possil)lc,
similar espinsion charactcristics an6 masirnuin hcat .
concluctivity.
Listccl in Table 3 arc thcrmal expansion, conclactivity,
and Iiarclncss for scvcral scal matcrials. Other properti'es
sucll as film laying cl~aractcristics,friction and wcai-ing
qualitics, must bc dctcnnincd by actual test.
Various combinations of carbon facc and mating ring
matcrials wcrc tested as summarized in Tablc 4. Initial
tests nrcre performcd ising a seal with an intcgral carbon
'nose wit11 a G39 carbon fact nlatcrial operating versus
scveral cliflcrent mating ri~lg~natcrials.Carbon film transfer onto thc mating ring was hcavy and lcakagc, wcar,
and torque were gcncrally high ancl not acceptable.
A 1'2003 grapliitc matcrial with a clieinical salt imprconation
opcrati~igvcrsus scvcral mating ring material~
9
geilerally rcsultccl in high leakagc. Also, it was clisco\lcred
in the coursc of thc program that tliis ~natcrialwas hydroscopic and, tlicrcforc, not suitablc for cryogenic use.
Moisture attractecl to it rcsultcd in frcczing
- bctwcen tlic
seals and matigg rings \vithin the pump.
Next, a P5N casbon graphite facc material with a
chclnical salt impregnation was operatcd against a P5N
mating ring. This resulted in high friction, torquc, wear
and Icakagc, ancl confirmccl similar rcsults obtainccl with
othcr carbon vcrsus casbon combinations in this pump
unit. The 1'5N nose piccc was also tested versus flarnc
platcd mating rings of aluminum oxiclc ancl chromium
carbide. Carbon nose n7car and scal leakage \\we high.
This zppcarccl to bc due to sclcctive wcar of thc flamc
platetl materials resulting in sharp conical surface projcctions that abraiclecl thc carbon nosc matcrial. Thc P5N
was also opcratcd against a silicon cahidc mating ring.
\17ear and lcakagc wcre high and sealing \!?as erratic.
In an attempt to rcducc seal friction, two non-casbon
scal facc matcrials ~ \ ~ e tcstecl.
rc
One was a lligli tcrnpcratilrc material consisting largely of tungstcn disclcr~icle
solicl lubricant ancl the othcr was silvcr-tcflon composition. Both rcsullecl in higli. wcar ancl leakage. The tungsten disclc~liclematerial had Ihc undcsirablc property of
bccoming soft, dimensionally unstablc and wearing excessivcly after bcing cxposcd to liquid osygcn. Thc silverteflon material, duc to the fibrous nature of thc embcdclccl tenon particles, \\?asdiificult to polis11 to. the higli
dcgrcc of surface finish ncccnary for good scaling.'i\n
'attempt to run-in thc niatcrial did not improve its scaling characteristics.

'

. An h.lYl0K ciubon fucc piccc with an antilnony atldilive \\.as tested \rcrsus I~nrdcnccl(Ilc 55) 440c stainlcss
slccl. This material producccl a vcry I~cnvytralisfcr filn~
on tlic mating ring. l'llc carl&gt;on fcicc \\.as polislicd. IZcSulL:~utlediagc.wils low but scal friction torclt~c\ifas exccssivcly high.
Tests wcrc also. conducted \\lit11 a I'5N carbon scal
face opcrating vcrsus ~natingrings of harcl clirolnc platc
on bcryllii~mcoppcr and also versus tungstcn carbide witli
a nickcl binclcr. In both cascs thc mating rings ancl
carbon faccs werc vcry liglltly scorccl across tllc arcas of
contact. A vcry light carbon transfcr film was prcscnt on
the mating rings. Lcakagc.and \ircar resl~ltswcrc approsimately thc salnc as obtainccl will1 P5N vcrsus harcl chromc
on 440c stainlcss stecl.
?lie bcst and most consistc~ltrcsults wcrc obtainccl with
a P5N carbon face opcraling versus a mating ring of
hard chrome platc on annealed 440c stainlcss stccl. ljrear,
leakagc, and friction torque wcrc within acceptable limits
and werc repeatable. This material co~nl&gt;iilation
has bccn
qualified ancl is presently being med in'a liq~iicloxygen
punlp on a space veliicle.
CONCLUSIONS

From the work clcscril~cdhcrein tlic followi~lgcon
clusions nrere reached:
1. The best seal co~nbilialionconsistccl of a P5N ear-

bon face opcrating vcrsus a rotating ring of Ilarcl
chronic platc 011 annealcc1440c stainless steel with a
hydra~ilicoverbalailce of 55%, a face pressure of 10
psi ancl a spring load of 2.5 lbs.
2. The over-all pcrformaucc of the floating carbon facc
typc scal was superior to tlie intcgral facc type
seal.
3. The floating carbon facc seal \rw..found to have thc
following advantagcs:
a. Scal facc distortion cluc to the differential contraction bctwecn the carbon face ancl thc stainless stccl Lcllo\\~send platc was eliminated.
b. Aclcquatc axial ancl torsional. .vil&gt;ration damping
- was achicvcd by friction between the car1)on
.
facc and the seal stationary keys with no conse.
qucnt incrcasc in bcllows spring rate.
c. Rcfinisliing and rcplacclncnt of tllc scal ca'rbon
facc coulcl be donc without removal of the scal
from
thc pump housing.
.
d. Thc Iappccl bcllo~\~s
encl plate dicl not rcqriirc
rcfinisliing during the life of tllc unit. .
'

.

�</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="19964">
                <text>spc_stnv_000054</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19965">
                <text>"A Helium Face Seal Application In a Liquid Oxygen Pump."</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="19966">
                <text>FICFS Preprint 24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19967">
                <text>Presented at the Fourth International Conference on Fluid Sealing held in conjunction with the 24th annual meeting in Philadelphia, May 5-9, 1969.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19968">
                <text>Cieslik, Walter</text>
              </elementText>
              <elementText elementTextId="19969">
                <text>American Society of Lubrication Engineers</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="19970">
                <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="19971">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19972">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="19973">
                <text>Liquid oxygen</text>
              </elementText>
              <elementText elementTextId="19974">
                <text>Pump seals</text>
              </elementText>
              <elementText elementTextId="19975">
                <text>Sealing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19976">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="19977">
                <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="19978">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="19979">
                <text>Box 31, Folder 32</text>
              </elementText>
              <elementText elementTextId="205805">
                <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="19981">
                <text>FICFS Preprints</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19982">
                <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="19983">
                <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="19984">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1139" public="1" featured="0">
    <fileContainer>
      <file fileId="986">
        <src>https://digitalprojects.uah.edu/files/original/20/1139/spc_stnv_000055.pdf</src>
        <authentication>a3ffc30c2c9f010d1c077286206b49e3</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177273">
                    <text>A Hybrid Simulation for Dynamic Verif icatio
of Saturn Guidance and Control Subsystem:

�IBM NO. 68-U6O-0013

A HYBRID SIMULATION FOR DYNAMIC VERIFICATION O F
SATURN GUIDANCE AND CONTROL SUBSYSTEMS

.

Ronald T Patray

May 15, 1968

International Business Machines Corporation
Federal Systems Division
Space Systems Center
Huntsville, Alabama

�A HYBRID SIMULATION FOR DYNAMIC VERIFICATION O F
SATURN GUIDANCE AND CONTROL SUBSYSTEMS

Ronald T. Patray
International Business Machines Corporation
Federal Systems Division
Space Systems Center
Huntsville , Alabama

I. INTRODUCTION
This paper presents a discussion of a hybrid simulation used to dynamically verify the Saturn Guidance and Control subsystems. First, the Saturn
vehicle is briefly described to provide background information. The Instrument Unit (IU) is considered in more detail to give a proper setting f o r the
Guidance and Flight Control (G and FC) discussion that follows. After a brief
description of the actual G and FC System operation, simulation models of the
G and FC components a r e considered in detail. This is followed by a discussion of the model assignment to a particular computer (digital o r analog) and
justification f o r making that assignment. Finally, results of the A S - 2 0 4 / ~ ~ 1
hybrid simulation studies a r e briefly considered with mention of the actual
flight data. 1
11. SATURN VEHICLE DESCRIPTION
The Saturn IB, which has two propulsive stages (Slide I ) , is serving
as a launch vehicle f o r the Apollo spacecraft earth orbital flight tests. These
flights simulate certain studies of the lunar landing mission and provide flight

1

Some of the material in this paper is based on notes f r o m an IBM conference
presentation entitled, "Digital Computer Program for Support of Hybrid
Computer Simulation of Saturn Launch Vehicle, " by E. W. Snyder.

�t e s t s for the spacecraft and the S-IVB/IU Stage. Each Saturn IB has
a payload consisting of some combination of a Lunar Module (LM), Service
Module (SM), Command Module (CM), and Launch Escape System (LES).
The Saturn V, which has three stages (Slide I ) , is the launch
vehicle f o r the actual lunar landing missions. For these missions the Saturn V
will c a r r y a payload consisting of an LM, SM, CM, and LES.
111. INSTRUMENT UNIT
The major purpose of the Instrument Unit (IU) shown in Slide 2 is to provide the Saturn vehicle with a centralized astrionics package for guidance,
control, sequencing, and telemetry during boost and earth orbit, and through
lunar trajectory insertion. The IU subsystems (Slide 3 ) include the Structural
Portion, Guidance, Flight Control, Environmental, Instrumentation, and
Electrical.
A. Guidance and Flight Control Subsvstems
Slide 4 lists the major components of the Guidance and Flight Control
Subsystems. Included a r e the Launch Vehicle Digital Computer (LVDC), the
Flight Control Computer (FCC), the ST-124 Inertial Platform, and the control
accelerometer and rate gyro /control signal processor.
Slide 5 shows a rough sketch depicting the closed loop operation of the
Guidance and Flight Control Subsystems. Sensors on the inertial platform meas u r e the angles ( 8 ) between the inertial and body reference f r a m e s and changes
in velocity along each inertial axis. These signals a r e transmitted to the
LVDC-LVDA where the velocities a r e used in navigation and in computing the
commanded gimbal angles (x). The actual platform gimbal angles ( 8 ) a r e differenced
with the x's to give attitude e r r o r signals ($1 in the inertial platform frame.
These $ 's a r e transformed to result in attitude e r r o r signals ( A qb ) in the body
frame, which a r e fed to the FCC where they a r e filtered and summed with the
filtered rate gyro signals
to give engine actuator commands (4).The ,f3
signals drive the actuators and thus change the thrust vector orientation which
in turn changes the vehicle attitude.

(6)

IV.

DYNAMIC VERIFICATION OF THE GUIDANCE AND CONTROL SYSTEM

Filters in the FCC and parameters in the LVDC flight program a r e
designed to give satisfactory stability margins while maintaining good vehicle

�response to guidance commands. These designs a r e determined by using
linearized models and linear stability analysis techniques at a few frozen
points in time. While this method of design has proved, thus f a r , to be reliable, it does not consider the effects of nonlinearities in the guidance system,
nor does it consider vehicle dynamics continuously throughout boost flight.
Thus, a means of dynamically checking the FCC filter design and LVDC flight
program in a total system configuration under flight conditions, over all times
of vehicle boost flight, was needed to ensure the nonexistence of adverse
dynamic effects on the vehicle, the astronauts, and the guidance accuracy. It
was decided that a system would be devised in which, except for the LVDC
flight program, all components significantly affecting the vehicle dynamics
would be simulated. For this task, a six degree-of -f reedom real time hybrid
simulation with LVDC/LVDA flight hardware in the loop was chosen that would
fully exercise the flight program and check its dynamic effects on the vehicle
throughout simulated boost flight, and at the same time check the FCC filter
design for vehicle stability and response.
V. HYBRID SIMULATION
Slide 6 shows a simplified G &amp; FC loop for pitch and yaw. The LVDC and
LVDA a r e flight-type hardware, while the Flight Control Computer, Engine
Actuator, Vehicle Dynamics, Rate Gyro, Inertial Platform Assembly, and
Propellant Utilization System (PU) a r e simulated on the hybrid system. Each
component that significantly contributes to vehicle dynamics is described
below, followed by a description of the simulation model of each component.
A. Launch Vehicle Digital Computer (LVDC)
1. Actual LVDC
Slide 7 depicts the Saturn V flight computer (LVDC) tasks by phase:
Phase I includes the time of f i r s t stage boost. During this phase the
vehicle is moving through the dense portion of the atmosphere where high
aerodynamic pressure occurs. To avoid excessive structural loads caused
by guidance maneuvers, no guidance constraints a r e applied. An open loop
guidance scheme in the form of a time tilt program is used.
Phase I1 includes the second stage boost time. The flight program
during this phase uses a path adaptive guidance scheme called Iterative

�Guidance Mode (IGM) in which guidance is a function of space-fixed position (F )
and velocity (G ) , ~ / m
and time. This adaptive guidance scheme seeks to
attain predetermined space -fixed position and velocity vectors with the consumption of a minimum amount of propellant.
Phase I11 includes the f i r s t burn time of third stage boost and orbital
time. IGM guidance is used during the boost portion of this phase.
Phase IV includes the second burn time of third stage boost. IGM
guidance is also used during this phase.
Phase V includes all mission time after $-NB/IU Apollo Spacecraft
separation.
The LVDC/LVDA has a s inputs inertial platform gimbal angles, measured changes in velocity along each platform axis, and flight sequencing
discretes. The LVDC/LVDA outputs a r e attitude-error steering commands
and flight sequencing discretes.
Since an actual flight type LVDC/LVDA is used in the simulation, no
LVDC/LVDA model was devised.

B. ST- 124 Inertial Platform Assemblv
1. Actual Platform

The Inertial Platform Assembly (Slide 6) is the main sensor for guidance.
At guidance reference release, which occurs a few seconds before liftoff, the
platform becomes inertial (space-fixed). A resolver attached to each platform
surface measures the gimbal angle ( 8 ) between the surface and vehicle axis.
These resolver outputs a r e read by the LVDC flight program every 40 milliseconds.
Integrating accelerometers, mounted along each axis of the platform,
sense changes in measured velocities (AX,, A * ~ , A 2,) in increments of
.05 m/sec. Signals representing these velocity changes automatically increment o r decrement velocity counters in the LVDA. These counters a r e read
periodically by the LVDC flight program.

�2.

Platform Simulation Model

Platform gimbal angles ( 0 ) a r e simulated by first transforming the
simulated body r a t e s
(Slide 6) into the inertial coordinate frame, and then
integrating the resulting gimbal angle r a t e s (8). Gimbal angles a r e computed
and transmitted to the LVDA at a 40-millisecond rate.

(4)

The platform integrating accelerometers a r e simulated in two ways:
During f i r s t stage simulation, vehicle thrust is obtained through a table lookup
scheme of thrust versus vehicle altitude. Thrust is then used with remaining
vehicle m a s s (m,), which is computed, to obtain total vehicle acceleration
.
engine angles
(F/mV). This acceleration is resolved through the simulated
( P ) to result in body acceleration components gB,yB, ZB). which in turn
a r e transformed via the platform gimbal angles (0) into inertial platform
acceleration components Wm, Y,,
z,). These accelerations a r e then used
to compute changes in measured platform velocity components
(AX,,
A
A i m ) which would normally be sensed by the platform integrating accelerometers. The measured velocity changes a r e computed and
transmitted through special interface equipment to the LVDA every 40 milliseconds. During the second and third stage simulation, vehicle thrust is
obtained through a table lookup scheme of thrust versus Propellant Utilization
System (PU) valve position, which is the output of the PU System simulation
model. After vehicle thrust has been obtained, changes in the platformmeasured velocities (AX,, A
, A z,) a r e derived in the same manner as
in the f i r s t stage simulation.

.

C.

Flight Control Computer (FCC)

1. Actual FCC
The primary functions of the FCC a r e to provide command signals (PC)
to the engine actuators and to ensure adequate vehicle stability by compensating the guidance and control loop with proper attitude e r r o r and r a t e filters.
These f i l t e r s a r e implemented with passive elements.
The FCC shown in Slide 6 has as inputs attitude-error steering commands ( A4's) from the LVDA and body r a t e s (4's) f r o m the body rate gyros.
These inputs, when filtered in the FCC and summed, result in actuator commands (PC's)which move the engine actuator, and thus the thrust vector, to
cause changes in vehicle dynamics.

�2. FCC Simulation Model

Slide 8 shows a simplified block diagram of the pitch control loop,
including sloshing and bending models for a single engine stage. The simulated attitude and attitude rate filters a r e implemented with passive elements
a s in the actual FCC. The control gains a. and a 1 a r e changed during actual
and simulated flight in discrete steps to offset changes in the control moment
of inertia.
D. Engine Actuators

1. Actual Actuators

The Saturn engine actuators, while differing in type from stage-to-stage,
a r e all highly nonlinear with rate and position limits.
2 . Actuator Simulation Models

Linear approximations of the engine actuators a r e used in the hybrid
simulation. The transfer functions for these actuator models a r e of order
three o r four, depending on the boost stage. In using these linear approximations, small engine angles (0 to 1 3 degrees) a r e assumed. Simplified
nonlinear actuator models a r e presently being developed to handle more
severe cases of engine movement.
E. Bodv Bending Model
The effects of one mode of body bending, caused by forces due to engine
position ( p ) and acceleration
a r e simulated in the pitch plane (Slide 8) by
a second order linear model. The effects of bending (dB and A O B ) a r e sensed
by the rate gyros and platform gimbals and therefore affect the guidance and
control loop.

(B),

F. Moment Equation Model
Motion of the rigid body is described by simple rotational mechanics:
is equal to a moment coefficient C2 times Sin P ,
The attitude acceleration (4)
where C2 is total thrust times the moment a r m (distance from engine gimbal
to center of gravity) divided by the moment of inertia. The Hybrid Simulation

�computes C2 on line from its component parts. The small angle approximation Sin P = P (radians) is used.
G. Propellant Slosh Model

Propellant Sloshing (LOX and LH2) effects on the vehicle attitude acceleration in the pitch plane and the Propellant Utilization System Valve Control
a r e included in the simulation of the second and third stages. The inputs that
cause major sloshing action in the pitch plane a r e the vehicle translational
acceleration due to thrust in the pitch plane and vehicle attitude acceleration
in the pitch plane. These inputs cause the propellants to move against the
tank walls which, in turn, causes attitude acceleration to be induced by two
factors: the force of the propellant sloshing m a s s acting on tank walls through
a moment a r m about the center of gravity, and the sloshing m a s s being displaced from the center line of the vehicle acting through a radial moment a r m
about the center of gravity. The model used to simulate the sloshing effect
during second and third stages consists of two linear second-order directly
coupled differential equations with m a s s varying coefficients. These differential equations describe the radial motion of the slosh m a s s (LOX and LH2)
in the pitch plane.
H. S-I1 and S-TVB Propellant Utilization Systems (PU)
1. Actual PU System

One function of the PU system is to control the LOX and LH2 flow to the
thrust chamber in such a manner that depletion of LH2 and LOX will occur
simultaneously. Remaining LOX and LH2 a r e measured by capacitance-type
probes in each tank. The signal from each probe is gain adjusted so that when
the two signals a r e differenced, a resulting signal will drive the PU valve
position servo to give a desired EMR.
Sloshing (LH2 and LOX) causes the signals representing remaining propellant to vary, which in turn tends to cause the PU valve position, EMR, and
thrust to vary at the sloshing (LOX and L H ~ frequencies.
)
Since a varying
thrust has ill effects on the guidance system, the PU valve control signal is
filtered so that sloshing frequencies a r e highly attenuated in the resulting
valve control signal.

�2. PU Simulation Models
Slide 9 depicts a S-IVB PU system model obtained from a MSFC Guidanct
This is basically the model used in the Hybrid
Dynamics Design Document.
Simulation. The S-I1 model is essentially the same except for a different
sloshing filter. In the PU model, remaining LH2 and LOX masses at any point
in time a r e determined by integrating the total flow r a t e s and subtracting these
f r o m the initial LH2 and LOX masses. Slide 9 also shows how the effects of
propellant sloshing on the PU system are implemented.
VI. COMPUTING TASK ASSIGNMENTS

In assigning computing tasks several factors were considered that seemed
to fall into two general categories as shown in Slide 10 and as follows:
A. Application Orientation

1. Frequency Content
In the Hybrid Simulation, models with high frequency content were simulated on the analog computer, which has a bandwidth of several kH. The f r e quency response of digital computers depends on both the algorithms used to
represent a given model and the solution r a t e of the algorithms. In general,
f o r good accuracy, the solution rate must be several times the highest significant frequency .

2. Precision Requirements
Where high precision was required the digital computer was used, because parameter value can be maintained and expressed in much smaller
increments. An analog signal value is usually expressed in no more than
four o r five decimal places.

3 . System Composition
In the r e a l world the LVDC is digital while the FCC is analog. Precision
in a simulation need not be greater than it is in the actual system. This was
a consideration in assigning the FCC simulation task.

MSFC Memo #R-ASTR-F-66-45, Phase I1 Guidance Dynamics Design Document f o r AS-207, 8 March 1966.

�Flight Hardware Interface

4.

The output of the hardware (LVDC-LVDA) consists of attitude steering
commands ( A 4 ) which a r e analog signals. The inputs to the flight hardware
a r e platform velocity counts, which a r e discrete in nature, and platform gimbal angles, which a r e analog signals.
5. Type of System

One important consideration in some of the model assignments was the
time varying coefficients in the differential equations representing the models.
The analog computer readily lends itself to modeling the differential equation
while the digital computer easily handles time varying coefficients. The
models were therefore simulated on a hybrid system using multiplying DAC's
to combine the coefficients with the dependent variable and i t s derivatives.
B

.

Simulation Hardware

1. Memory Size and Speed of Digital Computers

While memory size can be important, it was not a consideration in this
simulation. The speed of the digital computer was a consideration, in that i t
determined how fast the various loops in the program could be processed and,
therefore, what the solution r a t e s f o r the various model algorithms would be.
2. Equipment Configuration of the Analog Computer
Task assignment is largely dependent on the types and number of elements on the analog computer. In this simulation the analog computer specifications were based on the already determined task assignments listed below;
thus the elements were not really a consideration in this case.
3 . Linkage Characteristics

The bit configuration (word length), conversion rates, and number of
channels @/A, A/D, D/D) were important considerations in assigning c e r tain tasks.

�4. Communication Channel Count and Precision Versus Consolidation of
Small Computing Task on One Machine
When implemented all-analog o r all-digital by the use of special techniques, a model which is best suited to hybrid application will use fewer conversion channels but may lose precision and accuracy.
C

.

Assignments

Slide 11 shows a list of the actual computing task assignments.
a r e as follows:

These

Analog

-

-

-

Flight Control Computer
Control Actuator
Moment Equations
Propellant Slosh Model
Body Bending Model
Propellant Utilization Control System
Digital

-

-

D.

Inertial Platform
Time and Mass Varying Function Generation
Navigation Model
Telemetry Ground Station
Control of Automated Setup and Checkout of Analog Computer
Propellant Utilization System Valve and Pump Model
Data Reduction and Preparation

Hybrid Simulation Tie -In

Tie-in of the total hybrid simulation is presented by tracing system
signal flow in the S-IVB stage pitch plane as follows. The analog computer
receives the attitude steering command ( A 4 ) from the LVDC-LVDA. The
P
control computer model filters this signal and sums it with the filtered body
attitude rate ($p) generated by the vehicle dynamics model. The resulting
signal (PCP)is fed to the actuator model which generates the simulated engine

�(9).

angle
This is then multiplied by the control moment coefficient (CZp),
provided by a digital model, to result in a rigid body pitch attitude acceleration
due to engine thrust. This component is summed with the attitude acceleration
arising from propellant sloshing to give total attitude acceleration ($p). This
$p is integrated once to result in rigid body attitude rate (dp)that is summed
with attitude rate due to body bending
) to give a simulated body rate gyro
bp
output (bgp). The propellant sloshing model has a s inputs, engine angle ( 6 )
P
and attitude acceleration (Pp), while the bending model is forced by engine
angle (Pp) and engine rotational acceleration (b ).
P

(6

The propellant utilization (PU) system is forced by remaining LOX and
LH2 m a s s which a r e computed on a digital computer. The PU system is
perturbed by radial positions of propellant sloshing m a s s e s (LOX and LH2).
The output of the PU system is valve position (av).

A digital computer receives as inputs from the analog models the
attitude rate (dgp), the engine angle (Pp), and the PU valve position (8,). The
$gp is resolved into the inertial platform frame to result in a platform gimbal
angle rate ( 6 p), which is integrated to give the gimbal angle (0 p). The PU
valve position (6 ). is used in a table look scheme of total thrust ( F ) versus
6, to obtain F, which is then divided by remaining vehicle m a s s (mv) to result
in total vehicle acceleration (F/mv). Vehicle m a s s is computed by subtracting
integrated propellant flow rates from initial vehicle mass. Components of body
m ~ the engine gimbal angles.
acceleration a r e obtained by resolving ~ / through
These components a r e in turn resolved through the inertial platform gimbal
angles to result in inertial platform accelerations components, which a r e used
to compute changes in measured platform velocities. These changes in velocities
and the simulated inertial platform gimbal angles a r e transmitted via special
interface equipment to the LVDC -LVDA where the accumulated velocity changes
a r e used for navigation and computation of commanded platform gimbal angles
(x). These x ' s when differenced with the actual platform gimbal angles result
in attitude e r r o r signals (+) which a r e transformed into the body frame to
result in attitude steering commands (A$). These A $ 's a r e then transmitted t o
the analog computer to close the guidance and control loop.

�VII. RESULTS
In concluding this presentation, some of the results from the AS-204
L M / ~Hybrid Simulation studies will be discussed. Slides 12 and 13 show

s t r i p recordings of some of the simulated vehicle and systems dynamics f o r
a nominal case. From left to right on Slide 12 a r e the pitch attitude steering
command (A$*), pitch engine angles (Bp (1,2) and ($ (3,4), pitch body r a t e
(&amp;p), yaw attitude steering command ( ~y),
4 yaw engine angles (fly (2,3) and

(Py (1,4), and yaw body rate (&amp;y). Magnitudes of these parameters and significant flight events a r e indicated. Slide 13 shows Cfrom left to right) the
roll attitude command @OR), body roll r a t e (eR), radial displacement of the
fuel and LOX sloshing m a s s (Z and ZL), remaining LOX and fuel weight
(WL and WF), the change in engine mixture ratio (AEMR), and P U valve position (aV). These simulation results compare favorably with actual flight data.
All significant differences a r e attributable to uncertainties in certain initial
conditions. While results from the hybrid simulation have been good, certain
anomalies in actual Saturn flights have revealed a need f o r studies that were
not previously considered. These studies can be handled by making slight
modifications to certain simulation models.
VIII.

SUMMARY

A hybrid simulation is used to dynamically verify the guidance and cont r o l subsystems of Uprated Saturn I and Saturn V vehicles. This is done by
simulating pertinent vehicle dynamics in a closed guidance and flight control
loop with flight-type (LVDC and LVDA) hardware in the loop. In conjunction
with equipment constraints, the computational complexity imposed by the
requirements for high precision solutions of the guidance and navigation equ:
throughout the total boost portion of the mission and f o r accurate solution of
nonlinear differential equations with variable coefficients and high frequenc:
content led to the choice of a hybrid system for this application. This simr
has already proven to be a valuable tool fop preflight prediction of vehicle/
system dynamic performance and i t s effects on guidance accuracy. With
further developments, it will also be useful for detailed evaluation of dyna.
behavior under extreme combinations of off -nominal situations.

�LAUNCH ESCAPE
SYSTEM

LAUNCH ESCAPE
SYSTEM

COMMAND
MODULE

SERVICE
MODULE

COMMAND
MODULE
SERVICE
MODULE

ADAPTER

S-IVBSTAGE

LUNAR
LE

q+- - -

I
1 J -2 ENGINE

INSTRUMENT

S-IVB STAGE

5-IVB AFT
INTERSTAGE

--I I
. 1 J-2 ENGINE

S -IC STAGE
S-IB STAGE

8 H-1 ENGINES
APOLLO-SATURN V VEHICLE

UPRATED SATURN I VEHICLE

Slide 1

�SATURN INSTRUMENT UNIT

Slide 2

�Instrument Unit Subsystems

e

STRUC'TURAL PORTION

e

GU IDANCE AND CONTROL

e

ENV I RONMENTAL CONTROL

e

MEAS UR ING AND TELEMETRY

e

RAD 10 FREQUENCY

e

ELECTR ICAL

Slide 3

15

�Guidance and Control Subsystem

o

LAUNCH VEHICLE DIGITAL COMPUTER (LVDC)

o

LAUNCH VEHICLE DATA ADAPTER (LVDA)

o

FLIGHT CONTROL COMPUTER (FCC

o

ST 124 INERTIAL PLATFORM

a

BODY RATE GYROS

Slide 4

16

�Simplified Saturn V

Slide 5

17

�Guidance and Control System

- ..

..

..

Xm ' Ym ' Zm

lnertial
Platform
Assernbl y

&gt;P

-------------------

B~

-

I
I
I
-%
JJ

I
I

inertial Velocities (~11,A V , OW)
Inertial Platform Gimbal Angles ( 0 )

1

__c

LVDC

-1

-1

LVDA

n v ~

b

Flight
Control
Computer

@CP

Engine
Actuator

Vehicle
.
-@%
Dynamics
I

A

A '

-vT'
'

PU
System
Rate
Gyro

---------

Slide 6

18

I
I
I

�FLIGHT COMPUTER TASKS B Y PHASE

185 Kilometers (100 Naut. Miles
I

SATURN V I APOLLO

PHASE

t

Slide 7

19

I

TASK

I

�Control Loop

Slide 8

�Propellant Utilization System

z~

,c o s e F

SLOSH
INITIAL
L H 2 ~ t ~LH2~ ~ ~

--

.

8wF

a z ~

FROM SLOSH MODEL

NOMINAL L H ~
FLOW RATE

I

LH2 BRIDGE SERVO

I
'PU

K~ ( d s 2

cs5

t

6s4

-

- bS '

-

es3 fs2 g s

POSlTlONER

VALVE
AA\P

FORWARD SHAPING

-1

VALVE

:

K~

I

GEARS &amp; POT

REDBACK

I

LOX BRIDGE SERVO

-

-

2C~"~

,
1

1\ .s

K~~

z~
FROM SLOSH MODEL

-

'

coseL .

IINITIAL

aW~
aZL

LOX SLOSH
WEIGHT

Slide 9

LOX
WEIGHT

I

N O M l NAL LOX
FLOW RATE

Lox

TO
THRUST
MODEL

�Factors Related to Computing Task
Assignments in Hybrid Simulation

1. APPLICATION
a.
b.
c.
d.
e.
2.

FREQUENCY CONTENT
PREC IS ION REQU I REMENTS
SYSTEM COMPOS IT1ON
FLIGHTEQUIPMENT INTERFACE
TYPE OF SYSTEM

COMPUTER HARDWARE
a.
b.
c.
d.

MEMORY S I Z E AND SPEED OF D I G l T A L MEMBER
EQU I PMENT CONFIGURATION OF ANALOG MEMBER
LINKAGE CHARACTER1 STICS
COMMUNICATION CHANNEL COUNT AND PRECISION
vS
CONSOLIDATION OF SMALL COMPUTING TASK ON ONE MACHINE

Slide 10

22

�Computing Task Assignment

ANALOG

a
a
a
a
a
a

FLIGHT CONTROL COMPUTER
CONTROL ACTUATOR
MOMENT EQUATIONS
PROPELLANT SLOSH MODEL
BODYBENDINGMODEL
PROPELLANT UTl L l ZATl ON CONTROL SYSTEM

DIGITAL

a
a
a
a
a
0
0

lNERTl AL PLATFORM
TIME ANDIOR MASS VARYING FUNCTIONS GENERATION
NAVIGATION MODEL
TELEMETRY GROUND STATION
CONTROL OF AUTOMATED SET-UP AND CHECKOUT OF ANALOG
PROPELLANT UTILIZATION SYSTEM VALVE AND PUMP MODELS
DATA REDUCTION AND PREPARATION

Slide 11

23

�Slide 12

�Slide 13

�4

Federal Systems Division, Space Systems Center, ~untsville,Alabama

�</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="19985">
                <text>spc_stnv_000055</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19986">
                <text>"A Hybrid Simulation for Dynamic Verification of Saturn Guidance and Control Subsystems."</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="19987">
                <text>IBM No. 68-U60-0013</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19988">
                <text>This paper presents a discussion of a hybrid simulation used to dynamically verify the Saturn Guidance and Control subsystems. First, the Saturn vehicle is briefly described to provide background information. The Instrument Unit (IU) is considered in more detail to give a proper setting for the Guidance and Flight Control (G and FC) discussion that follows. After a brief description of the actual G and FC System operation, simulation models of the G and FC components are considered in detail. This is followed by a discussion of the model assignment to a particular computer (digital or analog) and justification for making that assignment. Finally, results of the AS-204/LM1 hybrid simulation studies are briefly considered with mention of the actual flight data.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19989">
                <text>Patray, Ronald T.</text>
              </elementText>
              <elementText elementTextId="19990">
                <text>International Business Machines Corporation. Federal 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="19991">
                <text>1965-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="19992">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19993">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="19994">
                <text>Project Apollo (U.S.)</text>
              </elementText>
              <elementText elementTextId="19995">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="19996">
                <text>Apollo spacecraft</text>
              </elementText>
              <elementText elementTextId="19997">
                <text>Spacecraft guidance</text>
              </elementText>
              <elementText elementTextId="19998">
                <text>Spacecraft control</text>
              </elementText>
              <elementText elementTextId="19999">
                <text>Computerized simulation</text>
              </elementText>
              <elementText elementTextId="20000">
                <text>Dynamic tests</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20001">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20002">
                <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="20003">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20004">
                <text>Box 26, Folder 34</text>
              </elementText>
              <elementText elementTextId="205806">
                <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="20006">
                <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="20007">
                <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="20008">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1148" public="1" featured="0">
    <fileContainer>
      <file fileId="995">
        <src>https://digitalprojects.uah.edu/files/original/20/1148/spc_stnv_000064.pdf</src>
        <authentication>ad809db4108abf8a07cf50bfc0872e0d</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177282">
                    <text>With the 1970 lunar touchdown already in its sights,
NASA's Office of Manned Space Flight seeks to make
the United States pre-eminent in space.

A Nation Goes to
/r&amp;(/iS
".Note/ is the kime to take longer strides-time for a p e a t new
American enterprise-tirrle,fir this nation to take a clearly leading
role in space achieuernent a~hichin many zoaj)s may hold the key
to our,future on earth. I belieup thal this nation should comrnit
itself to achieving the goal, befire lhis decade is out, of landing a
man on the moon and returning him safely to earth. . . . It will not
be one man going to the moon . . . it will be an entire nation."
-President John F. Kennedy

ive years ago the United States
took its first tiny steps toward
the moon when Commander
Alan Shepard became the first American to be rocketed into space. And
the entire nation-indeed the whole
world-witnessed his flight, sharing
in the tension and the triumph. Today, at the halfway point in the tenyear program to land a man on the
moon and return him to earth safely,
the United States manned space program has both lengthened and quickened its stride. And the distance from
the earth to the moon doesn't seem
quite that far anymore.
In developing the elements and
capabilities for this decade's manned
lunar landing, NASA has marshalled

F

I
I

the men and machines that will make
it possible to undertake a wide range
of space missions beyond the initial
moon touchdown. Indeed, as Dr.
George Mueller comments, "manned
lunar flight serves as the focal-point
of a program whose principal goal is
to give the United States world leadership in all elements of space activity. The Gemini and Apollo-Saturn
programs are equipping this nation
with the ability to carry men and instruments into hitherto inaccessible
regions of space for hitherto unachievable periods of time."
Dr. George E. Mueller
Associate Administrator
Office of Manned Space Flight

��Dr. Mueller, Associate Administrator for NASA's Office of Manned
Space Flight, bases his appraisal on
the remarkable progress that has been
made in the tri-lateral manned flight
program-Projects Mercury, Gemini
and Apollo. Together the three constitute the greatest single engineering
enterprise in this nation's history. The
manned space flight program is carried out by some 300,000 men and
women. They work in NASA'sWashington, D.C. office, at three field centers-the John F. Kennedy Space
Center in Florida; the Manned Spacecraft Center near Houston, Texas, and
the George C. Marshall Space Flight
Center at Huntsville, Alabama-and
a t some 20,000 industrial plants in

every part of the country. Dr. Mueller
directs this competent crew by means
of a geographically dispersed program
office structure which penetrates directly through the functional organizations of the field centers and the
prime contractors, to the subcontractors and the vendors. It has been
said that Dr. Mueller's techniques of
managing so vast a research and development program may, in the long
run, prove to be one of the most valuable assets derived from the program.
The first phase of the tri-lateral
manned space flight program, Project
Mercury, set the stage for the sophisticated space maneuvers of today and
tomorrow. Using experimental oneman vehicles, Project Mercury put the

first Americans into space and laid a
solid foundation for the technology of
future manned space flights. It demonstrated the effects of space on man,
and proved that men could increase
the reliability of spacecraft controls.
NASA logged its first manned space
flight success on May 5,1961, the day
Astronaut Shepard rode his Freedom
7 space capsule on a 19-minute suborbital mission, 116 miles high into
space. Another Mercury milestone
was achieved the following February.
Astronaut John Glenn became the
first American in orbit, completing
three global circuits. The following
spring Gordon Cooper completed a
22-orbit mission of 34 and one-half
hours, triumphantly ringing down the

�curtain on Project Mercury.
Dr. Mueller was a witness to, rather
than a participant in, NASA's
manned
flight program at the time of the
Mercury space spectaculars, although
he was deeply involved in other aspects
of aerospace technology. During the
five years before he joined NASA in
1963, he was associated with Space
Technology Laboratories, Inc., serving successively as director of the
electronics labs, program director of
the "Able" space program, vice president of space systems management,
and finally vice president for research
and development. I n this last position, he had overall responsibility for
the technical operations of the company. While at STL, Dr. Mueller
headed the design, development and
testing efforts of the systems and components for Atlas, Titan, Minuteman
and Thor ballistic missiles. He also
played a major role in the development of Pioneer I, the United States'
first successful space probe, and had
overall responsibility for several other
space projects, including Explorer VI
and Pioneer v, and for the establishment of the Air Force satellite track- Gemini Twin Ed White maneuvers 120 miles above the Pacific Ocean, connected to Gemini
4 spacecraft by an umbilical cord. Extravehicular activity, operational term for walking
ing network.
in space, is a basic technique required for manned space flight capability.

Mercury's Dividends

Dr. Mueller adds thisfootnote to the story on the path to the moon, and forged
Mercury which had j u t con- ahead with the second phase, Project
cluded when he became Associate Adminis- Gemini.
Named for the twin-star constellatratorfor the Ofice of Manned Space Flight:
"Originally, NASA assigned only two broad tion of Castor and Pollux, Project
Gemini called for a two-man spacemission objectives to Project Mercury-jrst,
to investigate man's ability to survive and craft system to conduct orbital flights
perform in the space environment; and sec- around the earth for up to two weeks'
ond, to develop the basic space technology duration. Twelve flights were schedand hardware for manned space JEight pro- uled for the Gemini series-ten of
prime
grams to come. But the dividends Mercuy them manned. One of NASA's
paid went beyond those basic goals. Thty objectives was to determine man's
include the development of a NASA manage- performance and behavior during
ment system to carryforward more advanced prolonged orbital flights, including
manned spacejight ventures; exploration of his ability to pilot and control his
the fundamentals of spacecra) re-enty; spacecraft. Other mission objectives
raising a family of launch vehiclesfrom ex- were orbital rendezvous; docking or
isting rockets that led to new booster designs; joining two spacecraft, and maneuverexpansion of the aerospace industry through ing the joined spacecraft as one unit;
astronaut activity outside an orbiting
NASA contracts; setting up an earthgirdling tracking system, and training a spaceship, and a series of scientific excadre of astronauts for future space explora- periments.
Dr. Mueller and his capable
tion programs."
Small wonder, then, that NASA was manned space flight crew are justifiencouraged by this successful first step ably proud of the stand-out achieve-

of Project

ments of the Gemini program and the
early successes of Apollo-Saturnachievements which can only be described as spectacular in light of the
stepped-up pace of the United States
manned space flight schedule. In the
spring of 1964 the first unmanned test
flight of the Gemini-Titan 11 space
vehicle was flown. By spring of this
year Gemini astronauts had logged
more than 1,300 man-hours in space,
and traveled some 11 million milesthat's almost fifty times the distance
from the earth to the moon.
Other mission objectives have been
fulfilled. Last year, during the third
revolution of an extended earth orbital
flight, Gemini 4 Astronauts James
McDivitt and Ed White carried out
the first extravehicular activity in the
manned space flight program. White
left the spacecraft to walk in space,
becoming a human satellite orbiting
the earth at an altitude of 120 miles.
Command pilot McDivitt remained

�Mueller, is that in every case, the men returned in excellent physical and mental
health. From the medical point of view the
jights show that well-trained men can live
and work in space for extended periods of
time, and the condition of weightlessness
does not appear to cause any serious afterefects. 7 h e astronauts' state of health is
measured continuously, bbefoejight, during
j i g h t and after their return. The overall
appraisal of NASA'smedical team is that
jights lasting a month or more are feasible.

I

Talented Management

Another noteworthy aspect of the
Gemini program is the talented management Dr. Mueller gives it. A little
more than a year ago, the program
was behind sdhedule, and there
was.. ...
"rave
concern about the possibility of
cost overruns. "We instituted a new
kind of contract administration," Dr.
Mueller remarked, "one in which the
profit of the Gemini program contractors is ,tied to their total perform-

Astronaut David Scott's camera captures orbiting Agena target docking vehicle as Gemini
8 spacecraft hovers about 190 feet away. Michael Collins and John Young maneuvered
near this same rocket during the Gemini 10 mission in July.

a t the controls with the difficult task
of keeping the spacecraft in a stable
attitude so that White would have a
constant and dependable point of reference to gauge his movements outside the capsule.
Orbital rendezvous was another
mission objective. Dr. Mueller recalled
the events which led to its achievement: "Within hours after Tom Love11
and Ed Borman took off on their twoweek Gemini 7 flight, preparations
began for launching their rendezvous
ship. Gemini 6 lifted off eleven days
later, with Wally Schirra and Tom
Stafford aboard. For five hours
Schirra a n d Stafford carried out a
complicated series of maneuvers.
Then, 185 miles above the Pacific,
they rendezvoused with Gemini 7.
Despite their speeds of 17,000 mile
a n hour, Schirra was able to guide his
spacecraft to within one foot of the
other. I might add that he was aided
by some very fine guidance and con-

trol equipment." Docking in space
was added to the plus side of the mission objective ledger in March of this
year after Astronauts Neil Armstrong
and David Scott docked their Gemini
8 spacecraft with an unmanned Agena
target vehicle.
Among the most remarkable
Gemini space successes was the Gemini
10 flight in late July. During that
record-setting three days, astronauts
Michael Collins and John Young
chased and linked up with a fuel supply Agena rocket and spent nearly 39
hours linked with the other statellite;
fired the rocket engine of the captured
Agena for the first manned launching
at orbital altitudes; soared to an orbit
of nearly 475 miles-deeper
into
space than man has ever gone; opened
the hatch of their capsule to the space
environment three times; maneuvered
near the orbiting Agena 8 rocket and
retrieved a package from it, and accomplished a 25-minute space walk.

trol. I think the operation of these
contracts has constituted one of the
finest examples of the proper working
of the free enterprise system."
The manned space flight program
has a valuable asset in the person of
George Mueller (pronounced Miller).
The "Show Me" state native received
a bachelor's degree in electrical engineering from the Missouri School of
Mines, then moved to Indiana to earn
a master's in the same discipline at
Purdue University. H e came east to
the Bell Telephone Laboratories
where he conducted television and
microwave and measuring experiments, and pioneered in the measurement of radio energy from the sun, in
microwave propogation, and in the
design
- of low field electrons. After a
stint of graduate study a t Princeton
University, George Mueller joined the
faculty of Ohio State University as
assistant professor of electrical engineering; later he bacame a full professor. At Ohio State, he conducted
research on the study and design of
broadcast and dielectric antennas,
cathode emission, low field magne-

�trons and traveling wave tubes, and
was awarded a P H . D in physics. The
next stop was Redondo Beach, California and the Space Technology
Laboratories where Dr. Mueller spent
the next five years before he assumed
direction of NASA'smanned space
flight program.
Dr. Mueller was one of the originaLurs of the concept and design of the
Telebit digital telemetry system. He
holds seven patents in electrical engineering, and is the author of more
than 20 technical papers. With E. R.
Spangler, he is co-author of a book,
"Communication Satellites." Dr.
Mueller is a n active participant in
national and international conferences
on space communications and space
technology.
Successful Stepping Stones

Uprated Saturn I on Cape Kennedy launch pad just before it successfully boosted unmanned Apollo spacecraft into a 300-mile high suborbital flight. The February 26, 1966
flight marked the first test in space of the Apollo command and service module, the CKIH
which will house America's moon explorers.

30

The Mercury and Gemznz space successes
are the steppzng stones to the Apollo moon
landzng mzssions and to other space operatzons of the future. The Ofice of Manned
Space Flzght zs movzng ahead wzth Gemznz
and expects to accomplzsh all the remaznzng
program obyctzves zn the addztzonalJzghts
scheduled over the remaznzng months of thzs
year. Szmultaneously, remarkable progress
zs also bezng made zn the Apollo program,
the largest research and development program the Unzted States has ever undertaken.
Project Apollo calls for NASA to develop two major launch vehicles and
a three-man spacecraft; to assemble a
nation-wide government-industry
team; to construct a complex of advanced launch facilities, and to carry
on a comprehensive testing program
. . . all on a coordinated schedule.
Under George Mueller's direction,
they're doing just that.
America's moon men will make
the half-million-mile round trip in the
three-man Apollo spacecraft now
under development at NASA's
Manned
Spacecraft Center (MSC)
near Houston,
Texas, where a cattle range was converted to a modern installation in less
than three years. Dr. Robert Rowe
Gilruth directs MSC,an organization
responsible for the design, development and testing of manned spacecraft and associated systems, for the
selection and training of astronauts,

�for support.of manned flight operations and for managing the work of
the industrial team which shares the
work load.
The MSC Giant

Probably the biggest thing at MSG
these days is the Apollo spacecraft.
Weighing in at 45 tons and standing
84 feet tall, the spacecraft is divided
into three sections-a command module, a service module and a lunar
module. T h e command module,
something like the crew compartment
of a commercial jet airliner, is designed so that the astronauts can eat,
sleep and work and relax in a shirt
sleeve environment. It is furnished
with life support equipment and is
chock full of controls and instruments
to enable the astronauts to maneuver
their craft. Since the command module will return to earth, it is constructed to withstand the tremendous
deceleration forces and intense heating caused by re-entry. It's a room
with a view. The double-walled pressurized chamber has three windows
in front of the astronauts' couch, and
two more windows on the side. A
tower-like launch escape system
perches atop the command module
for use in an emergency launch situation. It is jettisoned after the second
stage of the launch vehicle ignites.
Beneath the command compartment is the service module, a 128foot diameter cylinder weighing
about 50,000 pounds. Inside are supplies, fuel and an engine which the
astronauts use to maneuver their craft
into and out of lunar orbit or alter
their course and speed in space.
Once the Apollo spacecraft is orbiting around the moon, two of the
astronauts crawl through a hatch into
the bug-like third section, the lunar
module. "The bug" detaches from the
combined command-service module
and descends to the moon's surface.
The lunar module has its own complete guidance, propulsion, computer,
communications and environmental
control systems. The vehicle has two
stages. The bottom stage contains the
rocket engine and spidery legs which
extend for lunar landing. This unit is
detachable and forms the "launch

platform" for the upper stage which
houses the astronauts. Attached to the
upper stage is the rocket engine which
America's lunar explorers will ignite
when they are ready to rejoin the
hovering command-service module.
After the astronauts crawl back into
the command module, the lunar
module is jettisoned and the trio heads
back to earth. Just before re-entry,
the service module is also detached.
Parachutes are deployed to slow down
the re-entry forces just before splashdown.
The Manned Spacecraft Center is
an outstanding example of the advanced facilities, unique in both size
and capability, which NASA has constructed to meet Apollo program
objectives. MSC is the home of the
Mission Control Center-an office/
laboratory combination where engineers, scientists and technicians team
up with computers to direct operations
of manned space flights. Support functions at the Center include recovery
control, recovery communications,
meteorology and trajectory data, network support and monitoring devices
for life support and vehicle systems.
MSC is also the site of the country's
largest "man-rated" space environment chamber. Altitudes of about 80
miles can be simulated in this chamber and spacecraft can be subjected
to temperatures and solar radiation
conditions that will be experienced
on a flight to the moon.
Muscle for Apollo

The muscle for the Apollo program
is provided by the Saturn family of
heavy launch vehicles. Development
of these mammoth boosters is the responsibility of Dr. Werner von Braun,
director of NASA'sGeorge C. Marshall
Space Flight Center (MSFC)
at Huntsville, Alabama. Some 7,000 MSFC employees are engaged in the research
and development of the Saturn workhorses-from conception through design, development, fabrication and
assembly of the hardware, and testing.
Baby of the Saturn family is the
120-foot tall, 2 1.5-foot diameter Saturn I. It has been flight tested with a
perfect record of ten successes in ten
launches, a record without parallel in

the development and operation of
large launch vehicles. In unmanned
test flights Saturn I has placed test
versions of the command and service
modules of the Apollo spacecraft into
orbit. With its cluster of eight rocket
engines burning refined kerosene and
liquid oxygen, Saturn I develops 1.5
million pounds of thrust in its first
stage. Its second stage has six engines
which burn liquid hydrogen and liquid oxygen, producing 90,000 pounds
total thrust.
Also under development at MSFC is
the uprated Saturn I with an improved
first stage version of the Saturn I, and
a new and more powerful second
stage. With 1.6 million pounds booster
thrust, and 200,000 pounds second
stage thrust, the uprated Saturn I will
boost Astronauts Virgil Grissom, Ed
White and Roger Chaffee into earth
orbit for a long duration mission of
up to two weeks.
Saturn V Moon Rocket

Big Daddy in the Texas-size booster
corral is the Saturn v, a vehicle of
gigantic size and power. The Saturn v
moon rocket tops the 250-foot high
Statue of Liberty by 31 feet. Assembled on the launch pad with the three
modules of the Apollo spacecraft on
top, the moon rocket stands 364 feet
tall and weighs about six million
pounds. Its first stage has a diameter
of 33 feet, and is powered by a cluster
of five engines packing a wallop of 7.5
million pounds of thrust. Another million pounds of thrust will be furnished
by a cluster of five engines in the second stage. On top of the first two is
the third stage which is identical to
the uprated Saturn r second stage.
The Saturn's first stages are built
by NASA's
Michoud Assembly Facility
in New Orleans, Louisiana, and later
are floated by barge into Mississippi
for rumbling static tests at NASA's
Mississippi Test Facility. The second
and third stages of Saturn v are built
in California. At Mississippi the gigantic stages are lifted directly from
the barges onto the test stands, held
captive and run through full strength,
full duration "hot" firings. After testing, the rocket stages are replaced on
the barges and floated via a complex

�canal system to Cape Kennedy.
Other flight equipment, manufactured and tested at NASA's
nation-wide
facilities, are also shipped to the John
F. Kennedy Space Center (KSC)in
Florida, where an integrated governmenthndustry team takes over assembly, checkout and launch of the
moon-bound space ships under the
direction of Dr. Kurt Debus. KSC, the
major launch organization for manned
and unmanned space missions, is the
focal point for the development of
launch philosophy, procedures, technology and facilities. So huge and so
complicated are the Apollo-Saturn
launch vehicles that NASA had to devise
new approaches to assembling them.
Thus a new generation of space
facilities was born. Towering over the
Kennedy Space Center terrain is the
VAB (vehicle assembly building), a
524-foot high plant where four Saturn
rockets can be assembled simultaneously and checked out stage by stage.
Scheduled for completion this year,
the VAB provides for assembly and
checkout of the moon rockets in a con-

trolled environment which eliminates
the hazards weather could wreak on
rockets and time schedules.
After assembly, the Saturn v rocket,
its mobile launch tower and mobile
platform leave the VAB through a
doorway 456 feet high. A monstrous
tractor trundles the works to the
launch pad. The Kennedy moonport
will have two Saturn v launch pads,
with the capability of launching about
six vehicles a year after 1968.
The pieces in this massive jigsaw
puzzle called manned space flight are
falling into place. Excellent progress
is being made on the development of
the Saturn launch vehicle; hardware
is being assembled for a 1967 test
flight of the Apollo lunar module,
astronauts are being trained.
At the pivotal halfway point in the
program this spring, Dr. George
Mueller, the man who manages this
engineering enterprise had this to say:
"The government/industry team required to carry out the manned flight
program is in place and working. The
program is on schedule, a schedule

set when the program began. And, if
progress continues, we will accomplish the manned lunar landing and
safe return of America's astronauts in
this decade."
But Dr. Mueller doesn't want to stop
there. He has emphasized many times that
the lunar mission is just one of the many
possible misszons which can use the capabilities of the Apollo-Saturn program. "The
j r s t successful manned lunar landing will
just scratch the surface. Its greatest achievement will be a demonstration ofthe ability
to travel a quarter of a million miles from
earth, land on that heavenly body and
return safe&amp; here. Other journeys must follow. W e must use the Saturn rockets, the
Apollo spaceship and the launch facilities
. . . over and over again to gain the fullest
return on our investment.
"We can make many jlights in orbit
about the earth, about the moon or to the
moon's surface. By using our capabilities
efectively and imaginatively, we will be
able to carry out a wide variety of missions
of great scientiJic value and of direct bent$
to mankind."

In Mission Operations Control Room at the Manned Spacecraft Center near Houston, Texas, personnel monitor Gemini space flight.
Mission Control Center is the focal point of a global network of tracking and communications stations which provide centralized
control for orbital flights.

32

�</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="20176">
                <text>spc_stnv_000064</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20177">
                <text>"A Nation Goes to the Moon."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20178">
                <text>Written by NASA Office of Manned Space Flight Associate Administrator George E. Mueller, this is an article from &lt;i&gt;G. E. Challenge&lt;/i&gt;, Fall 1966, page 26 to 32.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20179">
                <text>Mueller, G. E. (George Edwin), 1918-2015</text>
              </elementText>
              <elementText elementTextId="20180">
                <text>General Electric 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="20181">
                <text>1966-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20182">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20183">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20184">
                <text>Mueller, G. E. (George Edwin), 1918</text>
              </elementText>
              <elementText elementTextId="20185">
                <text>Project Apollo (U.S.)</text>
              </elementText>
              <elementText elementTextId="20186">
                <text>United States. National Aeronautics and Space Administration--History</text>
              </elementText>
              <elementText elementTextId="20187">
                <text>Manned space flight</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20188">
                <text>Clippings</text>
              </elementText>
              <elementText elementTextId="20189">
                <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="20190">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20191">
                <text>Box 19, Folder 6</text>
              </elementText>
              <elementText elementTextId="205815">
                <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="20193">
                <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="20194">
                <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="20195">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10389" public="1" featured="0">
    <fileContainer>
      <file fileId="9197">
        <src>https://digitalprojects.uah.edu/files/original/20/10389/ssfmanewteltec_031307114348.pdf</src>
        <authentication>4ef1f7ca06204154ca271b8f0509b50c</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="155799">
                <text>ssfmanewteltec_031307114348.pdf</text>
              </elementText>
              <elementText elementTextId="155800">
                <text>spc_stnv_000845</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155801">
                <text>"A new telemetry technique."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155802">
                <text>A technique new to telemetry is discussed which promises to alleviate an enigma facing the telemetry engineer : How to adequately transmit the avalanche of vibration and other wideband data desired in the development phase of large missiles and launch vehicles. The data channels are stacked in the frequency spectrum as single sideband subcarriers which frequency modulate the RF carrier. The system design utilizes to advantage the statistical properties of vibration data to achieve maximum data transmission efficiency from the available RF carrier deviation. However, in contrast to proposed statistical predigestion techniques, the data is transmitted in raw form.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155803">
                <text>Frost, Walter O.</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="155804">
                <text>1961-10-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155805">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155806">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155807">
                <text>Aerospace telemetry</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155808">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155809">
                <text>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="155810">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155811">
                <text>Box 6, Folder 7</text>
              </elementText>
              <elementText elementTextId="210199">
                <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="155813">
                <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="155814">
                <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="155815">
                <text>spc_stnv_000825_000849</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="155816">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16694</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1944" public="1" featured="0">
    <fileContainer>
      <file fileId="1831">
        <src>https://digitalprojects.uah.edu/files/original/55/1944/uah_hockey_003.pdf</src>
        <authentication>b1e2a4de527a01d2b6067c03a203fb69</authentication>
      </file>
    </fileContainer>
    <collection collectionId="55">
      <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="16121">
                  <text>UAH History 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="17113">
                  <text>UAH History Collection</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="39065">
                <text>uah_hockey_002</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39066">
                <text>"A New Year's Maine Attraction."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45708">
                <text>This flier advertises a trip to Maine for UAH hockey fans to see "the Chargers capture the top-ranked Black Bears of the University of Maine." Tours of Maine scenery and sites, a "New England Style Dinner," lodging, and transportation are offered in the package. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45709">
                <text>University of Alabama in Huntsville. Division of Continuing Education</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="45710">
                <text>1989-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="45711">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45712">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="45713">
                <text>Continuing education--United States</text>
              </elementText>
              <elementText elementTextId="45714">
                <text>Hockey</text>
              </elementText>
              <elementText elementTextId="45715">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="45716">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="45717">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45718">
                <text>Fliers (Printed matter)</text>
              </elementText>
              <elementText elementTextId="45719">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45721">
                <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="45722">
                <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="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="206351">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2337" public="1" featured="0">
    <fileContainer>
      <file fileId="4010">
        <src>https://digitalprojects.uah.edu/files/original/20/2337/spc_stnv_000109.pdf</src>
        <authentication>0688c277ff575a7f8a5578951cf23151</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="46387">
                <text>spc_stnv_000109</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46389">
                <text>"A Practical Approach to the Optimization of the Saturn V Space Vehicle Control System Under Aerodynamic Loads."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46390">
                <text>This paper includes the equations for the bending moment of a launch vehicle with the effects of bending and sloshing dynamics. It also includes a comparison between the bending moment response envelope of the measure winds and the bending moment response of the MSFC synthetic wind profile.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46391">
                <text>Ryan, Robert S. (Robert Samuel), 1925-</text>
              </elementText>
              <elementText elementTextId="46392">
                <text>Teuber, Dieter</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="46393">
                <text>1965-07-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46394">
                <text>Optimization</text>
              </elementText>
              <elementText elementTextId="46395">
                <text>Spacecraft control</text>
              </elementText>
              <elementText elementTextId="46396">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="46397">
                <text>Saturn Project (U.S.)</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="46400">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="46401">
                <text>Box 14, Folder 30</text>
              </elementText>
              <elementText elementTextId="206427">
                <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="46402">
                <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="46403">
                <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="46404">
                <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="46405">
                <text>&lt;a href="%E2%80%9Dhttp%3A//libarchstor.uah.edu:8081/repositories/2/archival_objects/17177%E2%80%9D"&gt;View item in ArchivesSpace&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="46610">
                <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="46611">
                <text>Memorandums</text>
              </elementText>
              <elementText elementTextId="46612">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="46613">
                <text>Text</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="89515">
                <text>NASA TM X-53698</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2338" public="1" featured="0">
    <fileContainer>
      <file fileId="4011">
        <src>https://digitalprojects.uah.edu/files/original/20/2338/spc_stnv_000110.pdf</src>
        <authentication>73fb9d367015e683f202a542837d94c6</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="46406">
                <text>spc_stnv_000110</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46408">
                <text>"A Prime Contractor's Reliability Program for Components/Parts for the Douglas S-IVB Stage Project."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46409">
                <text>This paper, presented at the fifth annual Reliability and Maintainability Conference in New York City, contains a "prime contractor's reliability program for components/parts for the Douglas S-IVB stage project." These parts include special flight critical items and their complementary reliability engineering program plan is outlined in this paper.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46410">
                <text>Wilson, R. B.</text>
              </elementText>
              <elementText elementTextId="46411">
                <text>Hug, N.L.</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="46412">
                <text>1966-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46413">
                <text>Quality control</text>
              </elementText>
              <elementText elementTextId="46414">
                <text>Reliability engineering</text>
              </elementText>
              <elementText elementTextId="46415">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="46416">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="46417">
                <text>Saturn S-4B stage</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="46418">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="46419">
                <text>Box 18, Folder 5</text>
              </elementText>
              <elementText elementTextId="206428">
                <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="46420">
                <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="46421">
                <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="46422">
                <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="46423">
                <text>&lt;a href="%E2%80%9Dhttp%3A//libarchstor.uah.edu:8081/repositories/2/archival_objects/17500%E2%80%9D"&gt;View this item record in ArchivesSpace&lt;/a&gt;</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="46604">
                <text>Douglas Paper No. 3794.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="46605">
                <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="46606">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="46607">
                <text>Still image</text>
              </elementText>
              <elementText elementTextId="46608">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9393" public="1" featured="0">
    <fileContainer>
      <file fileId="8183">
        <src>https://digitalprojects.uah.edu/files/original/132/9393/r10_02-06.pdf</src>
        <authentication>b2022dcdc7fd73903b40e9d1065b2786</authentication>
      </file>
    </fileContainer>
    <collection collectionId="132">
      <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="142296">
                  <text>Series 10: Books and Pamphlets</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="142297">
                  <text>Series 10: Books and Pamphlets</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="142590">
                <text>r10_02-06</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="142591">
                <text>Series 10, Box 2, Folder 6</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142592">
                <text>"A Profile of Gabriel Hanby" by Blount County Historical Society, 1962</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="142593">
                <text>r10-211020</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10698" public="1" featured="0">
    <fileContainer>
      <file fileId="9264">
        <src>https://digitalprojects.uah.edu/files/original/20/10698/Progplaneart_012709164341.pdf</src>
        <authentication>bfd2bb526157cf3d96d008ec773907cd</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="161927">
                <text>Progplaneart_012709164341.pdf</text>
              </elementText>
              <elementText elementTextId="161928">
                <text>spc_stnv_000621</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161929">
                <text>"A Program plan for earth orbital space astronomy."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161930">
                <text>Manned space flight offers the opportunity to couple the astronaut/scientist's ability to select and process data and to calibrate, modify and repair instruments with the vantage point for astronomical observations provided by a platform located above the Earth's atmosphere.  This paper briefly examines the role which manned space flight may play in the 1970-1990 time period in meeting astronomy research needs.  The instruments and facilities which appear feasible for that period are described.;  Paper presented by J. R. Olivier, National Aeronautics and Space Administration, George C. Marshall Space Flight Center and H. L. Wolbers, Ph.D, McDonnell Douglas Astronautics Company - Western Division, Advance Space and Launch Systems.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161931">
                <text>Olivier, J. R.</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="161932">
                <text>1968-11-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="161933">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161934">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="161935">
                <text>Manned space flight</text>
              </elementText>
              <elementText elementTextId="161936">
                <text>Technology utilization</text>
              </elementText>
              <elementText elementTextId="161937">
                <text>Astronomical observatories</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161938">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="161939">
                <text>Program Plans</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="161940">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="161941">
                <text>Box 29, Folder 11</text>
              </elementText>
              <elementText elementTextId="210415">
                <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="161943">
                <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="161944">
                <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="161945">
                <text>spc_stnv_000600_000624</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="161946">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17997</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13828" public="1" featured="0">
    <fileContainer>
      <file fileId="10352">
        <src>https://digitalprojects.uah.edu/files/original/193/13828/Defense_Billboard_31_001.pdf</src>
        <authentication>32d541eb570df3a0e7b6b44aed4e1d98</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197409">
                    <text>American Forces Information Service, Department ol Defense
601 N. Fairfax Street, Room 312, Alexandria, VA 22314-2007

�</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="196074">
                <text>Defense_Billboard_31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196075">
                <text>"A Promotion...A Party...A Pity"</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="196076">
                <text>D2.9:P94</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196077">
                <text>Woman's purse and shoe on street outside of a bar as a cab drives away</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196078">
                <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="196079">
                <text>1990-08-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="196080">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196081">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="196082">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="196083">
                <text>Drunk driving</text>
              </elementText>
              <elementText elementTextId="196084">
                <text>Alcoholic beverages</text>
              </elementText>
              <elementText elementTextId="196085">
                <text>Nightlife</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196086">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="196087">
                <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="196088">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="196089">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="196090">
                <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="196091">
                <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="196092">
                <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="196093">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10672" public="1" featured="0">
    <fileContainer>
      <file fileId="9257">
        <src>https://digitalprojects.uah.edu/files/original/20/10672/Realtimeopersyst_101507115951.pdf</src>
        <authentication>29c0579a15c0eddd0f4d38fc8ad1481a</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="161391">
                <text>Realtimeopersyst_101507115951.pdf</text>
              </elementText>
              <elementText elementTextId="161392">
                <text>spc_stnv_000642</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161393">
                <text>"A real time operating system for the Saturn V launch computer system."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161394">
                <text>Presentation aimed to encourage a final check on the Saturn V project before its first launch to ensure safety and success.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161395">
                <text>Palm, Frank R.</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="161396">
                <text>1966-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="161397">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161398">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="161399">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="161400">
                <text>Real-time data processing</text>
              </elementText>
              <elementText elementTextId="161401">
                <text>Automatic test equipment</text>
              </elementText>
              <elementText elementTextId="161402">
                <text>Real time operation</text>
              </elementText>
              <elementText elementTextId="161403">
                <text>Operating systems</text>
              </elementText>
              <elementText elementTextId="161404">
                <text>Computer programming</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161405">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="161406">
                <text>Presentations</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="161407">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="161408">
                <text>Box 17, Folder 69</text>
              </elementText>
              <elementText elementTextId="210389">
                <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="161410">
                <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="161411">
                <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="161412">
                <text>spc_stnv_000625_000649</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="161413">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17492</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
