<?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/browse?output=omeka-xml&amp;page=55&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-09T04:25:05+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>55</pageNumber>
      <perPage>20</perPage>
      <totalResults>8239</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10582" public="1" featured="0">
    <fileContainer>
      <file fileId="9211">
        <src>https://digitalprojects.uah.edu/files/original/20/10582/satsivcryoweighsyst-II_072007103745.pdf</src>
        <authentication>1be6512f78ca58e0c4ece0b73fa74770</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="159652">
                <text>satsivcryoweighsyst-II_072007103745.pdf</text>
              </elementText>
              <elementText elementTextId="159653">
                <text>spc_stnv_000694</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159654">
                <text>"Saturn S-IV cryogenic weigh system. Part II : weigh operations."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159655">
                <text>Two basic methods for mass determination are: (1) direct measurement, (2) volume and density determination. Both methods or variations have been used to determine space vehicle propellant mass with varying degrees of success. Stringent propellant loading accuracy requirements of k0.5 percent for the Saturn S-IV Stage have led to the development of a Cryogenic Calibration Weigh System. The method employs accurate electronic force transducers and measuring systems as the standard and experimental weighings have verified achievement of better than the required accuracy.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159656">
                <text>Matsumoto, G. A.</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="159657">
                <text>1965-06-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="159658">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159659">
                <text>Liquid propellant rockets--Fuel tanks--Level indicators</text>
              </elementText>
              <elementText elementTextId="159660">
                <text>Cryogenic rocket propellants</text>
              </elementText>
              <elementText elementTextId="159661">
                <text>Saturn S-4 stage</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159662">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="159663">
                <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="159664">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="159665">
                <text>Box 14, Folder 17</text>
              </elementText>
              <elementText elementTextId="210346">
                <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="159667">
                <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="159668">
                <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="159669">
                <text>spc_stnv_000675_000699</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="159670">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17164</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10580" public="1" featured="0">
    <fileContainer>
      <file fileId="9213">
        <src>https://digitalprojects.uah.edu/files/original/20/10580/satsivcryoweighsyst_072007101249.pdf</src>
        <authentication>17cfd3ced4f9086134a3da162c1067aa</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="159614">
                <text>satsivcryoweighsyst_072007101249.pdf</text>
              </elementText>
              <elementText elementTextId="159615">
                <text>spc_stnv_000692</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159616">
                <text>"Saturn S-IV cryogenic weigh system. Part IV : safety."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159617">
                <text>During cryogenic weigh system operation, hydrogen when combined with oxygen can create an unsafe condition. Therefore the concentration of the residual oxygen and hydrogen from leaks in the cryogenic weigh environmental bags must be known at all times during the cryogenic weigh.  Hydrogen and oxygen detectors will provide the optimum method for maintaining safe conditions.  Hydrogen properties and safe mixtures are reviewed.  The method selected to analyze the oxygen content is discussed. The selection, development, and testing of a hydrogen detector system is examined.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159618">
                <text>Corcoran, Edward G.</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="159619">
                <text>1965-06-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="159620">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159621">
                <text>Liquid propellant rockets</text>
              </elementText>
              <elementText elementTextId="159622">
                <text>Cryogenic rocket propellants</text>
              </elementText>
              <elementText elementTextId="159623">
                <text>Safety</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159624">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="159625">
                <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="159626">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="159627">
                <text>Box 14, Folder 8</text>
              </elementText>
              <elementText elementTextId="210344">
                <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="159629">
                <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="159630">
                <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="159631">
                <text>spc_stnv_000675_000699</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="159632">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17165</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10515" public="1" featured="0">
    <fileContainer>
      <file fileId="9148">
        <src>https://digitalprojects.uah.edu/files/original/20/10515/Satusivengi_110110145014.pdf</src>
        <authentication>9d5b1e8dd512865c3853bc062a6719e1</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="158329">
                <text>Satusivengi_110110145014.pdf</text>
              </elementText>
              <elementText elementTextId="158330">
                <text>spc_stnv_000749</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158331">
                <text>"Saturn S-IV engines."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158332">
                <text>Folder of information.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158333">
                <text>Pratt &amp; Whitney Aircraft Company</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="158334">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158335">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="158336">
                <text>Launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158337">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="158338">
                <text>Photographs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="158339">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="158340">
                <text>Box 32, Folder 24</text>
              </elementText>
              <elementText elementTextId="210302">
                <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="158342">
                <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="158343">
                <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="158344">
                <text>spc_stnv_000725_000749</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="158345">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18212</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10469" public="1" featured="0">
    <fileContainer>
      <file fileId="9147">
        <src>https://digitalprojects.uah.edu/files/original/20/10469/Satusivfirs_102810143053.pdf</src>
        <authentication>47a1bdb01d79f03806635a043908a236</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="157418">
                <text>Satusivfirs_102810143053.pdf</text>
              </elementText>
              <elementText elementTextId="157419">
                <text>spc_stnv_000751</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157420">
                <text>"Saturn S-IV first firing."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157421">
                <text>Press release detailing the firing of the Saturn S-IV in California.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157422">
                <text>Douglas Aircraft</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="157423">
                <text>1962-08-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157424">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157425">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157426">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157427">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157428">
                <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="157429">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210257">
                <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="157431">
                <text>Saturn S-IV engines.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157432">
                <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="157433">
                <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="157434">
                <text>spc_stnv_000750_000774</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10514" public="1" featured="0">
    <fileContainer>
      <file fileId="9149">
        <src>https://digitalprojects.uah.edu/files/original/20/10514/satuS-IVBquartechprogrepo_110607103908.pdf</src>
        <authentication>ec89715c7c041fbb8ed75639c71cf920</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="158307">
                <text>satuS-IVBquartechprogrepo_110607103908.pdf</text>
              </elementText>
              <elementText elementTextId="158308">
                <text>spc_stnv_000748</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158309">
                <text>"Saturn S-IVB quarterly technical progress report."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158310">
                <text>Douglas Aircraft Company Report DAC-56445, Saturn S-IVB Quarterly Technical Progress Report, covers design and development progress on the Saturn IB and Saturn V configurations of the S-IVB stage during August and September 1966.  This report is prepared for the National Aeronautics and Space Administration under Contract NAS7-101.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158311">
                <text>Rainwater, B. J.</text>
              </elementText>
              <elementText elementTextId="158312">
                <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="158313">
                <text>1966-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="158314">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158315">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="158316">
                <text>Saturn launch vehicles--Design and construction</text>
              </elementText>
              <elementText elementTextId="158317">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
              <elementText elementTextId="158318">
                <text>Project management</text>
              </elementText>
              <elementText elementTextId="158319">
                <text>Saturn S-4B stage</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158320">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="158321">
                <text>Progress Reports</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="158322">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="158323">
                <text>Box 19, Folder 5</text>
              </elementText>
              <elementText elementTextId="210301">
                <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="158325">
                <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="158326">
                <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="158327">
                <text>spc_stnv_000725_000749</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="158328">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17526</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10578" public="1" featured="0">
    <fileContainer>
      <file fileId="9215">
        <src>https://digitalprojects.uah.edu/files/original/20/10578/Satquatecprorep_022108133339.pdf</src>
        <authentication>95165ed12e55edf43f345ca94c56cb37</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="159579">
                <text>Satquatecprorep_022108133339.pdf</text>
              </elementText>
              <elementText elementTextId="159580">
                <text>spc_stnv_000690</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159581">
                <text>"Saturn S-IVB quarterly technical progress report."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159582">
                <text>Douglas Aircraft Company Report DAC-56533, Saturn S-IVB Quarterly Technical Progress Report, covers design and development progress on the Saturn IB and Saturn V configurations of the S-IVB stage during January, February, and March 1967. This report is prepared for the National Aeronautics and Space Administration under Contract NAS7-01.;  Prepared for National Aeronautics and Space Administration under NASA contract NAS7-101.;  Approved by A. P. O'Neal, Director, Saturn Development Engineering.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159583">
                <text>Rainwater, B. J.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159584">
                <text>1967-03-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="159585">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159586">
                <text>Saturn launch vehicles--Design and construction</text>
              </elementText>
              <elementText elementTextId="159587">
                <text>Saturn launch vehicles--Testing</text>
              </elementText>
              <elementText elementTextId="159588">
                <text>Project management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159589">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="159590">
                <text>Progress Reports</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="159591">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="159592">
                <text>Box 19, Folder 5</text>
              </elementText>
              <elementText elementTextId="210342">
                <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="159594">
                <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="159595">
                <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="159596">
                <text>spc_stnv_000675_000699</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="159597">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17526</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10504" public="1" featured="0">
    <fileContainer>
      <file fileId="9153">
        <src>https://digitalprojects.uah.edu/files/original/20/10504/saturnsa-1flighanditsinstrumenta_031607091738.pdf</src>
        <authentication>3a7e47a2a9d4269193f09c9a0e86bd84</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="158114">
                <text>saturnsa-1flighanditsinstrumenta_031607091738.pdf</text>
              </elementText>
              <elementText elementTextId="158115">
                <text>spc_stnv_000736</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158116">
                <text>"Saturn SA-1 flight and its instrumentation."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158117">
                <text>Presentation focusing on empahsising the importance of space programs such as Saturn.</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="158118">
                <text>1962-04-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="158119">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158120">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="158121">
                <text>Saturn 1 SA-1 launch vehicle</text>
              </elementText>
              <elementText elementTextId="158122">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="158123">
                <text>Astronautical instruments</text>
              </elementText>
              <elementText elementTextId="158124">
                <text>Spacecraft instruments</text>
              </elementText>
              <elementText elementTextId="158125">
                <text>Astrionics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158126">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="158127">
                <text>Presentations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="158128">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="158129">
                <text>Box 6, Folder 56</text>
              </elementText>
              <elementText elementTextId="210291">
                <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="158131">
                <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="158132">
                <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="158133">
                <text>spc_stnv_000725_000749</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="158134">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16768</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10471" public="1" featured="0">
    <fileContainer>
      <file fileId="9146">
        <src>https://digitalprojects.uah.edu/files/original/20/10471/SatuST12inerguid_051310124015.pdf</src>
        <authentication>59b9cecf1915a4fd9c82224181eb4ad0</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="157454">
                <text>SatuST12inerguid_051310124015.pdf</text>
              </elementText>
              <elementText elementTextId="157455">
                <text>spc_stnv_000753</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157456">
                <text>"Saturn ST-124-M inertial guidance platform."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157457">
                <text>a press release which focuses around the Apollo 9 flight and what role the ST-124-M inertial guidance platform has in it.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157458">
                <text>Bendix Corporation. Navigation &amp; Control 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="157459">
                <text>1969-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157460">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157461">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157462">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157463">
                <text>Lunar module</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157464">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157465">
                <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="157466">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157467">
                <text>Box 30, Folder 28</text>
              </elementText>
              <elementText elementTextId="210259">
                <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="157469">
                <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="157470">
                <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="157471">
                <text>spc_stnv_000750_000774</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="157472">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18078</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10583" public="1" featured="0">
    <fileContainer>
      <file fileId="9643">
        <src>https://digitalprojects.uah.edu/files/original/20/10583/satstasIIjul71961min_031307092529.pdf</src>
        <authentication>9c4f9f2166f47fe2b5df4afe06e61335</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="159671">
                <text>satstasIIjul71961min_031307092529.pdf</text>
              </elementText>
              <elementText elementTextId="159672">
                <text>spc_stnv_000695</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159673">
                <text>"Saturn stages S-II : July 7, 1961 : Minutes of the phase II pre-proposal conference for stage S-II procurement."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159674">
                <text>Transcription of a confrence aiming to propose ideas for new rocket designs. Includes references to slides.</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="159675">
                <text>1961-07-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="159676">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159677">
                <text>Saturn stages</text>
              </elementText>
              <elementText elementTextId="159678">
                <text>Saturn S-2 stage</text>
              </elementText>
              <elementText elementTextId="159679">
                <text>Saturn S-4 stage</text>
              </elementText>
              <elementText elementTextId="159680">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159681">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="159682">
                <text>Presentations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="159683">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210347">
                <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="159685">
                <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="159686">
                <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="159687">
                <text>spc_stnv_000675_000699</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11097" public="1" featured="0">
    <fileContainer>
      <file fileId="9782">
        <src>https://digitalprojects.uah.edu/files/original/20/11097/Satusyststud.pdf</src>
        <authentication>2bb900b88002ede944f200bb13b2f7f2</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="169968">
                <text>Satusyststud.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169969">
                <text>"Saturn system study II."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169970">
                <text>Study regarding the three-stage carrier vehicle E-1 engines.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169971">
                <text>United States. Army Ballistic Missile Agency. Development Operations 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="169972">
                <text>1959-11-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="169973">
                <text>1950-1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169974">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="169975">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="169976">
                <text>Saturn stages</text>
              </elementText>
              <elementText elementTextId="169977">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169978">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="169979">
                <text>Essays</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="169980">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="169981">
                <text>Box 4, Folder 24</text>
              </elementText>
              <elementText elementTextId="210788">
                <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="169983">
                <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="169984">
                <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="169985">
                <text>spc_stnv_000750_000774</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="169986">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16591</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11104" public="1" featured="0">
    <fileContainer>
      <file fileId="9775">
        <src>https://digitalprojects.uah.edu/files/original/20/11104/Sa-203.pdf.pdf</src>
        <authentication>2f23877357766caa4afb305cfc714dea</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="170107">
                <text>Sa-203.pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170108">
                <text>"Saturn technical information handbook.  Volume III of four volumes : SA-203."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170109">
                <text>The "Saturn Technical Information Handbook" provides up-to-date reference material to the Launch Operations Center personnel. This material shows the assembly and operation of the Saturn Vehicle components for systems analysis.;  Volume II is available on the NASA Technical Reports Server (NTRS) as a PDF.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170110">
                <text>Technical Writing and Handbook Section</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="170111">
                <text>1960-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="170112">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170113">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="170114">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170115">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="170116">
                <text>Manuals</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="170117">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="170118">
                <text>Box 17, Folder 11</text>
              </elementText>
              <elementText elementTextId="210795">
                <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="170120">
                <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="170121">
                <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="170122">
                <text>spc_stnv_000675_000699</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="170123">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17434</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10472" public="1" featured="0">
    <fileContainer>
      <file fileId="9145">
        <src>https://digitalprojects.uah.edu/files/original/20/10472/satutelesystforSA-6_032207094948.pdf</src>
        <authentication>56cbebd2298e6994c8686e71fdf2a651</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="157473">
                <text>satutelesystforSA-6_032207094948.pdf</text>
              </elementText>
              <elementText elementTextId="157474">
                <text>spc_stnv_000754</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157475">
                <text>"Saturn television system for SA-6."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157476">
                <text>The Saturn television system is an instrumentation device intended to provide visual information on vehicle performance in real time. The system covers the entire problem from the original image presented to the television camera to the presentation of the finished photographs for analyses.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157477">
                <text>Huggins, Carl 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="157478">
                <text>1963-02-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157479">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157480">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157481">
                <text>Saturn launch vehicle</text>
              </elementText>
              <elementText elementTextId="157482">
                <text>Television</text>
              </elementText>
              <elementText elementTextId="157483">
                <text>Spacecraft electronic equipment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157484">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157485">
                <text>Internal Notes</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="157486">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157487">
                <text>Box 8, Folder 14</text>
              </elementText>
              <elementText elementTextId="210260">
                <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="157489">
                <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="157490">
                <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="157491">
                <text>spc_stnv_000750_000774</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="157492">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17311</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10490" public="1" featured="0">
    <fileContainer>
      <file fileId="9134">
        <src>https://digitalprojects.uah.edu/files/original/20/10490/SatVnsproclauvehgrosuppequip_042108143716.pdf</src>
        <authentication>ba5bcfe3e47376e2347d5a395f8d694b</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="157827">
                <text>SatVnsproclauvehgrosuppequip_042108143716.pdf</text>
              </elementText>
              <elementText elementTextId="157828">
                <text>spc_stnv_000772</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157829">
                <text>"Saturn V : non-stage procured launch vehicle ground support equipment."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157830">
                <text>The functions, authority, management relationships, and responsibilities of the Launch Vehicle Ground Support Equipment Project Office are described. Functions and examples of non-stage procured Launch Vehicle Ground Support Equipment (LVGSE) are described and illustrated.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157831">
                <text>George C. Marshall Space Flight Center. Vehicle Ground Support, Equipment Project Office</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="157832">
                <text>1967-08-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157833">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157834">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157835">
                <text>Ground support systems</text>
              </elementText>
              <elementText elementTextId="157836">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157837">
                <text>Ground support equipment</text>
              </elementText>
              <elementText elementTextId="157838">
                <text>Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157839">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157840">
                <text>Design 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="157841">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157842">
                <text>Box 23, Folder 30</text>
              </elementText>
              <elementText elementTextId="210277">
                <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="157844">
                <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="157845">
                <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="157846">
                <text>spc_stnv_000750_000774</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="157847">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17720</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10486" public="1" featured="0">
    <fileContainer>
      <file fileId="9137">
        <src>https://digitalprojects.uah.edu/files/original/20/10486/satvamemooroc_013008120434.pdf</src>
        <authentication>f2df90757d333786a613f13cdb84c7e6</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="157747">
                <text>satvamemooroc_013008120434.pdf</text>
              </elementText>
              <elementText elementTextId="157748">
                <text>spc_stnv_000768</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157749">
                <text>"Saturn V America's moon rocket."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157750">
                <text>Diagram that displays the Saturn V rocket with a page beneath detailing the function of each stage.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157751">
                <text>George C. Marshall Space Flight Center.  National Aeronautics &amp; Space Administration</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157752">
                <text>1967-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157753">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157754">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157755">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="157756">
                <text>Space flight to the moon</text>
              </elementText>
              <elementText elementTextId="157757">
                <text>Manned space flight</text>
              </elementText>
              <elementText elementTextId="157758">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157759">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="157760">
                <text>Diagrams</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="157761">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157762">
                <text>Box 20, Folder 5</text>
              </elementText>
              <elementText elementTextId="210273">
                <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="157764">
                <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="157765">
                <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="157766">
                <text>spc_stnv_000750_000774</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="157767">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17588</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="907" public="1" featured="0">
    <fileContainer>
      <file fileId="748">
        <src>https://digitalprojects.uah.edu/files/original/20/907/spc_stnv_000010.pdf</src>
        <authentication>10ac3b82dac2dd680af8b5ecb2d1e5dd</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177173">
                    <text>�</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="16548">
                <text>spc_stnv_000010</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16549">
                <text>"Saturn V Apollo Flight Configuration."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16550">
                <text>Drawn by Don Sprague at the Huntsville Engineering section of Boeing.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16551">
                <text>Boeing Aerospace Company. Space Division. Launch Systems Branch </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="16552">
                <text>1967-03-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="16553">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16554">
                <text>Project Apollo (U.S.)</text>
              </elementText>
              <elementText elementTextId="16555">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="16556">
                <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="16557">
                <text>Diagrams</text>
              </elementText>
              <elementText elementTextId="16558">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="16559">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="205710">
                <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="16561">
                <text>This item was digitized for the Apollo 11 50th anniversary celebration.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16562">
                <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="16563">
                <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="16564">
                <text>ap11_exhibit_2019_08</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10487" public="1" featured="0">
    <fileContainer>
      <file fileId="9135">
        <src>https://digitalprojects.uah.edu/files/original/20/10487/satvapoflicon_060508122521.pdf</src>
        <authentication>a94d2316bfab4e7dc611af8084120488</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="157768">
                <text>satvapoflicon_060508122521.pdf</text>
              </elementText>
              <elementText elementTextId="157769">
                <text>spc_stnv_000769</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157770">
                <text>"Saturn V Apollo flight configuration."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157771">
                <text>Diagram displaying the internal rooms, pieces and functions of the Saturn V as well as the space-suits of the astronauts.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157772">
                <text>Huntsville Engineering</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="157773">
                <text>1968-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157774">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157775">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157776">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="157777">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157778">
                <text>Space suits</text>
              </elementText>
              <elementText elementTextId="157779">
                <text>Saturn launch vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157780">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="157781">
                <text>Diagrams</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="157782">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210274">
                <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="157784">
                <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="157785">
                <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="157786">
                <text>spc_stnv_000750_000774</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="157787">
                <text>http://libarchstor.uah.edu:8081/search?utf8=%E2%9C%93&amp;op%5B%5D=&amp;q%5B%5D=Saturn+V+Apollo+flight+configuration&amp;limit=&amp;field%5B%5D=&amp;from_year%5B%5D=&amp;to_year%5B%5D=&amp;commit=Search</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10488" public="1" featured="0">
    <fileContainer>
      <file fileId="9136">
        <src>https://digitalprojects.uah.edu/files/original/20/10488/satvapollunorbitrend_050807104721.pdf</src>
        <authentication>581a71addaf6520a34710d85d773fc7d</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="157788">
                <text>satvapollunorbitrend_050807104721.pdf</text>
              </elementText>
              <elementText elementTextId="157789">
                <text>spc_stnv_000770</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157790">
                <text>"Saturn V Apollo lunar orbit rendezvous mission."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157791">
                <text>Diagram explaining the process of a lunar mission from liftoff to recovery.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157792">
                <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="157793">
                <text>1963-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157794">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157795">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157796">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="157797">
                <text>Saturn stages</text>
              </elementText>
              <elementText elementTextId="157798">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157799">
                <text>Space flight to the moon</text>
              </elementText>
              <elementText elementTextId="157800">
                <text>Orbital rendezvous</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157801">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="157802">
                <text>Diagrams</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="157803">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157804">
                <text>Box 9, Folder 30</text>
              </elementText>
              <elementText elementTextId="210275">
                <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="157806">
                <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="157807">
                <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="157808">
                <text>spc_stnv_000750_000774</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="157809">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16857</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10473" public="1" featured="0">
    <fileContainer>
      <file fileId="9660">
        <src>https://digitalprojects.uah.edu/files/original/20/10473/SatuVDeri_062308104520.pdf</src>
        <authentication>65e8a00304464fbdf8d8a8d8c4a9ff96</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="157493">
                <text>SatuVDeri_062308104520.pdf</text>
              </elementText>
              <elementText elementTextId="157494">
                <text>spc_stnv_000755</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157495">
                <text>"Saturn V derivatives."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157496">
                <text>This paper desciibes an evolutionary family concept of !h turn V derivative launch vehicle systems, discusses their performance capabilities, and outlines their ability to perform orbital and hlgh-energy missions at minimum total program cost.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157497">
                <text>Scott, Ronald D.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157498">
                <text>1965-02-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157499">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157500">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157501">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157502">
                <text>Saturn V launch vehicles</text>
              </elementText>
              <elementText elementTextId="157503">
                <text>Technology</text>
              </elementText>
              <elementText elementTextId="157504">
                <text>Research and development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157505">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157506">
                <text>Essays</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="157507">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157508">
                <text>Box 25, Folder 10</text>
              </elementText>
              <elementText elementTextId="210261">
                <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="157510">
                <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="157511">
                <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="157512">
                <text>spc_stnv_000750_000774</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="157513">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17818</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10474" public="1" featured="0">
    <fileContainer>
      <file fileId="9659">
        <src>https://digitalprojects.uah.edu/files/original/20/10474/satuVfirsstagannuprogrepofiscyear1966_091207124644.pdf</src>
        <authentication>7d805789537ed2ae46a5e5185e7ba4fc</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="157514">
                <text>Satuvfirststag.pdf</text>
              </elementText>
              <elementText elementTextId="157515">
                <text>spc_stnv_000756</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157516">
                <text>"Saturn V first stage annual progress report : fiscal year 1966."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157517">
                <text>This report is the consolidation of D5-11994, "Quarterly Technical Progress Report," for the fourth fiscal quarter and the fiscal year 1966 Annual Progress Report and places special emphasis on activities on the fourth fiscal quarter.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157518">
                <text>Boeing Company. Space Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157519">
                <text>1966-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="157520">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157521">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="157522">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="157523">
                <text>Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157524">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="157525">
                <text>Progress Reports</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="157526">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="157527">
                <text>Box 18, Folder 1</text>
              </elementText>
              <elementText elementTextId="210262">
                <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="157529">
                <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="157530">
                <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="157531">
                <text>spc_stnv_000750_000774</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="157532">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17496</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1150" public="1" featured="0">
    <fileContainer>
      <file fileId="997">
        <src>https://digitalprojects.uah.edu/files/original/20/1150/spc_stnv_000066.pdf</src>
        <authentication>dc89991be249aab5abf4e1bf6256528d</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177284">
                    <text>THE

COMP)IIYY/SPCE

DIYISION,~AUNCH SYSTEMS BRANCH

�ANNUAL PROGRESS REPORT

J U N E 30, 1967 THROUGH J U N E 27, 1 9 6 8
CONTRACT N A S 8 - 5 6 0 8 , SCHEDULES 1 A N D 1A
J U L Y 27, 1 9 6 8

LAUNCH SYSTEMS B R A N C H
SPACE D I V I S I O N
T H E BOEllUO C O M P A N Y

PREPARED BY

SUPERVISED BY

D.6. Valentine
M a n a w m R w m g and Analysis

APPROVED BY

APPROVED BY

Illlichawl Pmgram Warning
and Reporting Manager

APPROVED BY

�DISTRIBUTION
M, L. Alberstadf., Jrr

1

L, D, Alford
J* F, Allan
W. R. Allen
We C, Applegate
N. Bender
S. Bergeman
L, E. Buchart

*

L, G, Chchraa
F. L, Csenen
E. IG Cooper
D. H. Creim
R. T. Crowley
W. W. Davis
C. H. Donald
Re C. Dunigan
J. J. Eckle
C, E. E n a f t
A, A. Geiger
H. D. Gunning
D. 0. Haas
C, W. Harris
K i S. ingram
J. Irico
I, A. Johnson
S. P. Johnson
H. Kudish
S. D. KruU
T. R. Marley
A. D. Martin
C. L. M c h t i r e
E. J. Merkel
T. M. Mladfneo *
J. D. Monroe
R. H. Nelson
J. L. O1Neil
B, L. Osborne
J. E. Parazynsld
W, H. Quarles
H. C. Runkel
I%, C, Sanders
J. V. Smith
T. J. Smith
H. L. Smotherman
T. P. Snow

C. J. Solar
J, C. Sormsw

D5-12601-6

I

1-1855
5-9000
5-1830
5-3100
5-1800
5-1100
5-1660
5-1910
5-1500
6-8000
5-1900
5-1200
5-7300
5-7900
5-1705
5-1070
5-7400
5-7150
5-8010
5-1070
5-1854
5-3000
5-1910
5-1300
5-1211
5-7200
5-1600
5-5000
5-3200
5-1700
5-1230
5-1230
5-1800
5-1400
5-1000
5-3600
5-1100
5-1430
5- 1940
5-7000
5-1010
5-1020
5-1260
5-9100

LA-42
JA-51
LN-70
LA-35
LA-02
LT-90
LR-69
LD-42
LR-60

FA44
LD-42
LA-19
LS-72
LS-55
LC-23
LA-42
LS-76
LS-23
FA-14
LA-42
LN-54
LA-10
LD-33
LT-43
LT-91
LP-36
LR-65
TA-01
LA-03
LA-23
LD-03
LT-92
LA-02
LN-98
LA-42
LA-18
JB-75
LN-87
JD-2 1
LS-40
LA-42
LA-31
LT-96
JD-5 1

2-5907 Sahara Park
5-1100
LT-90
5-7100
L9-28

R. L, Stallings
G, H, Stoner (2)
C, D. &amp; C O U ~
R. F. T e ~ r y
D, G. Valentiue (10)
J. G. Weber
C. W. Weteel
C, A. WlIWnson
L, A. Wood
L, Yanolf
Michoud Contracts
Files
Facilities Central
Files
Program Presentations
Library (2)

J. Keller

5-5240
5-1000
5-1300
5-1220
5-1220
5-1020
5-1100
5-2000
2-1000
5-1020

TA-03
84-22
LT-43
LA-2 1
LD-59
JB-33
LT-90
RS-O 1
1448
JB-33

5-1100

LT-90

5-1492

LN-95

5-1220

LP-02

1200 Cornmonwedth Bldg,
1625 K. Street, N. W,
Washington, D. C. 20006

R. W, Brown
M. E. Buchholz
A. V. Clark
H. S. Garrett
J. E. Glazner
H, W. Hallisey (2)
C. W. Holmes
F. W. Johnson
T. S. Johnston
L. L. Jones
J. R. King
H. T. Mimey
J. W. Moody
D. H. Newby
W, R. Reynolds
M. H. Riley
C, L. Thionnet
J. B, Taylor

R-QUAL-J
I-CO-LH
R-P&amp;VE-XG
MS-D
R-QUAL-AE
I-V-S-IC
R-OM-V
I-V-T
I-V-P
MS-H
R-ASTR-BV
I-CO-LB
I-V-Q
DE P-A
R-QUAL-QP
R-QUAL-PC
R-AERO-P
I-K-V

NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA
NASA

B. H.
W. M.
G. N,
W, B.

I-MICH-C
I-MICW-F
I-MICH-MGR
I-MICH-QES
I-MICH-OB
I-MICH-DU
11-MICH-QR

NASA
NASA
NASA
NASA
NASA
NASA
NASA

Aldridge
Bailey
Constm
Herrhgbn
R, J, Nuber
S, Smith
W, L, WiW.ms

iii

�Summary
Michoud Assembly Facility
Mississippi Teet Facility;

Page No,

iii
iv

DBTRXBUTION
CONTENTS
ILLUSTXUTIOSS
FOREWORD
S-IC PfiOCRAM SUMMARY

c

1

,.,

0

'

Summary
Documentation Support
Spares Support
Personnel Support
Spares for Government
Furnished Equipment

1
3
4
8
9

9
10
10
10
10
15
18
19

5
6

-

23
25
30
54
57
63
66
66

81

LAUNCH OPERATIONS
Launch Operations
S-IC-3 Quality Verification

7

79
81
81
81

STAGE SYSTEMS STUDIES

89
89

ADVANCED STUDIES

APPENDIXES
Appendix A
Appendix B
Appendix C
Appendix D

- Contract Modifications

- Proposals Submitted
- Negotiations Completed

- Deliverable Data
Submitted
Appendix E - Engineering Change

CONTRACT END ITEMS AND
SERVICES
Summary
Deliverable Hardware
Design and Engineering
Manufacturing Development
Quality Assurance
Product Performance Assurance
New Technology
Deliverable Data

Q

LOGISTICS

4

vf
vii

PROJECT MANAGEMENT
Summary
Contracting Activity
Program Plans, Schedules and
Reports
Equipment Management
Configuration Management
Technical Program Analysis and
Review
Cost Effectiveness Program
Cost Improvement
Motivation
Industrial Management
Computer Sciences
Business Information Services
Michoud Organization Realignmen&amp;

2

v

69
71
73

Appendix G Appendix F

GLOSSARY

Documentation Completed
During FY 1968
Engineering Changes
Initiated During FY 1968
MTF Systems Test
Documentation Status

97
97
97
97

98
105
118
120

�ILLUSTRATIONS
Page No.
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 2-9
Figure 2-10
Figure 2-11
Figure 2-12
Figure 2-13
Figure 2-14
Figure 2-15
Figure 2-16
Figure 2-17
Figure 2-18
Figure 2-19
Figure 2-20
Figure 2-21
Figure 2-22
Figure 2-23
Figure 2-24
Figure2-25
Figure2-26
Figure 2-27
Figure 2-28
Figure 3-1
Figure3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 3-7

D5-128016

Michoud Program Control Center
R e p o m d Xnjuriaa in FY 1968
FY 1968 Injuries P e r Million Manhours MTF
Document Activity During FY 1968
AS-501 Moving From KSC VAB
AS-501 Launch
S-fC -F LUX Duct Removal
LOX Duct Installed in POGO Test F i x b e
S-PC Stage Being Moved From Factory
S-IC-7 Stored in Factory Building
S-IC-8 in Vertical Assembly
S-IC-8 Being Removed From VAB
F-1 Engine Installation in S-IC
6-IC Propellant Tank Being Moved From Factory
Percentage Complete Major Structures June 27, 1968
S-IC-3 Versus -2 Dry Weight Status
Breakdown of S-IC Stage Weights
S-IC Power Distribution System
LOX Fill and Drain Valve Redesign
S-IC Propellant Dispersion System
Center Engine Redundant LOX Cutoff Sensor
S-IC TV System
S-IC Film Camera Capsule Assembly
S-IC ODOP System
S-IC Qualification Test Summary
Growth of Assessed Reliability S-IC Stage
S-IC Repair Weld Frequency
Quality Audits
S-ICRiskAppraisalCycle
S-ICQualityMaintenanceProgram
Organizational Safety Relationship
~htegratedSafety Program Controlling Documentation
Cincinatti Automatic Tooling Center
S-IC-5inTestStand
S-IC-5 Static Firing
S-IC-5 Being Removed From T e s t Stand
Couapsed S-IC-6 Fuel Emergency Drain Duct
Instalfation d 8-IC-D in T e s t Stand
Plexighs Ducts Installed on S-I[C-33

-

-

-

-

6
11
13
20
25
25
26
26
27
27
28
28
28
29
29
30
32
33
34
35
36
40
41
42
48
54
55
60

64
65
65
65
71
73
73
73
74
75
75

v

��F Y 1968 several major Saturn&amp;-IC program milestones, whichwere of utmost importthe ApoUo program's mission of placing men on the moon, were achieved. The most
icant milestones reached were the successful launchings of the first and second Apollol
V vehicles, AS 4 0 1 and -502, from the Kennedy Space Flight Center, The AS-501 wate
ed from K e m d y Space Flight Center at ?:QQ!O1 a, m. , EST, on Navember 9, 1888.
-1C-1 and its Boeing Schedule I supplied ground support equipment performed exceedwell during launch and flight. AS-502 lift-off occurred at Kennedy Space Flight Center
t 7:00:01, on April 4 , 1968. Performance of all systems on the S-IC-2 and its Boeing
Schedule f supplied ground support equipment was satisfactory during launch and flight. However, longitudinaf oscillations (POCO)were experienced during flight. Boeing is expending
every effort to alaviate thfe phenomenon in all future S-IC fights.
Subsequent to the launch of AS-501 and -502, the decision to make AS-503 the first manned
aturn V mission was reached. The first stage for this mission, the S-IC-3, is the
Michoud assembled S-IC flight stage. This vehicle was accepted by NASA during F Y
and then placed in storage at Michoud. It was later removed from storage, retested,
shipped to Kennedy Space Flight Center, arriving there on December 27, 1967. At the
s e of the reporting period, the S-IC-3 was at Kennedy Space Flight Center where it is
ergoing extensive modification in preparation for the first manned launch.
Other significant S-IC program incentive milestones achieved during 1968 include delivery of
he 5-IC-4 to the Customer, on-dock Michoud, on August 28, 1967; successful static firing
of the S-IC-5 at the M ississfppi Test Facility on August 25, 1967; and successful completion
of the S-IC-6 and -7 post-manufacturing static firing readiness tests on July 24 and N o v e d e r
12, 1967, respectively.
oeing/'Michoud testing programs were conducted throughout the year with the purpose of
resolving design data problems, discrepancies, and anomalies identified during manufacturng , static firing, and AS-5 01 and -502 launch support operatiom. Major testing programs
hat were conducted on a continuing basis included the reliability, qualification, development,
and failure analysis test programs.
Project management techniques, designed to assure efficient and effective management of the
S-IC program, were under constant surveillance throughout FY 1968. An S-IC Integrated
Safety Program, which is responsive to both Boeing Corporate policies and NASA requirements ,-was established during October of 1967. This program combines and integrates the
previously separate industrial and systems safety plans into one overall safety program, and
is overseen by the S-IC Safety Board that meets on a regular basis to provide program direction. This arrangement provides for a single safety focal point for increased Management
control and improved visibility of safety performance versus assigned tasks, thereby assuring safety excellence in all phases of the S-IC program.

t

Throughout FY 1968 management reviews, concerning all aspects of the S-IC program, were
conducted. Among these reviews were the three contractually required S-IC Technical Progress and Program Reviews that were conducted to inform NASA personnel of Boeing's progress and performance on Contract NAS8-5608. Internal Boeing Management reviews during
the year included periodic meetings of the Saturn Performance and Saturn Launch Readiness
Boards. These Boards are made up of Boeing executives from affected Boeing/Saturn programs and have as their mission assurance of proper performance of all Saturn contractual
obligations.
Personnel reassignments and organizational restructuring continued throughout the year with
the purpose of assuring effective management of the S-EC program. Of major significance
was the relocation -of the Baeing S-IC Systems Test eanagerts office from Michoud to the
Mississippi Test Fwility. This relocation was made to enhance the coordination between
Boeing Manageme* ar$ W NASA Missiesippi Test Facility Management.

DS-12601-5

vii

��b

SUMMARY
Project Management activities during the year were
directed toward managing the S-IC program to assure
optimum utilization of resources and the attainment
of sfa;nliic&amp; Bllllestones including ail contractudly
roquLPed obUgstiolup.
During BY 1968 long-lead procurement for stages S1C-16 aod -17 was initiated under Contract NASB19644. This contract was executed on July 25, 1967,
Urnfaate$ 3 the convrraienca, of *.he g o v e m e n t an
Octotrer 18, 1967, and rs-at@ld an Mmoh 8, 1968.
Because S-IC stages were being produced at a greater
rate than they could be effectively utilized, revised
program schedules and guidelines were received during the year, Boeing agreed to these revisions subject to an equitable adjustment to the Contract, and
on November 13, 1967 Supplement Agreement 1MICH662 formally placed the Apollo Program 4.H schedule
on contract. Negotiation of MICH-662 began on June
17, 1968 arid was continuing at the end of the reporthg mria, aft,J w 14, ti368 S ~ p g t b ~~ sg !n~v ~UId Apallo Pram= 43
meat. 977, wkfch c
Schedule, was received from NASA. Negotiation of
this new schedule wLU begin "immediately following"
completion of MLCH-662 negotiations,

The Michoud Cost Effectiveness Program was established during the reporting period. Activities under
this program are directed toward identifying, evaluating, i~ndimplementing ckangea that reduce t;he
total cost of the S 4 C stage and derivatives. The
Michoud Cost Improvement program also continued
to operate effectively throughout the year with a
reported validated cost savings of $14,200,788 as
compared to a goal of $9,585,740.

The Boefngmfofisud work; foroca u d e m e n t adljusrtments during this fiscal year to compensate for the
reduction in activity resulting from schedule slides.
The work force reporting to the Boeing/Rlichoud
manager was reduced by 833 which resulted in a
total workforce of 4254 at the end of the fiscal year.
Various Boeing/Michoud personnel were also placed
on loan to alleviate manpower problems at other
Boeing Saturn locations,
Efforts were made to assure that Plans for Progress
and Equal Employment Opportunityprograms continued during the repnrtiw prlod. Ao a part d %&amp; g ~ e parrn an Equal Employment Opportunity Adminiskation function and aa Equal Employment Opportunity
Committee were established to promote equal
wPOm@*

*

D5412601-5

1

�CONTRACTING ACTIVITY
CONTRACT DELIVERY SCHEDULE
During 1967, it became increasingly apparent that

S-IC stages were being produced at a rate greater
than the ApoUo Program could effectively utillse.
On SeptemSer 1, the NASA Contracting Officer gave
official recognition to this fact by a letter requesting
immediate implementation of certain "revised program gutdeliine8." On September 12, Boeing agreed
to proceed with a revised plan subject to an equitable
odjatment of the contract. an November 13, Supplemental Agreement FA) MICH-662 formally placed
the new 4H Schedule on contract.

the Saturn S-IC program. The requirements for such
equipment are established by program needs and submitted to the government in the form of a fiscal year
plan. The forecast is negotiated and the necessary
level of funding is placed on contract. During FY 1968,
funding of the facilities contract was increased in the
amount of $930,000.
CONTRACT MASS-5608 (SCHEDULES I &amp; AND IA)

During this reporting period, the following schedule
and performance incentive milestones were accompll~bedunder Srihedule I of the constract:
July 24, 1967

Successful completion of the
S-IC -6 stage post-manufacturing
static firing readiness test for
full (299.6) incentive points

O n June 17, 1968, negotiation of the 4H Schedule (SA
MICH-662) was initiated based on cost proposals submitted in February and March 1968. Both parties have
agreed to negotiate the further impact of SA 777
"immediately following' the conclusion of the SA
MICH-662 negotiation.

August 25, 1967

Successful static firing of the
S-IC-5 stage for maximum (260)
incentive points

August 28, 1967

Acceptance by the Government of
the S-IC-4 stage for 3494.6 out of
a possible 3498.6 incentive points

NASA PROCUREMENT REORGANIZATION

For the above milestones, a total of 4,054.2 of a possible 4,058.2 incentive points were earned.

In early 1968, informal conversations with NASA/
Michoud contracting personnel indicated that the procurement function for S-IC stages would be moved to
MSFC in Huntsville, Alabama. This was done on April
1, 1968. A s a result, Boeinghlichoud Contracts has
established and staffed the "Huntsville Representative"
office to maintain li*$son with the NASA procurement
function. The transition has been made without major
perturbations, and it is believed that, other than the increased travel by Boeinghlichoud Contracts personnel,
no impact will result.

November 13,1967 Successful completion of the
S-IC -7 stage post-manufacturing static firing readiness test
for maximum incentive points.
The incentive points earned on
this milestone a r e being held in
abeyance pending revision of
contract schedules and incentive
arrangements in accordance with
SA MICH-662.

A further schedule slide identified as 41 was contractually implemented by SA 777 on June 14, 1968.

CONTRACT NAS8-5608 (SCHEDULE 8 )

CONTRACT NlANAGEMENT
CONTRACT NAS8-2577

I n a letter dated February 1, 1968, NASA formally
acknowledged accompii8hment of the performance requirements and administrative actions necessary to
close out this contract. F M payment was received
on F e b r u a y 5, 1968.
CONTRACT NAS8-5606(F).

This contract covers special facilities equipment for

05-1260 1-5

On February 15, 1968, Schedule IB to Contract NAS85608 was established for the purpose of providing documentation, modification kits, and parts to support the
S-IC-T stage and the Systems Development Facility
Mechanical Automation Breadboard (MAB. The new
schedule was fully funded in the amount of $170,000.
CONTRACT NAS8-17218

The technical work statement has been completed.
To effect contract closeout, letters of cerfification
and dher eoidence of contract completion are be-

�ing provided to the Contracting Officer.
CONTRACT NAS8-19528

The technical work statement has been completed. In
order to effect contract closeout, letters of certification and other evidence of contract completion a r e being provided to the Contracting Officer.
CONTRACT fU&amp;8-19544

"

TNs contmct for the procurement of long-lead items
for owgee $-IC-16 ssd -17 was e x e c ~ t e don July 21,
1967. Nottce af TerminaUon fsr the conv@ntanc@
sf
the Government was received from NASA on October
16, 1967. A 11 organizations, including Seattle and
Wichita , reported work stopped within the required
five-day period. On February 21, 1968, Boeing was
informed that NASA Headquarters had approved reactivation of Contract NAS8-19544, SA No. 2 , received (fully executed) on March 8,1968, officially reinstated
the contract. This SA provided for:
a)

Cancellation of the Notice of Termination;

b)

Reinstatement of the long-lead effort previously
authorized by the contract;

c)

Adjustment of the contemplated delivery dates
for stages S-IC-16 and -17 to July 1, 1971, and
January 1, 1972, respectively; and

d)

Extension of long-lead effort through July 31,1968,
with provisions for negotiation of a monthly extension toMarch 31, 1969.

CONTRACT ACTIVITY fY 1968~

A summary of contract modifications, proposal^ submitt&amp;, negotiations completed, and deliverable data
submitted a r e s e t forth in Appendices A , B C and

PROGRAM PLANS,
SCHEDULES AND REPORTS
PROGRAM SCHEDULES
Document D5-11040-5, "Launch Systems Branch S-IC
Project Contractual Schedules," superseded D5-110404 and was published during the previous reporting
period (June 13, 1967). This document outlines the
LSB S-EC project eontract schedule for stages 8-IC-3
through -15 a s set forth in CPIF Contract NAS&amp;*5&amp;08

(Schedule I and IA), and S-IC Stage Development and
Delivery Plan, MA -2 Schedule, Plan VQIA , which is
published by the NASA/MSFC S-IC Project Office.
This schedule data establishes the contractual parameters for development of LSB S-IC Plan VIIIA Internal
Working Schedules. During FY 1968, one revision
was made to D5-11040-5. This revision adjusted contract schedule milestones on S-IC-3, S-IC-5, S-IC-6,
and S-IC-7 as directed by the customer and added the
period of performance for procurement of long-lead
items authorized by CPIF Contract NAS8-19544 for
S-IC-16 and -17.
Document DS-12695, "8-IC P ~ o g r m
Reporting Milestones ," identifies and provides schedule dates for
the S-IC program milestones used by Boeing in reporting the progress of Contract NAS8-5608, Schedules I and IA , to MSFC. The milestones s e t forth in
this document were established through mutual agreement between Boeing and MSFC to establish a common reporting baseline by which program progress
could be measured. Revision "L" to D5-12535, released October 31, 1967, (1)incorporated a revised
format, (2) added reference milestones for MSFC
produced stages (S-IC -T , S-IC -1, and S -1C -2) and
the dynamic test stage (S-IC-D) , (3) added reporting
milestones for stages S-IC-11 through -15, and (4)
deleted reliability and logistics program reporting
milestones. In accordance with revised reporting
frequency from "as required" to "once every two
months ," three additional revisions, "M ," "Nl1 &amp; "0,
It
were prepared and released on December 2 1, 1967,
February 28, 1968, and April 22, 1968, respectively.
Revision "M" and "0" incorporated minor schedule
revisions and added actual completion dates for closed
out milestones. Revision "N" implemented a completely revised interim schedule, in lieu of a negotiated contract schedule, based on required on-dock
Michoud delivery dates contained in Supplemental
Agreement MICH-662. Revision "P" is presently
being prepared and is scheduled for release during
July 1968. This revision will update the interim
schedule to be compatible with the internal working
schedule released ~ u n e17, 1968.

,.

~5-1.3595, .S-IC ,urn- round Equipment Schedules
serves a s an instrument of agreement between MSFC
and Boeing on the requirements for and utilization of
turn-around equipment a t the Michoud Assembly Facility, Mississippi Test Facility, Marshall Space Flight
Center, and Kennedy Space Center. Turn-around
equipment,is defined a s those major items of equipment, regardless of complexity, that a r e reused in
the assembly, handling, testing, and tramporting of
S=-IC stages, Revisions "C" and "I)" to this document
were released July 31, 1967 and Maroh 6 , 1968, re-

�sptlctively. Both were complete revisions realigning turn-around equipment utilization requiremenis k, be compatible with revised stage internal
working schedules,
LSD S-IC Internnl Wqrking Schedules, released by
Program Letter through tho 8-1;C Program Executivets
office, are fssued to establfsh real-time schedule
milestones and organizational work interfaces to ensure stage production and test continuity. Three revised working sehedules (schedule No. 's 103, 104,
and an interim schedule pending negotiation of a posrlbtr! eehocluic No, 106) ware! reIeased during this raporting pe~lod, Working f3ekedtile Na. 109 was relensed, July 3, 1967, to reflect revised end-item delivery requirements for S-IC-5 and -6 and adjusted
schedule dates for completion of PMC for S-IC-7 in
accordance with negotiated schedule changes. Working Schedule No, 104 was issued January 5, 1968 to
reflect internal schedule realignment necessary to
eupport the revised delivery requirements for stages
S-IC-3 through -14, which were contained in Supplemental Agreement MICH-662. Arm interim working
schedule was published May 28, 1968 to provide transitory schedule direction pending negotiation of a revised delivery schedule. MICH-662 delivery requiren e n t s were invalidated by customer issuance of stop
work orders on S-IC-5 and -6.

PROJECT PLkN
Document D5-11960, Revision D , 'IS-IC Stage Project
Management Plan," published in June 1967, presents
a sununary view of the organization, planning, and
methods used by the Boeing Launch Systems Branch
t o provide the most effective means of completing the
S-IC project within the schedule and cost g o d s established by Contract NAS8-5608, Schedules I and IA,
The contractual requirements for a semi-annual updating of D5-11960, during this reporting period, were
changed to an "as-required" basis by Supplement
Agreement MICH-310.

ings which are held bi-weekly. PERT computer printouts are also forwarded to designated representatives
in each affected organization.
k number of new innovations have been adopted that
reduced the manpower required to support the current
level of reporting effort. The major changes included.
a)

The substitution of Saturn Apollo Reporting Procedure (SARP) charts with a form cover letter
for formal bi-weekly reports to the customer;

b

A $et ~f trend ohart@and a s b z t fel~llf~1e
of major prsbleme, that are displayed in the Status
Display Center (see Management Control Centers , page 6) were adopted instead of a formal
bi-weekly report to Boeing management; and

A computer program was developed to automatically construct logic networla from the
biweekly master PERT tape. These networks, produced for approximately $. 05 each,
provide a graphic image of the computer tape.
This greatly reduces the human e r r o r and
time required to maintain a history of program accomplishments.

MANAGEMENT CONTROL CENTERS
The Boeing Program Controlcenter (PCC) (Figure 1-1)
provides management with current status of S-IC program schedules, events, and items of concern. The
items displayed assist management by depicting the
status in a concise manner for rapid comprehension.
Among the many changes to the PCC which resulted in
increased effectiveness was the installation of ultraviolet lighting during FY 1968. Fluorescent materials
are used along with the lighting for vivid portrayal of
schedules, event sequences, and other items displayed to aid management.
During FY 1968, an area ofthe PCC was devoted toResources Status. Items displayed included manpower,
long-lead procurement and budget status. This coverage of resource items will continue to aid in planfuture program activities.

ning

PROGRAM ASSESSMENT AND
PERT SYSTEM
The Saturn V/S-IC Launch Systems Branch PERT System report presents milestone status measured against
the currently apprwed plan. This report is produced
bi-weekly. Items that a r e behind schedule are identi- .
fied by t&amp;e PERT system and are called to the attention of management thrwgh PERT assessment meet-

The Boeing Status Display Center (SDC) was utilized
in FY 1968 to provide real-time tracking for management visibility of stage and GSE open items prior to
the launch of S-IC-1 and -2. The viewgrkphs displayed in the SM: were also used to provide the latest
S-IC status during the Stage Managerrs Pre-Flight
Reviews, the Program Manages's Pxe-Flight Readiness Reviews, MSFC Pre-Flight Reviews, Launch

�Readiness Reviews, the Apollo FIight Readiness Reviews, Launch Readiness Board meetings, and other
reviews held a t MSFC and BATC The information on
the viewgraphs was also transmitted to BATC to inform them of the latest status of hardware for retrofit
changes. The status of the S-IC-3, -4, and -5 and
associated GSE , MTF , Mechanical Automation Breadboard (MAB) and PERT delinquency status i s currently displayed in the SDC.

.

The Miehoud Morning Report is published daily
to augment the S-IC program information that
i s displayed in We P C P and SDC and to inform
management of the significant events occurring
a t Michoud.

.

The Management Information Center was established
in August 1966 upon completion of the "In-Depth
Analysis" of the Michoud organization. This study
was initiated to provide an assessment of individual
skills and organizational structuring against tasks to
be performed. This data is maintained on a current
basis and displayed in the Management Information
Center= Another important use for this center is the
availability of comprehensive personnel data and
special display material applicable to equal employ- .
ment opportunities. These displays have been reviewed by visiting personnel from the Equal
Employment Opportunities Commission and have
proven fruitful in assuring the commission of
Boeing respo'nsiveness to equal opportunities for
all employees.

6

.

MANAGEMENT' REVIEWS
TECHNICAL PROGRESS AND PROGRAM REVIEWS

Customer requirements for S-IC Quarterly Reviews were
reducedfromfour tothreeberyear inFY 1967. This requirement remained constant for FY 1968. The 18th, 19th,
and 20thS-IC program reviews were conducted inFY 1968.
The 18th Technical Progress and Program Review was
held at Michoud on July 26, 1967 and reviewed the
status of S-IC stages and related activities, particularly S-IC-1 flight readiness. Technical problem r e views covered the need for test data on the characteristics of the Slow Release Mechanism and its effect on
AS-501 l&amp;unch, environmental control system incompatibility, and potential stage and GSE changes.
The 19th Technical Progress and Program Review conducted at Michoud on December 14, 1967 concentrated
on AS -501 (S-IC -1/GSE) prelaunch and flight performance. Anomalies that occurred during prelaunch and
flight were discussed and recommendations were made
for a number of S-IC instrumentation modifications
necessary to obtain technical performance data On subsequent flights. Other problem areas reviewed included configuration differences between S-IC-1 and -2,
qualification tests and certifications remaining and the
reliability test program. The review ended with a discussion on how configuration management might be improved between Boeing and MSFC

.

The 20th Technical Progress and Program Review
was held at Michoud on June 6, 1568. Major items

D5- 121101-5

�covered in the meeting were S-IC-2 Pre-Launch and
Flight Performance, and significant preflight and
flight anomalies, with emphasis on the LOX vent and
relief valve position switch and POGO. Other imporkant items reviewed were S l C - 3 manned eonfiguration c h a m status, S-IC stage distributor rework
plan aad schedule, &amp;st and retest quality verification
program, and a discussion on the pragrammed reduction of critical skills in Engineering and Operations.
SATUW PERFORMANCE AND LAUNCH READINESS BOARD
MEETINGS
As a part of the Boeing p r o p =

tn assure pvoper
performance of all Saturn contractual obligations, the
Saturn Performance and Saturn Launch Readiness
Boanle met periodically throughout F Y 1968. These
boards, the membership of which consists of Boeingexecutives from affected Boeing/Saturn programs,
hsve as their purpose and scope:
a)

sult of these conclusions, the following action items
were assigned to Boeing Schedule I, and these
items have been accomplished to the extent possible
at Ohis time:
1)

Identify failure modes resulting in vehicle
loss and provide the rationale for the acceptability of these risks.

2)

Establish the plan and schedule for the elimination of these critical failure modes in support of the first manned ve-bhle.

3)

Identify the failure modes that result inlamch
scrub o r delay and provide for the elimination of these or the rationale for their acceptance as risks.

,

4)

-

Saturn Performance Board
examine the
activities of The Bueing Company that provide assurance that the Saturn V launch vehicle
will perform in accordance the contract performance requirements and the expectations of
the customer, The Board i~iresponsible for
initiating corrective action as necessary to
assure performance adequacy.

b) Saturn Launch Readiness Board

-

examine the
activities of The Boeing Company leading to the
preparation of a successful launch of each Saturn
V mission. This Board initiates corrective action,
where necessary, to assure the maximum effeeUveness of Boeing's overall participation in the
Saturn V launch program.

The Saturn Performance Board met six times during

b) A pre-launch review of Boeing AS-501 and 502

launch critical problems, assessment of the impact of these problems, and assignment of necessary corrective actions.
c) Identification and assessment of the adequacy of
those activities that represent the unique requirements to qualify Boeing contracted hardware and
test operation for man-rating a specific Saturn
mission, including:
1)

Identfffcation of essential requirements that
must be met to provide confidence in manned
mission success;

2)

Determination if these requirements can be
assured by documented analysis and test; and

3)

Determination if the evidence of accomplishment can be accommodated in the Design
Certification Review written and oral reports.

FU 1968. Some of the topics discussed at these meetings were:
a)

The Board reviewed the design, modification, and
test programs associated with S I C pneumatic
equipment. As a rerult of this seview, the Board
concluded that although this equipment had successY
fully (without significant delay) supported 20 static
firings of the S-IC, it would be required to operate
unattended at KSC for long periods of time (4 to 14
hours) and therefore provided the risk of potential
launch delay as a result of component failure. The
Board further concluded that there were several
failure modes for this equipment that could result
in the loss of a stage at MTF o r a vehicle at KSC,
and that there were many faflure modes that could
result in delaiy a t l m c h scrub at KSC, As a re-

Mentify the action necessary to make MTF
safe, i. e, , so it is not possible to lose the
stage through a failure of this equipment.

During FY 1968 the SaturnLaunchBeadiness Board met
eight times. Discussions at these meetings included:
a) The POGO effect experienced during AS-502 launch

and POGO history, possible suppression systems
and solutions in work.
b) Mscuseion and disposition of AS-501 and -502 prelaunch open-work itemsc
c) A r e a of unsatisfactory or marginal performance

�EQUIPMENT
MANAGEMENT

during the AS-501 flight wcre reviewed with the
purpose of preventing recurrences during launch
of the AS-502.

OTHER MANAGEMENT REVIEWS
hrrfng F Y 1968 Boeing/Michoud orientation and activity reviews were given to many visiting dignitaria.
A synopsis of same of these reviews follows:
B

a) On October 10, 1967 a briefing was conducted for
the Sub-Committee f o r NASA Over-Sight, U. S.
ftourss of Reproeenativee (liesiqucr Committee). At
this revicw, the sub-committee was briefed on trill
Boeing/Sahrn V Apollo activities, including Contract NAS8-5608 schedules I, IA, I1 and Ill, the
Apollo Technical Integration and Evaluation contract (NASW-1650f, and New Technology disclosures, Schedule I and LA participation in this
briefing consisted of a review of CY 1966 and 1967
schedules, costs, and problems and a preview of
anticipated CY 1968 activities. These reviews
brought out the fact that Boeing Schedules I and LA
a r e underrunning estimated costs, and that the
S-IC production program i s well ahead of the contract delivery schedules and Saturn V launch
schedules, thus resulting in the necessity to place
completed o r partially completed stages in storage.
Boeingls transition to this reduced activity and the
resultant decreased manpower needs were also
reviewed for the committee. A review of the complete Boeing presentation to the sub-committee ie
available in the study prepared f o r the Subcommittee on NASA Oversight, entitled "Apollo and
Apollo Applications, I f dated February 26, 1968,

e

b) A short S-IC program briefing was given April 22,
1968 to Dr. Thomas 0. Paine, the then newly
appointed Deputy Administrator for NASA. He was
accompanied by Dr. Wernher von Braun, General
OIConnor, and other NASA representatives. They
were also given a tour of MTF and Michoud (NASA,
Chrysler, and Boeing).

c) On June 6, 1968 a review of the S-IC program
was given by Dr. H. E Newell, Associate
Administrator for NASA. The presentation
explained Boeing's requirements and major rolls
in the Saturn V/ApoUo Program, Boeing Space
Division organization, a general S-IC stage
assembly orientation, and cost performance for
Schedules I and LA. The S-IC stage delivery
schedule and factory utilization were also dis- cussed. Fallowing the presentation, Dr. Newell
was given a plant tour.

.

a

,

During FY 1968, the Equipment Management Organization systematically re-evaluated all of its organizationaf functions and responsibilities to determine if
certain organizational tasks were still required and if
required tasks a r e being accomplished in the most efficbnt manner. Equippent management activities for
the year included:
a)

The "Associated Contractor Liaison Plansffcontract document IN-I-V -S-IC -66-3, equipment
management supplied the Marshall Space Flight
Center with five data deliveries, including weekly inputs on S-IC equipment acceptance testing.
This material will be used in the subject plan;

b)

"Rocketdyne Requests For Boeing S u p p ~ r t con,~~
tract document IN-I-V-S-IC -65 -9-Rocketdyne
requests for Boeing support increased during
the reporting period. Ten Rocketdyne requests
were received and all were processed;

a)

Control of operating agreements-Action was
taken by equipment management to convert all
Boeing Schedule I/Schedule II operating agreements to standard command media. Schedule I /
Schedule IlI operating agreement activity continued during FY 1968. This activity increased
prior to and after the launch of AS-501 and -502.
Schedule I/Schedule ILI operating agreements
were reviewed and updated to correct discrepancies and to cover additional needs that became apparent during launch support. Four
new operating agreements were established;

d)

"Master Equipment List," Document D5-12888Equipment management reviewed requirements
for ground support equipment, manufacturing
support equipment, and all additional equipment.
*
The master equipment list and all associated
documents were revised and updated. The purpose of this review was to determine new equipment requirements and to ensure that all deliv.ered equipment was listed in the document.
The result of this study was to provide an accurate and up-to-date listing of Launch Systems
Branch S-IC equipment Pequiretnents. A n ad-

�ditiond study was made to reduce document
frequency md distribution. A s a result, the
master equipment list and associated document
publications were reduced by 532 per year;

B)

"Covermont Fumshed Property," (GFP)
Document D5-11044-1-TO eliminate duplication that existed due to the publication of two
C FP documents; D5-11044-1 (Boeing, and
IN-I-V-S-IC-66-1 (contractual], the Equipment
Control Board elected to cancel the Boeing CFP
document and rely on IN-I-V-S-IC-66-1 as the
all-inclusive GFP document. This single document now contains all firm, preliminary, and
loaned NAS8-5608 government equipment. During FY 1968, 30 new requests for GFP were reviewed and coordtmted by the Esuivment
Con- trol Board, These requists were coordinated
with NASA and all equipment has been received
by the requesting Boeing organizatiosls. The
control board also processed 24 GFP reallocations during the reporting period; and
Equipment Control Board-All procedures that
define the operation and authority of the Equipment Control Board were reviewed and modernized. One of the objectives of this review was
to assure more effective control and reaction
time on reallocated equipment. A fast reaction
task force was established to accomplish this
objective. Controls were also initiated to follow up on reallocated equipment,

CONFIGURATION
MANAGEMENT
Implementation of Program Directives 44 and 44A, to
certify stages S-IC-1 and -2 and their associated GSE
prior to launch, was accomplished during the year.
Certification of the S-IC and its GSE , as directed by
Program Directive 44.4, was underway at the end of
the fiscal year for a more thorough description of activities required by Program Directives 44 and 4 M ,
see page 66.
Implementation of the requirements of Change Order
MICR-633 (Master Installation Notice Card Implementation Program) has been accomplished. This requisement was a prerequisite to proper implementation of that portion of MSFC/KSC Program Directive
448 that pertdm to our certification of the W F C

"Saturn V Configuration Index and Modification Status
Report" prior to launch of any stage. MICH-770,
which has the same intent as MICH-633, has superseded MICH-633, Implementation of MICH-770 had
been completed.
During FY 1968, limited Product Revision Records
(PRRts) were implemented to correct minor engineering deficiencies on delivered but uninstalled retrofit
kits. Strict control over the release of these PAR'S
is maintained by the configuration accounting office.

TECHNICAL PROGRAM
ANALYSIS AND REVIEW
In February 1968 the new office of Technical Program
Analysis and Review was established under the S-IC
Program Executive. The purpose of this office is to
analyze current management and operational control
systems and interfaces with the goal of significantly
increasing the effectiveness and efficiency of their
performance in supporting program management decision processes.

During F Y 1968, two task force efforts were conducted
by this new office with the aim of improving the effectiveness and efficiency of stage transfer and delivery,
and paperwork circulation at Michoud. The following
results were achieved with an estimated net cost reduction of more than $10,000 per stage:
a)

TO level office labor peaks that occur at stage
transfer and delivery, three steps were taken:

1)

Changes were initiated against the mechanized as-built data system to minimize effort required to resolve configuration exceptions;

2)

A team composed of representatives from
the Boeing/Michoud Quality and Reliability
Assurance, Operations, and Systems Test
organizations was established for Ule purpose of resolving canfiguration exceptions
via a procedure that eliminates duplicate
effort and shortens flow time; and

3)

A factory area was s e t up to perform intermediate staging of "J" (flight) eonfig-

�MiCHOUD CENTRAL SAFETY BOC\RO

and severity rates of disabling injuries per million
manhours worked are represented in Figure 1-2.

During FY 1968 the NASA Emergency Evacuation
Plan, M-1-29, was published and the Michoud Cen-.
tral Safeby Board Chairman, directed each Michoud
ccmtr8ctor1s Heath and Safety office to eurvey their
wsasr far compliance with this plan, As rr, result of
the Boeing survey, thirteen specific recommendations
were made, primarily in the Building 102 south
mezzanine area, to improve the location and condition
of exit signs in the factory

.

A comprehensive survey was taken of those areas u#-

Uziw Pyr-A-Larm fire and smoke dctttsctbrs which
contain small amounts of radioactive material. All
such detectors were identified and registered with the
Louisiana Board of Nuclear Energy,

--

MICHOUD LlNE CONTROL SAFETY COUNCIL

The Line Control Safety Council continued its
activities in safety awareness and accident prevention programs. During the reporting period, recognition for outstanding safety participation was given
each month to an individual employee who was
chosen by the Council. Additionally, a letter of
commendation was written each month to the organization m q e r of the Safety Director who was most
effective in promotion accident prevention.
LlNE CONTROL SAFETY PROGRAM SUPPORT

.

The Michoud Safety Training Program gained impetus
by the addition of a Safety Indoctrination Course series.
This six course series covers safety command media,
accident causes and prevention, and specific job hazards. All maintenance and manufacturing employees
have attended each course in the series. The Line
Control Safety supervisor and the Line Control Safety
monitor training courses were updated during the
fiscal year and presented monthly, Michoud new hire
safety orientation includes instructfon on industrial
hazards, Company policy, and command media. Participation in the Line Control program is continually
monitored. The "Line Control Program Supervisor's/
Safety Guidewhas been revised and distributed to all
supervisors in the Line Control Program.

-

SAFETY ADMINISTRATION

There were 1262 reported injuries in FY 1968 compared to 1625 reported injuries in FY 1967. Health
and Safety processed 97 Workmen's Compensation
claims in F Y 1968, 8 of which were disabling injuries, This compares ta f27 claims fn FY 1967, 10 of
which were disabling injmies, The monthly frequency

D5-12601-5

Figure 1-2

Reported Injuries in FY 1968

The statistical injury indices for FY 1968 are compartable:
ed to FY 1967 rates in the foUFY 1968 FY 1967
Reported total injury
frequency average rate

0'83

Disabling injury frequency
rate

0.98

Disabling injury severity
rate

20.24

180

1.11
18.2

Workmen's Compensation
claim rate
11.9
14.0
*All ratee are per million manhours worked,

11

�A program for inrlrroving the evaluation of crnployees

for high risk, high v:liue jobs has been proposed, This
program involved revising tho existing certification
p r o g r m and providing additfond supervisor training
and b?.tfdn$We. I n adtiition, a new combined certificntion and ltcalth csmination progr'm will be administered to provide s standard health examination to all
employees engaged in critical tasks.
NOUSTRNL HYGIENE AND RADIATION SAFETY

Znriustrial hygiene activities d u r i FY 1968 consisted
primmay of cvnluntign nrrd control of: emfromental
health hazards resulting from fndust~ialoperations.
Specific accotnplishments during the past year include
the following:

TECHNOLOGY AND AUOIT

A Health and Safety technology audit function has been
formed. This function includes industrial hygiene,
radiation safety, safety audits, artd speciai projects.
The safety audit program schedule was accelerated to
achieve the goal of performing an audit of each shop
area every six months, Audit emphasis has shifted
from detailed area safety inspections to evaluation of
the Line Control Safety Program, and the effectiveness
of each organization's hazard identification and conk o l meoaures.
PARTICIPATION IN LOCAL INDUSTRIAL HYGIENE AND SAFETY
EFFOR?S

a)

Improved exhaust ventilation was obtained to
reduce the exposure to toxic and irritating vapors in the silk screen room and the potting and
molding facility;

b)

A central dust collection system was ob-

t a e d for the tool grinding shop, and all
equipment in the shop was provided with
local exhaust ventilation;

During the reporting period, several lectures were presented to classes at Delgado College and Tulane University, and a class of graduate students in environmental health fromTulane were given a lecture and a
tour of the Michoud Assembly Facility.

c)

All changes to process specifications were reviewed to determine that adequate instructions
were included conoerning safety handling of
hazardous materials; and

The New Orleans office of Civil Defense presented a
ten-hour Civil Defense Radiological Monitoring Course
to selected Michoud personnel. Seventeen Boeing employees completed the course.

d)

Noise surveys were performed in several
areas of the Michoud Assembly Facility, including the carbon arc gouging operation in the
manufacturing development laboratory.

SAFETY ENGINEERING

*

A summary of FY 1968 radiation exposure levels for

several groups of radiation workers is given below:
Number of radiation workers on program

34

Average exposure to all radiation worke r s (millirem)

25

Active support of industrial hygiene activities in New
Orleans colleges, universities, and professional societies has continued.

Emphasis on hazard analysis and safety design review has been maintained in the areas of manufacturing
process changes, test systems, tooling acquisitions,
and facility modifications. Functions requiring special
attention in the planning of safeguards were the oxygen
flow tests, titanium machining, fuel tank hydrostatic
test cycling, ablative coating, helium bottle changeout,
"POGO" test program, hardware or stage transportation, and steel handling ring installation.
SAFETY SURVEILLANCE

,

Average exposure to a l l quality radiographers (millirem)

33

Average of health and safety monitors (rnillirefn)

53

The maximum allowable dose of radiation, as stated in
Louisiana Radiation Regulations, is 5000 millirem per
year. The employees on the radiation control program are engaged id welds-x-raying, laboratory work,
radiation monitoring, and instrument, calibration.

Engineering surveillance and inspection activities have been expanded to provide direct technicd support
to the shop safety organizations. Professional safety
personnel have been assigned to each shop area to
assist in the identification of shop production groblems. This method has proven to be effective.
MISSISS1PPI TEST FACILITY HEALTH AND SAFRY

~oeing/MississippiTest facflity completed FY 1968

'

�without a disabling injury, A total of 884,399 manhours were recorded during this period. Boeing/MTF
has worked 2,061,972 manhours and recorded only
one such injury. That injury occurred in May, 1966.
S h e that date 1,89B,6 17 manhours have been worked
without a dissblfng injury, The monthly rate of fnjurfea per a9il;lion mmboure worked at MTF ars
presented in Figure 173.
TOTAL INJURIES

January and May 1968. Each of these inspections indicated that our security procedures and Industrial Security Manual compliance are satisfactory.
Representatives of Factory Mutual Insurance and Factory Xnsurance Association conducted recurring larss
preventton inspections on a quarterly bmis during
1968. These inspections revealed that Boeing fire prevention procedures were satisfactory.
A security eduoation program was given to L80 memk
bars at mwgrmsnt Iry the Paew Qollrpora%Bimatm
of Security on March 25, 1968. Security clearances
were granted to 459 employees during FY 1968.

tX,
J

0

I

=r"

gm
-I

d

Evacuation control plans were developed for Boeing
areas in the S-IC test complex, S-IC
booster storage building, and Engineering and
Administration Buildings at MTF Evacuation
routes were posted in all work areas of these
facilities, and detailed instructions were distributed to all personnel. Fire and evacuation drills
have been conducted and assessed by management
in each facility. Fire brigades were formed and
trained for each facility consisting of four teams
in the S-IC static test stand and one team in
each of the other facilities.

-- occupied

a

3

.

B W

.D

9

I
:

s
Figure 1-3

FY 1968 Injuries Per Million Monhours
MTF

-

Several studies have been made to improve fire protection capability on the S-IC Test Stand. These studies have resulted in a proposal that, when implemented , will provide auxiliary fire protection capabiIity
when the high-pressure industrial water system is out
of service.
In August 1967 the Michoud Safety Contest was expanded to include Boeing activities at MTF. Out of a possible 100 points, the MTFts point standing rose from
63.1 to 98.7 by the end of CY 1967. At the end of the
fiscal year, Boeing/MTFfs point standing is third with
a cumulative standing of 600.5.
An MTF quarterly Safety Award Program was established in April 1968, This award is presented to the
employee who has demonstrated outstanding safe-work
attitudes, influenced the safe-work attitude of fellow
employees, taken Mtiative to locate, identify, and report safety hazards, and measurably contributed to
the Safety Program.

sECURw
Proper security of all classified data, matsrial, and
hardware was maintained during FY 1968, Security
inspections of the Boeing pcrrtiw of the Michoud Aasembly Facility were conduoaed in SepWmber 1967 aad
DP-1260 1-5

The Hurricane Preparation Committee conducted a
comprehensive review of our existing "Hurricane and
Tropical Storm Plan," and although the content of the
plan required no changes, there were sufficient organization, location, and title changes necessary to require ib reprinting.
The "Boeing/Michoud Plant Disaster Plan," which is
a comprehensive disaster control plan, has been updated and released. I t contains detailed planning for
the protection of personnel and plant during natural
disasters, major accidents, and civil disturbances,
also a civil defense and evacuation plan.

PERSONNEL
MANPOWER

Michoud and the Mississippi Test Facility employment
declined by 833 employees during FY 1968. This
planned reduction was made possible by incrieaafng
efficiency, schedule changes, and tke continuing transition from a developmentalto a production type
program. The following comparison indicates the
reduction in each payrok

13

�T O W Michoud,and MTF
6-29-67

6-27-68

Hourly
1,607
Ccnernt O i f i c ~
2,023
Proksslonalfloohnfcn1 850
Supervisory
508
Office Exempt
99

1125
1767
769
490
103

,

P,ayroll

'

-

-

-

Total

Net Change
-482
-256
81
18
+ 4

--

-833

Of the Miahoud and MTF tutrrt of 4284

sa of June 27,
1968, 3394 employees were new hires anel 860 were
transfers from other Boeing locations.

TRAINING

Paid-time training increased during F Y 1968 with
14,677 employees completing 1474 classes. In FY
1967, 8182 completed paid-time training classes.
Of the 14,677 employees who received paid-time
training during FY 1968, 1641 completed 296 certification classes ; 1808 completed 5 12 re-certification
classes; and 11,228 completed 666 systems, skills
and management courses.
MTF training requirements have been supported on a
continuing basis. Major emphasis has been placed on
certification, re-certification, reliability, and safety
training programs in support of critical operations
for S-IC stage testing.
A steadily declining work force caused a r ~ d u c t i o nin

the number of employees particiwatim i n off-hour training programs. During FY 1968, 640 employees cornpleted 55 courses. Durihg FY 1967, 883 employees
completed 82 courses.
Attendance at seminars, technical sessions, and
symposiums ipcreased during FY 1968 with 610 employees i n attendance. During FY 1967 , 341 attended
similar sessions.
MANAGEMENT DEVELOPMENT PROGRAhn

The Management Development Program has been significantly expanded and strengthened during FY 1968.
A separate management development function has been
established a s a p a r t of the Industrial Relations organization. This function is responsible for the administration of activities leading to early identification,
selection, and development of the management talent
needed to meet current and future needs.
Michoud is represented on the Boeing Launch Systems
Branch M magement Development Committee which fe

responsible for the formulation of objectives and
plans that will ensure effective management development actions. It also identifies improvements, reviews progress, and provides recommendations
pertaining to Launch Systems Branch management
development activities.
Three off-hour management courses were attended
by Boeing employees; and 12 paid-time management
courses were conducted f o r 680 employees.
GRADUATE STUDY PROGRAM
As s r e e 9 t of the Boeiarg Graduab Study Broglem, I f
amploytsss will receive their Masters degree at the
end of the ItSurnmer term in 1968. Additionally, 75
empfoyees took 361 credit hours during the Fall semest e r 1967, and 55 enrolled for 271 credit hours for the
Spring semester of 1968.
UNDERGRADUATE PROGRAM
As a result of the Boeing Undergraduate Study Program that was implemented in FY 1967, four employees will receive their Bachelors degree at the end of
the Summer term in 1968. Additionally, 54 employees
took 299 credit hours during the Fall semester, 1967
and 37 enrolled for 182 credit hours for the Spring
semester of 1968.
COOPERATWE WORK-STUDY PROGRAM

The Michoud Cooperative Work-Study Program has
increased from 28 students in FY 1967 to 50 students
in F Y 1968. This represents the largest number of
Co-op students of any location o r Division in the Company. Forty-four a r e Engineering students, five a r e
Math and Computer Science students, and one is a
Management student.
PLANS FOR PROGRESS AND EQUAL
EMPLOYMENT OPPORTUNW PROGRAMS

A special team of investigators from the Contracts
Compliance Office of the Department of Defense conducted a formal investigation of the Michoud Assembly
Facility in August, 1967. Fourteen recommendations
concerning certain personnel practices and procedures
resulted from this audit. Subsequent Boeing action
taken on each of these recommendations has been
acceptable to the Contracts Compliance Office.
An Equal Employment Opportunity Administration function was established in October, 1967. This function
includes the development, maintenance, and monitoring of affirmative action policies and procedures for all
aspects of the Boeing/Michoud Equal Employment Opportunity Program,

A Boelng/Michoud Equal Employment Opportunity

�Committee was established in January, 1968. I t concerns itself -with all activities related to Equal Employment Opportunity within the Boeingl'Michoud cornplex and assists in the promotion of equal employment
opportunity regardless of race, religion, color, sex,
age or natio~alorigin.
During the reporting period, a member of Boeing
Management ww elected Vice-President of the New
Orleans Voluntary Equal Employment Opportunity
Council. Boeing Hanqement was also represented
on bhe boards of the following organizations: (I) New
Qrtecule amid Wolfme P l m w C o m a the plmaing a r m of the Unlted Fund: (2) The f2ommuntty Relations Council a biracial group affiliated with State
and Nation4 Community Relations Council Organizations; (3) The City Department of Public Welfare; (4)
The Citizens Advisory Committee to the Southwest
Educational Development Laboratory a committee
organized to resolve problems on intercultural education related to Negro and Southern American minorities; 45) The Urban League of New Orleans; (6) New
Orleans Area Manpower Advisory Committee a committee that has approval authority for the funding of
all training in a seven parish sector falling within the
provisions of the Manpower Development Training
Act of 1962;and (7) Personnel Advisory Committee
of Total Community Action the committee devoted
their efforts toward ensuring the success of the Concentrated Employment Program (CEP)

-

-

-

-

-

.

All non-supervisory Boeing employees were briefed
on the Company's Equal Employment Opportunity
policy. Supervisors and prospective candidates for
supervision who attended the Introduction to Management course received comprehensive EEO briefings.
The Fall and spri$g College Relations Program resulkd in recntiang kamw visiting 21 colleges, seven
of which were predominantly Negro. Industrial Relations hosted 30 Job Development Specialists and
Center Directors from the 15 Systematic Training and
Redevelopment (STAR) Incorporated Basic Education
Centers located in Mississippi. A briefing and tour of
thenfacilities were included in the visit.
Two Negro students from Southern University, Baton
Rouge, Louisiana, participated in the 1967 Co-op
Program. A former Negro Co-op student of the University of Detroit accepted an offer of permanent employ ment.
Seven Negro employees (five supervisors and two nonsupervisors) completed the recently developed Introduction to Management course for supervisors aad
prospective candidates for supervision. One of the
non-supervisors was later promoted ta supervisory
status,
D5-12601-5

During this reportirig period, three Negro employees
were promoted to supervisory status raising the number of Negro supervisors to six.

COMPUTER SCIENCES
During FY 1968 the Business Information and Support
Services, and Command Media Organizations were
transferred from the Information Management Organization to the Program Planning and Reporting Organization. The remaining Information Management Organization was then rede~ignatedComputer Sciences
AppUostions (CBA) This wganfz&amp;tion was d@smed
necessary to permit CSA to effectively support the
conversion to third generation computer systems.
During the organizational realignment, a Computer
Systems Requirements Organization was created within CSA to act as liaison between using organizations
and systems design groups. This organization exercises surveillance over all mechanized data systems
from request to implementation, and assures maximum system efficiency and integration.

.

MECHANIZED DATA SYSTEMS
DEVELOPMENT
NEW SYSTEMS IMPLEMENTED

As-Built Configuration System-The Michoud A s-Built
Configuration Management System was successfully implemented with the delivery of the S-IC-4 in March
1968. Many of the reports previously prepared manually for the Acceptance Data Package are now obtained
automatically from the mechanized system.
The mechanized system examines a specified Engineering design baseline and then expresses the asbuilt configuration of a given S-IC stage as equal to
the design baseline, plus or minus some known level
of exceptions, Thie provides Boeing Quality and Reliability Assurance with overall configuration management in support of deliveries, as well as data for
launch readiness reviews.
The as-built system uses the exception principal
for recording configuration data. This allows
the system to rapidly recognize and/or resolve
differences in configuration due to engineering design changes, The system also tracks instrumentation components, traceable parts, time-cycle and
age We sensitive parts, retrofit installations, and
con£i@ration exceptions.
The as-built system:
a)

Eliminates the need for manual comparisons
between two engineering design baselines;

b)

Provides a concise listing of configuration ex15

�ccptlons in an indcnhred sequence, thereby
providing a display of the systems which
are in a "no-go" condition due to a configuration deficiency;
C)

Produces summary- listings and reports on a
blnlely basls for Management vfaibility; and

g

Allows for rapid accountability of as-built
conEigwation differences between any two
S-IC vehicles.

exp'mdcd to serve the needs of MTF and the Boeing
Atlantic Test Center (BATC), This will provide a
colnmon configuration accountability system for each
S-IC from manufacturing through flight.
hlTF Recap System-The MTF Recap System, a set
of computer programs designed to track Saturn record
system papmvark by maintaining a visual listing of
open items against stage processing and GSE configuration changes at MTF, has been implemented. This
system is directed toward obtaining zero defects testing by providing the necessary visibility for organizing
scheclulcd work, tracking open work, and documenting
completed work,
Operations Change Status Reporting-The Operations
Change SL~tusReporting System was implemented during FY 1968. This system's objective i s to schedule
and monitor a committed change to the basic contract
from the time the change i s committed by the change
board to the date of delivery. Reports from this system provide operations management with current detailed status visibility on committed change; a detailed change scheduling tool; and a means to measure
performance on committed changes.
Some of the other mechanized data systems deveioped during the past year, and a brief description of each, are:

Cost Review System-Major modifications were made
to the Launch Systems Branch Cost Review System
which collects and updates actual labor cost data by
task and NASA 533 report line number. These changes
increased the capabilities of the system to produce
automated graphical displays and management and customer reports of actual and budget data at the task,
contract-schedule , organization, and manager levels.

CONVERSIOM TO THfRD GENERATION
EQUIPMENT
We are continuing the conversion of Honeywell computer equipment programs to run on the Univac 1108
computer. The following systems are now being processed on the Univac 1108: Part Requirements, Material Inventory Control, Facilities Equipment A cquisition, Plant Services Maintenance, Southeast Personnel Accounting and Records, Suggestion Records,
Filling of Hourly Openings, Stage Cost Control, AsBuilt Configuration, Engineering Release, Traffic
Routing, and Facilities Stores Inventory. As part of
the conversion redesign, significant compression of
programs is being accomplished, leading to reduction
in computer run-time and operational set-up time.
COMPATIBLE CONVERSION SYSTEM

af

Equipment and Final Assembly P a r t Shortage
System - provides management with better
visibility on parts shortages existing in equiprnent and final assembly parts crib areas;

b)

Packaging Preservation Requirements System
a reference file of packing and cratmaintng specifications for all parts shipped from
Michoud; and

c)

Facilities Stores Inventory System maintains
inventory control of spare parts and cansumable

16

SfGNlFICANT SYSTEMS MOOlFlCATlONS

PERT-VZsuaJ Task Analysis (VISTA), a computer
program designed to rtutomatically plot PERT networker
on the SC-4020 Digital Plotter, has been implemented.
The automation of plotting networks will replace the
manual drafting efforts required to update PERTed
networks while permitting a one-to-one accuracy correlation of network graphics to PERT tabular reports,

The scope of the As-Built System is currently being

-

supplies stocked for use in the Factory Equipment Maintenance Program,

-

The requirement that Boeing convert its programming
to operate on a Univac 1108 computer with direct access mass storage has led to the concept of a centralized file management system as the most economical
and efficient approach to conversicm. The file management system must perform record address lockup,
data retrieval, data restructuring, file backup, and
access control. Additionally, the system must support operationp under both Univac 1108 Executive Systerns--EXEC 11 and EXEC VEIf. The Compatible Conversion System satisfiee these requirements. A b o ,
operating as a set of library subroutines available to
both Fortran and Cobol worker programs, it supports
the following features:

D5-12601-5

�utomatic index constructioi~and maintenance
for user-specified data files;
ata storage, retrieval, and updding commands

r direct record access;
Automatic record blocking a d deblocklng to
increase serial processing speed;

d)

Standard file backup and recovery procedures; and

e)

LolSfcd file structuring facilities.

The Compatible Conversion System will operate under
either Univac EXEC 11 o r EXEC MIZ, allowing conversion of \vorker programs to a stable mass storage
interface, The system has been designed and coded
and is currently being checked out against both Executives

.

A l l deliverable data items for S-IC-2 were delivered on or before schedule even though some
input data items were received late. The outputs
of the system required to support Boeing's presentations to the FLight Evatuation Working Group were
available when needed.

MECHANIZED DATA PROCESStNG
CONVERSION TO UNIWAC 1005

The Univac 1004 Card Processor was upgraded to a
Univac 1005 Card Processor, This equipment modification allows usage of internally stored program
instructions to execute production processes. Before
the equipment was modified, machine instructions
had to be wired into a logic panel. This is a timeconsuming process. The programming effort required to put a job into production has been significantly
reduced by the equipment modification.
OPTICAL SCANNER UTILIZATION

NUMERICAL CONTROL
A year ago, the use of Numerical Control (NC) machinery at Boeing/Michoud was just beginning. Only
the Cincinnati ATC-430 machine was in production.
No software was available for this machine; hence, all
part programming was manual, difficult, and tedious.
Since that time the N/C computing group has modified,
implemented, and checked out software (postprocessors) for six N/C machine tools. They a r e the Cincinnati ATC430, Sunstrand N/C-3 Milling Machine,
Gorton 2-30 Tape Master, Sunstrand OM-3 Machining
Center, Kearney and Trecker Skin Milling Machine,
and Cincinnati Veroi-Power N/C Bed Mill. The first
three machines are in production status. The other
three are scheduled to go in production by the summer of 1968. A l l software packages have been checked out and a r e awaiting machine activation.

FLIGHT DATA EVALUATION
A system of computer programs developed during
1967 and 1968 to support S-IC flight evaluation was
rtsed to process data from S-IC-1 and -2 flights.
Some of the outputs of this system, e. g. , tapes confaining re-formatted, calibrated data, are contractually required deliverable data, with a very rigid
schedule. Half of the data items for S-IC-1 were delivered on schedule and half were behind schedule for
various reasons, includiug late receipt of input da@,
unexpected data anomalies, aad processing problems,

Usage of the Control Data Corporation 915 Optical
Scanner has been significantly increased during FY
1968. Current output volume of cards is approximately 25,000 per month. Applications under development
are expected to boost this figure to 100,000 records
per month by mid-year.

MECHANIZED DATA SYSTEMS
STANDARDS
Technical standards to direct and control the development and implementation of automated systems have
been written and released. Documentation standards
for defining automated system requirements, system'
design, and maintaining computer program system
configuration control are now in force. Documentation standards governing the acceptance test, the
user's guide, and the program maintenance guide will
be released in the near future. In addition, approximately 120 technical standards have been issued to
CSA programming personnel describing the equipment
available for use in automated systems ( both second
generation and third generation), characteristics of
the software on these systems, and guides to efficient
use of this computer hardware/software.
During the next year it is expected that the initial development of technical standards will be completed.
These standards will cover all areas of technical information needed to interface with the Slidell Computer
Operations Office contractor, guides to good programWag practice, docwnenWon standards, design stan-

�dnrds, nnd progrnn~minglanguage and equipment s b n cf:wds. These standards a r c e.upccterf to contribute to
in~provoiidesign of computer programs and to their
usc~iiifnessto others by virtue of program generality
nrtd comprehensive program documentation.

BUSINESS INFORMATION
SERVICES
During FY 1968 the n u m b r of listings in the Michmd
telephone directory and the number of volumes ~ u b lishcd were reduced. On March 20th, the alphabetical
section for Boeing was reduced from 5300 name listings to 1735, The number of pages for the Boeing
section was reduced from 67 pages to a t o t d of 22
pages. The total number of directories received from
the Support Contractor was reduced from 5000 books
p e r quarter to 3000 copies. This resulted i n an estimated cost savings of $16,840 per year.
On March 14, 1968, NASA restored indicia mail privilegcs to Bocing official mail destined for Washington,
D.C ,, Huntsville, Alabama, and Cape Kennedy, Florida. This privilege will result in estimated postage
savings to the government of approximately $24,000
per year.
During FY 1968 a Michoud directive was revised
and published to establish telephone standards
patterned after the Boeing Aerospace Group Administrative Services Business Manual. As a result,
since October 31, 1967, Michoud telephone equipment costs have been reduced by $2563 p e r month,
This reduction represents $30,756 per year savings
to the Government.

RECORDS MANAGEMENT
During FY 1968, approximately 2500 cubic feet of
records were received from Michoud organizations
and stored in the records storage center. Based on
Boeing Aerospace Group records and release cost
standards, a savings of $2.65 per cubic foot of records is realized when records a r e placed in inactive
status in storage a r e a s as opposed to office areas.
I n FY 1968, using this standard, a net savings i n the
amount of $6651.50 was realized.
A mechanized system, which provides a listing of
organization working files, ha^ been developed, TMs

system provides a master listing of records, with
common Michoud categories and subcategories, including specific types of records, file location, and
responsible supervisors. The purpose of the system
is to provide rapid identification, location, and retrieval of records associated with cost, schedule,
and product technical performance.

a

The Classified Control Station has comr~letedanother
full year of service to the various Michoud organizations without a single security violation.

COMMAND MEDIA
The Boeing Launch Systems ~oeing/MichoudCommand Media System formally establishes and documents management policies and controls, authority
delegations, and practices. During FY 1968, the
command media documentation of systems and product
control was revised to ensure meeting NASA and
Boeing goals. The record system for the S-IC stage
was more clearly established with the issue of eighteen new and revised procedures. A new system has
been devised to ensure timely response, traceability,
and economy for contractual data delivery requiremen&amp; and i s proposed for implementation through
appropriate command media. The documentation of
the Saturn V interschedule working relationships between Schedules 1, 11, and IZT to command media is
now in progress. Management Directives and Operating Procedures a r e forwarded to NASA, on a quarterly basis, as contractual data delivery requirements.

*

I

DOCUMENT CONTROL
The Boeing Launch Systems Branch Document Control
System, since its implementation, has proven to be
one of the most cost effective operations at Michoud.
During this reporting period, additional significant
reportable savings have been generated and validated
through the cost improvement system. Identified savings, associated with the cancellation of documents
during preparation (that were considered valid by
both Boeing and NASA/MSFC) , were undetermined
by NASA Headquarters at the close of FY 1967. ~ k ; e
validity of these savings was established during FY
1968 when $480,590 in savings for these activities
were approved for the Launch Systems Branch. The
total validated contribution of the Document Control
System t o the Cost Improvement program through
CY 1967 exceeded $13 million, which was 13.57 percent of Michoud and 9.64 percent of the total Boeing
Launch Systsrns Branch savings.

C

-

�Document Control participated in NASA/Boeing
tiations for the revision of contract deliverable
requirements directed toward consolidating Con
NAS8-5608, Schedules I and LA, Data Requireme
Lists (DRLJ, developed a data management statement sf work, and clearly Identified, through line
itsme In the DRL , total data delivery requirement
for both contract schedules. Text proposed by
Document Control to improve contract h a t a ~ &amp; j g e ment was successfully negotiated into the statement of work. The consolidated DRL and statemen%of work were implemented try Contract DOCUmsnt TNdeS-IC-67-10, S-IC P r a g r a n Deliverable
Data, in January 1968.
T o fulfill h need to improve contract data delivery
management, Document Control participated with
Michoud Contracts in developing a new system for the
production release, accountability, and delivery of
data. The new system eliminates multiple channels
for delivering data to NASA and replaces them with a
more orderly and cost-effective flow through existing
centralized release services. I t also establishes a
data serial numbering system, consistent with contract requirements, which permits management accountability and traceability of deliverable data.
In March 1968, Document Control issued instructions
that changed the focal point for issuing Boeing document serial numbers and implemented a new format
f o r requesting document development authorization.
These changes simplified the maintenance of the
"LSB Document Control Report" by eliminating previously required monthly organizational data inputs.
Consolidation of the document number issuance with
the preparation of data inputs into one functional area
under Document Control has reduced workloads of all
organizations. It has also ensured the timeliness and
accuracy of document indices.
A review of document activity during the reporting
period (see Figure 1-41 indicates an increase in the
number of active documents during the last year, A
substantial portion of this increase is the result of
incorporating into the system, documentation that was
not formerly included, and for which accountability OX
distribution control did not exist.

FORMS MANAGEMENT
During FY 1968, the LSB Business Forms Management System has continued to be a cost effective aperation. Under this system there has been no out-of-

D5-1260 1-5

tock situation in Forms Store during the past year.
so, by careful inventory, issue and reorder control,
production requirements imposed on the support
services contractor for business forms has been decreased by 40 percent while the number of controlled
form items has increased 35 percent over the pre-

GOVERNMENT FURNISHED SUPPORT
SERVICES
A t the request of NASA, Boeing conducted a study of
its support services requirements to seduce the overall support effort by 25 percent, The FY 1968 neaotiated budget for government furnished support s e k i c e s (less Computer Services) for Boeing/Michoud was
$6,973,000 compared to $8,350,000 for FY 1967. The
reduction in projected support services was about 16
percent. Actual expenditures, if extended through
June 1968 at the present rate, will amount t o $6,458,
600, an additional support services reduction of about
7.3 percent. Therefore, the government furnished
support services required during FY 1968 were decreased by 23 percent, or $1,891,000 from the FY
1967 level.
As a result of improved communications and coordination between Boeing Reproduction and the support
services contractor's reproduction representatives,
more Boeing reproduction requirements a r e being
accomplished in a timely manner by the support
services contractor. This has enabled us to reduce
headcount in the Boeing reproduction shop by
approximately 30 percent.

MICHOUD ORGANIZATIONS
REALIGNMENTS
During FY 1968, several significant changes were
made in the Boeing/Michoud organization structure.
T o provide a consolidation of related functions and
posture during the first quarter, the Information
Management organization concentrated its resources on the task of implementing the new computing equipment a t the Slidell Computer Center.
Business information and support services and the
command media functions were transferred from
Information Management to the Program Planning
and Reporting organization.
In the second quarter, the Michoud Information hlaaagemer;lt organization was redesignated
Michoud Computer Sciences Applicatic~ns, which

19

�ACTIVE DOCUMENTS

-

CANCELLED DOCUMENTS (RELEASED) III
I

ChNCELLED WCUMENTS (UNRELEASED) rflflfl/#m

t
Figure 1-4

Document Activity During W 1968

properly denotes the functional description of
the organization.
*

At the beginning of the third quarter, the S-IC
Program test function emphasis shifted from static
firing to flight, thus the test evaluation function was
transferred from the Systems T e s t organization to
the Engineering organization. This change enables
the test evaluation involvement in flight evaluation
tasks t o be accomplished more efficiently.

-

I he S -IC Operations organization was realigned in
the third quarter of the reporting period. This realignment involved combining all Industrial Engineering organization t o more effectively utilize
skills while maintainlag proper support to the manufachtring organization; and consolidating all manu-

facturing activities and manufacturing support
activities to effectively reduce operating costs without impacting performance schedules.
The S-IC Systems Test Manager's office was relocated from Michoud to MTF in the third quarter of
the fiscal year to enable Boeing to establish a
closer working relationship with the NASA Manager
at MTF

.

The Management Development Coordinator position
was established during the fourth quarter of the
fiscal year, reporting to the Michoud Industrial
Relations Manager, because of increased emphasis
on management development and because of
recommendations s e t forth in the Launch Systems
Branch Management Development Plan.

�CONTRACT END ITEMS
&amp; SERVICES

�SUMMARY
Launch of the AS-501 and -502 took place at the
Kennedy Space Flight Center (KSC) during F Y 1968.
These vehicles were thrust into flight by the S-IC-1
and -2, Both stages, and their Boeing supplied
ground support equipment, functioned satisfactorily
and no anomalies o r objective discrepancies occurred
which adversely affected their flight.
The flxrst ~wina;Michoudmadachrred flight stage,
the 8 4 C - 3 , ww rhfpped to x l C on December 23,
196'1. This stage is now a t KSC where it is being
modified in preparation for the first Manned Apollo
Saturn Launch.
Several significant incentive milestones were achieved
during F Y 1968. The S-IC-4 was delivered to NASA,
on-dock Michoud, on August 28, 1967. This stage
has remained at Michoud since formal delivery, and
la presently undergoing modifications which were
originally scheduled for completion at KSC. Also
during FY 1968 the S-IC-5 was auccessNly static
fired, and S-IC-6 and -7 completed post-manufacturing checkout.
At the end of the reporting period the S-IC-8 and -9
had been completely assembled and were in storage
a w a i w start of post-mmufaoturing checkout. Also,
the SIC-10 was in horizontal assembly, and S-IC-11
through -15 major struckues assembly was proceeding as achecialed.

Throughout the fiscal year S 4 C stage and W E d e s m

activities were directed toward increasing the quality
of the product and resolving problems and anomalies
identified. These efforts were supported by various
testing programs including reliability, qudification,
development, and failure analysis. During FY 1968
Engineering laboratories completed 331 tests. A s
a result of the POGO phenomenon experienced during the AS-502 flight Boeing has formed a task force
to cope specifically with this problem to assure its
slbviation prior to the next 8-IC flight.
Quality and product assurance activities were conducted on a continuing basis during FY 1968. The
objective of these activities is assurance of the quality of the end item and its components, and assurance
that
activities critical to missions or programs are
...
identified, planned, and accomplished. During the
reporting period 55 quality audits were conducted as
a part of the quality program. These audits resulted
in the definition of 467 discrepancies which have been
resolved or are being resolved at this time.
The Quality Maintenance Programwas initiated by
Boeing during FY 1967 and expanded by Change Orders
MICH-544 and MICH-723 during FY 1968. The purpose of this program is to assure the quality of vendor hardware, with primary emphasis on that hardware where failure could cause loss of stage or crew.
his program includes Boeing Management visits to
vendors, audits of engineering documentation, quality
analysis of vendor hardware, and other testing and
moffvational techniques designed to improve the
quality of vendor hardware.

-t

DS-12601-5

23

�DELIVERABLE HARDWARE
STAGES

*

NASA/MSFC ASSE

t of FY 1968, both the S-IC-1 and -2
e r e they were undergoing prepamtion
These vehicles were lwnched, a s part
68, respectively. (Figure 2-1 crh

ng mwed from the KSC VAB , Fi
S-501 launch.

Subsequent to the AS-501 and -502 launches, all available S-IC-1 and -2 performance data, including engiring sequential film and S-IC/S-11 stage separation
from the 8-11 stage was evaluated by the Boeing
ormance Analysis team.
he SdC-1 and Boeing supplied GSE performed ati isaetorfly during AS-501 countdown and flight and, in
1 S-IC-1 mission objectives were met.
e of all systems was satisfactory, and
ies o r objective descrepancies which
urred did not adversely affect overall stage
systems performance.
mance of all S-IC-2 systems was satisfactory
countdown and launch of the iiS-502. Performance of the Boeing supplied S-IC GSE was also satisfactory, and no f d u r e s of components o r systems occurred during launch countdown. No failures o r deviations which occurred in S-IC systems during the
AS-502 launch adversely affected overall stage systems
performance. The occurrence of the POGO phenomenon
(see page 371 caused no problems on the S-IC-2.
Specific problems encountered during the AS-501 and
-502 launches, and the corrective actions taken to
rectify these problems, are discussed throughout Section Kt of this report. Detailed information on S-IC-1
and -2 performance during these flights can be obtained from Documents T5-7000-1, S-IC-1 Flight Report,
released January 11, 1968 and T5-7000-2, S-IC-2 Flight
Report, released June 28, 1968.

S-IC STAGES

- BOEiNG ASSEMBLED

The S-IC-D was stored in the S-IC booster storage
building at MTF at the start of the fiscal year. On
November 10, 1967, it was erected in the S-IC static
stand a t MTF for a s e r i e s of fuel tank drain tests,
h commenced on December 18, 1967, and were
leted on January 17, 1968. (See anti-vortex tests,
75.) On February 1the stage was removed
the test stand and on February 6 was again placed
rage in the booster storage building at MTF.
1968, the S-IC -D was placed aboard
ansferred to Michoud. It was then
n April 23, 1968, where MSFC plans
lay a t &amp;e Space Orientation Cen-

1968, the 5-1C-F

, in storage at
25

�Michoud, ivils hcing used for crew training in preparation for the S-IC-3 helium bottle changeouts authorized
by ECP 0215. The atage rcrnaincd in storage until
March 8 , 1968, when it was ~novedto the Michoud Vertical rlssembly Building (VAB) where it was erected on
hf~trc-h12, 1968. t2'hiie in the VAB, the duminum forward hnncff i&amp;ring was removed , nnd n steel handling
ring was installed in its place. The stage wits returned to storage on hIwch 18, 1968, where i t remained
until hlay 20, 1968, when it was moved to the factory
for rcmavai of a LOX suction duct required to support
the Michoud LOX Suction Duct Flow test fixture whicl~
has been constructed at Michoud to test dynamic chnracteristics of suction lines for the proposed POGO suppression system (see POG0,page 37). Figure 2-3
shows thc LOX duct being removed, Figure 2-4 shows
i t installed in the test fixture. At the end of the report period, the S-EC-F was still in the Michoud factory building.

where it was erected in the VAB on December 30,1967.
Following launch of the AS-502, it was decided that the
AS-503 would be a manned launch, For this reason
the vehicle was de-erected, and the S-IT stage was
shipped back to MTF for a second static firing. A t
present, the S-KC-S ia undergoing extensive
modification at KSC , with a tentative lamch date
in November 1968.

Figure 2-4

The S-iC-3 was accepted by NASA (Michoud on-dock
incentive milestone) on March 15, 1967. The stage
was then placed in storage a t Michoud where it was located at the s t a r t of the reporting period.
During the first half of FY 1968, eighty-one modifications were incorporated into the S-IC-3 at Michoud.
Formal retesting of the S-IC-3 prior to shipment to
KSC began on November 13, 1967. Retesting was
completed on December 5,and the S-IC-3 was accepted by NASA on December 11, 1967. The stage was then
placed on a barge on December 21, departed Michoud
on December 23, and arrived at KSC on December 27

26

LOX Duct installed in POGO Test Fixture

The S-IC-4 was undergoing refurbishment and poststatic checkout at the start of the reporting period.
Post-static checkout was completed with customer
acceptance of the simulated flight test on August 16,
1967. The stage was then placed in storage on August
22, 1967. It was accepted by NASA, on-dock Michoud
on August 28, 1967 (3494.6 out of a possible 3498.6
incentive points were earned) and it remained in storage until December 27, 1967, when i t was moved t o
the stage test facility for modification and retest. Retest was accepted by NASA on March 22, 1968, however
shipment of the stage to KSC was deferred by NASA
direction. On April 1, 1968, incorporation of all changes that could be "rolled bacK' from KSC began at Mich-

D5- 12601~5

�wid. &amp;%adification
is continuing, with shipment of the
stage to KSC presently scheduled for August 23, 1968.

S-IC-5
The s b g e had just been loaded into the static test
stand a t MTF at the hsegfnning of FY 1068. Pre-static
firing checkout sf the stage was completed, and on
August 25, it was successfuly static fired for 125 seconds. Incentive points of 260.0 out of a possible 260.0
were earnod for this firing. (For a detailed descripUon of S-IC-5 static firing activities s e e page 73.)
The stage was removed from the static test stand on
September 11, shipped back to Michoud on September
12, and moved (Figure 2-5 shows an S-IC stage being
moved from the Michoud factory building) into the
stage test facility f o r refurbishment and modification
on November 15, 1967, Refurbishment and modification were discontinued for a period of time but were
renewed on January 30, 1968. On April 1, 1968, the
stage began preparation for post-static checkout,
scheduled a t that h e to commence on April 22, 1968,
Post-static checkout was deferred at NASA's request
and, at the clwe of the reporting period, is scheduled
tcJ commence on July 8, 1968.
!f------

--

.

.

Systems 'tA" instrumentation (hardwire instrumentation for static firing purposes only), and incorporation
of committed modifications, It was shipped to MTF
on March 1, 1968 and erected in the test stand on
M,wch 4, 1968.
Stage power-on wns accomplished on April 4, but on
April 23, a t the direction of the Program Executive,
S-IC-6 acceptance tests were suspended s o that proposed POCO suppression modifications, resulting
from AS-502 flight analysis, could be studied for possible incorporation and testing on the S-IC-6 prior to
the decision to incorporate them on the S-XC-8, A raview of changes affecting the stage was then conducted
to decide which changes would be practicable for accomplishment prior to a later static firing schedule.
At the end of the reporting period, S-IC-6 static firing was scheduled for eary August 1968.
S-IC-7

Post-manufacturing checkout of the S-IC-7 began on
August 14, 1967 This activity was completed
on November 13. Maximum incentive points were
earned for achievement of this milestone, but
they a r e being held in abeyance pending negotiation of SA MICH -662 (see page 3). The stage
was placed in storage on November 22, 1967.
" _*-""f
Figure 2-6 shows the S-IC-7 in storage in the
Michoud factory building. On March 13, 1968,
the S-IC-7 began installation of Systems "A" instrumentation (hardwire instrumentation for
static firing purposes only) and incorporation of
committed modifications. At the close of FY 1968, the
stage was scheduled to be delivered toMTF (to begin
preparation for static firing) onSeptember 13, 1968.

.

S-IC-6
The S-IC-6 was undergoing post-manufacturing checkout at the end of FY 1967, Post-manufacturing checkout was completed on July 24, 1967, with customer
acceptance of the simulated static firing test. (Maximum incentive points of 299.6 were earned for attainment of this milestone. ) The stage remained ak. Michoud through February 1968 for storage, inst&amp;&amp;%ionof

Figure 2-6

S-IC-7 Stored in Factory Building

�S-IC-8
Vcrtlcnl nssembly of the S-rC-8 was completed Septcmbcr $1, 1967 imnc? hoz.izontni assembly begon the following clay. (Figure 2-7 shows the S-IC-8 invertical assembly and F i w c 2-8 shows ft being removed from the
vcll.tict11 position in the RIichoud V A B , ) Due to modifications to thc ~vorkingschedule, the vehicle remained
in a fitctory work position for horizontal assembly and
morlificaliw incorporntion until May 110, 1968, when it
was tmnsfcrred to a factory storage position where i t
will remain for an indE.finite period.

Several proposals have been made during the past year
to initiate a factory verification test with the S-IC-8
vehicle. This test would consist primarily of a proof
pressure test Eo check for leakage in the LOX and fuel
tank systems, At one time, in mid-March 1968, dl
preparations were completed and readiness reviews
were held with the Mickoud Operations Manager, but
performance of the test in the factory was suspended
a t the last moment by NASA directive.
S-iC-9

All major structure@for the vehicle were completed
furing FY 1968. Vertical assembly was completed
February 22, 1968, and horizontal assembly began the
following day. Horizontal assembly was completed
June 17, 1968, and the vehicle began a period of modification incorporation. Figure 2-9 shows F-1 engine
installation in an S-IC stage during horizontal assembly,
Delivery to the Michoud Systems Test organization for
post-manufacturing checkout is presently scheduled for
November 14, 1968,

Figure 2-7

S-It-8 i n Vertical Assembly

Figure 2-9

Figore 2-8

28

S-IC-8 Being Removed From VAB

F-1 Engine installation

in S-IC

A l l major structures for the S-IC-10 were completed
during the past year. Figure 2-10 shows completed
S-IC propellant tank being moved from the Michoud factory building. Vertical assembly of the stage was
completed June 18, 1968, and horizontal assembly began the following day. Delivery to Systems Test for
post-manufacturing checkout is presently scheduled
f o r Junuary 22, 1969.

D5-1260 1-5

�?,

*

-".***---

-)r*$,

m--~-7*.-.e.*Cw-"w-*;P"Q.~*1

-

'

r* --'
rr*.llla"W?
t

I

I

included one refurbishment unit for RP&amp;VE and two
KSC generd units.

?

9

i

1.
f

1
.*

.

---

Figure 2-16

---__-- -.
---

'$
\

11Y---

S-iC Propellant Tank Being Moved
From Foctory

During the past year, CCP 9289 (launch support hardware at KSC) , which established Michoud as the focal
point for umbilical refurbishment, was initiated. Under this concept, all five of the S-XC umbilical carriers
installed on a LWT will be removed from that LUT after
a launch and returned to Michoud for refurbishment
and updating. The present contract provides that a s e t
of umbilicals be supplied for launches through the
S-IC-15 with replacement of the units on each LUT after
the last presently scheduled launch. Assembly i s now
in progress on sets for the S-IC-4 and -6 and production support.

*.I

- .Jd

S-JC-IITHROUGH -15
Assembly was started on the 3-XC-11 through S-IC-14
vehicles during the past year. Several of the major
structures for the S-IC-11 have been completed. Assembly is proceeding as scheduled on the S-IC-11
through -15. Figure 2-11 gives the percentages of
completion on S-IC-11 through -15 major structures
a t the end of the report period.

The remaining three units of Modification 122/174
pneumatic equipment were deivered to KSC during the
past fiscal year.
The helium and nitrogen sections of the LUT #3 pneumatic console were returned to Michoud Operations by
Engineering Laboratories in mid-August 1967 following completion of a life-cycle test, Refurbishment and
updating of the two units was accomplished on an accelerated basis, and the last of the two units was delivered to KSC on January 5, 1968. The third unit,
the LUT Number 3 pneumatic checkout rack Number 2,
was delivered to KSC on January 17, 1968.
S-IC STAGE SUPPORT EQUIPMENT

Figure 2-1 1

Percentage Complete
June 27, 1968

-

S-IC stage transportators
Due to the revisions
to the vehicle delivery schedule during the past
year, S-IC stage transporters have become the
pacing item in the completion of vertical assembly at Michoud. This is due primarily to the
length of time the transporters a r e required to
stay at KSC , and the number of vehicles in process at MAF in the horizontal position. At present, plans axe being made to work around the
transporter shortage problem by placing vehicles
in horizontal assembly on storage stands. T o
provide a more definite resolution to this problem, action will also be taken in the near future
to attempt to have transporters released from
KSC as soon a s a vehicle is erected.

b)

S-IC forward handling rings
The provisioning
of handling rings to support the lift and join of
the forward skirt has become an a r e a of concern during the past year. Because the S-IC-3
handling ring could not be released in time to
support the S-TC -10, it became necessary to
erect the S-IC-F vehicle in the VAB and change

- Major Structures

GROUND SUPPORT EQUIPMENT

KSC EQUIPMENT
Thirteen end items required by MICH 112, CCP 9001,
were delivered during the past fiscal year. Fifteen end
items remain to be delivered.
T h e last three units of Modification 123/185 umbilicals
were delivered in the past fiscal year. These units

D5-12601-5

-

a)

-

29

�out i t s aluminum handling ring for anPIISFC supplied
steel handling ring. Yet even with this measure, it
was necessary to waiver postproof-load test impectionin order to lift the forward s k i r t on schedule,
The 5-16-3 h,wdlng ring i s now programmed for
turnar*aund utfllzntian on tho S-IC-11 vehicIpt,
and again does not support the MAF demand date,
El oivever , efforts a r c now being made to accelcr:dc releaso of this handling ring from KSC ,
and with the use af premium time effort during
rccyclo teat, the problem may be resolved.

DESIGN AND
ENGINEERING
S-IC ENGINEERING DOCUMENTATION

other committed changes. There were 3679
documentation packages released, of which 1961
were retrofits.
Documentation releases associated with change action
consisted of the completion of documentation for 117
chmgus ars listed in Appendix A, Changes initiated
included 185 ECPs, 25 PRRs and 8 CCPs for a total
of 218 changes a s listed in Appendix 3.
During F Y 1968, Boeing Engineering worked ~ l o s e l y
with the Computer &amp;fences Applications organbatian ta assure that the Automtitic Rdeass &amp;atem
conversion from Honeywell to Univac computing
equipment was successful. As a result, a high level of
confidence can now be placed in the Automatic Release System, and the quality and timeliness of the
required reports are excellent.

S-IC STAGE WEIGHT STATUS
Engineering dncumentatfon releases for F Y 1968were
of a sustaining nrtture and consisted of retrofit and

The final S-IC-1 stage dry weight a s determined by

�the weight and balance log was 307,550 pounds
pounds over the Contract End Item (CEI) speci
tion weight of 305,284 pounds. The final S-ICdry weight a s determined by the weight and bal
log was 306,159 pounds. This final weight is 137
pounds under the CEI specification weight of 306,2
pamde, T h s calculated dry w i g h t of the S-IC-3
stage for which Boeing has responsibility has increased 353 pounds during this reporting period.
The F-1 engine weight did not change. At this ti
Bocing is 669 pounds under the specification wei
for 5-16-3. Variations in S-IC-3 versus S-f
weight are plo-d Q Figure 2-12, Those
do not include R&amp;D fnstswnentauon, which
with each vehicle (S-IC-2 through S-IC-5).
Figure 2-13 represents the CEI spectfication wei
CEI specification weight (less engines), 330
rent weight (R&amp;D less engines), current dry
(less R&amp;D), and dry stage weight {R&amp;D) for
S-IC-2 through -15, A comparison of current we
versus CEI specification weight for the S-IC-3 is
included.

- -

S-IC STAGE DESIGN
SERVOACTUATORS

-

Hydraulic Research servoactuator spring failure
During pre-static firing checkout of the S-IC-5 a t
NTF, the locks-off null position test revealed that
the Hydraulic Research (HR) servoactuators on engine
number four were not within specified limits, thereby
causing erratic response. The cause of this out-ofnull positioning was traced to broken torsional springs
that a r e designed to. preload the rotational mechanical
feedback mechanism in one direction to remove backlash in this portion of the actuator control loop.
Investigation revealed that the spring failure was due
to contamination during heat treatment,
As a result, HR servoactuators on the S-IC-1 were
replaced with Moog servoactuators, and we were
directed by NASA to replace the material used in Ihe
failed spring (17-7PH steel) with a material not
susceptible to s t r e s s corrosion. The actuators removed from S-IG-1 were used on the S-IC-2 after
incorporation of improved process 17-7 PH steel
springs, and Inconel 718 was selected a s the new
material for the S-IC-3 and subsequent stages.
Servoactuator s t r e s s corrosion- Failure of a Moog
50M (MSFC prmured) servoactuator occurred during
bench test* at MSFC in February 1968, Severd
other failures were subeequeatly dfseovered on

D5-12601-5

tor bodies at both Moog and MSFC, MetalluranaIysis of the f i r s t f a i l u ~ eindicated that s t r e s s
osion cracking occurred at the parting plane of
e forged body, which m e constructed of 7075-T6
uminum. ~ e c a u s ethe S-1C-2 had four actuators
this model installed, a change was initiated to reme them with BOB (Boeing procured) servoactuars. Boeing procured servoactuators were acceptable because additional processing controls, to
minimize residual tension stresses on the surfaces
f the actuator bodies, had been imposed during
abrication, As a result of the above events, both
Moog axl Hydraulic Researoh (Wlt) servollnkratDrs
a r e being redesigned, and a test program for comparing s t r e s s corrosion resistance of 60B and 50M
actuators has been initiated. 7075-T73 aluminum
will be used a s body material for both the Moog and
HR servoactuators, The Moog cylinder will remain
4340 steel while the HR cylinder will be changed to
7075-T13 aluminum. Miscellaneous other components win require processing modification to preclude s t r e s s corrosion. Test evaluation procedures
for comparing 60B and 50M servoactuators will
include accelerated s t r e s s corrosion testing bv
alternate immersion in 3.5 percent salt water and
X-ray diffraction measurements to determine residual s t r e s s levels on actuator body surfaces. Completion of the actuator redesign program is scheduled
to provide production parts for use on the S-IC-6.
The 6 0 3 (Boeing procured) 50M (MSFC procured)
comparison study is scheduled for completion in
September 1968.

-

Servoactuator redesign to eliminate s t r e s s corrosion
and hydrogen embrittlement - Change Order MICH
738 directed Boeing to redesign servoactuators to
eliminate all s t r e s s corrosion and hydrogen embrittlement susceptible materials, A review of all
materials used in servoactuators has been conducted
and material changes will be accomplished.
Servoactuator electrical filter design-During S-IC-1
static firing, unexplained electrical noise in the Moog
servoactuators input signal, accompanied by random
movement of the actuator, was experienced, fnvestigation revealed that the observed noise resulted
from vibration of the servoactuator torque motor that
occurred in sufficient magnitude to saturate the flight
amplsier and cause loss of actuator control. A
change was initiated to reduce the noise level of
Moog servoactuators on S-IC-3 through -10 by the
use of a filter assembly that has been successfully
tested in actual firings on the single-engine stand a t
MSFC during &amp;ne 1967, On August 31, 1967, S-IC-5,
the f i r s t stage equipped with the flight configuration

31

�i-

CEI SPEC.
WEIGHT

S- l C-2

-

BOElNG CURRENT
WEIGHT (R&amp;D)
(LESS ENGINES) (LESS ENGINES)

~ E SPEC.
I
WT.

306,296

" AS REPORTED BY THE F l N A l WEtGHT AND BALANCE LOG. .

S-I C-3 WEIGHT STATUS

12-30-67

6-27-68

CHANGE

305,435
211,976

305,788
212,329

4.353
+353

7,931

7,931

0

304,681

305,498

+817

212,181
7,847

212,998
7,847

t817
0

I, CURRENT WEIGHT
A. DRY STAGE (INC. R&amp;D)
B, DRY STAGE (INC. R&amp;D)
(LESS ROCKETDYNE)
C. RESEARCH AND DEVELOPMENT ilR&amp;D)
II.CEI SPECIFICATION WEIGHT
A. CEI SPEC. WElGHT (INC. R&amp;D)
B. BOEINC PORTION, CEI SPEC.
WEIGHT f INC. R&amp;D1
C. R&amp;D, CEI SPEC. WEIGHT

RESEARCH AND DEVELOPMENT INSTRUMENTATION (R&amp;DI (CURRENT)
S- 1 C-2
S- IC-3
S- IC-4
S-1C-5

7,950
7,931
5,407
5,177

POUNDS
POUNDS
POUNDS
POUNDS

C

Figure 2-13

32

Breakdown of S4C Stag6 Weights

D5-12601-5

�filter msembly, was static fircd at MTF, and malysis of thrust vector control data showed that actuator8
equipped with the filter asr;embly performed within
end item test plan requirements,

ELEMRICAL 01STRIBUTORS
During FY 1968 the Electrical Distributor Qualification Test Report was revised to incorporate certain
exaggerated environmental test results and minor
changes requested by MSFC , including changes to determine the effect of foam fn electrical distributors.
Testa were conducted on cr distributor without foam,
and results indicated that foam did not affect component o r structural dynamic responses. To eliminate
concern with foam expansion, deletion of BMS 8-38
Sta-foam from electrical distributors wm proposed,
However, this modification was disapproved by NASA.
Inspection of printed circuit boards in electrical distributors revealed that some solder joints were
cracked. Analysis indicated that the cracked solder
joints were caused by differential rates of thermal
expansion between component leads and board material, Environmental tests, thermal shock, and vibration verified the functional integrity of printed circuit
boards with cracked solder joints. To eliminate
cracked solder joints, manufacturing processes were
revised to reduce stress in solder joints, and redesign of printed circuit board was initiated to provide strain relief for susceptible solder joints.
An electrical distributor redesign study was initiated
dufing the reporting period. This study will define
distributor design criteria and investigate application
of advanced packaging, interconnection, and termination techniques to electrical distributors. The study
goal is to determine methods of improving distributor
maintainability.
During rework of S-IC-3 spare distributors to S-IC-1
stage configuration, misaligned and protruding contact members were noted in methode printed circuit
card connectors. Subsequent discrepancy inspections
revealed that these conditions were prevalent in a
large percentage of installed connectors and in new
connectors in stores. Cracked contacts were also
noted in a number of connectors during these inspections Investigation revealed that the conditions
were not design discrepancies, but resulted from inadequate control of materials and dimensions, which
is inherent with parts procwred to vendor part n m bers with no control by the procuring activity, To
provide tighter c&amp;ols atld to assure producti~nof
eatiafa&amp;ry parts, a cormecEor specification was

.

335-12801-5

originated, and a change was initiated to replace the
FD744-%-SF connectors with MBC455 connectors on
S-IC-3 and subsequent stages. Since no failures of
the FD744-%-SF connectors had occurred during
qualification, reliability, development, subsystem or
stage level tests, or during numerous static firings,
they were retafned on S-Ie -1 and -2,
Figure 2-14 illustrates the S-LC power distribution
system,

Figure 2-14

S-IC

Power Distribution System

LOX FllL AND DRAIN VALVES

During countdown demonstration testing of the AS501, LOX fill and drain valves were found to be leaking. Analysis of the valve failure revealed a eircumferential crack in the main seal, which is believed to
be caused by severe thermal stresses induced in the
teflon seal when it contracts, at cryogenic temperatures , at a rate faster than the surrounding metal.
These stresses could also be enlarged by tolerance
buildups, high flow rates, or valve cycling. This
failure could not be duplicated during follow-up testing by the vendor, Parker Aircraft Comp+ny. Boeing
assumed the risk of flying the S-IC-1 and -2 without
changes to these valves. These decisions were
based on the following:
a)

The valve has been installed in 18 locations
per stage on the 8-1 and S-I3 stages with no
eimilar failures experienced;

b)

Only two other failures (one seal cracked and
33

�onc showing cvidcncc of a crack starting) of
this type had bccn experienced on the S-IC stage;
c)

A review of quality records was unable to attributc the failure to any specific lot of seals. Visual examination of approximately eight other,
scals , inclucting one from the e.me lot as the
S-IC stage valves, revealed no additional
cracked seals; ,and

d)

Analysis indicates a high probability that any
leakage would be GQX rather than LOX in the
in installed valves. In
event of a cracked ~t?d
addition, the SA-501 mission revealed only
gaseow leakage in the valve area.

ORtGlNAL DESIGN

S-IC PROPELLANT DISPERSION SYSTEM

-

Installation interference As a result of the problems encountered during installation of the Flexible
Linear Shaped Charge (FLSC) on both the S-IC-1 and
-2, the ordnance cowling installation has been redesigned, The redesigned cowling consista of m openfaced box with cover plate, and allows lateral insertion of the ordnance. Rework operations on the
S-IC-3 ordnance included cleaning of the existing
propellant tank cowling and replacement of the cowling on the forward skirt and intertank with the openface and cover-plate configuration mentioned above,
The propellant tank cowling was reworked rather
than removed because this cowling is bonded to the

REDESIGN

1
:iguse 2-15

LOX Fill and Drain Valve Redesign

The vendor has redesigaed the main seal area by
splitting the existing one-piece seal into an internal
dynamic seal arsd an external static seal (see Figure
2-15), An additional row of circumferential springs
on a metal seal back-up contains the internal dynamic seal and provides the sealing surface. The new
design has been subjected to limited qualification
tests to assure that all design requirements can be
met, and the redesigned valves will be incorporated
into S-IC-3 and subsequent stages. However, qualification testing revealed that existing test procedures
could allow a valve to qualify and yet experience
leakage in stage use after repeated dry cycling during
stage test and checkout. This condition has been
evaluated by Engineering with the conclusion that the
condition is an acceptable risk for the S-IC-3 Mght.
However, efforts to resolve the problem are
continuing and Engineering will initiate changes
proposing the development and procurement of an
improved design.

34

tanks and rebonding requires environmental control
that is not available at KSC On S-IC -4 and on, the
existing bonded cowling is being replaced with the
new, open-face cowling.

.

-

Support bracket failure During a routine inspection
of the S-IC-1 fuel dispersion system installation, it
was discovered that 31 support brackets had become
unbonded. Investigation concluded that this failure
resulted from sustained load application to the support brackets. This situation has been avoided on .
subsequent vehicles by assuring a clearance between
the cowling and the support strap. The failures on
the S-IC-1 were dispositioned by removing the failed
brackets and support straps. On the S-IC-2, failed
brackets were removed, all support straps inspected,
and shims were installed to provide desired clearance,
An inspection of the support bracket installation on
S-E-3 and -4 reveded only one failed bracket on the

D5-12601-5

�EtECTRlCAL INPUT

OMMAND DESTRUCT

I
Figure 2-16

J

S-IC Propellant Dispersion System

S-IC-3 and none on the S-IC-4. All support strap
installations were inspected and reworked as required on all subsequent stages. Figure 2-16 is a schematic of the S-IC' propellant dispersion system.
PROCEDURES FOR CHANGE-OUT OF TIMEICYCLE
SENSITIVE ELEMENTS

LOX ENGINE CUTOFF SENSORS

-

Solar Cell Redesign The LOX engine cutoff sensor
solar cell has been replaced with a solar cell that is
reliable at cryogenic temperatures. This action was
taken because the previous solar cell had a history
of failures.

-

During FY 1968 a change was initiated to resolve
difficulties encountered in controlling time, cycle,
or age sensitive S-IC parts, and to implement a new
50 percent life requirement at stage delivery. Life
limit requirements, which were originally listed in
Document D5-12713, will be released as new Class
I documentation. The new Class I documentation
will define the life limits and life apportionment by
test phase of all S-IC time, cycle or age sensitive.parts. This documentation will also define the disposition of parts a t the end of life limits and, if parts
can be reworked, the work necessary to restore the
time, cycle, or age life to zero.

Center Engine Redundant LOX Cutoff Sensor A new
optical LOX engine cutoff sensor was developed, for
installation in the center engine LOX duct, to provide
a redundant method for initiating center engine shutdown upon LOX depletion (see Figure 2-17). This
change is effective on S-IC-2 and S-IC-4 and subsequent stages. This change is not necessary on the
S-IC-3 because the center engine on this stage is
shut down by a timed signal from the instrument unit.

LOX VENT AND RELIEF VALVES

A redesign of the position switches on the LOX vent

�and relief valves was initiated to resolve the following problems:

a)

Oil contamination could result in switch failure
causing countdown delay due to the LOX vent
valve position interlocks; and

b)

The actuator post-to-spring spotwelded joint
failed during the S-IC-2 CDDT , resulting in an
electrical short and loss of "open" position
indication, which caused CDDT delay.

PARKER VALVES STRESS CORROSION

To eliminate the possibility of s t r e s s corrosion in
the Parker Normally Closed IN.C ) Fill and Drain
Valves (LOX and fuel), N. C LOX Interconnect
Valves, and Normally Open (N. 0. ) LOX Interconnect
Valves, the actuator housings of these valves were
reheat treated to a 7075-T7351 condition. This
change was initiated on stages S-IC-2 and on because
failure of the actuator housings could result in loss
of actuator pressure that would cause closing of the
N C , valves and opening of the N .O vaIves If
this occurred during fuel and/or LOX fill operations,
the fuel and/or LOX fill and drain lines could rupture
because the GSE would not be able t o shut off the fuel/
LOX supply in time to prevent excessive surge
pressures.

.

.

.

.

.

LOX INTERCONNECT VALVE
During the reporting period three Whittaker LUX
interconnect valve shafts failed, and a fourth was
f
d to have circumferential cracks, that were

36

identical to those found on the three failed shafts,
indicating a potential failure. Of the three valves
that failed, two failed during functional testing, and
the third failed during reliability test cycling. Seven other valves were disassembled and their shafts
were magnetically inspected. Of these seven,
one was found to have circumferential cracks
on the shaft.
To prevent such failures, which would render the
valve inoperative, the shaft material was changed
(S-IC-2 and on) from 440C to Inconel 718, heat
treated to 180,000-200,000 psi.
F-1 ENGINE LOX SEAL PURGE REGULATOR

The LOX Seal Purge Regulator is a flight critical
component that has been subjected to prolonged operating time during prelaunch test activities at KSC
Because this additional operating time was not anticipated during initial design and testing, a reliability
test program was initiated to simulate five complete
life cycles. There were no critical failures on three
test regulators each of which waa subjected to a total
of 840 hours of operation to satisfy the reliability
test that simulated static firing, prelaunch, flight
environments, and service times, A burst test will
be conducted using one of the reliability test regulators to determine any detrimental effects the reliability Iff@~ y ~ f might
b g have h%dBI t
h rfa@atorr
This @&amp;tier erck@&amp;ledto kgin in Augwt 1988,

.

RETROROCKETS

-

During FY 1968 there have been several major

D5-1260 1-5

�problems concerning S-IC retrorockets. These problems and their resolution are:

-

Propellant cracks, voids, and separation Problems of this type have occurred on S-IC retrorockets.
'
I
o solve such problems as they arise, Z'hiokol Chemical Corporation (the vendor) details propellant problams on Material Review Board (MRB) forms, submits the MRB forms t b Boeing Engineering for approval, and then proceeds to take the approved corrective actio~.
Localized thin aroas in rocket cases

- During a

drwwintJ operation that ww used in ttra rnfu~uf~oftrre

of rocket cases, longitudid thin strips, called
creases, were generated in the case walls. To resolve the problem, a stress analysis was made on
each case-to determine the maximum pressure each
would withstand. The three cases with lowest wall
thickness in the creases were then hydroburst.
These operations indicated that the remaining creased
cases were acceptable insofar as design strength requirements are concerned.
Overdrilled holes in rocket cases and out-of-round
rocket cases These problems were resolved by
stress analysis and the test firing of one rocket. The
test rocket had an unacceptable out-of-round condition, and the 1/4 28UNF holes in the head end were
overdrilled, Thiokol created a "worst possible''
condition in the roeket by extending the already overdrilled holes through the case and into the propellant.
The bolts were installed and the rocket was fired
resulting in nominal performance parameters and no
evidence of case deterioration due to either discrepancy.

-

seconds to T+135 seconds, a significant longitudinal
oscillation of 5 cps built UP and then died out after
reaching maximum at T+126 seconds. Acceleration,
thrust, and propellant pressures were all in phase,
indicating a closed loop instability, called POGO,
that limit cycled, Accelerations reached 0.8 gts
peak-to-peak at the Command Module interface and
0.4 g's peak-to-peak on the S 4 C stage. These
oscillations can affect payload structure and impair
the effectiveness of the astronauts, The Crolution t;o
this problem involves a change to the LOX delivery
system to effect a change in propellmt line freqwncier , t;heeeby dsloclupli~the orsefllatfm and estaXslishing stability. A full-scale analysis is underway
to determine and incorporate the solution to this
problem prior to the S-IC-3 launch.
Several POGO solutions have been considered, and
the two prime corrective systems currently being
considered are a helium injection sysbm (ECP 0442)
and prevalve accumulators with helium injection
fECP 0446). A brief description of these systems
follows.
a)

This system involves injection of gaseous
helium into the upper portion of the LOX suction ducts through existing bosses of the four
outboard engines during the time that POGO
could occur. The helium supply will be tapped
off the high pressure side of the stage helium
manifold, then routed through shutoff valves,
regulators, and orifices to manifolds located
in the intertank area, and then through check
valves into the suction ducts.

-

S-IC-1 and S-IC-2 flight retrorocket performance
exceeded prediction Both the S-IC-1 and S-IC-2
flights have revealed retrorocket motor performance
in excess of that predicted. Pressure transducers
are used in flight to measure the performance of each
of the eight retrorockets. Investigation revealed that
Tkiokol uses tubing filled with grease to measure
performance while the Boeing instrumentation is
coupled directly to the pressure chamber and exposed
to direct pressure and temperature transients. Because flight performance was predicted on Thiokol
measurements, it was necessary to run comparative
instrumentation tests, The results of this testing
indicate that flight instrumentation read high in an
indication of excessive performance. Final reso*
Iution of tNta problem i s not complete for W8
report;fng period,

-

POGO

During the S-IC-2 flight, in the period from T+110

D5-1260 1-5

Helium Injection System (ECP 0442)

b)

Helium P revalve Accumulator System (ECP
0446)

This system involves injection of helium gas
into the LOX prevalve cavities, thus enabling
the prevalves to serve as accumulators. Onboard helium will be provided by tapping off
the high pressure side of the helium manifold.
As a result of the POGO resolution effort an extensive
testing program has been undertaken by Boeing Schedule I, Numerous component tests, development, reliability, and qu&amp;f1cation, have been initiated to help
raaolve thia problem. A LOX suction duct flow test
fixture, which is being used to test dynamic
characteristics of suction lines as a result of
proposed POGO suppression s y s t e m , has also
been constmcted at Michoud,

37

�AIR SCOOP BIMINATNIN
hfSFC hnx ngrccd to delete the base air scoops for
st,ngc,s S-IC-3 and on, This i s being done because
nnnlysis intficatcs that the base air scoops used on
the S-IC a r e not rrqulrcd to maintain temperatures
in tho base rugtan within ncceptztblc levels. The 5IC-1 flight verified this m d y s f s when the data was
cx,unined and thc actual base environment was found
to be much less scvcre than the design environment.
This data indicnted that air scoops were not necessac far coaling, Scoop elimination was also desirnblc Imm thc et.mdpoint of weight (a~&gt;proximably
,500
Ibs,), cost, and possible interference with LUT hardware during llft-off; and a chmgc to provide a rain
cover ovcr t h scoops
~
to prevent deflection of rain
water on thc fnsulatcd base area surfaces will also be
avoided by scoop elimination. Data from the S-IC-2
flight confirmed that the scoops are not required.
The base environment on the S-IC-2 was more
severe than S-16-1, as expected, but still less
than design levels.

HEAT SHIELD

-

Heat shield material
The basic ingredient of the
&amp;I-3 1 ccramic hsulation originally used on the heat
shield was Tipersul. Therefore, upon notice from
the I)upont Company that production of Tipersul would
be discontinued, Boeing stockpiled a supply to support estimated S-IC requirements. However, due
to an unexpected high usage rate in production
and refurbishment operations, the stockpile
proved insufficient.
As a replacement for M;3 I, the MSFC M&amp;P Laboratory developed a new insulation, FTA 442A. The
Rohr Corporation performed development tests and
fabricated production panels with the new insulation
f o r qualification. Tests were run subjecting the
panels to the predicted flight environmenb. As a
reliability test, panels were subjected to an additional 140 seconds of acoustic test with minor damage, In a separate test, engine shutdown followed by
a flight cycle was simulated with favorable results.
Based on preliminary data and reports, the new
mateda.1 appears more than adequate for flight use,
and will be used, rather than Tipersul, for the heat
shields on S-IC-I0 through -15.
"

-

Heat shield delamination During the S-IC-1 flight,
two thermocouples located on the heat shield a t holddown M i t i o n III indicated a sharp temperature rise a t
approximately T+110 seconds. During the S-1C -2
flight, two thermocouples located on the heat shield

38

at holddown Position Il indicated a sharp temperature
rise at T+96 seconds. These anomalies were attributed to cracking and/or delamination of the M-31
ceramic insulation. TV camera film at Position I on
the S-IC-2 flight showed a triangular area of delamination approximately 10 inches on each side, bat no
thermacouples axe installed in this area to record the
effects of the delamination. This problem appears to
be localized because average coldside and brazeline
temperatures were 72OC and 185OC, respectively,
These low average temperatures indicate that, even
though local damage may have occurred, the heat
shield remained effective. Additional vibration and
acoustic measurements will be included on the S-IC-3
heat shield to determine the cause of the delamination.
FORWARD SKIRT TEMPERATURE

Insulation was applied to the S-IC-1 forward skirt to
prevent high temperatures. Data received from the
S-IC-1 flight indicated that temperatures were lower
than anticipated. However, because the insulation
thickness was not strictly controlled, this data is not
completely reliable. Therefore, controlled thickness
insulation will be placed on the S-IC-3 at thermocouples, and temperature data will be gathered during
its flight. If this S-IC-3 flight data indicates that insulation is not required, it will be eliminated from
S-IC-4 and subsequent stages.
STAGE RAINWATER DAMAGE

While the S-IC-1 was on the pad at KSC, rainwater
entered the thrust structure area through the electrical cabling access opening underneath the electrical
tunnel and caused water damage to certain electrical
components. To prevent rainwater from entering the
stage, a type of adhesive tape was applied to the
electrical and pressurization tunnels and other affected areas on S-IC-1 through -3. Because this tape
application is a temporary measure, rubber and
metal seals will be installed on the S-IC-4 and
following stages.
FORWARD UMBILICAL DOOR

Film taken of the launches of the S-IC -1 and -2 disclosed that the forward umbilical door interfered with
the umbilical disconnect cable at liftoff and remained
open during flight. Although no apparent stage and
only slight umbilical damage resulted, the forward
umbilical door was redesigned to prevent interference
with the disconnect cable and to ensure proper closure
of the door during Right. The change was made for
S-IC-3 and on, but the change could not be made to
the S-fC-2 due to schedule impact.

D5-1260 115

�measurements. Of the 880 active measurements,
865 provided valid data.

OESICCANT FILTER UMlTS

The desiccant filter unit is comprised of a particulate filter, which is 100 percent efficient in removing
particles 50 microns or larger, and a silica jell
desiccator which ha$ the capability to reduce the
relattve hum?tdiw of Znnawiw air frum 98 percent to
65 percent. NASA has reviewed the application of
desiccant filter units to be used on the S-IC propellant
tanks and approved their usage during all MAF operations, This change constitutes a major cost reductien because the prc%viowlym a d positive greseurization ayrtrttn required c m a t monitorif af the equipment. The desiccant filter systam requires monitoring only to the extent of changing out the desiccant
portion approximately unce each seven to ten days.
.
The mags of the desiccant alter system on propellant tanks of the S-IC stage in storage was applied
earlier, and its usefulness and convenience has been
establshed. Recently, relative humidity samplings
of the tank interiors were found to be well below a
new customer requirement of 40 percent maximum.
SLOW RELEASE MECHANISM

Boeing Schedule I and II were concerned about the
number (12) of slow release mechanisms (SRIVI) and
the possibility of inadequate lubrication of the SEW
with the KSC procedure of greasing after SRM assembly of the pin in the die.

,

Three spares S-IC-2 slow release mechanism, lubricated to a new KSC procedure, were pulled in the
MAF laboratory. The peak extrusion loads of
66, 63, and 69 kips were in the low portion of the
range of peak loads obtained during the developmental
test program, Loads analyses, with 12 SRMs having
these latest test data characteristics, indicated that
although the vehicle responses have increased, in
all cases these vehicle responses remained within
design limits. Also, the time required for SRM extrusion had dropped indicating less probability of
AS-502/LUT interference than would have existed
with a 16 SRNl configuration having peak force values
of the original specification. Therefore, a properly
instrumented 12 SRM configuration using thc4 new
KSC SRM lubrication procedure was used on S-IC-2
and will be wed on S-IC-3.
1NSTRUMENTATFON

-

Flight measurements On the S-IC-1 flight there
were 854 active and 18 waived measuremeats. Of
the 854 active m e ~ u r e m e n t,s 831 provided valid
data. The S-IC-2 flight had 880 active and 13 waived
.

-

Thermocouple bond failure Thermocouples bonded
to the LOX and fuel tank surfaces became detached
during flight and gave erroneous data. Improved
bonding methods have been developed aad all taak
surface measurements on S-IC-3 through -5 will
be rebonded.

-

-

Engine area vibration data
Sptwious high amplitude, low frequency ~ u t p u bhave invdidaO;(admuch of
the vfb~aionand acwstlc date o b t a e d during static
firings and the S-IC -1 and S-I@-2 Rights. This problem is concentrated in the engine area, and is caused
by the emitter followers and AC amplifiers being
overdriven by excessive piezoelectric transducer outputs. The high transducer outputs are caused by
high amplitude, high frequency shocks that are generated by uneven engine combustion. To resolve the
problem on S-IC-2 though -5, a change was initiated
which removed seventeen engine area vibration transducers that had se~aratelvpackaged emitter followere and interconnecting coaxial cables, and substituted seventeen transducers that have integral emitter
followers with a higher output capability. S-IC-2
flight data indicated that this change considerably
reduced, but did not eliminate, the problem. Another
change has been initiated to add a capacitor to the
AC amplifier input to block low frequency noise signals. This change is effective for all engine measurements on S-IC -3through -5, and should reduce the
high amplitude, low frequency outputs to a level that
will not interfere with accurate measurements.

-

LOX pump inlet pressure measurements The
60B72091-1 transducer used on the LOX pump inlet
high frequency pressure measurements has consistently failed during static tests and flight. These
failures are apparently caused by physical shock
while the transducer is at LOX temperature. These
measurements are important for the detection and
evaluation of POGO. To determine the best corrective
action for this problem, several new measuremente
will be made on the S-IC-6 and tested during that
stage's static firing. These new measurements include relocation of the subject transducer to a less
severe environment, replacement wlth a prototype of
a more rugged design, and determination of the
feasibility of using existing measurements for detection of POGO-indbed pressure oscillations by increasing the sampling rate.
Fuel filter manifold differential pressure transducers -- f mes€igation afthe fuel filter manifolddifferenUalppessure trsn8ducgrbiaashift problem revealed that

-

D5-1260 1-5

39

�LEGEND
1. YAGI ANTENNA
2. TRANSMITTER
3. -28 VDC
4. VIDEO REGtSTER
5. TO SYSTEM 2
6. CAMERACONTROL
7. TV CABLE ASSEMBLY
8-CAMERA
9. COUPLING LENS
10. IMAGE ENHANCER
11. DC TO AC INVERTER
12. FIBER OPTICS BUNDLE
13. JUNCTION BOX
14. OBJECTIVE LENS
15. PROTECTIVE WINDOW
16. INSULKTION BLANKET

shifts can be induced in the transducer by prolonged
temperature soak at 130°C. However, after 1200
hours af soaking, test transducers showed no decrease
in shift rate with time. Extensive studies by the
vendor produced design modifications that were
thought to eliminate stress in f i e seneor unft aesem-

40

bly, and thus eliminate the shift problem. Prototypes
of the new design, however, showed no improvement.
A new design consisting of a single diaphragm with a
depasited thin-film strain gage bridge is being investigated. This design m d d eliminate the need for a
reference bellows and silicone ofl fill, Also, the new

D5-12601-5

�tfansducer would be of an all-welded construction which would minimize diaphragm stresses.
Two prototypee of the new design are being built
for evaluation.

-

LOX and fuel loading system During 6-IC-1 checkout, tbe loading system "out-of-lock" monitor that is
used ae an interlock in the propellant tankkg computer
system (PTCS) operated intermfttently. This waa
caused by the loading electronics being susceptible to
stage noise under certain conditions. The pr6blem
w m corrected by a new design.

transfer tests. This problem was corrected by providing untnterrupted power ta the loading syetem.
During this reporting period, a change was released
to disconnect the checkout (RACS) cables from the
loading electronics for S-IC-1 and -2. This prevented
instrumentation test,, usfng the RACS system, from
upsetting discretes in the PTCS. A change waa also
released to provide control of the calibration commands to the loading system from the measuring and
R F console in the LCC for S-IC-3 and on,
S.IC fv SYSTEM

During LOX lotxding at MTF where LUX wm load&amp; Q
near 100 percent on the loading probe, the LOX overfill sensor intermittently indicated a wet condition.
This was attributed to LOX being splashed onto the
overfill sensor due to LOX boiling. This problem wae
corrected by moving the overfill sensor approximately
four inches forward.

The S-IC-2 was the first S-IC flight stage with the TV
system lastaIled. The system, which is detailed in
Figure 2-18, operated satisfactorily during pre-launch
operations and launch.

During the SIC-1 CDDT, power to the loading system
was lost durfng the power transfer test, upsetting the
propellant tanldng c o m p t e r system dfscretes. This
was caused by the loading eystem being powered from
GSE bueees that a r e turned off during the power

The S-fC-2 was the first S-IC flight stage with the
film camera system insta31ed. The Position X separatfon camera capsule waa the only capsule recovered,
but its fflm was washed out during the first five
seconds after separation. It is concluded ehat this

FILM CAMERA SYSTEM

�was caused by a combination of sun glare and S-II
ullage rocket deposits on the quartz protective
window, The action necessary to correct this problem will be accomplished on the S-IC-3 and subsequent stages. The W e e camera capsules, that were
not recovered, apparently were not ejected, Excesaive temperature and pressure environments immediately following separation -me suspected to have
caused faflure of the camera ejection pressurization
syrstem. The exact cause of this failure is still being
investigated, and changes being incorporated to prevent ita recurrence on S-IC-3 are:

from

a)

Change
pneumatic
to stainless isteel;

b)

Add orifices to prevent pneumatic line ruptures
from bleeding down the ejection bottles;

c)

Add thermal insulation to exposed protective
cover cables;

d)

Modify the GSE regulator system such that the
ejection bottle can be pressurized to a higher
pressure ;

e)

Add orifices to prevent pneumatic line ruptures
from bleeding down the ejection bottles;

f)

Add thermal insulation to exposed protective
cover cablea; and

g)

Modify the GSE Regulator System such that the
ejection bottle can be pressurized tu a higher
pressure.

Figure 2-19 illustrates the Camera Capsule Assembly.

�TELEMETRY SYSTEMS

-

DC-DC converter and DC power isolator DC-DC
converter (60B76 123) and DC power is01a h r
(60B76503)failures, due to incompatible production
procedures, caused a redesign of the assemblies to
provide more reliable componante, Also, NASA
disapproved the qualiQcation of the assemblies because of the under voltage rated capacitors used in
the vendor design.

-

'

Remote digital sub-multiplexer (RDSM) -ring a
sitnulaW flight test on ehe S-IC-2 at KSC, a 108s of
synchronization occurred on the pulse code modulation (PCM) telemetry link. The cause was traced to
a remote digital sub-multiplexer (RDSM) output word
containing nine logic llzeros" and one logic "one, "
while the preceding word contained ten logic "ones. "
Under these conditions, the RDSM output caused the
digital gate card in the PCM/DDAS assembly to
trigger erroneously and inject an incorrect bit into
the 30 bit PCM synchronization pattern. Duplication
of the problem in the Boeing electronics laboratory
indicated that the problem was due to cable capacitance
between the RDSM and PCM/DDAS assemblies. A
new digital gate card, with input capacitors that
masked the effect of the cable capacitance, was incop
porated on 5-IC-2 and subsequent stages. This
change was not required on S-IC-1 because of the
RDSM measurement profile.

-

Offset Doppler (ODOP)Transponder Boeing has
been unable to verify qualification of the Offset Doppler
(ODOP) Transponder to the Contract End Item Specification for the S-IC. However, sufficient data was
provided on the range safety decoder, and Boeing
concurs that the decoder is qualified for the S-IC
stage, Figure 2-20 illustrates the ODOP system,

GSE/MSE DESIGN
S-E PNEUMATIC EQUIPMENT

-

-

S-IC pneumatic console MTF The LOX dome
purge maximum lock-up requirement has been increased to 1200 psig and the lock-up pressure recorded from the S-IC-5 static firing was within this
limit, A change was also processed to put the low
purge on an orificed by-pass circuit to reduce the
service time on the regulator.
Analysis of S-IC-T static firing data indicated a
potential pressure overshoot problem on low h e 1
prepressurization when the fuel tank is at minimum
ullage. This pressure overshoot could cause the

D5-1260 1-5

stage fuel tank relief valves to cycle. Therefore, a change has been processed to assure that .
the stage relief valve will not be actuated under
normal conditions.
The high failure rate of the helium bottle fill regulator ham been corrected. Andyeie of S-IC-4 and -6
static firing data indicated a potential pressure overshoot problem on LOX prepressurization. Also,
calculations based on the static firing and launch data
indicated a potential pressure undershoot problem tm
fuel prepressurization during engine startup. A
change wae processed to corrsot thaae problems
prior to S-ZC-3 launch. This change will be verified during the S-IC-6 static firing.

-

-

S-IC pneumatic console KSC All systems met
launch mission rules requirements for S-IC-1 and
S-IC -2 launches. Subsequent to each launch, one
piece of equipment (forward umbilical service) was
found slightly damaged due to severe launch environments. Problem areas which became evident during the processing of S-IC-I, and S-IC-2 are:
a) A rupture of the GHe Primary Regulator diaphragm would'result in loss of LOX bubbling
capability and therefore jeopardize the stage.
A change was processed to add redundant
capability and was incorporated prior to launch.

b) Position of hand ball valves needed more positive control to preclude position change during
vibration and allow easy monitoring of valve
position. A change that provides position indication and locking was processed to rectify this
problem.
c) A considerable number of failures occurred in
Pneumatic Console solenoid valves. An extensive failure analysis program was conducted in
cooperation with the vendor and it was determined that serious seat deformation was occurring when valves were energized for extended
periods of time under high pressure conditions.
A development program was then initiated to
determine the best possible material to resist
the seat deformation and meet sealing requixements. Necessary changes have been made and
the valves have passed a rigid qualification test.

d) Numerous problems were experienced with the
primary module Ladewig pilot operated relief
valves during qualification testing for 5-IC-1
certification, Redesign of the valves was underW e n and accomplished prior to S-IC-1 launch.
Life cycle testing at ~ o e i n g / ~ i c h o uwas
d suc43

�cessful. The ncw valve c o a ~ r a t i o nuses a
pilot valve: separated from the main valve body
by flcsfble hoscs to correct a vibration sensitivit~;problem with the original integral pilot
mounting.

the subsystems of the S-IC stage handling equipment,
At that time, design, maintenance, proof load, and
inspection requirement responsibilities were divided
between Engineering, Operations, and Facilities for
various segments of the total handling equipment.

e) Two regulator failures occurred in the LOX
dome purge module during CDDT activities for
S-IC-2. The failure effects were identical, but
the failure causes were not. The f i r s t remla*
apparently failed due to operating the module
with the inlet manual isolation valve instead of
the LCC control. The mpsccrnd rdgtuIator had the
same law outlet pressure but had misaligned
poppet guide bores that resulted in abnormal
wear. A change that provides for incorporation of redundancy, and deletes the failed regulator has been processed.

Boeing Engineering was directed, on may 27, 1967
to accept responsibility for the forward lifting linkage assembly and the rotational brace assembly for
the Michoud VAB. A production revision record
was then established which, (1) provided a new forward hfting linkage assembly, (2) modified the forward handlfw ring b e t f ~ r too proof teet the new
forward lifting linkage assembly, (3) modified the existing rotational brace assembly, and (4) modified
the existing adjustment linkage assembly. This
equipment was used for the first time during lowering operations of the S-IC-10 in the Michoud VAB.

Mathematical models were constructed to simulate components, specifically valves and re@lators, in the pneumatic console, thereby facilitating prediction of in-flight operation of these
components. Results compared favorably with
test data. In addition, studies were made on
the necessity of adjusting pipe sizes at the inlet
to the pneumatic console to retard the introduction of facility contamination. Research has
continued on filtered flow restrictors designed
to reduce contamination while still regulating
fluid flow.

S-IC storage racks The storage racks that were
secured to the LUT during the launch of AS-501 were
damaged and their contents, including the bulkhead
protection equipment, were partially destroyed. It
was apparent from inspection of the launch damage
that the racks had been subjected to a more severe
environment than the environment furnished a s design criteria.

f)

-

-

S-IC pneumatic checkout racks KSC Tests conducted using the mechanical automation breadboard
(MAB) indicated that the pneumatic checkout racks
(PCR) a s presently designed a r e not capable of
meeting the customer accuracy requirements for
checkout of the S-IC stage LOX, fuel, and thrust OK
calips switches. This problem is twofold; first, the
ramp rates for pressurization/depressurization of
calips systems a r e too high, resulting in excessive
pressure change; and, second, the pressuretransducers cannot be calibrated to the required accuracy
of 5 -05 percent full scale due t o operation of the
transducers a t 16S0F. An engineering change will
be processed to eliminate the problems outlined
above.

GSUMSE TRANSPORTATFON AND HANDLING EWPMENT

-

-

6-IC stage handling equipment Xichoud VAB
H u e r o w rejections against the forward handling
ring and the forward Ufthg linkage aseambly brought
out the fact that major inconsistencies exfsGed within

44

-

An interim change was established to reinforce the
rack structural integrity and to provide additional
holes for venting the inside of the racks to outside
pressures. However, incorporation of this change
could not be made to support the AS-502 launch and
the launch caused even more damage to the storage
racks than AS-501. Damage to the bulkhead protection equipment was eliminated for S-IC-2 since the
equipment was relocated from the storage racks to
a room in the base of the LUT prior to launch. Subsequent to S-IC-2 launch, the interim change was revised to provide additional vent holes and structural
reinforcement on several of the LUT level 60 racks.
These modifications constitute an interim fix based
primarily on launch damage experienced during the
first two launches. The fix is planned for installation prior to S-IC-3 launch.
The major problem in redesigning the storage racks *
has been in defining the actual launch environment.
Adequate data to define the environment has not been
gathered because requests that the GSE equipment
a r d o r the adjacent LUT structure be suitably instrumented to collect data to define the actual launch
environment have been rejected, F i n d redesign of
actual launch environthe storage racks to susmen&amp; ia being held pending definition of the launch
environment.

D5-1260 1-5

'

�SWMSE

Intertank umbilical reconnect assembly

(a) The intertank umbilical reconnect assembly con-

,

taias a switch that provides a signal indicating
that carrier retraction has been completed. The
signal is used to initiate retraction of the swing
arm, and its failure can cause mission abort.
MSFC requested that a change be submitted to
incorporate a redundant "Carrier Retracted"
signal source. This was done, the design
qualfffed by tercrt, and the chan~qewse fncorparat*
ed on the LUT 1intertank umbilical reconnect
assembly prior to the S-IC-1 launch. This design change will also be incorporated prior to
the launch of all subsequent stages.

[b) A failure analysis of the intertank umbilical reconnect locking mechanism, which had failed at
KSC during swing-arm tests, disclosed a design
deficiency in that an adverse accumulation of
manufacturing tolerances could cause breakage
of internal parts. Breakage results in the malfunction of the locking mechanism, and prevents
a reconnection of the carrier to the S-IC stage.
Design corrective action for the locking
mechanism to support the S-IC-1 launch resulted
in an interim fix, which could be incorporated
by rework of existing components. Rework was
necessary to support the launch without impacting the schedule. The corrective action taken
for stages S-IC-2 and on resulted in a design to
prevent recurrence of the failure.
(0) The Boeing Company initiated a change for the
redesign of the intertank umbilical to include
backup capability for the retract system. Th&amp;
change resulted from a failure mode and effect
analysis and revealed that single
- -point failures
cwld prevent umbilical retraction. Also, a
request for change action has been initiated
by S-IC liaison at BATC requesting that the
single point failure be eliminated from the retract system. This change has been approved
with additional directions to eliminate single
point failure modes in the retract and reconnect
systems.

dl

During the extension of swing arm number 1 at
KSC, following the S-IC-2 overall swing arm
test, the intertank umbilical inadvertently became unlatched from the retracted position. The
event went unnoticed durfng the remainder of arm
extension a d as the gwlng arm approached full
extension, the umbilfcal struek the stage. Minor

damage, requiring no repair, was experienced
by the stage, but the umbilical LOX lines were
damaged to the extent that partial replacement
was required. Subsequent investigation revealed
that the ability of the latch to hold the umbilicd
in the retracted position under shock conditions
wae marginal, Therefore a change was initiated
which provided a redesigned latch to prevent a
recurrence of the problem.
Forward umbilical carrier problem at KSC on S-IC2- Two valve-type umbilical ooupZings on the S-IC
forward urnbiliaal ground oarrier did not mate prom
perly with the flight-half couplings. This resulted in
partial*closureof the valves within the couplings and
restricted flow. Indications were that hardware nonconformance (currently undefined) prevented the
ground carrier from fully contacting the vehicle plate.
The problem with the couplings was corrected by a
change that installed a spacer behind the ground-half
couplings thereby assuring that the internal valves
are fully open. With MSFC and KSC concurrence,
S-IC liaison generated a change, that called for replacement of the poppet valve couplings with straightthrough couplings on S-IC-3. The straight-through
couplings should eliminate any problem of flow and
lock-up pressure associated with the forward umbilical service unit. However, with the bowed condition
of the forward umbilical flight plate, shimming of the
straight-through couplings may be required to prevent
leakage at the coupling seal. The closure problem of
the coupling valves will not occur on S-IC-4 and subsequent stages because couplings used on the forward
umbilical for these stages are not susceptible to this
problem, However, the basic cause of the problem,
improper umbilical carrier mating, is still under
investigation.
MISSISSIPPI TEST FACILITY

S-IC-5 static firing - While preparing for the S-IC-5
static firing the stage fuel emergency drain duct collapsed during the fuel loading portion of the propellant
load test. Investigation revealed that a negative pressure of as much as 12 psig was being developed in the
facility RP-1 fill and drain system by a recirculating
procedure that was being used for cleaning purposes.
Although the same procedure had been used on previous stages (S-IC-T and S-IC-4) the condition was
not detected because these stages were equipped with
heavy-walled I.060'3 drain ducts. The wall thickness
of the 5-IC-5 duct was only 03Zrt. After additional
investigaffon and experbentation, the ta*g
Procedure was revised to eliminate the recirculation mode,
a nitrogen preesurization system was installed in the

.

�facility RP-1 lines, md the lines were instrumented
to give a continuous r e d o u t of system pressures,

-

During the second propellcant load test of the S-IC-5
the LOX tank ullage pressure was observed tu go negaifve about 0.3 psig for a few seconds after two-line
LOX bubl~lingwas initiated. This negative pressure
was produced when the ullage volume was suddenly
chilled by LOX geysering into the tank from one o r
more of the partially filled suction ducts. The tanking procedure w3s changed to close the vents and
pressurize the LOX tank to 3 to 4 psig before start of
bubbling, This procedure was used eutcessfully on
firing day. However, the auxiliary vent had to be
cycled 38 times in maintaining the ullage pressure
between 3 add 4 psig. Experimentation is under way
at MSFC (S-IC-T at R-TEST) to devise a procedure
that will suppress geysering without the necessity for
cycling the vents.
Valve position indications from the pneumatic console
were lost momentarily four times during the S-IC-5
static firing. A post-firing examination disolosed no
broken wiree or loose connections in the power circults, and a change was initiated to provide a redundant path for indicating power to the pneumatic consoles at MTF and KSC,

Oiict

a)

b)

46

Support KSC
An engineer from Michoud has been on site atKSC
to provide direct coordination between Boeing
Schedule I (Test Requirements) and Schedule Il?
(Test Procedures),. This work involves assisting
in the review of approximately 150 test procedures
per stage, the resolution of commenta from
Michoud and KSC on approximately 50 test procedures per stage, and the preparation of the
detailed audit of test procedure compliance with
test requirements. This support will beprovided
to KSC as long as it effectively contributes to the
S-IC stage program.
Technical support was also provided during the
prelaunch tests and during the actual launch
countdown of AS-501 and -502. This support was
provided through participation in a team stationed in the central instrumentation facility at
KSC and through a team stationed in the Huntsville operations support center at MSFC. For
the CDDT and launch of the AS-50 1 and -502,
continuous support during the final 24 hours of
countdown was provided for KSC from Michud,

-

Preoperational safety review
An S-IC preoperational safety review for the S-IC-1 was conducted at
KSC during the period July 5 through August 11,1967.
The review team consisted of members from Boeing,
General Electric, International Business Machfnes,
and Rocketdyne. Test procedures affecting the S-IC
stage were reviewed against safety criteria that were
developed to determine whether or not unsafe conditions could occur as a result of executing the procedures. A total of 159 test procedures were reviewed,
resulting in 119 safety problems reports. All 119
have been closed out.

-

KSC test requirements coordination
Revision E to
"Specifications and Criteria for S-IC Stage Prelaunch
Checkout and Launch Operation at KSC" (D5-13618)
was released during FY 1968. This revision incorporated committed changes and MSFC comments.
The majority of these comments concern level of
detail and the addition of primary requirements for
tests being conducted in excess of the existing requirements. These comments were discussed with
MSFC on December 19, 1967, and The Boeing Company agreed to make many of the changes to encourage a more uniform MSFC acceptance of document
D5-13618 as KSC test requirements.

-

AS-501 and -502 GSE launch damage As a result of
the launch environment, some GSE items on the
mobile launcher were damaged. The following table
is a brief asseslsment of this damage:
S-IC-1

S-IC-2

a)

S-IC pneumatic
console

Valve
manifold
assembly
damaged

No damage

b)

Pneumatic
checkout racks

No damage

No damage

c)

Prevalve
accumulators

No damage

No damage

d)

Aft umbilicals

Major damage

No damage

e)

Intertank
umbilical

Minor damage

Control box
panel
missing

Miaar damage

No damage

Forward
umbilical

'

D5-1260 1-5

�I'

Intertank

"

3) Thrust

Minor damage

Minor
damage

Minor damage

Minor
damage

No drtm

structure
h)

Heat shfeld
storage

No damage

No damage

i)

Thrust structure No damage
vertical internal
access equipmetlt
storage r a c h

No damage

j)

Forward skirt

Moderate

Moderate

&amp;ten%mcear

dam

~ W W

equipment
storage racks
k) Fuel tankupper
bulkhead protection equipment
storage racks
1)

LOX tank upper
bulkhead protection equipment
storage r a c h

Racks
heavily
damaged

Totally
destroyed

Racks
heavily
damaged

Racks
heavily
damaged

damaged

Totally
destroyed

A damage assessment for tbe S-IC umbilical equipment that supported the S-XC-1 launch was aecomplished* The three AFT umbilical carriers sustained
major damage resulting from the f a u r e of the tail
service mast protective doors. The intertank reconnect assembly and the forward umbilical carrier
euetafned only minor damage, A change w a initiated
~
a s a result of thie assessment. This change provided
additional fasteners for the intertank reconnect aseembly control box covers to prevent the covere from
beearning detached as Ls reeult of vibratfon.
A preliminafy assessment of the damage euetaiaed by

D5-12601-5

A detailed analysL of this damage L contaiaed in
dacument B5-%584&amp; "MobBa Launcher No. 1 Q8E
Damage
- Assessment and Corrective Action Recommendations," for the AS-501 launch and the follow-on
document, D5-13842-1, for the AS-502 S-IC-2 launch,

ENGINEERING TEST PROGRAMS
During F Y 1968 test activities were directed toward
the completion of the reliability program, qualification program, and resolution of design data problema
and discrepancies identified during manufacturing,
~t;;Lt;lD
Xi&amp;%,
a 4 6-IC-I, BXXd 8=XC43 I w ~ suggsst
~h

sper&amp;aaaa,

rn) Intertank vertical Heavily
internal access
equipment
storage racks

the 8-IC umbilical equipment during the AS-502 launch
was conducted. The three Aft umbilical carriers
sustained no visual damage and appeared to be d e quately protected by the redesigned blast shields that
were added to the t a i l service masts following the
AS-501 launch. The intertank umbilical reconnect
arssembly sustained moderate damage resulting from
heat and vibration, but there was no major structural
damage. The forward umbilical carrier eustained no
apparent damage.

At the beginning of the reporting period, Engineering
Laboratories had 59 tests on hand. During the year,
355 tests were received, and 331 were completed.
Testing is divided into categories of reliability, qualification, and development testing, and f aflure
analysis.
The High Pressure Test Facility, which experienced
approximately five months of down time due to a high
pressure line failure, resumed operations in August,
1967. To minimize the impact of the loss of the
facility, six tests were conducted at the adjacent
Michoud/Chrysler laboratory facilities.
RELIABILITY TEST PROGRAM

The reliability test program began the report period

with six testa scheduled for a December 6, 1967,
completion date. During that period, four teats were
received, one was cancelled, one was reopened, and
nine were completed.
Reliability tests completed during F Y 1968 include:
R401- Pressure relief switch
R415 Redesigned outboard engine GOX line
assemblies
R427 Engine purge system regulator
R22Z Thrust OK distributor

--

47

�R409
R465
R402
R4 11

R413

-- Redesigned
Valve-to-tunnel
duct aseembly
feeder duct
- Upper hot helium supply duct
GOX
GOX

--

lnboard GOX line assembly
Uppcr outboard GUX duct assembly

OUALIFICATION TEST PROGRAM

During the reporting period, qudiflcation testing for
220 compotients was successfully completed, increasing the number of certified components by 208 from
1103 to 15I I, sixty components r e m h to be certified (see Figure 2-21),
All S-IC-1 and S-IC-2 stage and stage-peculiar GSE
hardware was qualified prior to launch, and all S-IC3 stage and stage-peculiar GSE will be qualified
prior to launch.

At the beginning of this reporting period, the engineerirrg laboratories had eIeven qualification tests on
hand scheduled for completion during December,
1967, During the period, sixteen additional tests
were received, one was cancelled, and nineteen were
completed, leaving seven tests to be oompleted,
Also, the piece parts qualifioation test, P24 (quality
assurance inspection of MBR37496-9 and MBR3749610 relays), is an open end item with lots tested on a
periodic basis as they are delivered.

DEVELOPMENT TEST PROGRAM

During F Y 1968, 208 Development Tests were initiated, and 213 were completed.
Engineering Laboratories supported the AS-50 1

mtowlmmr~

S-IC CONTRACTOR QUA1TEST SUMMARY

OnmlOltOU1WEl'

ALL CATEGORIES

+--.

Figure 2-21

48

--

S-fC Qualificatian Test Summary
Dti- 1260 1-5

�lnunch by conducting three development tests. Five
development tests were conducted in support of the
AS-502 lnunch.
Subsequent to the S-IC-2 launch, Engineering Labora-

torirs also participated in the search for cause
mtl solutions of problems encountered during the
flight of AS-502.
Durlng FY 1968 twenty-eight development testa that
lcd to desibq changes were conducted. Eight development tests that deal with current problems were in
progresa at the end of the reporting period.
FAILURE ANALYSIS TEST PROGRAM

During the fiscal year 90 faflure analysis testa were
completed.

INVESTIGATION OF DEEP-FLAW EFFECT IN S-IC TANKAGE

Problems on the S-II stage focused attention on all
S-IC stage pressure vessels that a r e proof-tested at
room temperatures and a r e used at cryogenic temperatures. The problem involves the fracture toughness of tank material in the presence of a deep surface flaw. A fracture toughness test program has
been initiated in Seattle to investigate the deep-flaw
effect in 22 19 aluminum with a scheduled completion
date of July 1968. Previously, an evaluation of all
S-IC pressure vessels had been conducted by the
structural development unit in Seattle. Based on
existing data, the S-IC propellant proof tests were
found to be adequate. Results of the current test
program a r e expected to verify this evaluation.

S-IC SYSTEMS A N D STUDIES
STAGE SAFETY STUDY

The stage safety study was conducted for S-IC-2
through S-IC-15 stages, a t MSFC1s request, to determine whether the stages would be safe at KSC for a
seven-day period during which RP- 1 fuel is onboard,
stage electrical power off, and GSE electrical power
on o r off. "Safe" was considered to be a condition
that would assure no physical o r functional damage to
stage systems o r subsystems. Damage was considered to have occurred if the design limits, tolerances,
o r specifications of a stage, system, o r subsystem
were exceeded. The study indicates that the S-IC
Stages a r e "safet1 when certain conditions exist as'
defined in the study.

S-IC ENGINEERING SYSTEM SAFETY PLAN

Safety Engineering i s preparing an, "S-IC Engineering Safety PlanrTwhich will develop and implement a
system that identifies relevant goals, requirements,
controls, procedures, responsibilities, methods of
accomplishment, and schedules for systems safety
engineering. A preliminary copy of this plan was
reviewed and commented on by affected organizations,
and the estimated final release date is July 1, 1968.
SPECIFICATION COMPLIANCE STUDY

All S-IC requirements necessary to assure astronaut
safety, stage integrity, and achieve end conditions of
flight have been designated a s "Man-Rating Requirements", and will be verified as completed through an
S-IC-3 specification compliance study. The S-IC
contract end item specifications and Saturn interface
control documents have been reviewed and a l l applicable man-rating requirements identified. Documented
verification of compliance is being established by reviewing engineering and test documentation to assure
that the identified requirements have been met. This
study will be published as document D5-13874, "Specification Compliance Study for S-IC-3," which is
scheduled for release on June 28, 1968.
S-IC STAGE DAMAGE PREVENTION STUDY

Document D5- 13704, ITS-IC Stage Damage Prevention
Study," was completed on April 12, 1968, and is
currently being released. This document presents
the results of a study that was performed to establish
and recommend dispositions of ground support equipment failures that could cause S-IC stage damage at
MTF, The original findings were based on the S-IC4 configuration. A formal "Fault Tree Analysisf1wae
used to identify areas of concern. One hundred
twenty-one potential hazard areas have been identified of which 93 have been satisfactorily resolved
with the remaining 28 still under study. A follow-on
study to update the findings for the S-IC-6 configuration is in progress and will be documented prior to
static firing.
S-IC STAGE STORAGE

S-IC stage storage requirements have been prepared
and forwarded to MSFC for approval. MSFC standards 492 and 500, giving S-IC stage storage specifications, were received as information from MSFC,
and have been reviewed. In several areas, these
standards a r e more stringent than the Boeing prepared requirements. Major differences a r e in the

�basic processing program modifications were
incorporated, and PERT charts were released
in about one half the time required for the S-IC1 flight. Data handling team interface review
meetings were held to strengthen the overall
communication network between the various
flight evaluation organiz;ationa.

area of ambient humidity, maintenance of contaminant levels and restriction of partfeulate material,
and, in general, cover long storage periods* The
fin&amp; agpmvod requirements for storage will become
part of the CEI Specification Part XI,

FllGHf NAUIATION PROGRAM

Test data requirements for analysis of the AS-

S-1C.l Flight
a)

502 CDDT, countdown, and launch were compiled

and coordinated with the MSFC Mission Operations Office and MSFC Com~utationLaboratory.
Inputs were made for fnclu'ion in the NASA Program support requirements document and the
MSFC processed data requirements document,
Attempts were made to obtain installation of
additional instrumentation at KSC for measurements of the launch environment and its effect on
the GSE. This was not successful for the ASS02
launch, but efforts are continuing for the S-IC-3
launch.

Flight Ev aluat ion Preparations

In prcpriration for tho S-101 flight, a complete
practice run was necornplfshed using the S-IC-3
static firing telemetry data as the data bank, The
practice*run provided a successful verification
of our capability to reduce, process, and analyze the S-IC-l flight data. Also, a complete
set of flight predictions were calculated and
documented. These predictions were used to
provide a rapid assessment of the S-IC-1 flight
performance by identifying mearsurements that
were significantly different from those anticipat&amp;,
b)

Flight Evaluation
The S-IC- 1launch occurred at 7:00:0 1 a. m. ,
EST, on November 9, 1967. The Boeing flight
evaluation team participated in three presentatfon meethgs which reviewed the flight d a t a
The required twenty-one day report was submitted to MSFC a s scheduled, on December 5,
1967.
Generally, the AS-50 1 flight met all mission
objectives except a s specified in the BoeingSixty
Day Report, document T5-7000-1, which was
released as scheduled on January 11, 1968. The
report evaluated the performance of the first
flight of the S-IC stage.

The flight prediction document, was released on
March 11, 1968. This document listed the predictions for S-IC-2 flight measurements.
b)

Flight Evaluation
S-IC-2 post-flight activities, including the reduction and processing of the raw telemetry data,
followed the PERT plan as closely as possible.
The BERT completion times of some items were
not met due to late delivery of data tapes from
MSFC, and special analysis of the POGO problem, which impacted the entire processing
effort.
Data from the TEL 4 ground receiving station

was used as the primary source for the PAM and
FM data until the POGO problem became evident,
A 2 cps "wow and flutter" error was found in this
data, and the Central Instrumentation Facility
ground receiving station data was used.

S-IC-2 Flight
a}

Flight Evaluation Preparations
Preparation for the S-IC-2 flight included such
activities as certification of the basic data processing program using S-IC-2 flight readiness
test data as input and verification of the stage
telemetry configuration.
Standard basic processing analysis program work
was completed on schedule, As a result of prubIems encomtersd on the S-TC-1 Bight, several

50

Processing charts were released daily aa a
tracldng method for the flight processing. These
charts were released through L+14 days as
required.
A11 b e i n g contractual data deliveries were completed on or before the required delivery dates.
The S-IC-2 data quality and delivery schedule
was generally better than that for the S-IC-I.
launch,
As a result of pereonnel training after the S-IC-1

D5-1260 1-5

�ght and improved activity schedttlbg, the numbcr of aperture cards made for the S-IC-2 flight
reduced by 33 per cent from the $-IC-1

t.
a result of a problem encountered Sn the PCM
a from the S-IC-2, a new formatting &amp;ahue for PCM data was designed.
The L+1, L+8, and L+14 day presentation material for the SIC-2 night were delivered on
schedule to the MSFC flight svduatem working
gmup FEW^ ohtlimas, The boejlng be21 dw
input to the FEWG AS-602 report waer submitted
aa scheduled on May 9, 1968, The L+60 day
report T5-7000-2 was released, as scheduled, on
June 28, 1968,

V.7 PH. STAiNLESS STEEL USAGE SURVEY
A Boeing survey is being conducted to determine all
17-7 PH steel parts used on the 5-IC stage that are
reliability critical per document D5-11910. Fiftyfour parte made from this alloy were f~und, These

are urrd In c~mpntaa@Xirat&amp; h tat&amp; dssmctat~
A matsix sf the pmoesssrr tur$ proceesing wed h
fabrication of these parts is in preparation,

to launch, that are dispositioned "use-as-is. " The
procedure requires both NASA and Boeing technical
and contract signatures to validate the waiver. All
waivers are then documented in the appropriate Part
I CEI Specification subsequent to vehicle launch. Ten
5-6-2 waivers were processed, approved, and incorporated hta the Part I CEX Specg$cation using
this procedure.

INTERFACE CONTROL DOCUMENTATION
(ICD) AND INTERFACE REVISION
N O T E E (IRN)
STATUS OF BASIC ICD'S

As of May 16, 1968, there were forty-five basic ICDta
applicable to the S-IC stage, of which thirty-three
are applicable to the stage hardware, eleven are
applicable to the GSE, and one is common to both
stage and GSE. All ICD1s a r e identified fn the May 1,
1968, issue of MA-004-002-2H, "Saturn V/S-IC
Interface Control Documentation Contractual Index
and Stabs Report. l t

pa*

CONTRACT END ITEM (CEI)
SPEClFlCATiONS
The Part II S-IC CEI Specification, S-IC-3 through
S-IC-10, has been prepared and is currently being
reviewed by NASA. This specification will be incorp r a t e d into CPIF Contract NAS8-5608, Schedule I,
subsequent to negotiation and NASA approval, and
when it is approved, will serve as the basis for configuration definition and a c c e p h c e testing of Stages
S-IC-3 through S-XC-10.
Ttre S-IC-4 was delivered to the Customer at Michoud
with one government and two contractor CEI nonconformaaces for which no corrective action was required. Of these nnnconformances, eleven MSFC
and twenty-four contractor qualified electrical comportents failed to fully achieve electromagnetic interference test requirements under MIL-I-618D. Also,
voltage fluctuations (transient@ in excess of the end
item test plan limit8 (t 14 volts) appeared at one of
the monitored electrical circuit mints during power
application add removal sequences.
During the fiscal year, a wafver procedure was establlshed to cover wncodo~mancee,evidenced prbr

D5-1260 1-5

Of the forty-five basic ICD1s applicable to the S I C

stage and associated GSE, forty-one were officially
accepted by Boeing, three have not been received,
and one is not acceptable at this time. The three
ICD1s not received are flight sequence programs for
AS-508, -509, and -510, The ICD not acceptable to
Boeing is the interface between the LUT and the S-IC
access and bulkhead protection equipment storage
racks. An administrative change propos d, which
defines the changes required for compatibility with
S-IC stage documentation, has been submitted to
NASA.

On August 8, 1967, Boeing initiated the use of record
ECP's for the purpose of contractually accepting IcD/
ntN1s if they are compatible with S-IC Stage and CSE
hardme and documentation. ~~~~d
E C P I ~~ - 0 0 0 1
through R-0073 have been submitted to MSFC through
May 16, 1968.

RELIABILITY ENGINEERING
RELIABILITY ANALYSIS

-

Documents'D5-12572-1, Its-IC System Design Analysis
Propulsion/Alechaaical,'~and D5-12572-2, llS-XCSystem
Design Analysis Electrical/Electronfcs ,'I were each
updated Mce during this reporting period. These updates reflecEed failure mode and effect analysis, both

-

51

�1

propulsion/mcehanical and electricallelectronics , for
S-IC-3 and -4.
Other imporbtnt S-IC reliability documents that were
relemed during the reporting period, and the purpose
for the release, are:

4

Document D5-11910, ,"Saturn S-IC Reliability
Status Report,ll -Two updates were made, one to
add additional status on reliabiliQ program elements, and one to add S-IC-4 stage release.

b

Dacumefit D5-31964-1, "Saturn S-IC Stage Reliability Analysis Record. "-Updated twice during
F Y 1968 to report predicted and assessed reliaWlity for S-IC-3 and -4.

6)

Document D5-13693, "Hydrogen Explosion Hazard
Survey." -Updated twice to report that no ignition
source is present in the interstage area that is
sufficient to detonate an assumed hydrogen atmosphere.

d)

Document D5-11954, llSaturnS-IC StageReliability
~'
Assessment and Prediction P r ~ g r a m . -Revised
once during the year. This document contains the
methodology used to apportion reliability goals
and describes in detail, the Saturn S-IC reliability information system,

8)

weekly I1FailureStatus SummaryM(unresolved failures)
for program corrective action, the Michoud Reliability
Data Center has initiated a "Top Priority" report for
each scheduled launch. This report includes only those
failures that could impact launch. If program corrective action cannot be implemented prior to the launch,
the problem is submitted to the BoeinghIichoud UER/
CER Assessment Board for launch impact assessment.
This "board" is chaired by the S-IC Chief Engineer
with representatives from Boeing Quality and Reliability Assurance (Q&amp;RA), and Product Assurance.
Equipment Ouality Analvsi8

The equipment quality analysis effort was expanded
during F Y 1968. This was the result of increased emphasis on product quality initiated in 1967. Emphasis
has been placed on the analysis of reliability critical
components. Additionally, this area has been expanded to provide the quality maintenance testing required
by contract change order MICH-723. This combination
of equipment quality analysis and quality maintenance
testing constitutes an ambitious schedule of in-depth
testing and analysis of "criticals1hardware. During
the fiscal year, 111 Equipment Quality Analyses sad
six Quality Maintenance Testa were performed. A
summary of this activity follows:
a)

Document D5-12789, "Design Analysis for S-IC
Malfunction Detection System. "-Updated once to
reflect release of S-IC-4. This document cmtafns
the necessary analyses and data from which the
S-IC design requirements for a malfunction detection system may b t determined.

'

In addition to monitoring receiving and subassembly
discrepancies, major emphasis has continued on monitoring and evaluating in-service faiIures that occur on
stage and GSE hardware during post-manufacturing
checkout, static firing, and post-static checkout and
after delivery to KSC

.

In addition ta tracking each in-service failure in the

52

........................111

Number of EQA's performed
andclosed..........................,...

92

................. 51
Design C hasge ................. 5
Process Change.. .............. 5
Quality Control Improvement.. .. 31

1) With no anomalies..
2) With anomalies resulting in :

Failure Analysis

Continuow emphasis has been placed on the S-1C Failure Analysis program. A total of eighty-two failure
analysis test were completed during the reporting
period. Operating procedures were revised during
FY 1968 t o improve processing and analysis of failed
hardware.

Number of EQA's performed,
during F Y 1968..

NOTE: Some EQA's resulted in more than
one type of change.

c)

Number of EQAts performed
remaining open

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

d)

A11 QMTts performed are open.

e)

Number of hardware problem
analyses performed F'Y 1968

f)

Number of discrepancy checks idsued

FY 1968...*.r..rrea.*.e.-o..*..e=~...*.

19

............. 138
39
D5-12601-5

�Oata Gallect~on artd Analysis

During F Y 1968, 525 special computer printouts concernirrg faifure data were supplied to requesting organfzafioas by the Launch Systems Branch Reliability
Data Center. These special printouts were reqaired
to @upportsuch varied actfvitfae m product mcsaurmca,
hurnaa engineering, and logistics.

L

A totrh of 789 Boeing Investigation and Corrective Action Requests (BICAR") were initiated by the Launch
Systems Branch or assigned to Bming by NASA during
F Y f 968, 8even hundred Urirty-five of these werecloered,
and 54 r e m a n open and are programmed for completion
aMf closeout during the first quarter of FP 1969.
Continuous effort is being expended to isolate repetitive
failure trends. Some of these collective analyses have
resulted in further laboratory analysis and/or design
corrective action, The requests for design corrective
action are included in the BICAR statistics above.

A total of 84 NASA "ALERTS" (problems experienced
by other NASA centers and contractors) were received
and evaluated for 6-IC impact during FY 1968. Seventyfive were closed; nine remain open,
Refiability Audits

The results of the FY 1968 reliability audits of compliance with the reliability requirements as defined
by D5-11013, "Reliability Program Plan," and related documentation have been published for the first
three quarters of FY 1968. These three quarterly
"Reliability Program Status" reports were D5-13747-3,
D5-13747-4, and 05-13757-1. The "Reliability Pro=am Status" report for the fourth quarter FY 1968
will be published after the end of the fourth quarter and
will be designated D5-13757-2.

The review included analysis of specifications, qudification, receiving inspection, functional test, vendor
surveillance, and failure history. As a result of the
review, recommendations were made for strengthenina;
product quality of piece parts and standards. These
recommendations resulted in tighter receiving inspection, increased vendor surveillrmae, and inoremced
equipment quality analysis activity. Also, an engjneering review board recommended action on 34 critical
piece parts for either new specifications, revised
specifications, or higher level of qualification, Those
recommendations were approved by the S-IC Chief
Engineer and are in process of being implennenbd.
Reliability Analysis Model

Work continued during this report period in support of
the reliability analysis model. This model delineates
ground rules for providing S-IC stage reliability data
I Reliability
to MSFC as an input into the MSFC Level X
Analysis Model (RAM). Failure effect analysis loadsheets, non-critical cables lists , criticality determination loadsheets , symbolic block diagrams, and engineering critical components lists for S-IC-3 and S-IC-4
have been completed and transmitted to MSFC.
Faiture Management by UCR Task Force and Assessment Board

During FY 1967, a task force was established to assure
that all Unplanned Event Records (UER) and Unsatisfactory condition Reports (UCR) were properly dispositioned , failure analyses completed, program corrective actions taken, and flight readiness actions specified prior to the AS-501 flight. Major functions performed were:
a)

Classification of all S-IC program failures by
their criticality as assessed in relation to
S-IC-1 launch effect;

b

Establishment and implementation of a workable
failure and failed hardware activity tracking
system; and

c)

Support to the UERNCR Assessment Board,
which was established based on the task force
finding that program corrective actions could
not be ,completed on all failures in time to meet
the launch date.

Product Quality Survey

Work continued on the "Product Quality Survey" during
this report period. This survey, which was initiated
during FY 1967, reviews and updates existing GSE
failure mode and effect analyses. This updating covers
hardware and time intervals not previously analyzed,
identifies single failures that could cause abort, and
identifies single failures that could cause loss of stage
vehicle o r crew.
As a part of the product quality survey, an in-depth review was made of all $-IC stage piece parts and standards, This review was conducted by Engineering,

Quality and RellaE&gt;ifityAssurance , and 0perat;fom.

f35-52601-5

Assessment Board members were the S-IC Chief Engimer ,Q&amp;RA representative, Product Assurance manager and the UCR task force manager,

,

53

�I

The itshiesamcnt Board reviewed all w e s o l v e d failures
and evvluatccl the risk each might have on the AS-501
launch and flight to assess Boelng's 8-IC flight readincss position.
R e l i a b L ~Program Ptesentations

The monthly S-IC reliability program status was presented to NSFC on February 19, March 18, aad April
16, 1968. The general outline of these presenWions
is as follows:
Activities of relihility and ssordinaaon
sf
b)
c)
dl
e)

0
g)
h)

committcre;
Summarize ECP's initiated, c h w-e d , o r s t o ~ v e d
because of reliability activities;

--

Summary of ECP1s reviewed by reliability organizations ;
Failure reporting and correction action;
Human factors;
F M ~ E A ' S ,reliability predictions and assessReliability test;
P a r t s program activity;

j)

Materials and processes activity;
Boeing selected areas from 65-18 history
approach, philosophy; and

k)

Significant changes in program o r organization.

I)

Since July 1967, the reliability coordination committee
has held bi-monthly meetings to implement corrective
actions required to eliminate S-IC reliability deficiencies , all of these actions were completed by December
29, 1967, Two NASA/Boeing meetings concerning reliability program deficiencies and planned corrective
actions were held August 91, 1967 and September 5,
1967. These meetings presented The Boeing Company's
positiotl and planning to implement an effective S-IC
reliability program, Another meeting was held on
December 7, 1967 to report the status of the 6-IC reliability program and discuss associabd prablems.
Growth of Assessed Reliability for S-IC

Figure 2-22 depicts the growth of assessed reliability
for the S-IC stage.

MANUFACTURING
DEVELOPMENT
The Manufacturing Development organization, a part
of the Boeing/Michoud Operations organization,
supports manufacturing in all areas necessary for the
production of S-IC stages. This organization works
closely with Engineering Design and other technological groups, and maintains constant surveillance
on new trends in materials, design, and techniques
that a r e applicAle to the Boeing/Michoud S-IC
program.

WELD DEVELOPMENT
TANK SKtN TEE STIFFENER CRACKS

At Michoud Engineering's request, a weld repair
program war, devised to repair tee stiffener web
cracks. Since minimum heating in skin membrane
was desired, the following heat sink methods were
employed on simulated repair weld panels: copper
chill blocks were placed adjacent to the manual
'i'ungstenInert G a s (TIG) repair on ofie side of the
skin membrane, and dry ice was held in place on
the opposite side of the skin membrane. As a
result, heat-affected membrane areas of the simu-.
lated repair weld did not exceed 300°F, and this repair procedure was adopted in lieu of riveted doublers for future tee stiffener crack repairs.

6UX DUCT LINE MODIFICATION

Figure 2-22
54

Growth of Assessed Reliability1-S-IC Stage

Manufacturing Development was requested by
Michoud Engineeriag to assist in high priority prototype weld fabrication of an S-IC GOX line duct. This
work bvolved manual ETA (Gas TungsWben Arc)

D5-12601-5

�1

I

welding of A-286 alloy with Hasteltoy W filler wire

DIAPHRAGM TEST HARDWARE

' and was initiated after reliability tests [static

pressure plus induced vibratory stress) resdted in
fillet weld failures. Engineering redesigned the
COX duct line by deleting four fillet welded gussets
qnd replacing them with an attachment flange with
400 p r c e n t penetration single ves weld joints,
yabrlcatfon of needed weld tooling and establishment of welding sequence was then undertaken by
Manufacturing Development. Upon completion of
this redesign, reliability testing established acceptability of the redesigned assembly,

As a part of Boeingls company-sponsored activities
at Michoud, two flat bulkhead tank assemblies were
completed this year in support of Boeing/Nmtsville
Engineering. Fabrication of these tanks was part of
a program initiated by Huntsville to determine. the
feasibility of replacing forward S-IC bulkheads with
flat diaphragm bulkheads.

MACHINING AND FORMING

SATURN S-rC REPAIR WELD HISTORY

ELECTROMAONETIC C Q ~ LREPOTTING AND MANUFACTURING
FACILITY ESTABLISHMENT STUDY

Repair welding a t Miehoud is monitored by the Manufacturing Development organization. Records of repair weld frequency include the S-IC-15 stage.
Figure 2-23 is a data plot, which includes 1968 repair
weld frequency. Accumulative percentage of required repair welde through March 1968 was 0.605
percent, This compares favorably with the March
1967 average of 0.614 percent,

During the reporting period, a repotting procedure,
including tooling, was established for repairing o r
buklding new 4-1/2-inch diameter electromagnetic
coils that a r e used with the high-energy capacitor
discharge unit to correct contour distortions on the
S-KC. Damage occurs to these coils when part of
the polyurethane potting compound separates from
the coil or when a dielectric breakdown of the pot-

I

AlRS/100" OF WELD)

Figure

2-23

D5-12601-5

S-IC Repait Weld Frequency
55

�1.

ting occurs. f n thc past, dnmaged forming coils

wcrc sent lo itnother fscility to be repairad. This
usuaily took rtbaitt three months. I t is now possible
to repair a rlamnged coii at X-lichoud in five days.
It is also possible to produce new coils to alleviate
tkc pmscnt shortnge and to evaluate coil efficiency
for various dcslgns,

close tolerance requirements, an orbital fIaring
concept developed by NASAfMSFC was evaluated.
This concept, which utilized a cone and die cartridge assembly may alleviate the misalignment
problem encountered with the conventional Leonard
3CP machines. Its use will possibly enable certification of only one machine oapable of ueing varying tube sizes.

STRESS RELIEF WITH VlBRELlEF MACHINE

CHEMtCAL PROCESSES
An evaluation was made of sonic vibration for s t r e s s
relieving metal parts warped by machining, welding,
o r hcnt treating, This was done to find a method
for expediting the flattening of base heat-shield
panels warped during test firing of the S-IC-4 stage
s o that these panels could be used on the S-IC-8.
T e s t s conducted using a Vibrelief machine manufnctured by Lodding Engineering Corporation were
unsuccessful; therefore, sonic vibration for s t r e s s
rclicving metal parts of the S J C vehicle i s not considered practical a t this time. Further research
on this method i s necessary to expand its potential
for future production use.
IFFU US ION BONDING CAPABILITIES AT BOElNGlMlCHOUD

The growing importance of diffusion bonded assemblies in aerospace applications prompted a study of
limitations and capabilities within the Boeing/
Michoud facility. One of the objectives of this
study is the development of a sub-scale facility in
which various concepts relative to the production of
a true diffusion bonded assembly may be evaluated.
Successful solid-state diffusion bonding of Ti-6A1-4V
(titanium alloy) to itself has been achieved with
little difficulty. Solid-state bonding of 6061 aluminum to itself has also been achieved with the use of
a copper interleaf. Efforts a r e continuing to diffusion bond aluminum to itself without the use of an
interleaf. As a part of this effort, an evaluation is
being made of a process by which component specimens a r e protected from atmospheric contamination
by being totally immersed i n a cleaning solution a t
each stage of the cleaning process. While still immersed in the final cleaning solution, the components
a r e transferred to a vacuum chamber within the
furnace. This chamber, containing the same solution, is then sealed, pumped out, and back-filled
with argon. Diffusion bonding then takes place in
this argon atmosphere.

AIR POlLUTlON CONTROL
Many Boeing suppliers are located in Los Angeles
County, California, where a i r pollution control
regulations have been put into effect. Since there
is a trend toward increased legislation regulating
permissible contamination, Manufacturing Development is conducting a survey of current control regulations and legislation. Boeing/Seattle has already
found it necessary to modify one process specification to meet Los Angeles County requirements.
Possible replacement processes for Boeing specifieations that do not meet Los Angeles County air
pollution standards a r e being investigated.
HIGH TEMPERATURE RESIN FOR ELECTROMAGNETIC
FORMING COIL ENCAPSULATION

Several materials have been examined for electromagnetic forming coil encapsulation. Criteria for
evaluation included high-impact strength, hightemperature stability, and a hardness comparable
to cured polyurethane resin, the material that is
used to pot coils for ambient use. Representative
formulations of the following three different types
of material have been selected for further development: a temperature-resistant epoxy resin, a high-. :
strength silicone rubber, and a high-temperatureresistant polyaromatic.
'

EVALUATION OF ZlNC PAINT COATINGS FOR
STEEL TABLES IN VAB
A zinc paint coating was applied to one section of a
steel turntable in the VAB and was found to resist
the corrosion that normally occurs. Plans have
been made to apply this coating to the three turntables in the VAB. This will result in a labor Cost
savings.

.

�reinforced with advanced filaments, such as
oron, in lieu of normal glass fibers. The result
is a high-strength, high-stiffness , low-weight
material with major structural applicstiom
Fabrication data and experience on a laboratory
basis is being gained for possible use e stages bepond the S-XC-5. Tensile and flexural test p-la
of boron filaments in an epoxy matrix have been
fabricated and tested, and continued evaluation is
planned for combined boron filament/gtass cornpoaites where advantage can be taken of the high
strength of boron filaments and the low c w t of
QbaOnen,

.

ELECTRICAVELECTRONICS
SHEET M

PROGRAM DEVELOPMENT
SYSTEMS
During this reporting period a product analysis
function was established in the source control group.
As a result, undesirable trends, potential problem
areas, and deficiencies, can now be detected by review and evaluation of Equipment Quality Analysis
( E W )reports, Unplanned Event Records (UER1s),
fdlus%/defecl data, receiving fmpe~Woa~ ( I ~ o F E B I ,
laboratory reports, and other pertinent data, and
action as necessary will be initiated to correct the
same.

E MOLDS FOR ELECTRICAL CABLES

During the reporting period, a technique was devefoped for polyethylene molds to be produced for
use in electrical cable production. A .O4-inch thick
polyethylene molding materid i s used since it is
semi-transparent, semi-ridged , i s eaaily trimmed,
and requires no mold release. The molds axe made
on a commercial RAY-VAC vacuum-form machine,
which has a 24 by 24-inch capacity. The sheet
polyethylene, while hot, is formed over a die by
pulling a vacuum under the mandrel. Significant
savings can be realized by using sheet plastic molds
since they can be reproduced at the rate of one per
minute on the RAY -VAC machine.

IMPROVED MANUFACTURING
TECHNIQUES
During FY 1968, Boeing/Michoud worked with tool
eupaliesa ts d w e I ~ pa z q y inapx~vedmmubacW=
imVB be@n
komqusB * T h s ~ ewahalmB@
"*d
in Boeing Operations experience retention documents
dealing with the following subjects:

a)
b)
c)
d)

QUALITY ASSURANCE

"Portable and Perishable Tools;"
"Cryogenic Hardware Processing;"
"Machine Shop Modernization;" and
"Weld Fabrication of Large 22 19 Aluminum
S-IC Booster Components. "

In relation to the above mentioned improved mamifacturing techniques, Boeing/Michoud developed a
presentation that points out how American industxy
as a whole has benefited from the improved techniques developed. This presentation was made to
the Subcommittee on NASA Oversight, Committee
on Science and Astronautics, U, S, House of
Representatives, and t o key personnel a%MSFC,

A mechanized priority system was implemented in
the mechanized procurement system during FY 1968.
The receiving inspection daily status report now
displays status and estimated completion dates for
each priority item.
A new "Work Plan" format for source surveillance
and inspection has been completed. A source coordinator visited all field locations for the purpose
of conducting an indoctrination course of the new
plan.
NASA representatives in the receiving inspection
area audited the receival of gases during the month
of Aunust 1961. Recommended actions were made
to re&amp;e that each receipt be chemically tested
for all attributes of the procurement specification
or have the vendor supply certified test data. Purchase orders were changed to require that certified
test data be furnished with each receipt.

A revbed system far planning inspections of government haisbed equipment has been put intoeffect. A
detailed inspection record repIaced the previous
"blanket" planning.
A receiving inspection/source control work plan has
been developed that provides for unified and coordinated inspection effort from release of purchase
order until delivery of hardware to the production
store.
A review of the piece part inspection plans and
failure rejection history was conducted during the
fiscal year. The aim of this review was to reduce
inspection when possible to do so without compromising the quality of the end product. The end result of this review was that inspection wa8 reduced

�on certain parts, tncrcascd on some, and remained
the s m e on others.

d)

Eddy current inspection for detecting surface
cracks in steel spherical bearings and housings;

The computerized Q&amp;RA configuration accountability system was implemented during the redelivery of 5-IC-3 and was proven to be fully operatiannf d u r l a the rodellvery of tb 8-IC-4, This
system i s a s e r i e s of interrelated comptiter programs that mechanize the configuration evaluation
and accounting systems. I t will be implemented a t
KSC for 5-16 -4 and on.

e)

Eddy current technique for detecting surface
cracks in nonmetallic ablative coating;

ft

A system to provide visual and audible alarm at
a remote location of the presence of a fuel leak;

gj

A system with an automatic tube feed that inspects lengths of aluminum tubing for rejectable surface defects with a visual and audible

MT;P Q&amp;TZA wnca reorgarixzed during FY 1988 to form
a Qualitaf Engineering support section in addition to
the existing test inspection and configuration accountability s e c t i o h , This reorganization provides overall quality program coverage for the MTF portion
of the S-IC program.

MTF Q&amp;RA initiated the development of a computerized t'ab run system which provides an automatic recap system for all tests, a daily status report, and
a work scheduling report. The tab run is a daily
updated listing of all open, planned and unplanned,
paper listed by location, milestone, and test event
prerequisites. This system has resulted in an
estimated savings of $84,000 annually at MTF

darm;
h)

A new method of preparing mounts of titanium
fasteners has been developed and implemented.
The new method provides for mounting the
fasteners in full section and then surface grinding, instead of splitting, on the cutoff machine.
This provides a much superior specimen, with
no cutting burns, which was very difficult to
obtain previously; and

i)

A new test fixture was developed in the physical
test laboratory to do torque and tensile tests on
nut plates and other self-locking fasteners. The
fixture reduces setup time and improves testing
capabilities.

.

A facilities inspection plan was established by MTF
Q&amp;RA for inspection of preventive maintenance
accomplished on all critical systems where &amp;&amp;RA
is required to control functional configuration o r
cleanliness level. Planning for 4 1 facilities work
is being reviewed by Q&amp;RA for quality requirements.
The MTF &amp;&amp;RA organization also initiated a program of periodic inspection and preventive maintenance of government furnished property not
formerly included in the preventive maintenance
program.

The development of nondestructive testing techniques
is continuing. At the present time, the following
techniques a r e under investigation and development:
a)

Crack detection in drilled holes - objective is to
develop an ultrasonic technique and portable
instrument to rapidly detect cracks in the sides
of drilled holes with ultrasonic surface waves;

b)

Comparison of nondestructive test methods for
weld inspection objective to compare the capabilities of visual, X-ray, eddy current, and ultrasonics to detect defects in welds using actual
defects a s determined by destructive inspection
as the standard;

c)

Soldering capability of printed circuit (PC)
board objective is to develop an eddy current
technique and instrument to determine the
capabiuty of PC boards to produce an accept-

TECWMMUES
The development and documentation of nondestructive testing techniques continued during the reporting period. Techniques developed that further enhance our ability to verify the integrity of S-IC
components are:

a)

Eddy current thickness measurement of nonmetallic coating;

b) Ultrasonle mtrmuretment of metal Chicknesa
from one side ;
6)

58

Eddy current techniques for identifying 3-nuts
of different tempers;

-

-

able @olderosmction;
d)

-

Surface roughness measurements objective to
develop an eddy current technique and portable
instrument to rapidly measure surface roughness of machined surfaces;

D5-1260 1-5

�-

propagation dekction objective to
p an ultrasonic technique (acoustic
emission) to detect the propagation of cracks
metals. Particularly directed toward longm stress corrosion crack generation in
red structures;

I

-

f)

Weld penetratiqn monitoring objective to
develop an infrared technique that measured
the depth of weld penetration during welding
process;

g)

Pene-trmt capabilities objecttve to compare
the capabilities of selected penetrants to detect
surface cracks in metal; and

h)

Ultrasonic hand scanner objective to evaluate
the performance and capabilities of an ultrasonic system utilizing a portable hand scanner
for spot weld inspection and other selected
applications.

-

c)

LABORATORY INSPECTION

PROCEOURES
The basic technical document for Factory Operatiomfiest Inspection, D5-11982, "Special Inspection Procedures" is continually being updated and
expanded as necessary to reflect changes in hardware. The basic technique document for Factory
Operations/'Test Inspection, D5-11997, "Quality
Technical Instruction'', is also being updated and
expanded as necessary to reflect the adoption of new
techniques as they are developed.
"Sampling Procedures for Fluids and Gases",
Document D5-13666, is being rewritten to establish
guidelines for all gas and fluid systems at MTF.
This rewrite develops the criteria for systems
sampling rather than components sampling and provides a single source for fluid cleanliness control.
The end result will be the development of a composite Document D5-12855, "Cleaning, Testing and
Handling of Oxygen, Fuel and Pneumatic Components", which will include the requirements and control methods to be applied to stage and support
facility s y s t e m .

Set up criteria for accepted certified vendor
test data in lieu of in-house functional testing;

b) Assure compliance to all safety standards during LOX compatibiZity testing of materials; and
D5-126060-5

An additional portable magnetic particle tester
ww reaeived and cer#fied for reaeivfnyr inspeation nondestructive testing;

6) Two new particle identification kits were received by the quality evaluation laboratories.
These kits contain slides of identified contaminants that will aid in the identification of unknown contaminants found in clean environments
or on cleaned parts;
c)

Two 23 by 70 inch "Mylar Flol' laminar flow
benches were received and installed for contamination control and receiving inspection,
These benches greatly increase the capabilities
of both areas by providing a clean environment
for inspecting larger clean parts and a second
area for performing particulate contamination
analysis;

d)

Receiving inspection acquired five additional
10-power lighted inspection glasses to aid in
inspection of electrical circuits and other small
electrical parts;

e)

The metallurgical laboratory received a set of
eight electrical conductivity standards ranging
from 1.0 percent to 101.2 percent, International
Association of Copper Standards (IACS) to be
used for the verification of heat treatment of
alloy by eddy current method;

f)

Receiving inspection has received a Model
PT-1033-8 Product-0-Ron for precision measurement of roundness and geometrical relationship. This instrument records measurements on recording discs to an accuracy of
-+ 0.0000025"; and

g)

A portable vacuum tweezer system unit was received by the quality evaluation laboratories,
This unit will enable personnel to collect and
separate particles greater than .05" and, when
wed with the Swinny Hypodermic Adapter, to

Procedures have also been developed during the
fiscal year tb:
a)

- TOOLS AND EQUIPMENT

Following is a partial listing of tools and equipment
that have been obtained and put into use during the
reporting period:
a)

-

Provide a method of obtaining and m a i n t a i n t ~
a record of corrective actions taken by suppliers
on discrepant hardware.

59

�$ -

collect particles lcss than ,OB" on 13mm
dinnteter filters for conLmination and spectron
acopic ,malysfs;i.

a U A t l f V ASSURANCE ACTIVITIES
QUALITY ENGlNEERlNG RNIWS

-

During the fiscnl year, quality engineering reviewed
75 engineering drawings, 330 engineering orders, 52
supplier acceptance test procedures, 330 supplier
cleaninz tiocuments, and 110 company specifications
for compli,ancc with the requirements of EN-I-V-S-IC68-13. Thcy nlso participated in six critical design

INPLANT AUDITS

SPECIAL AUDITS

SUPPLIER AUDITS

Figure 2-24

reviewe for supplier furnished bardware.

QUACITY AUDITS
Figure 2-24 denotes the quality program audits performed during F Y 1968. A total of 55 audits were
made, sixteen of these were inplant, 13 were in
special categories, and the remaining 26 were audits
of Boeing suppliers. Audits performed resulted in a
total of 467 discrepancies. The 26 audits of Boeing
suppliers resulted in the identification of 54 system
and hardware discrepancies. The not&amp; ddlscrepanciee have been resolved, o r a r e in work at this time,

�i

SOURCE EVALUATION AND SURVEILLANCE

The Michoud source control chart room has been
expanded into an effective supplier performance and
hardware problem analysis function. Supplier performance review charts are maintained that reflect
both satisfactory and unsatisf acbry supplier performances, This technique provides source control
management with the aides necessary to assess manpower requirements and placement, arrd permits a
decrease in source control surveillance of suppliers
with coqtinuoue satisfactory performance and a concmtration of carrective effort on those suppliers
with current hardware or system deficiencies,
Nonconformance data is analyzed, categorized, and
displayed in the source control chart room in such a
manner that impact problems and discrepancy trends
a r e reedily recognized. This visibility provides a
means of initiating timely corrective action of noted
deficiencies, meaningful assessment of representative's performance, and effective product improvement. Product nonconformances are classified into
one of four categories; critical hardware failures,
noncritical hardware failures, critical hardware
defects, and noncritical hardware defects, The
number of nonconformances allowed to accumulate
against a supplier before initiating positive remedial
acffon depends upon the classification of the deficiemy as follows:
Category f

-

Category II

I

Category ItI

-

Category IV

-

Critical Hardware Failure
One Unit

-

Noncritical Hardware Failure
Two Units
Critical Hardware Defects
Two Units

-

-

Noncritical Hardware Defects
Three Units

-

When supplier performance review charts indicate
that a supplier is deficient in one o r more of the
above categories, a product analysis report is generated. This report, which describes the deficiency
in detail, is then forwarded to the cognizant source
representative and a date by which the representative must ensure that the supplier has taken appro~ r i a t ecorrective and nonrecurrence actions is
established. When analysis of a hardware deficiency
indicates that previously delivered hardware and/or
hardware currently in production c d d be affected by
the same anomaly, the cugnfzmt representative fe

-

immediately notified by telephone. The problem is
discussed and a decision made relative to withholding
acceptance of hardware at the supplier's facility until
the problem is resolved. When deficiencies in a
product are considered to be of sufficient magnitude
to withhold shipment, all affected inhouse materiel
and quality control personnel are notified. This
notification includes a description of the deficiency
and the justification for withholding acceptance, Upon
resolution of the reported deficiency, the representative is required to return the product analysis report,
containing a complete description of the correotive
action taken, to the Source Control offkre, The
stated corrective actton is reviewed for adequacy
and, if acceptable, retained by the supplier performance review group for future reference. Thh
continual evaluation of supplier performance assures
the delivery of high-quality products and provides
the necessary management tools for maximum
source control effectiveness.
The practice of periodically performing in-depth
hardware analyses and quality and process control
systems reviews at selected supplier facilities has
been formalized under Change Order MTCH-728,
"Quality Maintenance Program. The purpose of the
Quality Maintenance Program is to provide additional
confidence that existing hardware will perform as
intended and/or qualified, emphasizing critical
hardware and hardware with no apparent problems.
(A more complete description of the Quality Maintenance Program can be found on page 63 of this
document.) A document has been released defining
Quality Maintenance Program requirements, selected
suppliers, and the tentative schedule for review. As
now constituted, source control is responsible for
constructing all review plans, scheduling and coordinating review team activities, providing team
captains, and assuring that suppliers correct all
noted deficiencies. Suppliers selected for review
under the Quality Maintenance Program will be
reviewed annually throughout the life of their
contracts.
The process control function has been realigned,
Work plan surveillance is now being maintained at
processors in the Southeastern area, The surveillance schedule provides for a minimum of two
visits annually to each processor. All process
survey and surveiIlance activity is now being handled
through the Michoud source control office.
RECEIVING INSPECTKIN

The Xichoud receiving inspection group inspected
and processed 32,539 lots during FY 1968,

,

I

�QUALiN NALUATION LABORATORIES

During 1988 mnjor investigations were conducted by
the quality evaluation I,&amp;oratories, Some of these
investigations were:
a)

b)

c)

62

An Pnvosttgntion of the possibility of corrosion
of thc Saturn V fuel tank by microbial cont.unination found in RP-l fuel in February 1967
has k e n completed, No visual evidence of
pitting o r any form of corrosion were noted on
iridito test $-tripsof 2219 and 7075 dumfnurn
aoys,
Failure analysis of a cracked nut submitted to
the quality cvduation laboratory by KSC d e t e r
mined the failure to be due to s t r e s s corrosion
crnektng. Thc basic material of the nut is 303
stainless steel. Intergranular corrosion was
evident. Susccptibility to such a t h c k is attributed to excessive c ~ r b i d eprecipitate at the
grnin boundaries. Carbon combines with
chromium in the steel and may precipitate out
a s chromium carbide at the grain boundaries
during
This
and
in s o doing i t depleted the chromium in the areas
the
and hence made the
susceptible to intergranular attack, as chromium
i s the main element for resistance to corrosion.
A 300 s e r i e s alloy, such a s 304L o r 316L, with
much lower carbon content that 308 has been
discovered to be much l e s s susceptible to a t t s k ,
Periodic cracking when flaring 1/4 by .035 inch
wall 606 1-T6 aluminum tubing has been a manufacturing problem for Some time. Nearly all such
tubing has been procured from Alcoa to MIL-T7081 specification. Laboratory testing of this
tubing has found it to meet the mechanical
property and chemical requirements of the procurement specification. Flaring is done to
MS33584 drawing, From considerable testing
and examining done, regarding this problem, it
is apparent that optimum conditions must exist
in the tubing (including ideal chemical composition) before it can be consistently flared in the
T6 condition. Very sIight discontinuities
readily become crack initiators, Flaring tests
on a sample of recently received similar tubing
manufactured by Reynolds found it to flare
acceptable. Comparison tests with Alcoa smples showed some difference in chemical
composition, though both manufacturers were
within specification requirements. Magnesium,
f o r example, was 1.2 pex%f'cent irt the Reynolds

tubing and 0.86 percent in Alcoa. Mechanical
properties were determined to be essentially the
same. General surface condition, though
different (mottled on Reynolds and smooth on
Alcoa) is not believed to be directly accountable
for success or failure in flaring.
Further
testing is being done but at the present time it
appears that chemical composition is a key factor in the resolution of the problem.
PRODUCTION INSPECTION

Ikicrementd in-process inspection co-hcidont d t h
the build-up of the S-IC stage is continuing. The
Quality and Reliability organization is providing
support to Engineering for qualification t e s t i q ,
reliability testing and development testing.
DUALITY ASSURANCE ACTIVITIES (MTF)
Duality Engineering Review

During F Y 1968, quality engineering reviewed 160
facility maintenance instructions, 39 acceptance test
procedures, document D5-11789-100 test procedures,
Bnd all
inshplctionso The
used
were conformance to the end item test plan and IN-IY-S-1C-65- 13 requirements, and the incorporation
of prerequisites, correct sequence, and safety
requirements,

Configuration Accountability
The MTF GSE/MSE configuration definition was
established by comparing the engineering "asdesigned" and the "as-built" configuration, This
configuration assessment establishes the baseline
necessary to support the development of modification programs. The "as-built1' configuration was
used extensively in the review and development of
the planned modifications to incorporate the
engineering change proposals required to update
the S-IC pneumatic console.
S-IC-4 and -5 analysis data showed that Systems A
Dynisco Pressure Transducers in use had a high
failure rate. Investigation showed that, when the
transducers were first received, they were discovered to have an unstable zero. The 150 transducers were returned to the vendor, where some of
the potting was removed to allow the compensating
network to be rebalanced. fnspection of the failed
transducer also showed that the unsupported bridge
compensating coil had failed due to metat fatigue. A
substitate type of p r e s w r e traasducer was obtained
and put in use,

.

D5-12601-5

�- --.
[JRANCE
A

WIwa.

WAC&amp;

AANCE

The objcctive of the Product Performance Assurance
function a t Michoud is to provide incrcwcd confidcnoe
and assurance to both Boeing Management and NASA
that activities critical to the mission o r program a r e
ntified , planned, and accomplished. The organizarts directly to the Boeing Michoud Manager and
im in discharG-ing his obligations for $uccessstags nigh*, ft is raspomible for monitoring.
and assessing the adequacy of technical disciplines
throughout design, production and test, and the integratfon of these disciplines to ensure total product integrity and st'age flight readiness, with supporting data.
During FY 1968, Product Performance Assurance activlties were characterized by a continuation of a riskassessment approach and the promotion of techniques
to strengthen disciplines to minimize o r eliminate
identified risks. Particular emphasis was placed on
greater focal-point administration of the three closely
related disciplines of system safety, reliability, and
quality assurance to provide for increased task selectivity within and among these three disciplines and the
implcmenhtion of selected tasks in order of assurance
effectiveness.

STAGE FLIGHT READINESS
ASSESSMENTS
The final AS-501 formal flight readiness assessment of
the S-IC-1 stage was conducted during the Apollo Program ~ i r e c t o r ' ; Flight Readiness Review on October
19, 1967.
The MSFC Saturn V Program Manager's Pre-Flight
Review (PMPFR) for the S-IC-2 stage portion of the
AS-502 vehicle was held on January 16, 1968. This
review was preceded by a similar review at the IHSFC
Stage Manager's level on January 9, 1968.
The PMPFR presentation consisted of an overall stage
contractor and stage manager's assessment, plus a
~ystem-by-system review of the stage and its peculiar
GSE. The final flight readiness assessment of the
S-IC-2 stage was conducted during the Apollo Program Director's Flight Readiness Review on March
11, 1968. On April 4, 1968, the S-IC-2 stage was
flown successfully. However, the second and third
stages experienced some engine difficulties during
the flight necessitating certain changes to the AS-502
mission profile.

D5-12601-5

Both the AS-501 and AS-502 were unmanned flights.
In the last quarter of FY 1968, NASA designated the
AS-503 (s-IC-3 stage) as the first manned flight,
Assessments of S-IC stage flight readiness ( a Product
Assurance activity) a r e supported and validated
through reviews by the Boeing Performance Board
and Launch Readiness Board (see page 71, which consists of top management representatives from all
Boeing/Saturn Programs. The Manager of Product
Performance Assurance serves a s Secretary of the
Performance Board.

RISK APPRAISAL CYCLE
Work continued during the reporting period on assuring the technical and performance integrity of the
S-IC stage by strengthening the means fox timely
identification of problem sources and dispositions,
known a s the risk appraisal cycle, Figure 2-25 illustrates the sources of problems and screening
processes used to arrive at whether there is any r i s k
to the solution and if s o , is the r i s k acceptable for
the next launch o r does further action have to be taken
before the next launch. This activity is the cornerstone
for arriving at stage flight readiness assessments
a s discussed above.

QUALITY MAINTENANCE ASSURANCE
In February 1.967, ~oeing/Michoudinitiated a program to further assure the quality of vendor hardware,
with primary emphasis on that hardware where failure could cause loss of crew or stage (reliability
critical hardware)

.

During FY 1968, this activity was expanded under
Change Order MICH-544 issued in July 1967 and
Change Order MICH-723 issued in March 1968. The
major areas constituting this program are:

a)

Michoud management team motivation visits to
vendors to re-emphasize the significance of
their hardware in successful Saturn V launches;

b)

In-depth audit of documentation associated with
the engineering and procurement cycle for reliability critical hardware;

c)

Physical identification of hardware (and associated documentation) as reliability critical to highlight its unique stature in the function of the
stage o r GSE ;

63

�SOURCES AND D l SPOSTION OF PROBLEMS
RISK APPRAISAL CYCE

1

O P E N WORK L R B

-

ACTION
BEFORE
NEXT LAUNCH

ACTION

-

-

Z .

POTCNTIAL TECHNICAL CONCLRN

1

+
"TOP TEN"

I

ASSURANCE
A R E A S O F CONCERN

I

I
EVIEW A N D ASSESSMENT

POlNfS

AFTER

P E R F O R M A N C E BOARD

LRB

Figure 2-25

S-tC Risk Appraisal Cycle

d)

Hardware review at vendors for such disciplines
a s receiving inspection, processing methods,
and quality control standards;

e)

Quality hardware analysis of vendor hardware
consisting of both destructive and non-destructive
testing; and

f)

Design confidence tests consisting of selected
testing modes to augment and reinforce the qudification test program.

Considerable progress was made during this fiscal
year in accomplishing these objectives which are time
phased for completion by the end of 1970. Results to
date are contributing to increased confidence in total
product integrity. Figure 2-26 is illustrative of the
visibility given to this effort in the ~oefn&amp;tXIZichoud
Program Control Center.

I

#FAILURE A N D CORRECTIVE ACTION
PROGRAM
Continued emphasis was given to the area of hardware
failures to further improve the disciplines involved in
identifying, evaluating, tracking, and closing out such
failures on a timely basis. A closed-loop system was
established between Michoud and Boeing Atlantic Test
C enter to provide for "real-time" visibility on failures.
Also, a Failure Review and Assessment Board was
created to review, assess, and dispose of W s e failures impacting the next launch. This board is composed of representatives from Engineering and Product
Performance Assurance.

SYSTEM OPERATION A N D S A F E N
ASSURANCE
An 5-IC Integrated Safety Program was established in
October of 1967 under the administration of Product

I

�Figure 2-27

Figure

2-26

5-IC

Organizational Safety Relationship

Quality Maintenance Program

PesEormfmaa Aaeurace, TMhfr pragrrun 18 respamiw
to Boeing Corporate Policies and NASA requirements,
The nwel aspect of t h i s program is that it combines
and integrates the heretofore separate industrial and
system safety into one safety plan and calls for organizational ancillary plans responsive to this master
plan.
Product Performance Assurance controls and maintains the master plan, approves the ancillary plans to
ensure total safety integration and compatibility, chair
the S-IC Safety Board consisting of organizational representatives and provides program direction as recorn
mended by the Board. This arrangement provides for
a single safety focal point for increased management
control and improved visibility of safety performance
versus assigned tasks. Figure 2-27 illustrates the
organizational safety relationships including the composition of the S-fC Safety Board while Figure 2-28
depicts the controlling safety documentation for this
integrated safety program.
The S-IC Safety Board is chartered as a management
working group to provide the means by which the combined attention of all organizations can be directed toward assuring safety excellence in the S-IC program.
The Board meets on a regular basis and provides sui
effective tool for the integration of organizational acb
tivities relating to hazard tdentification m d control,
Visibility on these activities is m-d
in the
Boeing/Michoud Program Control Center,

Figure 2-28

Integrated Safety Program Controlling
Documentation

The line control safety effort is recognized as a continuing vital element in the master safety plan as is
the Line Control Safety Council of line safety directors.
This Council, as an adjunct to the S-IC Safety Board,
continues to specifically assist line supervision assigned to production, test, and laboratory operations
in carrying out their line control responsibilities.

PRE-OPERATIONAL SAFETY REVIEW
During F Y 1968, a pre-operational system safety review of the S-K-1 and -2 was held at KSC to provide
for increersed safety assurance. This was carried

�out aa part of a total system safety review of the AS561 aad 4 0 2 under Program Directives 44 and 44%.
The purpose of these directives, as they relate to
BoeIng Schedule I, is:
a)

-

b,

44

-

Provide correlation of the S-IC-1 configuration baseline and m a w e #at the 84G-1
launch vehicle, design, hardware, test
specifications and criteria, software, and
test procedures were consistent and
compatible.

'* - ments within Schedule I design'yetern
'lea
and/or
glosurance

respansibiljtty are technfc*
accurate, adequate, consistent, and cornn
patible for AS-502 and -503, GSE, and
KSC facilities.

MSFC SYSTEM SAFETY NETWORK

NEW T E CHN ()LOGY
During 1968, a total of 54 New Technology disclosures
were reported from Schedule I. One such item, which
should have broad appeal, is a technique for makiw
view graphs very quickly from expendable printsd matter, such a s magazines. The resulting transparancies
mW be either in
Or
and white*

,

DELIVERABLE DATA
Data submitted during PY 2868, in oompliance with
the requirements of Contrwt NAS8-5608 (Schedules I
&amp; IA), are included in Append&amp; D. Delivery of these
items was in accordance with requirements wt forth
in Document IN-I-VS-IC-67-10, "5-IC Progpaaa Deliverable Data. l1

TECHNICAL SUPPORT DATA

.

��SUMMARY
Facilities improvement activities at Michoitd during
the fiscal year were concerned with fmprovcment of
Boeiw/Alichoud production and fnbricntion capabilities. A s R pnpt of this program, flve numerically
controlled machines nwre iwtalled and checked-out.
Rearrnngoment and removal of outmoded machinery
is also being accomplished.

certain stores areas in the factory building,
Boeing's activation tasks at the Miesissippi Test Facility were completed during F Y 1867. The formal
letter acknowledging completion of the required tasks
by The Boeing Company, was received from NASA on
April 18, 1,968.

�tion of certain areas nnci a reduction of space required
for other functions.
The installation of a new GOO0 psi CN2 gas header line
In the high pressure test facility was completed during
tho third quarter of FY 1968. Also, a request for additibnnl paving at the high pressure test facility was
submitted and approved a s a NASA in-house responsibi1it-y. Thn l ~ c wpaving should be completed early in
F Y 1969.

SUPPORT AND GENERAL P U N T
ROCKETDYNE FACILITIES MODIFICATIONS

Modifications to the Rocketdyne area of the manufacturing builcting ware accomplished during March 1968.
These modifications, which were requested by NASA,
consisted of providing an office area and additional
clean room capability, upgrading the helium supply,
and completing other modifications which provided
Rocketdyne with a complete working operation. Also
in March 1968, at
request, all thermal iwulation b f a n w s were transferred to RockeMyne for
fication prior to shipment to KSC, Rocketdyne was also
assigned 23,000 square feet of storage space on the
south mezzanine to provide the space necessary to store
and modify the insulation blankets.

for additional equipment and the increasing need for better utilization of ow: existing equipment. It is estimated that there will be over 10,000 general-purpose type
items that will be controlled and issued through the centralized store.
During the pnst year, a rebuild shop, which allows
BoeingJMichoud to rehabilitate machines that would
otherwise require outside support, was established.
OFFICE

Significant progress toward reducing coets on the Saturn
program was made during the fourth quarter of FY 1968
by consolidating office space. Plans are to deactivate,
in early FY 1969, the entire southeast wing, first floor,
of the Office and Engineering Building (No. 350). This
will result in a considerable reduction in operations and
maintenance costs over the ensuing years.
TRAFFIC

The Facilities organization, in conj~nctionwith the
NASA-Michoud Traffic Safety Board, alleviated a large
number of internal safety and traffic problems b.Y installing caution signs at dangerous intersections, adding additional speed limit signs and roadway markings,
rerouting traffic and rearranging parking spaces in the
parking lots.

UTlLlZATlON FACILITIES FOR EQUIPMENT

A utifization system for equipment was completed in
November 1967 and it will be implemented a s soon as
the switchover to third-generation computers is complete. This is an electronic system that monitors utilization of equipment items, such as machine tools and
related production suppart equipment. Utilization is
defined in terms of equipment run time, time under load,
downtime and maintenance time, and is measured and
recorded in actual hours on a real-time basis. The system is completely automatic from point of origin to
actual recording, and can monitor up to 1000 pieces of
equipment. All monitored equipment is connected to a
central recording console via hardwire, and utilization
of each equipment item is recorded on a machine processible format for computer input.

MICHOUD FABRlCATlON PLANS AND
ACTIVITIES

"

-

GENERAL R A N T

-

The Facilities organization has implemented a centralized store concept that incorporates all general-purpose
type test and production equipment. This plan was hplemented in view of the decreasing avairabilie of funds

72

STAGE STORAGE

Early inFY 1968, it was recognized that there was not
sufficient storage area for S-IC stages atMichoud. This
inadequacy became a reality when revisions occurred
in the transfer and transportation schedules of stages
from Michoud to KSC At this time, Facilities planning prepared several proposals and a recommendation
to solve this problem. The stage storage plan was presented, accepted, and approved byNASA. To implement
the plan, it was necessary to relocate the specimen
preparation area and major painting facility, and to
double-deck certain stores areas within the plant.

.

Supplemental Agreement MICE-596 was received
in August approving the storage plan. As a result , 14,000 square feet of double-decking was confitructed for storage space (8000 square feet in the
factory building and 6000 square feet in the vehicle

'

component supply building). Positions 1 and 3 were
completed on schedule and supported the revised delivery schedule. Position 2 became available inApril
1968, Alf effort connected withthis project was completed in June 1968, when the floor and ramp repairs
were completed.

D5-12601-5

�AUGMENTATION, MODERNIZATION,
REHAEffLITATIOM A N D REBUILD
PROGRAM
Approved F Y f 967 funds (Contract NAS8-5606(F)) for
modification, replacement, and rehabifitation amounted
to $1,895,195, Thesc funds have either been oomc
rnitted o r a r e in the processof beingcommitted. During F Y 1968 5930,000 worth of funds were approved
f o r Contract NASB-5606(F).

b,
' i '

MISSISSIPPI TEST
FACILITY
P a s t annual progress reports have concentrated on
the facilitfes activation &amp;%sirsat MTF During FY
1967, The Boeing Company's facilities activation tasks
a t MTF were completed. The letter certifying cornpletion of activation at MTF was submitted to the
NAW/MTF Contracts representative for concurpence
on January 24, 1968. The letter of completion, recognizing concurrence on the part of The Boeing Company,
was reccived by Boeing on April 18, 1968.

.

S-1C-5 STATIC FlRtNG ACTIVITY
The S-IC-5 was installed in the S-IC test stand at MTF
on June 29, 1967 (Figure 3-2). Stage electrical connections were completed on July 12, and on July 13,
1967, power was applied. Propellant load tests were
eompleted by August 9, 1967, and the stage was successfully static fired for 125.096 seconds a t 6: 14 p.m. ,
August 25, 1967 (Figure 3-31, The S-IC-5 stage was
removed from the static test stand on September If,
1967 (Figure 3-41, and returned to Michoud at approximately noon the following day.

Figure 3-4

S-IC-5

Being

PROBLEMS ENCOUNTERED AND RESOLVED DURING S' S-IC-5
STATIC FIRING ACTIVITY

Figure. 3-2

D5-12601-6

S-IC-5 in Test Stand

Thrust Vector Control (TVC) system checkout began
July 21, 1967. During checkout, two Hydraulic Research servoactuators were found to be defective.
They were returned to the vendor for failure analysis
and replaced with serviceable items. TVC system
oheelrout was completed August 4, 1967.

73

�XPP-1 tanMag commenced J d y 25, 1567, After tanlciw
ha&amp; reached ?O wrcent fill level a shtdrlown ww called
due ttz Chc collapse of a fucI emergency drain duct
(Ffntra 3-51. An hZTF investigutinb. committee was

In~media'delyfosmezl to determine the cause of thLq ini~fcfonk. Spocblad test rbcju$remon~WOFQ orntlhed ts
dewmine the recirculation flow m d pressuse charactcristics of the facility fueling system, These tests
WCP'C co~niJuctedan J u l y ZF, 1967, and sufficient negative
preusttrss were encountered within tire system to have
a a u ~ s dthe duet t o coifapse (a ctoscriptiou of the cmses
ol Chis oollgf,'se w e @apage 45), dHI a l g a lp~owlXsmt
t e s b were 8usprenete-d pending a review and evaluation
by the Branch investigation t e r n wNeh was held July
27, XOG7, The facility fael emergency drain duct sysQ S ~
~ k &amp;$ubst"que~tly
q
modified a d rehrued to operatSoaal eodi~w;llsatiotl, F i n d Branch investigation
t e r n recommenrfations for revising LOX loadp r ~ c d u f e swere complied with prior lo pyaload bstts, which were completed on
4rernreb

a

re=-

,high pressurr?a, therefore , on August 5 , 1967, i t was
removed and replaced.
During preparation for the S-IC-5 static firing engine
servoactuators were changed out f.4 times because of
le&amp;ge, axereme limit cycling, out of specification ia
the lock-off-null position, anci piston rod seat leaks out
of tolercmce,

".

Duriw static firing of thc S-1C-5, a Z-inch piece of tha
tarbinn? h i s t tomperatuse maasr~iwtthsrm~colngle
crgehd md brake, off, Eta~XreMyaefowd the pigcs in
one of the turbine manifold nozzles of engine position
102. The piece trm removed and the exl@ne returned to
o p e r a t i o d corrf~wration,a pressure leak check retest was aaQsfactorily performed oa September 8 , 1967,
PLtST-STATIC FIRING ACTiWifY

Qn A~tgust31, 1967, a stand-up presentsttion ~vmgiven
by B w u g to stuumarize the static firing five-day
"Qdck Lmk Repot%," This presenbtiaa revealed that
'94 perceat of the System "Ar7measurements recorded
during static firing of the S-XC-5 \%re good.

A lf Certificates of A ccamplishen~tfor completion of
the S-XC-5 acceptance test procedures were rebased
by September 26, 1967,

8-iC-B STATIC FIRtsNB PREPARATBOM
The S-IC-6 stage was shipped from Mic2loud and mrived at MTF on March 1, 1968. The stage w s then
placed in the tata at if test ~ h ondN w e h 4, 1968.

Y

A req~xisement11y fada&amp;% to rerun s h hfSE a~domatic

checkoat procedmes , psiur
~ t a g epower-on, delayed power-on from M u c h 25, 1968 to April 4, 1968.
Three of the six MSE ~utomaticcheckout procedwes
that NASA reqEEir@dto be rerml cont.talaed errors and
were returned to Michoud for correction, Initid
power-oa was sxaeeessfully accomplished on April 4 ,
1968, a d heat shield installation was ssu@@essfally
completed 0x1April 5.

i

Figure 3-5

Calfapsed S-1C-5 FweO Emergency Drain
Duct

During the imtallation of a heavy manudl efig2oe aeluator on J d y 35, 1967, tkte No. 1 fuel &amp;&amp; pressme duct
on e e e 1Q4 m go~ged. Af er the gauge was polished, in accordance with a RockeMyn~disposition, Uzo
NoU 1 &amp;el high pressure riuct waas, b e &amp;in to suppor-f;

74

On Agrfl23, 31968, %-IC-Ci s t d i e firingactivity was .
suspended n$th the exception of 8utborized modifications,
This w m cFo~.loso tllczlt several m d f i c a t i o ~ ~
resulting
s
from AS-502 Bight iuadysis could b incoa.psrated rtnd
teslhd on the 6-IC-6 prior to the decisim to ixlelude
them on the 6-EC-3; the prhcipipali changes to be tested
a r e V 0 6 8 s@pressioa systems (set? pwe 37). A review of cbmges affecting t h 8-16-6
~
was conducted with
tXne purpose sf "raUing back? dl chmp;es practicable
for aecompl1Isbment prior to 8 Inter s&amp;Bo f i r i w sched-

ule,

135-12601~-5

i
i

.

,

�fncorporatlon of tflc required POGO suppression sys- ,
tern on tile S-IC-G began on June 14, 196s. Stage
power-on was trccon~plishedon June 26, axid static firing of the S-IC-li is scheduled for Auwst 6, 1968,

S-IC-D FUEL TANK DRAIN TESTS
(ANTI-VORTEX)

-

dl ;-crrit?xi~gcund'ition was observed during Ij8tl-j segment fuel tank drain tests at Michoud. A vortex formation in the fuel Lank during flight could cause gas ingestfon at tile engine fuel punlp inlets, and could result
in engine explosion. Because of a need for Eurther testing, the S-IC-D was installed in the MTF static test
stand (Figwe 3-6) and modiffed s o that water drain
tests could be conducted to determine i f a vortexing
condition existed in the stage fuel tank. Modifications
included removal of tlie S-iC-D engine simulators, and
Figure 3-7

Plexigiass ~ u c t sInstalled on S-IC-D

ing, it was decided to terminate drain tests, and replace S-XC fuel tank anti-vortex assemblies with
a~qsembXiesof the same design as those used on
S-XC-1 and -2.

S-IC PNEUMATiC CONSOLE

Figure 3-6

instaliation of S-IC-D in Test Stand

installation of necessary monitoring equipment including ten plexigl,ws ducts which were installed on the
fuel ducts to allow high-speed photography of bubble
ingestion patterns f see Figure 3-7),
~ea;in(: began on December 18, 1967 and was completed on Jaztliazy 27, 1968. During that period of time, a
total of 20 tests were cortducted on four different antivortex bdtlea. The basic test consisted of filling the
fuel tnnk ~4thwater to the 40 percent level and then
cameras located inside
record bubble fctrmatio
Test data reduction was comple

Work continued throughotd FY 1968 to revise the pneumatic console vent and relief circuitry. The original
vent and relief circuitry was not designed for a "wide
open" reedator failure. If this type of failure was to
occux, it would came an over-pressure condition to
exist i n the do\riastream piping and could abort a launch.
For various reasons, but principally because of the unavailability of parts, the work of modifying the console
was sporadic, workarounds were implemented so console modifications would not affect S-IC -6 power-on.
GROUND EQUIPMENT TEST SET

Because the manual Ground Equipment Test Set (GETS)
was designed as a continuity tester with no automatic
stage simulation capability, stage sequence tests could
not be verified without an S-IC stage. To eliminate the
use of an S-XC strage as a test fixture for verifying
ground support equipment. operation and for developing
t programs, the manual GETS
to a super or automatic GETS
ion. This modification was begun on Octomd completed November 17, 1967.
ckout was completed Novembor 27,1967.

75

�in static firing, was incorporated. The pipe assembly,
necessary for the rework activity, was built at Michoud
and delivered to M T F on April 26, 1968. The change
was functionally complete on May 13, 1968,

GSUMSE

t

?

i
t

1

I1
i
i
I

I
/:

Early in J~inuary1968, General Electric QuLzlity znd
HeUabiliW Assurance Engineering reported that comblning Stngefok and Cyrolok tube fittings could cause
"a potential hazard to safety, tutd a detriment t;o operatlon," General Electric hnd been issuing the tube fittfngs on tho assumption that the two varieties were interchmgeable in all combinations, A Boeing committee
'K'W appointed to investigate the possibility of any
anomalies in the Ground Support Ecluipmenthfanufacturt?rsQuppo~tEquipment (GSE/NISE) installations.
An bvcsltgaU.an wa9 conducted as a result of Uloir
findings m1d it was determined that no intermiuing of
S~tageloMGyroloktube fitting components existed on
the S-IC static test stand, cw stated in the oommitteelrr
rcport of M u c h 1968.
Work was started iti l a b February of 1968 to provide a
capability for remote pressurization and venting of the
GOX ductsystems, The test fLuture, used to marmally vent the COX ducting system during confidence
and leak tenting, presented a s d e t y hazard during confidcnce testting and therefore did not meot personnel
safety requirements

j
f
I

.

The tost fixture was sent to Michoud for re~vurkon
February 26, 1968, and a workaround version, borrowed from Michoud, was modified for use a t M T F during the time tile reworked test fixture was at Michoud.
a

i\iaGficatioxt of the hydraulic terminal equipment to
eliminate l e m e and/or functional failure of the pneumrrticdy operated ball valves and ~ s o c f a t e dp n e u m t u
ic and electrical controls, which would cause a dolay

Work to add rQmoh vQntfW$CWabfliW to gmeow
nitrogen (GN2) control pressme s p s b m s was started
on March 18, 1968. This ~ v a sdone to eliminate a
potellaal Wrsonnel safety hazard by providing remote venting. of trapped high pressure GN2, and to
retain sufficient GN2 pressure to allow prevalve closure during flight to ensure mission cornplotion. The
change was originally committed to be i n s t d e d at
Michoud prior to stage shipment to M T F but, because
of the late delivery 6f hardware, the change was made
at M T F .

,

The change to add the above mentioned remote venting
to the ON2 control pressure system made it necessary
to remove the stage mounted prevalve accumulator
bottles from stages S-IC-6 and on. Certain tests, performed to v e r i b operation without the accumulators,
were sdisfactorilly completed and the change was begun at M T F on Mwch 18, 1968. The tubing required
to add remote venting and to remove the accumulator
bottles was sent to Michoud for fabrication, testing,
and cleaning. Installation and functional checkout wm
conrploted on March 26, 1968,

MTF DQCUMEWTAP1ON
Boef.q/WI.Tf" document statup, for FY 1968 is indicated
Jn Appendix G,

r

*

Q

76

D5-12601-5

���DOCUMENTATION
$UPPORT
"S-IC LOGISTICS LAUNCH SUPPORT
PLAN," DS-13705
This document describes the actions necessary to ass u r e complete and timely Schedule 1 logistics support
for the S-IC launch, and has been updated to incorporntc changes resulting from the S-IC-1 launch. However, there knvc been no signlficttnt changes in the
manner o r scope of logistics support.

SPARE PARTS STATUS SUMMARY
The Stock Status and Consumption Report, DRD MFhas been deleted by con506B of IE-I-VS-IC-65-10,
tract change and replaced by a Spare Parts Status
Summary, DRD LS-078 of EN-I-VS-IC-67-10,
for
each stage. Reporting for the summary of each stage
is to begin thirty days prior to the on-dock KSC date,
and will reflect logistics1 support position for that
stage,

TECHNICAL SUPPORT DATA
Publication of S-IC stage and GSE technical manuals
continued on o r ahead of schedule throughout FY 1968.
During this period a complete revision on the S-IC-2
Stage Maintenance and Stage Flight Measurement Manuals was published. Also, a total of fifteen GSE technical manuals were revised.

"LOGISTICS INFORMATION REPORTING
SYSTEM," 05-13759
The implementation of third-generation computing
equipment necessitated reprogramking the logistics
reporting system. A study was conducted to devise
a system which would utilize the potentials of advaiced computing equipment and better satisy Iogistics' needs. The resulting system has been documented in D5-13759, "Logistics Information Reporting system, I' and is scheduled to be implemented during October 1968,

CENTRALIZED INVENTORY CONTROL
SYSTEM
q

Implementation of a centralized inventory control
system was postponed because of a delay in the avail-

ability of video displays Cathode Ray Tube (CRT)
units. When available, these units will allow direct
communication with the file in a third-generation online computer, and will function a s an integral part
of the logistics program.

SPARES SUPPORT
Three "sparesv hardware stores were supported during FY 1968. The Michoud store was used as a central store for test site provisioning and a s a site support store for post-manufacturing checkout and poststatic test checkout operations at Michsud.
Stock at the MTF store was built up and maintained
in support of S-IC-5 and -6 static tests. A limited
number of parts from ,the MTF stores were diverted
to KSC for backup support of launch critical applications, however, a full inventory level at MTF was
maintained. The S-IC-1 and -2 launches were successfully supported with no delays caused by spares
shortages. At the end of the fiscal year, stock levels
were satisfactory at all sites.
The task of refining and operating an effectiveBoeing/
vendor repair program for failed repairable components is being reviewed. This review has important
implications for future spares support due to kxtensions in the program performance period.

PERSONNEL SUPPORT
To assist BATC in the spares liaison effort to support the S-IC-2 test and launch, Logistics Engineering placed two additional spares maintenance representatives at KSC prior to the beginning of the Countdown Demonstration Test. The loan of these two additional liaison personnel provided round-the-clock
liaison between Michoud and KSC , resulting in rapid
resolution of any spares problems that might have
impacted test and launch operations. The personnel on
loan returned to Michoud immediately after the launch.

SPARES FOR GOVERNMENT
FURNISHED EQUIPMENT
A logistics problem was encountered with the GFE

provided to MTF by MSFC and operated by Boeing.
This problem is associated with lack of design definition and resulted in our inability to obtain formal design and drawilig corrective action on discrepancies
noted during spares provisioning and procurement
activities. However, in spite of such problems, the
spares support position for GFE has continually improved during this reporting period,

.

����LAUNCH OPERATIONS
There has been an on residence Test Conductor at
BATC from s-fC Systems Tests T e s t Engineering and
Operatiom M ichaud to support AS-$03 processing.

-

depth review and audit of all change incorporation, rework and retest activiQ involving the S-IC-3 from the
end of Post-Manufacturing Checkout (Simulated Static
Firing, 8-24-66) through May 1968. This review was
directed by NASA a s a result of the AS-502 flight failures. The initial Branch report was submitted to the
customer on June 5 , 1968.

����APPENDIX A

APPENDIX C

CONTRACT MODIFICATIONS

NEGOTIATIONS COMPLETED

The number of contract modifications
received during the period July 1, 1967
through J w 30, 1988, i e as follows:

The number of negotiations completed
with NASA during the period JuIy 1, 1987
through June 30, 1968, is as follows:

Contract NAS8-5606{F)
Ctantrnat NAS8-5608

Csntraat NAS8-1BIM

--

6
251

Cohtraet NAS8-5608
Gontrwt NA68-29844

1

--

93*
1

*Totaling approximately $8,155,063

APPENDIX B

APPENDIX D

PROPOSALS SUBMITTED

DELIVERABLE DATA SUBMITTED

The umber of firm cost proposals
aubrafmd ta N A a dwiq Mi@ period
Ju&amp; 1, $867
Ju\ht $08 28813, le

The number of items of deliverable data
submlmd $Q &amp;A% duardxag~the priad
July 1, 1867 Ukraugh 3we 90, lQ4i8, i a
as foIlows:

as follows:

�APPENDIX E
ENGlNEERtNG CHANGE DOCUMENTATtON
COMPLETED DURING FISCAL YEAR 1968
CHANGE NO*

DESCRIPTION

EFFECTIVrl'IES
STAGE
GSE

0247

Provide filter networks to reduce noise susceptibility and realign LOX and fuel loading electronics
assemblies

0248

Replace orifice irk fuel pre;prasrsuriaation
msdufe of the S-EC pneumatic cansole

MTF f
MILA 1, 2, 3
MAB

0249

Redesign aft umbilical # 1, $2, and #3 ball
valve actuator arm

MILA 1,2, 3

0250

R p o v e ground umbilical fluid couplings from
spare locations in S-IC umbilical equipment

3-15

0261

Replace helium shutoff valve with a check
valve

1-2

0264

Replace roller stops on LOX interconnect
support bracket installation

1-15

0265

Replace roller cams on LOX interconnect
support brackets

1-3

0266

Provide capability to vent downstream of
helium bottle fill isolation valve

0267

Rework circuitry of the DC-DC converter
and DC power isolator

0269

Provide separate vent lines for the presertation
module of the forward umbilical service unit

MILA 1, 2, 3

0270

S-IC engine alignment check

MTF 1

0273

Provide identification of S-IC stages by numbers

3-15

0275

Provide manllal ground control of stage prevalves at K5C

1

MILA 1, 2, 3

0276

Provide power-off turbopump seal purge
capability

1-15

MILA 1, 2, 3

0279

Prevent corrosion of spherical rod-end bearing used throughout the S-IC stage structure

2-15

provide electrical bonding of retrorocket and
manifold

1-15

9

E

1-15

MILA 1, 2, 3
MSE 1, 2

MAB

MTO 1
MAB
MILA 1, 2, 3

1-15

c

e

0280

' CDF

98

D5-12602-5

�CHANCE NO.

DESCRIPTION

E FFECTIvlPTfES
STAGE
OSE

0285

Incorporate improved lockwire installation
procedure on fluid power system duct insulation installation

3-15

0286

Revise visual fnstrumentation camera port
squib cable assembly

2, 3

0288

Add remote venting caa&gt;abiIlty of GNZ control
prsssurtzation sysbm

2-15

MTF 2
MSE 1, 2
MAB

0289

Remove stage mounted prevalve accumulator
bottles from the S-IC vehicle

6-l6

MAB

0290

Modify the fuel tank prepressurizsation module
of the S-IC pneumatic console

MTO 1
MILA 1, 2, 3
MAB

0291

Revise engine cocoon thermal conditioning
controls and thermocouple cable acceptance
test requirements

0295

Revise S-IC Level I electromagnetic
compatibility test requirements

0298

Add inlet filter to the forward umbilical
service unit

0299

Provide sealing of stage structure to prevent
equipment damage from rain w a b r

1-15

Provide redundant electrical power circuit for
fuel pressurization system

3-15

0302

Replace 50M04050-1 Hydraulic Research servoactuator with 60B84500-1 MOOG servoactuator

1

0303

Modify the S-IC pneumatic console LOX/fuel
prepressurization modules

0305

Rework 60B84500-3 Hydraulic Research
servoactuator

3-15

0306

Rework prefiltration valve subassembly on
MOOG servoactuator 60B84500-1

3-15

0309

Relocate the positive pressure line on the LOX
and fuel tank upper m e a d s s

4-15

0300

D5- 12601-5

*

I

I

MILA 1, 2, 3
MAB
7-15

MILA 1, 2, 3

MILA 1, 2, 3
MTO 1
MA3

99

�G&amp;MNGENO.

EFFECTNITIES
GSE

8TAGE

EfESCItFPTION

Provide separate mounting of three pilot relief
v d v e subassemblies in the S-IC pneumatic
console

0312

MTF 1

MILA 1, 2, 3
MAB

0313

Revise electrical surge suppression circuits in
the S-IC pneumatic console

0315

Delete non-flight hardware from flight
documentation

2-15

0316

Rework the Hydraulic Research servoactuator
50&amp;104050-1 removed from S-IC-1 and use them
for S-IC-2

2

0318

Add LOX pressure sewing line to the intertank umbilical reconnect assembly

0320

Revise fairing turn buckle attachment fitting
material to 7075-T73

1-15

032 1

Provide Parker LOX vent and relief valve as
standby for Whittaker LOX vent and relief
valve

I

0322

Provide explosion proof enclosure for prevalve ground accumulator pressure spheres

Sr

MTF 2
MILA 1, 2 , 3
MAB

MILA lr2, 3

MTF 2

MILA 1, 2, 3

0323

Revise S-IC propellant dispersion system
installation

2-15

0324

Revise test requirements and procedures for
ordnance safe and arm device

2-15

t

MILA 1, 2, 3

0328

Rework the intertank umbilical locking
mechanism

0329

Reroute cable installation on fins B and D

2-3

0330

Substitute amplifier used for ten mandatory
prelaunch red line temperature measurements

3-15

10332

Revise the S-IC stage thrust structure hazardous
gas detection system to provide sampling orifice
in each quadrant

3-15

0335

Remove, retest and re-identify dl 65B23280
check valves

MSE 1, 2

MTF 1
MILA 1, 2, 3

Q

100

OM4

Modify the fairing heat shield access panels

3-15

0345

Add weather protection covers to base air
scoops

2-15

I%-1260 1-5

�DESCRIPTION

EFFECTlVITIES
STAGE
GSE

iminate 17-7 P H mechanicd feed back
rings in trydrauh Research S-IC servo-

3-15

im engine fairing skin to prevent injury

3-15

odify servoactuator jack pin assembly

MSE 1, 2
MTF 1

WILA
evise materid of stage anti-friction plates

3-15

Provide additional vents for the servoactuator and Boeing supplied engine thermal

2-15

dify servoactuator boot fitting installation to
lace fasteners with through bolts

3-15

Change S-IC documentation to comply with
KSC pull test requirements

2, 3

Provide positive moisture sealing of electrical
vities for the 60B49002 helium pressurization
d emergency dump valves

2-15

ncorporate improved position switches in the

2-15

LOX tank vent and relief vqlve (60B51002f

Instdlation of the ordnance bracket assembly
on the LOX and fuel tanks

2-4

Protect electrical cables a entry {forward and
aR) to stage from electricd tunnel

2-15

Revise S-IC propellant dispersion system
installation kit
Provide uninterrupted power (+28 VDC) to LOX
and fuel loading electronics

KSC Genl
3-15

Modify S-IC interta.uk umbilical lock
mechanism

MILA 1, 2, 3.

0372

Modify the S 4 C pneumatic console helium
primary regulation circuit

MAB
MTF 1
MILA 1,2, 3

0374

Revise the main sed in the LOX fill and
drain valve

335- 4260 1-5

3-15

�CHANGE NO.

102

E FFECTWITIES
STAGE
GSE

DESCRIFTION

MLA 1

0377

Modify the S-IC storage racks to provide
protection during launch

0379

Replace vent seals on all Aireseareh prevalves
md emergency drain valves

5-15

0382

Eliminate H e flow overlap of the stage and
ground fuel tank pressurization system

2-15

0888

Modify filter m W o I d delta pressure

9-31s

0396

Block debris valvejs in S-IC intertank reconnect
assembly LOX fill and drain lines in the open
position

0401

Provide locking and position indicating
mechanism for S-fC pneumatic console and
forward umbilical service unit

MSE 1, 2

MILA 1

MTF 1

MILA 1, 2, 8
MA33

0406

Modify TV objective lens housing assembly

2,3

0411

Provide drain for servoactuator rod seal
leakage

2-15

0414

Replace bolts in fairing heat shield access panel

3-15

0415

Replace 50M04049 MOOG servoactuator with
60B84500 MOOG servoactuator

2

0419

Provide new latch on the S-IC intertank
umbilical reconnect assembly

MILA 1, 2, 3

0848 R1

Replace pressure gage in forward umbilical
service unit

LUT #1, #2, #3

0866 R1

Modify heater blanket assemblies

1-3

0867 R1

Modify base heat shield installation

1-15

0868 R1

Modify connector hex nut

3-5

0870 R1

Modify base heat shield support angle
installation

1-4

0871 R1

Correct bolt lengths on lower fairings

3-15

0873 R1

Modify support installation to allow
installation of the recoverable camera

2, 3

0874 R1

Correct bolt length on thrust structure baee
air scoop installation

1-15

0875 R1

Provide pilot relay for heater power contactor in 5-IC pneumatic console

MILA 1, 2, 3
MTF 1

t

D5-1260 1-5

�E FFECTlVrl'IES
CHANGE NO,

DESCRUPTfON

STAGE

0876 R l

Modify ground cables in TV camera system

2, 3

0877 R 1

Modify retrorocket initiation system

1-15

0879 Bl

-

MILA 1

Modify tube assembly in the pneumatic console

0880 R 1

Eliminate an out-of-tolerance condition in
the LOX leakmeter measurement F45-118

1-5

0883 R 1

Correct bolt length callout on servoactuator
boot installation

1-15

0884 R 1

Modify length of cable assembly 115W305

1-5

0885 R 1

LOX f i l l and drain valves (3-239, B240)

MILA 1,2, 3
MAB
MTF 1

control valves reversed cables

0887 R1

Calorimeter purge line clamp

0889 R 1

M9dfa7S-IC inbrtank umWUed to delay

GSE

2-5

XMXu

olotswe of detJsir%r
vRIvr3
0891 R 1

Heat shield panel installation

2, 3

0892 R l

Electrical installation forward skirt

2, 3

0893 Rl

Eliminate leakage in LOX pressure sensing line

MILA 1, 2, 3

0896 R1

Housing assembly aft 1 and 2

MILA 1, 2, 3

0897 R1

Rebonding of anti-friction plates

2

0903 R 1

Engine fairing blanket assembly

2-15

0904 R 1

Cable and instrumentation installation
units 101 and 102

2-4

0906 R 1

Measurement installation fin B

2, 3

0907 R 1

Propellant dispersion system installation
and retrorocket initiation system

2-15

0908 R1

Change bolt callout

2-15

0913 R 1

Rase heat shield bracket misalignment

3-15

1214 G

Increase accuracy of GOX flow control valve
pilot pressure measurement

I
I

MSE 1, 2

��ENGINEERING CHANGE DOCUMENTATION
I N n l A T E D DURING FISCAL YEAR 1968
CHANCE NO.

e

DESCRIPTION

E FFECTTVPTIES
STAGE
GSE

Reduce the fuel and LOX tank standby pressure
output in the forward umbilical service unit

MILA 1, 2, 3

0231
Cancelled

Provide 6-IC engine hydraulic sysbm
pressurization for stage shipment and storage

MILA 1, 2, 3
MTO 1

0242

Modify S-IC pneumatic console to provide
pressure calibratian source in mobile launcher
room

MILA 1,2, 3
'NIAB

0247

Provide filter networks to reduce noise
susceptibility and realign LOX and fuel loading
electronics assemblies

0248

Replace orifice in fuel prepressurization
module of the S-IC pneumatic console

MTF 1
MILA 1, 2, 3
MAB

0249

Redesign aft umbilical #1, #2, and # 3 ball
valve actuator arm

MILA 1, 2, 3

0250

Remove ground umbilical fluid couplings from
spare locations in S-IC umbilical equipment

3-15

0251

Modify the length of the telemetry antenna
feed cables

3-15

0260 *
Cancelled

Replace angular rate gyros for measurements
R4-120, R5-120 and R6-X20

2-15

0261

Replace helium shutoff valve with a check
valve

1-2

0263 *
Cancelled

Provide venting for stage access equipment
storage racks

0264

Replace roller stops on LOX interconnect
support bracket installtion

1-15

0265

Replace roller cams on LOX support brackets

1-3

0266

Provide capaljility to vent downstream of
helium bottle fill isolation valve

*

1-15

MILA 1, 2, 3
MSE 1, 2

I*

MAB

MILA 1, 2, 3

MTO 1

MAB
MILA 1, 2, 3

0267

D5-1260 1-5

Rework circuitry of the DC-DC converter
and W: power isdatas

1-15

105

�DESCRIPTION

CILZNGE NO,

EFFECTrnfES
STAGE
CSE

0269

Provide separate vent lines for the preservatioa
module of the fortvard umbilical service unit

MILA 1, 2 , 3

0271)

9-IC en&amp;&amp;@alignment check

MTF 1

0272

Provide S-IC forward skirt access equipment
for access to S-II engfnes

2-15

0273

Provide identification of S-IC stages by numbers

3-15

0274 *
Cancelled

Remove umbilical fluid coupling from spare
location on S-IC umbilical equipment

2-15

MSE 1 , 2
MTF
m u 1,2, 3

0275

Provide manual ground control of stage
prevalves at KSC

1

MILA 1, 2 , 3

0276

Provide power-off turbopump seal purge
capability

1-15

0279

Prevent corrosion of spherical rod-end
bearing used throughout the S-IC stage structure

2-15

0280

Provide electrical bonding of retrorocket and
CDF manifold

1-15

0285

Incorporate improved lockwire installation
procedurw on fluid power system duct
insulation installation

3-15

0286

Revise visual instrumentation camera port
squib cable assembly

2, 3

0287

Modify Marotta solenoid valves (65B23278)

0288

Ad&amp;remote venting capability of GN2 control
pressurization system

2-15

MTF 2
MSE 1, 2
MAB

0289

Remove stage mounted prevalve accumulator
bottles from the S-IC vehicle

6-15

MAB

0290

Modify the fuel tank prepressurization module
of the S-IC pneumatic console

MTO 1
MILA 1, 2 , 3
MA3

'0291

Revise engine cocoon thermal conditioning
controls and thermocouple cable acceptance
test requirements

MILA 1, 2 , 3,
MAB

i

106

MTF 1
MILA 1, 2, 3
MSE 1, 2
MAB

D5- 1260 1-5

�CHANGE NO.

E FFECTWITIES
STAGE
CSE

DESCRIPTION

0292

Provide backup engine pump seal purge systems

0293

LOX engine cutoff sensor solar cell redesign

0294 *

Add a mechanical relicf valve in the helium
bottle gas storage system

3,4

0295

Revise S-IC Level I electromagnetic
compatibility test requirements

7-15

0296

Add instrumentation provisions to the S-IC
pneumatic console forward umbilical service
unit and S-IC umbilicals

0297

Provide digital range safety command system
antenna shields

Q298

Add idet filter ta the fornard umbiliod service

C aneelled

MTF 1
NlfltA 1, 2, 8
PAAB

2-15

NIXLA lt2,3

uazlt
Provide sealing of stage structure to prevent
equipment damage from rain water

1-15

Provide redundant electrical power circuit
for fuel pi-essurization system

3-15

0301 *
Cancelled

Incorporation of second source LOX vent and
relief valve

6-15

0302

Replace 50M04050-1Hydraulic Research servoactuator with 60B84500-1 MOOG servoactuator

1

0299

0300

.

r

Modify the S-IC pneumatic console LOX/fuel
prepressurization modules

0305

Rework 60B84500-3 Hydraulic Research servoactuator

3-15

0306

Rework prefiltration valve subassembly on
MOOG servoactuator 60B84500-1

3-15

0309

Relocate the positive pressure line on the LOX
and fuel tank upper bulkheads

*

.

MfLA 1, 2, 3
MTO 1
MAB

0303

.

4-15

0310
C ancelied

Add umbilical interface measurements to
vehicle IP&amp;C list

1-15

0311

Provide redundant circuitry and power in the
stage separatidn system

3-15

MTF 1
MILA 1, 2, 3
MSE 1, 2

�EFFECTNITIES
CHANGE NO,
0312

DESCRIPTION

STAGE'

Provide separate mounting of three pilot relief
valve subassemblies in S-IC pneumatic consale

GSE

MTF 1
MILA 1 . 2 , 3

MAB

-

0313

Revise electrical surge suppression circuits in
the S-IC pneumatic console

MTF 2
MILA 1, 2, 3
MAB

0314

Add calibration valve to pressure switch
sensing line

MILA 1, 2 , 3

0316

Delete non-flight hardware from flight
documentation

2-15

0316

Rework the Hydraulic Research servoactuator 5011104050-1 removed from 8-IC-1 and
use them for S-IC -2

2

0317 *
Cancelled

Combustion chamber pressure measurement
telemetry channel change

5-15

0319

Add LOX pressure sensing line to the intertank

MILA 1, 2, 3

Provide redundant 28 VDC monitoring power
circuitry in the S-IC pneumatic console

MTF 1
MILA 1, 2, 3

MAB
0320

0321

Revise fairing turn buckle attachment fitting
material to 7075-T73

1-15

Provide Parker LOX vent and relief valve as

1

' standby for Whittaker LOX vent and relief valve

0322

Provide explosion proof enclosure for prevalve
ground accumulator pressure spheres

MTF 2
MILA 1, 2 , 3

Revise S-IC propellant dispersion system
installation
0324

Revise test requirements and procedures for
ordnance safe and arm device

2-15

0325

Provide a redundant method for initiating center
engine cutoff under LOX depletion condition

2-15

0320
Cancelled

Delete BMS8-38 sta-foam from S-IC electrical
distributors

3-15

0327

Modify the LOX vent and relief valve configuratiw by removing the actuator gear clutch springs

9d15

0

*

MTO 1
MILA 1, 2 , 3
MSE 1, 2

�CHANGE NO,
0328

DESCRXPTION

EFFECTIVITIES
STAGE
GSE
MILA 1, 2, 3

Rework the intertank umbilical locking
mechanism

-

Reroute cable installation on fins B and D

2 -3

0330

Substitute amplifier used for ten mandatory
prelaunch red line temperature measurements

3-15

0332

Rcvise the S-IC stage thrust structure hazardous
gas detection system to provide sampling orifice
in each quadrant

3-16

0333

Replace vibration transducers 60B72188-3 with
6OB72184-1 for 17 measurements in the engine
area

2 -5

0335

Remove, retest, and re-identify all 65B23280
check valves

0308

Reviae F-f engine cocoon temperature

0329

MSE 1, 2
MTF 1
lWLA 1, 2, 3

3-16

transducer
0337 *
Cancelled

Replace resistors on printed circuit of telemetry oscillator assembly

11-15

0338 *
Cancelled

Replace the RN 55C1253F resistor in the
50M65485-1 printed wiring assembly in the subc a r r i e r oscillator assembly

11-15

0339

Correct cabling installation design deficiencies
on S-IC stage

3

0344

Modify the fairing heat shield access panels

3-15

0345

Add weather protection covers to base a i r
scoops

0346

Redesign the LOX overfill sensor

0347

Eliminate 17-7 PH mechanical feedback springs
in Hydraulic Research S-IC servoactuator

3-15

0348

Eliminate single failure mode in outboard
engine cutoff measurements for time base T-3

3-15

0349

T r i m engine fairing skin to prevent injury to
personnel

0350

Provide attaching holes for hold down arms
hood closure lanyard

1

D5-1260 1-5

�DESCRIPTION

ClMMGE NO.

EFFECTIVITIE$
GSE

STAGE

Modify servoactuator jack pin assembly

6351

MSE 1, 2

MTF 1

MILA 1, a

0362 *
Cancelled

4

Provide special handling equipment at KSC

4-15

0353

Redesign of remote digital sub-multiplexer
power supply

3-15

0354

Revise material of stage antifriction plates

3-15

0355

Provide additional vents for the servoactuator
ancl Boeing suppBed engine thermal insulation

2-15

0356

Modify servoactuator boot fitting instauation to
replace fasteners with through bolts

3-15

0357

Change 5-IC documentation to comply with KSC
pull test requirements

2-3

6358

Provide positive moisture sealing of electrical
cavities for the 60B49002 helium pressnrization
and emergency dump valves

2-15

0359

Incorporate improved position switches in the
LOX tank vent and relief valve f 6OB51002f

2-15

0360

Installation of the ordnance bracket assembly
on the LOX and fuel tanks

2 -4

0362

Provide redundant electrical circuits to
eliminate single failure modes in the engine
cutoff system

3-15

0363

Protect electrical cables at entry (forward and
aft} to stage from electrical tunnel

2-15

0365

Revise S-IC pneumatic console documentation

MSE I, 2
MTO 1

MILA 1, 2, 3

MAB

110

KSC Geni

0367

Revise S-IC propellant dispersion system
installation kit

0368*
Cancel$&amp;

Delete brackets from LOX and fuel tanks

13-15

0369

Provide uninterrupted power (+28 VDC) to LOX
-and fuel loading electronics

3-15

0370

Redesign of GOX feeder duct (603[351403-1)

3-15

D5-12601-5

�EFFECTNITIES
STAGE
GSE
0371

hlodify S-IC intertank umbilical lock mechanism

MILA 1, 2, 3

0372

Modtfy the S-SC pneumatic cowole helium
primary 'egulation circuit

lMAB
MTF 1
MILA 1, 2, 3

0373 *
Cancelled

Requirements for structural load monitoring at

9374

Revise the main seal in the LOX fill and drain
valve

3-15

0375

Delete forward skirt umbilical door

4-15

0376

Reduce minimum pressure requirement for stage
helium bottles and delete the helium bottles high
pressure checkout switch

4-15

0377

Modify the S-IC storage racks to provide
protection during launch

MILA 1

0378

Provide additional fasteners for S-IC intertank
umbilical reconnect assembly control box covers

MILA 1, 2, 3

0379

Replace vent seals on all Airesearch prevalves
and emergency drain valves

5-15

0381 *
Cancelled

Provide "power off" turbopump seal purge
capability

3-15

0382

Eliminate He flow overlap of the stage and
ground fuel tank pressurization system

2-15

0389

Eliminate water acceptanoe testing for
Airesearch fuel prevalve 20PA32011-13

11-15

0385

Revise testing to prevent negative pressure in
the S-IC LOX tank

2-15

0386

Change spring material in Whittaker LOX
prevalves (2OM32010)and accomplish a modified requalification test

8-15

0387

Revise flight instrumentation to verify stage
performance and environment

3-15

0388

Redesign electrical disconnect bracket
(6OB67324-7)

3-5

0389 *
Cancelled

Modify filter manifold delta pressure transducer (Dl191 t
u
b
a

3-15

C

D5-12601-5

2-3

KSC

MTO 1
MILA 1, 2, 3
MAB

MSE 1, 2

MILA 1,2, 3

MTF 1

�CkiALANCE NO.

DESCRIPTION
Provide backup LOX bubbling system in the
S-IC pneumatic console

0390

0392

EFFECTNM'IES
STAGE
GSE

'

MTO 1
MAB
MILA 1, 2, 3

Delete the S-IC base air scoop
Provide a manual means to fill the stage
hefirun bottles

0394

MAB

MTQ 1
MXLA 1, 2, 3

Change O-rings in 65B23278 solenoid valves

MSE 1, 2
MTF 1
MILA 1, 2, 3

0396 *
Cancelled

Block debris valves in S-IC intertank-reconnect
assembly LOX fill and drain lines in the open
position

0397 *
Cancelled

Change the material on the 60B41044 LOX fill
and drain elbows

6015

0398

Provide for control of fuel and LOX loading
electronics calibration commands from
propellant tanking computer system

3-15

0399

Modlfy installation of acoustic vibration
measurements utilizing 60B67632-XXX coaxial
cable assembly

0400

Modi$ S-IC intertank umbilical reconnect
assembly to include a backup retract capability

MILA 1

MSE 1, 2
MTO 1

C

0401

112

Provide locking and position indicating
mechanism for S-IC pneumatic oonsole and
forward umbilical service unit manual ball
valves

MTF 1
MILA 1, 2, 3

MAB

0405

Modify the umbilical coupling for the oxidizer
suction line bubbling system

0406

Modify TV objective lens housing assembly

0407 *
Cancelled

Readjust outboard LOX and fuel depletion
system timers

2

0409

Provide hardwire engine actuator position
interlock for engine cutoff

3-15

MSE 1, 2
MTO 1

0410

Modify engine cutoff circuitry to reduce
potentiaI of premature shutdown

3-l6

MSE 1, 2
MTO 1

3-15

MSE 1, 2
MTF 1
MILA 1, 2, 3

D5-1260 1-5

�I

-*.

CHANGE NO.

'

'

,

DESCRIPTfON

EPFECWITIEs
BTAGE:
08E

0411 *

Y rovide drain for servoactuator rod seal

C ancelled

leakage

0$12

Replace Southwestern Industries gage and absolute pressure switches with Consolidated Controls
pressure switchers

3-15

0414 *
cmcsw

Replace bolts in fairing heat shield access panel

3-15

0415

Replace 5OM 04049 MOOG servoactuator with
60B84500 MOOG servoactaator

2

0419

Provide new htch on the S-IC intertank
umbilical reconnect assembly

0421

Solder RF coaxial shield braid to connect
shield clamp

3-8

0423

Y isual identification for S-IC stage ordnance

3-15

_

2-15

M
I
U 1, 2,'3
AiLAB

IVIIfLA 1, 2$ 8

systems

I

0425 *
C mcelted

Modify fuel tank vertical internal access
equipment

0426

Identification of equipment containers to
twit 120

4-15

0428 *

Propellant depletion system timer setting for
S-IC-3 (B/P 30)

3

0429 *

Add instrumentation for analysis of vehicle
release condition

3

0430

Change frequency of telemetry links

6-15

0432

Modify LOX and fuel prepressurization syshms

0437

Lockwire threaded connectors which do Ifid
have drilled holes for lockwiring

3-15

0441

Provide additional protection for components
vulnerable to damage from the S-E/S-XI
separation environment

3-15

0442

install helium injection POGO suppression
systems

3-15

0444

Increase Ecmvard umbilical servioe unit flow
cmilitg

.

G ancelled

,

D5-U60 1-5

I

KSC Genl

MSE 1, 2
MTO 1

MILA 1, 2, 3
MTO 1
MAD

MSE 1, 2
MTO 1

MU 1
113

�CHANGE NO.

DESCRfPTfON

EFFECTNPTBS

STAGE

0848 El

Replace pressure gage in forward umbilical.
service unit

O866Rl

Modify heater blanket assemblies

1-3

0867 R1

Modify base heat shield installation

1-15

W68 Rl

Modify connector hex tlut

3-45

0869 R1

Eliminate interfe~enceon base air scoop
measurement installation

1-5

0870 Rl

Modify base heat shield support angle
installation

1-4

0871 R1

Correct bolt lengths on lower fairings

3115

0873 R1

Modify support installation to allow installation
of the recoverabie camera

2, 3

0874 R1

Correct bolt length on thrust structure base
air scoop installation

1-15

0875 R1

Provide pilot relay for heater power contactor
in S-IC pneumatic console

0876 RI

Modify ground cable in TV camera system

2,

0875 R1

Mod*

1-15

0879 R1

Modify tube assembly in the pneumatic console

0880 R1

Eliminate an out-of-tolerance condition in the
LOX leakmeter measurement F45-118

0883 R1

Correct bolt length callout on servoactuator
boot installation

1-15

0884 R1

Modify length of cable assembly 115W305

1-5

0885 R1

LOX fill and drain valves (B-239,B240) control
valves reversed cables

retrorocket initiation system

GSE

LUT #I, 82, #3

MILA 1, 2, 3
MTF 1
3

MILA 1, 2, 3
MAB

MTF 1

114

0887 Rl

Calorimeter purge line clamp

0889 R1

Modify S-IC intedank umbilical to delay
closure of debris valve

0890 R1

LOX arrd fuel loading electronics unit calibrai
tion cablee

2 -5

MILA
1,2

D5-12601-6

�CHANGE NO,

.

a

.

E FFECTrVRTElS
STAGE
GSE

DESCRIPTION

0891 R l

Heat shield panel installation

2,3

bBQ2R1

Electrical installation forward skirt

293

0893 R l

Eliminate leakage in LOX pressure sensing line

MILA 1, 2, 3

0896 R l

Housing Assembly aft 1 and 2

MfLA 1, 2, 3

0887 RZ

Rebonding of antifriction plat;ee

2

0900 R1

Fuel delivery system installation fuel tank

1-15

0902 R1

Cable and instrument installation thrust
chamber tmit 105

2-5

0903Rl

Engine fairing blanket assembly

2-15

0904 R1

Cable and instrumentation installation
units 101 and 102

0906 R1

Measurement installation fin B

2, 3

0907 R1

Propellant dispersion system installation and
retrorocket initiation system

2-15

0908 R1

Change bolt callout

2-15

0913 R l

Base heat shield bracket misalignment

3-15

0914 R1

Rework fuel ordnance cowling and revise
ordnance installation requirements

2 -15

0916 ~i

Rework thrust chamber insdation

2-5

0918 R1

Revise fin and fairing nut callouts

3-15

0920 R1

Replace insulation bracket covers

2-9

0929 R1

Disconnect position switch cables on vent and
relief valves

2

1214 G

Increase accuracy of GOX flow control valve
pilot pressure measurement

MSE 1, 2

1219 G

Revision to stage handling equipment (MAB VAB)

MAB

1221 G

Utilize RCA llOA as primary engine test
programmer

MTF

1224 S

Correct errors on LOX anti-vortex
documenwon

D54f2601-5

-

2-4

10-15

115

�CHANCE BO,

DESCRDPTION

EFFECTIVITIES
STAGE
GSE

1225 S

Replace roller cams oh LOX interconnect
support bracket installation

1226 G

Modify MTF rotational brace

MTF 1

1227 C

Modify the MTF hydraulic terminal equipment

MTF 1

1232 0

Modify pin puller assemblies a d adjustment

MTF 1

4-15

l i n a p s assembly at MTF

1233 G

Modify the area contamination detection system

1235 S

Provide self-aligning capability for engine
fairing turnbucMes

5-15

1236 S

Redesign rate gyro heater blanket assembly

10-15

1237 S

Relocate engine actuator electrical filter
assembly

5-15

1238 S

Revise S-IC servoactuator thermal insulation
documentation

10-15

1239 S

Revise 60B19612-1 static firing antifriction
plates to facilitate removal

6-15

1240 G

Provide capability for remote pressurization
a d venting of the COX ducting system

1243 G

Modify aluminum forward handling ring test
requirements

7-15

Provide new presampling filter and modified
power supply cards

-15

Eliminate solder joints susceptible to cracks
in electrical distributors

10-15

1244 S +
Cancelled
1245 S

MSE 1, 2

MTO 1

t.

��APPENDIX G

-

SYSTEMS TEST M T O
DOCUMENT STATUS REPORT

DOCUMENT NO,
5-10016-1
f)fi*11789-005

DOCUMENT TITLE

STATUS

BMTOEMERGENCYCONTROLPUM

IN WORK

BTACE BEQUENCE/QBERATI[QNE Pub3 FOR

COMPLETED

SATURN S-IC -5
D5-11789-008

STAGE SEQUENCE/OPERATIONS PLAN FOR
SATURN S-fC -6

COMPLETED

05-11789-100

STAGE SEQUENCE/OPERATIONS PLAN FOR
SATURN S-IC -- PROCEDURES AND INSTRUCTIONS FOR PROCESSING STAGES AT MTF

COMPLETED

D5-13034

S-IC S P E C U L TESTS

COMPLETED

D5-13034-3

LOX EMERGENCY DUMP LINE TEST

CANCELLED

D5-13034-38

S-IC BOOSTER STORAGE BUILDING FLOOR
SETTLEMENT TEST

COMPLETED

D5-13034-39

POST EMERGENCY DRAIN LINE COLLAPSE,
SPECIAL RP-1 TRANSFER TESTS

IN WORK

D5-13034-40

FUEL TANK DRAIN TESTS S-IC -D

IN WORK

D5-13034-41

TEST OF S-IC STATIC TEST STAND
VENTILATION

IN WORK

D5-13034-42

RCA/IlOA BECKMAN COMPUTER PROGRAM
DEVELOPMENT

COMPLETED

D5-13034-43

TEST OF HOLDDOWN ARM ANTI-FRICTION
PLATE

IN WORK

D5-13034-45

ENVIRONMENTAL TEST, S-IC EAST
OBSERVATION BUNKER

IN WORK

D5-13034-46

IN-PLACE GN2 ONE-HALF INCH BY-PASS
LINE TEST

INWORK

D5-1304'747

HELIUM FLOW CONTROL VALVE FLOW
RESPONSE TEST

IN WORK

5

/

D5-13034-48

118

SIMULATED ON2 ONE-HALF INCH BY-PASS
LINE TEST

W WORK

D5-1260 1-5

�DOCUMENT NO.

DOCUMENT TITLE

STATUS

- MTF

D5-13743

FACILITIES MAINTENANCE PLAN

D5-13781

FACILITIES mINTENANCE RECORD
SYSTEM

CANCELLED

CONTAMINATION CONTROL OF S-IC

IN WORK

D5-13970

SYSTEMS AT MTF

CANCELLED

�GLOSSARY

CRT

Cathode ray tube

AS

Apollolsaturn

CSA

Computer Sciences Applications

MTC

Bwing A t

CSM

Central Stores Michoud

BEAR

Boeing Investigation and Corrective Action
Request

CY

Calendar year

DAF

Data Acquisition Facility

DDAS

Digital data acquisition system

DEE

Digital even&amp; evaluator

-

Test Center, ICSC , Florida

CAM

Change action memo

CAR

Corrective action request

CCB

Configuration Control Board

CCP

Contract change proposal

CDDT

Countdown Demonstration Test

CDF

Confined detonating: fuse

CDR

Critical design review

CEI

Contract end item

CID

Cable Interconnect diagram

C U S S I CHANGE:
If an engineering change deviates from the
contract and must, therefore, be covered by
contract revision, it is Class I. All Class I
changes are processed by Engineering Change
Proposal. Class I changes are specifically
identified as such if one or more of the following is affected: (I) Part I CEI Specifications;
(2) Contract price o r fee and contract guarantees, delivery, or test schedules; (3) Changes
to Part lI CEI Specifications if any or the
following are affected interchangeability,
electrical interference, present adjustments,
interfaces, computer programs, change in
vendors, retrofit, requalification testing, and
any change affecting high energy nuclear
radiation sources.

-

CLASS If CHANGE:
All changes that are not Class I.
C/O

Checkout

CPFF

Cost plus fixed fee f contract)

CPZF

Cost plus &amp;cenW@fee (contrwt)

120

Discrete iddiscrete out
DRD

Docutnent requirements description

DRL

Document requirements list

DTS

Data transmission system

EAMR

Engineering Advance Material Releases

EAPL

Engineering assembly parts list

ECM

Engineering change memorandum

ECP

Engineering change proposal

ECPR

Engineering change proposal requirements

E CS

Environmental control system

EDS

Emergency detection system

E/E

Electrical/electronic

EITP

End item test plan

EMC

Electromagnetic compatibility

EM0

Equipment management organization

EMPL

Engineering master parts list

EO

Engineering order

EPRR

Engineering parts release record

EQA

Equipment quality analysis

ERS

Experience retention study, also
Equipment record system

FACX

First article configuration inspection
D5- 12601-5

�FISC

Flexible line~wshaped charge

LSBRS

Launch Systems Branch records system

FM

Frequency modulated (modulation)

LUT

Launch Umbilical Tower

FY

Fiscal year

MAB

Mechanical automation breadboard

GETS

Ground Gquipment Test Set

MAF

Michoud Assembly Facility

GFE

Government furnished equipment

MAR

Maintenance Action Revision

GFP

Govelmment furnished property

MB

NASA/MSFC-Boeing (jointly issued
specification, drawing, o r part number) .

GN2

Gaseous nitrogen

COX

Gaseous oxygen

gPm

Gallons per minute

GSE

Ground support equipment

HLS

Hydraulic load simulator (NLAB)

HPA

High pressure air

HPG

High pressure gas

HPIW

High pressure industrial water

HPSU

Hydraulic power supply unit

ICD

Interface control documentation

ICE

Instrument calibration equipment

IDEP

Interservice Data Exchange Program

MBR

.

MSFC/Boeing relay (last letter
represents type of part)

MCMRP Minimum configuration management
requirements plan
MCL

Measurement control laboratory

MDS

Malfunction detection system
Manufacturing engineering

MF

Medium Frequency

Michoud Michoud Assembly Facility, New Orleans,
Louisiana
MIG

Mechanical inert gas (welding process)

MRB

M m r i e l Review Board

MSC

Manned Spaceflight Center, Houston,
Texas

MSE

Manufacturer's support equipment
(GSE to support manufacturing facility)

MSE I

Manufacturer's support equipment
this test complex used for PSC and
refurbishment of stages.

MSE 11

Manufacturer's support equipment
this test complex used for PMC of
stages.

MSFC

Marshall Space Flight Center, Huntsville,
Alabama

3

IRN

Interface Revision Notice

ITGE

Integrated telemetry grouud equipment

JOD

Joint occupancy date

KSC

Kennedy Space Center, Florida

KSI

Kips per square inch

KVA

Kilovolt ampere

-

=I2

Liquid hydrogen

LN

Liquid nitrogen

MTF

Mississippi Test Facility, Mississippi

LOX

Liquid oxygen

MTO

LSB

Launch Systems Branch

Mississippi Test Operations (Boeing
Systems Test organization responsible
for MTF activities)

121

�:,- 1
i'9i

A
'

,

0

:

National Aeronautics and Space
Administration

HC

Numerical Control

NBT

Nondeshzlctive Test

N/N

Next IIiyher Part Number

HME

NitrogeRnlelium

NPSII

Not positive suction head

OAT

Overall test (procedure)

0bE3

On-Line data input system

OWP

Offset Doppler system

PAM

Pulse amplitude modulated

PAR

Part analysis report

PART f

CEI specifications set forth "detail
design and performance requirements"
for S-IC-F, S-IC-1 through S-IC-10,
and all deliverable GSE at KSC

QC

Quality control

QMT

Quality Maintenance Test

R&amp;D

Research and development

RACS

Remote automatic calibration system

RAM

Reliability Analysis Model

RDC

Reliability Data Center

RMM

Remote Digital Sub-Mult;lplexer

RF

Radio frequency

RFP

Request for proposal

RP-I

Fuel (kerosene)

I

I?

f
C

NASA

'
h

h*

R-QUAL Quality Laboratory, MSFC

-

.

-

PART Ef CEI specifications set forth "drawings
and test requirements" for S-IC-3 on
(does not affect S-IC-F , S-IC-1, S-IC-2,
o r deliverable GSE)

R-TEST

Test Laboratory, MSFC

SA

Supplemental Agreement

SCN

Specification Change Notice

SDC

Status Display Center

SE

Support Equipment

ST-MTF Systems test
PCA

Production control area

PCC

Program control center

PCM

Pulse code modulated

PD

Program Directive

PERT

Program evaluation and review technique

PMC

Post-manufacturing checkout

p/N

Part Number

PRR

Production revision record
(a claas IT change)

PSC
Q&amp;RA

- MTF

TCC

Test control center

TIG

Tungsten inert gas (welding process)

T/M

Telemetry

TVC

Thrust Vector Control

UCR

Unsatisfactory Condition Report

UER

Unplanned event record

VAB

Vertical Assembly Building

VISTA

Visual Task Analysis

Post-static checkout

WAC

Work Authorization Change

Quality and Reliabiliw Assurance

AP

Delta p , differential pressure

C

122

D5-1260 1-5

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20212">
                <text>spc_stnv_000066</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20213">
                <text>"Saturn V First Stage Annual Progress Report: Fiscal Year 1968."</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="20214">
                <text>D5-12601-5</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20215">
                <text>The report covers June 30, 1967 through June 27, 1968: Contract NAS8-5608, Schedules 1 and 1A, July 27, 1968. Prepared by J. P. Delaloye, Management Reporting and Analysis; Supervised by D. G. Valentine, Management Reporting and Analysis;  Approved by R. F. Terry, Program Reports; D. H. Creim, Michoud,  Program Planning and Reporting Manager; E. K. Cooper, S-IC Program Executive.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20216">
                <text>Delaloye, J. P.</text>
              </elementText>
              <elementText elementTextId="20217">
                <text>Boeing Aerospace Company. Space Division. Launch Systems Branch</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="20218">
                <text>1968-07-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20219">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20220">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20221">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="20222">
                <text>Saturn S-1C stage</text>
              </elementText>
              <elementText elementTextId="20223">
                <text>Project management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20224">
                <text>Annual reports</text>
              </elementText>
              <elementText elementTextId="20225">
                <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="20226">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20227">
                <text>Box 27, Folder 33</text>
              </elementText>
              <elementText elementTextId="205817">
                <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="20229">
                <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="20230">
                <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="20231">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
