"Instruction Series Number"

AFSPCI

"Series Number"

10-202

BY ORDER OF THE COMMANDER

"Date of Instruction - Spell Month Out Completely"

24 November 1995

"Series Title"

Operations

"Long Title - Type In All Capital Letters"

AIR FORCE SPACE COMMAND REPORTING SYSTEM

This instruction implements AFPD10-2, Readiness, and applies to HQ AFSPC and subordinate units. This instruction defines instructions for commanders to monitor the mission and logistics status of the command, including sensor, communications, data, and launch support systems outages; their impact on operational missions and other AFSPC resources, status of repair actions, and the coordination and evaluation of supply, transportation, and restoral actions. The reporting requirements in this instruction are structured to conform to those in the Joint Reporting Structure (JRS) of the Joint Staff (JS), the Air Force Operational Reporting System (AFOREP), and AFMAN 10-206, US Air Force Reporting Instructions and AFP 102-2, Vol I, Joint Users Handbook for Message Text Formats (JUH-MTF). This instruction does not apply to the Air National Guard nor Air Force Reserve.

SUMMARY OF REVISIONS
Revises Air Force Space Command Regulation 55-2 into instruction format; The SAWOR report has been renamed to the System Outage Report (SOR). New reporting criteria has been established for the OPREP-3 HOMELINE reports. BEELINE and PINNACLE reports have been taken out to tie in line with AFMAN 10-206. A new Spacelift Summary Message (SSM) has been incorporated. Aircraft off-station and Commander non-availability reports have been added. The SITREP report is now in line with NAF responsibilities.

PART ONE - INSTRUCTIONS, RESPONSIBILITIES, AND PROCEDURES

Paragraph

Chapter 1 -- Introduction
General .....................................................................................................................................1.1.
Overall Responsibility ................................................................................................................1.2.
Definitions and Abbreviations ....................................................................................................1.3.
Supporting Procedures ..............................................................................................................1.4.
Recommendations for Changes ................................................................................................1.5.

_______________________________
Supersedes: AFSPCR 55-2, 27 March 1992
No. of Printed Pages: 40
OPR: DOCO (MSgt Richardson)
Approved By: Brigadier General Donald G. Cook
Distribution: F

Paragraph
Chapter 2 -- AFSPC Reporting System (ARS)
General ....................................................................................................................................2.1.
AFSPC Reporting System ........................................................................................................2.2.
How to Submit Reports .............................................................................................................2.3.
Reporting Authority ...................................................................................................................2.4.
Report Categories ....................................................................................................................2.5.

Chapter 3 -- Responsibilities
General ......................................................................................................................................3.1.
HQ AFSPC ................................................................................................................................3.2.
HQ AFSPC Functional Managers ...............................................................................................3.3.
Numbered Air Force (NAF) Functional Manager ....................................................................... 3.4.
Wing/Group/Unit Responsibilities ...............................................................................................3.5.

Chapter 4 -- ARS Format and Changes
General ......................................................................................................................................4.1.
Report Description Format ..........................................................................................................4.2.
Changes, Additions, or Deletions ............................................................................................... 4.3.
Report Transmission ...................................................................................................................4.4.
Reporting Requirements and Procedures ....................................................................................4.5.

PART TWO - OPERATIONAL STATUS REPORTS

Chapter 5 -- Operational Reports (OPREP-3)
Purpose .....................................................................................................................................5.1.
Submitted By .............................................................................................................................5.2.
Submitted To .............................................................................................................................5.3.
When Submitted ........................................................................................................................5.4.
How Submitted ..........................................................................................................................5.5.
Specific Reporting Instructions ...................................................................................................5.6.
OPREP-3 Report Content ..........................................................................................................5.7.

Chapter 6 -- System Outage Report (SOR)
Purpose .......................................................................................................................................6.1.
Submitted By ...............................................................................................................................6.2.
Submitted To ...............................................................................................................................6.3.
When Submitted ..........................................................................................................................6.4.
How Submitted .............................................................................................................................6.5.
Specific Reporting Instructions .....................................................................................................6.6.
Headquarters Functional Managers ..............................................................................................6.7.

Chapter 7 -- Commander's Situation Report (SITREP)Purpose .......................................................................................................................................7.1.
Submitted By ...............................................................................................................................7.2.
Submitted To ...............................................................................................................................7.3. When Submitted ..........................................................................................................................7.4.
How Submitted .............................................................................................................................7.5.
Report Content .............................................................................................................................7.6.
Headquarters Functional Managers ..............................................................................................7.7.

Paragraph
Chapter 8 -- Launch and Range Systems Operations Report
Purpose .....................................................................................................................................8.1.
Requirements ............................................................................................................................8.2.
Scope ........................................................................................................................................8.3.
Responsibilities...........................................................................................................................8.4.
Definitions .................................................................................................................................8.5.
Classification .............................................................................................................................8.6.
Range Launch and Scrubbed Reports........................................................................................8.7.
Purpose ..................................................................................................................................8.7.1.
Submitted By ..........................................................................................................................8.7.2.
Submitted To ..........................................................................................................................8.7.3.
When Submitted .....................................................................................................................8.7.4.
How Submitted .......................................................................................................................8.7.5.
Specific Reporting Instructions ................................................................................................8.7.6.
Report Content ........................................................................................................................8.7.7.
Sample Launch Report ............................................................................................................8.7.8.
Headquarters Functional Manager ...........................................................................................8.7.9.
Spacelift Status Message ...........................................................................................................8.8.
Purpose ...................................................................................................................................8.8.1.
Daily Scheduling Message ........................................................................................................8.10.
Purpose .................................................................................................................................8.10.1.
Procedures .............................................................................................................................8.10.2.
Format ....................................................................................................................................8.10.3.

Chapter 9 -- Space Operations, Space Warning and Space Surveillance
Reporting Requirements
Daily Operations Report (DOR)/Daily Activity Report (DAR)..........................................................9.1.
Purpose ......................................................................................................................................9.1.1.
Procedures ................................................................................................................................ 9.1.2.
Notice Advisory to Navigation Users .......................................................................................... 9.3.2.

Chapter 10 -- Spectrum Interference Resolution Program
Purpose ......................................................................................................................................10.1.
Submitted To...............................................................................................................................10.2.
Report Format..............................................................................................................................10.3.

Chapter 11 -- Support to Civilian Law Enforcement (RCS DD-FF&P (Q) 1595)
Purpose ........................................................................................................................................11.1.
Submitted By ...............................................................................................................................11.2.
Submitted To ..................................................................................................................................1.3.
When Submitted ...........................................................................................................................11.4.
How Submitted .............................................................................................................................11.5.
Specific Reporting Instructions ......................................................................................................11.6.

Chapter 12 -- AFSPC Aircraft Off-Station Reporting
Purpose ........................................................................................................................................12.1.
Submitted By ................................................................................................................................12.2.
Submitted To ................................................................................................................................12.3.
When Submitted ...........................................................................................................................12.4.
How Submitted .............................................................................................................................12.5.

Paragraph
Chapter 13 -- Commander Non-Availability
Purpose ......................................................................................................................................13.1.
Submitted By ..............................................................................................................................13.2.
Submitted To ..............................................................................................................................13.3.
How Submitted .............................................................................................................................3.4.

Page
Attachments
Launch Processing Milestones ........................................................................................................33
Reportable Launch Processes .........................................................................................................35
List of Abbreviations ........................................................................................................................39

Figures
3.1. Headquarters AFSPC Functional Managers ...............................................................................7
4.1. Sample Format for Explanation of ARS Reports .........................................................................9
5.1. OPREP-3 Address List ..............................................................................................................14
6.1. System Outage Report ..............................................................................................................17
8.1. Launch or Scrubbed Launch Report Address List ......................................................................23
8.2. Sample Launch Report .............................................................................................................23
8.3. Spacelift Status Message (SSM) Address List ...........................................................................25
8.4. Generic Spacelift Status Message (SSM) Format ......................................................................26
8.5. Example SSM for 13 Apr 95 ......................................................................................................27
8.6. Sample Daily Scheduling Message ............................................................................................28
12.1. Aircraft Off-Station Report .......................................................................................................31
13.1. Commander Non-Availability Report ........................................................................................32
___________________________________________________________________________________

PART ONE - RESPONSIBILITIES AND PROCEDURES

Chapter 1

INTRODUCTION

1.1. General. This instruction establishes operational reporting within AFSPC. The reporting requirements in this instruction are structured to conform to those specified in Joint Reporting Structure (JRS) of the Joint Staff (JS) and the Air Force Operational Reporting System (AFOREP). Specific Air Force Space Command responsibilities, formats, and reporting requirements are outlined herein.

1.2. Overall Responsibilities. The Commander Space Operations Flight (DOC), Directorate of Operations (DO), and Headquarters AFSPC are the overall offices of primary responsibility (OPR) for the AFSPC Reporting System (ARS).

1.3. Definitions and Abbreviations. The definitions and abbreviations used in this instruction conform to JS Publication 1.

1.4. Supporting Procedures. This instruction outlines the requirements for the ARS and requires supporting operating procedures and checklists.

1.5. Recommendations for changes. Send recommendations and revisions to this instruction to HQ AFSPC/DOC, 150 Vandenberg St, Ste 1105, Peterson AFB CO 80914-4190 for approval.

Chapter 2

AFSPC REPORTING SYSTEM (ARS)

2.1. General. JS reports are designed at the highest level of command, and are specified for use at all levels. The JRS serves as a model for all report systems created by subordinate levels of command. The JRS defines the format and content of reports specifically required by the JS of subordinate commands and further establishes a report structure that is used by all subordinates as a prototype for subsequently designed reporting systems. This system does not include all service and command designed reports necessary to satisfy the unique missions of the services and the commands. Within AFSPC there are three separate reporting systems: the JRS of the JS, the AFOREP, and the ARS as detailed in this instruction. Where possible, the ARS follows the content and format criteria of the JRS and AFOREP. The reporting requirements in this instruction are exempt from licensing in accordance with paragraph 2.11.10 of AFI 37-124, The Information Collections and Reports Management Program; Controlling Internal, Public, and Interagency Air Force Information Collections. All AFSPC subordinate units are required to maintain Air Force publications referenced in this instruction as follows:

2.1.1. AFMAN 10-206, Operational Reporting.

2.1.2. AFP 102-2, Vol I, Joint User Handbook for Message Text Formats (JUH-MTF).

2.1.3. AFI 91-204, Investigating and Reporting USAF Mishaps.

2.1.4. AFI 31-101 Volume 1, and Volume 2 (C) The Physical Security Program (PA) (U).

2.1.5. AFI 10-707, Spectrum Interference Resolution.

2.2. AFSPC Reporting System (ARS). The system is designed to:

2.2.1. Conform to the reporting format and reporting criteria of the JRS of the JS and the AFOREP while allowing the latitude to design AFSPC unique reports using the same standardized reporting criteria.

2.2.2. Satisfy the information needs of the NCA, Chief of Staff of the Air Force (CSAF), USSPACECOM, USSTRATCOM, NORAD, and Commander, AFSPC.

2.2.3. Help the Commander, AFSPC plan, direct, coordinate, and control assigned forces.

2.2.4. Provide a systematic approach to establishing and monitoring report requirements.

2.3. How To Submit Reports:

2.3.1. AFSPC wings and groups submit reports using the procedures and addressees specified in this instruction. Wings/groups will specify reporting procedures for subordinate units. Maximum support from host bases should be arranged to meet Air Force reporting requirements for subordinate units that are tenants on other installations. Reports submitted by host bases will not be duplicated through AFSPC channels.

2.3.2. Voice reports submitted by AFSPC units begin and end with the report title.

2.4. Reporting Authority. Joint Publication 2, DOD Directive 7750.5, and AFMAN 10-206 provide the authority for ARS reporting requirements.

2.5. Report Categories. Information sent through the ARS is divided into the following categories:

2.5.1. Operational and Maintenance Reports. Provide information on planning, initiation, termination, and results of operations, significant events, incidents, or operational situations. These reports enable AFSPC commanders at all levels to determine and report their readiness capability and to provide and receive appropriate responses to significant incidents. Reports under this category are the operational reports (OPREP) and the Spectrum Interference Resolution Report.

2.5.2. Other Reports and Notifications. Provide Daily Operations Reports (DORs) and Daily Activity Reports (DARs). Those units with a requirement to submit DORs or DARs will use formats and requirements in each unit's Tactical Requirements Document (TRD), AFI, or similar document.

Chapter 3

RESPONSIBILITIES

3.1. General. This chapter identifies AFSPC responsibilities in support of the ARS.

3.2. HQ AFSPC. Commander, Space Operations Flight (DOC):

3.2.1. Manages the ARS.

3.2.2. Monitors JRS and AFOREP to ensure JS and Air Force reporting requirements are accurately reflected in this regulation.

3.2.3. Coordinates AFSPC report structure support between the JRS, AFOREP, and ARS per DOD Directive 7750.5.

3.2.4. Reviews established AFSPC operational reports to delete requirements which are no longer valid or change reports as necessary to increase effectiveness.

3.2.5. Ensures operational reporting requirements levied on AFSPC wings and groups are kept to the absolute minimum required to accomplish AFSPC's mission.

3.2.6. Validates the effectiveness of new reporting requirements recommended by AFSPC functional managers (FM).

3.3. HQ AFSPC Functional Managers (FM). FMs identified in figure 3.1. coordinate with HQ AFSPC/DOC on all reports for which they are responsible. All FMs:

3.3.1. Ensure the content, addressees and associated message PLAs of reports are current.

3.3.2. Recommend necessary changes to existing reports.

3.3.3. Identify new operational reporting requirements for ARS formatting and inclusion in this regulation.

3.4. Numbered Air Force Responsibilities (NAF). 20 AF units will be responsible for maintaining and complying with reporting requirements established by USSTRATCOM Directive 701-1. Info HQ AFSPC/DOCP and HQ AFSPC/SCMB on message and voice reports. 14 AF will be included in the Air Force Space Command chain of reporting for 14th units.

3.5. Wing/Group/Unit Responsibilities: Wing, group, and unit commanders are responsible for operating the command post and ensuring reports pertaining to assigned and attached forces are upchanneled to the AFSPCCC through the appropriate NAF operations center in a timely and accurate manner.

REPORTS OPR
AFSPC Reporting System (ARS) DOC
Operational Report (OPREP) DOC
Commander's Situation Report (SITREP) DOC
Launch and or Scrubbed Launch Report DOO
Spectrum Interference Report DOY
Spacelift Status Message (SSM) DOO
Daily Scheduling Message DOO/DOY
System Outage Report (SOR) DOC/SCM
Daily Operations Report DOO
Daily Activity Report DOO
Support to Civilian Law Enforcement Agencies (1595) DOC
Helicopter Off-Station Report DOOH
Commander Non-Availability DOC
Figure 3.1. HQ AFSPC Functional Managers.

Chapter 4

ARS FORMAT AND CHANGES

4.1. General. The ARS requires standardization of rules for describing reports and effecting changes to the system.

4.2. Report Description Format. This instruction uses a standard, formatted sequence of characteristics (figure 4.1) to describe message types. Some message types (e.g. SOR/DORs/DARs) may deviate from this format.

4.3. Changes, Additions, or Deletions. Changes, additions, or deletions to the ARS may require new reporting policies, procedures, instructions, requirements, data elements, and revisions to existing reports. Users at all levels are encouraged to submit recommendations, additions, or deletions when necessary. Changes to individual reports are sent to the FM as listed in figure 3.1 with an information copy to HQ AFSPC/DOC. FMs must review report requirement and content at least annually. FMs coordinate all changes, additions, or deletions with HQ AFSPC/DOC and applicable wings and groups to ensure currency of all reports.

4.4. Report Transmission. Reports are sent by AUTODIN/SACCS from wings, groups or GSUs (as determined by parent wing/group) unless the AFSPC Command Center directs voice only.

4.5. Reporting Requirements and Procedures. Specific reporting guidance to support the ARS is contained for each report in the appropriate chapter of this instruction. ACTION and INFORMATION addressee guidance is contained in paragraph three of each individual chapter. Specific addressee lists are the responsibility of the individual wings and groups.

PART TWO - OPERATIONAL STATUS REPORTS

Chapter 5

OPERATIONAL REPORT-3 (OPREP)

5.1. Purpose. The OPREP-3 reports use Command and Control channels to notify commanders immediately of any event or incident which may attract international, national, U.S. Air Force or significant news media interest. The report must be timely and concise, contain enough information to
allow ACTION addressees to fully understand the situation and provide information to higher levels as required. Do not delay an initial report for lack of information rather use follow-up and amplifying reports to provide additional information when it becomes available. There are a number of different OPREP-3 reports which apply to AFSPC units. For the submission of OPREP-3 PINNACLE or BEELINE reports refer to AFMAN 10-206.

5.1.1. OPREP-3 HOMELINE. Used to notify Commander, AFSPC and specific command agencies of any event or incident where HQ AFSPC-level interest is indicated, but the occurrence does not meet the criteria for submission of a PINNACLE or a BEELINE. Submit an OPREP-3 HOMELINE for:

Notes:

1. Routine speeding tickets, minor accidents (fender benders), and parking tickets will not be
reported.

2. Under no circumstances will name(s) and social security number(s) (SSN) of individuals committing, charged with, victimized by, or involved in any crime be included in either the voice or record OPREP-3 report. Identification, when needed, will be limited to broad categories such as active duty, reserve, airman, noncommissioned officer (NCO), officer, dependent, etc.

5.1.1.1. A documented attempt to disrupt or otherwise damage a ground system resource that is critical to a space program mission supported or unsupported by redundancy.

5.1.1.2. A spacecraft debris accident resulting in a complete or partial loss of a satellite's primary mission.

5.1.1.3. Loss of primary mission capability due to a satellite anomaly that is expected to exceed 48 hours, cause and or recovery action have yet to be determined, but permanent loss of mission capability is not yet declared.

Paragraph HeadingContent

1. Purpose Provides a brief description of the contents and purpose of the report.

2. Submitted By Indicates the agencies and organizations required to submit the report.

3. Submitted To Indicates the agencies and organizations to which the report is
addressed. Divides sections in ACTION and INFORMATION
addressees, as required. In all cases, the appropriate NAF and
HQ AFSPC/DOCP is an ACTION addressee.

4. When Submitted Indicates when a report is to be submitted. This may be expressed with
a specific time or on an "as required" basis.

5. How Submitted Indicates:

a. Classification instructions for reporting unit.

b. Precedence and MINIMIZE considerations.

c. Primary and alternate method of transmission.

6. Specific Provides information on special instructions and notes to include
Reporting definition of data elements. Includes the report headline where
Instructions applicable.

7. Report Content Indicates the content, specific entries, and format (if required) of the
report.

8. Sample Report Provides sample reports, where possible, for reference. Addressees
may be omitted (see SUBMITTED BY and SUBMITTED TO above).

9. Headquarters The individual assigned as the office of primary Functional Manager
responsibility for a specific report. Any and all guidance pertaining to
the report is provided by the particular functional manager.
Figure 4.1. Sample Format For Explanation of ARS Reports.

5.1.1.4. The total loss of a redundant satellite mission capability due to non-hostile causes, including personnel error. Overall program mission is unaffected.

5.1.1.5. A permanent total loss of secondary mission capability due to a non-hostile cause.

5.1.1.6. A permanent partial loss of primary/secondary/tertiary mission capability due to a non-hostile cause.

5.1.1.7. A spacecraft radioactive incident due to a non-hostile cause, involving only national agencies, and presenting no danger to human life.

5.1.1.8. Anomalous launch events up to booster and satellite separation.

5.1.1.9. Anomalous early orbit events following booster and satellite separation for space assets owned by AFSPC or those destined to be turned over to AFSPC. This report is applicable to AFSPC Satellite Operations Centers (SOCs) that participate in early orbit checkout.

5.1.1.10. Any damage to Air Force property, facilities, or equipment which affects the operational capability of the unit. Damage which is initially estimated to exceed $20,000 will also be reported. These instances include but are not limited to: structural damage to launch facilities or booster, equipment or property fires affecting Air Force installations, and other emergency situations in which base civil engineering and service personnel are directly involved.

5.1.1.11. Any widespread or extended commercial power and/or communications failures which affect sites or mission capability.

5.1.1.12. A mishap which results in a serious injury or death to a Code 4 through Code 7, Very Important Person (VIP) (see AFI 91-204).

5.1.1.13. Death or serious injury of any AFSPC active duty military. Death or serious injury of civilian personnel occurring while on duty or on the military installation. Note: Serious injury is a disabling injury resulting in hospitalization or loss of duty for more than one week (seven days).

5.1.1.14. Criminal activity in which felony charges are made or pending. (See notes 1 and 2 below).

5.1.1.15. Any contact or visit by a non-AFSPC general officer or other government official which has not been previously coordinated with HQ AFSPC Command Protocol.

5.1.1.16. Weather phenomena affecting airfield/missile/mission capability, missile warning, spacelift surveillance, satellite control, and spacelift capability (e.g. flooding, tornadoes, hurricanes, etc.).

5.1.1.17. Requests for disaster relief or actual emergency assistance provided to civilian authority.

5.1.1.18. Demonstrations on or near the military installation which are directed specifically towards the military or the installation.

5.1.1.19. Events/incidents producing aircraft damage, flight control problems or aircrew injury.

5.1.1.20. Any civil aircraft mishap which occurs on Air Force property or under the control of/in airspace controlled by an Air Force facility.

5.1.1.21. Any control tower, radar approach control (RAPCON), or launch control tower evacuation that impacts the mission.

5.1.1.22. Any aircraft, missile, missile transporter vehicle, or site damage in excess of $1,000 for ICBM forces. For space launch facilities, booster, launch vehicle or site damage in excess of $20,000.

5.1.1.23. Any dropped object incident that does not meet BEELINE criteria.

5.1.1.24. Any aircraft that has failed to arrive at its destination/compulsory reporting point, clearance limit within 30 minutes of the estimated time of arrival, and communications with or location of aircraft cannot be established.

5.1.1.25. Reports of low overflights or unauthorized flight activity near AFSPC installations.

5.1.1.26. Any extraordinary situation which exists that the unit believes justifies use of emergency use of battery power during peacetime. The report should contain any supporting information to include (as a minimum) power status of all launch facilities, travel conditions, and weather predictions.

5.1.1.27. Any missile/missile alert facility/ launch facility mishap not reportable under BEELINE or higher OPREP-3 criteria.

5.1.1.28. Status of critical Aerospace Equipment/Test Equipment which is out of commission, normal support is insufficient to resolve problem, and the equipment problem impacts the mission.

5.1.1.29. A possible code compromise not reportable in BEELINE or PINNACLE procedures.

5.1.1.30. Weather phenomena (excluding local thunderstorm activity) or other environmental factors causing termination of normal maintenance dispatch activities for missile units.

5.1.1.31. Weather phenomena or other environmental factors causing a 3-hour or more delay of regularly scheduled missile alert crew changeover.

5.1.1.32. Any electrical system malfunction, engine failure, flight control malfunction, flight instrument failure, hydraulic/pneumatic system malfunction, landing gear system and/or wheel/tire failure, or inflight physiological incident (e.g. smoke in cockpit, rapid decompression, etc.) resulting in the declaration of an inflight emergency on any AFSPC aircraft.

5.1.1.33. Helicopter Search and Rescue (SAR) support provided to either civilian agencies or to the Air Force Rescue Coordination Center (AFRCC).

5.2. Submitted By. OPREP-3 event or incident reports are submitted by the lowest level of command having knowledge of the event or incident. Commanders of tenant units make arrangements which allow them to submit record reports through host command post whenever possible.

5.3. Submitted To. AFSPC units initiate the OPREP-3 reporting sequence with a voice report through appropriate WCP or 2 CACS, followed by a record copy. Transmit record copy reports to those agencies identified in figure 5.1. (as a minimum) and route voice HOMELINE reports to the AFSPC Command Center through the appropriate NAF.

5.4. When Submitted. Send OPREP-3 HOMELINE reports by the fastest means available consistent with security constraints. This is usually by non-secure voice report followed by a record transmission. Timeliness for voice and record transmissions are as follows:

5.4.1. OPREP-3 HOMELINE voice reports must be submitted as rapidly as possible, but within 15 minutes after the affected unit commander or designated representative hasthat the event or incident isHOMELINE reportable. Transmit the record copy within one hour after the voice transmission.

5.4.2. Submit follow-on voice and record reports as new information becomes available. New information for follow-on reports (voice and record) may be consolidated as long as the basic time constraints are adhered to.

5.4.3. Submit a final voice and record report on termination of the event or incident.

5.5. How Submitted:

5.5.1. Classification. by originator according to messageand appropriate security classification guidelines.

5.5.2. Method of Transmission. Voice with follow-on record communications unless directed otherwise.

5.5.3. Precedence: IMMEDIATE for voice and record reports. FLASH in the event of any Launch and Predicted Impact (L&PI) message generation (anomalous, valid, or under investigation) with no voice communications to the MWC.

5.5.4. MINIMIZE. Not affected by MINIMIZE.

5.5.5. Authentication. As required.

5.5.6. Voice Report. Make telephonic communications, via host WCP for all appropriate higher headquarters agencies through the appropriate NAF to the AFSPC Command Center. Use voice notification format located in AFP 102-2, Vol I., Annex 141 to chapter 3, para 3-141-6.

5.5.6.1. HOMELINE. OPREP-3 HOMELINE reports thatdeal with USAF and AFSPC matters exclusively; such as deaths, injuries, and assaults are not sent to USSPACECOM or NORAD addressees. Send voice reports through the WCP, appropriate NAF, and AFSPC Command Center.

5.5.6.2. Agencies. When contact is made with the WCP, NAF and Command Center, pass a voice report giving all available information on the event or incident.

5.5.7. If the report contents are classified and securevoice communications are not available, advise higher headquarters that a hardcopy message has been submitted.

5.5.8. If expected to exceed the record copy time constraints, pass an initial voice report stating this fact.

Note: Use the OPREP reporting chain for advice or direction whenever in doubt as to which report to send.

5.5.9. Degraded Communications: When there is no voice contact with the WCP or appropriate NAF, pass all reports to the next higher level of command. If there is no contact with any level within AFSPC, pass BEELINE/PINNACLE reports to the NMCC (DSN 851-3840) or AFOC (DSN 227-6103) directly until contact with the AFSPC is reestablished. For HOMELINE reports when there is no contact with the WCP, NAF, or AFSPC Command Center, send the report to the following agencies:

5.5.9.1. NORAD/USSPACECOM Consolidated Command Center (NUCCC).

5.5.9.2. Either the Missile Warning Center (MWC), or the Space Control Center (SCC), but only if direct communication is available to these agencies.

5.5.9.3. The agencies listed in above paragraphs will pass reports to the appropriate NAF Operations Center or AFSPC Command Center by the fastest means available.

5.6. Specific Reporting Instructions. DO NOT delay OPREP-3 reporting for the purpose of sending a cosmeticallyreport. The knowledge of the event or incident is more importanttimeliness is of the essence. Commanders must be prepared to make an immediate decision as to the degree of significance of each occurrence and the necessity for reporting it. The paramount guideline for commanders making the decision to report or not report an incident or event is: WHEN IN DOUBT - REPORT IT. No criticism is forthcoming for reporting an event or incident which at the time seemed significant but is later deemed to be not reportable. If the event or incident is later deemed not reportable, make appropriate up channel notification.

5.6.1. Report Numbering. Number all OPREP-3 reports consecutively and keep a separate log for the various OPREP-3 message types. Number the first report for the calendar year 001 and subsequent in sequence; for example, 002, 003 and so forth. Further reports concerning the same event or incident use the same number with an alphabetical suffix; for example, 001A, 001B, and so forth. Since a voice report is sent first, it is numbered and the follow-on record reports use the same number; for example, initial voice report is 001, initial record report is 001, follow-on voice and associated record report is 001A so forth.

5.6.1.1. Exercisenumbered independently of real-worldbeginning001 at the start of each exercisecontinueduntil exercise termination. Exercise reports should have their own log.

5.6.2. OPREP-3 HOMELINE.

5.6.2.1. At joint tenant bases, AFSPC host units submit OPREP-3 HOMELINE reports for all events or incidents affecting either the host or tenant unit.

5.6.2.2. All wing and group command posts coordinate OPREP-3 HOMELINE reporting criteria or requirements with appropriate lateral agencies (for example, security police, maintenancecontrol,
etc.) to ensure that those events or incidents which are reportable are immediately brought to the attention of the command post.

5.6.2.3. Evaluation of property or equipment damage should include a cost estimate, if available.

5.6.2.4. If requested, provide personnel data to include name, grade, and duty information on personnel involved in all events or incidents except those involving drug abuse crimes. Such personnel data may only be requested by the AFSPC staff or higher headquarters through the HQ AFSPC Command Center Crew Commander. This information is never sent in the record copy. If information is required it is sent by secure telephone.

5.6.3. Responsibilities:

5.6.3.1. NAF Operations Center and AFSPC Command Center:

5.6.3.1.1. Monitor reports submitted by wings and groups to ensure proper addressing and routing.

5.6.3.1.2. Advisestaff agencies of information received which has not been formally reported and asks for determination on the reportability of the information.

5.6.3.1.3. Maintain OPREP-3 message logs.

5.6.3.2. HQ AFSPC staff agencies notify the Command Center of events or incidents. Copies are sent immediately to HQ AFSPC Director of Staff (DS) and Public Affairs (PA). Coordinate with other staff agencies to avoid report duplication.

5.6.3.3. Wing Command Posts:

HOMELINE ADDRESS REMARKS

A HQ AFSPC PETERSON AFB CO//DOCP//

A HQ AFSPC PETERSON AFB CO//SCMC/SCMV//See Note 4

I SMC LOS ANGELES AFB CA//CC/DOC// See Note 6

I HQ AFSPC PETERSON AFB See Notes 2,4
CO/CC/CV/CE/DO/SP/JA/PA/SC/DS/DOC/DOO/
DOOH/DOOW/DOY/DPX/SCM/

I HQ AFSPC PETERSON AFB CO// See Note 4
CS/PA/SCM/DPX/DOOW/

I USSPACECOM PETERSON AFB CO//J3// See Note 5, 6

A USSTRATCOM OFFUTT AFB NE//
J361/J3612// See Note 5

A Appropriate Wing Command Post/
Group Operations Center and unit addresses See Note 8

I AFOC WASHINGTON DC// See Note 9

I Host Base //CC// See Note 3

A Appropriate NAF//CC/DO/SE//

I HQ USAF WASHINGTON DC//XOOOO// See Note 6
Figure 5.1. OPREP-3 Homeline Address List

Notes:

1. A = Action; I = Information

2. Include AFSPC/CC/CV/DS/DO as a minimum on all Homeline Reports. All AFSPC units include HQ AFSPC Security Police (SP) and Judge Advocate (JA) as an ACTION addressee only for security, law enforcement incidents, and suspected sabotage activity.

3. Address appropriate host commander on all reports.

4. Address DPX for personnel items only, DOOW concerning weather phenomena affecting AFSPC assets or capabilities, SCM for communication or computer systems, PA if incident will cause news media attention, and CE for fires or structural damage. DOOH for incidents involving AFSPC aircraft.

5. Address these agencies for impacts to the ITW/AA system.

6. Address this agency on space system incidents, accidents, mishaps, or anomalies.

7. NAF addressees will be determined by each NAF.

8. Unit addressees will be determined by each wing command post.

9. Address this agency if HOMELINE is sent to the Joint Staff or a theater CINC.

Figure 5.1. OPREP-3 Address List (Continued)

5.6.3.3.1. Monitor reports (addressed within this instruction) submitted by units to ensure proper addressing and routing.

5.6.3.3.2. Report any event or incident which may affect theof their operational mission(s) or impacts their personnel.

5.6.3.3.3. Maintain appropriate OPREP-3 event or incident numbering logs.

5.6.3.3.4. Submit reports according to the guidance in this chapter.

5.6.3.4. Wings or Groups:

5.6.3.4.1. Report any event or incident which may affect the completion of their operational mission(s) or impacts their personnel.

5.6.3.4.2. Review any event or incident which may be of interest to higher headquarters for reportability.

5.6.3.4.3. Specify reporting procedures for subordinate units.

5.6.3.4.3. Pass to appropriate command center (AFSPC Command Center or applicable WCP) informationevents or incidents which do not fall within the formal OPREP-3 reporting requirements.

5.6.3.4.4. Maintain appropriate OPREP-3 event or incident numbering logs.

5.6.3.4.5. Submit reports according to the guidance in this chapter.

5.7. OPREP-3 Report Content:

5.7.1. General Information. All reports, both voice and record, are according to the OPREP-3 format listed in AFP 102-2.

5.7.2. OPREP-3 HOMELINE. Ensure the voice or record report includes the following information when applicable:

5.7.2.1. Message identification number.

5.7.2.2. For record reports, include a reference to applicable voice and record copy reports in each additional record report.

5.7.2.3. Date time group of the event or incident.

5.7.2.4. If final report, state whether reporting is to continue via another type of report. If so, identify the type of report.

5.7.2.5. Analysis ofrelations factors involved and estimate of news media reaction.

5.7.2.6. Description of all known facts and circumstances.

5.8. Headquarters Functional Manager. Commander, Space Operations Flight (DOC).

Chapter 6

SYSTEM OUTAGE REPORT (SOR)

6.1. Purpose. The System Outage Report (SOR) is used to notify the AFSPCCC, the MWC, the SPADOC, and the NAF of any condition which could affect or is affecting the mission accomplishment of units under the control of the Commander, AFSPC. This includes all unscheduled outages that exceed or are expected to exceed the time criteria listed in paragraph 6.6.2.1. thru 6.6.2.4. or 4 hours, whichever is less. This report does not apply to launch operations. Commanders should use initiative and judgment in determining what should be reported to higher headquarters.

6.2. Submitted By. Any unit under the control of AFSPC that has knowledge of a reportable situation, with the exception of launch operations.

6.3. Submitted To: As a minimum submit the SOR to the addressees listed in figure 6.1. Wings/groups will determine further addressing.

6.4. When Submitted. When a condition is known or anticipated to exceed the timing criteria listed under paragraph 6.6.2.1 thru 6.6.2.4. or four hours, whichever is less. A voice report is required ASAP of the occurrence. Send a record copy within two hours after the voice report. Send follow-on record copy reports every 24 hours for as long as the condition exists. Send a final record report when the condition is corrected or the investigation into what caused the condition has been completed.

A= ACTION ADDRESS
I= Information

A HQ AFSPC PETERSON AFB CO//DO/DOO/DOCP//

A CMOC CHEYENNE MTN AS CO//J3OCM/SCC//

A USSPACECOM COMMAND CTR CHEYENNE MTN AS CO//MD//

A 14AF CP VANDENBERG AFB CA//

I CMOC CHEYENNE MTN AS CO//J30/J30CS//

I HQ USSPACECOM PETERSON AFB CO//J33/J330/J3//

I HQ AFSPC PETERSON AFB CO//SCMA//

I SMC LOS ANGELES AFB CA//CC/DOC//
Figure 6.1. SOR Address List.

6.5. How Submitted. Classification. Use the following criteria:

6.5.1. If a reportable condition is in progress and the estimated time of return to operation (ETRO) will or has resulted in a degradation of the unit's operational capability, classify accordingly.

6.5.1.2. Classify individual conditions according to specific system security classification guides.

6.5.2. Voice reports are sent by secure or non-secure telephonic methods depending on the classification. Send voice reports through the WCP, 14 AF, and AFSPCCC.

6.5.3. Record copy reports are sent by AUTODIN.

6.5.4. Precedence. ACTION - IMMEDIATE, INFO - PRIORTY.

6.5.5. MINIMIZE. Unaffected by MINIMIZE.

6.6. Specific Reporting Instructions. Units use the SOR to notify higher headquarters of significant operational events or incidents not reportable under OPREP-3 guidelines. DO NOT submit a SOR for routine correspondence between sites and headquarters. Avoid dual reporting. When the incident is reportable by an OPREP-3 according to this instruction, DO NOT submit a SOR. Higher headquarters (Wings, NAF, or AFSPCCC) will determine if the SOR should be elevated to OPREP-3 criteria. Submit a SOR when there is:

6.6.1. An anomalous Integrated Tactical Warning and Attack Assessment (ITW/AA) Launch and Predicted Impact (L&PI) message unless generated from a pre-planned launch while operating with unbonded software. Any L&PI message generation (anomalous, valid, or under investigation) when no voice communication is available to the MWC.

6.6.2. For missile warning units (DSP, BMEWS, PAVE PAWS, and PARCS) any unscheduled sensor site OPSCAP RED time (RED or YELLOW for BMEWS site II) exceeding or expected to exceed:

6.6.2.1. DSP, PAVE PAWS, BMEWS Site I, II, and PARCS - 30 minutes. (BMEWS Site III is regulated by SR 55-122 (S) Combined USAF/RAF Operations Manual (COM) Ballistic Missile Early Warning (BMEWS) Site III, RAF Fylingdales, England (U).

6.6.2.2. AN/FPS-17 or AN/FPS-79 unit - 2 hours.

6.6.2.3. Other space surveillance sensors - 30 minutes OPSCAP RED except when due to blanking or weather.

6.6.2.4. Total loss of communications (this includes both secure voice and teletype) for greater than 2 minutes from missile warning units to the MWC or from space surveillance units to the 2 CACS.

6.6.2.5. For AF Satellite Control Network (AFSCN):

6.6.2.5.1. Upon change of unit SYSCAP/OPSCAP caused by other than a scheduled outage if however, a unit outage continues beyond the end of a scheduled outage.

6.6.2.5.2. Upon loss of primary communications capability (voice or data) which adversely impacts the unit's ability to complete mission requirements, i.e., satellite tracking, commanding and or telemetry data retrieval. This applies to end-to-end communications capability (from the Mission Control Center (MCC), Test Support Center (TSC), Satellite Operations Center (SOC) to or from the remote ground facility/station).

6.6.2.6. For satellite operations units:

6.6.2.6.1. For satellite systems, any SYSCAP/OPSCAP change.

6.6.2.6.2. For satellite operations units (DSP, GPS, DMSP, MILSATCOM) any ground segment OPSCAP RED time exceeding or expected to exceed 30 minutes.

6.6.3. Report Content.

6.6.3.1. Name and location of unit.

6.6.3.2. Date time group of event or incident.

6.6.3.3. Equipment involved.

6.6.3.4. Statement on operational impact to include:

6.6.3.4.1. Any loss of coverage.

6.6.3.4.2. Any degradation to site primary mission and secondary mission.

6.6.3.4.3. ETRO or ATRO.

6.6.3.4.4. ETRO, use appropriate classification.

6.6.3.4.5. ATRO, include duration of event or incident.

6.6.3.4.6. Specific details of the event or incident to include:

6.6.3.4.6.1. Cause or suspected cause.

6.6.3.4.6.2. Actions taken or required to be taken.

6.6.3.4.6.3. Assessment of effect on any other equipment.

6.6.3.4.6.4. Explanation of any restoration delays.

6.6.3.4.6.5. Statement (from site point of view) on whether help from higher headquarters or another agency will be or is required.

6.6.3.4.6.6. Launch and impact (L&I) coordinates in the event of anomalous L&I message generation.

6.6.3.4.6.7. Launch and impact coordinates in the event of any L&I message generation (anomalous, valid, or under investigation) if no voice communication is available to MWC.

6.6.3.4.6.8. Any additional information which could add to the understanding of the incident.

6.6.3.4.6.9. Name, grade, and title of the person making the report.

6.7 Headquarters Functional Manager. Commander, Space Operations Flight (DOC).

Chapter 7

COMMANDER'S SITUATION REPORT (SITREP)

7.1. Purpose. The commander's SITREP is an executive assessment of the situation to include circumstances or conditions which increase or materially detract from the capability or readiness of the wing or group. See AFMAN 10-206 for specific uses of the SITREP.

7.2. Submitted By. All AFSPC wing and Group Command Posts, Numbered Air Force and the HQ AFSPC battle staff. If the battle staff is not formed, the command center submits and forwards SITREPs as required. Wings/groups will specify unit SITREP reporting requirements of subordinate units.

7.3. Submitted To:

7.3.1. Wings/Groups submit SITREPs to:

ACTION: 14AF VANDENBERG AFB CA//DO// (For space units)
20AF F E WARREN AFB WY//DO/LG// (For missile units)

7.3.2. NAFs will consolidate reports and submit to:

ACTION: USSPACECOM PETERSON AFB CO//J3/CAT// (14 AF)
CMOC CHEYENNE MTN AS CO/ /JCCD// (14 AF)
USSTRATCOM OFFUTT AFB NE//J36// (20 AF)
INFO: HQ AFSPC PETERSON AFB CO//SBS/DO/DOC/DOO/DOY/DP/IN/LG/SP/SCM//
AFMPC RANDOLPH AFB TX//PRC/DPMC//
7.3.3. HQ AFSPC submits SITREPs to:

7.3.2.1. ACTION: CSAF WASHINGTON DC//
AFOSC WASHINGTON DC//
INFO: AFMPC RANDOLPH AFB TX//PRC/DPMC//

7.4. When Submitted:

7.4.1. SITREPs are submitted automatically at DEFCON 4 or higher.

7.4.1.1. Information will be "as of" 1700Z. The report is due from the wings to appropriate NAF by 1930Z daily.

7.4.1.2. HQ AFSPC SITREP is due for HQ AFSPC SITREP no later than 0200Z the following day.

7.4.1.3. 14AF SITREP is due to USSPACECOM by 2300Z. 20AF SITREP is due to USSTRATCOM by 2300Z.

7.4.2. When directed by the respective unit commander, the Commander of AFSPC, USCINCSPACE, or the United States Air Force Chief of Staff.

7.4.2.1. When there is a significant change to the operational capability of a wing/group or NAF.

7.4.2.2. When a situation occurs which does not warrant OPREP-3 reporting, but requires Commander, AFSPC notification.

7.5. How Submitted:

7.5.1. Classification. Classify according to applicable Security Classification Guides (SCGs).
.
7.5.2. Method of Transmission. Record communications.

7.5.3. Precedence. IMMEDIATE or FLASH for record communication.

7.5.4. MINIMIZE. Unaffected by MINIMIZE.

7.6. Report Content. See AFMAN 10-206, and AFP 102-2, Volume I, SITREP Annex.

7.7. Headquarters Functional Manager. Commander, Space Operations Flight (DOC).

Chapter 8

LAUNCH AND RANGE SYSTEMS OPERATIONS REPORTS

8.1. Purpose. This chapter establishes the requirement, format, frequency, and responsibility for submission of reports on launch and range system operations. It applies to HQ AFSPC, 14 AF, 30th Space Wing (30 SW), and 45th Space Wing (45 SW).

8.2. Requirement. Reports advise the Commander, AFSPC of launch support capabilities, and existing or potential problem areas inmission capability, progress of launch generation, ranges capability to meet user needs, and launch-generation milestones.

8.3. Scope. Range systems not officially accepted as operational, but available to a user under waiver by the spacelift commanders will be reported in the same manner as operational systems.

8.4. Responsibilities:

8.4.1. The 30 SW/CC and 45 SW/CC are responsible for meeting reporting requirements established by this instruction.

8.4.2. The AFSPC Command Center incorporates the information into the commander's morning briefing or provides voice reports to the commander on significant events.

8.4.3. Changes to the status of the wing's launch readiness will be relayed to the AFSPC Command Center, in a timely manner, for dissemination to Commander, AFSPC.

8.5. Definitions:

8.5.1. Spacelift System. The launch vehicle, upper stage, payload, ground support equipment (GSE) and facilities.

8.5.2. Processing. Launch sortie generation, readiness, and range support functions performed or supported by the 30 SW and 45 SW.

8.5.3. Launch. Countdown, ignition, and subsequent flight of a launch vehicle.

8.6. Classification. Reports will be classified according to applicable program, system, and Air Force Satellite Control Network security classification guides.

8.7. Range Launch and Scrubbed Launch Reports:

8.7.1. Purpose. The Range Launch and Scrubbed Launch reports are used to provide Commander, AFSPC pertinent information on an actual launch or a launch attempt. The Range Launch Report covers the status of the vehicle from launch through final nominal time. Final nominal time is defined as: Space Launch - separation of spacecraft from booster, Missile Launch - separation of reentry vehicle from the post - boost vehicle.

8.7.2. Submitted By. Each space wing tasked to perform spacelift operations will submit this report when events warrant.

8.7.3. Submitted To. See figure 8.1.

8.7.4. When Submitted. When a launch has taken place or a scheduled launch has been scrubbed within 6 hours of T-0 time, a voice report will be upchanneled not later than 30 minutes from the first motion/broach/ignition (for Pegasus) time or the decision to scrub a launch. If a record copy will be sent within 30 minutes of the voice report, report only items 1, 2, and 3 of para 8.7.7.1. If the record copy will take longer than 30 minutes to submit, then report items 1-10.

8.7.5. How Submitted.

8.7.5.1. Method of Transmission.

8.7.5.1.1. Voice reports are made by secure or non-secure telephonic methods, dependent on classification, to 14 AF for relay to AFSPC Command Center.

8.7.5.1.2. Record copy reports are sent by AUTODIN.

8.7.5.1.3. Precedence. IMMEDIATE.

8.7.5.1.4. MINIMIZE. Unaffected by MINIMIZE.

8.7.6. Specific Reporting Instructions. The Range Launch Report should also summarize launch activity, including launch time and any range safety actions. The Scrubbed Launch report should summarize the reason for the scrubbed launch attempt, rescheduling time, and any associated information. If a record copy will be sent within 30 minutes of the voice, report only items 1, 2, 3, 8 and 9 of para 8.7.7.2. The initial report may also be a final report provided no additional information is pending.

8.7.6.1. Units will use the Range Launch or Scrubbed Launch reports as appropriate for all launch programs conducted or supported by AFSPC. This will include, but not be limited to, the following:

8.7.6.1.1. Space Launches (Titan II, Titan IV, Atlas II,IIA/IIAS, Delta II, Pegasus, NASA Shuttle, etc.).
8.7.6.1.2. Ballistic Missile Launches (Minuteman II & III, Peacekeeper, Trident I (C-4), Trident II (D-5), etc.).

8.7.6.2.3. Avoid dual reporting. Do not use the Scrubbed Launch Report for changes in launch schedules which take place prior to initiation of the range countdown. For events where catastrophic failures occur; units will report pertinent information IAW the appropriate OPREP-3 report.

8.7.7. Report Content

8.7.7.1. Format voice and record Range Launch Reports as follows:

8.7.7.1.1. LAUNCH VEHICLE/PAYLOAD: (i.e. satellite name, missile type, BMDO test name).

8.7.7.1.2. OPERATIONS NUMBER: (i.e. range scheduling Number).

8.7.7.1.3. FIRST MOTION/BROACH: (HHMM:SS.SS/DD MM YY).

8.7.7.1.4. LEAD RANGE AND LOCATION: (SLC, LF, LAT/LONG as appropriate).

8.7.7.1.5. MISSION AGENCY: (i.e. NAVY, BMDO, SDIO, 30SW, MDSSC, OSC).

8.7.7.1.6. INITIAL ASSESSMENT OF MISSION PERFORMANCE.

8.7.7.1.7. UNPLANNED HOLDS IN COUNT: (i.e. identify all unplanned/unexpected holds in count, when they occurred, their duration, and their cause).

8.7.7.1.8. FLIGHT STATUS: (Nominal,non-nominal,errant). (If launch is Errant, report current track and predicted impact point if available).

8.7.7.1.9. SAFETY ACTIONS: (N/A, functions sent and confirmed, functions sent and unable to confirm; confirmed destruct time (HHMM); reason for safety actions (to subsystem/component level if available).
(If launch is errant, report current track and predicted impact point if available) (data wrong).

8.7.7.1.10. REMARKS: (any amplifying information relating to events occurring during the launch operation).
8.7.7.2. Format voice and record Scrubbed Launch Reports as follows:

8.7.7.2.1. LAUNCH VEHICLE/PAYLOAD: (i.e. satellite name, missile type, SDIO test name).

8.7.7.2.2. OPERATIONS NUMBER: (i.e. range scheduling Number).

8.7.7.2.3. SCRUB DATE AND TIME: (HHMM/DD MM YY).

8.7.7.2.4. LOCATION AND LAUNCH COMPLEX: (i.e. Cape Canaveral AFS, Complex 40).

8.7.7.2.5. MISSION AGENCY: (i.e. NAVY, BMDO, SDIO, 45SW, MDSSC, OSC).

8.7.7.2.6. UNPLANNED HOLDS IN COUNT: (i.e. identify all unplanned/unexpected holds in count prior to scrub decision, when they occurred, their duration, and their cause).

8.7.7.2.7. NEXT LAUNCH ATTEMPT: (i.e.,specific date or unknown).

8.7.7.2.8. CAUSE FOR SCRUB: (i.e. what is broken, what action needs to be accomplished, estimated completion date/time).

8.7.7.2.9. REMARKS: (i.e. actions required to return to an operational launch status, the new projected launch date and whether or not this date is within the original launch period, impact to range schedule, and POC for additional information).

8.7.8. Sample Launch Report. See figure 8.2.

8.7.9. Headquarters Functional Manager. Chief of Current Operations (DOO).

Action/Address
Information
A 14AF VANDENBERG AFB CA//DO//
A HQ AFSPC PETERSON AFB CO//DOCP/SCML//
A HQ SMC LOS ANGELES AFB CA//CC/CLFP/CLU/DOC//
I HQ AFSPC PETERSON AFB CO//DOC/XPF/DOOL//
I HQ USSPACECOM CHEYENNE MTN AS CO//J3MO/J3SO/SSC//
I HQ USAF WASHINGTON DC//AQSS/XOOO//
I CSTC ONIZUKA AS CA//CC/VOE/VOS//
I 30 SW VANDENBERG AFB CA//CC/DO/CP//
I 45 SW PATRICK AFB FL//CC/DO/DOC//
I 1ST COMMAND AND CONTROL SQ CHEYENNE MTN AS CO//CC/DO//
I 21 SW PETERSON AFB CO//CC/CP//
I 21 OG PETERSON AFB CO//CC//
I 50 SW FALCON AFB CO//CC//
I 50 OG PETERSON AFB CO//CC//
I HQ AFMC WRIGHT PATTERSON AFB//DR//
Figure 8.1. Launch or Scrubbed Launch Report Address List

8.8. Spacelift Status Message (SSM).

8.8.1. Purpose. The SSM reports processing status and major milestones of all major spacelift systems and associated payloads. The SSM also reports significant events occurring at space launch squadrons such as pad maintenance activity and events not reported by other means.

8.8.2. Procedures.

8.8.2.1. Submission. The SSM is submitted by the wing to update mission status and report significant events at spacelift wings. If there are no changes from the previous day's SSM for a particular mission, wings will submit a message indicating "No Changes to the SSM." Message addressees are listed in figure 8.3.

UNCLAS / JOPREP JIFFY / LAUNCH REPORT/ INITIAL/028

SUBJ: TRIDENT II LAUNCH

1. LAUNCH VEHICLE: Trident II D-5
2. OPERATIONS NO: D3302
3. FIRST MOTION/BROACH: 2042:04.337 4 NOV 91
4. LEAD RANGE AND LOCATION : LAT/LONG
5. MISSION AGENCY: NAVAL ORDNANCE TEST UNIT
6. HOLDS IN COUNT: TWO
A. HELD AT T-180 MIN AWAITING SUB ARRIVAL, DURATION 45 MIN.
B. HELD AT T-20 MIN FOR FOULED TERMINAL AREA DUE TO SHIP IN AREA, DURATION 57 MIN.
7. FLIGHT STATUS: NON-NOMINAL
8. SAFETY STATUS: Confirmed destruct at 2044
9. REMARKS: Vehicle began tumbling two minutes into flight

Figure 8.2. Sample Launch Report.

8.8.2.1.1. Begin reporting on missions not later than five calendar days prior to the Booster On Stand (BOS) date (or equivalent BOS milestone) for each spacelift mission. Report planned/on-going maintenance activity, within one year, in the Other Significant Activities section of the SSM. When a vehicle is launched, report the launch time and any anomalous conditions in the remarks section of the next SSM. No further SSM inputs are required once all milestones are completed. See attachment 1 for major mission milestones.

8.8.2.1.2. The SSM is not used in lieu of normal staff actions which are the subject of separate correspondence. Wings should submit additional reports following guidance in AFMAN 10-206 or AFI 10-201.

8.8.2.1.3. The SSM will cover events for a 24 hour period beginning daily at 0600Z.

8.8.2.1.4. Use IMMEDIATE precedence and transmit NLT 0800Z over existing primary or backup record communications circuits. The SSM is not affected by MINIMIZE.

8.8.2.1.5. Each reporting space launch squadron will have a dedicated Part on the SSM (i.e. Part 1 - 1 SLS, Part 2 - 3 SLS).

8.8.2.2. Format. Use the format in Figure 8.4.

8.8.2.2.2. Paragraph 1 contains an overview of each mission being processed.

8.8.2.2.2.1. Mission. Identify the customer (DOD, Civil, Commercial) and the range operations number.

8.8.2.2.2.1.1. Payload. Identify program (i.e., GPS, DSCS, STEP), block number, and flight number.

8.8.2.2.2.1.1.1. The initial SSM for any mission will include a brief description of the mission payload, including sensor compliment and capabilities, orbital information, launch weight, etc., in the remarks section. National missions that are classified above secret will not contain a description.

8.8.2.2.2.1.2. Launch vehicle. Identify the booster (Delta II, Atlas IIAS, Titan IV, Pegasus, etc.) with tail numbers and upper stage.

8.8.2.2.2.1.3. Launch pad. Identify the pad being used for each mission.

8.8.2.2.2.1.4. Major milestones. As a minimum, identify launch processing milestones IAW attachment 1 and indicate original planned date (as planned of the booster on stand or equivalent date), current date, and actual date accomplished. Launch notification is the first date the squadron requests a launch date on the range schedule.

8.8.2.2.2.1.5. Remarks. Identify additional information associated with the specific mission such as reason for milestone slip. Account for every day of schedule difference between the planned date and actual completion date. Slips which cause more slips to the remainder of the schedule should be noted as such in the remarks section. Remarks for slips or scrubs should include the exact cause (Weather, Range, Booster, GSE, Spacecraft, Upper Stage, Solid Rocket Motors, Awaiting Anomaly Investigation, Personnel, Previous Delay, and Other), any other appropriate amplifying information, the actions required to return to green status, and the projected launch date. If status changes, explain the reason for the change, ETRO, and any follow-on actions.

8.8.2.2.2.1.6. POC. Identify a point of contact for each mission.

8.8.2.2.2.1.7. The final SSM for each mission will contain process durations (in work days) for those processes outlined in attachment 2.

8.8.2.2.2.2. Paragraph 2 of the SSM contains other significant events not related to missions in paragraph 1 such as planned maintenance downtime and hardware anomalies.

TO: HQ AFSPC PETERSON AFB CO//DOCP/DOOL/DRSS/SCML//
HQ USAF WASHINGTON DC//SEC/AQSL/XOOOO//
HQ USSPACECOM PETERSON AFB CO//SPJ330//
14AF VANDENBERG AFB CA//DO/SE//
INFO: 20AF F E WARREN AFB WY//DO//
30 SW VANDENBERG AFB CA//CC//
30 OG VANDENBERG AFB CA//CC//
30 RANS VANDENBERG AFB CA//CC/DO/DOR/DOF/DOS//
30 OSS VANDENBERG AFB CA//DOO//
45 OG PATRICK AFB FL//CC//
45 OSS PATRICK AFB FL//OSO//
45 SW PATRICK AFB//CP//
45 RANS CAPE CANAVERAL AS FL//DO//
50 OG FALCON AFB CO//CC//
50 OSS FALCON AFB//OSP//
1 SOPS FALCON AFB CO//DO//
2 SOPS FALCON AFB CO//DO//
3 SOPS FALCON AFB CO//DO//
4 SOPS FALCON AFB CO//DO//
5 SOPS ONIZUKA AFB CA//DO//
6 SOPS OFFUTT AFB NE//DO//
1 SLS CAPE CANAVERAL AS FL//DO//
2 SLS VANDENBERG AFB CA//DO//
3 SLS CAPE CANAVERAL AS FL//DO//
4 SLS VANDENBERG AFB CA//DO//
5 SLS CAPE CANAVERAL AS FL//DO//
HQ SMC LOS ANGELES AFB CA//CC/DOC/ME/CLNI/CZS//
DET 9 SMC VANDENBERG AFB CA//CC//
HQ AFMC WRIGHT PATTERSON AFB//DR//
Figure 8.3. Spacelift Status Messge(SSM) Address List.

SECRET (UNCLAS EXAMPLE)
SUBJECT: SPACELIFT STATUS MESSAGE (SSM)
PART 1 - X SLS
1. MISSION OVERVIEW
A. (U) MISSION CUSTOMER OP#
(1) (U) PAYLOAD PROGRAM BLOCK FLIGHT NUMBER
(2) (U) LAUNCH VEHICLE BOOSTER - TAIL # UPPER STAGE TAIL #
(3) (U) LAUNCH PAD SLC-XX
(4) (U) MAJOR MILESTONES:
MILESTONE PLANNED CURRENT ACTUAL
LAUNCH NOTIFICATION N/A N/A N/A
BOS DD MMM YY DD MMM YY DD MMM YY
SYSTEMS LEVEL TESTS DD MMM YY DD MMM YY DD MMM YY
LAUNCH DD MMM YY DD MMM YY DD MMM YY
(5) (U) REMARKS: MISSION RELATED
(6) (U) POC.
(7) (U) Processing Durations (last report only)

2. (U) OTHER SIGNIFICANT ACTIVITIES:
NON MISSION RELATED

FIGURE 8.4 Generic Spacelift Status Message (SSM) Format

SECRET (UNCLAS EXAMPLE)
SUBJECT: SPACELIFT STATUS MESSAGE (SSM)

PART 1 - 1 SLS

1. A. (U) MISSION COMM E2214
(1) (U) PAYLOAD DTV - 2
(2) (U) LAUNCH VEHICLE DELTA II - 225 N/A
(3) (U) LAUNCH PAD SLC - 17B
(4) (U) MAJOR MILESTONES:
MILESTONE PLANNED CURRENT ACTUAL
LAUNCH NOTIFICATION N/A N/A 02 FEB 95
BOOSTER ON STAND 03 APR 95 03 APR 95 06 APR 95 (A)
SOLIDS MATED 07 APR 95 07 APR 95 07 APR 95
SECOND STG ERECT 07 APR 95 07 APR 95 08 APR 95
SIM FLT 11 APR 95 11 APR 95 12 APR 95 (B)
SPACECRAFT MATE 13 APR 95 13 APR 95
PAYLOAD FAIRING INSTALL 15 APR 95 15 APR 95
SECOND STG PROP LOAD 16 APR 95 16 APR 95
LAUNCH 21 APR 95 21 APR 95 (C)
(5) (U) REMARKS:
(A) BOS SLIPPED 3 DAYS DUE TO WX
(B) SIMFLIGHT SLIPPED 1 DAY DUE TO MALFUNCTIONING GSE
(C) PLANNED LAUNCH DATE STILL ACHIEVABLE BY ADDING A WEEKEND SHIFT
1. B. (U) POC. CAPT JOHN DOE, 1 SLS, 467-XXXX.

FIGURE 8.5 Example SSM for 13 APR 95

8.10. Daily Scheduling Message.

8.10.1 Purpose. The daily scheduling message (DSM) provides a listing of major operations completed, scheduled, or changed since the last update and lists all major operations for the next 30 days.

8.10.2. Procedures:

8.10.2.1. Submission. The DSM will be submitted daily. However, the DSM may be submitted more frequently if required.

8.10.2.2. Submitted By. The 30th and 45th RANS scheduling centers.

8.10.2.3. Submitted To. The 30th will use AIG 8025 and the 45th will use AIG 8260.

8.10.3. Format. See Figure 8.6.

8.10.3.1. Part I. Listing of major operations completed since the last scheduling message.

8.10.3.2. Part II. Listing of major operations scheduled since last scheduling message.

8.10.3.3. Part III. Changes to major operations forecasts.

8.10.3.4. Part IV. Listing of all major operations scheduled for the next 30 days.

8.10.3.5. Part V. Miscellaneous information affecting other support agencies (i.e. ARIA and other Ranges).

8.10.3.6. Part VI. For operations not reported in the SSM, provide reason for changes listed in Part III and provide the name and phone number of a POC (i.e. Program Support Manager).

UNCLAS EFTO FOUO
SUBJECT: DAILY SCHEDULING MESSAGE (U)
(U) MESSAGE COMPILED AS OF 102100z MAY 94
1. (U) PART I: WR OP W1234 FIRST MOTION TIME OF 10/1349:00.181Z.
2. (U) PART II: ADD WR OP W7890 ATLAS E ON 04/0900-0904 JUL 94.
3. (U) PART III: WR OP W2323 NOW 03/1309-1330Z, VICE 01/1300-1321Z.
4. (U) PART IV: THIRTY DAY OPERATION FORECAST 10 MAY - 10 JUN 94:
OPNBR DATE TIME Z
W2222 12 MAY 94 1000-1100Z
W5656 19 MAY 94 1500-1515Z
W6677 08 JUN 94 1248-1356Z
5. (U) PART V: FOR ARIA W7890 REQUIRES 2 ARIA
6. (U) PART VI: W2323 SLIPPED DUE TO BOOSTER INERTIAL MEASUREMENT UNIT (IMU) FAILURE. POC: CAPT JOHN DOE, DSN 234-5678.
Figure 8.6. Sample Daily Scheduling Message

Chapter 9

SPACE OPERATIONS, SPACE WARNING AND SPACE
SURVEILLANCE REPORTING REQUIREMENTS

9.1. Daily Operations Report (DOR).

9.1.1. Purpose. The DOR reports on operational activity system outages for the Space Operations, Space Warning, and Space Surveillance squadrons.

9.1.2. Procedures:

9.1.2.1. Submission. The DOR will be submitted daily. Consider classification level of information, releasability of information, proprietary concerns, and national interest.

9.1.2.2. The DOR is not used in lieu of normal staff actions which should be the subject of separate correspondence. The wings should submit additional reports following guidance in AFMAN 10-206.

9.1.2.3. The DOR will cover events for a 24 hour period beginning daily at 0600Z.

9.1.2.4. Use IMMEDIATE precedence for action addresses, PRIORITY for information addresses, and transmit NLT 0800Z over existing primary or backup record communication circuits. The DOR will not be affected by MINIMIZE.

9.1.3. 21 SW Reporting Requirements.21 SW units will submit Daily Activity Reports (DARs)/Daily Operations Reports (DORs) to 14 AF and HQ AFSPC/DOCP/SCM/DOOO/SCMV as summaries of systems operational capabilities and performances. Space Warning Squadron DORs will be submitted IAW AFSPCI10-120105 (Tactical Requirements and Doctrine (TRDs). Space Surveillance Squadron DORs will be submitted IAW UR 55-12. DARs will be submitted IAW 21 OPORD 55-11.

9.1.4. 50 SW Reporting Requirements: 50 SW units will submit Daily Activity Reports (DARs)/Daily Operations Reports (DORs) to 14 AF and HQ AFSPC/DOCP/SCM/SCMC/DOOS as summaries of systems operational capabilities and performances.

9.1.5. The DORs contain the overall OPSCAP/SYSCAP by color code for system elements/systems at the time of the DOR closeout, a chronological listing of OPSCAP/SYSCAP changes since the previous DOR, a twenty-four hour summary of operations, rehearsal activities, and Significant Data Losses (SDLs), and remarks to include corrections or additions to previous DORs, high-interest items related to operations and mission, and miscellaneous information essential to support DOR entries. For GPS, include a chronological listing of Selective Availability/Anti-Spoofing (SA/AS) periods and levels, NDS events, and link 3 (L-3) activations. 50 SW will also provide (as soon as available) orbital accuracy (apogee, perigee, and inclination) for payload-booster separation for all launches and final mission orbit for AFSPC-operated systems in sigma terms.

9.2. Notice Advisory to Navigation Users (NANU). For GPS, the 50 SW will submit routine and supplemental NANU reports. NANUs advise GPS users of systems changes affecting quality of navigation messages and contain past and or predicated changes in accuracy or availability of navigation messages, satellite status as it affects navigation mission, remarks including corrections or additions to previous NANUS, and items related to the navigation mission. Routine NANUs are submitted as soon as possible after confirmation or implementation of a system change affecting accuracy or availability of navigation messages. Supplemental NANUs are submitted within 1 hour when navigation outages last more than 30 minutes. Transmit by PRIORITY precedence. Emergency status and precedence category assigned to this report is IMMEDIATE (C-2), minimize code is YES, classification is according to the GPS/NDS SCG.

Chapter 10

SPECTRUM INTERFERENCE RESOLUTION PROGRAM

10.1. Purpose. For reporting, identifying, evaluating and controlling electromagnetic interference (EMI) to meet electromagnetic compatibility (EMC) goals of the Air Force Electromagnetic Environmental Effects (E3) program as defined in DOD Directive 3222.3/AFSUP 1. Department of Defense Electromagnetic Compatibility Program, August 20, 1990.

10.2. Submitted To. To addressees listed in AFI 10-707 and addressees determined by parent wing. Also address the following: HQ AFSPC PETERSON AFB CO//SCMA/DOYO//

10.3. Report Format: In accordance with AFI 10-707.

Chapter 11

SUPPORT TO CIVILIAN LAW ENFORCEMENT (RCS DD-FM&P (Q) 1595)

11.1. Purpose. To notify higher headquarters of the AFSPC resources used in support of Federal, State, and local civilian law enforcement agencies and implement DOD Directive 5525.5.

11.2. Submitted By. All AFSPC wings and groups.

11.3. Submitted To:

11.3.1. Units submit the report to appropriate NAF. NAF will consolidate inputs and forward to HQ AFSPC/DOCO.

11.3.2. HQ AFSPC/DOCO submit consolidated report to:

11.3.2.1. TO: HQ USAF WASHINGTON DC//XOOOO//

11.4. When Submitted. NAFs submit report to HQ AFSPC/DOCO no later than (NLT) three working days after the end of each quarter. (Jan-Mar, Apr-Jun, Jul-Sep, Oct-Dec).

11.5. How Submitted:

11.5.1. Classification. Individual conditions are classified according to existing security classification guides.

11.5.2. Method Message, letter, or fax to HQ AFSPC/DOCO. Negative inputs are required and may be made via telephone to HQ AFSPC/DOCO.

11.6. Specific Reporting Instructions. See AFI 10-801 for instructions to complete Air Force Assistance to Civilian Law Enforcement Agencies (RCS DD-FM&P (Q) 1595).

CHAPTER 12

AFSPC AIRCRAFT OFF-STATION REPORTING

12.1. Purpose. To notify higher headquarters when an AFSPC aircraft remains over night (RON) at another installation other than homestation or their assigned unit missile facilities.

12.2. Submitted By. All AFSPC Rescue Flight (RQF) Airlift Flight (ALF) commanders.

12.3. Submitted To. RQFs/ALFs will submit reports to their wing/group command posts. Wing command posts will submit the report to the appropriate NAF with info to HQ AFSPC//DO/DOO/DOCP/DOOH//. See figure 12.1 for format and proper addresses.

12.4. When Submitted. Off-Station reports are submitted any time an aircraft is diverted to another installation due to weather, maintenance, etc. However, if the aircraft is scheduled for a planned RON, submit report 48 hours prior to departure. For C-21 aircraft, report only for those that are not higher headquarters tasked.

12.5. How Submitted:

12.5.1. Classification. Normally unclassified. If classified, classify according to classification of mission.

12.5.2. Method of Transmission. Record communications.

12.5.3. Precedence. Routine.

ACTION: 14AF VANDENBERG AFB CA//DO/CP// (For 76 RQF only)
20AF F E WARREN AFB WY//DO/CP// (For all other RQFs)

INFORMATION: HQ AFSPC PETERSON AFB CO//DO/DOO/DOCP/DOOH//

UNCLAS
SUBJECT: AFSPC AIRCRAFT OFF-STATION REPORT
1. ORGANIZATION SUBMITTING REPORT
2. CALLSIGN/TYPE OF AIRCRAFT
3. AIRCRAFT TAIL NUMBER
4. DATE/TIME DEPARTURE
5. LOCATION OF RON
6. REASON FOR RON
7. DATE/TIME RETURN
8. AIRCREW RANK AND NAME
9. WHO APPROVED THE RON
Figure 12.1. Aircraft Off-Station Report

CHAPTER 13

COMMANDER NON-AVAILABILITY REPORTING

13.1. Purpose: To notify higher headquarters when a NAF/wing/group commander is not present for duty.

13.2. Submitted By: All NAF/wing/group command posts.

13.3. Submitted To: Wing/group command posts will submit reports to HQ AFSPC//DOCP// and applicable NAF with info copies to HQ AFSPC//DO//. See figure 13.1 for sample report.

13.4. How Submitted:

13.4.1. Classification. Normally unclassified.

13.4.2. Method of Transmission. Voice and record communications when the commander departs. Voice when the commander returns.

13.4.3. Precedence. Routine.

FROM: 45SW PATRICK AFB FL//CP//
ACTION: HQ AFSPC PETERSON AFB CO//DOCP//
APPROPRIATE NAF
INFO: HQ AFSPC PETERSON AFB CO//DO//
UNCLAS
SUBJECT: COMMANDER NON-AVAILABILITY REPORT
A. REASON FOR NON-AVAILABILITY (TDY/LEAVE)
B. DATES OF NON-AVAILABILITY ( 1 SEP 1500Z-4 SEP 2200Z)
C. LOCATION OF LEAVE/TDY AND METHOD OF CONTACT (VANDENBERG AFB, CA -COMMERCIAL (805) 734-1307 DSN: 276-0327
D. REASON FOR TDY, IF APPLICABLE (ATTEND COMMANDERS CONFERENCE)
E. NAME OF SUCCESSOR

Figure 13.1. Commander Non-Availability

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

Launch Processing Milestones

ER/WR DELTA II:

Launch Notification
Booster on Stand (BOS)
Solids Mated
Second Stage Erection
Simulated Flight Test (Sim Flight)
Spacecraft Mate
Payload Fairing Installation
Second Stage Propellant Load
Launch

ER/WR Atlas I/II/IIA/IIAS:

Launch Notification
Booster on Stand (BOS)
Initial Current Profile and Compatibility Test (ICPCT)
Simulated Flight Test (SIM Flight)
West Dress Rehearsal (WDR)
Solids Mated (if applicable)
Spacecraft Mate
Composite Elect. Readiness Test (CERT)
Launch

ER Titan IV (NUS/IUS/Centaur):

Launch Notification
Vertical Integration Building (VIB) Rollout
Upperstage Mate (if applicable)
Baseline Combined Systems Test
Terminal Countdown Demonstration (TCD)
Spacecraft Mate
Payload Fairing Installation
Launch Combined Systems Test (CST)
Launch

WR Titan II

Launch Notification
Booster on Stand (BOS)
Baseline Combined Systems Test
Terminal Countdown Demonstration (TCD)
Spacecraft Mate
Payload Fairing Installation
Launch Combined Systems Test (CST)
Launch

Launch Processing Milestones (cont'd)

WR Titan IV

Launch Notification
1st SRM/SRMU Erection
Baseline Combined Systems Test
Terminal Countdown Demonstration (TCD)
Spacecraft Mate
Payload Fairing Installation
Launch Combined Systems Test (CST)
Launch

ER/WR Pegasus

Combined Systems Test
Spacecraft Mate
Payload Fairing Installation
Booster-Aircraft Mate
Launch

Reportable Launch Processes

Delta 7925 & 7920
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Receive 1st Stage
Receive 2nd Stage
Process PLF
Process Solid Rocket Motors (SRM)
Process GPS Payload
Process Commercial Payload
Process NASA Payload
Upper Stage Processing
Upper Stage/Payload Mate
Inspect and Process 1st Stage
Inspect and Process 2nd Stage
Integrated DMCO
Horizontal Processing Facility (HPF) Processing
Area 55 & HPTF Processing
Erect 1st Stage BOS
Erect & Mate SRMs SRM 3
Erect and Mate 2nd Stage 2nd Stage Erect
Test 1st and 2nd Stages SIMFLT
Final Standalone Testing
PLF Integration
Payload Mate Spacecraft Mate
Integrated Testing and Countdown
Launch
Refurbishment

Reportable Launch Processes (cont'd)

Western Range - Delta
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Receive 1st Stage
Receive 2nd Stage
Inspect and Process 1st Stage
Inspect and Process 2nd Stage
Process PLF
Integrated DMCO
Transport 1st & wnd Stage to VAFB
Receive at VAFB
Process Solid Rocket Motors (SRM)
Process Payload
Upper Stage/Payload Mate
1st Stage HPF Processing
2nd Stage HPF Processing
Erect 1st Stage BOS
Erect & Mate SRMs SRM 3
Erect ISA and 2nd Stage 2nd Stage Mate
Test 1st and 2nd Stages SIMFLT
Final Standalone Testing
Install PLF in MST
3rd Stage/Payload Mate Payload Mate
Integrated Testing and Countdown
Launch
Refurbishment

Atlas I/II/IIA/IIAS
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Receive/Inspect Booster and Centaur
DSCS Payload Prep
Commercial Payload Prep
R&D or other DoD payload Prep and Encapsulation
Payload Encapsulation
Booster erection Erect Atlas
ISA and Centaur Erection Erect Centaur
Stand-alone Testing ICPACT
Launch Operations SIMFLT
WDR WDR
SRM Integration
Spacecraft mate
Integrated Operations CERT
Launch Prep/Countdown
Launch Launch
Refurbishment

Reportable Launch Processes (cont'd)

Titan IV - Centaur, IUS, & NUS
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Engine Installation
Core Erection
Core Processing
SRM Processing
SRM Buildup
SRMU Buildup
Core/SRM (or SRMU)mate
Payload Fairing Prep
Centaur Preparation 1
Centaur Preparation 2
IUS Processing
Centaur Transfer
Payload Processing
Booster Vehicle Integration 1
Upper Stage Mate Centaur/IUS Mate
BV Integration 2 TCD/Baseline CST
Payload mate and Checkout
PLF Assembly and CST Preps Launch CST
Readiness Count
Launch
Pad Refurbishment
Transporter Refurbishment

Reportable Launch Processes (cont'd)

Western Range - Titan IV
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Core Preparations
Process PLF
Receive and Inspect SRMs
Pre-Stack Preparations
Payload Processing
MST Drive System Calibration
Clean Enclosure Configuration
SRM Assembly
Core Erection
BV Checkout
Clean room cleaning and Security Validation
Payload Fairing Lift and Stow
Payload Mate and Checkout
Integrated Checkout
Payload Unique Launch Preparations
Countdown
Launch
Pad Refurbishment

Western Range - Titan II
Process
Milestone at End of Process
Start Date
End Date
# Days not worked on the Process (i.e., weekends, holidays)
Core Preparations
Payload Processing
MST Erection Preparations
Booster Vehicle Erection and Checkout
Payload Mate Preps
Payload Mate
Payload Fairing Lift and Stow
BV and Facility Launch Preps
Payload Checkout
PLF Mate
Final Preparations and Countdown
Launch
Pad Refurbishment

LIST OF ABBREVIATIONS

ADPE Automatic Data Processing Equipment
AFSATCOM Air Force Satellite Communications
AFSCN Air Force Satellite Control Network
AFSPCCC Air Force Space Operations Center
ATRO Actual Time of Return to Operations
CAMS Core Automated Maintenance System
CCAFS Cape Canaveral Air Force Station
CCPDS Command Center Processing and Display System
CCSD Command Communication Service Designator
CCTV Closed Circuit Television
CINCNORAD Commander in Chief NORAD
CMASN Cheyenne Mountain Air Station
CMC Cheyenne Mountain Complex
CNTR Center
COMAFSPC Commander Air Force Space Command
CREDIT CINCNORAD'S Remote Display Information Terminal
CSS Communications Systems Segment
DCS Deputy Chief of Staff
DISA Defense Information System Agency
DMSP Defense Meteorological Satellite Program
DOD Department of Defense
DSI Division Special Interest
DSN Defense Switched Network
DTVE Digital Television Equipment
EPC Early Pentagon Conference
EMI Electro Magnetic Interference
ESR Equipment Status Report
ETRO Estimated Time to Return to Operations
GA Ground Antenna
GPS Global Positioning System
GRC Group Readiness Center
HAMMER ACE Project name for emergency communications support team provided by
HQ AF Communications Agency
HAZCON Hazardous Condition
ICBM Intercontinential Ballistic Missile
ICP Interface Computer Processor
IFP Interface Processor
JCN Job Control Number
JRSC Jam Resistant Secure Communications
JSD Job Status Document
L&I Launch and Impact

LIST OF ABBREVIATIONS (cont)

LRC Logistics Readiness Center
MCCC Mobile Consolidated Command Center
MCS Master Control Station
MEBU Mission Essential Back-up Unit
MICAP Mission Incapable
MLP Multiple Line Phone
MS Monitor Station
MWBP Missile Warning Bypass
OBSS Operational Briefing Support System
OCS Operational Control Segment
OL Operating Location
OPSCAP Operations Capability
OSR OPSCAP/SYSCAP Report
QRP Quick Reaction Package
RCC Resource Control Center
RP Restoration Priority
RTS Remote Tracking Station
SAV Staff Assistance Visit
SCA Satellite Control Authority
SCC Space Control Center
SCP Secure Conferencing Program
SDIN Space Digital Information Network
SIIR Special Interest Item Report
SOC Satellite Operations Center
SPADOC Space Defense Operations Center
ST Subscriber Terminal
STS Space Transportation System (Shuttle)
STU-III Secure Telephone Unit Number III
SYSCAP System Capability
TACAN Tactical Air Navigation
TTY Teletype
TUDE Teletype User Data Entry
TW/AA Tactical Warning and Attack Assessment
USCINCSPACE Commander in Chief of US Space Command
WCP Wing Command Post
WIN WWMCCS Intercomputer Network
WRC Wing Readiness Center
WWMCCS Worldwide Military Command and Control System