<?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=108&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-04T04:30:51+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>108</pageNumber>
      <perPage>20</perPage>
      <totalResults>8239</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10878" public="1" featured="0">
    <fileContainer>
      <file fileId="9397">
        <src>https://digitalprojects.uah.edu/files/original/20/10878/Liquhydr_110110140123.pdf</src>
        <authentication>a3a41e72af2bd4dc1311e88a6598689b</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="165394">
                <text>Liquhydr_110110140123.pdf</text>
              </elementText>
              <elementText elementTextId="165395">
                <text>spc_stnv_000404</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165396">
                <text>"Liquid Hydrogen."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165397">
                <text>Review detailing the use of liquid hydrogen in Saturn rockets.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165398">
                <text>Douglas Aircraft Company</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="165399">
                <text>1962-05-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="165400">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165401">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="165402">
                <text>Liquid hydrogen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165403">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="165404">
                <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="165405">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210570">
                <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="165407">
                <text>Is part of: Saturn S-IV engines.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165408">
                <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="165409">
                <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="165410">
                <text>spc_stnv_000400_000424</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10725" public="1" featured="0">
    <fileContainer>
      <file fileId="9316">
        <src>https://digitalprojects.uah.edu/files/original/20/10725/newsreleaseliqhydrog_041207113432.pdf</src>
        <authentication>a4e7fd99fdc6931a87d2a6edcfa70b4e</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="162473">
                <text>newsreleaseliqhydrog_041207113432.pdf</text>
              </elementText>
              <elementText elementTextId="162474">
                <text>spc_stnv_000550</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="162475">
                <text>"News release : Liquid Hydrogen."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="162476">
                <text>Press release covering the nature and use of liquid hydrogen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="162477">
                <text>Douglas Aircraft Company, Inc.</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="162478">
                <text>1962-05-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="162479">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="162480">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="162481">
                <text>Liquid hydrogen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="162482">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="162483">
                <text>Press Releases</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="162484">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210442">
                <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="162486">
                <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="162487">
                <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="162488">
                <text>spc_stnv_000550_000574</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11029" public="1" featured="0">
    <fileContainer>
      <file fileId="9514">
        <src>https://digitalprojects.uah.edu/files/original/20/11029/douairnewreldisintgroqualtesprofrosIVsta_041107131816.pdf</src>
        <authentication>bd52a42d30528b2ac04804b237f3a84b</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="168437">
                <text>douairnewreldisintgroqualtesprofrosIVsta.pdf</text>
              </elementText>
              <elementText elementTextId="168438">
                <text>spc_stnv_000258</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168439">
                <text>Douglas Aircraft news release.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168440">
                <text>ABSTRACT: Discusses intensive ground qualification testing program for S-IV stage.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168441">
                <text>Douglas Aircraft Company, Inc.</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="168442">
                <text>1964-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="168443">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168444">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="168445">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168446">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="168447">
                <text>Press Releases</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="168448">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210721">
                <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="168450">
                <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="168451">
                <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="168452">
                <text>spc_stnv_000250_000274</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11030" public="1" featured="0">
    <fileContainer>
      <file fileId="9513">
        <src>https://digitalprojects.uah.edu/files/original/20/11030/dougairnewsrel_071107103358.pdf</src>
        <authentication>f1454b271274d8fe293f623505a3f774</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="168453">
                <text>dougairnewsrel.pdf</text>
              </elementText>
              <elementText elementTextId="168454">
                <text>spc_stnv_000259</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168455">
                <text>Douglas Aircraft news release.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168456">
                <text>ABSTRACT: Discusses intensive ground qualification testing program for S-IV stage.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168457">
                <text>Douglas Aircraft Company, Inc.</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="168458">
                <text>1964-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="168459">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168460">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="168461">
                <text>Saturn S-4 stage</text>
              </elementText>
              <elementText elementTextId="168462">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="168463">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="168464">
                <text>Press Releases</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="168465">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210722">
                <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="168467">
                <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="168468">
                <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="168469">
                <text>spc_stnv_000250_000274</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2345" public="1" featured="0">
    <fileContainer>
      <file fileId="4018">
        <src>https://digitalprojects.uah.edu/files/original/20/2345/spc_stnv_000117.pdf</src>
        <authentication>51a201750a9890d8cac13ae810163818</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="46522">
                <text>Asecolookatmanmachandautotestoper_111607151040.pdf</text>
              </elementText>
              <elementText elementTextId="46523">
                <text>spc_stnv_000117</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46524">
                <text>"A Second Look at Man, Machine, and Automatic Test Operations."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46525">
                <text>A summary found following the errata page reads: "This paper presents a second look at the subject of the man-machine relationship in automatic test operations. 'Man, Machine, and Automatic Test Operations' was presented by the writer at Battelle Memorial Institute in November of 1963...It is the purpose of this second look at the man-machine interface to pinpoint those concepts which have proven their worth with time and those concepts which have proven to be weak, and as a result modified with time." This paper was prepared by George F. Meister, Jr. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46526">
                <text>Douglas Aircraft Company, Inc. Missile and Space Systems Division.</text>
              </elementText>
              <elementText elementTextId="46527">
                <text>Meister, George F., Jr.</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="46528">
                <text>1966-11-09</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="46529">
                <text>Automatic test equipment</text>
              </elementText>
              <elementText elementTextId="46530">
                <text>Human-computer interface</text>
              </elementText>
              <elementText elementTextId="46531">
                <text>Human-machine systems</text>
              </elementText>
              <elementText elementTextId="46532">
                <text>Launch vehicles (Astronautics)</text>
              </elementText>
              <elementText elementTextId="46533">
                <text>Saturn Project (U.S.) </text>
              </elementText>
              <elementText elementTextId="88691">
                <text>Huntington Beach (Calif.)</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="46535">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="46536">
                <text>Box 19, Folder 33</text>
              </elementText>
              <elementText elementTextId="206435">
                <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="46537">
                <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="46538">
                <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="46539">
                <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="46540">
                <text>&lt;a href="%E2%80%9Dhttp%3A//libarchstor.uah.edu:8081/repositories/2/archival_objects/17554%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="46564">
                <text>Douglas Paper No. 3941</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="46565">
                <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="46566">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="46567">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="46568">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10691" public="1" featured="0">
    <fileContainer>
      <file fileId="9271">
        <src>https://digitalprojects.uah.edu/files/original/20/10691/presrelsacrcaloct4_041207114716.pdf</src>
        <authentication>2b355167cd1c0472d1af3da2f11687cf</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="161797">
                <text>presrelsacrcaloct4_041207114716.pdf</text>
              </elementText>
              <elementText elementTextId="161798">
                <text>spc_stnv_000613</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161799">
                <text>"Douglas Aircraft Company Press release."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161800">
                <text>Press release covering the static firing of the S-IV rocket for a full seven minutes.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161801">
                <text>Douglas Aircraft Company.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="161802">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161803">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="161804">
                <text>Saturn S-4 stage</text>
              </elementText>
              <elementText elementTextId="161805">
                <text>RL-10 engines</text>
              </elementText>
              <elementText elementTextId="161806">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161807">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="161808">
                <text>Press Releases</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="161809">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210408">
                <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="161811">
                <text>Is part of: Letter to Mr. David L. Christensen.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161812">
                <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="161813">
                <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="161814">
                <text>spc_stnv_000600_000624</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10280" public="1" featured="0">
    <fileContainer>
      <file fileId="9185">
        <src>https://digitalprojects.uah.edu/files/original/20/10280/thethorhis.pdf</src>
        <authentication>6d79fc6a4422cc33f30a8dec134415e6</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="153615">
                <text>Thorhist.pdf</text>
              </elementText>
              <elementText elementTextId="153616">
                <text>spc_stnv_000909</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153617">
                <text>The History of Thor.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153618">
                <text>This history is intended as a quick orientation source and as a ready-reference for review of the Thor and its systems.  The report briefly states the development of Thor, summarizes and chronicles Thor missile and booster launchings, provides illustrations and descriptions of the vehicle systems, relates their genealogy, explains some of the performance capabilities of the Thor and Thor-based vehicles used, and focuses attention to the exploration of space by Douglas Aircraft Company, Inc.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153619">
                <text>Douglas Aircraft Company. Missile and Space Systems Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153620">
                <text>1963-05-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="153621">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153622">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="153623">
                <text>Launch vehicles</text>
              </elementText>
              <elementText elementTextId="153624">
                <text>History</text>
              </elementText>
              <elementText elementTextId="153625">
                <text>Thor</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153626">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="153627">
                <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="153628">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="153629">
                <text>Box 8, Folder 28</text>
              </elementText>
              <elementText elementTextId="210115">
                <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="153631">
                <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="153632">
                <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="153633">
                <text>spc_stnv_000900_000924</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="153634">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17325</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10398" public="1" featured="0">
    <fileContainer>
      <file fileId="9104">
        <src>https://digitalprojects.uah.edu/files/original/20/10398/Sixengiclusof_102110102741.pdf</src>
        <authentication>1b903f24ca33d669815ff9c3e2b199b2</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="155990">
                <text>Sixengiclusof_102110102741.pdf</text>
              </elementText>
              <elementText elementTextId="155991">
                <text>spc_stnv_000804</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155992">
                <text>"Six-engine cluster of the Saturn S-IV rocket."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155993">
                <text>A press-release detailing the successfuly firing and the specfic launching information of the Saturn I-V rocket-launch.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155994">
                <text>Douglas Aircraft Company. Missile and Space Systems Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155995">
                <text>1962-10-04</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155996">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155997">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155998">
                <text>Rocket engines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155999">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="156000">
                <text>Press Releases</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="156001">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210208">
                <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="156003">
                <text>Is part of: Saturn S-IV engines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156004">
                <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="156005">
                <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="156006">
                <text>spc_stnv_000800_000824</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14409" public="1" featured="0">
    <fileContainer>
      <file fileId="10958">
        <src>https://digitalprojects.uah.edu/files/original/21/14409/001.pdf</src>
        <authentication>57c118af0b27289322b6f8f251bd3c0e</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="215911">
                    <text>NASA Contractor Report 3942

Human Performance Issues Arising
From Manned Space Station Missions

William K. Douglas

CONTRACT NAS2-11725
OCTOBER 1986

fVJASA

��SK (.58
NASA Contractor Report 3942

Human Performance Issues Arising
From Manned Space Station Missions

William K. Douglas

McDonnell Douglas Astronautics Company
Huntington Beach, California

Prepared for
Ames Research Center
under Contract NAS2-11723

fUASA

National Aeronautics
and Space Administration

Scientific and Technical
Information Branch
1986

��CONTENTS

SUMMARY
INTRODUCTION
METHOD
MECHANICS
SAFEGUARDING CONFIDENTIALITY
GENERAL FINDINGS
ANSWERS TO PREPARED QUESTIONS
SPONTANEOUS COMMENTS
APPENDIX A
APPENDIX B

��SUMMARY
Ten former NASA astronauts were Interviewed t o provide Information f o r use
In planning f u t u r e space f l i g h t missions.

Although no s t a t i s t i c a l analysis of

t h e material was performed, t h e responses do provide Insight Into numerous
aspects of space f l i g h t . Including psychological aspects, t r a i n i n g , command
s t r u c t u r e , health and comfort, physical aspects, and many o t h e r s .

The

responses by t h e Astronauts t o t h e questions a r e presented together with
coRTients by t h e researcher, himself a physician with long experience with the
space program.

Additionally, spontaneous matters t h a t came up 1n t h e

questioning periods a r e reported upon together with t h e r e s e a r c h e r ' s comments
on t h e s e a s w e l l .

The r e s u l t s , which maintain the s t r i c t c o n f i d e n t i a l i t y of

the Individual respondents, contribute t o t h e basic Information required by
those planning f u t u r e missions In space.
INTRODUCTION
This I s a report of information obtained during t h e course of separate
Interviews with ten former NASA astronauts t h a t took place during t h e f i r s t
half of 1984.

The purpose of t h e Interviews was t o e l i c i t Information t h a t

had not been previously reported and t h a t might open leads f o r f r u i t f u l
research endeavors applicable t o the United S t a t e s Space Station program.
There a r e many reasons why t h i s Information might not have been reported.
I t might have been forgotten during the Astronaut's p o s t - f l i g h t debriefing, o r
he might not have f e l t t h a t i t was Important a t t h a t time.

There may have

been personal reasons why he did not care t o mention some Items.

Some

material may have developed in h i s mind as a r e s u l t of r e f l e c t i o n s since h i s
f l i g h t and of h i s observations of f l i g h t a c t i v i t y t h a t have occurred since h i s
own mission.
Every e f f o r t has been made t o safeguard t h e c o n f i d e n t i a l i t y of t h e
inquiry, a s described in t h e section on c o n f i d e n t i a l i t y .

1

�METHOD
A 11st of fifty-one questions (Appendix A) was formulated by the
Investigator.

Published documents, discussions with NASA personnel, and the

Investigator's own personal knowledge of space f l i g h t human factors entered
Into the formulation of the questions.

Some changes were made In the l i s t of

questions as Insights were gained during the course of the Interviews.
The original thought was that each subject would be asked each question on
the l i s t , but I t soon became apparent that t h i s approach would not be the best
way t o proceed.

Some of the questions clearly referred t o specific programs.

Project ApoUo for example, and would be of l i t t l e use in Interviewing a
person whose experience was restricted t o an e a r l i e r program.

Further, I t was

seen that s t r i c t adherence t o the l i s t of questions would result In s t i l t e d ,
stereotyped replies - the questions became boring rather than stimulating.
After the f i r s t two o r three Interviews, I t was decided t o use the questions
only t o stimulate discussion.

Although some questions were given t o a l l ten

contacts, some were only given t o one or two. with each question being
presented t o an average of 6.2 contacts.

This I s somewhat misleading because

In certain Instances questions would stimulate answers t o l a t e r questions, and
the responses were combined.

(See Question 4)

Ames Research Center provided the Investigator with a l e t t e r of
Introduction (Appendix B), which described the program and I t s goals, and
which reviewed the background of the Investigator. The l e t t e r gave absolute
assurance that the Information given would be safeguarded In such a manner
that no statement could be attributed e i t h e r t o an Individual o r t o his
specific f l i g h t .
The contacts were each paid a consultant's fee of $50.00 per hour.
I t was originally Intended for Mr. Donald K. Slayton t o be present a t each
Interview so as t o take advantage of his background, training, and knowledge
of manned space f l i g h t operations.

I t proved nearly Impossible t o coordinate

the schedules of the Investigator, of Mr. Slayton, and of the contacts.

2

�without delaying the progress of the project to an unacceptable degree; Hr.
Slayton, therefore, was present during only two of the interviews.
The first interviews were with people known personally to the investigator
or to Hr. Slayton (or both).

These individuals made suggestions for

subsequent interviews.
MECHANICS
The contacts were first called by telephone and the purpose of the study
was explained to them.

If they consented to being interviewed (and some

declined because of their busy schedules), an appointment was made, and a copy
of the letter of introduction was mailed to them in sufficient time to allow
them to review it before the interview.
Because of the preconceived opinion of the investigator that the presence
of a tape recorder would be inhibitory to the free flow of information, the
original plan specifically excluded the taping of the interviews.

When the

first individual was contacted, and when it was explained to him that a tape
recorder would not be used, he said he felt the taking of handwritten notes
would be distracting to him.
interview.

He then asked that a recorder be used in his

When subsequent contacts were made, each person was given his

option of using a tape recorder or not.
reluctance to being taped.

None expressed even the slightest

One even asked for a copy of the tape for his

children.
In all cases the investigator traveled to the community where the contact
lived.

The interviews took place in the contact's office on three occasions,

in his home on three occasions, and in the investigator's hotel room on four
occasions.
The environment was very informal.
used only to stimulate discussion.
question was selected and asked.

As stated earlier, the questions were

When the conversation lagged, another
This usually resulted in a great deal more

spontaneous conversation.

3

�SAFEGUARDING CONFIDENTIALITY

Each contact was assured at the time of the initial telephone conversation
that anything he said would not be traceable to him or to his flight.

The

letter of Introduction contained these same assurances, and they were repeated
in the investigator's letter that forwarded the NASA letter of Introduction.
Finally, the subject was given the same assurances orally at the time of the
Interview.

It was apparent that most of them appreciated the assurances of

confidentiality and were probably more open In their discussions as a result
of those assurances.
After each Interview the tapes (12 In all) were brought back to the
Investigator's residence, where they have remained stored In a safe location.
They are identified only with a numerical code number.
does not appear on the cassette label.
material verbatim In most Instances.

The contact's name

The Investigator transcribed the
Paraphrasing was rarely used and then

only when It became necessary to clarify syntax that was peculiar to the oral
Interview situation.

There are a few portions of the tape that have not been

transcribed because they referred to the personal social relationships of the
contact and the Investigator.
The Investigator transcribed a11 the recorded material on an Apple He
personal computer In his home, using the Apple Writer II word processing
program.

No secretarial assistance was used In either transcribing the taped

material or In the preparation of this report.
tapes of these Interviews.

No other person has heard the

To facilitate preparation of this report, the

transcribed Interviews were printed on 104 single-spaced sheets.
than the Investigator has seen these typed pages.

No one other

When not In use. they are

kept In a combination-locked safe In the Investigator's office.
Each transcription Is saved on a magnetic disc, and duplicate discs have
been made and stored separately.

4

�GENERAL FINDINGS
The subjects were, without exception, extremely cooperative.
towards the investigator or the project was expressed.

No animosity

The investigator could

detect no evidence of conscious withholding of information.
A broad range of experienced people were interviewed, including persons
who had flown on all NASA programs, with the exception of the Space Shuttle.
Interviews were conducted with crew members from Mercury, Gemini, Apollo, and
Stcylab.

The Apollo contacts included men who had participated in the

Earth-orbiting phase of the project, and in the lunar landing phase.

One of

these latter contacts landed on the moon and another was a Command Module
Pilot who remained in lunar orbit alone during a lunar landing mission.
No meaningful statistical evaluation can be made for several reasons:
1.

The list of questions was not rigidly adhered to.

All subjects were

not asked all questions.
2.

Answers to questions were subjective in nature.

3.

Many spontaneous questions generated by the subject's comments evolved

on the spot.
interviews.

Some of these were not really applicable to subsequent
On the other hand, some of these spontaneously generated

questions were asked at subsequent interviews, but no effort was made to
contact earlier subjects to ask them to answer the newly generated questions.
4.

Only ten people were interviewed.

In this report the questions will be stated, and in cases where the
question was presented to several individuals, an evaluation of the replies
will be attempted.
Spontaneous statements of importance and answers to spontaneously
generated questions are included at the end of the answers to the list of
fifty-one questions.
NOTE:

After the answers to each question, there is a section labeled

"COMMENTS'.

This section contains the investigator's own subjective remarks

5

�and evaluation of the statements made by the contacts.

A COMMENTS section

w111 be found after each spontaneous comnent as well as after the answers to
the prepared questions.
ANSWERS TO PREPARED QUESTIONS
1.

Opinion of the Crew Health Stabilization Program.
Surprisingly, only 2 of 9 who were asked this question were opposed to the

program.

All stated either spontaneously (5) or upon questioning (2) that

they thought It was helpful In keeping the crews Insulated from annoying
contacts.
•1 thought 1t was kind of fun.

It kept the world away from us."

•It allows the crews to concentrate on what It Is they have to think
about.
flight.

They are not being pulled In a number of directions just before the
It allows them to focus on the task and the training ahead."

CoiMents;

Inasmuch as the Crew Health Stabilization Program is no longer

practiced with as much rigidity as It was In the early Apollo flights, 1t
might be wise to develop some policy for providing a similar degree of privacy
and seclusion for future missions.
2.

Thoughts on Space Station maintenance activities.

NOTE:

Because of the similarity of responses to this question and Question 4

regarding tools, the responses to both questions have been cond&gt;1ned here.
This question was presented to all the contacts.

Two had no comments on

the subject.
One man said that multipurpose tools were Important.
Inclusion of files, wrenches, and other common tools.
Swiss Army knife was especially valuable.
tape with the adhesive on both sides.

He urged the

He stated that his

He also suggested providing sticky

This would be useful In restraining

small parts to the workbench surface when making repairs.

6

�One man commented that the Apo11o tool kit was very good.
Another urged that maintenance should be kept simple - at the 'black box'
level.
One respondent thought that neutral buoyancy training was good practice
for maintenance, but another stated that it was misleading at best.

He urged

that any procedures developed in a neutral buoyancy tank be checked out in the
zero-g aircraft before being adopted for use in space flight.
Only one person mentioned the importance of foot restraints.
One recommendation was to project maintenance instructions, and even
diagrams, on the inside of the helmet visor in the manner of a Head-Up Display
(HUD).
A quotation from one of the contacts might prove interesting:
•You design things for routine maintenance done there by people with tools
in order to keep the system simple, and with simplicity you gain reliability.
You get the reliability through that route rather than through redundancy and
automation."
Comments:

The most significant response to this question is contained in the'

last quotation.

The recent remarkable successes in satellite recovery

operations add emphasis to the quotation.

Future satellites and future Space

Station equipment should be developed with the plan in mind that crew members
are capable of performing routine bench-level maintenance.
3.

Alarm Systems.
This question was presented to seven contacts.

Two of them mentioned that

they noticed a decrease in the loudness of sounds somewhat proportional to the
reduction of pressure in the helmet.
experience.

Another denied that he had had that

Other comnents included the reconmendation that the volume of the

alarm be proportional to the severity of the situation; that for critical

7

�energencles t h e r e should be simultaneous visual and a u d i b l e alarms; and t h a t
audible alarms should be a "warble t o n e ' a s i s used by some European police
cars.
Two individuals mentioned t h e g r e a t importance of e l i m i n a t i n g f a l s e
alarms. One suggested t h a t a study of t h e c h a r a c t e r i s t i c s of f a l s e alarms
might reveal a "signature" f o r f a l s e alarms.

This s i g n a t u r e could be

Incorporated i n t o a computer, and alarms could be evaluated a g a i n s t t h e s e
signatures before being sounded.
Comments:

The suggestion t o i n v e s t i g a t e t h e " s i g n a t u r e s ' of f a l s e alarms

might be worthy of f u r t h e r i n v e s t i g a t i o n .
4.

Tools f o r o n - o r b i t r e p a i r and maintenance.
Inasmuch a s t h i s was covered adequately in Question 2 , r e l a t i n g t o

maintenance a c t i v i t i e s , t h e answers t o t h i s question have been combined with
those obtained i n response t o Question 2 .
Comments;
5.

None.

Food and meals.
Of t h e ten persons Interviewed, one had no cormnent; t h r e e suggested t h a t

meals be s elected from a menu i n - f l i g h t ; and f i v e advised t h a t a l l individuals
e a t t h e same thing a t each meal with no s e l e c t i o n .

Hention was made by these

individuals t h a t t h e m i l i t a r y chow l i n e had much t o reconmend i t . One of the
f i v e suggested t h a t snack Items be provided f o r f r e e s e l e c t i o n from a pantry,
but he s t i l l did not recommend t h a t t h e r e be Item s e l e c t i o n f o r t h e main meals.
One person said he f e l t a menu determined ahead of time by crew interviews
was of l i t t l e value because people lose some of t h e i r a b i l i t y t o t a s t e when in
zero-g.

He a t t r i b u t e d t h i s t o loss of convection c u r r e n t s carrying aromatics

i n t o t h e nose.

He s a i d t h i s could be helped by providing strong condiments -

pepper i n o i l s o l u t i o n , hot mustard, and s o f o r t h .

6

�One contact suggested the Investigation of foil-packaged foods that are
marketed under the brand name of RETORT FOODS.

These are not freeze dried,

and may be eaten hot or cold.
One contact urged that more attention be paid to the nutritional aspects
of the diet.

He distinguished between those aspects of food preparation that

are conventionally performed by a dietician and those performed by a
nutritionist.

He suggested NASA pay more attention to the latter aspects of

menu and diet selection.
Comments;

Those who advocated the military chow-line approach have probably

not seen today's chow line.

In present-day military dining halls, there is a

remarkably broad selection of items available.

One of the contacts suggested

that each crew member be asked about his dislikes rather than his likes.
disliked foods would not be provided in his menu.

The

This seems like a

reasonable approach.
6.

Trash disposal.
This question did not stimulate much discussion in the early interviews so

was eliminated later on.

Two subjects suggested that trash be pyrolized -

convert trash to energy.

Two others who were asked had no comment.

Five were

not asked.
Comments;
7.

None.

Clothing design.
The overwhelming opinion was for a two-piece garment with lots of pockets

(seven out of nine, with two "No Comments").

The advantage of being able to

shed the upper garment for comfort in warm areas was comnented on twice.

All

agreed that many pockets were a necessity, but pocket closure should be with
Velcro rather than with buttons, which could catch on things.

Two unusual

comments included the suggestion that a "dress" uniform be provided for
special occasions- this for morale purposes.
colors and styles was important for morale.

9

Another was that a variety of
One individual stated the need

�for strict dress-code enforcenient as an aid to maintaining discipline.

One

subject stated he had had some experience with polypropylene outdoor clothing
and thought it might be worthwhile investigating.

He said it was quite

comfortable, but brought up the question of its fire resistance.
One suggested a different garment for wear during exercise periods.
One man suggested that two-piece uniforms have some means of fastening the
shirt/jacket to the waist of the trousers to prevent uncomfortable gapping at
that point.

He suggested Velcro.

There was a need expressed for a place to carry an emergency checklist at
all times.
Free choice of underwear was suggested.
One man suggested that slippers be provided for off-duty wear.
Coweents:

As might be expected, there was a wide range of suggestions

regarding clothing.

When some of the more extreme suggestions are eliminated

one reaches the conclusion that the basic in-flight uniform should be a
two-piece garment with many pockets.

The suggestion for the provision of a

place to keep an emergency checklist available at all times is a good one.
B.

Personal hygiene equipment.
Three contacts had no comments, and three were not asked.

The remainder

had comments that did not fit any pattern:
One wanted to use an electric toothbrush and an electric razor.

Another

preferred manual toothbrushes and a blade razor.
One man said that all on board should use whatever turned out to be
'issue' equipment.

He also mentioned that he would insist on daily shaving as

he felt it to be good for mental discipline.
mental set.

10

He felt it establishes a good

�Although not r e a l l y classed a s personal hygiene equipment, one man
commented t h a t showers were important but he f e l t a sponge bath might do a s
well.
Comments;

One might question t h e a d v i s a b i l i t y of providing e l e c t r i c razors,

what with t h e p o s s i b i l i t y of producing "whisker dust" In t h e v i c i n i t y of t h e
face of t h e u s e r .

Since e l e c t r i c razors seem t o be more p r a c t i c a l i n the

Space S t a t i o n environment, i t might be worthwhile t o conduct s t u d i e s on t h e
Shuttle t o determine whether o r not whisker dust r e a l l y i s formed in the
v i c i n i t y of t h e external nares in a zero-g environment.

One might a l s o

perform animal s t u d i e s t o determine whether o r not dust produced from t h a t
animal's own guard h a i r s produced any lung pathology when inhaled on a d a i l y
basis f o r extended periods of time.
9.

Aids t o t r a n s f e r of massive o b j e c t s .
The question was asked of only four people, and two of them had no

comments.

One person s a i d , "Put a loop of rope around i t and snub i t down."

Another suggested t h e use of a "Brooklyn c l o t h e s l i n e " .
loop of rope strung between two p u l l e y s .
l i n e with c l i p s .

This i s a continuous

Objects could be attached t o the

On t h e other hand, another contact mentioned, in response t o

a d i f f e r e n t question, t h a t he had t r i e d such a device in t h e Weightless
Environment Training F a c i l i t y (WETF) and found i t worked very well, but when
he t r i e d i t in t h e zero-g a i r c r a f t i t became tangled t o such an extent as t o
prove u s e l e s s .
Comments:
10.

None.

I d e n t i f i c a t i o n of "Up" and "Down".
Because of t h e s pecial i n t e r e s t of t h i s question, a g r e a t deal of time was

spent on i t .

Of t h e t e n subjects questioned, nine were very d e f i n i t e in

s t a t i n g t h a t t h e r e was no need t o t a k e any p a r t i c u l a r pains t o i d e n t i f y up and
down.

Several commented t h a t down was always where t h e i r f e e t were.

There

appeared t o be no d i f f e r e n c e between t h e answers from individuals who had
flown in confined spacecraft and answers from those who had flown in spacious

11

�vehicles.

One Individual said he himself was not bothered by the lack of up

and down, but stated he f e l t I t would be wise t o ensure t h a t everything In a
given volume have the same orientation.
One contact related that one of his colleagues had spent "hours and hours'
In the simulator, then went Into f l i g h t and became 111 even before he had
gotten out of the s eat . The point of t h i s observation I s t h a t t h i s person had
excellent up and down references but became 111 anyway.
In response t o a direct question, one man said t h a t even seeing his
colleagues In an orientation different from his own did not disturb him.
Two men conmented that the use of a simulator may drive the configuration
of the Space Station, a t least In areas where simulator training 1s
extensive.

The simulator will have t o be constructed with an up and down

orientation because I t I s used In a one-g f i e l d .

The Space Station area must

match the simulator for training If I t I s t o serve any purpose.
The following quotations are presented:
(1)

'Before I came Into the space program I tended t o have a great amount

of familiarity with mathematical techniques of rotation and translation of
axes systems...! tended t o look a t something and j u s t figure t h a t I had a
rotated coordinate system.

(In space) I ' d look out a t the Earth, and I ' d

recognize the Earth had I t s own set of Earth-centered coordinates.

The

spacecraft had I t s space-centered coordinates. Whenever I saw the two In the
same field of view 1 just automatically thought of the spacecraft as being
oriented t o the Earth, but more Importantly, I had my own body-centered
coordinates, and the Input, If somebody allows them t o , can be of those
things. . . . I f you operate 1n egocentric coordinates "down" will be towards
your f e e t .

I t makes no difference whether you're going over the Earth upside

down o r diving under I t , or any of those things, If you really look a t I t as
your world Is where you are, and everything else I s oriented around you."
(2)

One contact said he thought I t fun t o look a t the world upside down.

"Trying t o force a one-gravity mode of operation Into zero-gravity I s a
mistake.

I t defeats a l l of the freedom which you a r e given."

12

�(3)

When he would go from one compartment t o another, one person s a i d ,

•There would be moments of d i s o r i e n t a t i o n and you would kind of f l i p your body
around and you'd pick t h e work s t a t i o n you were going t o work a t , and then a s
soon as you got your body flipped around t o where you were within about 45
degrees of t h a t work s t a t i o n ' s local v e r t i c a l then everything clicked in and
you were comfortable."
(4)

" I think t h a t maybe i f you s t a r t i d e n t i f y i n g up and down you may be

reminding people of t h i n g s they should be f o r g e t t i n g . "
" I think we adapt e a s i l y t o most any environment, but I j u s t d o n ' t think
there i s a g r e a t deal t o be gained by t r y i n g t o force people t o think as they
do here on Earth when they a r e , i n f a c t , in space."
Comments:

If t h e opinions of t h i s small sample of people a r e f e l t t o be

s i g n i f i c a n t one must conclude t h a t special e f f o r t s t o i d e n t i f y "up" and "down"
in Space Station will not pay l a r g e dividends.

The comment t o maintain a

constant local v e r t i c a l i n each module seems worthwhile following, i f i t i s
a r c h i t e c t u r a l l y f e a s i b l e and charges no penalty from a design standpoint.
On t h e other hand, none of t h e ten subjects interviewed admitted t o having
experienced any degree of nausea.

If none of t h e ten contacts became i l l , and

i f approximately 40X of S h u t t l e crew members become i l l , we a r e drawn t o four
possibilities:
(1)

The sample i s s o small t h a t chance alone resulted in my interviewing

only those individuals who did not become i l l .
(2)

There really i s some difference between those interviewed and Shuttle

crew members.
(3)
flight.

The persons interviewed did not admit t h a t they become i l l i n
From t h e obvious s i n c e r i t y and d i r e c t n e s s of t h e s e ten contacts, I am

convinced t h a t none of them became i l l .

This, I must admit, i s a very

subjective assessment, but i t i s my conviction t h a t they were a l l t r u t h f u l and
f o r t h r i g h t in t h e i r answers t o my questions.

This opinion i s substantiated by

t h e f a c t t h a t one individual did admit t h a t he would have become i l l had he
not paced h i s o n - o r b i t a c t i v i t y f o r t h e f i r s t t h r e e o r four days.

This

person's conments a r e found in t h e SPONTANEOUS COMHENTS s e c t i o n , which follows.

13

�(4)

The flight environment of these ten contacts was different from the

Shuttle environment.
I suspect that the reason for the observed difference 1n distribution of
nausea In this group Is a combination of (1) and (4).
11.

Use of vented gases for attitude control.
This was only asked of four contacts.

One remarked that vented gases had

been used as an expediency to control tumbling In Gemini V.

Another had no

coment regarding the use of gases for attitude control, but he did suggest
that they be used to run turbines for power.
One said he did not think It such a good Idea - use control moment gyros
Instead.
Comments:
12.

None.

Importance of private cwnnunlcatlons.
This question was asked of all ten Individuals.

Responses varied from,

'Hot all that Important' to 'Absolutelyl'
Host of the respondents thought a private line was Important for personal
connunlcatlon with families, but of equal Importance was Its use In
operational control of the flight.

One subject gave an example of a situation

In which Instructions had to be paraphrased to keep them from being heard by
the press.

The paraphrased Instruction was misinterpreted to be a Joke and

was not followed.

The example cannot be further Identified or described here

as it would reveal the source, but suffice It to say that the well-being of a
crew member was Jeopardized by this misunderstanding.
One contact said, 'The Administrator [NASA] doesn't have a microphone In
his office with the world listening Into everything he says.
astronauts have the same privilege?'

14

Why can't

�Another s a i d , 'They ( t h e press) have no more r i g h t in your bedroom on
o r b i t than they have in your bedroom on Earth.

They a r e not allowed t o go t o

your doctor and find out how you a r e and what you a r e doing (on Earth so they
d o n ' t have t h a t r i g h t i n s p a c e ) .
Coffinents:

I d o n ' t c a r e who's paying t h e b i l l . "

The respondents' r e p l i e s t o t h i s question were based more on t h e i r

feelings of p r i v i l e g e r a t h e r than on t h e a c t u a l need f o r and u t i l i t y of a
private communications l i n k .

They admitted t h e importance of the r i g h t t o

speak p r i v a t e l y t o t h e i r f a m i l i e s , but they did not seem too concerned with
the beneficial e f f e c t such communications would have on mission
accomplishment.

The comment regarding the u t i l i t y of a p r i v a t e link t o

discuss purely operational matters was s i g n i f i c a n t .
I would l i k e t o point out t h a t during s t r e s s f u l t r a i n i n g exercises during
the Mercury program I had many opportunities t o use t h e private l i n e and found
i t t o be of g r e a t b e n e f i t in assessing the s t a t u s of t h e t r a i n e e .

The

t r a i n e e s more than once made statements a s t o t h e i r physical s t a t u s t o me on
t h e p r i v a t e l i n e t h a t they would not make on t h e open loop.

As an individual,

and not a s t h e i n v e s t i g a t o r i n t h i s study. I would strongly recommend t h a t an
absolutely p r i v a t e communications l i n k be provided.

The "Earth end" of t h e

link would be under t h e control of t h e crew member.

That i s , t h e crew member

would decide who he would t a l k p r i v a t e l y t o , h i s family, t h e f l i g h t
c o n t r o l l e r , t h e physician, o r anyone e l s e .

One of t h e contacts in t h i s

investigation even mentioned t h a t a person spending many weeks o r months in a
Space S t a t i o n might wish t o speak p r i v a t e l y t o h i s broker!
13.

Use of portable f a n s .
Five contacts were asked t h i s question, and none of t h e f i v e ventured an

opinion.
Comments:
14.

The question was not presented t o t h e o t h e r f i v e .
None.

Opinions regarding t r a n s l a t i o n a l a i d s , control/switch p r o t e c t i v e devices,

o r i e n t a t i o n cues, and p r o t e c t i v e gear f o r personal wear.

15

�Five of t h e ten contacts were not asked any p a r t of t h i s q u e s t i o n . Of the
f i v e remaining, only p a r t s were asked, o r only p a r t s were answered.
Four subjects expressed s a t i s f a c t i o n with t h e coninon "wicket-type" switch
guards.
One person s a i d he could not v i s u a l i z e r o l l r a t e s of such a magnitude as
t o require personal p r o t e c t i v e equipment such a s headgear.

He a l s o said

rounded corners and o t h e r methods should be used t o p r o t e c t a person moving
about in t h e cabin.
be required.
Comments;
15.

One o t h e r person s a i d he did not b e l i e v e headgear would

None.

Opinions regarding t h e a i r l o c k on Skylab.
This question was presented t o only t h r e e people, and only one of them had

an opinion.

He s t a t e d , "There should always be a s a f e haven one can g e t t o .

The racetrack design I s good. To have a s a f e haven in each module I s too
c o s t l y , I t takes up t o o much room."
Cocmaents:
16.

None.

Ideas regarding crew q u a r t e r s .
This was addressed by nine out of t h e ten Interviewed.

f e e l t h a t p r i v a t e crew q u a r t e r s were necessary.
very Spartan conditions.

Only two did not

One of t h e s e two advocated

He commented t h a t we c a n ' t a f f o r d t o build a Space

S t a t i o n t o accormodate anybody and everybody.

We must s e l e c t crews t h a t can

t o l e r a t e Spartan l i v i n g conditions f o r ninety days.
they can hang up anywhere."

"Olve them a sleeping bag

The o t h e r one of t h e s e two s a i d he compared a

ninety-day Space S t a t i o n t o u r with an overseas m i l i t a r y t o u r o r a camping
trip.

He s a i d , " I d o n ' t t h i n k you need t o have a p r i v a t e room and a l l t h a t as

long a s you have a place t o s l e e p . "

16

�One of t h e remaining seven who commented s a i d he saw two c o n f l i c t i n g
requirements, one was t h e need f o r q u i e t and privacy, and t h e o t h e r was t h e
need t o be near t h e work s t a t i o n t o respond t o emergencies.

He suggested t h a t

NASA explore t h e p o s s i b i l i t y of providing a "sea cabin" f o r one o r more crew
members.

He a l s o f e l t t h a t any alarms sounded In t h e crew q u a r t e r s should be

p r i o r i t i z e d - perhaps only a " B a t t l e S t a t i o n s ! " type of alarm.
One contact with Skylab experience said he thought t h e crew quarters
should be a t l e a s t twice t h e s i z e of t h e Skylab q u a r t e r s .

He a l s o advised

t h a t they not be located near t h e exercise area t o diminish t h e noise l e v e l s .
One person commented t h a t t h e Apollo s l e e p r e s t r a i n t s were adequate, and
one commented t h a t t h e Skylab s l e e p r e s t r a i n t s were good.
With t h e exception of t h e two "Spartans", everyone believed p r i v a t e ,
individual, comfortable q u a r t e r s should be provided.
Comments:

There seems t o be no question but t h a t p r i v a t e crew quarters should

be provided.

These should be a s large a s I s practicably possible.

It Is

evident t h a t t h e e a r l y Space S t a t i o n w i l l not be large enough t o provide
commodious q u a r t e r s , but I t seems t h a t , given t h e a l t e r n a t i v e s , privacy I s
more t o be desired than volume.
17.

Medical t r a i n i n g f o r crew members.
This question was presented t o e i g h t of t h e ten c o n t a c t s .

The most common

response was t h a t e i t h e r a f l i g h t surgeon be on each crew, o r t h a t two of t h e
crew members should be t r a i n e d t o t h e level of paramedics. One respondent said
he believed a l l crew members should have extensive t r a i n i n g 1n physiology so
t h a t they would b e t t e r understand medical o r physiological problems t h a t arose
In themselves o r In o t h e r s . He a l s o f e l t t h e r e should be a f l i g h t surgeon on
board f o r long-term exposures.

Another f e l t t h a t every crew member should

have t h e equivalent of paramedic t r a i n i n g , and t h a t a physician was not
necessary unless he was dual t r a i n e d - a s a payload s p e c i a l i s t f o r example.
One o t h e r contact suggested t h a t i f a physician were assigned he should be

17

�dual t r a i n e d .

Another contact reconnended t h a t NASA. 1n t h e i r s e l e c t i o n

program f o r mission s p e c i a l i s t s . Include s u f f i c i e n t physicians a s t o provide
one f o r each Space S t a t i o n crew.
Comments:

C l e a r l y , a minimum of two people on each crew must have some

competency 1n providing medical c a r e .
other can take care of him.

If one of t h e s e two becomes 111, the

A good compromise would be f o r one of t h e crew

members t o be a dual-trained ( a s a payload s p e c i a l i s t ) physician and t h e other
a s a dual-trained person with medical t r a i n i n g e q u i v a l e n t t o t h a t of a
paramedic.
18.

Need f o r group dynamics t r a i n i n g .
Group dynamics t r a i n i n g was b r i e f l y described a s a psychological technique

which helps people t o work together and t o give each o t h e r mutual support and
tolerance.
This question was presented t o nine c o n t a c t s .

Only two f e l t no t r a i n i n g

was required, and one f e l t I t should be given only If a problem a r o s e .
stated he had heard t h e Russians had had a problem.

One

One commented a s follows:

*I think t h a t I t ' s going t o be Increasingly important t h a t they have a t
l e a s t some amount of t h i s [group dynamics t r a i n i n g ] because you would l i k e t o
have a preconditioned a t t i t u d e of how t h e y ' r e supposed t o work t o g e t h e r .

You

d o n ' t want t o have some highly motivated mission s c i e n t i s t back t h e r e [ I n the
space lab o r an analogous p a r t of a Space S t a t i o n ] who d o e s n ' t understand
where t h a t p r i o r i t y I n t e r f a c e s with t h e s e o t h e r p r i o r i t i e s . "
Another commented t h a t he f e l t f u t u r e crews, who would not have a s much
I n t e r a c t i v e t r a i n i n g a s those of today, should be required t o function In some
s o r t of environment together before they launch.

He suggested t h a t Survival

School might be useful f o r t h a t purpose.
One contact was e s p e c i a l l y concerned In regard t o t h i s m a t t e r .

His

coenents took up more than a page of single-spaced t y p e s c r i p t , and Included
t h e following statements:

16

�' I think t h a t [ t h e lack of p s y c h i a t r i c o r psychological support] i s one of
the shortcomings of NASA over t h e y e a r s , and I d o n ' t know i f they've solved
t h a t problem yet today, and t h a t i s t h a t t h e r e i s no a c t i v e program having t o
do with t h e behavioral sciences t h a t helps e i t h e r t h e astronauts in dealing
with one another o r t h e a s t r o n a u t s and t h e i r families dealing with t h e
situation."
' I think i t i s unfortunate t h a t astronauts have never been given any kind
of opportunity f o r behavioral science understanding.

There has been such a

stigma associated with psychologic o r p s y c h i a t r i c therapy t h a t everyone stays
away from i t l i k e i t i s some kind of poison."
' I though i t was j u s t r e a l l y too bad t h a t t h e r e was not some s o r t of a
program in NASA t o help i n some s o r t of an upbeat way - t o give them access t o
these people - give them some t r a i n i n g on techniques of dealing with t h e s e
problems.

The problems a r e t h e r e ! "

Another c o n t a c t ' s comments f i l l e d t h r e e single-spaced t y p e s c r i p t pages,
but were mostly personal experiences with h i s f r i e n d s , and cannot be reported
here because of t h e p o s s i b i l i t y of revealing t h e source.

He l e f t no doubt in

t h i s i n t e r v i e w e r ' s mind t h a t he was strongly i n favor of professional
psychological support f o r t h e crews and f o r t h e i r f a m i l i e s .
Comments:
19.

See comments t o Question 1 9 .

Should f a m i l i e s have s i m i l a r psychological support?
This question was posed t o e i g h t of t h e t e n c o n t a c t s .

One had no comment,

two said i t need not be provided, and one s a i d i t should be provided only on a
voluntary b a s i s If t h e family member f e l t t h e need and asked f o r i t .

The r e s t

f e l t i t should be provided In some degree o r another.
A commonly expressed suggestion was t o keep t h e f a m i l i e s very well
informed about a l l a s p e c t s of t h e program, and t o g e t them involved with
whatever i s going on.

One man s a i d , "The more you involve t h e wives i n t o t h e

19

�operation, t h e more support you g e t from them.

Keep them Informed and give

them l i n e s of conmunlcatlon t o , f o r example. Mission Control Center." He also
s a i d , ' I know when I was t h e r e [assigned t o NASA], t h e wives and t h e families
were r e a l l y I s o l a t e d .

They were r e a l l y pushed back In a c o r n e r .

I s , t h a t kind of treatment was I n f e c t i o u s .

The program t r e a t e d t h e wife t h a t

way, and p r e t t y soon we s t a r t e d t r e a t i n g our wives t h e same way.
really tragic."

The problem

" I know I t cost a l o t of guys t h e i r m a r r i a g e . "

I t was
He continued

by saying. 'You c a n ' t t r e a t people l i k e numbers, and t h a t ' s what NASA d i d .
t h e wives were unhappy, w e l l , t h a t ' s t o o bad!

If

'Think of a l l t h i s Important

work t h a t your husband I s doing and go home and s h u t u p ! '

I t d i d n ' t work."

On the other hand, another contact s t a t e d , "The t h i n g s t h a t d o n ' t k i l l you
make you s t r o n g e r .

I , f r a n k l y , think t h e experience was a p o s i t i v e experience

f o r my w i f e . "
He was not one of those In favor of a formal program f o r t h e f a m i l i e s .
Comments:

Because Question 18 and Question 19 a r e s o c l o s e l y r e l a t e d ,

comments t o both of them w i l l be presented h e r e .

For some reason t h e r e seemed

t o be more enthusiasm expressed f o r providing some s o r t of psychological
support f o r t h e crew members than f o r providing s i m i l a r support f o r t h e
families.

I had expected t h e reverse would prove t h e c a s e .

I t would seem

Important t o ensure t h a t f u t u r e Space S t a t i o n crews have t h e opportunity t o
work very c l o s e l y together in s i t u a t i o n s t h a t w i l l r e q u i r e mutual support.
Although I t might be d i f f i c u l t t o j u s t i f y giving survival t r a i n i n g t o Space
Station crews, t h a t s o r t of s o c i a l I n t e r a c t i o n would probably pay large
dividends when t h e crew occupy t h e Space S t a t i o n .

I t might a l s o be of benefit

f o r NASA t o Introduce a c e r t a i n amount of psychological t r a i n i n g I n t o t h e
program.
The contacts, f o r the most p a r t , were not concerned about providing
psychological support f o r t h e f a m i l i e s .

However, t h o s e who were In favor of

such support were very p o s i t i v e In t h e i r s t a t e m e n t s .

My personal f e e l i n g s in

t h i s regard, and many of t h e s e f e e l i n g s have been generated by t h e very strong

�and sincere statements expressed by two of t h e c o n t a c t s , a r e t h a t NASA has
been remiss In not Including t h e f a m i l i e s a s p a r t of t h e program. I t seems
that more d e t a i l e d b r i e f i n g s might be given t h e wives so t h a t they would have
a better Idea of of what t h e i r husbands a r e doing.

This action might not

Improve the effectiveness of t h e husbands, but nevertheless should be provided
if only f o r humanitarian reasons.
The question of r e l i g i o u s b e l i e f s was never presented a s a formal
question, but I t did come up spontaneously In t h e discussions with most of t h e
contacts.

From t h e i r expressions of belief and f a i t h 1 t I s my conclusion t h a t

a resident chaplain a t JSC would be of g r e a t value t o t h e program.
20.

Crew I n t e r a c t i v e t r a i n i n g In a one~g simulator.
Because of t h e many very strong polarized f e e l i n g s brought out by t h e

questions on group dynamics t r a i n i n g (Questions 19 and 20), I t was f e l t t h a t
t h i s question should be eliminated.
misinterpreted i t .

I t was asked of only one contact and he

His answer r e l a t e d t o command s t r u c t u r e of a Space Station

crew, and will be included with t h e answers t o Question 45.
Comments:
21.

None.

Problem of ambient nois e.
Here I s another question t h a t was, f o r a l l I n t e n t s and purposes,

eliminated. The contacts a c t u a l l y answered I t when speaking of t h e need f o r
quiet In p r i v a t e q u a r t e r s .
The question was posed t o t h r e e I n d i v i d u a l s .

One Implied In h i s answer

t h a t noise was not a big problem - one g e t s used t o I t .

On t h e o t h e r hand,

unanticipated noises o r motions of t h e s p a c e c r a f t a r e very d i s t r a c t i n g .

The

third said t h a t on h i s f l i g h t , crew member noise prevented sound sleeping In
shifts.
Comitents:

None.

21

�22.

Wardroom, e n t e r t a i n m e n t , e x t e r n a l v i e w i n g , and E a r t h p o s i t i o n .
All t e n c o n t a c t s a g r e e d t h a t a wardroom was I m p o r t a n t .
There was near-unanimous o p i n i o n t h a t p e r s o n a l l y s e l e c t e d books and music

t a p e s were I m p o r t a n t t h i n g s t o t a k e a l o n g .

Other suggestions Included the

p r o v i s i o n of movies on VCR t a p e s , and one I n d i v i d u a l s u g g e s t e d t h a t books,
movies, and o t h e r forms of a u d i o - v i s u a l e n t e r t a i n m e n t c o u l d be p u t on l a s e r
video d i s c s .

Hany I n d i v i d u a l s commented on t h e f a c t t h a t r e a l - t i m e coimerclal

news progratming and e n t e r t a i n m e n t shows c o u l d be u p - l i n k e d w i t h l i t t l e
difficulty.
Only one person had no s t r o n g o p i n i o n on t h e need f o r windows, b u t even he
s a i d t h e y were h i g h l y d e s i r a b l e , b u t n o t o f prime I m p o r t a n c e .

One person

s a i d , 'Nobody e v e r g e t s enough t i m e l o o k i n g o u t o f w i n d o w s . '

Another s a i d ,

'They should make s u r e t h a t t h e r e a r e a s many windows a s p o s s i b l e . '

He

suggested one be p u t n e a r t h e e x e r c i s e d e v i c e s o one c o u l d l o o k o u t w h i l e
exercising.

One man s a i d t h e windows a r e e x t r e m e l y 1nQ)ortant from a

recreational as well an Inspirational standpoint.
p o r t s and t i m e t o u s e t h e m . '
spacecraft the better.

He s a i d , 'You need viewing

One of t h e c o n t a c t s s a i d , ' T h e more windows In a

One of t h e most e n j o y a b l e t h i n g s you have t o do up

t h e r e 1 s t o look o u t t h e window.

I n f a c t , even a b u b b l e window might be n i c e . *

One of t h e more a r t i c u l a t e c o n t a c t s s a i d :
' I , f o r o n e , am t o t a l l y convinced t h a t t h e magic of s p a c e and t h e v a l u e of
being t h e r e I n v o l v e s being a b l e t o s e e w h a t ' s o u t t h e r e . . . I t 1 s from t h e human
s t a n d p o i n t t h a t I t h i n k you need l o t s of viewing p o r t s .
Important.

I d o n ' t c a r e I f 1 t does c o s t more money.

I t h i n k t h a t ' s very

The r e t u r n I n keeping

p e o p l e ' s I n t e r e s t , and t h e m o t i v a t i o n and a l l t h a t s o r t o f t h i n g , t o d o more
and more, and t o g o f u r t h e r , 1 s v e r y d r a m a t i c a l l y enhanced by b e i n g a b l e t o
see.'
Comments:

The most c o n s i s t e n t answer t o a n y of t h e f i f t y - o n e q u e s t i o n s was

t h e s t r o n g p o s i t i v e e x p r e s s i o n of a need f o r a wardroom w i t h some s o r t of
entertainment equipment.
Individual preferences.

The s u g g e s t i o n s f o r t h i s equipment c l e a r l y followed
Of equal unanimity was t h e e x p r e s s e d need f o r many

22

�and large windows.

This has such g r e a t importance t h a t i t would appear

important t o consider t h e p o s s i b i l i t y of providing bubble windows, a s was
suggested by one of t h e c o n t a c t s .
23.

Body waste c o l l e c t i o n and d i s p o s a l .
Six contacts were asked t h i s question.

Two had no ccHwnents, and two said

they f e l t t h a t t h e Skylab system was adequate, although they did not l i k e t h e
idea of bagging t h e f e c e s .

One man said even t h e Apollo system was a l l r i g h t

in s p i t e of t h e need t o bag t h e f e c e s .

The t h i r d comment related only t o

urine collection and t h a t person said he f e l t t h e ordinary a i r c r a f t , r e l i e f
tube was adequate.

Although he d id not say s o , i t was c l e a r t h a t he meant

such a device would have t o be adapted t o t h e zero-g environment.
Comments:
24.

None.

Personal c l e a n l i n e s s .
Since t h i s question had a l s o been addressed in Question 8 , Personal

Hygiene Equipment, i t was presented t o only f o u r of t h e c o n t a c t s .

Two of them

had no comment; one recommended t h e use of a spring-driven razor; and another,
who uses a blade r a z o r , s a i d he f e l t frequent o r d a i l y shaving was good f o r
crew d i s c i p l i n e .
Conments:
25.

This was t h e second contact t o make t h a t comment.

This was considered in t h e comments t o Question 8 .

Exercise.
This question was asked of nine c o n t a c t s .

important.

All agreed t h a t exercise was

One s a i d he f e l t e x e r c i s e and good food were t h e two most

in^ortant things t o provide f o r long-duration space f l i g h t .

Two others said

they f e l t e x e r c i s e was important from a psychological and morale standpoint a s
well as from a physical well-being point of view.
Five people recommended t h a t both a bicycle ergometer and a treadmill be
provided.

One mentioned only a treadmill and one mentioned only a bicycle.

a

�Two people mentioned that it Is also necessary to exercise the upper torso
and arms.

One of these recoimiended spring or bungee devices for this

purpose.

Another thought a Nautilus-type of exercise device should be

provided.
One person said he thought the Cxergenle was a very useful device, but
another stated that he tried to use it on his flight and found that the nylon
ropes heated from the friction of use and stretched, making the device useless.
Another person said he believed there is a need for something that will
provide structural stress to the skeletal system, but he had no ideas on how
to do that.
Only two people suggested a duration for the exercise period.

One

suggested ninety minutes and the other sixty minutes.
Coniwents;

The need for exercise was strongly supported by all.

It Is my

understanding that investigations into the types of exercise equipment needed
are being conducted.

I can only urge that these Investigations be continued

both on the ground and In flight.
2b.

How to manage books and manuals.
This question was presented to only four of the ten contacts.

One stated

he preferred books, but could learn to live with Information presented on
CRTs.

One contact had no comments, and the other two said that they did not

think that everything had to be In data banks.

Some material can best be

presented in book form, and other material can be stored In data banks for
retrieval when needed.
The feeling seemed to be that recreational material was best presented In
book form, but technical material (with the exception of emergency checklists)
could be stored In data banks.
Cowaents:

None.

24

�27.

Han/machine interface.
This question was put to five of the ten contacts.
One suggested that color be used more in the design of the Space Station,

and one said color was not a11 that important.

One had no comment.

One man suggested that NASA employ what he called "functional artists" to
help in designing the interior of the Space Station.

He stated that the

wardroom should be of a "relaxing* color and the flight deck should be of an
"alerting" color.
One individual urged caution in accepting the use of digital displays.

He

said:
"Digital offers various advantages in terms of accuracy, precision when
you need precision, but the human being is an integrator, he doesn't take
snapshots, and there is a lot of information and intelligence lost when you're
looking at a digital display."
Comments:

The science of architecture is advancing at a great pace.

NASA

would be well advised to use the services of this discipline in establishing
interior design criteria for the Space Station.
I was impressed by the warning about digital displays.

From a purely

personal standpoint I find it easier to integrate analog informational
displays than I do digital displays, but this may be purely cultural.

An

interesting area for investigation would be to assess whether people get more
or less information from one display than the other.

Unquestionably, it is

easier and quicker to read, for example, the exact time from a digital
display, but does one find it also easier to tell how many minutes have
elapsed since a given event or how much time remains before a given action
must be taken. I am sure similar analyses could be made of altimeters, and
other displays of changing quantifiable information.

25

�2B.

Three s h i f t s o r one?
This question was asked of s i x people.

One had no connient.

Only one of

t h e remaining f i v e f e l t t h a t a l l crew members should be allowed t o s l e e p a t
t h e same time.
times.

They f e l t t h a t someone should be awake and on watch a t a l l

One man s a i d t h a t t h e crews should be a b l e t o work longer than

eight-hour s h i f t s .

He s a i d , 'You're not t h e r e on a v a c a t i o n , even f o r three

months.'
One contact s t a t e d t h a t timelines should be f l e x i b l e enough t o accomnodate
t h e mission, and t h e crew members should be i n d o c t r i n a t e d in t h e occasional
need f o r working on t h e i r off-duty time.

For exati^le, an Earth resources task

night require t h a t t h e Earth resources s p e c i a l i s t t a k e photos a t a p a r t i c u l a r
time on a p a r t i c u l a r o r b i t , and t h a t might occur during h i s o f f - d u t y time.
This question a l s o asked t h e contact t o comment on whether e x e r c i s e should
be an off-duty endeavor o r a duty-time a c t i v i t y .
obtained.

Only t h r e e answers were

One man said exercise should be done during o f f - d u t y hours.

The

second said t h e question was i r r e l e v a n t because one i s never ' o f f d u t y ' In
space.

The t h i r d said he thought half of t h e e x e r c i s e should be done during

on-duty time and half of i t when off d u t y .
Comments:

As was t h e case i n most of t h e s e q u e s t i o n s , t h e r e was no r eal

unanimity of opinion unless i t was t h a t someone should be awake a t a l l times.
This seems t o be a most reasonable and l o g i c a l p o s i t i o n .
29.

Importance of real-time TV.
Here i s another example of a question t h a t was covered f a i r l y well i n an

e a r l i e r question.

See Question 22. which addresses wardroom accommodations.

This question (29) was asked of only t h r e e persons.

One had no comment:

one thought i t was very important; and t h e o t h e r did not b e l i e v e i t t o be of
g r e a t importance.
Comments:

None.

�30.

Who should s e l e c t t h e crews?
All but t h r e e of t h e contacts were asked t h i s question and, a s one might

expect, t h e r e was a wide range of opinion i n t h i s regard.
person a r e summarized in t h e following paragraphs.
(1)

A crew s e l e c t i o n committee has v i r t u e .

made by one person.

The r e p l i e s of each

No r e a l p a t t e r n emerged.

The s e l e c t i o n should not be

Perhaps t h e Captain should be s e l e c t e d f i r s t .

He would

then s e l e c t a second person; t h e two of them would s e l e c t t h e t h i r d ; and s o on
until a l l crew members had been chosen.
(2)

Overall Management should make t h e s e l e c t i o n .

The Commander should

not have s o l e s e l e c t i o n a u t h o r i t y , but he should have veto powers.

The peer

review concept has v i r t u e i n t h a t i t i d e n t i f i e s t h e unpopular individuals.
(3)

The crew should be s e l e c t e d by Management - they have more

information a v a i l a b l e t o them than does anyone e l s e .
i s a useful t o o l .

The peer review process

Management needs an input from t h e crew Commander.

This

contact believed t h a t a small group of crews should be selected and flown
frequently.

This saves expensive t r a i n i n g time over t h e o t h e r a l t e r n a t i v e ,

which i s t o have a l a r g e pool of candidates from which crews a r e selected t o
fly less fre q uently.
(4)

Believes a nucleus of crew members should be s e l e c t e d .

These people

fly frequently and t r a i n t h e i r own replacements ( t h e r i g h t - s e a t man eventually
moves i n t o a l e f t - s e a t assignment).

Whatever system i s used, i t should be

well understood by a l l t h e candidates.

Each should know what the s e l e c t i o n

c r i t e r i a a r e , and how t h e process o p e r a t e s .
(5)

Mentioned t h a t he l i k e d t h e way Slayton handled t h e s e l e c t i o n

process, but believes t h e s e l e c t i o n pool i s much too l a r g e .
(6)

Also mentioned t h a t he liked t h e way Slayton did h i s job i n t h e p a s t .

(7)

NASA management should s e l e c t t h e operational crew.

authority should s e l e c t t h e t e c h n i c a l crew.

Some o t h e r

The combined group should work

together f o r a period of time, and t h e Commander should be a b l e t o e x e r c i s e
veto power over members of both groups i f he f e l t an individual would not f i t
in.
Conments:

I am i n c l i n e d t o go along with respondent Number 3 .

Number 7 made e s s e n t i a l l y t h e same comments.

27

Respondent

My disagreement with Number 3 i s

�only i n regard t o t h e concept of peer review.

I an s u r e i t does point out the

unpopular i n d i v i d u a l s , a s s t a t e d by c o n t a c t Number 2 , but a t what expense?

I

am s u r e t h e unpopular individual i s already known by Management by t h e time
they g e t around t o s e l e c t i n g t h e crews.

One i s i n c l i n e d t o ask how important

i s popularity anyway?
31.

Does EVA require t h e 'buddy system"?
Only four people were asked t h i s question.

One had no conntent, and the

other t h r e e said they believed i t was necessary.

One of them s a i d he thought

the buddy might be a f u l l y s u i t e d a s t r o n a u t who remained i n s i d e t h e s t a t i o n ,
but was ready t o go outside a t a moment's n o t i c e .
None said they though t h e buddy system was unnecessary.
Comments:
32.

None.

How can t h e EVA s u i t be in^troved?
This question was asked of seven people.

Again, t h e comments were not

c o n s i s t e n t , and r e f l e c t t h e i n d i v i d u a l ' s personal views.

There i s a l s o some

overlap in t h e answers with t h e answers t o some of t h e o t h e r q u e s t i o n s .
(1)

For prolonged EVA t h e astronaut should be provided with a 'motorman's

f r i e n d * , a d i a p e r , water, but no food.
(2)

For missions t h a t w i l l require EVA soon a f t e r a t t a i n i n g o r b i t , t h e

EVA crewman should be s elected from a pool of i n d i v i d u a l s who, by t h e i r past
experience in o r b i t , have shown t o be r e s i s t a n t t o space motion s i c k n e s s .
Nevertheless, vomitus containment apparatus should be provided ' j u s t in case.*
(3)

Consider using honey water a s a source of energy and f l u i d .

glove needs improvement s o a s t o provide b e t t e r t a c t i l e s e n s a t i o n .

The
A wire saw

(Gigli saw) should be taken along on every EVA f o r emergency u s e .
(4)

Mentions b e t t e r gloves with improved t a c t i l e s e n s a t i o n .

(5) Suggests t h a t t h e problem of f i n g e r t i p i n j u r y could be solved by
c l o s e r trimming of t h e f i n g e r n a i l s .
(6)

Recommends t h e hard, r i g i d , high-pressure ( 8 p s i ) s u i t .

(7)

One man had no comments.

28

�Cownents:

The suggestion t o use honey water a s a source of nourishment and of

fluids c e r t a i n l y deserves i n v e s t i g a t i o n .

Methods f o r c o l l e c t i n g urine and

feces (a diaper should be adequate f o r emergencies) a r e e s s e n t i a l , and I
believe t h a t some s o r t of vomitus containment device i s a l s o e s s e n t i a l .
People s t i l l become i l l , even on t h e s u r f a c e of t h e Earth in a one-g f i e l d ,
^

and there i s no reason t o suspect t h i n g s w i l l d i f f e r i n space.

^

problem comes up with t h e food s t o r a g e equipment, t h e r e might well be some
gastroenteric I l l n e s s e s developing.

In f a c t , i f a

F i n a l l y , i t seems logical t o develop a

suit t h a t provides a t l e a s t 8 - p s i p r e s s u r e , more If f e a s i b l e .

The advantages

to such a garment a r e t o o well known t o warrant elaboration in t h i s r e p o r t .
33.

EVA r e s t r a i n t s , t e t h e r s , hand holds, l i g h t s , e t c .
After receiving t h r e e "no comments" i n a row, t h i s question was

eliminated.

I t was asked of f o u r c o n t a c t s and only one had any comments.

His

are as follows:
"There i s a need f o r a s m a l l , multipurpose t o o l k i t with interchangeable
end-effectors.

Small l i g h t s on t h e f i n g e r t i p s a s were used in the Mercury

program a r e extremely u s e f u l .

These can be d i r e c t e d b e t t e r than a

helmet-mounted l i g h t . "
Comments;
effective.
34.

The use of f i n g e r t i p l i g h t s on t h e Mercury s u i t was most
This might be i n v e s t i g a t e d again f o r t h e Space S t a t i o n s u i t .

Suggestions regarding mortuary a f f a i r s .
This question was posed t o f o u r of t h e persons interviewed.

Two s t a t e d

that the sensible t h i n g t o do would be some form of o n - o r b i t d i s p o s a l .
said, in some s e r i o u s n e s s , "Shoot me i n t o t h e Sun!"

(One

He was aware of t h e

high-energy c o s t of doing t h i s , s o t h e r e was some l e v i t y i n t h e remark t o o . )
6ut they a l s o recognize t h a t t h i s would not be acceptable in today' s s o c i e t y .

I
^

One of t h e contacts s a i d t h e problem should be addressed and solved before
we go t o Space S t a t i o n , but he had no i d e a s .

The f o u r t h person agreed with

the necessity t o bring t h e body back i n a condition s u i t a b l e f o r an
open-casket f u n e r a l , but he had no ideas on how t h i s could be accon4)lished.

29

�Conroents;

One approach t o mortuary ser vices might be t o c o n s u l t with various

museums of natural h i s t o r y .

One of t h e modern methods of taxidermy i s t o

place the animal In a l i f e - l i k e pose and f r e e z e I t in t h a t p o s i t i o n .

A vacuum

i s then drawn on t h e container, and t h e animal i s c o n p l e t e l y d e s i c c a t e d . The
desiccated specimen i s then placed in a sealed c a s e .

This technique could be

adapted t o t h e Space S t a t i o n as a method of preserving t h e body of a deceased
crew member u n t i l a r e l i e f vessel makes c o n t a c t .
35.

Foot r e s t r a i n t s a t t h e work s t a t i o n .
This question was given t o four s u b j e c t s .

Three had no comments, and one

s t a t e d t h e t r i a n g u l a r shoes used in Skylab worked f i n e .
Topics explored in t h i s question were a l s o addressed i n Questions 33 and
36.
Comments:
36.

None.

Locomotion a i d s .
Only two s u b j e c t s were asked t h i s question.

One had no comments, and the

other s a i d , 'Only what i s needed f o r f a c i l i t y and s a f e t y .

The best locomotion

i s j u s t t o head out and across!*
Co—mnts:
37.

None.

Body r e s t r a i n t s f o r t a s k s requiring extreme s t e a d i n e s s .
This question was presented t o only t h r e e s u b j e c t s .

Two f e l t i t t o be no

problem, and one s t a t e d t h a t perhaps a r i g i d arm could be i n s t a l l e d a t t h e
work s t a t i o n .

This could be swung out from a stowed p o s i t i o n and used t o

clamp t h e a s t r o n a u t i n t o p o s i t i o n .
Comments:

None.

30

�38.

Thoughts on a r t i f i c i a l g r a v i t y .
This topic was discussed with nine c o n t a c t s .

make.

Two had no connients t o

One s t a t e d c a t e g o r i c a l l y t h a t he thought t h e r e i s a d i s t i n c t medical

need for a r t i f i c i a l g r a v i t y .

Three were of t h e opinion t h a t a r t i f i c i a l

gravity should not be considered unless an overwhelming physiological need
developed.

One expressed t h e opinion t h a t when t h e time comes when we can

build very-long-term-exposure f a c i l i t i e s , a r t i f i c i a l g r a v i t y should be
provided because t h e time expended in e x e r c i s e (he estimated one t o one and a
half hours a day.) a r e nonproductive hours which could be put t o b e t t e r use i f
a r t i f i c i a l g r a v i t y were provided.
No respondent f e l t a r t i f i c i a l g r a v i t y i s required f o r psychological
reasons.
One was very s t r o n g l y opposed t o i t .

Our conversation went a s follows:

'Another thing - I wouldn't worry about a r t i f i c i a l g r a v i t y .
i s considering a r t i f i c i a l g r a v i t y any more.

I hope nobody

I t h i n k t h a t ' s a waste of time.

And you destroy many of t h e advantages you gain by being weightless.
Particularly f o r those people who may have a g r a v i t a t i o n a l handicap.
don't have a g r a v i t a t i o n a l handicap in space.

They

They ought t o be permitted t o

participate a s f u l l - f l e d g e d workers and crew members i n space.
0.

There i s some consideration being given t o t h e so-called t e t h e r

system, which w i l l provide a r t i f i c i a l g r a v i t y .
A.

Well, I ' l l t e l l you - I t h i n k t h a t ' s a waste of money, a waste of

manpower and i n t e l l e c t s t o even worry about i t .
have a good reason t o do i t .

F i f t y years from now you may

I d o n ' t t h i n k you have a good reason now.

Certainly calcium loss i s not a j u s t i f i c a t i o n , i n my o p i n i o n . "
One person f e l t t h a t t h e r e was a need f o r an a r t i f i c i a l g r a v i t y area in
the Space S t a t i o n , but he had no ideas a s t o how t h i s could be accomplished.
He said:

31

�•There are some good benefits from zero-g, but I would hope that in the
Space Station there would be some area or some volume of the Space Station
that would have artificial gravity. I don't know whether it should be the
gravity of Earth or the gravity of the moon, but some light gravity field
would prevent the deterioration, the decondltioning, of the cardiovascular
system, and also the sickness that comes Initially with exposure to the
weightless environment.'
Comments:

I am in agreement with the contact who stated that the provision of

artificial gravity negates one of the more Important reasons for being there.
Of course, it Is self-evident that If an overwhelming medical or physiological
need arises for artificial gravity. It must be provided, but lacking that, I
can see no justification for It.

The concept that the provision of artificial

gravity would eliminate the need for exercise and thus be an economically
justifiable approach warrants study.

The economics of this question Is beyond

my area of knowledge, so I do not feel competent to coiment one way or another
on the suggestion.
39.

What about autonomy?
This question was presented to eight contacts, and all but one had very

definite opinions on the subject.

Four contacts stated that they believed the

Space Station Commander should be the final authority.
ground should perform strategic planning only,

Four felt that the

other comaents included one

that the Control Center should be used only for their more extensive
resources.

Two others stated that Hisslon Control Center should be used for

routine data analysis only, and this because 1t was more economical to do this
kind of Information processing on the ground than in the Space Station.
Another connent was that the Control Center should be informative, not
protective, and finally, one person commented that the Control Center should
be absolutely honest with the flight crew; no information should be withheld
from the crew using the Justification that they were being protected by this
action. This respondent also said that the crew must be open and honest with
the ground as well.

32

�Conments;

All of t h e contacts were i n c l i n e d towards more autonomy f o r the

Space Station, and l e s s r e l i a n c e on t h e ground.
logical and a p p r o p r i a t e .

This trend seems t o be most

I concur with t h e conment t h a t t h e g r e a t e r

analytical resources on t h e ground should be used in preference t o i n - f l i g h t
analysis.
40.

U t i l i t y of a miniature helmet-mounted TV camera.
This question was presented t o only two c o n t a c t s .

useful, but only f o r c e r t a i n (unspecified) t a s k s .

One said i t might be

The o t h e r contact had no

connents t o make on t h e s u b j e c t .
Conntents:
41.

None.

What about an expendable launch vehicle rescue c a p a b i l i t y .
The question was put t o f i v e people, of which one had no comment.

Only

one person was e n t h u s i a s t i c about t h e concept and he s a i d :
"I d o n ' t s e e why n o t .

I t would be expensive, but i t would be only a

one-time expense. Once you got t h e t h i n g ready t o go, t h e expense of recycling
i t would not be t h a t g r e a t .

You could even go with a s o l i d .

have t o be reserviced a s o f t e n .

I t would not

Over a period of years t h e r e ' s going t o be

some times when i t j u s t might be needed, and i t would c e r t a i n l y pay f o r
itself.'
One said he would r a t h e r put t h e emphasis on more on-board r e l i a b i l i t y .
Another said he would r a t h e r use t h o s e resources t o expand t h e o r b l t e r f l e e t
so as t o provide a quick-rescue c a p a b i l i t y .

One individual said he would

rather have t h e escape c a p a b i l i t y b u i l t i n t o t h e Space S t a t i o n i t s e l f .
Comments:
42.

None.

How can man-on-board reduce redundancy?
This question was presented t o only f o u r c o n t a c t s .

that they had no comments.

33

Three of them said

�One s t a t e d he did not want t o g e t Involved 1n a lengthy discussion of the
question, but did want t o venture h i s opinion t h a t we a r e s t i l l designing too
much redundancy I n t o experiments because t h e s c i e n t i s t s r e f u s e t o accept t h a t
man can make up f o r i t .
Cowwents;

The comments following Question 2 point out t h e u t i l i t a r i a n value

of man on t h e scene.

Again, we should design equipment f o r r e p a i r and

maintenance on o r b i t r a t h e r than provide layer s of redundancy.
A3.

Ideas f o r design of a safe haven.
This question was put t o seven people.

Two of them had no comments.

One

s t a t e d t h a t he did not think we needed more than two s a f e havens on t h e Space
S t a t i o n ; another man said he thought every module should be I s o l a t a b l e ; and a
t h i r d suggested designing t h e s a f e haven s o t h a t t h e occupants could continue
t o be productive.

He f e l t t h i s was e s s e n t i a l t o t h e i r morale.

One contact s t a t e d , " I would put my e f f o r t s I n t o Introducing realism t o
t h e public."

When asked t o explain t h e statement he s a i d t h a t we must prepare

the public t o accept the f a c t t h a t we're going t o lose a s p a c e c r a f t sometime.
pomnents:

The suggestion t o provide means f o r crews t o remain productive as a

morale booster In t h e s a f e haven I s one t h a t deserves some thought.
44.

Philosophy f o r EVA use.
Of t h e f i v e people who were presented with t h i s q u e s t i o n , one had no

comment; two f e l t t h a t I t should be used r o u t i n e l y ; one s a i d I t should be used
when c o s t e f f e c t i v e ; and one s t a t e d only, " I am s u r e i t would be u s e f u l . "
Conmmnts:
45.

None.

On-board command s t r u c t u r e .
This question probably stimulated a s much discussion a s any of t h e 51.

was presented t o a l l ten c o n t a c t s .

Six of them unequivocally recomaended a

strong Commander with a c l e a r and d i s t i n c t chain of conmend.
p o s i t i v e voice In t h i s group was one who s a i d :

34

The most

It

�•The Commander 1s the boss—just like 1n a military vehicle [or] In polar
exploration trips.

He's the boss.

varied opinions on things.

He can appoint deputies.

He's a real strong individual.

'This is the way it's donel [Strikes table for emphasis.].

He can ask for
He's going to say,
We're not even

going to question it.'"
A considerably milder comment was made by another contact who said that a
clear chain of command was needed but, "...you don't need a man beating his
chest."
The nearly opposite view was expressed by a contact who said:
"Yog know the stereotype of Marine Drill Instructor - you don't need those
kinds of abilities up there - you need people with a broad perspective; people
who are interested in enough different things outside their own area of
expertise. I think that would be especially apropos of the Commander of the
mission."

He went on to say, "When you go to autonomy in space and you have

your scientists up there [there are going to be conflicts which the Commander
will have to solve].

You have to be able to compromise, and accommodate all

those kinds of things.

The Commander will have to be real diplomat."

Another contact recommended a strong authoritative Commander, but he has
to be the kind of person who knows how to lead, and "...just to give an order
is not the best way to lead."

But, he said, there also has to be a strong

connand structure.
One man who stated there must be a chain of command suggested that there
night possibly be a Commander for each shift with interaction between them.
He said that the Commander should be not be resistant or blind to suggestion
and inputs from the rest of the crew.

When asked if he would recommend a

military hierarchial system, he replied that he would prefer a NASA
hierarchial system, which he said is not as rigid as the military system.
Another contact also recommended a dual command system, but constructed
around different lines.

He suggested a military Commander and a scientific

35

�conmander.

The military Conroander would be in ultimate charge, but as long as

things are going well, he would delegate command to the chief scientist.

He

agreed tha,t this might be somewhat analogous to the relationship that exists
between the Captain of a carrier and his Air Sroup Commander.

The contact

stated that the ultimate responsibility must be assigned to one person.
said, 'You cannot have a voting situation up there."
NOTE:

He

The term "Hilltary Commander" as used above was not meant by the

speaker to imply that he advocated the Space Station be conuianded by a DOD
representative.
Conments:

He used it as a figure of speech.

Most of the respondents focused on the role that the Conmander must

play, and how he must act in exercising that role.

One contact really caught

the significant part of the question and stated that even more important than
the Commander's actions was the need for a strong comaand structure.

It has

been my observation that some Military Commanders get the job done by virtue
of the fact that their subordinates are afraid of them; others because they
are respected:and others because they are idolized.

Regardless of the

Commander's attitude, the job always gets done unless the conmand structure
breaks down.

Even the autocratic Commander gets the job done unless he

attempts to dissolve the command structure.

When he does that, the

organization falls apart and the mission is a failure.
46.

How Hi-Fi should the Space Station simulator be?
This question was given to five people.

Only one recownended that the

simulator have as much fidelity as possible recognizing the limits imposed by
gravity.

Two men felt that a complete simulator, a duplicate Space Station, was not
needed.

Part-task and modular simulation should be adequate.

These were

thought to be especially valuable devices for problem solving.
one man suggested that the Space Station control room should be fairly
well simulated, but the other functions of a Space Station need not be

36

�duplicated on the ground.

He suggested a minimum ground training period and

conpletion of training In the Space Station itself under the supervision of
the crew.

He presupposed that only part of the crew, perhaps two out of ten,

would be replaced at any one time.
One man had no comments.
Conments:

The suggestion that part-task and modular simulations should be

adequate seems to be a reasonable approach.

The concept of training after

arriving on station is an interesting one and might be an area for
investigation.
49.

Accommodating diverse groups of people.
Seven people were asked this question.

Two people expressed disapproval

of the concept of taking the "man on the street".

Both of these contacts felt

that, in the foreseeable future, we would be taking selected people.

One

mentioned that we would select them first for their skills, second for their
motivation, and third for their physical and mental health.
mentioned construction workers.

One contact

He thought we would ask for volunteers from

the population of construction workers, then we would select the most skilled
and the most fit.
Three contacts mentioned their opposition to the practice of applying
arbitary age limits.

They felt that the results of a physical examination

should determine a person's fitness to fly, not his age.

One mentioned a Dr.

Vincent in Houston who has a program that is an excellent predictor of mental
acuity.

The respondent thought some of the airlines were using Or. Vincent's

technique.
One stated that we could markedly relax our physical requirements because
there are no stresses in space.
Another felt that most of the problems will be societal, and the Commander
will have to deal with them.

37

�Another suggestion was t h a t planning f o r medical c a r e f a c i l i t i e s must take
Into consideration t h a t crew members of t h e f u t u r e may n o t be 1n t h e b e s t of
health o r of optimum age.
Comments;

I was pleased t o hear one of t h e contacts s t a t e t h a t we could

markedly relax our physical requirements because t h e r e a r e no s t r e s s e s In
space.

I do not know. In any g r e a t d e t a i l , what physical l i m i t a t i o n s NASA

places on s e l e c t e e s f o r space f l i g h t , but senators and school t e a c h e r s a r e now
being considered.

From a purely s c i e n t i f i c standpoint 1 t seems reasonable t o

f l y a group of "average" people t o see whether they perform any d i f f e r e n t l y
than the highly selected and superbly f i t persons we have flown In t h e p a s t .
There was r e a l l y no reason f o r s e l e c t i n g t h e cream of t h e crop a f t e r Mercury
and Gemini.

Both of those e a r l y missions had t h e unknown p o s s i b i l i t y of

requiring t h e a b i l i t y t o s u s t a i n hIgh-Q reentry followed by a survival
experience l a s t i n g several days a t sea o r on t h e d e s e r t .
e x t r a o r d i n a r i l y f i t human specimen was required.

Obviously an

We might be surprised t o

find out t h a t the average person who I s accustomed t o a more sedentary l i f e
might even perform I n t e l l e c t u a l t a s k s In space a t l e a s t a s well a s t h e more
f i t person does.
I have not followed up on t h e suggestion t h a t Or. Vincent In Houston be
contacted because of h i s a b i l i t y t o p r e d i c t mental a c u i t y s e p a r a t e from age.
50.

Thoughts regarding s a f e t y hazards.
This question was presented t o nine c o n t a c t s .

nothing t o c o n t r i b u t e .

One said t h e only thing he could t h i n k of was a k i t t o

s e a l meteorold punctures.
redundancy a s p o s s i b l e .

Three s t a t e d t h a t they had

Another suggested only t h a t we build In a s much
One person said t h a t a s i d e from t h e pure vacuum of

space, living In t h e Space Station I s no d i f f e r e n t , from a s a f e t y point of
view, than l i v i n g on Earth.

The hazards a r e t h e same and you p r o t e c t against

them with s t r u c t u r a l design. You c a n ' t p r o t e c t a g a i n s t a l l e v e n t u a l i t i e s .
f e l t compartmentallzatlon w i l l solve many problems.

38

He

�Another person made t h e s e f i v e p o i n t s :
1.

Follow e s t a b l i s h e d p r o c e d u r e s .

2.

Have two c u e s t o a p r o b l e m , i . e . , a u d i o and v i s u a l warnings i n

case one o r t h e o t h e r i s m i s s e d .
3.

Eliminate single-point failures.

He s a i d NASA has done a v e ry

?oo(l job of doing t h a t .
4.

When a f a i l u r e d o e s o c c u r , f a l l back t o a s a f e p o s i t i o n

iimediately, and examine t h e f a i l u r e .
5.

Use e x t r a o r d i n a r i l y w e l l - t r a i n e d p e o p l e i n p o s i t i o n s of p r i n c i p a l

responsibility.
One respondent urged t h a t NASA d o c a r e f u l f a i l u r e mode a n a l y s e s , and where
they discover h a z a r d s t h a t t h e crew w i l l have t o l i v e w i t h , t h e n make s u r e t h e
crew i s well t r a i n e d , o r e v e n o v e r t r a i n e d t o d e a l w i t h t h e m .
One of t h e most l e n g t h y and t h o u g h t f u l comments was:
'The hazardous s i t u a t i o n i s a c o m p l i c a t e d one i n which you a r e n o t q u i t e
sure what t o d o .

The s i m p l e r t h e s i t u a t i o n , t h e l e s s d a n g e r t h e r e i s of

screwing i t up.

I t h i n k t h e most i m p o r t a n t t h i n g from t h a t s t a n d p o i n t i n

Space S t a t i o n i s t o c l e a r l y i d e n t i f y and c o l o r - c o d e a l l t h e v a r i o u s p i e c e s of
equipment a t d i f f e r e n t l e v e l s of h a z a r d .

The most s e r i o u s b e i n g r e d , t h e n e x t

yellow, then maybe y e l l o w - a n d - b l a c k s t r i p e s .
now.

B a s i c a l l y l i k e t h e m i l i t a r y does

Mark 'NO STEP' and 'HAND HOLD', and s o f o r t h .

A c o n c e r t e d e f f o r t should

be made t o s e e t h a t we d o n ' t g e t s h a r p c o r n e r s and t h a t s o r t of t h i n g .
"The dangers a r e g o i n g t o be i n t h e p r e s s u r e s u i t p e o p l e w e a r .

With a l o t

of people up t h e r e working around t h e r e i s g o i n g t o be a s u i t p u n c t u r e , o r
swneone i s n o t g o i n g t o p u t t h e w r i s t s e a l on p r o p e r l y and a g l o v e w i l l pop
off.

Those a r e t h e k i n d s of problems we a r e g o i n g t o h a v e .

We a r e n o t going

to have any problems i n s i d e . "
Cowitents:

Of a l l t h e r e s p o n d e n t s , I c o n c u r most c l o s e l y w i t h t h e i n d i v i d u a l

who made t h e f i v e p o i n t s .

They s h o u l d be remembered and p r a c t i c e d by a l l who

have any r o l e i n s a f e t y d e s i g n o r p r a c t i c e s - and t h a t i n c l u d e s n e a r l y
everyone.

39

�51.

Suggestions which would help maintain crew h e a l t h .
This question was asked of nine c o n t a c t s .

t o make.

Two s t a t e d they had no comments

Proper n u t r i t i o n o r d i e t was mentioned by t h r e e people, a s was

proper e x e r c i s e .

Recognition t h a t people have t h e same psychological needs In

space as on Earth was mentioned frequently.

One c o n t a c t urged t h a t t h e time

l i n e be structured t o provide time f o r q u i e t r e f l e c t i o n and contemplation.
The b e n e f i t In crew member contributions t o t h e mission w i l l outweigh any cost
In time.

Another said t h a t we must choose s e n s i t i v e . I n t e l l i g e n t people t o

serve on Space S t a t i o n .

You d o n ' t need t h e "machonnan", and b r u t e - f o r c e kind

of people - they should be kept o u t .
One man s t a t e d , "Try t o make I t a s much l i k e a normal c i v i l i a n l i f e a s
possible, recognizing t h a t we're going t o have a connand s t r u c t u r e , and by
t h a t I mean If a guy wants t o have a g l a s s of wine with dinner o r a s h o t of
brandy a f t e r , he ought t o be e n t i t l e d t o do s o .
I t ' s home!"

He's not f l y i n g an a i r l i n e r -

One other man had mentioned t h a t he thought moderate consumption of
alcohol was probably b e n e f i c i a l .

Another man, who I am s u r e would have agreed

with the comments above regarding wine with t h e meals and brandy a f t e r ,
nevertheless warned against what he perceived a s t h e c u r r e n t s o c i a l acceptance
of overindulgence by m i l i t a r y p i l o t s .
s a f e flying t h e next day.

He f e l t t h a t behavior was hazardous t o

The mental health aspects of t h e Space S t a t i o n were considered by another
contact.

He s a i d , "He should allow a routine-enough work c y c l e and approach

t o Space S t a t i o n operations so t h a t If someone does g e t s1ck they can go take
a day off and r e s t .

L e t ' s ease off on t h e work load.

L e t ' s l e t the

astronomers have some time t o j u s t s i t t h e r e and look through t h e telescopes.
Hhat's wrong with t h a t ?
g r e a t Ideas anyway."
Coweents:

T h a t ' s where a l l t h e g r e a t astronomers got a l l t h e i r

Here a g a i n , I was pleased t o s e e t h e emphasis on f a c t o r s

Influ e n c i n g m e n t a l h e a l t h .

If one lesson should have been learned from a l l of

40

�our space f l i g h t p r o j e c t s , i t i s t h a t we must guard a g a i n s t overloading the
crew metrtier.

I was most impressed by t h e l a s t comment recorded, " L e t ' s ease

off on the work load.

L e t ' s l e t t h e t h e astronomers have some time t o j u s t

sit there and look through t h e t e l e s c o p e s .

What's wrong with t h a t ?

That's

where a l l the g r e a t astronomers g o t a l l t h e i r g r e a t ideas anyway."
I can only applaud t h a t a d v i c e .
SPONTANEOUS COMMENTS
As stated in t h e s e c t i o n e n t i t l e d METHOD, t h e 51 questions were a c t u a l l y
used only t o s t i m u l a t e d i s c u s s i o n .

Although a g r e a t many comments were

received in response t o t h o s e q u e s t i o n s , t h e r e were some additional statements
•ade either spontaneously o r a s a r e s u l t of thoughts stimulated by t h e
questions.

Some of t h e s e spontaneous statements a r e presented in t h i s s e c t i o n .

1. I t had been several y e a r s , and even decades, since some of t h e contacts
had flown.

One of them opened t h e interview with t h i s statement:

" I t i s i n t e r e s t i n g your coming around doing t h i s .

I commented t o [ h i s

wife] t h i s morning t h a t t h i s i s t h e f i r s t time anybody has asked my opinion
about anything s i n c e t h e day I l e f t NASA.

And, consequently, i t i s of a l o t

less value than i t might have been a year a f t e r I l e f t NASA."
Conments:

In l i g h t of t h e remark made by one c o n t a c t t h a t h i s remarks might

have had more value had he been contacted a year a f t e r leaving t h e program
rather than several years l a t e r might suggest t h a t NASA give consideration t o
establishing a procedure whereby a l l former a s t r o n a u t s would be interviewed a
year or two a f t e r they leave t h e program.

1 f e e l confident t h a t individuals

who are no longer competing f o r a f l i g h t p o s i t i o n , o r who a r e no longer hoping
for advancement i n , o r rewards from, t h e system might well be a very valuable
source of information.

Among t h e t e n people I interviewed, 1 f e l t t h a t some

of there were so long out of t h e program a s t o be of l i t t l e value t o t h i s
project.

On t h e o t h e r hand, some who were more r e c e n t menders of NASA had

•any good conments which t h e y probably would not have made had they been
corepeting f o r f l i g h t assignment.

41

�2.

One stated that he feU gymnastics might be a good training procedure,

particularly use of the trampoline, in combatting space motion sickness.
Cowwents;

3.

None.

In view of the fact that EVA astronauts do not appear to use their legs

very much, one contact was asked his opinion regarding a suit without separate
legs. He replied;
•Some of the EVA tasks would require that you anchor your feet somehow,
because that's the way you apply the torque.

If. of course, you have some

umbilical 'belly-button' kind of thing with which you attach yourself rigidly
through your center of gravity, then you could obviously use your arms pretty
well without a foot restraint.

I would kind of think that having your legs

separate would give you much better torque and muscle control."
In response to the same question another contact said•But If you're thinking In terms of a Space Station where you're going to
have to do some manual work with your arms, and you look at the situation
Where you put In a torque motion. I don't know how you would counteract that
without having your feet somehow [stabilized],

speaking of construction work

1n space he said. "It Is In that kind of a mode where I would envision that
you might want [to use your legs].'
Comments:

4.

None.

When speaking of training, one contact mentioned what he called an

advocacy position In training,

it Is sitting down ahead of time and asking

what^one will do If a certain event takes place.

He said:

•Within certain limitations you could take the advocacy role ahead of
time.

It's a 'brain-washing', and I know that's a bad word, but you train to

the point where, when you get there, the actual case Is a piece of cake.
many times It doesn't have to be a hands-on kind of training.

And

You can sit In

a room and discuss what we're going to do If this happens and why do that
one.

But you gotta go through that exercise.

42

It's a very Important part of

�getting ready t o go."

The contact then gave two examples from h i s f l i g h t

where f a m i l i a r i t y with the system and procedures saved t h e mission.
Cofiments;

The remarks regarding "advocacy" t r a i n i n g were i n t e r e s t i n g t o me.

The mental exercise of s i t t i n g q u i e t l y alone o r with o n e ' s colleagues and
contemplating possible events and how t o cope with them I s probably an
excellent way t o t r a i n f o r foreseeable e v e n t u a l i t i e s .

Perhaps such t r a i n i n g

methods could be encouraged.
5.

At the close of h i s interview, one contact offered t h e following

independent thought:
"One of t h e t h i n g s I d o n ' t think we're doing t o o w e l l . . . i s designing
things l i k e t h e Space S t a t i o n , taking advantage of t h e r eal and unique
environment.

Using t h e d e l t a temperature and t h e d e l t a pressure a s driving

forces t o some degree in equipment design.

We're s t i l l designing things f o r

here t h a t we then make a l l s o r t s of special precautions t o operate up t h e r e
instead of designing them t o r e a l l y optimize the environment they have t o be
in.

I think when t h a t happens we w i l l have problems t e s t i n g i t down here, but

i t w i n [work b e t t e r up t h e r e . ] "

When asked f o r examples he said t h a t he had

none a t t h e moment.
Comments:
6.

None.

Another contact i n explaining why he thought he did not g e t motion

sickness i n f l i g h t s a i d :
"We would go up and do parabolas in t h e T-38 where we could do between 15
and 23 r o l l s on a given parabola.
with each r o l l .

We put our head i n d i f f e r e n t o r i e n t a t i o n s

I ' d do t h a t maybe twice, and a l l of a sudden t h e sweat would

break out—you'd s i t t h e r e with t h e world going around and you'd t r y t o f l y
s t r a i g h t and level f o r f i v e minutes u n t i l you could g e t t h e world back
together again, then you'd go a t i t a g a i n .
[before t h e f l i g h t ] .

I did t h a t down a t t h e Cape

I got t o where i t r e a l l y took something t o g e t me s i c k .

I d o n ' t know whether i t was t h a t conditioning t h a t helped o r whether i t was
t h a t I was j u s t more n a t u r a l l y r e s i s t a n t than some.

43

You can do t h e same thing

�in a swlnwing pool.
nystagmus.*

You can get some pretty high rates—until you get severe

He continued t o cowaent that performing r o l l s In a zero-g parabola and
holding the head in different positions a t the same time was the most
efficient way of producing nystagmus that he knows.

He got t o the point where

he could make the world 'twitch* in any direction depending upon how he held
his head during the r o l l .
£ommsntsj_

NASA might give some thought t o investigating t h e training routine

described by the contact who stated he and his partner executed 15 t o 23 rolls
while in a zero-g parabola, with t h e i r heads in a d i f f e r e n t orientation for
each parabola.

I am astounded a t the piloting s k i l l which t h i s maneuver

requires, but if i t can be done I t might be of value i n anti-motion sickness
training.

I know that aerobatics have been attempted t o t r a i n against motion

sickness, largely without benefit, but t h i s i s the f i r s t I have heard of
stimulating the semicircular canals while in zero-g.
7.

One contact was asked for his ideas regarding the changing crews.

He said

that i t might be necessary t o bring up one o r two s p e c i a l i s t s for short
periods t o perform specific tasks, but he f e l t i t was important t o change the
e n t i r e basic crew a t the same time t o maintain a cohesive u n i t .
Comments:
8.

None.

Another Interesting concluding remark was:
"There i s one other thing I always make a pitch on. and t h a t i s that they

do not realize that people in space f l i g h t o r in zero-gravity condition are no
different than down here.

You have zero gravity and a b e t t e r view, but other

than that you are dealing with the same person and the same working
environment and they can do exactly the same thing they can do down here.

If

a person i s exceptionally good as an observer o r working out something
analytically, or if he i s good a t doing any kind of a detailed task (for
example, a photo interpreter), you can put him up there where he i s looking a t

44

�the real thing.

He can do just as good a Job up there as down here.

no reason for not using a person's intellect fully.

There is

So far, the way space

flights have been constructed, they want to dictate everything by checklist
and take away your ability to think.
Coninents;
9.

See comments following Statement 9.

Another man expressed the same thoughts in this way:
"My big 'soap box' effort is the thing about let's not forget who we are

and what our needs are as people, and carry those things with us.

Let's not

lull ourselves into thinking that this is such a special environment that all
the rules change and everything is different, and that people will give up
this and give up that In order to be up there.

They will do it for a ten-day

mission, but they won't do it for ninety days."
He went on to say, "One of the problems we ran into on our mission was
that we forgot to think about those things, and we got ourselves caught up in
a workaday thing where we were working fourteen to sixteen hours a day, and
working strictly following a carrot - following a very precise agenda every
day.

Halfway through the mission we began to get inefficient and made

mistakes.

Me finally recognized our problem and did something about it, and

came out at the end of the mission in good shape.

We finished everything we

were supposed to do and got it all right."
Comments: I commend the two remarks regarding utilization of people for their
capabilities and their human abilities to NASA for serious consideration. I
agree with both comments.

If we are to put people in space we must take

advantage of their capabilities and their "humanness", whatever that is.

He

should recognize the tendency to overschedule and actively correct for that
tendency.
10.

One contact believes that the absence of low-frequency electromagnetic

radiation in space might have some physiological consequences.
this radiation is commonly referred to as Schumann resonance.
this subject he said:

45

He said that
Speaking to

�•W1th1n the Ionosphere-Earth surface cavity there is, I think, about an
8-H2

to 32-Hz oscillating field with a series of peaks in that field that is

generated by lightning storms on Earth, but the net result of all that
electromagnetic activity is that we're exposed from conception to death to
this oscillating field, and there is some evidence that if you play with that
field here on Earth, particularly by superimposing a 5-Hz, 4-Hz, or 3-Hz field
on what is already there (and it is very difficult to isolate the individual
from it unless you go underground) and you get some neurological problems.

It

does affect people, and it is probably related to what happens to you when you
get a relatively low-frequency strobe light flashing at you.

A lot of people

feel very very uncomfortable neurologically when that happens.
course, it's absent.

In space, of

Once you get above the ionosphere that field is absent,

and there is some concern among physicists who have a background in
neurophysiology that there might be an instantaneous effect contributing to
the Space Adaptation Syndrome, but they are more concerned about what the
long-term effect may be if the brain actually uses that frquency on occasion
or continuously to reset it's own timing signals in it's central processor.
So, 1 would FLAG that as an unknown."

This contact was also concerned about "intermittent sleep."
could cause difficulty from the standpoint of loss of REH sleep.
sleep is different from simple insomnia.

He felt it
Intermittent

Intermittent sleep is that situation

where a person wakes up and goes back to sleep several times during a sleep
period.

It should cause no problem over short periods, but if continued for

two months or so it might.

It has been noticed in sleep labs on the Earth,

but the contact was of the opinion that it occurs more frequently in space
flight than it does on the Earth.

Comments; I cannot connent on the role of low-frequency electromagnetic
radiation in space and its physiological consequences and I am unaware of
"Schumann Resonance", but I do want to underline this individual's connent as
a possible route of inquiry, which NASA might investigate.

I also am unable

to comment on this same contacts remarks regarding "Intermittent Sleep".

46

�11. One man mentioned t h a t he f e l t h i s mind worked b e t t e r i n space.

When

asked t o elaborate on t h a t s u b j e c t he s a i d :
' . . . i t might be j u s t t h a t you a r e doing i t f o r r eal r a t h e r than in
practice.

The f a c t t h a t you're i n 100X oxygen environment - t h a t should allow

you t o perform a l i t t l e b e t t e r .

I think i n a place of reduced g r a v i t y , t h a t

could have a contributing f a c t o r t o o .
including mental.
Cownent;
12.

[There was a ] changed response p a t t e r n ,

That i s p a r t i c u l a r l y t r u e in the weightless s i t u a t i o n . "

None.

One contact mentioned t h a t i t took him four t o f i v e days t o g e t adjusted

to the zero-g environment.

He s a i d t h a t he knew t h a t i f he moved about

Quickly he would become s i c k , s o he moved very slowly and very d e l i b e r a t e l y
until he became accustomed t o t h e environment.
He a l s o mentioned t h a t upon h i s return t o Earth he had " v e r t i g o " .
as if t h e bed was i n c l i n e d about 30 degrees head down.
for about a week.

He f e l t

This sensation lasted

He mentions t h a t he was unable t o c l e a r h i s e a r s during

parachute descent a t t h e end of h i s mission and wonders i f t h a t did not
contribute t o h i s f e e l i n g s of " v e r t i g o " .

He believes i t would have been

interesting t o go through v e s t i b u l a r t e s t i n g during t h a t period, but o t h e r
matters seemed t o occupy t h e time of t h e physicians.
Comments:

The contact who said i t took him four t o f i v e days t o g e t adjusted

t o the zero-g environment was t h e only one of t h e group t h a t admitted t o even
the l e a s t t r o u b l e .

I found i t i n t e r e s t i n g t h a t he experienced a head-down

sensation a f t e r return t o Earth.

I would have expected him t o experience a

head-down sensation in f l i g h t due t o migration of f l u i d t o t h e head and a
head-up sensation upon return t o Earth.
13.

Several s u b j e c t s mentioned d i f f i c u l t y sleeping i n f l i g h t .

The consensus

seemed t o be t h a t f r e e - f l o a t i n g s l e e p was not comfortable o r r e s t f u l .

One man

mentioned t h a t i n o r d e r t o g e t a comfortable n i g h t ' s s l e e p , t h e head and hands
have t o be r e s t r a i n e d t o prevent them from moving about i n random fashion.

47

�Coimients; I believe this last remark regarding the unsatisfactory nature of
unrestrained or free-floating sleep has been made before, so It requires no
further Investigation, but should be kept In mind when sleep restraints In the
Space Station crew quarters are being designed.

48

�APPENDIX A
1.

Flight Crew Health Stabilization Program;
Discuss in context of SS vs Skylab, Apollo, and STS.
Worthwhile?
Retain?
Eliminate?
Modify?

2.

Do you have any thoughts on facilitating SS maintenance activities of the

crew?
3.

Discuss alarm systems:
False alarms.
Lights.
Horns.
Voice.
Tactile.

4.

Any thoughts as to tools for on-orbit repair and maintenance?
Including "work bench", location, equipment, etc.

5.

What about food and meals?
A11 eat same foods on same days?
Individually selected menu?
Suggested changes/improvements.

6.

Any suggestions regarding trash disposal?

49

�7.

Any thoughts on clothing design?
One piece c o v e r a l l s v s . pants and s h i r t ?
Pocket l o c a t i o n , design, closure?
Off-duty and on-duty.

Any d i f f e r e n c e ?

Special clothing f o r e x e r c i s e ?
What kind of sleepwear would you choose?
Any personal Items of c l o t h i n g f o r you?
8.

Suggestions a s t o personal hygiene equipment.

9.

Aids t o t r a n s f e r of massive o b j e c t s .

1 0 . Skylab crews found t h a t they o r i e n t e d t o t h e f l o o r In small compartments,
but t r a n s l a t e d h e a d - f i r s t in large compartments.

Does t h i s Influence your

thinking In regard t o I d e n t i f i c a t i o n of "up" and "down"?

Would visual

o r i e n t a t i o n cues a s t o "up" o r "down" be helpful o r harmful?
[At l e a s t one Skylab crew member reported t h a t he always o r i e n t e d down
towards h i s f e e t . ]
n . What about using vented gases f o r a t t i t u d e c o n t r o l , o r what about using
opposing vents t o cancel any e f f e c t from venting?
1 2 . What I s the Importance of p r i v a t e coniminlcatlons with o p e r a t i o n s s t a f f ,
medical s t a f f , f r i e n d s , and r e l a t i v e s ?
1 3 . Some Skylab crew members reported t h a t p o r t a b l e f ans were of l i t t l e use
f o r crew comfort, but were useful f o r equipment c o o l i n g .

Others reported that

they a r e u s e f u l , e s p e c i a l l y t o cool a person during and a f t e r e x e r c i s e .
I s your opinion?
1 4 . Oo you have any Ideas concerning:
Translation a i d s ?
Control/switch p r o t e c t i v e devices?
Orientation cues?
Protective devices f o r personal wear (helmets, g l o v e s , e t c . )

50

What

�15. Skylab crew's coimients about the airlock Included such remarks as:
It was too small for two crewmen.
Insufficient stowage volume. "Like a rat's nest during EVA.'
Lack of foot restraints.
Poor location;
-Between Multiple Docking Adapter and Orbital Workshop.
-In mainstream of traffic.
-Failure of any one of three hatches would be cause for mission
abort or even catastrophic situation (EVA crewman being trapped
outside).
OUESTIOMS: Here any of these problems present on STS?
What suggestions have you for Space Station?
16. Any Ideas about the Individual crew quarters?
Location.
General arrangement:
(1) Size (Skylab nominal was 28 In. x 38 In. x 78 In.).
(2) Restraints.
(3) Stowage.
Noise.
Lighting.
Temperature.
Ventilation.
What kind of sleep restraint?
Should washing and toilet facilities be Included?
-Cofflode?
-Urinal?
-Both?
What about shift occupancy?
Communications?
Warning signals?

51

�17. How much medical training should crew members have?
Equivalent to CNT?
More?

Less?

18. Oo you believe crew members should engage in 'group dynamics* training
before being assigned to SS?

Should one CH be trained in this discipline?

19. Should families be given similar psychological training and support?
20. What about crew interaction training in a one-g simulator?
21. How much of a problem is ambient noise?
22. Wardroom:
What suggestions for entertainment?
Will external viewing be of great importance from a recreational
standpoint?
Is It Important that the Earth appear "down"?
23. Discuss body waste collection and disposal.
24. Personal cleanliness.
Shaving.
Haircuts.
Showers.
25. Exercise.
What kind?
26. How best to manage books and manuals.
Should everything be in data banks with CRT display?
27. Han/machine interfaces.
Brightness.
Shape, color, texture.

52

�28. Three shifts or one (or two)?
All sleep at the same time?
How long a work day?

Eight hours?

Hore?

Less?

Should work time Include one to two hours of exercise, or should all
exercise be performed In off-duty time?
29. How Important would be real-time TV, Including network news?
30. l&gt;/ho should select the crew?
What Input should crew members have In regard to crew composition?
31. Does EVA require "buddy system" or can one person do It alone with
monitoring from the Inside?
32. How can the EVA suit be Improved?
Urine collection.
Fecal collection.
Provision for food and water.
Vomiting.
33. EVA
Restraints and tethers.
Hand and foot holds.
Lighting.

Helmet mounted?

Tools.
34. With a twenty-one-day rescue time at worst, do you have any suggestions
regarding mortuary services?
35. What about foot restraints at the work station?
Locking grid and shoe.
Stirrups.
Clangs.
Velcro.
Other.

53

�36. Loconotlon aids.
Lines, slldewlres.
Distributed handles.
Other.
37. What about body restraints for tasks requiring extreme steadiness?
3B. Any thoughts on artificial gravity?
Need.
Methods.
Rotating SS.
Tether.
Continuous or Intermittent?
39. What about autonomy?
Is "control" by NCC a pain, or Is It reassuring?
40. Would a miniature helmet-mounted TV to record EVA activities be useful?
41. What about an ELV rescue capability?
capsules.

For example, a Titan with reentry

42. How can man-on-board reduce redundancy?
43. Any Ideas for design of a safe haven for two to three weeks' occupancy?
44. What about EVA?
Use only for contingency?
Use for contingency and major tasks only?
Design for and use routinely?
45. On-board command structure:
Strong, authoritative Comnander with clear chain of command?
Participative management?
Coenlttee decision making?

54

�46. How H1-F1 should the SS simulator be?
47. Is the orbiter overdesigned for safety?
Can safety requirements be relaxed for SS?

Any examples?

48. Any suggestions as to docking techniques or aids?
Proximity operations.
Approach corridors.
Plume impingement considerations.
Others.
49. In the future many diverse groups of people will have to participate in
Space Station activities.

For many of these people—scientists, construction

workers, and so forth—there will be no arbitrary age limit.
Can you think of any investigations that should be performed now, either
to select those persons or to accommodate them in flight?
50. Do you have any thoughts as regards safety hazards?
51. Do you have any suggestions as to measures that would help maintain crew
health?

55

��National Aeronautics and
Space Administration

APPENDIX B

Ames Research Center
Moffett Field. California 94035

rUASA

aeiirioAdnai: LMA:239-2

Dear Space Missioa Participant:

The purpose of this letter is to introduce Dr« William K« Douglas and a
project that he is conducting under the sponsorship of NASA's Anes
Research Center.
The Ames Man-Vehicle Systems Research Division under its Space Human Fac­
tors Office is in the process of planning research that will help to as­
sure high levels of crew effectiveness on future space missions, including
NASA's proposed space station. Several expected differences between the
space station and previous missions suggest that such research is warrant­
ed. Such differences include more heterogeneity of crew members in back­
ground and experience, broader variety of work requirements (including
more EVA), larger crews, and longer durations.
To accommodate some of these changes, plans and designs are being
developed for configurations of the total station, individual modules, and
work stations, as well as for habitability Issues and operational pro­
cedures.
In many cases the appropriate design or plan for promoting and
maintaining effective crew performance under the changing conditions is
unknown. Numerous cases involving new designs for work stations and habi­
tats have been documented, in which serious performance problems have ar­
isen because of either the lack of human factors information or the
failure to incorporate available information.
The Division has been active for several years in research to support the
aviation community in developing methods for avoiding such errors in
design, and operations. One of the more valuable sources of Information
that has directed our research activities has been the Aviation Safety Re­
porting System (ASRS), which we direct (through a contract, under the
sponsorship of the FAA).
The system solicits voluntary comments and
recommendations from pilots and air traffic controllers that concern any
procedural problems encountered in the aviation system, and how these
might be corrected. The reports are completely deidentified to insure
anonymity of the reporter.
Publication of the obtained information is
generally in the form of a report that synthesises Individual comments and
recommendations related to some particular Issue.
Information such as that generated by the ASRS has proven of value, not
only by indicating problems that require research for their solution, but
by Indicating when research is unnecessary, either because Information is
available to effect a solution, research is already in progress, or the

57

�problem Is not amenable to research. When research has been prescribed,
the value of Its product has been enhanced significantly by the direction
received from such information.
The project being conducted by Dr. Douglas Is consistent with the intent
and spirit of the ASRS. We are convinced that the experience of partici­
pants in previous space missions can form the basis for cogent recommenda­
tions for design, operations, and appropriate research relevant to future
space missions, similarly to our experience in aviation.
Therefore, we
have asked Dr. Douglas to solicit thoughts regarding apace station design
and operational requirements. The information obtained will be used to
help us (and others) supply guidelines to designers, and to discover
inadequacies in available knowledge that Indicate a need for further
research.
Dr. Douglas has contacted you as part of that process.
Dr. Douglas was
the first flight surgeon for the Mercury astronauts. We sought his assis­
tance in this project because of his reputation for sensitivity, objec­
tivity, general knowledge of and appreciation for the human in space mis­
sions, and his acquaintance with many members of the astronaut corps.
We are requesting your participation because of our sincere interest in
helping to assure a high level of effectiveness for future manned space
missions. Dr. Douglas' approach will be informal.
He will ask you a
series of questions designed to focus your consideration of design and
operational Issues, which we judge are important to the success of future
missions.
In your answers to the questions we are asking you to project
from your experience to the expected conditions on a space station.
We are not interested in documenting or reporting problems, either person­
al or general, from past missions. Rather, we are asking for your judg­
ment of where impediments to task performance, motivation, morale, etc.
could arise; what changes in design and operations would you recommend,
based on your experience and expected mission differences.
Dr. Douglas will be assisted on the project by Mr. Donald K. (Deke) Slayton, whom you may know personally. Mr. Slayton's experience and knowledge
should be of great assistance to Dr. Douglas in interpreting and syn­
thesizing the information, and producing a useful report.
Please be assured, should you elect to participate, that the information
obtained by Dr. Douglas will be completely deidentified from you as the
source. Not only will your individual anonymity be assured with respect
to specific information that you volunteer, but the identity of those per­
sons interviewed will not be revealed by Dr. Douglas or Mr. Slayton.

58

��1 fttcori No.
NASA CR-3942
4. Titlf and SuMiM

2. Geynwuwi HICHDH NO.

Human Performance Issues Arising From Manned Space
Station Missions
J

Autttorlll

3. Reopant't Cralog No.
&amp; Report Dite
October 1986
e. Performing Orgeniotlon Code
8. Perfornung Or^izabon Report No.

William K. Douglas
9. ^lormina Orfonitation Nama and Addras
McDonnell Douglas Astronautics Company
3301 Bolsa Avenue
Huntington Beach, CA 92647
17 Soomortnf A^ncy Nama and Addra«
National Aeronautics and Space Administration
Washington, DC 20546

MDC H1363
10. Work Unit No.
11. Contract or Grant No.
NAS2-11723
13. Type of Report and Period Ceiwad
14. Sporaoring Agency Coda
FLS

IS Supplamantary Nolat
The author was the flight surgeon for the original Mercury Seven Astronauts.
Point of Contact: Trleve A. Tanner, MS239-2
(415)694-5185
Ames Research Center. Moffett Field. CA 94035 FTS464-5185
IS Aeanoei
Ten former NASA astonauts were Interviewed using a set of 51 questions
developed to encourage the contacts to discuss any thoughts, opinions, con­
clusions, or suggestions which might have evolved since they left the astronaut
program.
Strict confidentiality was maintained. The reader will not be able to
attribute any recorded remark to an individual person or to a particular mis­
sion.
At least one astronaut from each of the NASA manned space flight programs,
excluding the Space Transportation System (Shuttle), was Interviewed. The
report records the answers to the questions asked, spontaneous comments, and
the Investigator's oim personal evaluations of the material obtained. No
statistical analysis of the material was attempted.
The professional opinions of these ten experienced astronauts will be
of value to persons concerned with the design and operation of mannoH space
craft and manned space stations.

17 Key Warm ISunxtad by AutbarNIl
l&amp; OtiMutMn StPMiweW
Crew health, maintenance, alarms, food,
Unclassified - Unlimited
clothing, personal hygiene, "up and
down" identification, private communi­
Subject Category 54
cations, psychological support, crew
selection, group dynamics, crew quartet s
19 Secieity OmuI.|o(itM'•pert)
20. Sacurilv Otmri.lef tN* page)
21. No. of Pagn
22
Unclassified
Unclassified
62
'Forseleby the Nst&gt;onii T*hriieel Infemriitttn Semee.Spnflgfield, Virgmi* 22161

.

A04
^

NASA'LANGLEY, 1986

��National Aeronautics and
Space Administration
Code NIT-4

BULK RATE
POSTAGE &amp; FEES PAID
NASA
Permit No. G-27

Washington, D.C.
20546-0001
0*hcrat Business
Penalty toi Pftfjie Use. S300

rwvsA

M-sCT^ AcxrB •
njS&gt;lMA^IkK.

If Undelfvcrablc (SBCCiun 156
MtnuBl) Do Not Return

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="21">
      <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="1071">
                  <text>Skylab Collection</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="1072">
                  <text>1973-1979</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="1073">
                  <text>https://libguides.uah.edu/ld.php?content_id=10578214&lt;br /&gt;&lt;br /&gt;&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/80"&gt;View the Skylab Collection finding aid on 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="17146">
                  <text>Skylab Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201654">
                  <text>Skylab was the first space station operated by NASA; it was launched without a crew on May 14, 1973. Skylab had three manned missions: Skylab 2, launched May 25, 1973, lasting 28 days, Skylab 3, launched July 28, 1973, lasting 60 days, and Skylab 4, launched November 16, 1973, lasting 84 days. Crews on Skylab conducted a variety of experiments during their missions, including experiments in human physiology, circadian rhythms, solar physics and astronomy, and material sciences. Important earth resources studies were conducting including studies on geology, hurricanes, and land and vegetation patterns.&#13;
&#13;
Two of the more important components for conducting research on Skylab were the Apollo Telescope Mount (ATM) and the Earth Resources Experiment Package (EREP). The ATM was a multi-spectral solar observatory, and NASA’s first full-scale manned astronomical observatory in space. The ATM yielded a significant number of images and provided useful data for understanding our sun. The EREP provided thousands of images of the Earth’s surface in visible, infrared, and microwave spectral regions.&#13;
&#13;
Skylab remained in orbit, unoccupied after the Skylab 4 mission, until July 11, 1973, when the space station reentered Earth’s atmosphere.&#13;
&#13;
References:&#13;
&#13;
https://en.wikipedia.org/wiki/Skylab#Manned_missions&#13;
&#13;
https://www.nasa.gov/missions/shuttle/f_skylab1.html&#13;
&#13;
https://history.nasa.gov/SP-402/ch4.htm</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="214103">
                <text>sdsp_skyl_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214104">
                <text>"Human Performance Issues Arising From Manned Space Station Missions."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214105">
                <text>This is a series of interviews with various anonymous astronauts from various programs including Skylab, focused on the future of manned spaceflight.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214106">
                <text>Douglas, William K.</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="214107">
                <text>1986-10-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="214108">
                <text>1980-1990</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214109">
                <text>McDonnell Douglas Corporation</text>
              </elementText>
              <elementText elementTextId="214110">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
              <elementText elementTextId="214111">
                <text>Skylab Program</text>
              </elementText>
              <elementText elementTextId="214112">
                <text>Human factors in engineering design</text>
              </elementText>
              <elementText elementTextId="214113">
                <text>Neutral buoyancy simulation</text>
              </elementText>
              <elementText elementTextId="214114">
                <text>Provisioning</text>
              </elementText>
              <elementText elementTextId="214115">
                <text>Airlock modules</text>
              </elementText>
              <elementText elementTextId="214116">
                <text>Extravehicular mobility units</text>
              </elementText>
              <elementText elementTextId="214117">
                <text>Experimentation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214118">
                <text>Interviews</text>
              </elementText>
              <elementText elementTextId="214119">
                <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="214120">
                <text>Skylab Collection</text>
              </elementText>
              <elementText elementTextId="214121">
                <text>Box 16, Folder 2</text>
              </elementText>
              <elementText elementTextId="215979">
                <text>University of Alabama in Huntsville Archives and Special Collections, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214122">
                <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="214123">
                <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="214124">
                <text>Skylab Document Scanning Project Metadata</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="22">
        <name>Skylab 50th Anniversary</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="4741" public="1" featured="0">
    <fileContainer>
      <file fileId="3962">
        <src>https://digitalprojects.uah.edu/files/original/33/4741/loc_gold_000424_000424.pdf</src>
        <authentication>722b16bf0779b8c7232b197ad85b64a2</authentication>
      </file>
    </fileContainer>
    <collection collectionId="33">
      <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="3811">
                  <text>Goldsmith-Schiffman 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="17135">
                  <text>Goldsmith-Schiffman Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201651">
                  <text>&lt;p&gt;"My ancestors were all German Jewish immigrants, members of four families who settled in Huntsville, Alabama before and following the Civil War. The Bernstein, Herstein and Schiffman families arrived during the 1850s, and Oscar Goldsmith arrived in 1879. Subsequent generations united these four families in marriage. Members of the extended family have figured in every phase of the history of Huntsville, both economically and socially; from the agrarian years of the nineteenth century through Huntsville’s growth after World War II, to becoming known as Rocket City USA; and socially, from the time of institutionalized slavery before the Civil War to segregation followed by the civil rights era."&lt;/p&gt;
&lt;p&gt;-&lt;a href="https://www.myjewishlearning.com/southern-and-jewish/highlighting-the-history-of-huntsvilles-jewish-community/"&gt;Margaret Anne Goldsmith in an interview with My Jewish Learning&lt;/a&gt;&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="91693">
                <text>loc_gold_000424_000424</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="91694">
                <text>Letter to J. P. Fuller from Lewis Douglass.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="91695">
                <text>Lewis Douglass writes to J. P. Fuller authorizing I. Schiffman to take control of his land.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="91696">
                <text>Douglass, Lewis</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="91697">
                <text>1909-11-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="91698">
                <text>1900-1909</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="91699">
                <text>Business</text>
              </elementText>
              <elementText elementTextId="91700">
                <text>Land use</text>
              </elementText>
              <elementText elementTextId="91701">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="91702">
                <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="91703">
                <text>Correspondence</text>
              </elementText>
              <elementText elementTextId="91704">
                <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="91705">
                <text>I. Schiffman and Company</text>
              </elementText>
              <elementText elementTextId="91706">
                <text>Box 27, Folder 1904</text>
              </elementText>
              <elementText elementTextId="207992">
                <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="91708">
                <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="91709">
                <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="91710">
                <text>loc_gold_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="544" public="1" featured="0">
    <fileContainer>
      <file fileId="388">
        <src>https://digitalprojects.uah.edu/files/original/39/544/spc_mraz_0000059.pdf</src>
        <authentication>c36d5d7458a2f7c4ce66f7d8669f5017</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="176814">
                    <text>CITATION
WILLIAM A. MRAZEK

Upon William A. Mrazek, internationally noted space
engineer and scientist, by choice a citizen of the United States
and a resident of Alabama, whose truly exceptional foresight
and judgment in planning, scheduling and directing design and
development activities have been highly instrumental in an
extraordinary number of space "firsts, 11 including: the nation's
first successful ballistic missile, the nation's first successful
intermediate range ballistic missile, the nation's first success­
ful satellite, the Army's first solid propellant missile, the
vehicle for the nation I s first two manned space flights, the
highly successful Saturn C-1 the largest known booster, and
the Saturn C-5 the vehicle to be used for the initial manned
lunar landing;
Whose willingness and ability to impart knowledge of vehicle
systems to industry has hastened the assimilation of technology
by contractors and has thereby contributed greatly to the space
effort and to the national standard of living;
And whose tremendous technical capability has led him to
be termed Marshall Space Flight Center• s chief engineer.
By virtue of the authority vested in me by the Board of
Trustees of Auburn University, I do now confer the Degree of:
DOCTOR OF SCIENCE, HONORIS CAUSA
together with all the rights, privileges and obligations thereunto
pertaining.

�1�iHi. �aug
President·

'

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="39">
      <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="9130">
                  <text>William A. Mrazek Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="90">
              <name>Provenance</name>
              <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
              <elementTextContainer>
                <elementText elementTextId="9131">
                  <text>This collection is digital only. This collection was generously lent to UAH for digitization by Ursula Mrazek Vann.</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="17130">
                  <text>William A. Mrazek Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201648">
                  <text>William Anthony Mrazek “(October 20, 1911 to February 8, 1992)” received his education at Deutsche Technische Hochschule, Brünn, Germany, graduating with an engineering diploma in 1935 (Wade, Lundquist). Mrazek worked at Peenemünde from 1941 to 1945 as a loads engineer (Lundquist, Wade). He worked with Wernher von Braun at Peenemünde. &lt;br /&gt;&lt;br /&gt;Mrazek was brought to America through Operation Paperclip and arrived at Fort Bliss on April 8, 1946 (Wade, Lundquist). In 1950, Mrazek moved to Huntsville, Alabama, and worked for the U.S. Army’s rocket programs until 1960.&lt;br /&gt;&lt;br /&gt;By 1960, Mrazek became Director, Structures and Mechanics Division at the George C. Marshall Space Flight Center, and by February 1969, he became the Assistant Director for Engineering for Industrial Operations (Wade, Lundquist). Mrazek later served as the “Chief Engineer for all Saturn development and fabrication work, reporting to the Saturn V Project Manager,” from “1965 to 1970” (Lundquist).&lt;br /&gt;&lt;br /&gt;Mrazek retired from the Marshall Space Flight Center in 1973 (Lundquist).&lt;br /&gt;&lt;br /&gt;Works Cited&lt;br /&gt;&lt;br /&gt;Lundquist, Charles. "Transplanted Rocket Pioneers," 2015.&lt;br /&gt;&lt;br /&gt;Wade, Mark. "Mrazek, Willi." &lt;em&gt;Encyclopedia Astronautica&lt;/em&gt;, http://www.astronautix.com/m/mrazek.html.</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="9334">
                <text>spc_mraz_0000059</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9335">
                <text>Citation for Doctor of Science, Honoris Causa degree presented to William A. Mrazek.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9336">
                <text>Given by Auburn University president Ralph Brown Draughon, the citation notes Mrazek's accomplishments as "Marshall Space Flight Center's chief engineer."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9337">
                <text>Draughon, Ralph B. (Ralph Brown), 1899-</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="9338">
                <text>1962</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9339">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9340">
                <text>Mrazek, William A.</text>
              </elementText>
              <elementText elementTextId="9341">
                <text>Aeronautical engineers</text>
              </elementText>
              <elementText elementTextId="9342">
                <text>Honorary degrees</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9343">
                <text>Diplomas</text>
              </elementText>
              <elementText elementTextId="34521">
                <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="9345">
                <text>William A. Mrazek Collection</text>
              </elementText>
              <elementText elementTextId="205350">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="90">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="9347">
                <text>This collection is digital only. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="9348">
                <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="9349">
                <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="9350">
                <text>spc_mraz_2019_03</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10952" public="1" featured="0">
    <fileContainer>
      <file fileId="9463">
        <src>https://digitalprojects.uah.edu/files/original/20/10952/Huntisasdec68_040709153450.pdf</src>
        <authentication>60e6e99d0e7c002ab551c0b878feb87e</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="166851">
                <text>Huntisasdec68.pdf</text>
              </elementText>
              <elementText elementTextId="166852">
                <text>spc_stnv_000330</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166853">
                <text>Huntsville Isascope: Volume V, No. 9.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166854">
                <text>The following article is a digest from the Book, "From Peenemunde to Outer Space", commemorating the fiftieth birthday of Wernher von Braun, March 23, 1962 condensed by H. M. Hammac).</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166855">
                <text>Driscoll, Daniel H.</text>
              </elementText>
              <elementText elementTextId="166856">
                <text>Schuler, Albert E.</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="166857">
                <text>1968-12-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="166858">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166859">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="166860">
                <text>Measuring instruments</text>
              </elementText>
              <elementText elementTextId="166861">
                <text>Rocket engines</text>
              </elementText>
              <elementText elementTextId="166862">
                <text>Liquid propellant rockets</text>
              </elementText>
              <elementText elementTextId="166863">
                <text>V-2 missile</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166864">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="166865">
                <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="166866">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="166867">
                <text>Box 29, Folder 29</text>
              </elementText>
              <elementText elementTextId="210644">
                <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="166869">
                <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="166870">
                <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="166871">
                <text>spc_stnv_000325_000349</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="166872">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18015"&gt; View this item in ArchivesSpace. &lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3276" public="1" featured="0">
    <fileContainer>
      <file fileId="2520">
        <src>https://digitalprojects.uah.edu/files/original/76/3276/loc_burw_-64.pdf</src>
        <authentication>aa823131810e5755a56a6162508dca74</authentication>
      </file>
    </fileContainer>
    <collection collectionId="76">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="28299">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="28300">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="133718">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/145" target="_blank" rel="noreferrer noopener"&gt;View the Burwell Family Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="133721">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3332" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1943-1944&lt;/a&gt;</text>
                </elementText>
                <elementText elementTextId="133722">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3333" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1944-1945&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="90">
              <name>Provenance</name>
              <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
              <elementTextContainer>
                <elementText elementTextId="133723">
                  <text>Materials donated and digitized by Dudley Burwell</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="64649">
                <text>loc_burw_000064</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64650">
                <text>Approval for Edwin D. Burwell Jr. to travel to Ireland for four days.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64651">
                <text>Driver, Don.</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="64652">
                <text>8/29/1945</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="64653">
                <text>1940-1949</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64654">
                <text>Burwell, Edwin D., Jr.</text>
              </elementText>
              <elementText elementTextId="64655">
                <text>United States. Army--Leaves and furloughs</text>
              </elementText>
              <elementText elementTextId="64656">
                <text>World War, 1939-1945--Military personnel</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64657">
                <text>Correspondence</text>
              </elementText>
              <elementText elementTextId="64658">
                <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="64659">
                <text>Burwell Family Collection</text>
              </elementText>
              <elementText elementTextId="206633">
                <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="64661">
                <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="64662">
                <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="64663">
                <text>loc_burw_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7572" public="1" featured="0">
    <fileContainer>
      <file fileId="6532">
        <src>https://digitalprojects.uah.edu/files/original/109/7572/r01c01-02.pdf</src>
        <authentication>d9fdee329b190118d4802afaa348f1dc</authentication>
      </file>
    </fileContainer>
    <collection collectionId="109">
      <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="124691">
                  <text>Series 01, Subseries C: Cabaniss Personal Correspondence</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="124692">
                  <text>Series 01, Subseries C: Cabaniss Personal Correspondence</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="128337">
                  <text>Subseries C, Cabaniss Personal Correspondence (CPC), consists of correspondence from letters from friends, relatives, and their children. Most of the family correspondence involves these children and families of S. D. Cabaniss, and his brothers and sisters who appeared to have been enormous burdens in these difficult years. These papers are sorted "to whom," "from whom," and then chronologically.</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="130896">
                <text>r01c01-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130898">
                <text>From Allen, Drury M., Jr., to Cabaniss, Charles Eugene, 1866-1869?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="130899">
                <text>r01c-210910</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178385">
                <text>Drury, Allen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="178386">
                <text>1860-1869</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178387">
                <text>Cats</text>
              </elementText>
              <elementText elementTextId="178388">
                <text>Cousins</text>
              </elementText>
              <elementText elementTextId="178389">
                <text>Charlottesville (Va.)</text>
              </elementText>
              <elementText elementTextId="178390">
                <text>Letters of introduction</text>
              </elementText>
              <elementText elementTextId="178391">
                <text>Cabaniss, Charles E. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178392">
                <text>Correspondence</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178393">
                <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="178394">
                <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="221011">
                <text>Frances C. Roberts Collection,  Series 1, Subseries C, Box 1, Folder 2, University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1262" public="1" featured="0">
    <fileContainer>
      <file fileId="1109">
        <src>https://digitalprojects.uah.edu/files/original/20/1262/spc_stnv_000119.pdf</src>
        <authentication>374a312919d60522d6a137389f89f4a6</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177310">
                    <text>DOUGLAS PAPER NO. 4054

SATURN UISTORY DOCUMENT
University of Alabema Research lnstitclte
History of Science &amp; Technology Grout,
-.rm3p"4"&amp;$IT.

Date --,-,Doc.
,,
No.
,,

-----,em

ASSURANCE AND MEASUREMENT OF
SPACE VEHICLE ALIGNMENT

PREPAREDSY

A.W.

DRYDEN

QUALITY ENGINEER
Q U A L I T Y E N G I N E E R I N G . R E L I A B I L I T Y ASSURANCE
SPACE SYSTEMS C E N T E R
DOUGLAS A I R C q A F T COMPANY. I N C .
HUNTINGTON BEACH. CALIFORNIA

PRESENTED T O

Z l S T ANNUAL T E C H N I C A L C O N F E R E N C E
F O R T H E AMERICAN S O C I E T Y FOR
QUALITY CONTROL
CHICAGO. ILLINOIS
30 MAY T O 2 J U N E 1987

�ASSURANCE AND MEASUREMENT O F
SPACE VEHICLE ALIGNMENT
A. W. Dryden, Quality Engineer
Reliability A s s u r a n c e
Douglas A i r c r a f t Company, Inc.
Space S y s t e m s Center
Huntington Beach, California
INTRODU CTION

T h i s p a p e r d i s c u s s e s the techniques implemented a t the Douglas A i r c r a f t
Company, Inc.,

M i s s i l e and Space Systems Division (MSSD), to m e a s u r e and

e n s u r e t h a t alignment of s p a c e vehicles conforms to design r e q u i r e m e n t s .
The intent of the p a p e r i s to d i s s e m i n a t e useful specialized information and
knowledge to enable those i n t e r e s t e d to keep a b r e a s t of technical advances.
Equipment and methods u s e d to align l a r g e s p a c e vehicles a r e i l l u s t r a t e d .
Combinations of s t a n d a r d c o m m e r c i a l tools, optical i n s t r u m e n t s , s p e c i a l l y
designed tools, f i x t u r e s , and equipment a r e employed to prove vehicle
alignment.

Special techniques developed to align l a r g e cylindrical, s p h e r i c a l ,

and c o n i c a l s t r u c t u r e s f o r rotational displacement, relationship of t r u e
c e n t e r l i n e , and engine geometry to vehicle a x i s a r e discussed.

Considera-

tion is given to f u t u r e alignment p r o b l e m s c r e a t e d by technological advances
and quality c o n t r o l s to e n s u r e hieh s t a n d a r d s that m e e t t o m o r r o w ' s
requirements.
SPACE VEHICLE ALIGNMENT- -ASSURANCE AND MEASUREMENT
Alignment i s the adjustment of a component' o r the interfacing of a s u b a s s e m bly and m a j o r s t r u c t u r e to a p r e d e t e r m i n e d line, point, o r basic r e f e r e n c e

system.

Alignment r e q u i r e m e n t s m u s t be imposed upon c o n t r a c t o r s to e n s u r e

uniformity of product.

A c c u r a t e alignment d a t a a r e of g r e a t value in d e t e r -

mining v a r i o u s design p a r a m e t e r s .

�Contractual Requirements
In the space program, numerous c o n t r a c t o r s participate jointly in the design

and fabrication efforts to produce multistage boosters and space vehicles.
To m e e t the demands f o r g r e a t e r dimensional accuracy and interface and
interchangeability r e q u i r e m e n t s , the contractors must adhere s t r i c t l y to a
rigid s y s t e m of measurement.

Contractual alignment requirements provide

the c u s t o m e r with objectives that e n s u r e that s t r u c t u r a l components achieve
acceptable and compatible s t r u c t u r a l integrity.
Data f o r Product Evaluation
Accurate alignment data a r e extremely important since they enable the
engineer to evaluate the effects of allowable s t r u c t u r a l and control misalignments.

Data furnish the b a s i s f o r the analysis of permissible and expected

dimensional tolerances, load distribution, load limits, and s t r u c t u r a l
adequacy.
Types of Structures Aligned
I t i s interesting to note the various
configurations involved in alignment,
Figure 1 i l l u s t r a t e s the t h r e e types
of s t r u c t u r e s that a r e of p r i m a r y
concern: cylinders, partial s p h e r e s ,
and cones.
The basic cylinder section i s conStructed of aluminum alloy segments.
The i n t e r i o r of the segments a r e
milled to a waffle -like pattern, then
formed to contour.

The s e g m e n t s

a r e progressively joined by welding
until the cylinder i s complete

Figure 1. Saturn IBIS-IVB Location of
Major Components

(Reference 1).

�"Orange peel" segments of partial spheres o r domes a r e formed to a
spherical radius, then mounted in special fixtures and welded progressively
to completion.
The thrust structure i s an example of a conical component.

The assembly

consists of attach angles and stringers riveted to aluminum skins and joined

-

to the engine mount casting.
ALIGNMENT METHODS
The size of large components and their relationship to required accuracies
generate numerous problems in the a r e a s of alignment and measurement.

To

meet these complicated and challenging problems, i t i s necessary to develop
mechanical and optical techniques f a r more sophisticated than those applied
to normal a i r c r a f t methods (Reference 2).

Specially designed tools a r e

fabricated to assemble huge components to exacting tolerances.
emphasizes precision and simplicity.

The design

A tool-proving cycle i s performed

thoroughly to guard against the p r e s s u r e s of tight manufacturing schedules
and l o s s of dimensional integrity (Reference 3 ) .

Proven success in the

performance of the tools i s necessary to ensure accurate results in the
alignment process.
Tooling a s an Inspection Medium
Use of tooling a s a medium of inspection permits g r e a t e r flexibility, f a s t e r
set-up time, and e a s i e r verification of control points.

Liaison between

quality engineering and manufacturing engineering in the tool design and
fabrication phase enables implementation o f inspection media.

Desirable

features a r e a s follows:
1.

Rotation capability that provides a means for turning the vehicle to
perform inspections during manufacturing.

2.

Floor target reference points which establish a basic reference
plane independent of that of the assembly tool, thus enabling
detection of any change o r misalignment in the assembly tool by
comparison of the reference systems.

�3.

Interfacing planes accurately machined to within 0.0 10 in. to e n s u r e
control of p a r a l l e l i s m while l a r g e vehicle components a r e being
a s s e mbled.

4.

Mastered hole patterns and index points f o r control of interchangeability requirements of l a r g e geometries. Index points furnish
positive component location and protect against rotational
misalignment.

Dial Indicators--Dial indicators a r e fine precision instruments which have a
number of applications and a r e capable of reaching virtually i n a c c e s s i b l e
areas.

Fabrication of indicator attach points a s p a r t of the a s s e m b l y tool

facilities i n - p r o c e s s checking and inspection.

Inspections combining rotation

and u s e of indicators a r e performed to (1) verify horizontal datum plane runout
and to (2) obtain concentricity and centroidal data to verify compliance with
engineering requirements.
Optical Instruments --The u s e of
optical i n s t r u m e n t s and optical
tooling has rapidly become e s t a b lished a s the only a c c u r a t e method
of performing m e a s u r e m e n t s o n
objects which a r e too l a r g e to p e r m i t
u s e of s u r f a c e plates o r s i m i l a r fixed
machined s u r f a c e s a s a b a s i s f o r
mechanical measurements.
F i g u r e 2 i l l u s t r a t e s the u s e of optic a l equipment and tooling to verify
vehicle alignment (Reference 4).
Jig T r a n s i t s -- The jig t r a n s i t e s t a b l i s h e s a v e r t i c a l plane, in any
location desired, between two e s t a b lished points a n d / o r p r e c i s e l y a t
right angles to any o t h e r line

Figure 2. Verifying Alignment with Optical
Equipment and Tooling

sight.

of^
I
I

�P r e c i s i o n Sight L e v e l s - - P r e c i s i o n sight levels establish a horizontal plane at
any d e s i r e d height.
Microptic Clinometer- -The precision microptic clinometer, an i n s t r u m e n t
capable of measuring minutes of a r c , is used to m e a s u r e angular displacements with consistent a c c u r a c i e s of 10 s e c of arc.

Values can be r e a d

directly.
ALIGNMENT POSITIONS
It i s important to consider alignment position.

A simple approach i s m o r e

often the c o r r e c t and m o s t economically feasible.

Experienced judgment m u s t

be e x e r c i s e d in a g r e a t number of instances.
Horizontal Alignment
Horizontal alignment, though d e s i r a b l e i n many r e s p e c t s , has limitations
which m u s t be considered:
1.

The vehicle configuration must be complete.

2.

In the horizontal position, loads a r e shifted and in many i n s t a n c e s
s t r e s s e s a r e c r e a t e d , making it difficult to obtain a c c u r a t e data.

3.

Additional tooling f o r supporting and handling the vehicle is often
required.

4.

F o r c e d implementation of nonscheduled manufacturing flow and outof-position techniques a r e utilized.

Vertical Alignment
Vehicle v e r t i c a l alignment through the c e n t r a l axis m u s t be accomplished
during the manufacturing phases.

The following significant f a c t o r s favor

adoption of v e r t i c a l alignment techniques :
1.

L a r g e s t r u c t u r e s and subassemblies a r e joined with the vehicle i n a
n o r m a l flight attitude.

2.

Tools designed to join the a s s e m b l i e s provide an inspection medium,

3.

Alignment verification is compatible with the manufacturing schedule.

�The c r i t i c a l alignment requirements f o r achieving v e r t i c a l alignments a r e
established by measuring the following:
1.

Rotational alignment.

2.

T r u e centerline location.

3.

Relationship of engine geometry to vehicle.

Rotational Alignment--Figure 3 i l l u s t r a t e s the method established to verify
displacement of assembled components.

Marks, precisely punched upon the

attach-angle s u r f a c e of the subassemblies during fabrication, f o r m the
component position axis.
Optical tooling establishes a network of invisible lines of sight which c a n be
arranged, r e a r r a n g e d , and adjusted i n a variety of sequences a s p r i m a r y and
secondary lines of sight.

Using these lines, inspectors can adjust and prove

dimensional relations, angularity, squareness symmetry, and perpendicularity
of l a r g e assemblies that r e q u i r e accurate alignment.
F i g u r e 2 i l l u s t r a t e s the floor r e f e r ence t a r g e t s which f o r m the b a s i c
datum points for the position axis.
A jig t r a n s i t i s adjusted to e s t a b l i s h
a line on the floor r e f e r e n c e target.
The assembly jig can be rotated to
OUWUL 1AllKn
m PHI

sn

room

.

c r w LT

a m -

RwHtiQararl

coincide with the line of sight of the
jig transit.

mn
,.)14110

allow the position points of the jig to

.

The jig t r a n s i t i s a r c e d

to observe attach-angle punch mark.
Adjusting the optical m i c r o m e t e r
attached to the t r a n s i t objective l e n s
r n ~ w u u u i r l a m

nacla r r r w r n m

p e r m i t s displacement observations
to be measured and recordec'
T r u e Centerline Location- -Analysis

Figure 3. Verifying Displacement of
Assembled.Components

of recorded displacement data
provides' the nieans f o r determining

�location of t r u e centerline and
implication of m e a s u r e m e n t e r r o r .
Relationship of Enqine Geometry to
Vehicle- - A single-engine configuration i s shown i n F i g u r e 4.

Relation-

ship of engine to vehicle i s verified
with a special alignment fixture
positioned on the engine exit plane
and indexed in tooling holes located
in the engine exit flange.

Two

clinometers positioned on the
machined surface block in the
c e n t e r of the fixture a r e adjusted to
p e r m i t center-level bubbles to r e a d
tUT RUf MLIMlUWLt M J U l l t O
tUT R u t UUmAIIO ffiLE

- W i l T E i r t x t l R u t IClIUl10. ffiU

- r o r ~ ~ r c t r ~ c v iia-1
ua

6

to the n e a r e s t 1/10 min.
E

S W I N ~ 111- mim I

Figure 4. Single-Engine Configuration

Clinometer

angles and directions f o r position
planes a r e recorded.

The "adjusted"

exit plane inclination angle i s computed to the vehicle horizontal datum
plane.

Data recorded m u s t be

accurately established i n o r d e r to
be useful and meaningful.
F i g u r e 5 i l l u s t r a t e s a vehicle with a
6-engine cluster.

Manufacturing

techniques implemented to i n s t a l l
the engines made i t n e c e s s a r y to
verify engine alignment by horizont a l methods.

Figure 5. Vehicle with Six-Engine Cluster

�FUTURE ALIGNMENT PROBLEMS
F u t u r e aerospace business will involve building, testing, firing, recovering,
and refurbishing large payload boosters.

Large crews on manned space

vehicles and longer missions can be expected.

Vehicle dimensional tolerances

and s u r f a c e smoothness requirements probably will not exceed c u r r e n t tolerances.

Other tolerances may be more critical because of the need f o r high-

performance structures, space limitations, and operating-temperature range.
Size alone often will c r e a t e problems.

New materials and requirements for

e x t r e m e reliability will necessitate development of highly refined manufacturing techniques and new skills.
Continued development of inspection c r i t e r i a and quality control methods i s
n e c e s s a r y to keep pace with advancements of the space age.

�REFERENCES

1.

A. J. Munson.

Welding Huge Components of Saturn Space Vehicles-Manufacturing Steps in P r e p a r a t i o n f o r the Shot to the Moon. Machinery,
Vol. 70, No. 2, October 1963.

2.

A. W.- Dryden. Stage Alignment P r o c e d u r e s Saturn S-IVB Stage.
Douglas R e p o r t No. SM-46843, April 1965.

3,

J. Madsen. Manufacturing Control f o r Advanced Vehicles.
P a p e r No. 1647, 24 September 1963.

4.

John D. McGrae. Optical Tooling in Industry.
C h r y s l e r Corporation, 1964,

Douglas

M i s s i l e Division,

�</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="22753">
                <text>spc_stnv_000119</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22754">
                <text>"Assurance and Measurement of Space Vehicle Alignment."</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="22755">
                <text>Douglas Paper No. 4054</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22756">
                <text>Prepared by A. W.  Dryden, Quality Engineer, Quality Engineering, Reliability Assurance, Space Systems Center, Douglas Aircraft Company, Inc., Huntington Beach, California. Presented to the 21st Annual Technical Conference for the American Society for Quality Control, Chicago, Illinois. 30 May to 2 June 1967.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22757">
                <text>Dryden, A. W.</text>
              </elementText>
              <elementText elementTextId="22758">
                <text>Douglas Aircraft Company. Missile and Space Systems Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22759">
                <text>1967-06-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="22760">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22761">
                <text>Alignment</text>
              </elementText>
              <elementText elementTextId="22762">
                <text>Contracts</text>
              </elementText>
              <elementText elementTextId="22763">
                <text>Government contractors--United States</text>
              </elementText>
              <elementText elementTextId="22764">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="22765">
                <text>Saturn Project (U.S.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22766">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="22767">
                <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="22768">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="22769">
                <text>Box 23, Folder 2</text>
              </elementText>
              <elementText elementTextId="205925">
                <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="22771">
                <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="22772">
                <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="22773">
                <text>spc_stnv_000119_000149</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="22774">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17692</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10875" public="1" featured="0">
    <fileContainer>
      <file fileId="9400">
        <src>https://digitalprojects.uah.edu/files/original/20/10875/Letttothepres101268_120808163249.pdf</src>
        <authentication>de900e2e728448b2f941b8c27350edde</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="165341">
                <text>Letttothepres101268_120808163249.pdf</text>
              </elementText>
              <elementText elementTextId="165342">
                <text>spc_stnv_000401</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165343">
                <text>"Letter to The President and White House."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165344">
                <text>Correspondance between the President and Hugh L. Dryden regarding administrative limitations of the President's power.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165345">
                <text>Dryden, Hugh 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="165346">
                <text>1962-10-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="165347">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165348">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="165349">
                <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="165350">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="165351">
                <text>Correspondances</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="165352">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210567">
                <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="165354">
                <text>Is part of: Dr. von Braun / NASA HQ Correspondence July 1968.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165355">
                <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="165356">
                <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="165357">
                <text>spc_stnv_000400_000424</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10945" public="1" featured="0">
    <fileContainer>
      <file fileId="9428">
        <src>https://digitalprojects.uah.edu/files/original/20/10945/lettdrhughodigfromhughdryd_031607081156.pdf</src>
        <authentication>1a1d4d6b0e40a4891ad8de6bb56ddcdc</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="166697">
                <text>lettdrhughodigfromhughdryd_031607081156.pdf</text>
              </elementText>
              <elementText elementTextId="166698">
                <text>spc_stnv_000373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166699">
                <text>Letter to Dr. Hugh Odishaw.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166700">
                <text>Letter to Hugh Odishaw from Donald Hornig regarding a previous meeting as well as an F-1 engine report.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166701">
                <text>Dryden, Hugh 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="166702">
                <text>1961-03-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="166703">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166704">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="166705">
                <text>F-1 Engine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166706">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="166707">
                <text>Correspondence</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="166708">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="166709">
                <text>Box 5, Folder 21</text>
              </elementText>
              <elementText elementTextId="210637">
                <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="166711">
                <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="166712">
                <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="166713">
                <text>spc_stnv_000350_000374</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="166714">
                <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16650"&gt;View this item on ArchivesSpace.&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7714" public="1" featured="0">
    <fileContainer>
      <file fileId="6674">
        <src>https://digitalprojects.uah.edu/files/original/119/7714/r02g07-36.pdf</src>
        <authentication>eca20bda04c28923b58fbc7911c1bed3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="119">
      <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="130919">
                  <text>Series 02, Subseries G: Roberts Correspondence</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="130920">
                  <text>Series 02, Subseries G: Roberts Correspondence</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="131638">
                <text>r02g07-36</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="131639">
                <text>Frances Cabaniss Roberts Collection</text>
              </elementText>
              <elementText elementTextId="183248">
                <text>Series 2, Subseries G, Box 7, Folder 36</text>
              </elementText>
              <elementText elementTextId="209304">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="131640">
                <text>Query Letter Concerning 1863 Pikeville Refugees, undated</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="131641">
                <text>r02g-210915</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="183240">
                <text>Dugan, Frank H.</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="183241">
                <text>12-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="183242">
                <text>Alabama–History</text>
              </elementText>
              <elementText elementTextId="183243">
                <text>Alabama–History–Civil War, 1861-1865</text>
              </elementText>
              <elementText elementTextId="183244">
                <text>Associations, institutions, etc.</text>
              </elementText>
              <elementText elementTextId="183245">
                <text>History–Sources</text>
              </elementText>
              <elementText elementTextId="183246">
                <text>United States–History–Civil War, 1861-1865</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="183247">
                <text>Correspondence</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="183250">
                <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="183251">
                <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>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1140" public="1" featured="0">
    <fileContainer>
      <file fileId="987">
        <src>https://digitalprojects.uah.edu/files/original/20/1140/spc_stnv_000056.pdf</src>
        <authentication>3c1d866c81cec99dbfe2a16cc984fec6</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177274">
                    <text>. .
t..:
..:,;.:.
\ ......

L . ,

1

{

.; :
,'.
LA....- ;'.';,I

e&gt;,.&lt;

-

i

&lt;..
,... : . .

&lt;.

.

.&lt;.;,

-&gt;

5

d
A
,
.

-.

;j&amp;..$?,;:,;;,;; ,:.'
........... ..,...

y:\. :;::'.

&amp;. . ,: ':..... "...J:,--.. . P
;.. .-.&lt;.
. . . :,. . " ,.,' . .'-&gt;,

-2

i

*&gt;-&gt;,..,

\.&lt;:.'..:.,

SI:,.

,&gt;

.

ri 4

;!
&gt;

'

'

'

,i'

.\,

,

.....

::
. .

-:,.

:

,
..... . !

.

"".

.

'

L.:;.
, :

'~

-

.'

&lt;t:$;3d; , ;,:::&gt;.

&gt;,

.r.&lt;&lt;;:;;::-..:::

.

.

.

......

,*,.-

:.;
.

:

%

&lt; ?

2

,r.'
...

'.-'
,../

.;,

! . , .

.$. ..

.',..&gt;

'

-:. . . .

&lt;

-+,--.

,:.L- ........ ;:.. . . . . . . . . . . ,. . .
. . . . - .
. .
,-; .... .: ,,... :,: ; . .:...:.... ..:.

-,-a
..:.;. .; :,;.
,.,.
.......

---

-.?4--,-:'

. .

,; ....... .,...* ........ ."..
...... ; ....
:..,&gt;,.
. . . . . . . .. . .. ....., .
' . . . .; . :,4-,*
*,:. :v."*.-v ; 2 - . C I - "
,- . , . . \
&gt;
-. - . -.
4........... ?
c.
-.-.'O*-:
h.&lt;; :;...; . :..... -%
. . ,:?T
,&gt;; 7sL2,:~.yi"
.-..\.&gt;
*,.-;.
-,&amp;&gt;
*2*..'...'
'

&gt;. . ,

.

CONTROL CONFERENCE

.

-,'

..;

/
.
/c.:.::
"if
. ..;.*r.

-...

. ':&lt;.-.,. .:. . .,..

........

.

.,,

.

. .A.

,
.
_
SF-,- . . . . . . .. . z 9 9

. .

-

.....

.

:

..,

,

.;,

:

12-14, 19631 MASSACHUSEl-iS 6NSTlTUTE OF TECHNOLOGY:

.'._. .

,

1
I,/,

. .
-;.?;~~,;~;,;.~;q~;;i;~;,j
?.~,
+
'&lt;

-.
.

,

-

k:-,-:.;:. :;:,: ;,..:::,;:?, \ ::,;.?*:,

.
,
,
.
,
%
.
.
&amp;
-

C,~MBIIIDGE, h4kSS?iCKL!SE-iTS
'

by

0. T. DUGGAN
Fiars2.,.ahl Spaco F l i g h t Center

National 2.esonautics and Space Aclrdn-is lration
Huntstaillo,
i2.2.
.-

No. 6 3 - 3 9

.

L - .

\. *::'.: ,! ,\ v:;..;:
*::. . ' , ,., :,;
'li: ..:.... ;. .... -:M
c . ,.&gt; ....... %
.
;
.
$
,
.
&lt;:..
&lt; . .;.&amp;i&gt;:.
b;.:;: :: .: :......... .-h
%.::.;. ....
...:. :..% '.- ......". .."
:

pUGUST

.

."-..*

U..,.

. ;::,*'Yh

AlAA GUIDAXCE AND

,

:.

".; . .'I, $ . . '2.
\-~~'.. ,-:,j
,
r,:-,,..;
.., v
L . .i:
-A .L, 1

,

c.:.,;.:':........ -3.&gt;,&gt;..*,

. . . t

.\. ;.;

.&lt;-.

'..

s:3,
v..\
....
*. , .&gt;

",

F '

.

-.:

?

R,,
L. 5:

-

:..:...,, ...
. . . . .
., . . . .
. . . . -....
. .,, .. .,'.. ..%
'
. .
,.
.
, ., .. . &lt; . . . . ,-: .. . .,
. .
.......... . . . . . . . . .
k.. . . ,. . . . ;.. . . . . . . . . . . . .
.
c....
........................
.-;.:.'.:-\!::
, . ,. , , : . '. , , .,,
..
. . . . .
.
,
. ,,
. . . . .- -. . . . .

G.h
:.. . ,
*J
,

E

I

, . .

&lt;.,A

,'.:.

.'.
"
.
. C.. . -. .;. . 1
;,

,

,....

:':.:

..\,
,.&gt;
.........:\\
*i.
. i*
,;. ... ':.;;. ' "1

.
..-.--j.

...I

'

,
,

,,,

,

6.

...
" . ... .. .. . .----------.
....
,+ 7..- . ..
6:.

..........*.

,&amp;;.
.

,

:-/"

,
L

..$

.

_.

.. . . . . .

/&lt;/

,-..

. . .

:..

.\

, '

... .J .? : ,,; ::d:----L-.;".:,.
&gt;./
;
,,' .
,L" ::
'j

. . &lt;, .:

~&lt;G
-,.',;

. . * ..-...:.......
. .&gt;.......:.....";;&gt;22-4'
;.
'..,...I.

-

/-

&lt;--:.=

C

.

. .- 7 7 i""
.-----. . ----.
. ..,

/ . .

- ' i .

-

��.,-- ;;;;p!iPier
,

is 109 db maximum and i s controlled

by an AGC voltage from the range tracker.
MODULATOR

-

POWER SUPPLY ASSEMBLY

The modulator-power supply i s b u i l t as one
assenbly. The roduiator i s an a l l s o l i d s t a t e device that receives a 144 pps sync pulse from the
timer and produces a
pps, I:&amp;s,
3500-volt
nodulator pulse iot- the transmitter. The modulator
c i r c u i t consists of a d.c, resonant charging network and an opsn-cndcd, pulse forming network t o
generate the oodu l a t o r pulses.
The power supply is a dace-to-d.c. converter
with a 26 V d o c . input t h a t supplies s i x regulated
v o i t c g e i ?in4 O n d ~ ~ f i r a g ~ l e tVvitags
ad
f o r t h e f ivo
assemb 1 ies of the a1 timeter.

tracker is to track the delayed video I-eturi? s i c j nal and produce a g s t e whose width i s a iuncticn
of the d i s t a n c e t o the eartii, It s l z c Senerates
AGC signals' t o control the Cjdiri of the I F amp!;fTers and a r e l i a b i l i t y signal w h i c h i n d i c s ~ e s
t h a t the t r a c k e r is lflocked-on" the return s igrzl
and t h a t the a l t i t u d e d a t a being tran;:a;ttcci i s
re! iabie.
~
The t r a c k e r can search f o r , " I c c k - ~ n,~and
t r a c k returned signal w i t h power levais as i c w a:,
-Ci dbm, and w i t h range r n t c s u p t o 6 ;.m/s. 7:-tc
t r s c k e r has two rrodes of operation:
rke l g t r a c % i !
mode and the t l s e a r c h t rmcde.

Figure 3 i s a simplIfIed biock diagram of the
t r a c k e r i n the H t r a c k s lmode of operaiion.

TIMER ASSEMBLY
The timer c o n s i s t s of the timer sub-assembly
and a 21.233664 MHz clock o s c i l l a t o r . The o s c i l l a t o r supplies the time base f o r a l l functions of
the timer (Figure 2 ) .
The clock frequency i s divided t o produce the

144 pps sync pulse and i s f u r t h e r divided t o produce the 36 pps t r a n s f e r signal t h a t c l e a r s and
resets the storage r e g i s t e r and accumulator.
The 36 pps signal i s divided by 18 t o provide
the 2 pps time s i g n a l . This time signal i s the i n put t o a 9 - b i t counter t h a t provides a binary coded
elapsed time output.
The a l t i t u d e data is generated by gating the 21
MHz clock signal i n t o an 18-bit accumulator. The
&lt; z i n g signal i s the counter g a t e from the range
.acker. I t s width is proportional t o a l t i t u d e .
The counter gate occurs 144 times per second (four
times the r a t e of the t r a n s f e r puls?), which means
t h a t the IS-bit a l t i t u d e word i s the count a c ~
cumu lated during four counter g a t e i n t e r v a l s . This
provides an a i t i t u d e readout t h a t i s the average of
k a l t i t u d e measurements made over a 1/36 of a second
i n t e r v a l . This method a l s o slows the data r a t e t o
a r a r e reasonable va Iue.
The 18-bi t storage r e g i s t e r receives and s t o r e s
the 13-bi t a1 t i tude word f rom the accumulator. The
storage r e g i s t e r i s cleared and r e s e t 36 times per
second, j u s t prior t o r e s e t of the accumulator.
Data i s avai lable f o r telemetering f o r approximately
23 ns out of every 28 ms. Clear and r e s e t functions
a r e performed during the remaining 5 ms.
The stored 18-bit a l t i t u d e word i s read by the
te!emeter;ng equipment a t a r a t e not synchronous
w i t h che t r a n s f e r pulse r a t e , which r e s u l t s in
periodic readings t h a t occur while the 18-bit s t o r age r e s i s t e r i s i n the process of being cleared and
r e s e t (new data s h i f t e d i n fron the accumulator).
i n order tnat these erroneous readings w i l l not be
nisin:er?reted, an " i n h i b i t " signal i s generated
5 LLi:een
-- torag age c l e a r t 1 and "storage resetu ( t h e 5
ns pc;;od previously mentioned). This i n h i b i t s i g nal is used as a "flaga1 on t h e telernetered data t o
denote unrel iable data.
pP

1

.L,+

Rb,NGE TRACKER ASSE3BLY

The primary function of the a l t i m e t e r range

The negative s t a r t pulse from t h e t r a n s m i t t e r
s t a r t s the counter g a t e f 1 ip-f lop and the l inear
sweep generator. The l inear swaep generator gener a t e s a i i n e a r ramp function t h a t r i s e s to approximately l G O voi t s i n 3 6 0 0 4 s, The pick-off dioce
a t the output of the 1 inear sweep generator a 1 lows
some portion of t h e l i n e a r sweep t o psss t o tne
range g a t e generator c i r c u i t . The portion t h a t i s
passed depends upon the magnitude of t h e d.c. voltage fed f r o n the servo amp1 if i e r t o the p;ck-oii
diode. The portion of the l i n e a r swee? t h a t passes
~ h r o u g hthe pick-oci d i ~ d eis t h a t whicn occuis
a f t e r the sweep volrage has reached t h e n a g n i t u l s
of the d . ~ . voltage from t h e servo. Since the
amplitude of the l i n e a r sweep i s a Functir: of t i a e ,
the magnitude of t h e d.c. voltage fro,? the servo
determines a t what time along ehe i inear swccp the
pick-off diode w i l i begin t o pass the sweep,
The portion of the sweep'that i s passed t h r o u ~ h
the pick-off diode i s amplified, shaped, and
d i f f e r e n t i a t e d t o form a sharp pulse a t the i n s t a n t
the sweep i s picked o f f . This pulse i s used t o
range g a t e and t o generate the
generate the 2-/$s'
s t o p pulse which terminates the counter g a t e ,

-ine
,

counter g a t e i s fed t o the e r r o r sensor

where i t concrols a high speed video switch. The
I?
gated video pulse i s a l s o fed t o t h i s switcn.
the end of t h e counter g a t e does not coincide with
the c e n t e r of the returned video pulse, an e r r o r
signal causes t h e servo output voltage t o cnange i n
the di rection necessary t o return tne end 05 the
counter g s t e t o the c e n t e r of t h e video pulse.
As the a l t i t u d e changes, t h e e r r o r sensor and
servo c i r c u i t s mair,t : n ;he range g a t e a d t h e efid
of the counter g a t e coincident with the recurned
video pulse. As long as coincidence i s n a i n t a i z e d ,
range loss relay K-101 i s energized and t h e t r a c k e r
I n t e g r a t o r s i n the
operates i n t h e I'track" mode.
servo c i r c u i t s t o r e range r a t e information, whicn
a1 lows the t r a c k e r t o continue tracking a t tne
same r a t e during s h o r r duration s i g n a l fades,

i l I u s t r a t e s typical wavsshapes of 'the
Figure
tracking c i r c u i t s i n t h e "tracki1 mode of operation.
AGC C i r c u i t s (Fisure

5)

The range t r a c k e r produces t h r e e AGC s i g n a l
voltages: fixed AGC, noise A C C , and pdise AGC.
These t h r e e voltages a r e fed t o an "OR" g a t e ,
which a l lows only the most negative voi t a s e t o pzss.

~~-&amp;,?&gt;;hz

�Noise AGC i s used during the I1searcht8mode.
It i s generated by the IF noise and i s adjusted
fdr optimum searching action.

the storage c i r c u i t t o maintain "icck."

Pulse AGC i s used i n the
mode of
opera tion and i s generated f ron the 2 - 4 s rangegated video pulse alone.

The a ] timetei- aatenns was rjes l ~ c e de n d b u i l ';
by the Antenna Developiiient Ijnl t ot ;',SF::.
I t i8 a
planar 3 by 4 s l o t a r r a y . The s l o t 5 a:e ctched on
one s i d e of a l/b-inch t h i c k , coppcr-lsrninsted
rexoli t e sheet. The o t h e r s i d e of t h i s shze'c h z s
an etched feed l i n e which divides the poSwer cqvsi iy
a n d i n phase among the s l o t s . To bloc!: one 5 i d e of
the s l o t s , another l/8-inch ::hick, copper- 1c:~iI:;~iteJ
r e x o l i t e s h e e t i s used, duplicating the povtcr
divider on one s i d e where the lamination on tha
other side i s l e f t intact.

Fixcd AGC i s used during the t r a n s i t i o n from
"scarchI1 to lltrackll mode of operation to prevent
thc I F amplifier from s a t u r a t i n g ,
Video Gatinq (Fiqure

5)

The returned video pulse i s gated a t several
poinks i n the range tracker t~ gate out noise and
other unwsnted s l g n a l s wh! la allawing kka v f J e 6
return signal t o pass. The width of the gates
depends upon whether the tracker i s i n the search
mode o r track mode.
The f i r s t gating c i r c u i t (Al) encountered by
the returned video i s relay controlled. I n t h e
search mode, the g a t e width i s approximately
35004s long. The f i r s t 100As following the
transmitter pulse i s gated out by an i n h i b i t pulse
f torn the blanking g a t e generator and the l a s t 3300
,L(s of the time interval between transmitted pulses
is gated out by a blanking gate from the sweep g a t e
generator. This gate s e t s t h e maximum and minimum
tracking 1 i m i t s of the range t r a c k e r as required by
the mission of t h e a l t i m e t e r and prevents processing
of unnecessary noise.

I n the track mode, gating c i r c u i t A1 i s cont r o l led by the 2-14s range gate. This al lows only
the 1-,d/s video return and I - A s of noise t o pass t o
the o t h e r c i r c u i t s of the tracker.
The second g a t e (A2) gates the video i n t o the
pulse AGC and r e l i a b i l i t y signal c i r c u i t s . i t i s
always controlled by the 2&amp;s range gate; theref o r e , very l i t t l e AGC voltage i s deveioped by t h i s
c i r c u i t u n t i 1 t h e return video pulse and range g a t e
are coincident.
Gated storage c i rcui t A4 gates and s t o r e s t h e
video pulse energy during each range g a t e i n t e r v a l .
Th i s stored vo i tage produces the pulse AGC voltage ,.
and the "re1 iabi 1 ity" signal which causes the range
tracker t o swi tch from 18search1rt o ll.trackltmode of
operation.

ANT Eb!!IF\

One anfeqna i s used f o r both %fentimitt;n: ?nd
recei V I ng. This antenna conP i guration oroduccs a
pattern normal t o i t s a p e r t u r e having 16 db cjain a;
the c e n t e r of the lobe. The level of s i d a lobes
i a r e l a t i v e l y low, but high enough t o a s s u r e
aaequate signal s t r e n g t h u r i n g ' t h e e a r l y portion
of t h e f l i g h t t r a j e c t o r y .

9

PROBLEM AREAS
The two major problems encountered i n t h e
design of t h e Saturn radar a1 timeter stern f r o n
the lack of knowledge of radar returns f roa a l t i tudes beyond the c a p a b i l i t y of a i r c r a f t . Existing
theory as t o the r e f l e c t i v i t y f i g u r e of sea-water
v a r i e s over a wide range, even a t t h e r e l a t i v e i y
low a l t i t u d e s f o r which data e x i s t s . Transmit:zr
power requi reinent f o r the a 1 tlmeter was based ci?
a conservative r e f l e c t i v i t y f i.gure, and what ccltild
be realized within e x i s t i n g weight and space l i r i i i tations.
Accuracy of the system depends heavily c n the
shape of the return echo. Existing theory s t a t e s
t h a t above the c r i t i c a l a l t i t u d e of the s y s t e a , the
return pulse r i s e time becomes equal t o the tracsmitted pulse width. Attempts were made t o verify
t h i s theory, but f l i g h t t e s t s t o a l t i t u d e s of 22 k~
revealed very l i t t l e increase i n retiirn pulse r : s e
time.2 For lack of experimental data a t a i t i t z d e s
of 50 km t o 430 k ~ t,h e tracking system design was
based on the assumption t h a t e x i s t i n g theory as t o -.
return pulse shape i s c o r r e c t . An e r r o r i n t h i s
..'.
assumption w i l l r e s u l t in a b i a s e r r o r i n t h e a i t i tude data.
EXPERIMENTAL F L i GHT

Gate A3 allows a l l of t h e video and noise
from gate A 1 t o pass t o the noise AGC c i r c u i t ,
except the video t h a t occurs during the range
gate interval. I n the search mode, approximately
350yds of noise and video e n t e r s the noise AGC
c i r c u i t t o provide AGC voltage. I n the t r a c k mode,
however, the only video and noise reaching g a t e A3
i s t h a t which occurs during the 2 M s range g a t e
i n t e r v a l . The i n h i b i t pulse from the range g a t e
generator prevents t h i s from passing through A3;
consequently, p r a c t i c a l l y no noise AGC v o 1 t a g e . i ~
developed.
Gsted storage c i r c u i t A 5 gates and s t o r e s the
e r r o r signal used by the servo loop. During t h e
search node, the 3 5 0 w s of noise plus video i s
used as the gating signal t o determine t h e direction i n which the servo i s driven t o acquire the
returned signal. During t h e t r a c k mode, t h e 2-y$-'
s range gate i s used t o g a t e the e r r o r signal i n t o

The radar a l t i m e t e r was flown as an experimental passenger aboard Saturn vehicle SA-4 on
March 28, 1963. The t r a j e c t u r y o f t h i s vehicle
was not ideal f o r a l t i m e t e r operation because of
the t i l t angle of rhe vehicle over the p o r t i o ~of
L
LL
IZ
t r a j e c t o r y of i n t e r e s t . The antenna main lobe
was centered 90' from t h e main a x i s of the vehicle
f o r optimum- s i gnal return during hor i zonta 1 il ign t
( f o r which the a l t i m e t e r was designed), with minor
lobes centered 45' from the main lobe (Figure 6 )
Tne a l t i m e t e r lllocked-onll t h e return pblse when :hz
vehicle was s t i l l a t a t i l t angle of 47' from t h s
horizonta 1 . lrLock-onll occurred a t approximate :y
105 seconds a f t e r l i f t - o f f and was maintained until
approximately 125 seconds a f t e r lifi-sf:,
a t whicn
time the retro-rockets were f i r e d and :he v e h i c l e
began to r o l l . The a l t i m e t e r tracked From approximately 40 km t o 62 lun above the E a r t h ' s s u r f a c e .
Telemetered t e s t data indicates t h a t t h e a l t i n e ~ e r
operated properly throughout the f 1 i g h t .

.

~CQCU-3

,

- *

,*.-

--

�f i g ~ r e7 shows the f l u c t u a t i o n s i n t h e a l t i tude d a t a . The g e n e r a l t r e n d i n t h i s f i g u r e has no
signia;icancc and i s o n l y t h e r e s u l t o f some d i f f e r encing c a l c u l a t i o n s which were done t o emphasize
the h i s h e r frequency o s c i i i a t i o n s . T h i s f i g u r e
shows:
t h a t the data contains noise bursts t h a t
o c c u r about every second; t h a t an a l t i t u d e s h i f t o f
about 30 n o c c u r r e d a t o u t b o a r d engine c u t o f f (oECO) ;
dnd t n a c t h e rehdam o r r e f i p 06bbt *$Q rn, wXie1-i i s
w i t h i n t h e a1 t i m e t e r s p e c i f i c a t i o n s . Tne cause o f
:he n o i s e b u r s t s and t h e a l t i t u d e s h i f t a t OECO has
n o t y e t 5een c o m p l e ~ e l ydetermined.
The o u t p u t d a t a f r o m t h e a l t i m e t e r i s compared
w i t h t h e a c t u a l t r a j e c t o r y i n F i g u r e 8. The c a b l e
a s s o c i a t e d w i t h t h e a l t i m e t e r and t h e d i s t a n c e between t h e v e h i c l e c e n t e r o f g r a v i t y and t h e a l t i m e t e r
antenna c o n t r i b u t e about +I5 m t o 2 0 m b i a s i n t h e
d i f f e r e n c e s shown. The o s c i l l a t i o n s about t h e mean
a r e caused by t h e n o i s e i n t h e a l t i m e t e r o u t p u t .
T h e d e v i a t i o n s (a1 t i m e t e r minus a c t u a l t r a j e c t o r y )
v a r y f r o i i l +bO,m t o -20 m.

The AGC v o l t a g e du;lng
t h e lock-on ? - r i n d i n d i c a t e s t h a t t h e r e c e i v e d s i g n a l 5;i*ei,gth v z r i z d
bcewcen -60 dbm and -80 dbn,

-

i he n e x t e x p e r i m e n t a l f l i g h t F I 1 1 o f f e r a Gore
f a v o r a b l e t r a j e c t o r y and wl i l a i l o w t e s t i n g o f :ha
a i t i m e t e r performance t o an a l t i t d d e i n excess c ?
200 h.

1.

S a t u r n Antenna Systems, SA-4 ( ' J o l ~ m e 2) ,
G. 6 . M a r s h a l l Space F i i g h t C c q t e r , A s t r i o n i c s
D i v i s i o n , I n s t r u m e n t a t i o n Eranch, R? S y s t c n s
S e c t i o n , Antenna U n i s , December ! G , 1962

2.

A Study 0
: The Radar R e f l e c t i v i t y O f Sea Water
A t V e r t i c a l I n c i d e n c e , by Radar A l t i r c e t r y
Research L a b o r a t o r y , H.M. Summsr, Techn;ca?
Di r e c t o r , Auburn Research F o u n d a t i o n , Auburn,
Alabama, d a t e d dune 1, 19-52 ( F i r s t R e p o r t W ; t ~ &gt;
Data Supplemaat) and March 1, 1563 (Second
~eport)

.

MODULATOR

LOCAL

14-

MIXER

idA " * , ~1-4~ : ~ ~ ~
a

I

RALGE TRACKER

!----I

I

-1

TIMLA

Eii

ALTITUDE

vi023

��WI:jE#t;&amp; RADlATfCf: S)k4HEC&gt;,:,?A332 A::TEiJEW
FIGURE 6

RCOUCED ALTIMETER

OUTPUT I U E I E R S L

RETRC lGYtTlUl

ALTITUDE DIFFERENCE (METERS)

OECO

(ALTIMETER MINUS ACTUAL TRAJECTORY)

I

RANGE TIME (SEC)

poYw?rrFIGURE 8.

ALTIMETER DATA COMPARED TO ACTUAL TRAJECTORY

6

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20009">
                <text>spc_stnv_000056</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20010">
                <text>"Saturn Radar Altimeter."</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="20011">
                <text>No. 63-352AIAA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20012">
                <text>Paper given at the AIAA Guidance and Control Conference, August 12-14, 1963, Massachusetts Institute of Technology, Cambridge, Massachusetts.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20013">
                <text>Duggan, O. T.</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="20014">
                <text>1968-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20015">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20016">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20017">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="20018">
                <text>Altimeters</text>
              </elementText>
              <elementText elementTextId="20019">
                <text>Radio altimeters</text>
              </elementText>
              <elementText elementTextId="20020">
                <text>Altitudes--Measurement</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20021">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20022">
                <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="20023">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20024">
                <text>Box 9, Folder 25</text>
              </elementText>
              <elementText elementTextId="205807">
                <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="20026">
                <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="20027">
                <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="20028">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1272" public="1" featured="0">
    <fileContainer>
      <file fileId="1119">
        <src>https://digitalprojects.uah.edu/files/original/20/1272/spc_stnv_000129.pdf</src>
        <authentication>a306bb731d0e758b829ce5bf73574869</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177320">
                    <text>V H E A S T R O D Y N A M I C I S T ' S R O L E V I S - A - V I S T H E SYSTEMS E N G I N E E R
bv
REYNOLDS DUNCAN, JR.
NASA Marshall Space Flight Center
Huntsville, Alabama

J.

Smm
U,-,iversitY

WB~?'?

~esaarch\'*itUte

;enc;@,

HistmY oF Sc

Date

----------

Doc.NO.

-------I
.

�Z)EE

AS$RODY&amp;MXCIST'S ROLE VIS-A-VIS THE SYSTgMS ENGINEER

J. Reynolds Duncan, Jr.
Aerospace Engineer
NASA-Marshall Space P l i g h t Center
W u n t s v i l l e , Alabmna

The prablem o f e f f e c t i v e two-way c o m u n i c a t i o n s
is t r e a t e d , w i t h emphasis p l a c e d upon t h e compilat i o n a d p r e s e n t a t i o n of astrodynamical d a m f o r
w e by t h e systems e n g i n e e r i n t h e p r e l i m i n a r y
p h a s e s o f m i s s i o n p l a n n i n g . Such d a t a s h o u l d b e
p r e s e n t e d i n a form which is e a s i l y understood and
v h i c h c a n n o t b e e a s i l y m i s i n t e r p r e t e d by p e r s o n s
w i t h l i t t l e o r no k n o w l e d g e o f a s t r ~ d y ~ r a i c s .
Wherever a s t r o d y n a m i c a l p a r a m e t e r s may b p o s e
c o n s t r a i n t s upon a m i s s i o n , a c l e a r i n d i c a t i o n
s h o u l d be g i v e n o f t h e p o s s i b l e consequences f o r
v i o l a t i o n o f t h e s e c o n s t r a i n t s . When a l t e r n a t i v e s
a r e a v a i l a b l e , they should be indicated, along
w i t h any p e n a l t i e s a s s o c i a t e d w i t h t h e i r u s e . The
r e s u l t of t h e astrodynamicist's e f f o r t should be a
well-informed systems e n g i n e e r who h a s t h e o v e r a l l
p i c t u r e of t h e e f f e c t s o f astrodynamical parameters
upon a m i s s i o n and t h u s w i l l be a b l e t o perform
meaningful t r a d e o f f s t u d i e s w i t h r e g a r d s t o system
d e s i g n a &amp; performance.

I. l n t r o d u c t i o n
The r o l e a n a s t r o d y n a m i c i s t may p l a y i n a
m i s s i o n des.ign s t u d y c a n b e d i v i d e d i n t o two p a r t s :
t h a t o f s u p p l y i n g background o r p r e p l a n n i n g i n f o r mation and t h a t o f p r o v i d i n g additions:, u s u a l l y
more d e t a i l e d , i n f o r m a t i o n f o r u s e d u r i n g t h e s y s tem and subsystem d e s i g n phase. The t y p e and
amount of d a t a s u p p l i e d t o the systems a n a l y s t
d u r i n g t h e l a t t e r p h a s e depends t o a l a r g e e x t e n t
upon t h e completeness and u s e f u l n e s s o f t h e background i n f o r m a t i o n s u p p l i e d t o him e a r l i e r . The
t y p e and method o f p r e s e n t a t i o n of t h i s background
i n f o r m a t i o n i s t h e major t o p i c o f d i s c u s s i o n i n
t h i s paper.
Background i n f o r m a t i o n , a s used h e r e , r e f e r s t o
a s t r o d y n a m i c a l d a t a o f a g e n e r a l n a t u r e which may
c o n t r o l o r i n f l u e n c e t h e d e s i g n o f systems a n d / o r
subsystears. The g e n e r a l f t y o f t h e d a t a i m p l i e s
t h a t t h e d a t a may b e used f o r m i s s i o n p l a n n i n g
p u r p o s e s on a v a r i e t y o f m i s s i o n s . Of c o u r s e , a l l
p o s s i b l e missions? c a n n o t b e covered, b u t by res t r i c t i n g t h e launch, p l a n e t t o b e t h e e a r t h and
s p e c i f y i n g a s i n g l e t a r g e t p l a n e t , a manageable
gr0.q o f c h a r t s and g r a p h s c o u l d b e g e n e r a t e d
c o v e r i n g s u c h p o s s i b i l i t i e s a s d i r e c t and brokenp l a n e t r a n s f e r s f o r a l l r e a l i s t i c launch e n e r g i e s ,
and a r r i v a l c o n f i g u r a t i o n s v a r y i n g from f l y b y t o
low o r b i t a l r e c o n n a i s s a n c e m i s s i o n s . The d a t a
p r e s e n t e d s h o u l d i n d i c a t e t h e e f f e c t o r impact o f
i m p o r t a n t p a r a m e t e r s upon t h e o v e r a l l c l a s s o f
possible missions.
The p r e s e n t a t i o n o f t h e d a t a s h o u l d b&amp; a c m p l i s h e d i n s u c h a way a s t o i n d i c a t e p o s s i b l e
r a n g e s o f v a l u e s o f t h e parablerere. T h i s i s p r e f e r a b l e t o p r e s e n t i n g sample t r a j e c t o r i e s whieh
g i v e only s p e c i f i c values of t h e parameters f o r
Whenever
t h e v a r i ous s e l e c t e d t r a jsc t o r i e s
p o s s i b l e , p a r a m e t e r s which a r e f a m i l i a r t o t h e
u s e r s h o u l d be used and when t h e r e i s any p o s s i b i l i t y o f m i s i n t e r p r e t a t i o n o f t h e meaning o f t h e

.

p a r a m e t e r s , a f u l l e x p l a n a t i o n of t h e i r meaning
should accompany t h e c h a r t s o r g r a p h s . Also, t h e
v a l a e s o f any c o n s t a n t s used i n the g e n e r a t i o n o f
t h e d a t a should b e g i v e n , a l o n g w i t h a n y assumptions
which were made which might a f f e c t t h e a c c u r a c y o f
t h e d a t a . These may seem t o b e s m a l l p o i n t s , b u t
t h e omission o f such items a s t h e s e may c a u s e
problems i n t h e p r o p e r u s e and i n t e r p r e t a t i o n o f t h e
d a t a . One o f t h e primary c a u s e s of t h e s e omissions
i s the f a m i l i a r i t y of the astrodynamicist with the
m a t e r i a l h e i s p r e s e n t i n g . Although t h i n g s may b e
taken f o r g r a n t e d i n a d i a l o g u e between s p e c i a l i s t s
i n t h e same d i s c i p l i n e , making t h e same assumptions
when p r e s e n t i n g d a t a t o p e r s o n s i n a n o t h e r f i e l d
u s u a l l y r e s u l t s i n a c o m u n i c a t i o n problem. Thus,
t h e o b j e c t i v e of t h e a s t r o d y n a m i c i s t s h o u l d b e t o
p r e s e n t t o t h e systems e n g i n e e r d a t a which is e a s y
t o understand, e a s y t o u s e , and which c a n b e
r e g e n e r a t e d w i t h o u t a d d i t i o n a l informa t i o n .
To i l l u s t r a t e t h e s e p o i n t s , some g r a p h s w i l l b e
p r e s e n t e d which would be used i n a m i s s i o n a n a l y s i s
s t u d y o f a n unmanned m i s s i o n t o Mars d u r i n g t h e
1973-74 launch o p p o r t u n i t y . D i s c u s s i o n o f t h e g r a p h s
w i l l c e n t e r around t h e t y p e o f i n f o r m a t i o n which
should accompany each graph i n o r d e r t o make t h e
comunication of t h e information a s e f f e c t i v e a s
p o s s i b l e . Space does n o t p e r m i t t h e d i s p l a y o f a
more complete s e t ' o f c h a r t s and graphs which might
b e used i n such a s t u d y .
If.

Supplemental I n f o r m a t i o n

A graph such a s t h e one shown i n F i g u r e 1 would
b e one of t h e f i r s t graphs c o n s u l t e d i n a m i s s i o n
a n a l v s i s s t u d y . F i g u r e 1 shows t h e o v e r a l l launch
o p p o r t t i n i t y a s d e f i n e d by t h e launch energy, G.
From t h i s c h a r t , t h e maximum ranges o f t h e launch
d a t e , a r r i v a l d a t e , and time o f f l i g h t c a n b e
o b t a i n e d . accompany in^ t h i s graph s h o u l d be i n f o r mation g i v i n g t h e d e f i n i t i o n s o f Type I, 'llype I f ,
C l a s s 1, and C l a s s 2 t r a j e c t o r i e s a l o n g w i t h a n
explana t t o n o f C, a d a n i n d i c a t i o n o f t h e isccur8cy
o f t h e d a t a . Also, mention s h o u l d b e made o f any
pariameters which may e f f e c t t h e Cg determined launch
o p p o r t u n i t y a l o n g w i t h any p o s s i b l e a l t e r n a t i v e a
such a s broken-plane t r a n e f s r s . The accompanying
i n f o r m a t i o n f o r t h i s f i g u r e might b e p r e s e n t e d a s
follows.

-

Definition of T e r n
Type X t r a j e c t o r i e s a r e t h o s e on which t h e spacec r a f t would t r a v e l l e s s t h a n 180"around t h e s u n
from t h e time t h e s p a c e c r a f t l e a v e s t h e e a r t h u n t i l
i t a r r i v e s a t Mars. Type 11 t r a j e c t o r i e s a r e t h o s e
on which t h e s p a c e c r a f t would t r a v e l b e t w e n 180'
and 360' around t h e s u n . C l a s s 1 and C l a s s 2 t r a j e e t o r i e s a r e s u b c l a s s e s o f Type X: and 'Sypra I1 and
d i f f e r p r i m a r i l y I n t h e f l i g h t times r e q u i r e d ,
C l a s s 2 t r a j e c t o r i e s having l o n g e r f l i g h t times
t h a n C l a s s 1 t r a j e c t o r i e s f o r t h e same launch d a t e
and C3. The parameter, C, , comes from t h e e q u a t i o n
which g i v e s t h e v e l o c i t y of, a n o b j e c t when t r a v e l i n g

�Figure 1

-

1973-74 Launch Opportunity for Mars

�250 days

LAUNCH
Figure 2

-

DATE

1973 Type I Launch Opportunity for Mars

�o n a c o n i c s e c t i o n . The c o n i c e q u a t i o n f o r t h e
v e l o c i t y o f a n o b j e c t is
(I)
where
is the e a r t h ' s gravitational constant, R
i s t h e d i s t a n c e from t h e c e n t e r of t h e e a r t h , and
a i s a measure o f t h e s i t e o f t h e c o n i c s e c t i o n .
Bxpressed i n tenna o f %, Equathon (1) becomes

C, is t h e i n j e c t i o n e n e r g y p r o v i d e d t o the spacec r a f t by t h e l a u n c h v e h i c l e and i s e q u a l t o t w i c e
t h e t o t a l e n e r g y p e r u n i t miss. A s R becomes v e r y
l a r g e , C3 a p p r o a c h e s V?. When t h e s p a c e c r a f t
leaves the g r a v i t a t i o n a l influence of the e a r t h , V
becomes V-, which i s t h e " v e l o c i t y a t i n f i n i t y " o r
t h e "hyperbolic-excess v e l o c i t y . "

-

I n f o r m a t i o n N e c e s s a r y t o U t i l i z e Graph
The C3 l i m i t a t i o n o f t h e l a u n c h v e h i c l e , a s
p r o v i d e d by performance s t u d i e s , i s a l l t h a t i s
needed.
I n f o r m a t i o n O b t a i n a b l e from Graph
Ranges o f l a u n c h d a t e s , a r r i v a l d a t e s , and
f l i g h t t i m e s a s a f u n c t i o n o f t h e C, l i m i t a t i o n s o f
t h e launch v e h i c l e . See F i g u r e 2 f o r a n e n l a r g e d
view o f lower v a l u e s o f
f o r Type I t r a j e c t o r i e s .
See F i g u r e 4 f o r h and a r r i v a l Vm c u r v e s f o r t h e
lower e n e r g y Type I t r a n s f e r s , These p a r a m e t e r s
may l i m i t t h e s i z e o f t h e C, detgrmined launch
opportunity.
A d d i t i o n a l C o n s t r a i n t s t o Consider
'. ( s e e F i g u r e 4 2 ; a r r i v a l V- ( s e e F i g u r e 4 ) ;
ccmmunica t i o n d i s t a n c e r e s t r i c t i o n s ; t r a c k i n g
c o n s t r a i n t s ( b o t h e a r t h o r b i t a l and deep s p a c e ) ;
o p e r a t i o n a l l i m i t a t i o n s on minimum l e n g t h o f launch
period.

Assumptions Made/Accuracy o f , Data/Cons t a n t s Used
Two-body c o n i c s were used i n t h e computation o f
t h e d a t a because t h e c o m p u t a t i o n time r e q u i r e d f o r
c o n i c t r a j e c t o r i e s is much l e s s t h a n t h a t r e q u i r e d
f o r n u m e r i c a l l y i n t e g r a t e d t r a j e c t o r i e s . Accuracy
of the d a t a i s considered adequate f o r mission
a n a l y s i s s t u d i e s . u (sun) = .13271544E12, t h e
a n a l y t i c ephemeris used t o o b t a i n t h e p l a n e t a r y
p o s i t i o n s is d e s c r i b e d i n E n g i n e e r i n g P l a n n i n g
Document No. 406, J e t P r o p u l s i o n L a b o r a t o r y , J u l y ,
1966.
Possible Alternatives
It may b e p o s s i b l e t o e x t e n d t h e launch opportuni'ty w i t h t h e u s e o f b r o k e n - p l a n e t r a n s f e r s .
T h e s ~a r e t r a j e c t o r i e s on which t h e s p a c e c r a f t
t r a v e l s p a r t o f t h e way t o Mars i n one f l i g h t p l a n e
a n d , a f t e r a v e l o c i t y c o r r e c t i o n i s made, t r a v e r s e s
t h e remaining d i s t a n c e i n a d i f f e r e n t f l i g h t p l a n e .
The t o t a l e n e r g y expended (C, + p l a n e change bV +
a r r i v a l Vm) i s l e s s f o r t h i s t y p e of t r a n s f e r t h a n
f o r e i t h e r a Type I o r Type I1 t r a j e c t o r y when t h e
h e l i o c e n t r i c t r a n s f e r angle for a single-plane
On
t r a n s f e r (Type I o r Type T I ) is n e a r 18$.
F i g u r e 1, t h e b r o k e n - p l a n e t r a n s f e r s o f i n t e r e s t
would b r i d g e t h e narrow gap between t h e Type Z and
Type f I c o n t o u r s . U n a t t r a c t i v e f e a t u r e s o f t h e
broken-plane t r a j e c t o r i e s a r e the a d d i t i o n a l

o p e r a t i o n a l complexity of t h e m i s s i o n and t h e
p o s s i b i l i t y o f l i t t l e o r no r e t u r n o f s c i e n t i f i c
i n f o r m a t i o n from t h e v i c i n i t y o f t h e t a r g e t p l a n e t
i f t h e plane-change maneuver f a i l s .
The s i x subheadings used above r e p r e s e n t a usea b l e and e f f e c t i v e method o f p r e s e n t i n g t h e supplemental i n f o r m a t i o n which should riccompany F i g u r e 1.
The ma t e r i a 1 p r e s e n t e d under t h e s e subheadings i s ,
t o a s t r o d y n a m i c i s t s , of a v e r y f a m i l i a r n a t u r e , and
might b e c o n s i d e r e d i n f o r m a t i o n which i s n o t worth
i n c l u d i n g s i n c e "everyone knows it." But, a g a i n , it
is t h i s f a m i l i a r i t y o f t h e a s t r o d y n a m i c i s t w i t h h i s
m a t e r i a l t h a t i s o f t e n t h e c a u s e o f comnunication
p r o b l b s . I f t h e above subheadings were used a s a
g u i d e o r c h e c k l i s t i n d e t e r m i n i n g whether t h e i n f o r mation accompanying t h e c h a r t s and graphs s u p p l i e d
t o t h e systems a n a l y s t i s complete, then t h e p o s s i b i l i t y o f misunderstandings and m i s i n t e r p r e t a t i o n s
o f t h e d a t a c o u l d b e reduced.
I n t h e d i s c u s s i o n of the ensuing g r a p h s , t h e
supplemental i n f o r m a t i o n w i l l n o t b e broken down
aad p r e s e n t e d under t h e above subheadings. I n s t e a d ,
t h e s a l i e n t f e a t u r e s o f t h e graphs w i l l be d i s c u s s e d
and t h e terms o r concepts which would b e p r e s e n t e d
i n g r e a t e r depth o r d e t a i l i n a n a c t u a l r e p o r t f o r
u s e i n m i s s i o n d e s i g n s t u d i e s w i l l b e mentioned b u t
not necessarily discussed i n d e t a i l .
It s h o u l d b e noted t h a t t h e supplemental i n f o r mation f o r F i g u r e 1, a s p r e s e n t e d above, c o n t a i n s
not o n l y Lnformation which may b e u s e f u l f o r t h e
c o r r e c t i n t e r p r e t a t i o n o f t h e graph b u t p e r i p h e r a l
i n f o r m a t i o n which p r o v i d e s t h e u s e r w i t h a backdrop
a g a i n s t which t h e d a t a on t h e graph c a n b e viewed.
T h i d p e r m i t s t h e systems a n a l y s t t o i n t e r p r e t t h e
d a t a i n a more e f f e c t i v e and meaningful manner.

The v a l u e o f a graph such a s F i g u r e 1 i s t h a t i t
provides an indication, i n the large, of t h e r e s t r i c t i o n s imposed by t h e launch energy. However, s i n c e
t h e g r e a t e s t i n t e r e s t probably c e n t e r s around t h e
lower v a l u e s o f C,, graphs such a s t h e one shown i n
F i g u r e 2 should a l s o be provided. A complete s e t o f
C3 c u r v e s f o r Mars would i n c l u d e seven o f t h e type
p r e s e n t e d i n F i g u r e 1 and f o u r t e e n o f t h e t y p e p r e s e n t e d i n F i g u r e 2 (seven graphs o f t h e lower C,
v a l u e s f o r t h e Type I t r a n s f e r s p l u s seven graphs o f
Also
t h e lowet C3 v a l u e s f o r Type I1 t r a j e c t o r i e s ) .
i n c l u d e d would be seven graphs showing t h e brokenp l a n e t r a n s f e r s which c o u l d b e used t o b r i d g e t h e
energy r i d g e between t h e Type I and Type I1 c o n t o u r s .
These t w e n t y - e i g h t graphs would r e p r e s e n t t h e
f i f t e e n y e a r p e r i o d r e q u i r e d f o r t h e e a r t h and Mars
t o r e t u r n t o a s i m i l a r s p a c e - f i x e d geometry. S i n c e
t h e supplemental i n f o m t i o n which should accompany
graphs o f t h e type shown i n F i g u r e 2 would b e n e a r l y
i d e n t i c a l t o t h a t which i s provided w i t h t h e F i g u r e 1
type o f g r a p h , t h e e n t i r e group o f l a r g e and s m a l l
s c a l e C3 c u r v e s f o r both 5 p e I and Type 11 could b e
i n c l u d e d under t h e same supplemental informa t i o n
s h e e t . The graphs r e p r e s e n t i n g t h e broken-plane
t r a n s f e r s would d i s p l a y n o t only t h e launch energy
c u r v e s b u t curves r e p r e s e n t i n g t h e AV needed f o r t h e
plane-change maneuver i n o r d e r t h a t a proper a s s e s s ment o f t h e energy requirements can b e made. The
method o f computation o f t h e AV would need t o b e
e x p l a i n e d and a d e t a i l e d i l l u s t r a t i o n o f t h e compari s o n between s i n g l e - p l a n e and broken-plane t r a n s f e r s
should a l s o be provided.

�8 =

DECLINATION

OF

=

INCLINATION

OF

ORBIT

P

:

Figure 3

-

Constraints

It would a p p e a r from F i g u r e 1 t h a t a continuous
o p p o r t u n i t y t o l a u n c h e x i s t s from a b o u t t h e middle
of J u n e , 1973 t o t h e m i d d l e o f
assuming t h a t a C, o f 3 0 &amp; / s e
t h e maximum
launch energy a v a i l a b l e . T h i s
month launch
o p p o r t u n i t y would indeed b e a v a i l a b l e i f t h e o n l y
r e s t r i c t i o n f o r a Mars m i s s i o n was t h e launch
energy. However, t h e r e a r e many o t h e r c o n s t r a i n t s
which need t o b e c o n s i d e r e d and which impose some
r a t h e r s e v e r e r e s t r i c t i o n s on t h i s twenty month
launch o p p o r t u n i t y ,
Consider f i r s t the d e c l i n a t i o n of the outgoing
asymptote,
F i g u r e 3 shows t h a t
i s one of t h e
two a n g l e s which d e f i n e t h e d i r e c t i o n o f t h e o u t going a s y m p t o t e ( t h e o t h e r a n g l e b e i n g t h e r i g h t
ascension).
The o u t g o i n g asymptote i n d i c a t e s t h e
d i r e c t i o n t h e s p a c e c r a f t must b e t r a v e l i n g r e l a t i v e
t o t h e e a r t h when t h e s p a c e c r a f t l e a v e s t h e e a r t h ' s
g r a v i t a t i o n a l i n f l u e n c e . The t h r e e views shown i n
F i g u r e 3 i n d i c a t e t h a t any v a l u e o f i may b e used
t o obtain the d e s i r e d value of 6 a s long a s i 2 h.
T h i s may n o t seem l i k e much o f a r e s t r i c t i o n e x c e p t
t h a t t h e v a l u e s o f i which c a n b e o b t a i n e d
(assuming t h a t t h e n e a r - e a r t h f l i g h t t a k e s p l a c e i n
a pace-fixed p l a n e ) a r e l i m i t e d by t h e l a t i t u d e of
t h e launch s i t e and t h e a v a i l a b l e r a n g e o f launch
a z i m u t h s . The minimum i n c l i n a t i o n o f t h e p a r k i n g
o r b i t which may be o b t a i n e d from a l a u n c h i n g a t
Cape Kennedy i s approximately 21;.28', which c a n be
a c h i e v e d by l a u n c h i n g due E a s t on a launch azimuth

*.

-

THE

ASYMPTOTE

E A R T H ' PARKING

I

HYPElE8OLA

VALUES

ACHIEVE

OF
THE

i MAY
SAME

BE

8,

USED

t i L 81

,

R e l a t i o n s h i p o f t h e Parking O r b i t P l a n e t o
t h e D e c l i n a t i o n o f t h e Outgoing Asyslptote

111. E v a l u a t i o n o f t h e h and

,V

OF

MANY

TO

s

OuttOiNG

PLANE

PERIGEE.

NOTE:

THE

of 90' E a s t of North. The maximum v a l u e o f i i s
determined by t h e range s a f e t y r e s t r i c t i o n s a n d / o r
t r a c k i n g requirements which r e s t r i c t t h e a v a i l a b l e
range o f launch azimuths. Thus, a r a n g e of launch
azimuths such a s 70' t o 110' would r e s u l t i n a
this
maximum a t t a i n a b l e v a l u e of i o f a b o u t 35'
would r e s t r i c t t h e u s a b l e v a l u e s of R t o a r a n g e
o f +3s0. The r e l a t i o n s h i p between launch azimuth
and h w i l l b e d i s c u s s e d i n g r e a t e r d e t a i l i n
Section IV.

-

The h y p e r b o l i c - e x c e s s v e l o c i t y a t a r r i v a l , Vm, is
a n o t h e r parameter which r e q u i r e s c o n s i d e r a t i o n i n a
m i s s i o n d e s i g n s t u d y . It p r o v i d e s a n i n d i c a t i o n o f
t h e minimum amount of veloc'ity which t h e s p a c e c r a f t
must l o s e i n o r d e r t o a t t a i n a n o r b i t a b o u t Mare.
Of c o u r s e , t h e s m a l l e r t h e d e s i r e d o r b i t a b o u t Mau,
(assuming t h e shape of o r b i t , e , i s c o n s t a n t ) t h e
g r e a t e r w i l l be t h e impulse o r AV t h a t t h e spacec r a f t w i l l have t o supply. Thus, knowledge of t h e
range o f v a l u e s o f Vm would p r o v i d e i n f o r m a t i o n f o r
d e t e r m i n i n g t h e s i z e o f r o c k e t motor and amount of
f u e l which would be n e c e s s a r y t o a t t a i n an o r b i t
a b o u t Mars.
Shown i n F i g u r e 4 a r e p l o t s of c o n s t a n t v a l u e s of
t h e s e p a r a m e t e r s . The h o r i z o n t a l and v e r t l c a l s c a l e s
a r e i d e n t i c a l t o t h o s e used i n F i g u r e 2 s o t h a t t h e
e f f e c t af t h e s e two parameters on t h e o v e r a l l Type I
launch o p p o r t u n i t y c a n b e e a s i l y e v a l u a t e d . A more
e f f e c t i v e way o f p r e s e n t i n g t h e combined e f f e c t of
C a r Vm, and h i s t o reproduce t h e c u r v e s o f Vm end h
on t r a n s p a r e n c i e s which would o v e r l a y t h e Cg c u r v e s .
It can b e s e e n from F i g u r e 4 t h a t f o r Type I

�.

-

.

ARRIVAL DATE

-

.-

MAY

APR

1974

JAN

DEC
1973 NOV

21

!

, ,
6 44
JUN 73
1

, , ,
16 21 26

,
I

JUL

Figure 4

-

,
6

./
, ,

,

,

,

,

,

,

,

,

,

10 15 20 25 30 4 9
AUG
SE P
LAUNCH DATE

I 1 16 21 26 31

5

Curves of b n d Vm f o r the 1973
Q p e I Launch Opportunity for Mars

.
I

14

i

�t r a n s f e r s , t h e e a r l i e s t a r r i v a l d a t e a t %rs would
p r o b a b l y b e determined by ,V a n d t h a t e a r l y launch
d a t e s a r e r e s t r i c t e d by h . The r e s t r i c t i o n s imposed
upon t h e launch o p p o r t u n i t y by V- and 6 a r e more
s e v e r e i n o t h e r launch y e a r s than is t h e c a s e i n
1973. For m i s s i o n d e s i g n purposes, c u r v e s o f 6 and
,V would a l s o b e provided f o r use w i t h F i g u r e 1
t y p e g r a p h a s w e l l a s t h e lower enargy Type I1
graphs.
A f t e r imposing upon t h e launch o p p o r t u n i t y t h e
c o n s t r a i n t s which have thus f a r been d i s c u s s e d , i t
m y b e u s e f u l t o i n c l u d e some p i c t u r e s t o i l l u s t r a t e what some o f t h e a v a i l a b l e t r a j e c t o r i e s would
look l i k e . Shown i n F i g u r e s 5 and 6 a r e t h r e e o f
t h e t r a j e c t o r i e s t h a t c o u l d b e used f o r a 1973
mission.
The t r a n s f e r s , and t h e o r b i t s o f e a r t h
and Mars, a r e drawn t o s c a l e and a r e viewed from a
v a n t a g e p o i n t above t h e North E c l i p t i c P o l e , with
t h e s u n a t t h e c e n t e r o f t h e f i g u r e s . An examinat i o n o f t h e t r a j e c t o r i e s would r e v e a l t h a t i n
t r a v e r s i n g t h e d i s t a n c e from e a r t h t o Mars, a l l
three of the transfers require a heliocentric transf e r a n g l e o f l e s s t h a n 180°, and thus a l l t h r e e a r e
Type I t r a n s f e r s . Using t h e p r e v i o u s l y mentioned
r e s t r i c t i o n s on A and f&amp; (6 5 +3s0, C j 5 30 &amp; / s e c 2 )
and p l a c i n g a r e s t r i c t i o n upon VW 5 4.0 laa/sec., i t
can b e s e e n from F i g u r e s 2 and 4 t h a t t h e t h r e e

EARLY

LAUMCH

-

EAALY

ARRIVAL

t r a j e c t o r i e s f a l l on t h e boundary of t h e launch
o p p o r t u n i t y d e f i n e d by t h e upper l i m i t s o f V
,
:,
and $ . The t r a j e c t o r y shown i n P i g u r e 5 is
c h a v a c t e r i z e d by v a l u e s o f C3 and
which a r e n e a r
t h e upper l i m i t s of t h e p e r m i s s i b l e r a n g e s o f t h e s e
c o n s t r a i n t s . The two t r a j e c t o r i e s shown i n F i g u r e
6 a r e t h e r e s u l t o f launches which o c c u r l a t e i n
t h e launch o p p o r t u n i t y w i t h t h e s h o r t f l i g h t time
t r a n s f e r having high ,V and C3 v a l u e s , and t h e long
f l i g h t tit r a j e c t o r y r e q u i r i n g t h e maximum a 1 lowa b l e value of &amp;.
P l o t s o f t r a j e c t o r i e s such a s
t h e s e would be o f v a l u e i n h e l p i n g t o visualize t h e
s i m u l a r i t i e s and d i f f e r e n c e s o f t h e t r a n s f e r s which
a r e a v a i l a b l e d u r i n g a launch o p p o r t u n i t y . For
completeness, a group o f t h e s e p l o t s i n t e n d e d f o r
use i n a m i s s i o n d e s i g n s t u d y would a l s o i n c l u d e
i l l u s t r a t i o n s o f a few Type I1 t r a n s f e r s a s w e l l
a s some broken-plane t r a j e c t o r i e s .

IV. Launch Windows
Thus f a r , t h e d i s c u s s i o n of m i s s i o n d e s i g n c h a r t s
h a s c e n t e r e d around t h e launch o p p o r t u n i t y a s
d e f i n e d by 6 , Vm, and C3. T h i s launch o p p o r t u n i t y
( s e e f i g u r e s 2 and 4 ) is a g r i d , w i t h e v e r y p a i r of
launch and a r r i v a l d a t e s r e p r e s e n t i n g a s m a l l s q u a r e
w i t h i n t h e g r i d . The p e r i o d o f time w i t h i n e a c h o f
t h e 24 hour s q u a r e s d u r i n g which a launch c a n o c c u r

*D

LA'E
LATE

. A L ~ I C ~ -I L A ' E A R R I V A L
LAUNCH
E A R L Y ARRIVA!

-

Pigure 6

Figure S
1973 Type I T r a n s f e r s Drawn to S c a l e

�Figure 7

- Launch
Azimuth a s a Function o f Launch
Time w i t h D e c l i n a t i o n a s t h e Parameter

e
i s known a s t h e launch window. Note t h a t w i t h i n
each launch window t h e v a l u e s o f C,, 6 , and Vm
remain r e l a t i v e l y c o n s t a n t . The u s e o f a launch
window is d e s i r a b l e s i n c e t h e a l t e r n a t i v e , t h e
l a u n c h i n g of a v e h i c l e a t a p r e c i s e t i m e , would n o t
p e r m i t a n y unscheduled d e l a y s i n t h e launch prep a r a t i o n s and would n o t a l l o w any h o l d i n g time f o
a w a i t improved w e a t h e r c o n d i t i o n s . The d u r a t i o n of
t h e launch window depends upon t h e r a n g e of a v a i l a b l e launch a z i m u t h s , t h e l a t i t u d e o f t h e launch
s i t e , and t h e d e c l i n a t i o n of t h e o u t g o i n g asymptote,
S i n c e t h e v a l u e o f 6 is e s s e n t i a l l y f i x e d , and t h e
launch s i t e i s r e l a t i v e l y f i x e d ( a t a l a t i t u d e o f
t h e o n l y t h i n g t h a t can b e v a r i e d t o
a b o u t 28.28'),
a c h i e v e a n extended p e r i o d d u r i n g whi,ch t o launch
is t h e launch azimuth. The use o f a v a r i a b l e h u n c h
azimuth implies t h e use of a parking o r b i t s o t h a t
t h e Eirtel b u r n of t h e o r b i t i n g b o o s t v e h i c l e c a n be
properly pos~.rionedw
. t t h r e s p e c t t o t h e outgoing
asymptote. F i g u r e 7 shows t h e s i z e o f t h e launch
window t h a t c a n be o b t a i n e d by v a r y i n g t h e launch
me b f s w i t h the a s t e r i s k s ( * I s ) i n d i c a t e
t h a t t h e y a r e t o b e r e a d a g a i n s t t h e upper launch
t i m e s c a l e , w i t h t h e remaining A ' s t o be r e a d
'
a g a i n s t t h e losJer s c a l e . ~h~ e x c e p t i o n i s 6 = 0'
which i s r e a d a g a i n s t b o t h launch time s c a l e s .
m e d o u b l e v a l u e d n a t u r e of t h e launch time i n d i c a t e s t h a t two s e p a r a t e launch windows may e x i s t
w i t h i n one 24 hour p e r i o d . When t h e a v a i l a b l e
r a n g e o f launch a z i m u t h s is k n a j n and t h e v a l u e o f
8 is known ( t h i s c a n b e o b t a i n e d from graphs such
a s shown i n F i g u r e 4 1 , t h e n t h e l e n g t h o f t h e
a v a i l a b l e launch window(s) c a n be o b t a i n e d i n t h e
f o l l o w i n g manner. A s s m i ng t h e launch azimuth
r e s t r i c t i o n s s t a t e d p r e v i o u s l y (5 110', 2 70') and
R h o f +15',
f i n d t h e i n t e r s e c t i o n of t h e h = 15'*
curve with the horizontal l i n e representing a
lqunch azimuth (LAZ) of 70' and n o t e t h e v a l u e of

*

launch time on t h e
s c a l e -1.93 h o u r s . Now move
a l o n g t h e 6 = 15'* c u r v e towards t h e upper r i g h t
(always move a l o n g t h e c u r v e s o f S i n t h e d i r e c t i o n
o f i n c r e a s i n g time on t h e launch time s c a l e ) u n t i l
t h e i n t e r s e c t i o n w i t h LAZ = 110' i s reached and n o t e
t h i s time on t h e
s c a l e below -6.93 h o u r s . Take
t h e d i f f e r e n c e between t h e s e two times and f i n d t h a t
t h e launch window d u r a t i o n i s f i v e hours. Now t r a c e
a l o n g t h e 6 = 15' c u r v e i n a s i m i l a r mannet from
LAZ = 70' t o LAZ = 110' and, r e a d i n g a g a i n s t t h e
lower launch time s c a l e , t h e d u r a t i o n o f t h e launch
window w i l l be found t o b e 22.07 h o u r s minus 17.07
h o u r s , o r f i v e hours. When t h e ran$e of launch
azimuths i s s w e t r i c a l a b o u t 90' ( a s i s t h e c a s e
w i t h 70°and 110' ) t h e l e n g t h o f t h e two launch
wir~dowsw i l l b e i d e n t i c a l . Assume now t h a t t h e
launch azimuth r e s t r i c t i o n s a r e 6 8 _&lt; LA2 5 loo0
and t h e v a l u e of 6 is +30°.
Tracing along t h e
= 30°* c u r v e shows t h a t i t never r e a c h e s t h e r a n g e
o f al1o;able launch azimuths and t h u s does n o t prov i d e any launch window. However, t r a c i n g a l o n g t h e
= 30' does p r o v i d e a launch window o f 23.77 h o u r s
minus 17.50 h o u r s , o r 6.27 h o u r s . The launch times
shown on F i g u r e 7 do n o t correspond t o t h e S a s t e r n
Standard o r Greenwich Mean times o f launch
the
time shown on t h e s c a l e s is a r e l a t i v e and n o t a n
a b s o l u t e time. S e v e r a l o t h e r s e t s o f c u r v e s , used
i n c o n j u n c t i o n w i t h F i g u r e 7 , would be n e c e s s a r y t o
supply t h e a c t u a l launch times. The primary r e a sons f o r p r o v i d i n g a f o l d e d launch time w a l e on
F i g u r e 7 were t o make i t e a s y t o compute t h e l e n g t h
o f time between t h e end o f t h e f i r s t launch window
and t h e beginning o f t h e second and t o h e l p r e l a t e
t h i s i n f o r m a t i o n t o t h a t on F i g u r e 8. The p r o c e d u r e
whieh has been o u t l i n e d above f o r u s i n g F i g u r e 7 i s
v a l i d only f o r p o s i t i v e v a l u e s of 6 . When n e g a t i v e
v a l u e s o f A a r e ueed i t i s n e c e s s a r y t o move t h e
a s t e r i s k s (*IS) from t h e top launch t i m e s c a l e t o

*

-

�thi? bottom launch time s c a l e and then proceed a s
before.
I n a d d i t i o n t o the d u r a t i o n of t h e launch window,
t h e time t h e boost v e h i c l e must spend c o a s t i n g i n
t h e parking o r b i t can a l s o be expressed a s a funct i o n of t h e launch azimuth and 6. The use of a
c o a s t a r c provides an e f f i c i e n t method f o r t h e prop e r p o s i t i o n i n g of t h e f i n a l burn a r c of t h e boost
vehicle
t h i s is . t h e burn which removes t h e spacec r a f t from i t s e a r t h parking o r b i t and p l a c e s it
o n t o t h e d e s i r e d i n t e r p l a n e t a r y t r a j e c t o r y . Figure
8 and Figure 9 provide a means f o r determining what
t h e l e n g t h o f t h e c o a s t time ( o r c o a s t a r c ) must be
i n o r d e r t o a c h i e v e t h e proper e a r t h d e p a r t u r e
geometry. The i n t e r p r e t a t i o n of Figure 8 i s accomp l i s h e d i n a manner very s i m i l a r t o t h a t used i n
Figure 7. Knowing t h e v a l u e of fi needed and t h e
range of launch azimuths which can b e used, t h e
range of c o a s t a r c s ( c o a s t times) which a r e required
can be found on t h e s c a l e s a c r o s s t h e bottom o f t h e
graph. The a s t e r i s k s (*'s) have t h e same meaning on
Figure 8 a s they d i d on F i g u r e 7 , including t h e
switching of s c a l e s f o r n e g a t i v e values o f h . The
primary d i f f e r e n c e i n t h e i n t e r p r e t a t i o n of Figure 8
a s opposed t o Figure 7 is t h a t t h e s c a l e s f o r t h e
c o a s t time and c o a s t a r c on Figure 8 a r e a b s o l u t e ,
and t h e r e f o r e i n d i v i d u a l values of c o a s t time (coast
a r c ) can be read from t h e graph (on Figure 7 i t was
only p o s s i b l e t o read time spans, a s t h e i n d i v i d u a l
times on t h e graph were r e l a t i v e ) . For example,
assuming a launch azimuth range o f 70' 5 LAZ _&lt; 110'
and a 6 of +IS', i t can be seen from Figure 8 t h a t
t h e c o a s t a r c - r e q u i r e d f o r one launch window ranges

-

"

from about 85' t o 150°, while a range £ran a b o u t
210' t o 275' is necessary f o r the o t h e r launch
window. Since t h e values of t h e c o a s t s r c a r e
a b s o l u t e , then i t can a l s o be s a i d t h a t i f a launch
azimuth of 70' i s used t o achieve a 6 o f +15',
it
would be necessary f o r t h e l e n g t h o f t h e earth
o r b i t a l c o a s t i n g a r c to* be e i t h e r 1 5 6 o r 275'.
*By
using Figures 7-and 8 t o g e t h e r , t h e behavior of t h e
c o a s t a r c a c r o s s t h e launch wtn%ow(s) can be observed. From t h e above example i t i s h n n n t b d t
t h e c o a s t a r c s f o r t h e two launch windavs r a n g e
To determine
from 85O t o 150' and 210' t o 275'.
which is t h e i n i t i a l and which L s t h e f i n a l v a l u e
of the c o a s t a r c s it i s necessary to r e f e r back t o
Figure 7. Using Figure 7, t r a c e a l o n g t h e curves
= +15' i n t h e sense of i n c r e a s i n g launch time.
of
Notice t h a t both launch windows open using a launch
azimuth o f 60' and both c l o s e , f i v e hours l a t e r ,
with a launch azimuth o f 118. Now, using F i g u r e 8 ,
t r a c e along t h e 6 = +15' curves and n o t e t h a t t h e
only way t h e behavior of t h e launch a z i m t h , a s
noted on Figure 7, can be d u p l i c a t e d , i s t o t r a c e
along t h e curves o f d e c l i n a t i o n from r i g h t t o l e f t .
This method o f nro\reprent alpng t h e l i n e s of c o n s t a n t
-%a -&amp;be d e c l i n a t i o n , always moving t o t h e
c o r r e c t procedure f o r u t i l i z i n g Figure 8, i.e.,
within a launch window, a s t h e launch t i m e i n c r e a s e s ,
t h e c o a s t time (coast a r c ) decreases. 2he ranges of
c o a s t a r c s (and c o a s t times) obtained from F i g u r e 8
can be matched t o t h e launch windows o b t a i n e d from
Figure 7 by combining t h e values from t h e a s t e r i s k
(*) s c a l e s t o d e f i n e one launch window and combining t h e values from t h e unmarked s c a l e s to form
t h e o t h e r launch window. ' K e r e f o r e froan the range

LAUNCH AZIMUTH (dep)

COAST TIME (rnlnl

Figure 8

- Launch Azimuth a s a Function of

Coast Arc and
Coast Time with Declination a s t h e Paradleter

�o f launch azimuths and t h e v a l u e o f b used i n t h e
example above, t h e following information i s obtaina b l e front Figures 7 and 8. Two launch witidows a r e
a v a i l a b l e , both o f f i v e hours d u r a t i o n . The f g r s t
launch w i d o w opens w i t h a launch azimuth o f 7@ and
a c o a s t time o f d m u t 37 minutes. As t h e launch
tZme *ncreases, the launch azimuth slowly i n c r e a s e s
and t h e c o a s t time slowly d e c r e a s e s u n t i l , a t t h e
end of t h e f i r s t window, t h e launch a z i m t % has
reached 110' and t h e c o a s t time h a s d e c l i n e d to
about 21 d n u t e s . About 1 0 hours l a t e r the second
launch window opens w i t h a launch azimuth of 70'
and a c o a s t time o f about 67 minutes. Acxoss t h e
window, t h e launch azimuth and c o a s t time v a r y
slowly, a s b e f o r e , u n t i l a t t h e end o f tIy f i v e
hour wendow, t h e launch azimuth a t t a i n s 110' and t h e
c o a s t t i m e reaches 51 minutes.
I n a d d i t i o n t o t h e launch azimuth and 6, t h e
c o a s t a r c 19 a l s o a f u n c t i o n of such t h i n g s a s t h e
parking o r b i t r a d i u s , t h e i n j e c t i o n energy (C,) t h e
t&amp;e aneomely of' t h e iWje.ction. i t i W a t h e escape hyperb o l a , t h e l e n g t h o f t h e f i r s t and second burn a r c s
of t h e b o o s t v e h i c l e , t h e r a d i u s o f c l o s e approach
of t h e escape hypefbola, and t h e l a t i t u d e of t h e
launch s i t e . Constant values were assumed f o r a l l
of t h e s e parameters and t h e values t h a t were used
should c e r t a i n l y b e included w i t h thh supplemental
information provided w i t h t h e graph. It may n o t be
necessary t o i n c l u d e a f u l l e x p l a n a t i o n of t h e meani n g of t h e s e parameters, b u t t h e aystems a n a l y s t
should be provided w i t h t h e knowledge t h a t assumpt i o n s were made and should be given t h e values of .
t h e c o n s t a n t s t h a t were used. The values o f t h e
c o n s t a n t s used i n t h e g e n e r a t i o n o f t h e d a t a o f
Figure 8 a r e , i n t h e o r d e r given above and beginning
= 6583 km (a 100
w i t h t h e parking o r b i t r a d i u s :
12.125
n a u t i c a l m i l e a l t i t u d e parking o r b i t ) ; C,
k d ? s e c 2 ; u = 16.2'; 4 = 20.47'~ I)1 = 29.0';
RCA = 6583 km; m = 28.28'.
Since Pigure 8 could be
expected t o be used w i t h a wide range of Cj '8, and
a change i n t h e C3 does a f f e c t t h e v a l u e of t h e
c o a s t time ( c o a s t a r c ) , t h e e f f e c t o f a v a r i a t i o n i n
C, upon t h e launch window w i l l be discussed b r i e f l y .
A s f o r t h e e f f e c t of t h e o t h e r parameters upon t h e
c o a s t time, s u f f i c e i t t o say t h a t i f a launch i s
made from Cape Kennedy w i t h a S a t u r n V c l a s s v e h i c l e ,
t h e information obtained from Figure 8 would be
completely adequate f o r use i n mission design
s t u d i e s . I f t h e launch window information obtained
from Figure 8 i s a s s o c i a t e d w i t h a n i n t e r p l a n e t a r y
t r a j e c t o r y which r e q u i r e s a n i n j e c t i o n energy (C,)
t h a t i s d i f f e r e n t from 12 .I25 I&amp;
/sec2, then a
c o r r e c t i o n should be made t o t h e c o a s t times ( c o a s t
a r c s ) provided by Figure 8. Figure 9 shows t h e
amount of t h e c o a s t time c o r r e c t i o n a s a f u n c t i o n of
Simply combine t h e a p p r o p r i a t e c o a s t time
C,.
c o r r e c t i o n from Figure 9 w i t h t h e values of t h e
c o a s t time obtained from Figure 6.

+

COAST TIME ( m i n l

,

%

-

To complete t h e supplemental informatioh which
would accompany Figures 7 and 8 i n a mission design
document, mention should be made of t h e use of
"dog- leg" maneuvers which could be used t o extend
t h e launch window. Of course, t h e p e n a l t i e s i n c u r r e d from t h e use of a "dog-leg" maneuver should
a l s o be d i s c u s s e d . A s mentioned previously, i f t h e
s i x subheadings l i s t e d under S e c t i o n I1 a r e used a s
a c h e c k l i s t i n t h e p r e p a r a t i o n of t h e supplemental
information which should accompany each c h a r t o r
graph, then t h e l i k e l i h o o d of misunderstandings and
m i s i n t e r p r e t a t i o n s can be reduced, and t h e systems
engineer can u t i l i z e t h e d a t a with f u l l knowledge of
t h e options which a r e a v a i l a b l e t o him.

Figure 9
..
.

V.

- Parking-Orbit

Coast Time
Correction a s a Function of

C,

-

&lt; ~t eal l i t e O r b i t a l Considera t i o n s

The f i n a l phase t o be considered i n a mission
design study i s t h e a r r i v a l of t h e s p a c e c r a f t a t
t h e trjirget p l a n e t . The a s trodynamica 1 d a t a supplied
t o the' systems a n a l y s t i n support of t M s phase of
t h e study i s c h i e f l y concerned with t h e r e p r e s e n t s t i o n and c l a s s i f i c a t i o n of t h e c h a r a c t e r i s t i c s o f
a l l a v a i l a b l e o r b i t s about Mars, and t h e method by
which these o r b i t s can be a t t a i n e d . It i s n o t
f e a s i b l e , w i t h i n t h e l i m i t e d space a v a i l a b l e i n t h i s
paper, t o p r e s e n t and d i s c e s s the c h a r t s and graphs
which would b e used t o c l a s s i f y and l o c a t e s p e c i f i c
o r b i t s of i n t e r e s t . The d i s c u s s i o n w i l l d e a l p r i marily with the major s c i e n t i f i c and engineering
c o n s t r a i n t s which must be considered i n the course
of t h e o r b i t s e l e c t i o n process.
Since t h e primary reason f o r an o r b i t a l reconnaissance mission t o Mars i s the s c i e n t i f i c invest i g a t i o n of t h e p l a n e t , i t would seem reasonable t o
c o n s i d e r f i r s t t h e s c i e n t i f i c c o n s t r a i n t s upon t h e
o r b i t . These requirements might i n c l u d e r e s t r i c t i o n s on, o r s p e c i f i c a t i o n s o f , t h e o r b i t ' s s i Z e ,
shape, i n c l i n a t i o n and o r i e n t a t i o n f o r such purposes
a s photography, W photometry, meteorology, f i e l d s
and p e r t i c l e s measurements, S-band o c c u l t a t i o n s ,
magnerometer measurements, o r r e l e a s e of a lander
capsule. When a l l of t h e r e s t r i c t i o n s which r e s u l t
from experiments such a s these a r e imposed upon t h e
o r b i t , t h e r e s u l t i n g number of p o s s i b l e o r b i t s which
could be used i s , a t b e s t , s e v e r e l y reduced. Nat,
consider t h e engineering c o n s t r a i n t s upon t h e o r b i t .
These c o n s t r a i n t s a r e imposed s o t h a t t h e various
s p a c e c r a f t systems and subsystems w i l l o p e r a t e
e f f e c t i v e l y and e f f i c i e n t l y , and thus permit t h e
s c i e n t i f i c i n v e s t i g a t i o n s mentioned above t o proceed normally. The engineering c o n s t r a i n t s may
p l a c e requirements on the o r b i t f o r such things a s
power generation ( s p a c e c r a f t must remain i n s u n l i g h t

�.-

p

5

-.
a s much a s p o s s i b l e ) , navigation ( s p a c e c r a f t must
maintain f i x on n a v i g a t i o n a l s t a r t s ) ) , and commun i c e t i o n s (spacpcraf t must maintain c o n t a c t with
e a r t h f o r t h e transmission of d e w ) . I n a d d i t i o n
t o these c o n s t r a i n t s t h e l i m i t a t i o n imposed by t h e
performance of t h e s p a c e c r a f t retro-propulsion
system must be conaiderad. This performance ca2ab i l i t y p l a c e s a lower bound on t h e s i t e and shaoe
of t h e o r b i t s which can be a t t a i n e d about Mars.
The l i m i t a t i o n s imposed by t h i s c o n s t r a i n t a r e
represented on t h e i n t e r p l a n e t a r y launch opportunity
c h a r t s by t h e parameter VW (see Figure 4). When a l l
o f t h e s c i e n t i f i c and engineering c o n s t r a t n t s which
have thus f a r been discussed a r e imposed, i n t o t a l ,
a s requirements upon t h e o r b i t , t h e number of o r b i t s
which can provide t h e d e s i r e d c h a r a c t e r i s t i c s is
o f e n zero. Thus, s i n c e i t w i l l very l i k e l y be t h e
c a s e t h a t everything which i s required o r d e s i r e d
cannot be achieved, i t w i l l be necessary f o r t h e
systems a n a l y s t t o perform t r a d e o f f s t u d i e s i h
o r d e r t o maximize t h e t o t a l s c i e n t i f i c r e t u r n from
t h e mission. The arrtrodpnamicist should t h e r e f o r e
supply d a t a which would r e p r e s e n t , i n an e f f e c t i v e
manner, t h e impact of each of t h e c o n s t r a i n t s upon
t h e s i z e , shape, i n c l i n a t i o n , and o r i e n t a t i o n of
t h e a v a i l a b l e o r b i t s , and which would i n d i c a t e t o
t h e a n a l y s t t h e a v a i l a b l e ranges of t h e q r b i t a i
parameters s o t h a t t h e s t u d i e s can be perfomed i n
a n e f f i c i m t and m n i n g f u l manner.

,

The e f f e c t i v e t r a n s f e r of d a t a from t h e a s t r o dynamicist t o t h e systems engineer can be accomp l i s h e d r a t h e r e a s i l y i f e l i t t l e c a r e i s taken i n
t h e p r e p a r a t i o n of t h e supplemenU1 information
which should aceompany each of t h e c h a r t s and graphs.
The use of a c h e c k l i s t i n t h e p r e p a r a t i o n of t h e
supplemental i n f o m t i o n may help t o e l i m i n a t e
omissions which may occur because of t h e a s t r u dynamicist's f a m i l i a r i t y w i t h h i s own m a t e r i a l .
The o b j e c t i v e of the astrodynamicist should be t o
p r e s e n t t o t h e systems engineer material'whicF can
be used e s s i l y and e f f e c t i v e l y , and which w i l l cont a i n a l l of t h e supplemental information necessary
t o enable t h e system a n a l y s t t o perform meaningful
tradeof f s t u d i e s atid make knowledgeable d e c i s i o n s

.

�</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="22955">
                <text>spc_stnv_000129</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22956">
                <text>"The Astrodynamicist's Role vis-a-vis the Systems Engineer."</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="22957">
                <text>AIAA Paper No. 69-124</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22958">
                <text>By J. Reynolds Duncan, Jr., Aerospace Engineer, NASA Marshall Space Flight Center, Huntsville, Alabama. AIAA 7th Aerospace Sciences Meeting, New York City, New York, January 20 - 22, 1969.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22959">
                <text>Duncan, J. Reynolds, Jr.</text>
              </elementText>
              <elementText elementTextId="22960">
                <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="22961">
                <text>1969-01-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="22962">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22963">
                <text>Astrodynamics</text>
              </elementText>
              <elementText elementTextId="22964">
                <text>Communication of technical information</text>
              </elementText>
              <elementText elementTextId="22965">
                <text>Space flight to Mars</text>
              </elementText>
              <elementText elementTextId="22966">
                <text>Systems engineering</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22967">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="22968">
                <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="22969">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="22970">
                <text>Box 30, Folder 14</text>
              </elementText>
              <elementText elementTextId="205935">
                <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="22972">
                <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="22973">
                <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="22974">
                <text>spc_stnv_000119_000149</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="22975">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18064</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
