AFSPCI

"Series Number"

10-120102

"Date of Instruction - Spell Month Out Completely"

3 May 1996

BY ORDER OF THE COMMANDER
AIR FORCE SPACE COMMAND

"Series Title"

Operations

"Long Title - Type In All Capital Letters"

SPACE AND MISSILE CREW FORCE MANAGEMENT

This instruction implements Air Force Instruction (AFI) 10-1201, Space Operations, and complements Air Force Space Command Instruction (AFSPCI) 36-2202, Mission Ready Training, Evaluation, and Standardization Programs. It establishes policies that apply to the day to day management of the space and missile operations crew force. It applies to all Department of Defense (DoD) military, foreign national, and DoD civilian personnel assigned to Air Force Space Command operations duties. Ensure the requirement for compliance with this instruction, in conjunction with applicable portions of the Federal Personnel Manual (FPM), DoD, and other Air Force directives or instructions, is documented in the appropriate mission-ready duty position description for DoD civilian personnel. Users should send comments and suggested improvements on an AF Form 847, Recommendation for Change Publication, through appropriate command channels, to HQ AFSPC/DOO, 150 Vandenberg Street, Suite 1105, Peterson AFB CO 80914-4200. Organizations at any level may supplement this instruction. Process supplements as shown in AFI37-160, Volume 1, Table 3.2, The Air Force Publications and Forms Management Programs--Developing and Processing Publications. Forward one copy of supplements to HQ AFSPC/DOO.

SUMMARY OF REVISIONS
Changed items are indicated by an asterisk (*). Changes incorporate policy and guidance contained in HQ AFSPC/DO message, DTG 112000Z Dec 95, changes to the MCC Contingency and Severe or Hazardous Weather Checklists as a result of GUARDIAN SWORD 95-2, changes UR55-17 to NUR10-6, incorporates tour commitment dates for both 14th and 20th Air Force units and deletes references to AFSPCI36-2201.

Page

_________________________________________________________________________________

Chapter 1

POLICIES AND RESPONSIBILITIES.

1.1. Mission Ready (MR). All operations personnel who exercise command and control of an operational system or operations center that fulfills AFSPC mission requirements must be certified before performing unsupervised duty. Certification signifies confidence by a designated official in an individual's ability to perform unsupervised operations duty. MR certification applies to duty positions that are directly responsible for completing a unit's real-time operational mission. For units with an Emergency War Order (EWO) mission, MR certification will include Personnel Reliability Program (PRP), code handler, and EWO certification as prerequisites for unsupervised duty.

day duties of their assigned MR crew members and requires them to be MR as specified in chapter 3 and AFSPCI 36-2202. Numbered Air Force (NAF) commanders, wing and vice wing commanders, missile group commanders and deputy commanders, operations group commanders and deputy commanders, and operational squadron commanders (designated detachment commanders/operations officers) and operations officers of units with MR crew members all participate in the MRC Program. In addition, operational support commanders and operations officers in squadrons with MR crew members will also participate in the MRC Program.

1.3. Resource Utilization. Assigned personnel and resources must be utilized to maximize mission accomplishment.

1.5. Waiver Authority. HQ AFSPC/DOO is the waiver authority for this instruction unless specifically stated otherwise. Waivers will be granted on an individual and controlled basis. Waiver authority may not be delegated.

1.5.1. Submit fully justified waiver request, through each intermediate level of command, to HQ AFSPC/DOO.

1.5.1.1. Describe the specific requirement and state the reason a waiver is required.

1.5.1.2. Indicate when the waiver will no longer be required.

1.5.2. Intermediate command levels will recommend approval or disapproval.

Chapter 2

DUTIES AND RESPONSIBILITIES

2.1. HQ AFSPC. The Directorate of Operations will:

2.1.1. Develop policy and guidance for space and missile operations and provide assistance on problems that affect compliance when resolution is beyond the scope or resources of the NAFs.

2.1.2. Ensure Trained Personnel Requirement is adjusted to meet future strength requirements.

2.1.3. Provide MAJCOM functional managers for 13SXX and 1C6X1 AFSCs.

2.2. NAFs. The NAFs will:

2.2.1. Organize as required by AFPD38-1, Organization, and AFI38-101, Air Force Organization.

2.2.2. Implement and supplement policies and requirements established by this and other DoD and Air Force directives or instructions as required.

2.2.3. Supervise and monitor all subordinate unit operational activities and provide assistance on problems that affect compliance when resolution is beyond the scope or resources of subordinate units.

2.2.4. Monitor and assess unit mission readiness.

2.2.5. Standardize operations and procedures where possible.

2.2.6. Ensure NAF commander maintains MR status, as specified for the MRC Program, in one system supported by subordinate units.

2.3. Wings. Space and missile wings will:

2.3.1. Organize as required by AFPD38-1 and AFI38-101.

2.3.2. Implement and supplement policies and requirements established by this and other DoD and Air Force directives or instructions as required.

2.3.3. Ensure effective management and quality control of policies and requirements established by this and other DoD and Air Force directives or instructions.

2.3.4. Supervise and monitor all subordinate unit operational activities and operational effectiveness and provide assistance on problems that affect compliance when resolution is beyond the scope or resources of subordinate units.

2.3.5. Ensure wing commander and vice commander maintains MR status and evaluator qualification as specified for the MRC Program. When the wing supports more than one system, they need only be MR in one system and both should be certified in different systems.

2.3.6. Ensure adequate host base support to sustain operations (medical, command post, etc.)

2.4. Groups. When a group is a direct reporting unit to the NAF, the group assumes those responsibilities listed in paragraph 2.3. in addition to those listed below. Groups will:

2.4.1. Organize as required by AFPD38-1 and AFI38-101.

2.4.2. Implement and supplement policies and requirements established by this and other DoD and Air Force directives or instructions as required and provide assistance on problems that affect compliance when resolution is beyond the scope or resources of subordinate units.

2.4.3. Ensure standardization among subordinate units where possible.

2.4.4. Ensure group commander and deputy commander maintains MR status and evaluator qualification as specified for the MRC Program. When the group supports more than one system, they need only be MR in one system and both should be certified in different systems.

2.5. Squadrons and Detachments. Squadrons and detachments will:

2.5.1. Organize as required by AFPD38-1 and AFI38-101.

2.5.2. Implement policies and requirements established by this and other DoD and Air Force directives or instructions as required.

2.5.3. Effectively manage all resources available to optimize mission effectiveness.

2.5.4. Effectively utilize available personnel resources and maximize the number of MR crews from available resources.

2.5.5. Ensure squadron or detachment commander and operations officer maintains MR status and evaluator qualification as specified for the MRC Program.

2.5.6. Ensure assigned personnel maintain required proficiency and adhere to safe operating procedures, weapon system safety rules (WSSR), and system operations technical data or operating procedures.

2.5.7. Certify individuals assigned to MR duty positions.

2.5.8. Ensure additional duties do not interfere with individuals' responsibilities to accomplish the unit operations mission.

2.6. Individuals. Individuals will:

2.6.1. Effectively utilize all resources available to optimize mission effectiveness.

2.6.2. Maintain required proficiency and adhere to safe operating procedures, WSSRs, and system operations technical data or operating procedures.

2.6.3. Notify supervisors when a condition exists, either physical or mental, which may prevent mission accomplishment or endanger personnel safety.

Chapter 3

CERTIFICATION

3.1. Certification Requirements. Certification is the process by which an individual is authorized to perform unsupervised in an operational duty position that exercises command and control of an operational system or center. Before an individual is certified MR, they must:

3.1.1. Complete the appropriate Initial Qualification Training (IQT) and/or Unit Qualification Training (UQT) for the crew duty position or MRC Program as required by AFSPCI36-2202.

3.1.2. Complete an initial or upgrade qualification evaluation as required by AFSPCI36-2202.

3.1.3. Meet medical qualifications established in AFI48-123, if applicable.

3.2. MR Special Applications. Any time a new unit or duty position is established, new equipment or system modifications occur, or new or significantly changed operations procedures requiring training or evaluation occur, the most experienced or qualified personnel in the unit may be designated as the subject matter experts (SME) and MR. It only applies to those individuals necessary to develop the appropriate MR training and evaluation programs or those individuals necessary to support the operations, test, and evaluation process. SMEs must accomplish the appropriate training for the duty position, such as contractor provided Type I training.

3.3. Certification Official. The certifying official ensures the successful completion of all required mission-oriented training, evaluation, and any required ancillary training.

3.3.2. Duty position certification will be documented on the AFSPC Form 91, Individual's Record of Duties and Qualifications.

3.4. Restricted Status. Personnel in restricted status may not perform unsupervised MR crew duties. Document placement in restricted status on the AFSPC Form 91. As a minimum, the certifying official restricts personnel for the following reasons:

3.4.1. Failure to pass an evaluation. Multiposition certified personnel in restricted status are restricted in all assigned duty positions that require the same knowledge or proficiency that resulted in the evaluation failure.

3.4.2. Failure to receive recurring training.

3.4.3. Failure to complete a recurring evaluation.

3.4.5. (20 AF units) Failure to perform alert duty for 45 calendar days.

3.4.5.1. Effective date will be the 45th day following the last day of alert.

3.4.5.2. Alert duty at Vandenberg AFB during operational testing is creditable toward alert currency requirements of this instruction.

3.4.6. (20 AF units) Failure to maintain EWO/code handler currency.

3.4.7. (20 AF units) Failure to accomplish annual nuclear surety or missile safety training.

3.4.8. When the certifying official determines an individual no longer possesses the degree of proficiency or professionalism required and decertification action is not appropriate.

3.5. Removal from Restricted Status. The certifying official determines when to remove or retain an individual on restricted status based on the facts and circumstances of each case. Multiposition certified individuals must meet the requirements in each duty position for which they are in restricted status. Document removal from restricted status on the AFSPC Form 91. Apply the following criteria before considering removing an individual from restricted status:

3.5.1. If an individual has failed an evaluation:

3.5.1.1. Must complete the required corrective action.

3.5.1.2. As a minimum, must successfully complete a special evaluation. The certifying official may direct a recurring evaluation.

3.5.2. Individuals failing to receive recurring training must complete the unaccomplished training.

3.5.3. An individual who has not received a recurring evaluation must receive a recurring evaluation.

3.5.4. For failure to perform minimum alert or crew duty shifts, individuals must:

3.5.4.1. Complete any necessary training.

3.5.4.2. Be observed performing crew duties (simulator or field) by an instructor or evaluated by an evaluator.

3.5.5. (20 AF units) Individuals placed in restricted status for EWO or code handling errors or currency must complete individual training.

3.5.6. (20 AF units) Individuals placed in restricted status for failing to receive annual nuclear surety or missile safety training must complete the training.

3.5.7. Individuals placed in restricted status for substandard performance or professionalism must satisfy those requirements established by the certifying official.

3.6.1. Failure to demonstrate a degree of professionalism required to justify MR status or willingness to meet Air Force standards.

3.6.2. Failure to maintain the appropriate level of job proficiency.

3.6.3. (20 AF units) Pending PRP decertification action as circumstances warrant.

3.6.4. (20 AF units) Non-performance of alert duties for 90 calendar days.

Chapter 4

CREW FORCE MANAGEMENT

4.1. Crew Designators (30 and 45 SWs Excluded). For scheduling purposes, assign each crew a unique identifier. Designate individuals not assigned to a crew as either a MR or a NMR spare crew member.

4.2. MR Duty Positions. Refer to attachment 3 for a list of MR crew duty positions.

4.3. Crew Scheduling. Adherence to safe operating procedures and WSSRs is mandatory and will be given prime consideration in the planning, scheduling, briefing, and conduct of all activities.

4.3.1. (20 AF units) The OSS will publish a missile alert duty order (MADO) for each predeparture briefing. The MADO will be authenticated and distributed before the alert duty period.

4.3.2. A scheduling process will be established to build and approve a firm schedule. 20 AF units may use the Missile Crew Scheduling Information System (MCSIS) to build and maintain crew schedules.

4.3.2.1. Schedules will identify all crew operational requirements including individual duty shifts, leaves, TDY, Combat Crew Rest and Recuperation (C2 R2 ) and crew rest periods following multiday work cycles.

4.3.2.2. Coordinate schedule changes with all affected agencies as necessary. Write-in changes are acceptable if kept to a manageable level.

4.3.2.3. The planning process should take into account training, evaluation, and maintenance requirements.

4.3.3. Priorities. Availability of resources will determine the unit's ability to meet operational requirements. When scheduling, apply the following priorities:

4.3.3.1. Priority 1: Primary mission objectives.

4.3.3.2. Priority 2: Higher Headquarters (HHQ) inspections.

4.3.3.3. Priority 3: Training and evaluations.

4.3.3.4. Priority 4: HHQ directed missions, exercises or system testing.

4.3.4. Limitations. The following scheduling limitations apply:

4.3.4.1. Do not schedule duty or training 12 hours prior to predeparture briefings (20 AF units) or crew changeover (or other duty reporting time) (14 AF units). This does not preclude scheduling items of preparation immediately preceding the predeparture briefing or crew changeover.

4.3.4.2. (20 AF units) Do not schedule back-to-back alerts unless requested in writing by the MCC or missile combat crew member (MCCM). Unscheduled back-to-back alerts necessitated by unforeseen situations must be approved in writing by the scheduling authority. Annotating the MADO will suffice.

4.3.4.3. (20 AF units) Do not schedule duty or training during C2 R2 .

4.3.5.2.1. (20 AF units) Personnel with unauthorized launch (UL) access will not perform alert duty with only one other crew member. When MRCs with UL access perform alert, they will be in addition to the normally assigned crew. When rest periods begin, UL personnel will not remain in the LCC.

4.3.5.5. (20 AF units) C2 R2 period will be equal to at least 50% of the total alert time.

4.3.5.5.1. Total alert time is the time between the beginning and end of alert related duties.

4.3.5.5.2. C2 R2 begins when the MCC completes alert related duties after return to the support base.

4.3.5.6. (14 AF units) The maximum authorized rest period following a duty shift will not exceed 96 hours.

Chapter 5

ALERT AND SHIFT REQUIREMENTS

5.1. Daily Shift Requirements. The crew accomplishes all activities using the following priorities. Wartime mission accomplishment is AFSPC's number one priority and ensuring personnel safety in war and peace directly supports that goal.

5.1.1. Priority 1 - Mission in wartime environment.

5.1.2. Priority 2 - Personnel safety.

5.1.3. Priority 3 - Mission in peacetime environment.

5.1.4. Priority 4 - Primary shift responsibilities, e.g., equipment checkout, status monitoring, etc.

5.1.5. Priority 5 - Tasks required to support other than primary duty, such as training and evaluations.

5.2. Alert Duty (20 AF Units). Only complete crews composed of MR certified personnel will perform alert at EWO configured LCCs. MR spare MCCMs may perform alert in their appropriate crew position either as a substitute on a MR crew or with a complete crew composed of MR MCCMs.

5.2.1. Predeparture. Units will conduct a predeparture briefing for all MCCs before departure for each alert tour. As a minimum, the briefing will include:

5.2.1.1. Weather and road conditions.

5.2.1.2. Scheduled and unscheduled maintenance activities.

5.2.1.3. Code changes.

5.2.1.4. Unusual security requirements or situations.

5.2.2. Alternate Command Post (ACP) and Squadron Command Post (SCP). Alert tours at the ACP or SCP will be performed only by crews trained specifically in ACP or SCP duties and procedures.

5.2.3. Assuming Command. Under normal conditions, the missile combat crew commander (MCCC) assumes command of the flight area and responsibility for operations when MCC changeover requirements are complete. If EWO and Sealed Authenticator System (SAS) documents are not on site, the MCCC assumes command upon notifying the command post (squadron, alternate, or wing).

5.2.4. Command of Flight Area. While on alert, the MCCC specified on the MADO is in command of the flight area and is ultimately responsible for all activities, operations, security, and personnel in the flight area. The MCCC has authority over all personnel in the flight area, including those falling under other chains of command administratively.

5.2.4.1. The MCCC must exercise direct command and control during any actual or potential situation involving the safety and security of personnel or equipment.

5.2.4.2. The maintenance team chief is responsible for the safe operation of a missile system in the launch facility (LF) once the LF is penetrated and saved for maintenance activities. The MCCC resumes responsibility when the safety control switch is removed per maintenance withdrawal procedures.

5.2.4.3. The MCCC resumes responsibility of a sortie saved for deactivation upon start of maintenance withdrawal procedures.

5.2.5. Relief of Command. The wing commander, MG/CC, OG/CC, applicable squadron commander or flight commander may relieve an alert duty MCC or MCCM.

5.2.5.1. An evaluator or instructor MCCC may relieve a MCC if such action is required to preclude loss of life, violations of WSSRs, or major damage to equipment. If the evaluatee is rated unqualified or creates an error that would require restricted status, the evaluator must ensure the evaluatee is supervised by a crew member MR in that duty position until the on duty crew member is relieved.

5.2.5.1.1. When relieved, the former MCC must step aside and relinquish command immediately and without comment.

5.2.5.1.2. When conditions allow, the new MCCC must inform the wing and alternate command post and the squadron commander of the change of command.

5.2.5.1.3. If EWO and SAS documents are in use, they must be changed over to the new crew when conditions permit. Do not delay emergency actions to effect a changeover.

5.2.5.2. Higher headquarters inspectors or evaluators are not authorized to relieve a crew on duty in the LCC.

5.2.5.2.1. When a MCC or MCCM has received an unqualified rating due to committing critical or major errors, the inspection team chief will immediately inform the wing or MG, OG, and squadron commanders.

5.2.5.2.2. The wing or group will replace the MCC or MCCM on a priority basis.

5.2.5.3. A MCC may temporarily relinquish command to facilitate a standardization evaluation.

5.2.5.3.1. The evaluatee MCC, if qualified, or the evaluator MCC must be in command of the flight area during evaluations and will complete changeover per current weapon system operating instructions.

5.2.6. MCC Work Requirements. Schedule crew work requirements to provide reasonable and adequate sleep for each crew member. The desired minimum sleep period for each MCCM is 6 hours during each 24 hour alert duty tour.

5.2.6.1. When two MCCMs must be awake, alert, and physically capable of immediate detection of improper action (as required by WSSRs) for a period greater than 24 hours, the MG/CC or OG/CC will institute procedures to ensure crew members do not perform more than 12 consecutive hours of LCC duty.

5.2.7. Expanded Missile Data Analysis System (EMDAS). Record missile and communications maintenance and civil engineering discrepancies at the missile alert facility (MAF) on the EMDAS computer listing. 20 AF will establish standardized procedures for recording new discrepancies and cross check requirements. The MCC is responsible for the accuracy and completeness of the listing.

5.2.8. Missile Crew Logs. MCCs will use the AFSPC Form 524, Missile Combat Crew Log, to record significant events occurring during the alert. The log will be maintained in sufficient detail so significant alert activities can be reconstructed. No alterations are authorized in the preprinted area. Units may subdivide the large lined sections and locally overprint the form. For units configured with Rapid Execution and Combat Targeting (REACT), use the automated log.

5.2.9. Nuclear Weapons Transfer. DoD regulations require that custody of weapons or warheads be formally transferred to the individuals who control access to those weapons. 20 AF will establish standardized procedures to ensure this requirement is accomplished.

5.2.10. MCC Contingency Checklists. MCC actions are required for a wide variety of emergency situations for which specific guidance is not provided. If an unusual situation occurs that is not covered in technical data or other command directives, the MCC will refer to one of the following checklists, as applicable. These checklists are intended as guides and may be supplemented locally.

5.2.10.1. The MCC Contingency Checklist (attachment 4) will be used as a guide to report and control situations such as nuclear accidents, incidents, or deficiencies; non-nuclear disasters, mishaps, or hazardous situations; missile potential hazards; personnel injury or illness; Air Force Two-Person Concept violations; or any situation the MCCC deems appropriate.

5.2.10.2. The Severe or Hazardous Weather Checklist (attachment 5) will be used as a guide to receive and relay severe or hazardous weather reports. It includes procedures for tornadoes sighted in the vicinity of the MAF.

5.2.11. COMSEC. Inventory COMSEC material in the LCC in accordance with instructions provided by the local COMSEC custodian. The oncoming MCC inventories at the appropriate technical data step.

5.2.12. Control of LCC Communication Systems CRYPTO Materials. Inventory crypto devices/keying materials in accordance with instructions provided by the local COMSEC custodian.

5.2.13. Temporary Storage of Classified Material. Secure storage for classified materials carried by maintenance personnel remaining overnight at the MAF will be provided by the on-duty MCC. 20 AF will establish standardized procedures to provide for transfer of custody.

5.2.14. LCC SAS Container. Make an entry in the MCC log when the LCC sealed authenticator container is opened. Both crew members sign the log (during crew changeover) or initial the log entry (other than crew changeover) when the container is locked and verified secure. Units configured with REACT need only make an entry in the automated log.

5.3. Shift Duty (14 AF Units). The following are the minimum requirements for space operations shift duty.

5.3.1. Crew Positions. All crew positions designated as MR will be manned by MR certified personnel during all real world mission operations. The crew commander (CMDR) or crew chief, if applicable, is ultimately responsible for all activities, operations, security, and personnel in the operations (flight) area. The CMDR has authority over all personnel in the operations area, including those falling under other chains of command administratively.

5.3.1.1. A MR crew member may temporarily relinquish responsibility for his or her duty position to facilitate training or evaluation. In this instance, the trainee/evaluatee or the instructor/evaluator must be MR in the crew position. A changeover briefing is required.

5.3.2. Actions Prior to Assumption of Crew Duty:

5.3.2.1. Review the Crew Information File (CIF) for any new items.

5.3.2.2. Inventory COMSEC materials in accordance with instructions provided by the local COMSEC custodian.

5.3.2.3. Receive shift changeover briefing from off-going crew. As a minimum, the briefing will include environmental conditions, equipment status, mission status, and unusual events.

5.3.3. Operations Log. Use locally devised logs to document significant events occurring during the duty shift. If only one flight or crew log is maintained, annotate the names of all personnel performing duty during the shift. Personnel responsible for maintaining the log signs his or her name before assuming duty, at completion of duty, or both as determined locally.

5.3.4. Crew Information File (CIF). The CIF is used to provide new or updated information impacting operations to flight and crew members. Review the CIF weekly to ensure currency of information. Do not let items remain in the CIF for longer than 30 days unless still current. The CIF will not be used to notify crew members of items that are of general information not specifically pertaining to crew duty.

Chapter 6

TECHNICAL DATA AND PROCEDURES

6.1. Technical Data. Operational systems and weapon systems will not be operated without validated and verified technical data or operations procedures.

6.2. Missile Operations Manual (20 AF Units). Annotations on the paper technical data page must be in soft erasable black or red pencil only. All markings, except VB/supplement entries, must be completely erased before manual turn-in. Authorized annotations are:

6.2.1. Any annotation that does not obscure printed material, is non-directive in nature, and does not change the context or classification of the material being annotated.

6.2.2. Underlining which does not obscure or line out printed material.

6.2.3. Color highlighting on acetate that does not obscure the printed material.

6.3. Space Operations Procedures (14 AF Units). This section outlines the basic process for development, validation, and approval of procedures based on new or changed operations requirements. These procedures can be of a permanent or temporary nature. Contractor developed procedures are developed and delivered according to the specifications in the governing contract. The unit must review these contractor documents for impact to unit procedures.

6.3.1. Procedures Development and Validation:

6.3.1.1. Development. Any unit, wing, or headquarters agency may develop a procedure to fulfill a new or changed requirement. Analyze the requirement to determine exactly what actions are required by space operations personnel and which personnel are required to take the action. Once the tasking has been determined, organize the tasks in the sequence of implementation. The developer must also document the expected response for each action when accomplished.

6.3.1.2. Validation. The organization(s) required to implement the procedure first validates it through trial use. Run the procedures, noting the expected outcome for each step or task. If the outcome is not as expected, then an analysis must be done to determine any required modifications to the procedures or expected results. Provide recommendations to the developer for consideration or approval.

6.3.2. Permanent Procedures. Permanent procedures are necessary to ensure successful mission accomplishment. Although they are usually required for an indefinite period of time, they may be periodically modified to keep pace with changes to space systems or mission requirements.

6.3.2.1. Permanent procedures are documented in positional checklists or operations manuals. Locally prepared checklists are formatted in accordance with T.O. 00-5-1 and MIL-M-38784. Development of permanent procedures or changes is categorized based on the need to expedite their operational use. The three categories of changes are emergency, urgent, and routine.

6.3.2.1.1. Emergency. A change that must be implemented immediately or the deficiency would result in fatal or serious injury to personnel, extensive damage, or inability to achieve or maintain mission accomplishment.

6.3.2.1.2. Urgent. The need for a change to be implemented or the deficiency could result in personnel injury, damage to equipment or property, reduce operational efficiency, or jeopardize the safety or success of mission accomplishment.

6.3.2.1.3. Routine. The need for a change that does not fall into the emergency or urgent category. These are modifications to existing procedures that do not affect the overall process for completion, such as some regulation changes and corrections for typographical errors.

6.3.2.2. 14 AF develops procedures regarding the coordination and approval process for permanent procedures contained in positional checklists and operations manuals as well as checklist numbering schemes.

6.3.2.2.1. The coordination process must address procedure technical accuracy assurance, standardization of procedures, and training requirements.

6.3.2.2.2. The approval process must address who has final approval authority for new or changed procedures. The final approval authority ensures the procedure satisfies the operational requirement, is technically accurate, is in compliance with DoD and Air Force directives or instructions, and is formatted appropriately.

6.3.2.3. All permanent procedures are maintained in the appropriate work center. No new or changed procedures will be used for operations until properly coordinated and approved. A unit may recommend to the approving authority that the procedure be categorized as a temporary procedure (TP) pending final approval. In this case, the procedure must meet all TP requirements before implementation.

6.3.2.4. Individuals have the responsibility to take the necessary action to insure that the procedure in use is accurate. Work centers will review procedures at least annually to ensure accuracy, currency, and mission applicability.

6.3.2.5. Forward a copy of all approved permanent procedures and related training material to the unit providing system initial qualification training.

6.3.3. Temporary Procedures (TP). TPs are used once, for a limited time frame, or temporarily alter existing permanent procedures. They are usually required to be implemented because of a unique mission requirement, to support system testing, or to support a system engineering analysis requirement. They are seldom modified; instead they are regenerated as a new TP and the previous version rescinded.

6.3.3.1. A temporary procedure request (TPR) is the document used to implement a TP. The TPR includes the TP and the implementation instructions. There are three categories of TPRs to expedite their operational use, emergency, urgent, and routine.

6.3.3.1.1. Emergency. A TPR that must be implemented immediately or mission failure, extensive damage or destruction to property, or fatal or serious injury to personnel occurs.

6.3.3.1.2. Urgent. A TPR that must be implemented or the deficiency could result in personnel injury, damage to equipment or property, reduce operational efficiency, or jeopardize the safety or success of mission accomplishment. These must normally be implemented on or by a specific timeframe.

6.3.3.1.3. Routine. A TPR that does not need immediate action to ensure mission accomplishment. For example, implementation to assist in fulfilling a system engineering analysis requirement.

6.3.3.2. 14 AF develops procedures regarding the coordination and approval process for TPs.

6.3.3.2.1. TP and TPR generation will include which agencies generate TPs and TPRs, control TPRs, and close and archive completed TPRs. 14 AF establishes the specific documentation for TPRs such as temporary procedures, memograms, engineering requests, etc.

6.3.3.2.2. TPR coordination process must check the technical accuracy of the TP, determine operations personnel's ability to accomplish the procedure, and define the final approval authority before implementation and use.

6.3.3.3. As a minimum, affected duty positions receive a copy of the TPR.

6.3.3.4. The unit reviews open TPRs for possible integration into the operations of the unit. Wings determine who reviews, revokes, or extends TPRs.

DONALD G. COOK, Brigadier General, USAF
Director of Operations
REFERENCES

1. DoD Directive 1327.5, Leave and Liberty.

2. AFPD36-22, Military Training

3. AFPD38-1, Organization

4. AFI10-1201, Space Operations

5. AFI36-2201, Developing, Managing, and Conducting Training

6. AFI36-2616, Trained Personnel Requirements

7. AFI36-3003, Military Leave Program

8. AFR35-41V2 (to become AFMAN36-8001), Reserve Personnel Policy Reserve Training

9. AFI36-2104, Nuclear Weapons Personnel Reliability Program

10. AFI38-101, Air Force Organization

11. AFI48-123, Medical Examination and Standards

12. AFI60-101, Operations and Resources

13. AFI91-101, Air Force Nuclear Weapons Surety Program

14. AFI91-102, Nuclear Weapon System Safety Studies, Operational Safety Review, and Safety Rules

15. AFI91-114, Safety Rules for the Intercontinental Ballistic Missile Weapon Systems

16. AFI91-301, Air Force Occupational and Environmental Safety, Fire Prevention and Health (AFOSH) Program

17. AFI91-302, Air Force Occupational and Environmental Safety, Fire Prevention and Health (AFOSH) Standards

18. AFP36-2211, Management of Air Force Training Systems

19. AFM10-206, Operational Reporting

22. AFSPCI36-2202, Mission Ready Training, Evaluation, and Standardization Programs

23. AFSPCI36-2203, Missile Evaluation Performance Standards

24. T.O. 00-5-1, Air Force Technical Order System

TERMS EXPLAINED

1. Back-to-Back Alert. An alert tour that begins within 24 hours of completion of C2 R2 .

2. Certification. The authority given for a person to perform operations duty unsupervised.

3. Decertified status. The status of personnel previously certified as MR or in a MR duty position who may no longer accomplish any duties associated with that position.

4. Dual-position Certified. The status of an individual who is certified in more than one duty position and the tasks are either identical in both positions or one position's task requirements are a complete subset of the other duty position.

5. Duty Not Including Flying or Special Operation (DNIF). Temporarily medically unfit for operations duty. See also AFI 48-123.

6. Multiposition Certified. This is the status of operations personnel who are MR in more than one MR duty position and the operations tasking of one position is not a direct subset of the other duty position.

7. Restricted Status. Status of MR certified personnel who may not accomplish operations duty unsupervised.

MISSION READY DUTY POSITIONS

Aeronautical Control Officer (ACO)

Aeronautical Operations Control Officer (AOCO)

Commanding Systems Operator (satellite systems)(CSO)

Crew Chief (CCH)

Crew Commander (CMDR)

Data Systems Operator (DSO)

Deputy Crew Commander (DCMDR)

Deputy Missile Combat Crew Commander (DMCCC)

Detection Radar Environment Display Operator (DRO)

Flight Commander (FCMDR)

Flight Chief (FCH)

Ground Systems Operator (GSO)

Launch Director (LD)

Launch Controller (LC)

Launch Weather Officer (LWO)

Missile Combat Crew Commander (MCCC)

Mission Flight Control Officer (MCO)

Passive Systems Console Operator (PSCO)

Payload Operations Director (POD)

Planner Analyst Officer (PAO)

Range Control Officer (RCO)

Range Operations Commander (ROC)

Satellite Mission Analyst Officer (SAO)

Satellite Operations Officer (SOO)

Satellite Systems Operator (SSO)

Satellite Vehicle Officer (SVO)

Senior Mission Flight Control Officer (SMCO)

Space Object Identification Operator (SOI)

Space Systems Console Operator (SCO)

Spacecraft Operations Controller (SOC)

Systems Controller (SC)

Telemetry Systems Operator (satellite systems)(TSO)

Tracking Console Operator (TCO)

Tracking and Data Operator (TDO)

Upper Stage Vehicle Controller (UVC)

Restrict radio transmission within 50 feet of fuel spill or damaged nuclear weapon/high explosive material to those essential to control the situation. Transmission could result in fire or explosion.

NOTE

Steps in this checklist should be accomplished as the situation dictates.

1. RECORD: Time: _______________________________________

Location: ____________________________________

Event: _______________________________________

2. Evacuate personnel 4,000 feet upwind or crosswind (if required). If evacuation guidance is contained in a T.O. in use at the site, that T.O. takes precedence.

3. Direct first aid or buddy care as required.

4. Direct on site personnel to accomplish emergency procedures and stay in communication with the MAF or LCC.

5. Record important information for report:

a. Nuclear weapons involved (yes/no)

b. Required assistance:

(1) Medical: __________ ETA: __________ On site: __________

(2) Police: __________ ETA: __________ On site: __________

(3) Fire: __________ ETA: __________ On site: __________

(4) Security: __________ ETA: __________ On site: __________

(5) Other: __________ ETA: __________ On site: __________

(6) Team Chief on site: ___________________________________________

(7) Incidents or Deficiencies:

PCC __________ WSSR __________

CRE __________ 2-Person Concept Violation __________

6. Report to WCP and request assistance: "This is (grade/name) reporting a contingency situation. Are you ready to copy?" Read important information from steps 1 through 5.

7. Coordinate with the FSC for security response and brief flight area.

8. Monitor all communication systems and situation status.

9. Log contingency actions.

Tornado Watch or Warning: Post a spotter at the MAF and where any teams are working in the flight area. Direct the following evacuation procedures when personnel safety is in jeopardy:

Tornado spotted near MAF: Direct non-essential personnel to LCEB or base of tunnel junction. Direct the FSC and spotter to evacuate if safety is jeopardized. VCN procedures are not required for evacuating FSC. When hazard is no longer present, security personnel will validate site security by VCN.

Tornado spotted near manned LF: Evacuate personnel to the LEB or LSB. For a penetrated LF, evacuate security personnel to LEB or LSB and maintenance personnel to the LER. Any other teams should seek shelter in a ditch away from their vehicle.

1. Receive and report of severe or hazardous weather (as requires):

a. Weather advisory/warning number: ______________________________________________

b. Reported by: _______________________________________________________________

c. Location of report: ___________________________________________________________

d. Valid time from: _______________________________ to: ___________________________

e. Warning text: ________________________________________________________________

___________________________________________________________________________________

2. Notify the FSC to brief personnel in the flight area and MAF to take required actions.

3. Report to WCP (if required): "This is (grade/name) with a severe weather report. Are you ready to copy?" Read information gathered in step 1.

4. Monitor communication systems and situation status.

5. Log weather warnings.