<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="P0b002ee1803a09a7">
<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>
 <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">2002-04-30</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
</physicalDescription>
<classification authority="sudocs">GA 1.13:GAO-02-542</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-GAO-02-542</identifier>
<identifier type="local">P0b002ee1803a09a7</identifier>
<identifier type="former package identifier">f:d02542</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-GAO-02-542</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-GAO-02-542</accessId>
 <reportNumber>GAO-02-542</reportNumber>
 <subject>Air Force personnel</subject>
 <subject>Defense contingency planning</subject>
 <subject>Fighter aircraft</subject>
 <subject>Personnel management</subject>
 <subject>Strategic planning</subject>
 <subject>Internal controls</subject>
 <subject>Air Force Expeditionary Aerospace Force</subject>
 <subject>Concept</subject>
 <type>Other Written Product</type>
 <accountNo>A02927</accountNo>
 <USCode title="31">
                      <section number="720"></section>
                </USCode>
</extension>
<titleInfo>
 <title>Defense Plans: Plan to Better Use Air Force Squadrons Could Yield Benefits but Faces Significant Challenges</title>
</titleInfo>
<abstract>Defense Plans: Plan to Better Use Air Force Squadrons Could Yield
Benefits but Faces Significant Challenges (30-APR-02,		 
GAO-02-542).							 
                                                                 
To reduce the deployment burden on Air Force personnel by	 
spreading deployments more evenly across its force and increasing
the predictability of deployments, the Air Force implemented its 
Expeditionary Aerospace Force concept in 1999. By dual-tasking	 
some fighter squadrons the Air Force could  fulfill two 	 
requirements as the 2010 Concept envisions. Although significant 
challenges could impede the ability to maximize these benefits,  
the Air Force has not specifically analyzed what is needed to	 
implement dual-tasking by 2010. Dual-tasking would result in more
efficient use of squadrons and a greatly reduced need to task	 
squadrons above and beyond the Air Force&apos;s goal of one 90-day	 
deployment every 15 months. Dual-tasking would provide theater	 
commanders with the same number of aircraft to meet requirements 
as under current practice; however, the aircraft would come from 
fewer squadrons. Because a larger proportion of a squadron&apos;s	 
aircraft would be used to meet requirements, and because	 
dual-tasking uses fewer squadrons to meet requirements, the need 
to repeatedly task the same squadrons would be reduced. The	 
number of squadrons needed for more than one 90-day period over a
15-month period would decline from 26 squadrons to five. More	 
training would be required under dual-tasking. Yet, the Air Force
has not quantified this increase, assessed how it would manage	 
the increase, nor projected how it would support such an increase
either logistically or in its budget. To support deploying a	 
greater portion of dual-tasked squadron&apos;s aircraft, more of the  
authorized maintenance positions would have to be filled.	 
Currently, more than half of the maintenance specialties at the  
wings GAO analyzed were undermanned, and some were manned at less
than 60 percent. Such shortages already pose difficulties, since 
wing officials are limited in what they can do to make up for the
shortages. Dual-tasking could cause maintenance personnel to be  
deployed more frequently than desired unless more of these vacant
positions are filled. In addition, almost all of a squadron&apos;s	 
pilots would be needed to meet dual-tasking requirements. This	 
will pose challenges in managing pilot deployments.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-02-542/html/GAOREPORTS-GAO-02-542.htm</url>
</location>
<identifier type="preferred citation">GAO-02-542</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-GAO-02-542</url>
</location>
<note>Other Written Product</note>
<extension>
 <searchTitle>GAO-02-542; Defense Plans: Plan to Better Use Air Force Squadrons Could Yield Benefits but Faces Significant Challenges;
            </searchTitle>
</extension>
<subject>
 <topic>Air Force personnel</topic>
 <topic>Defense contingency planning</topic>
 <topic>Fighter aircraft</topic>
 <topic>Personnel management</topic>
 <topic>Strategic planning</topic>
 <topic>Internal controls</topic>
 <topic>Air Force Expeditionary Aerospace Force</topic>
 <topic>Concept</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Code</title>
  <partNumber>Title 31 Section 720</partNumber>
</titleInfo>
 <identifier type="USC citation">31 U.S.C. 720</identifier>
</relatedItem>
</mods>