Q A 20 AFI21-103.pdf

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE INSTRUCTION 21-103

9 APRIL 2010

Maintenance

EQUIPMENT INVENTORY, STATUS AND

UTILIZATION REPORTING

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: This instruction is available for downloading from the e-Publishing website at www.e-publishing.af.mil.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: AF/A4LM

Supersedes: AFI 21-103, 14 December 2005

Certified by: AF/A4L

(Sue A. Lumpkins)

Pages: 123

This instruction implements AFPD 21-1, Air and Space Maintenance. It establishes inventory, status, and utilization reporting for selected aerospace vehicles and equipment. This instruction applies to Active Duty, Air National Guard, and US Air Force Reserve Command, and

Government plant representatives assigned to commercial contractor facilities. This instruction implements the material condition measurement reporting requirements of DOD Instruction

3110.5, Material Condition Reporting for Mission - Essential Systems and Equipment, September 25, 2006. In addition, it provides guidance and direction for managing aircraft and missile equipment throughout the Air Force. Refer recommended changes and questions about this publication to AF/A4LM using the AF IMT 847, Recommendation for Change of

Publication; route AF IMT 847s from the field through the appropriate functional‘s chain of command. For the purpose of this instruction and development of maintenance policy, Lead

Commands are Air Combat Command, Air Mobility Command, Air Force Special Operations

Command, Air Education and Training Command, Air National Guard, Air Force Reserve

Command, Air Force Space Command and Air Force Material Command. As it pertains to weapon system specific issues or requirements, AFPD 10-9, Lead Command Designation and

Responsibilities for Weapon Systems takes precedence. This publication may be supplemented at any level and does not require HAF OPR approval or coordination. Ensure that all records created as a result of process prescribed in this publication are maintained in accordance with

AFMAN 33-363, Management of Records, and disposed of in accordance with the Air Force

Records Disposition Schedule (RDS) located at https://www.my.af.mil/gcss-af61a/afrims/afrims.

http://www.e-publishing.af.mil./ https://www.my.af.mil/gcss-af61a/afrims/afrims

2 AFI21-103 9 APRIL 2010

SUMMARY OF CHANGES

Major changes include defining Reliability, Availability, Maintainability for Pods (RAMPOD) as the tool used for financial reporting to Defense Finance and Accounting Service (DFAS) for all

AF externally carried pods (including leased pods) and uses RAMPOD to account for pod assets possessed by the ―Total Force‖ (Active Duty, Air National Guard, or US Air Force Reserve

Command). The use of possession purpose identifier (PPI) code "BU" is expanded. Clarifies policy on the use of PPI codes "PJ" and "PR", and provides additional guidance on Operations

Group Aerospace Vehicle Utilization Monitor (OG AVUM) responsibilities. Additionally PPI code ―BQ‖ is not authorized when the only reason for the communication with depot engineering has been directed by technical order or previous disposition instructions on an existing condition.

Office symbols and publication references were updated throughout. Also, the process for reporting aircraft possessed by depot/contract field teams has been updated. Finally, Chapter 5 has been deleted and Chapter 6 has been updated to provide current policy and procedures for all

Communication & Information maintainers.

Chapter 1—REPORTING GUIDELINES 9

1.1. Using Report Information

1.2. Correct Reporting

1.3. Offices of Responsibility

1.4. Allied Publications

Chapter 2—AIRCRAFT, DRONE, AND UNMANNED AEROSPACE SYSTEMS (UAS)

INVENTORY, STATUS, AND UTILIZATION REPORTING 11

Section 2A—Reporting System Overview 11

2.1. Concepts

2.2. The Reporting System

2.3. Transmitting Data

2.4. Security Classification

Section 2B—Reporting Responsibilities 11

2.5. Base and Depot Level Activities

2.6. MAJCOM and FOA AVDO and Utilization Monitors

2.7. HQ AFMC AVDO

2.8. Contract Administration Activities (Except Contract Field Teams)

Section 2C—Aircraft Inventory Reporting 14

2.9. Assignment Procedure

2.11. Criteria for Gaining or Losing Possession. Possession of an aircraft changes when: 16

2.12. Criteria for Terminating Possession

AFI21-103 9 APRIL 2010 3

2.13. Criteria for Reporting Aircraft as Deployed

2.14. Possession Reporting Criteria for Depot Teams

2.15. Notifying MAJCOMs of Possession Changes

2.16. Gain Message, Aerospace Equipment Possession Change Report

2.17. Loss Message Aerospace Equipment Possession Change Report

2.18. Termination Message, Aerospace Equipment Termination Report

2.19. Possession Purpose Identifier Code Change Message, A

2.20. Mission, Design, and Series (MDS)/Configuration Identifier Change Message, .. 19

2.21. How To Determine Codes

Section 2D—Aircraft Logistics Status Reporting 20

2.22. Reporting Maintenance Status

2.23. Determining Maintenance Status

2.24. Pacing Items

2.25. Minimum Essential Subsystems List (MESL)

2.26. Developing the MESL

Figure 2.1. Sample MESL

Figure 2.2. F -15 MINIMUM ESSENTIAL SUBSYSTEMS LIST (MESL)

2.27. Determining Aircraft Maintenance Status and Capability

Table 2.1. Aircraft Maintenance Status Code Flow Chart

Section 2E—Aircraft Utilization Reporting Note: Not Applicable to UAS‘s. 27

2.28. Flying Hour Program

2.29. Aircraft Utilization Reporting Concept

2.30. What to Report

2.31. Multiple Utilization Reporting

Section 2F—Accountability, Termination, and Delivery Procedures 30

2.32. Aircraft Accountability

2.33. Final Termination Accountability

2.34. Delivering Aircraft to Agencies Outside the Air Force

Table 2.2. DD Form 1149 Distribution Chart

2.35. Using AFTO Form 290

Section 2G—Reporting Assigned and Possessed Drones and Unmanned Aerospace Systems (UAS) 34

2.36. Possession Reporting

4 AFI21-103 9 APRIL 2010

2.37. Notification Procedures

Section 2H—Financial Accountability 34

2.38. Asset Value

2.39. Modification Value

Chapter 3—INVENTORY AND STATUS REPORTING OF MISSILES 37

Section 3A—Reporting Intercontinental Ballistic Missiles (ICBMs) 37

3.1. Types of Reporting

3.2. Possession Gain, Loss, and Relocation Criteria:

3.3. Notification Procedures

3.4. ICBM Accountability

3.5. ICBM Condition Status Reporting

3.6. NMCM and NMCS Time

Section 3B—Air Launched Cruise Missiles 39

3.7. Air Launched Cruise Missiles Reporting:

Section 3C—Financial Accountability 40

3.8. Asset Value

3.9. Modification Value

Chapter 4—FLIGHT SIMULATOR AND TRAINER DEVICE INVENTORY REPORTING 41

4.1. Trainers Covered Under This Instruction

4.2. Responsibilities

4.3. Trainer Equipment Designators (EQD):

4.4. Trainer Serial Number

4.5. Reporting Criteria

4.6. Possession Gain

4.7. Possession Loss

4.8. Possession Termination

4.9. Audit Requirements

Chapter 5—RESERVED 44

Chapter 6—COMMUNICATIONS EQUIPMENT STATUS AND INVENTORY REPORTING 45

6.1. Purpose

6.2. Terms/Status Definitions

6.3. Security Exemption

AFI21-103 9 APRIL 2010 5

6.4. Responsibilities:

6.5. What is Reportable?

6.6. Equipment Status Reporting Procedures

6.7. Inventory Records

Table 6.1. IMDS Current Downtime/ Delay Code Summary to REMIS Status Conversion . 53

Table 6.2. IMDS to REMIS Status Code Conversion Cross Reference

Table 6.3. – IMDS to REMIS Downtime to Reason Code

Table 6.4. IMDS to REMIS Delay to Reason Code Conversion Cross Reference

6.8. Organization Record

6.9. Organization Changes

Chapter 7—AUTOMATIC TEST EQUIPMENT (ATE) INVENTORY, STATUS, AND

UTILIZATION REPORTING 63

Section 7A—Reporting System Overview 63

7.1. How and What To Report

7.2. Basic Reporting Concept

7.3. Contractor Reporting

7.4. The Reporting System

7.5. Security Classification

Section 7B—Reporting Responsibilities 64

7.6. Unit-Level Activities

7.7. MAJCOMs:

7.8. MAJCOM POCs:

7.9. ATE SYSTEM PROGRAM DIRECTOR (SPD)

Chapter 8—SPACE VEHICLE INVENTORY, STATUS, AND UTILIZATION REPORTING 66

Section 8A—Space Vehicle Reporting 66

8.1. Purpose

8.2. What is Reportable

8.3. Reporting Accuracy

8.4. Status Definitions

Section 8B—Space Vehicle Responsibilities 66

8.5. Security Exemption

8.6. Inventory Reporting

6 AFI21-103 9 APRIL 2010

8.7. Status Reporting

8.8. Organization Record

8.9. Organization Changes

8.10. Notification Procedures

Chapter 9—AIRCRAFT AND MISSILE EQUIPMENT ACCOUNTABILITY PROGRAM 69

Section 9A—General Information 69

9.1. What the Aircraft and Missile Equipment Accountability Program Covers

9.2. Need for Management and Control Procedures

9.3. Aircraft and Missile Equipment Inventory

9.4. Lead Commands Supplements to AFI 21-103 regarding -21 TOs

9.5. Equipment not included in -21 TOs

9.6. Asset Categories

Section 9B—Responsibilities 72

9.7. Using Command

9.8. AFMC

9.9. Base Activities

Table 9.1. 1 SPRAM Guidance

Section 9C—Managing -21 Assets 76

9.10. Transferring Aircraft or Missile -21 Assets

9.11. Disposing of Excess Assets

9.12. Increasing Authorized Levels

9.13. Arrival of New Equipment

9.14. Adjusting for Shortages

9.15. Removing Assets From Transient Aircraft

9.16. Managing Deployed Assets

9.17. Transferring Assets

9.18. Changing the Accountable Individual

Chapter 10—AVIONICS POD SYSTEM INVENTORY, STATUS AND UTILIZATION

REPORTING 81

Section 10A—Reporting System Overview 81

10.1. Description of Pods

10.2. Description of RAMPOD

AFI21-103 9 APRIL 2010 7

10.3. How and What to Report

10.4. Contractor Reporting

10.5. The Reporting System

10.6. Security Classification

10.7. Waivers From Reporting

10.8. Unit-Level Activities

10.9. MAJCOM POCs

10.10. Pod System Program Office (SPO) Pocs will accomplish the following:

10.11. Forms Prescribed

10.12. Forms Adopted

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 85

Attachment 2—MAINTENANCE STATUS CODES AND CONDITION STATUS CODES 93

Attachment 3—STANDARD MESL MISSION CODES 96

Attachment 4—REFERENCES FOR CODES USED IN AIRCRAFT REPORTING/ICBM

REPORTING 97

Attachment 5—DOWNTIME CODES FOR COMMUNICATIONS EQUIPMENT 98

Attachment 6—DELAY CODES FOR COMMUNICATIONS EQUIPMENT 101

Attachment 7—HOW TO USE AF FORM 2691, AIRCRAFT/MISSILE EQUIPMENT

PROPERTY RECORD 103

Attachment 8—HOW TO USE AF FORM 2692, AIRCRAFT/MISSILE EQUIPMENT

TRANSFER/SHIPPING LISTING 105

Attachment 9—HOW TO USE DD FORM 1149, REQUISITION AND INVOICE/SHIPPING

DOCUMENT. 107

Attachment 10—AFI 21-103 AEROSPACE EQUIPMENT POSSESSION CHANGE REPORT, GAIN. 109

Attachment 11—SAMPLE AIRCRAFT/ICBM LOSS MESSAGE 110

Attachment 12—SAMPLE AIRCRAFT/ICBM TERMINATION MESSAGE UNCLASSIFIED 111

Attachment 13—SAMPLE POSSESSION (SEE PARAGRAPH 2.19.) PURPOSE IDENTIFIER

CODE CHANGE MESSAGE CLASSIFIED 112

Attachment 14—SAMPLE MDS/CONFIGURATION IDENTIFIER CHANGE MESSAGE

UNCLASSIFIED 113

Attachment 15—EQUIPMENT STATUS REPORTING FOR AIRFIELD METEOROLOGICAL

SYSTEMS 114

8 AFI21-103 9 APRIL 2010

Attachment 16—LOADING SERIAL NUMBERS FOR WEATHER SERVICE SYSTEMS 115

Attachment 17—AEROSPACE VEHICLE AND TRAINER PURPOSE IDENTIFIER CODES 116

Attachment 18—SAMPLE ICBM RELOCATION MESSAGE UNCLASSIFIED (SEE

PARAGRAPH 3.3.1.) 123

AFI21-103 9 APRIL 2010 9

Chapter 1

REPORTING GUIDELINES

1.1. Using Report Information. The Air Force uses the information from reports produced by each reporting system mainly for accounting and analysis. Each reporting system also gives basic historical management information and data on equipment availability and use to all levels of command. Use this information to:

1.1.1. Compute the official Air Force inventory.

1.1.2. Build the Air Force programming documents and their related budget and staffing requirements.

1.1.3. Produce statistical analysis for congressional committees, the Office of Management and Budget, and the Department of Defense.

1.1.4. The MAJCOMs establish capability goals in coordination with the Air Staff to include but not limited to Mission Capable (MC), Total Not Mission Capable Maintenance

(TNMCM), and Total Not Mission Capable Supply (TNMCS). These goals enable HQ

USAF to assess resource allocation funding on a quarterly basis. The MC-rate goals and plans also go into the yearly DoD Materiel Readiness Report to Congress.

1.1.5. Compute the official Air Force Chief Financial Officer (CFO) Information.

1.2. Correct Reporting. Because the Air Force uses reports named in this instruction to develop and defend the US Air Force Plan, Program, and Budget, correct and timely reporting is critical. Errors in reporting can cause the Air Force to lose needed funding, manpower authorizations, and supplies.

1.3. Offices of Responsibility. The office of primary responsibility (OPR) for this instruction is

AF/A4LM, 1030 Air Force Pentagon, Washington D.C. 20330-1030. Offices of collateral responsibility (OCR) are:

1.3.1. AF Aerospace Vehicle Distribution Officer (AVDO) at HQ AFMC, 4375 Childlaw

Rd, Area A, Bldg 262, Room N114, Wright-Patterson AFB OH 45433-5006.

1.3.2. Aerospace Vehicle Inventory - AF/A8PE, 1070 Air Force Pentagon, Washington DC

20330-1070.

1.3.3. Intercontinental Ballistic Missile Status - HQ AFSPC, 150 Vandenberg St, Ste 1105, Peterson Air Force Base CO 80914-4470.

1.3.4. Aerospace Vehicle Utilization - AF/A3OT, 1480 Air Force Pentagon, Washington DC

20330-1480.

1.3.5. Aerospace Vehicle Status - AF/A4LM, 1030 Air Force Pentagon, Washington DC

20330-1030.

1.3.6. Communications Status and Inventory Reporting - HQ AFNIC/ESPP, 203 W. Losey

St., Room 2100, Scott Air Force Base IL 62225-5222.

1.3.7. Air Launched Cruise Missile Status--HQ ACC/A4WN, 130 Douglas Street, Ste 210, Langley AFB, VA 23665-2791

10 AFI21-103 9 APRIL 2010

1.3.8. Externally-Carried Pod Inventory – WR-ALC/ITMS, 205 Perry Street, Suite 100, Robins AFB, GA 31098.

1.4. Allied Publications. For personnel to carry out the procedures in this instruction, Maintenance Information Systems functional user manuals must include:

1.4.1. Detailed rules for filling out the forms.

1.4.2. Instructions for data entry.

1.4.3. Report formats.

AFI21-103 9 APRIL 2010 11

Chapter 2

AIRCRAFT, DRONE, AND UNMANNED AEROSPACE SYSTEMS (UAS)

INVENTORY, STATUS, AND UTILIZATION REPORTING

Section 2A—Reporting System Overview

2.1. Concepts.

2.1.1. Each Aerospace Vehicle is always possessed by a designated Air Force reporting organization at either the organizational or depot level. The possessing organization or depot will report:

2.1.1.1. The hours it possesses the aerospace vehicle.

2.1.1.2. Changes in aerospace vehicle possession.

2.1.1.3. Status conditions that affect an aerospace vehicle's ability to perform assigned missions.

2.1.1.4. Flying hours and sorties.

2.1.2. If a contractor controls or maintains an aircraft that needs inventory, status, and utilization reporting, the administrative contracting officer must submit the needed reports or information to the agency that asks for them, unless the applicable contract states otherwise.

Use these reports whenever it is in the best interest of the Government.

2.1.3. The Weapon System Program Manager is responsible for ensuring CFO data elements are properly reported in Reliability and Maintainability Information System (REMIS) in a timely fashion:

2.1.3.1. Establish the acquisition value of each asset (including the value of the GFM) once the asset is established in REMIS by the AF-AVDO.

2.1.3.2. Determine which modification contracts (organic or contract installed) need to be capitalized for CFO reporting. Initially establish the modification records (serial number and average modification cost) for each asset being modified by the specific modification contract. Once the modification is completed on an asset, enter the specific completion date in REMIS to start the CFO reporting.

2.2. The Reporting System. Units process inventory, status and utilization data using an approved Maintenance Information System (MIS). MAJCOMs, Field Operating Agencies

(FOAs), HQ AFMC, HQ USAF, and other authorized users of the Reliability and Maintainability

Information System (REMIS) database check the data.

2.3. Transmitting Data. Data will be sent to the REMIS database at specified times.

2.4. Security Classification. Aircraft inventory, status, and utilization data reported under this instruction are unclassified. Do not enter classified data into the MIS or REMIS.

Section 2B—Reporting Responsibilities

2.5. Base and Depot Level Activities. Reporting starts at base or depot-level.

12 AFI21-103 9 APRIL 2010

2.5.1. Wing/Group Commanders or depot maintenance directorate responsibilities:

2.5.1.1. Ensure personnel maintain, correct, and report all data using the procedures in

AFI 16-402, Aerospace Vehicle Programming, Assignment, Distribution, Accounting, and Termination and this instruction.

2.5.1.2. Appoint a primary and alternate AVDO to report inventory status for the unit or depot. By e-mail message, provide the MAJCOM AVDO the name, grade, duty phone, e-mail address, and office symbol of the primary and alternate AVDO annually at the beginning of each fiscal year and as changes in personnel occur.

2.5.1.3. Appoint a primary and alternate unit Aerospace Vehicle Utilization Monitor

(AVUM) within the operations group to act as the units Point of Contact (POC) to check unit or depot utilization and to verify flying hour inputs with the proper organization every day. Provide the MAJCOM AVDO the name, grade, duty phone, e-mail address and office symbol of the primary and alternate AVUM annually at the beginning of each fiscal year and as changes in personnel occur.

2.5.1.4. Ensure aircraft status attributed to supply is reported to the Logistics Readiness

Squadron (LRS) POC.

2.5.2. Unit and Depot AVDOs:

2.5.2.1. Are the primary POCs for aircraft inventory and status reporting within their organization.

2.5.2.2. Monitor and/or input data in the MIS daily.

2.5.2.3. Resolve any data reporting problems.

2.5.2.4. Ensure equipment loads to MIS for aerospace vehicles contain correct current operating time prior to performing gain transactions.

2.5.2.5. Initiate inventory transactions and movement reports as required.

2.5.2.6. Send messages as required by this instruction and Lead Command supplements.

2.5.2.6.1. E-mails are the standard format to transmit messages. Unclassified messages will be sent through official NIPR E-mail and are required to be digitally signed and encrypted using the Common Access Card Public Key Infrastructure.

Classified messages will be sent through official SIPR E-mail.

2.5.2.7. Follow procedures in AFI 16-402.

2.5.2.8. Ensure DD Form 1149, Requisition and Invoice/Shipping Document, is completed and sent as required (see Attachment 9).

2.5.2.9. Distribute assigned aircraft as required.

2.5.2.10. Prior to processing MIS data and sending gain/loss messages, verify inventory transaction dates and times (Zulu) with corresponding units, depots or contractors to ensure they match.

2.5.2.11. Upon notification of aircraft movement, prior to aircraft movement a transfer schedule needs to be developed, funded and approved by MAJCOM and program office.

Notify the MAJCOM AVDO and weapons system functional manager of the aircraft

AFI21-103 9 APRIL 2010 13

serial numbers and transfer dates by email message.. When changes occur to the transfer schedule, an updated e-mail message is required with justification of change.

2.5.2.12. Unit and Depot AVDO, must maintain a continuity book/electronic folder and

AVDO training plan.

2.5.3. Wing Data Base Managers:

2.5.3.1. Monitor the receipt acknowledgment output transmittal files from REMIS daily.

2.5.3.2. Establish ―dummy‖ depot reporting units for local depot and contract field teams reporting within the MIS.

2.5.4. Unit and Depot AVUMs:

2.5.4.1. In conjunction with the AVDO, establish and publish daily procedures for operations and maintenance to verify the accuracy of unit or depot flying hours.

2.5.4.2. Track and report flying hours and sorties on a daily, monthly and yearly basis as required by this publication and Lead Command supplements.

2.6. MAJCOM and FOA AVDO and Utilization Monitors.

2.6.1. MAJCOM AVDO’s: Ensure aircraft inventory and status errors are corrected in MIS within their organizations.

2.6.1.1. Represent their MAJCOM or FOA at AVDO meetings.

2.6.1.2. Is the single POC for maintenance of the Geographic Location Table.

2.6.1.3. Work aircraft assignment:

2.6.1.3.1. Assign command aircraft based on Major Force Program authorizations.

2.6.1.3.2. Work with other MAJCOM AVDOs, staff agencies, numbered Air Forces, and specific units in assigning, controlling, and distributing aircraft.

2.6.1.3.3. Assign aircraft within the command by issuing transfer instructions, which are kept on file IAW the AF Records Disposition Schedule in AFRIMS, https://www.my.af.mil/gcss-af61a/afrims/afrims

2.6.1.3.4. Complete aircraft assignments or reassignments no earlier than 30 calendar days prior to and no later than 30 calendar days after the effective date.

2.6.1.3.5. Help MAJCOM agencies extract data from REMIS to assist them in monitoring the Programmed Depot Maintenance (PDM) and modification schedules.

2.6.1.3.6. Serve as the OCR for maintaining the Geographic Location Code Table, Command Code Table, and Organization Table in REMIS, as shown in AFCSM 25-

524, Volume IV, EIMSURS Users Manual.

2.6.2. For aircraft transfer, replacement, or disposal:

2.6.2.1. Coordinate with other MAJCOMs, Air National Guard Bureau, Air Force

Reserve, and non-USAF organizations to move, ship, or transfer vehicles inter-theater and to file applicable movement reports.

2.6.2.2. Provide technical help to subordinate AVDOs.

14 AFI21-103 9 APRIL 2010

2.6.2.3. Work with transferring units to choose aircraft serial numbers to meet TO 00-20-

1, Aerospace Equipment Maintenance Inspection, Documentation, Policies, and

Procedures, requirements.

2.6.2.4. Ensure Nuclear Weapons Related Material accountability is maintained IAW applicable Air Force guidance.

2.6.3. MAJCOM AVUMs:

2.6.3.1. Ensure utilization data reported by their units is correct and up-to-date, including mission symbols, PEC etc. Utilization errors will be corrected at the unit level.

2.6.3.2. Ensure flying hour/sortie data is coordinated between Operations and

Maintenance at the unit level.

2.6.3.3. Ensure utilization data is coordinated between Operations and Maintenance.

2.6.3.4. Represent their MAJCOM or FOA at Headquarters AF utilization meetings.

2.6.3.5. Verify REMIS data not later than the 12th day of each month.

2.6.3.6. Maintain the REMIS utilization data and Aircraft Utilization/Mission Code

Table for their MAJCOM as shown in AFCSM 25-524, Volume IV, EIMSURS Users

Manual.

2.7. HQ AFMC AVDO

2.7.1. AF-AVDO at HQ AFMC is the Air Force AVDO.

2.7.2. Collects and checks data reported under this instruction.

2.7.3. Keeps the master Air Force assigned aircraft inventory up-to-date as stated in AFI 16-

402.

2.7.4. Verify AF inventory using REMIS screen ERP4030

2.8. Contract Administration Activities (Except Contract Field Teams). Report all gains, losses, and terminations as stated in either this instruction, Lead Command supplements, or in accordance with maintenance contracts.

Section 2C—Aircraft Inventory Reporting

2.9. Assignment Procedure. Inventory reporting starts when an aircraft is accepted according to this section and AF-AVDO at HQ AFMC initiates the first assignment procedure according to

AFI 16-402. 2.10 Possession Reporting.

2.10.1. What to report as possessed inventory:

2.10.1.1. All US Air Force-owned aircraft, including those on loan or lease to agencies outside the US Air Force as directed by HQ USAF.

2.10.1.2. Non-US Air Force-owned aircraft as directed by HQ USAF.

2.10.2. Procedures. When a unit or depot gains or losses possession of an aerospace vehicle, the unit or depot must:

2.10.2.1. Start or stop possession reporting.

AFI21-103 9 APRIL 2010 15

2.10.2.2. Coordinate the gain/loss time of transfer with the reciprocating unit.

2.10.2.3. Inform the base/depot engine manager of all aerospace vehicle losses, gains, and terminations by providing a copy of the appropriate e-mail message..

2.10.3. Criteria and limitations for use of Possession Purpose Identifier (PPI) Codes BQ, BT, BU, PJ, and PR.

2.10.3.1. PPI code "BQ" is NOT authorized when using an automated communication system (such as the AFMC Form 202, Nonconforming Technical Assistance Request and

Reply Process) when the only reason for the communication with depot engineering has been directed by technical order or previous disposition instructions on an existing condition.

2.10.3.2. "BQ" is authorized for use when the wing has submitted a request IAW TO 00-

25-107, Maintenance Assistance, or thru an automated system to request depot assistance with an NMC condition preventing the aircraft from flying, requesting a depot team, equipment, or funding is anticipated from MAJCOM and the following conditions are met:

2.10.3.2.1. No additional field level scheduled or unscheduled NMC driver(s) are in-work, (e.g.. Phase).

2.10.3.2.2. The unit lacks capability to correct the deficiency at field level and the condition has been validated by Quality Assurance as a depot level repair.

2.10.3.3. MAJCOMs shall approve the use of PPI Code ―BT‖.

2.10.3.4. "BU" is authorized to prepare an aircraft 3 duty days prior to the start of a depot/contract field team. "BU" is also authorized for up to 5 duty days after depot level maintenance for rebuilding the aircraft and completing operational checks. During this rebuild period, under no circumstances will parts be cannibalized from the aircraft while in "BU" PPI code. Prior to any cannibalization action(s), units must regain the aircraft in its primary PPI code.

2.10.3.4.1. If other major field level maintenance, i.e. phase, is in-work, BU is only authorized for the portion of time that depot level work is actually being performed.

2.10.3.4.2. BU - Repair instructions outlined in field level technical orders do not constitute depot level repair and use of PPI code BU.

2.10.3.5. "PJ" is authorized for use from the first day of crating preparation until arrival at new location, reassembly, and ground operational checks are completed. Upon receipt the aircraft may be possessed in this code no longer than 10 duty days. If an aircraft is not reassembled or placed in PPI code "PR" after 10 duty days, the aircraft must be changed back to its primary code and the current maintenance status will be reported (i.e.

NMC).

2.10.3.6. "PR" is authorized for attrition reserve aircraft and remotely operated aircraft in storage. The aircraft must be mission capable (FMC or PMC) prior to being placed in storage and maintained in an MC condition. Aircraft can move from PJ directly to PR provided the MC requirement was met before shipment. Units will continue to monitor air vehicles in PPI code PR or PJ to ensure fleet health is maintained. If a cannibalization

16 AFI21-103 9 APRIL 2010

action that creates an NMC condition is required, the air vehicle must be removed from

PPI code "PR" and status changed to reflect the air vehicles current maintenance status

(i.e. NMCS). Once aircraft are placed in PPI code PR or PJ, the unit will notify

MAJCOM-AVDO of the code change thru normal AFI 21-103 message reporting channels. Air vehicles in PPI code PR or PJ will continue to be tracked on a daily status sheet to ensure continued fleet health is maintained.

2.11. Criteria for Gaining or Losing Possession.

Possession of an aircraft changes when:

2.11.1. The flight crew of the gaining organization accepts and leaves with the aerospace vehicle unless otherwise stated in an inter-command Memorandum of Agreement (MOA).

The time of possession change is the actual time the aircraft takes off from the losing organization. For aircraft moved in a "PJ" purpose identifier, the possession changes at the time the Traffic Management Flight (TMF) of the gaining organization accepts the aircraft.

2.11.2. The flight crew of the losing organization, or a neutral flight crew, delivers the aircraft. The time of possession changes when the engines shut down at the gaining base.

Note: The Air Combat Command Air Operations Squadron ACC/AOS aircrew is considered a neutral crew if they are not assigned to the losing or gaining unit. Because flying hour sorties and hours are directly tied to aircraft possession the unit that possesses the aircraft

IAW the rules outlined above will receive flying hour/sortie credit unless otherwise specified in a MAJCOM approved MOA. This MOA must be coordinated and approved by the

MAJCOM AVDO prior to the aircraft transfer.

2.11.3. In the event, an aerospace vehicle is damaged or destroyed:

2.11.3.1. The nearest base with the necessary repair or reclamation capability takes possession. The time of possession change is the time of landing or crash.

2.11.3.2. Possession does not change if the parent organization does the repair, reclamation or termination; however the unit AVDO must initiate the proper station location code and possession purpose identifier changes.

2.11.4. In the event, a transient aircraft requires maintenance lasting more than 7 calendar days:

2.11.4.1. The organization performing the maintenance gains possession of the aircraft when it is known the work cannot be completed in 7 days.

2.11.4.2. Do not change possession if the parent organization does the maintenance. The unit AVDO must change the station location code and the possession purpose identifier to "BL."

2.11.4.3. Do not transfer possession for AMC aircraft in transit at bases where AMC has transient or en-route maintenance responsibility unless depot assistance is required.

2.11.4.4. Do not transfer possession for KC-10 aircraft unless depot assistance is required.

2.11.5. An authorized government representative accepts an aircraft from a contractor on behalf of the Air Force. In this situation:

AFI21-103 9 APRIL 2010 17

2.11.5.1. AFMC becomes the first possessing activity for new production aircraft. AF-

AVDO at HQ AFMC processes the gain in coordination with the respective ALC program office.

2.12. Criteria for Terminating Possession. Possession terminates when vehicles become training aids or transferred to the National Museum United States Air Force or at the time the aerospace vehicle meets the termination requirements of this instruction and AFI 16-402.

Termination codes can be found in the Air Force Data Dictionary. Terminate the aerospace vehicle and cease reporting if it has permanently transferred to non-Air Force activities such as:

2.12.1. Foreign countries, as applicable.

2.12.2. Other DoD agencies, such as US Army or US Navy.

2.12.3. Other Government agencies.

2.12.4. USAF Heritage Program.

2.12.5. DRMS.

2.13. Criteria for Reporting Aircraft as Deployed. When sending aerospace vehicles for use at other locations or for specialized maintenance (other than that done by a depot), list such movements and their possession accountability according to the criteria contained in paragraphs

2.13.1. through 2.13.5.

2.13.1. Satellite Operation and Detachment. An aircraft is in a satellite operation or detachment when it is moved to another station and the parent command unit continues to operate and support it. Note: Do not change possession accountability unless directed by an

Operation Plan (OPLAN). The possessing command is the command to which the flying hours are allocated.

2.13.2. Rotations. An aircraft is on rotation when direct responsibility for its operation or support changes between CONUS or overseas activities, commands, or units.

2.13.2.1. Since the flying hours are allocated according to PA documents, MAJCOMs may not change possession accountability unless the host organization is within their own command.

2.13.2.2. When the aircraft moves as a part of a total unit movement that will not integrate under a host control, the possessing organization stays the same or changes as stated in the OPLAN.

2.13.2.3. Change in station location may be made by MAJCOM option.

2.13.2.4. All reporting is done according to the OPLAN.

2.13.2.5. MAJCOMs must include the time of transfer in the OPLAN describing the movement.

2.13.3. Supporting Exercises.

2.13.3.1. The OPLAN must state possession accountability for aircraft moved to support intra-command, inter-command, or inter-service missions.

18 AFI21-103 9 APRIL 2010

2.13.3.2. If the PA document uniquely allocates the flying hours or utilization for the aircraft, the command to which the flying hours are allocated is always the possessing command.

2.13.4. Consolidated or Centralized Repair Activities. When you move an aircraft for corrosion control, refurbishment, or other maintenance, normal reporting procedures apply unless otherwise directed by the MAJCOM AVDO or Lead Command approved MOA.

2.13.5. Loaned Aircraft. Possession changes to the command and unit having direct responsibility for using and supporting the aircraft. The MAJCOM AVDO(s) or operational order directs the change.

2.14. Possession Reporting Criteria for Depot Teams. If an aircraft goes in for maintenance by contract or depot field teams, transfer possession according to these criteria:

2.14.1. For field teams (depot or contract) performing maintenance or modifications, the owning unit AVDO reports possession changes for both the owning and depot units.

2.14.1.1. Transfer possession to AFMC in purpose identifier "DJ" when the operating command receives formal AFMC acknowledgment of repair responsibility per TO 00-25-

107, but before the team starts the repair.

2.14.1.2. Change possession to purpose identifier "DM" when the depot field team begins maintenance, repair, or modification on the aircraft.

2.14.1.3. Change the aircraft possession purpose identifier to "DR" only if an AFMC aircrew will perform a Functional Check Flight (FCF).

2.14.1.4. Possession returns to the proper organization if:

2.14.1.4.1. The aircraft has received all assigned work and the required operational check or FCF (if part of the workload agreement) is accomplished.

2.14.1.4.2. The host or operating organization receives, accepts, and controls the aircraft.

2.14.1.4.3. The host or operating organization accomplishes a permanent inventory loss transaction (―TP‖).

2.14.2. Other Field Teams. If an aircraft receives depot field team maintenance, other than stated above, the command with control responsibilities over the team doing the work possesses the aircraft.

2.14.2.1. Specific responsibilities must be stated in the workload agreement.

2.14.2.2. The host unit must do the required inventory reporting.

2.15. Notifying MAJCOMs of Possession Changes.

2.15.1. Accurate reporting of possession changes is essential in order for the Air Force to accurately account for the location and use of the aircraft inventory. MAJCOMs determine procedures for reporting changes of possession within the command. Possession change messages are required on aircraft transfers between commands. For aircraft transfers, both reporting organizations must use the same ZULU time and date.

AFI21-103 9 APRIL 2010 19

2.16. Gain Message, Aerospace Equipment Possession Change Report. The unit or depot

AVDO of the organization gaining the aircraft sends a priority gain e-mail message not later than the first workday after the possession changes. See Attachment 10 for a sample gain message and instructions for preparing it. This report is designated emergency status code (ESC) C-1.

Continue reporting during emergency conditions, priority precedence. Submit data requirements assigned this category as prescribed or by any means to ensure arrival on published due dates.

2.17. Loss Message Aerospace Equipment Possession Change Report. The unit or depot

AVDO of the organization losing possession of an aircraft sends a priority loss e-mail message not later than the first workday after the possession change takes place. On new production aircraft where engines are tracked as outlined in TO 00-25-254-1 series publications, the Air

Force program office will include engine serial numbers on the loss message. See Attachment

11 for a sample loss message and instructions for preparing it. This report is designated emergency status code (ESC) C-1. Continue reporting during emergency conditions, priority precedence. Submit data requirements assigned this category as prescribed or by any means to ensure arrival on published due dates.

2.18. Termination Message, Aerospace Equipment Termination Report. The unit or depot

AVDO of the organization losing accountability of an aircraft must send a priority termination e-mail message not later than the first workday after it has been decided the aircraft should be terminated. See Attachment 12 for a sample termination message and instructions for preparing

it. This report is designated emergency status code (ESC) C-1. Continue reporting during emergency conditions, priority precedence. Submit data requirements assigned this category as prescribed or by any means to ensure arrival on published due dates. Note: If a losing organization has removed the engine/s from an aircraft prior to the aircraft being terminated then the aircraft termination message must state at item 11 that no engine/s were installed on the aircraft. For aircraft being terminated by Aerospace Maintenance and Regeneration Group

(AMARG), engine serial numbers do not need to be listed on the termination message. The

AMARG Engine Manager must continue to report all engines according to AFI 21-104, Selective

Management of Selected Gas Turbine Engines and TO 00-25-254-1/ -2, Comprehensive Engine

Management System.

2.19. Possession Purpose Identifier Code Change Message, A erospace Equipment

Possession Purpose Identifier Code Change Report. When changing a possession purpose identifier, the possessing unit or depot AVDO must send a priority message, via an email, not later than the first workday after the change. See Attachment 13 for a sample possession purpose identifier change message and instructions for preparing it. This report is designated emergency status code (ESC) C-1. Continue reporting during emergency conditions, priority precedence. Submit data requirements assigned this category as prescribed or by any means to ensure arrival on published due dates.

2.20. Mission, Design, and Series (MDS)/Configuration Identifier Change

Message, Aerospace Equipment MDS/Configuration Identifier Change Report. The AVDO of the organization changing the MDS or configuration identifier must send a

MDS/configuration identifier change e-mail message. Obtain proper authorization from the

MAJCOM AVDO before making the change, and send a priority message not later than the first workday after the change. See Attachment 14 for a sample MDS/Configuration identifier change message and instructions for preparing it. This report is designated emergency status code (ESC) C-1. Continue reporting during emergency conditions, normal precedence. Submit

20 AFI21-103 9 APRIL 2010

data requirements in this category as prescribed, or as soon as possible after submission of priority reports.

2.21. How To Determine Codes. Attachment 4 lists the references used in inventory reporting under this instruction.

Section 2D—Aircraft Logistics Status Reporting

2.22. Reporting Maintenance Status. The reporting requirements in this section are exempt from licensing in accordance with paragraph 2.11.3 of AFI 33-324, The Information Collections and Reports Management Program; Controlling Internal, Public, and Interagency Air Force

Information Collections.

2.22.1. Use multiple status reporting to the maximum extent the MIS allows. Multiple

Status meaning an aircraft can be broken for more than one condition at the same time.

2.22.2. MAJCOMs will not include possession purpose identifiers codes BJ, BK, BL, BN, BO, BQ, BR, BU, BT, PJ, PL, PM, PN, PR, TJ, TX, XJ, XR, XS, XT, XU, and XW when computing and developing rates and standards for individual organizations. Note: To determine the possession purpose identifier codes to use for calculating status metrics refer to

TO 00-20-2-WA-1, Appendix L.

2.22.3. Status reporting for permanently assigned Ground Instructional Trainer Aircraft

(GITA) is not required.

2.23. Determining Maintenance Status.

2.23.1. Attachment 2 gives a list of maintenance and condition status codes and their definitions, which are based on DoDI 3110.5, Material Condition Reporting for Mission-

Essential Systems and Equipment. These codes describe the capability of an aerospace vehicle to do its assigned missions, that is, a unit's specifically assigned wartime, training, or test missions as specified in:

2.23.1.1. The unit's Designed Operational Capability (DOC) statements.

2.23.1.2. Unit training syllabuses.

2.23.1.3. Test mission requirements.

2.23.1.4. Mission Essential Subsystems List (MESL).

2.23.2. Report any aircraft not Full Mission Capable (FMC) with a maintenance status code determined by the following criteria:

2.23.2.1. Report an aircraft that can perform at least one, but not all of its assigned missions as Partial Mission Capable (PMC). Report an aircraft that cannot perform any of its assigned missions as Not Mission Capable (NMC).

2.23.2.2. Add the letter M (maintenance), S (supply), or B (both maintenance and supply) to show the reason the aircraft is PMC or NMC.

2.23.2.3. Aircraft in codes NMCM and NMCB also show if the needed maintenance is scheduled

(S) or unscheduled (U).

AFI21-103 9 APRIL 2010 21

2.23.2.4. The dual status condition--Not Mission Capable Both (NMCB) or Partial

Mission Capable Both (PMCB)--starts when an aircraft requires both maintenance and supplies.

2.23.2.5. Change an existing maintenance or supply condition to the dual condition if discovering a second problem. For example, when an aircraft is in NMCM maintenance status code and then you find a supply problem (NMCS), change the reported status to

NMCB.

2.23.2.6. Change the dual condition when you have rectified either the maintenance or the supply problem. For example, if you fix the maintenance problem before the supply problem, change the NMCB status code to NMCS (or vice versa from NMCB to NMCM when part becomes available but maintenance is not).

2.23.2.7. Work Unit Codes (WUC). WUCs are an important part of the MIS status reporting. They determine subsystem problems and repair actions associated with a piece of equipment or a system. A proper WUC is required to be entered into the MIS status reporting when an equipment problem is discovered or repaired. If a specific WUC is not known initially due to troubleshooting, then a system or subsystem WUC may be used until the faulty component is identified. When the equipment is returned to service or when parts are placed on order, it is the expeditor‘s responsibility to provide MOC with the proper WUC to be used for the PMC or NMC status reporting period. The use of

__000 and or __00 must not be used when a more specific WUC is available.

2.23.3. Scheduled or unscheduled maintenance status stops when you finish maintenance according to applicable technical data using the following criteria:

2.23.3.1. When all ground operations checks and cure checks are complete.

2.23.3.2. If in-flight operational checks are required by technical data, maintenance status will stop when all ground checks leading up to the in-flight operational check are completed.

2.23.3.3. When you verify a lack of parts limits the mission.

2.23.3.4. If a Functional Check Flight (FCF) is required IAW TO 1-1-300, -6 FCF requirements, or any other applicable technical data, maintenance status will not stop until the FCF is completed.

2.23.4. Supply status starts after all of these actions occur:

2.23.4.1. You find the aircraft requires an essential part.

2.23.4.2. You make a valid demand on supply and/or depot. Note: When the Engine

Manager makes a demand on depot for supported replacement engine to fill an aircraft hole for which no serviceable or repairable asset is available at the unit.

2.23.4.3. Maintenance verifies the part is essential.

2.23.4.4. Maintenance and supply together verify that the needed part (serviceable or reparable and not awaiting parts) is not available on base (does not apply to Contract

Logistics Support (CLS) or Contract Operated and Maintained Base Supply (COMBS) provided parts).

22 AFI21-103 9 APRIL 2010

2.23.5. Supply time stops when maintenance receives the part(s). If maintenance cannot accept the part(s) when they are available, supply status time stops at the time supply attempts to deliver the part(s). Note: Supply time will continue if a part is received from

LRS supply activities but must be sent off-base to a contractor facility/depot for additional adjustments/configuring/programming/drilling, etc. In this instance the supply time will stop when the part is returned to maintenance from off base.

2.23.6. When you find an aircraft discrepancy during flight, maintenance status starts at the time the aircraft returns to its parking spot/engine shutdown.

2.23.7. When you find an aircraft discrepancy during ground operation, maintenance status starts at the time you found the discrepancy.

2.23.7.1. It is imperative that aircraft status accurately reflects the capability of the aircraft to perform its assigned missions. While the majority of red X discrepancies require an aircraft to be reported in a not-mission capable condition, some red X entries do not. These entries do not necessarily affect the status or the mission capability of the aircraft and do not require a maintenance repair action. Examples of red X entries that do not affect the status and mission capability are:

2.23.7.1.1. External tanks/pylons ejector cartridges removed

2.23.7.1.2. Openings/panels taped/covered prior to and during a wash

2.23.7.1.3. Protective covers installed

2.23.7.1.4. Ejection seats de-armed for static display/training

2.23.7.1.5. Reconfiguration/installation/removal of Primary Mission Equipment

(PME)

This is not intended to be an all-encompassing list as there may be other red X entries that fall into this category.

2.23.8. When maintenance places an MC aircraft into scheduled maintenance on the printed flying schedule/maintenance plan, the status changes only if you determine that maintenance cannot, and will not return the aircraft to a MC status within 2 hours.

2.23.8.1. For example, if maintenance performs Planned Scheduled Maintenance on an otherwise MC aircraft and can and will return, or is scheduled to return, the aircraft to

MC status within 2 hours, do not report it as NMC.

2.23.8.2. As another example, when you find a discrepancy during scheduled maintenance that causes the aircraft to be declared NMC, and maintenance will need more than 2 hours to return the aircraft to MC status, NMC status starts when you find the discrepancy.

2.23.9. Aircraft entering phase, periodic, Aircraft Structural Integrity Program (ASIP), or isochronal inspections will be coded NMC using the support general work unit code (WUC) for the look phase/inspection. The NMC time using the support general WUC will start when the work cards are initiated and continue through the look phase/inspection. Normal

NMC-driver WUC reporting applies after the look phase is complete.

AFI21-103 9 APRIL 2010 23

2.23.10. Management uses certain groupings of status codes to perform summaries, analyses, briefings, and so on. These groupings show total supply and maintenance limitations. A complete list of these groupings appear in Attachment 2.

2.24. Pacing Items.

2.24.1. Units will report the WUC for the mission limiting condition that will take the longest for maintenance to correct on an aircraft in PMC and NMC status. Units will use a minimum of the 3 digit WUC when reporting the driving NMC condition. All maintenance status codes are defined and associated with a condition status code as shown in Attachment

2. Note: For aircraft with systems awaiting operational check, units will report the status of the next highest NMC/PMC driver (if another mission limiting system is reported). Status reported will not be below that of system requiring operational check. When all mission limiting conditions are corrected, the unit will then report the system requiring operational check as the system driver.

2.24.2. When accomplishing single/multiple status reporting, use the following order of precedence, from most severe to least severe: Note: All Mission Capability (MICAP) write-ups must be input.

NMCBS, NMCBU, NMCS, NMCMS, NMCMU, NMCBSA, NMCBUA, NMCSA, NMCMSA,

NMCMUA, PMCB, PMCS, PMCM, FMC

2.25. Minimum Essential Subsystems List (MESL).

2.25.1. MESLs lay the groundwork for reporting the status of aircraft capability. They list the minimum essential systems and subsystems that must work on an aircraft for it to perform specifically assigned unit wartime, training, test or other missions. The MESL brings together the Full Systems List (FSL) and the Basic Systems List (BSL).

2.25.1.1. The BSL lists a unit's specifically assigned wartime, training, and test missions and the systems and subsystems that must work for a unit to accomplish those missions.

2.25.1.2. The FSL lists all systems and subsystems needed for Full Mission Performance.

It lists the essential systems and subsystems that must work to do all BSL missions

(specifically assigned unit wartime, training, or test missions), and other kinds of unit sorties such as Program Depot Maintenance (PDM) delivery flights, aircraft transfer flights, cross-countries, or other training sorties units fly.

2.25.2. The MESL allows you to compare aircraft systems, subsystems, and components, by

WUC, against the FSL and BSL across the page. In each column, mark the equipment that must work with an "X".

2.25.3. A system may have an "X" in the FSL column only or in the FSL column and any or all of the BSL columns.

2.25.3.1. If there is an "X" in the FSL column only, the equipment does not have any specifically assigned unit wartime, training, or test mission. The equipment may have other kinds of unit sorties or missions to fly such as those listed in paragraph 2.25.1.2.

2.25.3.2. If there is an "X" in the FSL column and any or all of the BSL columns, the equipment must be operational for the mission identified by the column heading.

24 AFI21-103 9 APRIL 2010

2.25.3.3. If any system or subsystem with an "X" in the FSL column only is not working, put the aircraft in maintenance status code PMC.

2.25.4. If any system or subsystem with an "X" in the FSL and all BSL columns is not working, the aircraft cannot do any mission and is status code NMC. If any BSL column does not have an "X" for the inoperative system, the status code is PMC.

2.25.5. Determine…