| Branch | U.S. Air Force |
| Series | DAFPD |
| Publication date | 2021-05-25 (5.3 years ago) |
| Status | Current |
| Proponent / OPR | AF/A8 |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This publication establishes a basis for designating a lead command or lead agent when one or more organizations possesses or is responsible for a portion of a United States Air Force weapon system, non-weapon system, or activity. A lead command or lead agent is an organization designated by the Secretary of the Air Force or delegated representative to provide input and advocacy for developing and maintaining assigned systems and activities under the oversight of Headquarters Air Force (HAF).
This document has been substantially revised. Previous versions of this publication were limited to lead command designations and responsibilities for weapon systems/activities. This publication has been updated to add designations and definitions for non-weapon systems and activities. The “system” refers to both weapon systems and non-weapon systems
Publications state their own changes on page 1 — behind a PDF the official host will not serve to a search engine. This is that section, verbatim. It describes the edition above, not every historical change.
| Functional community | Publications | Which ones |
|---|---|---|
| Acquisition | 3 | AFPAM 63-129, DAFI 63-101 20-101, AFMAN 63-143 |
| Flying Operations | 2 | AFI 11-200, DAFMAN 11-402 |
| Personnel | 2 | DAFMAN 36-2806, DAFMAN 36-2806 ACC Sup |
| Inspections & Special Management | 1 | DAFMAN 90-161 OSANAB Sup |
| Materiel Management | 1 | DAFMAN 23-300 ACC Sup |
9 publications in 5 other communities depend on this one, which Operations owns. Each community inspects its own publications; a dependency that crosses communities is owned by nobody, which is why this list normally does not exist anywhere. Built from the publications' own citations, so it reflects what we have read.
If DAFPD 10-9 changes, these are the documents that point at it. Extracted from the publications' own text, so it reflects what we have read, not a complete dependency map. Every publishing office validates its own document; nobody validates the seams between them.