| Branch | U.S. Air Force |
| Series | AFI |
| Publication date | 2018-09-12 (8.0 years ago) |
| Status | Current |
| Proponent / OPR | AF/SG |
| Source of record | AF e-Publishing |
Download PDF Official document (AF e-Publishing)
This instruction establishes the USAF Respiratory Protection Program that implements and incorporates guidance and criteria from 29 CFR 1910.134 available at: https://www.osha.gov/pls/oshaweb/owadisp.show_document?p_t able=standards&p_id=127
This instruction primarily applies to the use of respiratory protective devices during the execution of operations in industrial worksites. With the exception of more stringent requirements in this instruction, the Respirat ory Protection Program shall adhere to the requirements stated in the most current version of 29 CFR 1910.134.
This document has been substantially revised and must be completely reviewed. Significant changes include removing of duplication with 29 CFR 1910.134, alignment of verbiage to match 29 CFR 1910.134, clarification on military unique respirators, and refinement of tiering
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 |
|---|---|---|
| Safety | 2 | DAFMAN 91-203, AFI 91-202 ANG Sup |
| Health Services | 1 | AFI 41-106 AFGSC Sup |
| Maintenance | 1 | AFI 21-101 ACC Sup |
| Operations | 1 | AFI 10-403 |
| Security Forces | 1 | AFI 31-118 |
| Services | 1 | DAFI 34-101 |
7 publications in 6 other communities depend on this one, which Aerospace Medicine 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 48-137 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.