AFPD10-9 Publication Summary:
Purpose:
The Air Force employs many diverse weapons and support systems in executing its global mission. Oper-ating,
maintaining, and modifying these systems to upgrade or extend economical service life greatly con-sumes
the Air Force’s budget. Ultimately, the Air Force must develop, purchase, and field new systems to
replace systems economically obsolete or beyond economical repair. The Air Force assigns responsibility
for overall management of each system to a "lead command" to ensure that all requirements associated
with every system receive comprehensive and equitable consideration This lead command provides a pri-mary
input into the process of developing and maintaining a force structure with a balance of complemen-tary
capabilities, and it establishes a basis for rational allocation of scarce resources among competing
requirements. The identity of the lead command is obvious when only one command has the system
assigned to it. However, when active Air Force Major Commands (MAJCOM) "share" a system among
themselves or with units of the Air Reserve Components (ARC), the Air Force clearly designates a lead
command so that all using and supporting organizations know who is the overall advocate for that system
over its life cycle.
Summary of Changes:
This revision incorporates interim change (IC) 2000-1 and changes lead command responsibilities for the
EC-130E/J COMMANDO SOLO variant to AFSOC from ACC and assigns to ACC lead command
responsibilities for the RQ-1. IC 2000-1 also clarifies the reference to AFPD 11-2 and the term "GEN"
used in Figure A2.1., and makes administrative changes to Attachment 2 to reflect actual using com-mands
and office of responsibility. The entire text of IC 2000-1 is at Attachment 4. Changed or revised
material is indicated by a bar (|).
Distribution:
Supersedes:
AFPD 10-9, 23 February 1998.
History:
AFPD 10-9, 23 February 1998; AFPD 10-9, 31 January 1997.