<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="P0b002ee18037f017">
<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>Accounting and Information Management 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-02-04</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>12 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:T-AIMD-98-63</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-98-63</identifier>
<identifier type="local">P0b002ee18037f017</identifier>
<identifier type="former package identifier">f:ai98063t</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-24</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-T-AIMD-98-63</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-T-AIMD-98-63</accessId>
 <reportNumber>T-AIMD-98-63</reportNumber>
 <subject>Systems conversions</subject>
 <subject>Computer software</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Data integrity</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Air traffic control systems</subject>
 <subject>Information resources management</subject>
 <subject>Systems compatibility</subject>
 <identifier>FAA Year 2000 Program</identifier>
 <type>Testimony</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Year 2000 Computing Crisis: FAA Must Act Quickly to Prevent Systems Failures</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO discussed the Federal Aviation
Administration&apos;s (FAA) efforts to address the year 2000 problem,
focusing on: (1) FAA&apos;s reliance on information processing; (2) where the
agency stands today; (3) what remains at risk; and (4) what GAO
recommends must be done to increase the likelihood that FAA systems will
be year 2000 compliant by January 1 of that year.&lt;p/&gt;GAO noted that: (1) many of FAA&apos;s systems could fail to perform as
needed when using dates after 1999, unless proper date-related
calculations can be assured; (2) the implications of FAA&apos;s not meeting
this immovable deadline are enormous and could effect hundreds of
thousands of people through customer inconvenience, increased airline
costs, grounded or delayed flights, or degraded levels of safety; (3)
FAA&apos;s progress in making its systems ready for the year 2000 has been
too slow; (4) at its current pace, it will not make it in time; (5) the
agency has been severely behind schedule in completing basic awareness
activities, including establishing a program manager with responsibility
or its year 2000 program and issuing a final, overall year 2000
strategy; (6) further, FAA does not know the extent of its year 2000
problem because it has not completed key assessment activities; (7)
specifically, it has yet to analyze the impact of its systems&apos; not being
year 2000 compliant, inventory and assess all of its systems for date
dependencies, make final its plans for addressing any identified date
dependencies, or develop plans for continued operations in case systems
are not corrected in time; (8) until these activities are completed, FAA
cannot know the extent to which it can trust its systems to operate
safely using dates beyond 1999; (9) delays in completing awareness and
assessment activities also leave FAA little time for critical
renovation, validation, and implementation activities--the final three
phases in an effective year 2000 program; and (10) with under 2 years
left, FAA is quickly running out of time, making contingency planning
even more critical.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-98-63/html/GAOREPORTS-T-AIMD-98-63.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-T-AIMD-98-63/pdf/GAOREPORTS-T-AIMD-98-63.pdf</url>
</location>
<identifier type="preferred citation">GAO/T-AIMD-98-63</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-T-AIMD-98-63</url>
</location>
<note>Testimony</note>
<extension>
 <searchTitle>GAO/T-AIMD-98-63; Year 2000 Computing Crisis: FAA Must Act Quickly to Prevent Systems Failures;
            </searchTitle>
</extension>
<subject>
 <topic>Systems conversions</topic>
 <topic>Computer software</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Data integrity</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Air traffic control systems</topic>
 <topic>Information resources management</topic>
 <topic>Systems compatibility</topic>
 <topic>FAA Year 2000 Program</topic>
</subject>
</mods>