<mods xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" ID="P0b002ee1803915b2">
<name type="corporate">
 <namePart>United States Government Publishing Office</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">publisher</roleTerm>
  <roleTerm authority="marcrelator" type="code">pbl</roleTerm>
</role>
 <role>
  <roleTerm authority="marcrelator" type="text">distributor</roleTerm>
  <roleTerm authority="marcrelator" type="code">dst</roleTerm>
</role>
</name>
<name type="corporate">
 <namePart>United States</namePart>
 <namePart>Government Accountability Office</namePart>
 <namePart>National Security and International Affairs Division</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">author</roleTerm>
  <roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
 <description>Government Organization</description>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">government publication</genre>
<language>
 <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<extension>
 <collectionCode>GAOREPORTS</collectionCode>
 <category>Legislative Agency Publications</category>
 <waisDatabaseName>gao</waisDatabaseName>
 <branch>legislative</branch>
 <dateIngested>2010-08-12</dateIngested>
</extension>
<originInfo>
 <publisher>U.S. Government Printing Office</publisher>
 <dateIssued encoding="w3cdtf">1998-11-10</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>29 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:NSIAD-99-2</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-NSIAD-99-2</identifier>
<identifier type="local">P0b002ee1803915b2</identifier>
<identifier type="former package identifier">f:ns99002</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-23</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-NSIAD-99-2</recordIdentifier>
 <recordOrigin>machine generated</recordOrigin>
 <languageOfCataloging>
  <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</languageOfCataloging>
</recordInfo>
<accessCondition type="GPO scope determination">fdlp</accessCondition>
<extension>
 <docClass>REPORT</docClass>
 <accessId>GAOREPORTS-NSIAD-99-2</accessId>
 <reportNumber>NSIAD-99-2</reportNumber>
 <subject>Communication satellites</subject>
 <subject>Military satellites</subject>
 <subject>ADP procurement</subject>
 <subject>Navigation aids</subject>
 <subject>Operational testing</subject>
 <subject>Ballistic missiles</subject>
 <subject>Military communication</subject>
 <subject>Defense capabilities</subject>
 <subject>Confidential communication</subject>
 <subject>National defense operations</subject>
 <identifier>MILSTAR</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>NSIAD</seriesAbbrev>
 <congReport congress="105" number="591" type="H"></congReport>
</extension>
<titleInfo>
 <title>Military Satellite Communications: Concerns With Milstar&apos;s Support to Strategic and Tactical Forces</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed the Department of
Defense&apos;s (DOD) multiservice Milstar system, focusing on the: (1)
Milstar system&apos;s capabilities to support strategic and tactical
missions; and (2) extent to which DOD has provided assurance of
continuing comparable satellite communications among the users after the
Milstar satellites under development are launched.&lt;p/&gt;GAO noted that: (1) there are several limitations associated with the
Milstar system&apos;s capabilities to support strategic missions; (2)
although the Milstar I system has been deployed for over 2 years, a May
1998 draft operational test report revealed that system support could be
limited in some critical strategic mission areas; (3) operational
testing showed that military commanders could not communicate by voice
in a timely and intelligible manner, when using the low data rate
capabilities; (4) this limitation was attributable to inherent
characteristics of Milstar&apos;s low data rate technology and associated
peripheral equipment; (5) operational testing of the missile warning
teletype network was planned, but not performed, to verify that accurate
and timely ballistic missile alert messages could be transmitted from
North American Aerospace Defense Command to other strategic command
centers; (6) a subsequent Air Force test of this teletype network
determined that a required redundancy check for data accuracy could not
be performed without software modifications; (7) operational testing
revealed a Milstar system endurance issue, associated with the nuclear
bomber force, that must be resolved because of the requirement for
continuous communication capabilities if the bomber force needed to be
recalled or redirected; (8) testing showed that the configuration of
peripheral equipment and its accompanying software has not been
effectively controlled or fully certified to ensure communications
interoperability with the Milstar system; (9) DOD has identified
corrective actions for the limitations in these four areas; (10) final
resolutions are dependent on approval of requirements, verification
through testing, a certification process, or obtaining necessary funds;
(11) DOD has not provided assurance that the continuity of protected
medium data rate satellite communication capabilities will be maintained
for tactical forces after the four Milstar II satellites are launched;
(12) the satellite constellation&apos;s communication capabilities are
predicted to degrade below a minimally acceptable level in fiscal year
(FY) 2003, before the advanced satellite system is expected to be
available in FY 2006; (13) the deployment of Milstar II tactical
terminals is expected to be completed by 2003, and tactical forces will
have become dependent on the Milstar II system; (14) this situation
could result in users not having the communications capacity they
require to execute their missions; and (15) DOD has not fully assessed
the associated operational risks to tactical forces.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-NSIAD-99-2/html/GAOREPORTS-NSIAD-99-2.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-NSIAD-99-2/pdf/GAOREPORTS-NSIAD-99-2.pdf</url>
</location>
<identifier type="preferred citation">GAO/NSIAD-99-2</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-NSIAD-99-2</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/NSIAD-99-2; Military Satellite Communications: Concerns With Milstar&apos;s Support to Strategic and Tactical Forces;
            </searchTitle>
</extension>
<subject>
 <topic>Communication satellites</topic>
 <topic>Military satellites</topic>
 <topic>ADP procurement</topic>
 <topic>Navigation aids</topic>
 <topic>Operational testing</topic>
 <topic>Ballistic missiles</topic>
 <topic>Military communication</topic>
 <topic>Defense capabilities</topic>
 <topic>Confidential communication</topic>
 <topic>National defense operations</topic>
 <topic>MILSTAR</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States House Report 591 (105th Congress)</title>
</titleInfo>
 <identifier type="congressional report citation">H. Rept. 105-591</identifier>
</relatedItem>
</mods>