| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2023-05-23 (3.3 years ago) |
| Status | Current |
| Proponent / OPR | AF/SE |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This instruction codifies the process whereby the Air Force (AF) implements DoDM 3150.02. The Air Force ensures adherence to safety standards by:
This document is substantially revised to comply with Department of Defense Manual (DoDM) 3150.02, DoD Nuclear Weapon System Safety Program Manual. This revision incorporates and supersedes AF I91-102_AFGM2020-01-Nuclear Weapon System Safety Studies, Operational Safety Reviews and Safety Rules, 28 August 2020, includes adding the purpose, timing, scope, distribution, and publication for safety studies. Clarification of Independent Technical Analysis Agency is more clearly defined. Handling of Air Force position when study results differ from the Nuclear Weapon System Surety Group (NWSSG) majority or minority position report and what is required within the Air Force Nuclear Weapons System Surety Report (AF NWSSR) along with processing of minority opinions associated with the AF NWSSR. Clarification of the meaning for voting within the NWSSG process was added. Administrative changes were made throughout
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 | 1 | AFPAM 63-129 |
1 publication in 1 other community depend on this one, which Safety 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 AFI 91-102 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.