BY ORDER OF THE CINC NI10-19
NORTH AMERICAN AEROSPACE DEFENSE COMMAND 12 April 1996
Operations

AEROSPACE REPORTING SYSTEM

"Long Title - Type In All Capital Letters"
This instruction outlines the procedures to report surveillance, tactical action, and supporting information to Commander in Chief, North American Aerospace Defense Command (CINCNORAD) and subordinate NORAD commanders. It applies to all forces and commands under the operational control of CINCNORAD, as well as those organizations tasked to support aircraft on NORAD alert either during day-to-day or increased readiness conditions. Region, sector, and unit commanders are authorized to supplement this instruction. Submit supplements through higher headquarters to HQ NORAD/J3OB for review and CINCNORAD approval. The reporting requirements in this publication are exempt from licensing in accordance with paragraph 2.11.10. of AFI37-124, The Information Collections and Reports Management Program, Controlling Internal, Public, and Interagency Air Force Information Collections. This publication applies to Air National Guard Air Defense units when published in ANGIND2. It does not apply to the Air Force Reserve.

SUMMARY OF REVISIONS
Extensive changes have been made to all chapters. Specifics on cruise missile reporting are detailed in Chapter 5. Chapter 4, Status of Resources and Training Systems (SORTS), Chapter 19, Continental United States Airborne Reconnaissance for Damage Assessment and Chapter 27, Joint Resources Assessment Data Base Report (JADREP) have been deleted.
Page
PART ONE - POLICY, RESPONSIBILITIES, AND PROCEDURES

Chapter 1 - Aerospace Reporting System (ARS)
1.1. Acronyms ................................................................................................................... 8
1.2. The Joint Reporting Structure (JRS) ........................................................................... 8
1.3. Service Reports .......................................................................................................... 8
1.4. The Aerospace Reporting System (ARS) .................................................................... 8
1.5. Reporting Authority ..................................................................................................... 9
1.6. Report Categories ...................................................................................................... 9
1.7. Communications Security (COMSEC) ........................................................................ 9

Chapter 2 - Responsibilities
2.1. General ..................................................................................................................... 9
2.2. Chief, Battle Management Operations Branch (J3OB) ............................................... 9
2.3. Staff Agencies ........................................................................................................... 9
2.4. NORAD Regions ....................................................................................................... 10

Chapter 3 - ARS Format and Changes

3.1. General ..................................................................................................................... 11
3.2. Standard Report Description Format .......................................................................... 11
3.3. Changes .................................................................................................................... 11

_______________
Supersedes: NR55-1, 14 Jan 91
No. of Printed Pages: 69
OPR: J30B (Major Trevor Kennedy)
Certified by: Major-General D. Fraser Holman, CF
Distribution: FX (See page 55.)
Page

3.4. Report Transmission ................................................................................................. 11
3.5. Use of Address Indicating Groups (AIG) .................................................................... 11
3.6. Reporting in a Degraded Environment ....................................................................... 11

PART TWO - OPERATIONAL STATUS REPORTS

Chapter 4 - Commander's Operational Report (OPREP)
4.1. Purpose ..................................................................................................................... 13
4.2. Submitted By ............................................................................................................. 13
4.3. Submitted To ............................................................................................................. 13
4.4. When Submitted.......................................................................................................... 14
4.5. How Submitted .......................................................................................................... 14
4.6. Report Indicator ......................................................................................................... 14
4.7. Specific Reporting Instructions .................................................................................. 14
4.8. Report Content .......................................................................................................... 14
4.9. Sample Report .......................................................................................................... 14
4.10. Headquarters Functional Manager ............................................................................. 14

Chapter 5 - Event or Incident Reports (OPREP-3)
5.1. Purpose ..................................................................................................................... 14
5.2. Submit By.................................................................................................................... 15
5.3. When Submitted..... ................................................................................................... 15
5.4. How Submitted .......................................................................................................... 15
5.5. Report Indicator ........................................................................................................ 17
5.6. Specific Reporting Instructions.................................................................................... 17
5.7. Report Content........................................................................................................... 17
5.8. Sample Report........................................................................................................... 17

Chapter 6 - Track Reporting
6.1. Purpose ..................................................................................................................... 18
6.2. Tracks Reported ........................................................................................................ 18
6.3. Reported By .............................................................................................................. 19
6.4. Reported To .............................................................................................................. 19
6.5. How Reported ............................................................................................................ 19
6.6. When Reported ......................................................................................................... 23

Chapter 7 - Radar Outage Report
7.1. Purpose ..................................................................................................................... 26
7.2. Submitted By ............................................................................................................. 26
7.3. Submitted To ............................................................................................................. 26
7.4. When Submitted ........................................................................................................ 26
7.5. How Submitted .......................................................................................................... 27
7.6. Report Indicator ......................................................................................................... 27
7.7. Specific Reporting Instructions .................................................................................. 27
7.8. Report Content .......................................................................................................... 27
7.9. Headquarters Functional Manager ............................................................................. 27

Page

Chapter 8 - Mandatory Scramble Report
8.1. Purpose .................................................................................................................... 28
8.2. Submitted By ............................................................................................................. 28
8.3. Submitted To ............................................................................................................. 28
8.4. When Submitted ........................................................................................................ 28
8.5. How Submitted .......................................................................................................... 28
8.6. Report Indicator ......................................................................................................... 28
8.7. Specific Reporting Instructions .................................................................................. 28
8.8. Report Content .......................................................................................................... 28
8.9 Headquarters Functional Manager ............................................................................. 29

Chapter 9 - Command and Control Identifiers (CCI) Report
9.1. Purpose ..................................................................................................................... 29
9.2. Submitted By............................................................................................................... 29
9.3. Submitted To ............................................................................................................. 29
9.4. When Submitted ........................................................................................................ 29
9.5. How Submitted .......................................................................................................... 29
9.6. Report Indicator ......................................................................................................... 29
9.7. Specific Reporting Instructions .................................................................................. 29
9.8. Report Content .......................................................................................................... 31
9.9. Sample Report .......................................................................................................... 31
9.10. Headquarters Functional Manager ............................................................................. 31

Chapter 10 - Computer Outage Report
10.1. Purpose ..................................................................................................................... 31
10.2. Submitted By ............................................................................................................. 31
10.3. Submitted To ............................................................................................................. 31
10.4. When Submitted......................................................................................................... 31
10.5. How Submitted .......................................................................................................... 31
10.6. Report Indicator ......................................................................................................... 32
10.7. Specific Reporting Instructions .................................................................................. 32
10.8. Report Content .......................................................................................................... 32
10.9. Sample Report for RAOC or SAOC Outage ............................................................... 32
10.10. Sample Report for Return to Operation ...................................................................... 32
10.11. Headquarters Functional Manager ............................................................................ 32

Chapter 11 - Fighter Status Report
11.1. Purpose ..................................................................................................................... 33
11.2. Submitted By ............................................................................................................. 33
11.3. Submitted To ............................................................................................................. 33
11.4. When Submitted ........................................................................................................ 33
11.5. How Submitted .......................................................................................................... 33
11.6. Report Indicator ......................................................................................................... 34
11.7. Specific Reporting Instructions .................................................................................. 34
11.8 Headquarters Functional Manager ............................................................................. 34

Chapter 12 - E-3 Status Report (AWACS)
12.1. Purpose ..................................................................................................................... 34
12.2. Submitted By ............................................................................................................. 34
12.3. Submitted To ............................................................................................................. 34
12.4. When Submitted ........................................................................................................ 34
12.5. How Submitted .......................................................................................................... 34
12.6 Specific Reporting Instructions ................................................................................... 35
 
 
Page
12.7. Report Content .......................................................................................................... 35
12.8 Sample Report .......................................................................................................... 35
12.9. Headquarters Functional Manager ........................................................................... 35

Chapter 13 - Weapons Readiness Deviation Report
13.1. Purpose ..................................................................................................................... 36
13.2. Submitted By ............................................................................................................. 36
13.3. Submitted To ............................................................................................................. 36
13.4. When Submitted ........................................................................................................ 36
13.5. How Submitted .......................................................................................................... 36
13.6. Report Indicator ......................................................................................................... 36
13.7. Specific Reporting Instructions .................................................................................. 36
13.8. Report Content .......................................................................................................... 36
13.9. Sample Report .......................................................................................................... 37
13.10. Headquarters Functional Manager ............................................................................. 37

Chapter 14 - Aircrew and Aircraft Loss Report (LOSREP)
14.1. Purpose ..................................................................................................................... 37
14.2. Submitted By ............................................................................................................. 37
14.3. Submitted To ............................................................................................................. 37
14.4. When Submitted ........................................................................................................ 37
14.5. How Submitted .......................................................................................................... 38
14.6. Report Indicator ......................................................................................................... 38
14.7. Specific Reporting Instructions .................................................................................. 38
14.8. Report Content .......................................................................................................... 38
14.9. Sample Report .......................................................................................................... 39
14.10. Headquarters Functional Manager ............................................................................. 39

Chapter 15 - NORAD Region Situation Reporting
Section A - General
15.1. Purpose ..................................................................................................................... 39

Section B - Commander's SITREP
15.2. Purpose ..................................................................................................................... 39
15.3. Submitted By ............................................................................................................. 39
15.4. Submitted To ............................................................................................................. 39
15.5. When Submitted ....................................................................................................... 39
15.6. How Submitted .......................................................................................................... 39
15.7. Specific Reporting Instructions .................................................................................. 40
15.8. Report Content .......................................................................................................... 40
15.9. Sample Report .......................................................................................................... 41

Section C - Quick Look Capability Index (QLCI)
15.10. Purpose....................................................................................................................... 41
15.11. Submitted By ............................................................................................................. 42
15.12. Submitted To ............................................................................................................. 43
15.13. When Submitted ........................................................................................................ 43
15.14. How Submitted .......................................................................................................... 43
15.15. Report Indicator ......................................................................................................... 43
15.16. Specific Reporting Instructions .................................................................................. 43
15.17. Report Content .......................................................................................................... 43
15.18. Sample Report .......................................................................................................... 44
15.19. Headquarters Functional Manager ............................................................................. 44

Page
Chapter 16 - Nuclear Detonation Report (NUDET)
16.1. Purpose ..................................................................................................................... 45
16.2. Submitted By ............................................................................................................. 45
16.3. Submitted To ............................................................................................................. 45
16.4. When Submitted ........................................................................................................ 45
16.5. How Submitted .......................................................................................................... 45
16.6. Report Indicator ......................................................................................................... 46
16.7. Specific Reporting Instructions .................................................................................. 46
16.8. Report Content .......................................................................................................... 46
16.9. Sample Report .......................................................................................................... 46
16.10. Headquarters Functional Manager............................................................................... 46

Chapter 17 - Environmental Hazard Report
17.1. Purpose ..................................................................................................................... 46
17.2. Submitted By ............................................................................................................. 46
17.3. Submitted To ............................................................................................................. 46
17.4. When Submitted ........................................................................................................ 46
17.5. How Submitted .......................................................................................................... 46
17.6. Report Indicator ......................................................................................................... 47
17.7. Specific Reporting Instructions .................................................................................. 47
17.8. Report Content .......................................................................................................... 47
17.9. Sample Report .......................................................................................................... 47
17.10. Headquarters Functional Manager ............................................................................. 47

Chapter 18 - Pilot Observation Reports of Post-Attack
18.1. Purpose ..................................................................................................................... 47
18.2. Submitted By ............................................................................................................. 47
18.3. Submitted To ............................................................................................................. 48
18.4. When Submitted ........................................................................................................ 48
18.5. How Submitted .......................................................................................................... 48
18.6. Report Indicator ......................................................................................................... 48
18.7. Specific Reporting Instructions .................................................................................. 48
18.8. Report Content .......................................................................................................... 48
18.9. Sample Report .......................................................................................................... 48
18.10. Headquarters Functional Manager ............................................................................. 48

Chapter 19 - Electronic Countermeasures Status Reports Electronic Countermeasures Tactical
Action Report (ECTAR) and Electronic Countermeasures Summary Report (ECSUM)
19.1. Purpose....................................................................................................................... 49
19.2. Submitted By .............................................................................................................. 49
19.3. Submitted To............................................................................................................... 49
19.4. When Submitted.......................................................................................................... 49
19.5. How Submitted............................................................................................................ 50
19.6. Report Indicator........................................................................................................... 50
19.7. Specific Reporting Instructions.................................................................................... 50
19.8. Report Content............................................................................................................ 50
19.9. Sample Report............................................................................................................ 51
19.10. Headquarters Functional Manager............................................................................... 51

Chapter 20 - Logistics Status Report (LOGSTAT)
20.1. Purpose ..................................................................................................................... 51
20.2. Submitted By ............................................................................................................. 51
20.3. Submitted To ............................................................................................................. 51
 
 
20.4. When Submitted ........................................................................................................ 51
20.5. How Submitted .......................................................................................................... 51
20.6. Report Indicator ......................................................................................................... 51
20.7. Specific Reporting Instructions .................................................................................. 51
20.8. Report Content .......................................................................................................... 51
20.9. Sample Report .......................................................................................................... 51
20.10. Headquarters Functional Manager ............................................................................. 51

PART THREE - SITUATION MONITORING

Chapter 21 - Intelligence Report (INTREP)
21.1. Purpose ..................................................................................................................... 52
21.2. Submitted By ............................................................................................................. 52
21.3. Submitted To ............................................................................................................. 52
21.4. When Submitted ........................................................................................................ 52
21.5. How Submitted .......................................................................................................... 52
21.6. Report indicator ......................................................................................................... 53
21.7. Specific Reporting Instructions ................................................................................... 53
21.8. Report Content ......................................................................................................... 53
21.9. Headquarters Functional Manager ............................................................................. 53

Chapter 22 - Daily Intelligence Summary (DISUM)
22.1. Purpose ..................................................................................................................... 53
22.2. Submitted By ............................................................................................................. 53
22.3. Submitted To ............................................................................................................. 53
22.4. When Submitted ....................................................................................................... 53
22.5. How Submitted .......................................................................................................... 54
22.6. Report Indicator ......................................................................................................... 54
22.8. Report Content .......................................................................................................... 54
22.9. Headquarters Functional Manager ............................................................................. 54

Chapter 23 - Reporting Vital Intelligence Sightings (CIRVIS)
23.1. Purpose ..................................................................................................................... 54
23.2. Submitted By ............................................................................................................. 54
23.3. Submitted To ............................................................................................................. 54
23.4. When Submitted ........................................................................................................ 54
23.5. How Submitted .......................................................................................................... 55
23.6. Report Indicator ......................................................................................................... 55
23.7. Specific Reporting Instructions .................................................................................. 55

23.8. Report Content ........................................................................................................... 55
23.9. Headquarters Functional Manager ............................................................................. 55

Chapter 24 - Critical Intelligence Report (CRITIC)
24.1. Purpose ..................................................................................................................... 55
24.2. Submitted By ............................................................................................................. 56
24.3. Submitted To ............................................................................................................. 56
24.4. When Submitted ........................................................................................................ 56
24.5. How Submitted .......................................................................................................... 56
24.6. Report Indicator ......................................................................................................... 56
24.7. Specific Reporting Instructions .................................................................................. 56
24.8. Report Content .......................................................................................................... 56
24.9. Headquarters Functional Manager ............................................................................. 56

Page
Figures
2.1. HQ NORAD's Functional Managers ........................................................................... 10
3.1. Standard Report Description Format .......................................................................... 11
5.1. Example of OPREP-3 Voice Template ...................................................................... 17
5.2. Example of OPREP-3 Cruise Missile Voice Template ................................................ 18
6.1. Example of NORAD Form 61, NORAD Track Report ................................................ 24
15.1. Example of a SITREP ............................................................................................... 41

Attachments
1. Acronyms .................................................................................................................. 57
2. Standard Codes - Designators and Identifiers ............................................................ 60
3. Track and Source Designators ................................................................................... 61
4. Message- Formats - Forward Tell .............................................................................. 64
5. Message Formats - Voice Tell ................................................................................... 65
6. Personnel Reporting - SITREP .................................................................................. 68

PART ONE

POLICY, RESPONSIBILITIES, AND PROCEDURES

Chapter 1

AEROSPACE REPORTING SYSTEM (ARS)

1.1. Acronyms. See attachment 1.

1.2. The Joint Reporting Structure (JRS). See USMTF Message Formats (CD ROM) JIEOH 9000, for reporting requirements. The Joint Chiefs of Staff (JCS) established the JRS to provide:

1.2.1. The information requirements of the National Command Authorities (NCA) and their supporting staffs.

1.2.2. A systematic approach for establishing, reviewing, and monitoring report requirements.

1.2.3. A set of standards to help data processing and display. Report information through this system that directly relates to the planning, execution, and analysis of military operations. The system includes all major areas of military operations required to support decision-making at the national level.

1.3. Service Reports. The Service Chiefs establish Service-unique report requirements in addition to the information required by JCS. The Chief Of Staff Air Force (CSAF) requirements are in AFM 10-206. Canadian Forces requirements are in HQDP 100. Since information reported through the Service systems falls within the general parameters in paragraph 1.3 (that is, planning, execution, and analysis), they are considered an integral part of the JRS. JRS standards are used in the Service systems, laterally and vertically. If a JCS report also meets the information requirements of a Service Chief, a dual address to JCS and the Service Headquarters is used instead of separate reports.

1.4. The Aerospace Reporting System (ARS):

1.4.1. JCS has tasked CINCNORAD, in support of the JRS, to develop a single reporting structure to provide information on the conduct of aerospace defense operations. Additionally, the Terms of Reference (TOR) for CINCNORAD, 27 October 1993, gives requirements for binational information flow. The ARS is the primary vehicle for NORAD support of the JRS, Canadian National Defense Headquarters (NDHQ) requirements, and CINCNORAD TOR. The ARS also includes other reports required by NORAD commanders at all levels to enhance the planning, directing, coordinating, and controlling of assigned forces. Maximum interface of the JRS and ARS is achieved by aligning NORAD procedures and reports with the JRS. Therefore, all record reports will be accomplished according to United States Message Text Format (USMTF).

1.4.2. Units assigned and supporting OPLAN 3110-95, OPLAN 3200-95 or CONPLAN 3310 submit reports using procedures and addressees in this instruction during actual or exercise defense readiness conditions (DEFCON). If required, recipients consolidate inputs from subordinate units and send to higher headquarters. Exception: OPREP-3 BEELINE and PINNACLE reports are not consolidated. Deployed NORAD units, which rely on host base units to submit reports, will ensure NORAD reporting requirements in this instruction are met. Augmentation forces follow procedures in this instruction during actual or exercise defense readiness conditions (DEFCON).

1.4.3. It is also directive in nature on NORAD Canadian Forces (CF) units for those matters that have a direct bearing on NORAD operational capabilities. In all other matters, NORAD CF units comply with appropriate CF directives.

1.4.4. When voice reports are submitted to NORAD, give the report title to the individual receiving the report before relaying the text.

1.5. Reporting Authority. DOD Directive 5000.19; and AFIs 10-206 and 37-124 give the authority for JCS and Service information requirements. CINCNORAD TOR gives the authority for NORAD requirements.

1.6. Report Categories. Information sent through the ARS, as in the JRS, is divided into two categories:

1.6.1. Operations Reports. These reports provide information on NORAD Operations and operational units. They include information about the planning, initiation, termination, and results of aerospace defense operations, significant incidents and events, or operational situations. These reports enable NORAD commanders at all levels to determine their readiness capability and to determine an appropriate response to a significant incident.

1.6.2. Situation Monitoring Reports. These reports provide essential intelligence information to NORAD commanders to help them evaluate the known or potential enemy tactical or strategic courses of action.

1.7. Communications Security (COMSEC). Classified encrypted reports are subject to compromise when attempts are made to clarify the report with unsecure telephone conversations. Do not attempt to "talk around" classified information when using unsecure means. Do not elaborate when discussing UNCLASSIFIED (but sensitive) information when using unsecure means. Consideration should be given to sending unclassified reports messages Encrypt For Transmission Only (EFTO).

Chapter 2

RESPONSIBILITIES

2.1. General. This chapter prescribes NORAD staff responsibilities in support of the JRS, ARS, and Canadian reports requirements.

2.2. Chief, Battle Management Operations Branch (J3OB):

2.2.1. Manages the ARS.

2.2.2. Monitors JRS report requirements and recommends changes to the JRS for JCS approval.

2.2.3. Coordinates report structure to the JRS and ARS per DOD Directive 5000.19 and AFI37-124.

2.2.4. Coordinates changes to the ARS (see Chapter 3) and the Canadian reports requirements.

2.2.5. Coordinates reports included in the ARS (see Chapter 3).

2.3. Staff Agencies. A functional manager has been assigned for each report. (See figure 2.1). Each functional manager:

2.3.1. Determines requirements for information which support the broad guidelines in Chapter 1.

2.3.2. Reviews existing JRS, ARS, and Canadian reports to decide if the information is readily available at this Headquarters or from other sources.

2.3.3. Develops procedures for collecting, analyzing, and maintaining information at this Headquarters, including the forwarding of data required by JCS, NDHQ, Air Command, and the US Service Chiefs.

2.3.4. Monitors the effectiveness of JRS and ARS reports to meet JCS and NORAD requirements.

2.3.5. Processes new report requirements or recommendations for changes.

2.4. NORAD Regions:

2.4.1. May develop detailed procedures (as supplements) to ensure reports are submitted promptly. Procedures must include compiling and forwarding reports from subordinate and field units (such as sector operations control centers (SAOC), long range radars (LRR), fighter units, and so on).

2.4.2. Monitor report effectiveness and make recommendations for improvements to the HQ NORAD report functional managers.

CHAPTERTITLEOPR

1. ARS N/J3O
2. Responsibilities N/J3O
3. ARS Format and N/J3O
Changes
4. OPREP CMOC/J3O
5.1. - 5.6. Event or Incident CMOC/J3IC
Reps (OPREP-3)
5.7. HELPING HAND and CMOC/J3IC
COVERED WAGON Reps
6.1. Track Reps CMOC/J3OA
6.2. Unknown Track Reps CMOC/J3OA
6.5. Special 17 Reps CMOC/J3OA
7. Radar Outage Reps N/J3W
8. Mandatory Scramble Reps N/J3O
9. Region CCI Reps N/J3W
10. Computer Outages N/J3W
11. Fighter Status Reps N/J3O
12. E-3 Status Reps N/J3O
13. Weapons Readiness N/J3O
Deviation Reps
14. LOSREP N/J3O
15.1. SITREP N/J3O
15.C. QLCI N/J3O
15.D. Attainment Reportin N/J3O
16. NUDET N/J3O
17. Environmental Hazard Rep N/J3O
18. GLASSEYE N/J3O
19. CARDA N/J3O
20. ECTAR and ECSUM CMOC/J3O
21. LOGSTAT N/SPJ4
22. INTREP N/J2FW
23. DISUM N/J2FW
24. CIRVIS N/J2FW
25. CRITIC N/J2FW
Figure 2.1. HQ NORAD's Functional Managers

Chapter 3

ARS FORMAT AND CHANGES

3.1. General. This chapter provides a summary of reporting instructions, and prescribes the format to be used for each required report. This chapter also prescribes the manner in which reports may be changed.

3.2. Standard Report Description Format. See figure 3.1.

3.3. Changes. Changes to the ARS include additions of new reporting policies, procedures, instructions, requirements, data elements, and revisions to existing reports. Before initiating a change proposal, review the ARS to determine if existing reports can provide the required information. The headquarters functional manager for the report provides this information (see figure 2.1). If the information is not available, send a change proposal to the appropriate HQ NORAD functional manager. The functional manager is responsible for staffing, obtaining necessary approvals, and proposing interim changes to HQ NORAD, Chief, Battle Management Operations (N/J3OB).

3.4. Report Transmission. Send reports either by courier, mail, forward tell, electronical record communications (TTY, AUTODIN, or FAX), Global Command and Control System (GCCS), or send secure/nonsecure voice reports using the Defense Switching Network (DSN), NORAD Tactical AUTOVON System (NTAS), or commercial phone system.

3.5. Use of Address Indicating Groups (AIG). Use AIGs with the ARS.

3.6. Reporting in a Degraded Environment:

3.6.1. When any alternate command post or operations center is manned and operational, they should be included in the flow of information.

3.6.2. When communications are degraded or saturated, the sending agency must prioritize reporting requirements to ensure that essential reports are submitted.

REPORT TITLE
SHORT TITLE
(ACRONYM)

Paragraph Heading Content

1. Purpose Gives a brief description of the purpose of the report. Indicates implementing authority and reference for the report.

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

3. Submitted To Indicates the agencies and organizations to
which the report is made. Divides section
into action and information addressees, as
required.

4. When Submitted Indicates when 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.

b. Primary and alternate method of transmission
(Automatic Digital Network (AUTODIN), Teletype (TTY), telephone, and so forth).

c. Precedence (FLASH, IMMMEDIATE, PRIORITY or ROUTINE).

d. Whether the report is submitted if MINIMIZE is in effect. If MINIMIZE is in effect state that MINIMIZE has been considered.

6. Report Indicator Shows the approved and assigned NORAD RCS or higher authority.

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

8. Report Content Indicates the format of fixed entries
required in the report. Indicates the field
if information which specifically denotes
JRS information requirements. If a narrative
format is used, discuss the information to
be covered. If automated, data formats are
included.

9. Sample Report Provides sample reports where possible for
reference. Addressees may be omitted (see
"Submitted By" and "Submitted To" above).
Where message formats from USMTF are
specified, refer to JCS Pub-25, volume II, for message formats. Otherwise use the reports as specified in this instruction.

10. Headquarters Functional Self-explanatory
Manager
Figure 3.1. Standard Report Description Format.

PART TWO

OPERATIONAL STATUS REPORTS

Chapter 4

COMMANDER'S OPERATIONAL REPORT (OPREP)

4.1. Purpose. The Commander's Operational Report (OPREP) provides all echelons of command with essential information on the planning, initiation, termination, and results of military operations. Additionally, the system provides for the reporting of any event or incident which may attract national level interest, whether or not it is related to possible military involvement.

4.1.1. The OPREP consists of:

4.1.1.1. Operations Planning Report (OPREP-1).

4.1.1.2. Operations Start Report (OPREP-2).

4.1.1.3. Event or Incident Report (OPREP-3). OPREP-3 is considered a special and separate report and is discussed in chapter 5 in detail. All references to the OPREP system in the remainder of this chapter refer to OPREPs 1, 2, 4, and 5.

4.1.1.4. Operations Stop and Results Report (OPREP-4).

4.1.1.5. Operations Summary Report (OPREP-5).

4.1.2. OPREP reports are prepared when required and normally support JCS Publication 6, volume II, part 2, chapter 3. OPREP-1 is used to describe planned operations for specific situations. NORAD reports are used as feeder reports to the OPREP-1 to include:

4.1.2.1. Fighter Status Report (see chapter 11).

4.1.2.2. E-3 Status Report (see chapter 12).

Note: If JCS, CSAF, or NDHQ requires a report of forces on a specific type of operation, use OPREP-1 to transmit the information.

4.1.3. OPREP-2 reports are start reports and there are no NORAD reports which could feed this report on a regular basis.

4.1.4. OPREP-4 reports advise of completion of an operation or phase and the results or estimated results. This could apply to intercept results or an operations plan if JCS required the information. No specific NORAD reports are scheduled to feed the OPREP-4.

4.1.5. OPREP-5 reports provide summarized data and are used only as required. The reports listed under OPREP-1 could also be used to formulate OPREP-5.

4.2. Submitted By. All NORAD units. It applies to Canadian Forces (CF) units for those matters that have a direct bearing on NORAD operational capabilities. In all other matters, NORAD CF units comply with appropriate CF directives.

4.3. Submitted To. See USMTF Message Formats JIEOH 9000; AFM 10-206; and Chapter 5 of this instruction.

4.4. When Submitted. Submit when directed by JCS.

4.5. How Submitted:

4.5.1. Classification. Determined by report content.

4.5.2. Method of Transmission:

4.5.2.1. Primary. AUTODIN.

4.5.2.2. Alternate. DSN or NTAS (voice).

4.5.3. Precedence. PRIORITY or higher depending on content.

4.5.4. MINIMIZE. Consider the implementing directive for this report.

4.6. Report Indicator. OP.

4.7. Specific Reporting Instructions. See MIL STAND 60-40 (USMTF).

4.8. Report Content. See MIL STAND 60-40 (USMTF).

4.9. Sample Report. N/A.

4.10. Headquarters Functional Manager. HQ NORAD, Chief, Battle Management Operations Branch (N/J3OB).

Chapter 5

EVENT OR INCIDENT REPORTS (OPREP-3)

5.1. Purpose. The OPREP-3 is the single vehicle within the JRS and ARS for the joint reporting of events or incidents to the National Military Command Center (NMCC) and the Canadian National Defense Headquarters (NDHQ). OPREP-3 reports use command and control channels to notify commanders immediately of any event or incident which may attract international, national, US Air Force, or significant news media interest. The report is established to provide time-sensitive information on which to base an appropriate response to any significant event or incident that has occurred or is in progress. OPREPs do not replace the requirement for more detailed reports such as the Commander's Situation Report (SITREP), and accident or incident investigation reports. Submitting an OPREP-3 report neither changes, nor substitutes for, any report required by other directives.

5.1.1. OPREP-3 reports categorize events or incidents according to their nature. Flagwords associated with each category aid prompt transmission, processing, and distribution of the reports by alerting people to their importance. The following common flagwords are extracted from AFMAN10-206 :

5.1.1.1. PINNACLE (OPREP-3P). This report provides information to the National Command Authorities, NMCC, and appropriate commanders on any incident or event of national level interest which does not require notification using other OPREP-3 reports. Submit an OPREP-3 PINNACLE report if there is any doubt an event or incident is, or could be, of interest to White House, Department of Defense (DOD), the Joint Staff, or news media.

5.1.1.2. PINNACLE NUCFLASH (OPREP-3PNF). This reports the actual or possible detonation of a US nuclear weapon which may cause the outbreak of a nuclear war. This report has the highest precedence in the OPREP-3 reporting structure.

5.1.1.3. PINNACLE FRONT BURNER (OPREP-3PFB). This reports any attack on North America or harassment of NORAD forces. For cruise missile reports (figure 5.2), include the following information:

-- Unit/aircraft detecting: Unit/aircraft name
-- Type and number as: (number) ALCM, SLCM, or ASM
-- Location: Lat / Long
-- Altitude: Low / Med / High
-- Heading: Degrees
-- Engagement Status: (if engaged, provide results in follow-up reports)

5.1.1.4. PINNACLE BROKEN ARROW (OPREP-3PBA). This reports an accidental event involving nuclear weapons or nuclear components but does not create a risk of nuclear war.

5.1.1.5. BEELINE (OPREP-3B). This report provides information on any incident or event where US Air Force level interest is indicated but not requiring an OPREP-3 PINNACLE report. Although the report normally remains within US Air Force channels, commanders may add other addressees, as appropriate, to avoid duplicate reporting. HQ USAF may make BEELINE information available to agencies outside the Air Force (e.g. NMCC, State Dept.) based on the situation.

5.1.1.6. BENT SPEAR (OPREP-3BS), and FADED GIANT (OPREP-3FG). These are service requirements which are reported through service chains of command.

5.1.1.7. HOMELINE (OPREP-3H). This report provides information on any incident or event with MAJCOM level interest indicated but not requiring OPREP-3 Pinnacle or Beeline reporting. Regions may identify Homeline reporting requirements in their supplements.

5.2. Submitted By. The lowest level of command having knowledge of an event or incident submits the OPREP-3 report (see paragraph 1.5.2.).

Note: When in doubt, report it!

5.3. When Submitted. OPREP-3 Reports Matrix (AFMAN 10-206 Part 2, Chapter 3) outlines OPREP-3 PINNACLE and BEELINE events/incidents. OPREP-3 Homelines events are identified by Regions. Continue to report OPREPs during MINIMIZE.

5.4. How Submitted:

5.4.1. Voice Reports. Rapid reporting is imperative. Do not delay an initial report for lack of information. Use follow-up reports for additional information when it becomes available. Due to the extremely time sensitive nature of the PINNACLE NUCFLASH report, transmit these voice reports no later than 5 minutes after learning of the event. Transmit OPREP-3 reports by the fastest means available consistent with security constraints (e.g.: the NORAD Alerting System, or a nonsecure voice transmission) followed by a confirming record transmission. Transmit reports containing classified or special intelligence information with the proper security precautions. Include the flagword JOPREP JIFFY after the classification on all OPREP-3 messages.

5.4.1.1. Regions will outlline procedures for conducting voice reporting.

5.4.1.2. Submit voice reports using figure 5.1 directly to the Air Force Operations Support Center (AFOSC) through the NORAD Command Center. AFOSC will ensure NMCC, or the Canadian National Defence Operations Center (NDOC), receives the appropriate information. Following telephone numbers are listed for reference to conduct OPREP reporting:

NORAD Command Center:
DSN 268-4581/4582/4583
STU-III 268-3351/3487
COMMERCIAL (719) 474-4500/4581

Air Force Operations Support Center:
DSN 227-6103, 225-2270
STU-III DSN 227-6784, 224-6759
COMMERCIAL (703) 697-6103, (703) 697-6784

NDOC:
NTAS (PRIMARY): (310) 261-2880
DSN: 627-8011

NMCC:
DSN: 851-3840/1911

5.4.2. Record Copy Reports. Record copy reports must be transmitted within 1 hour of initial voice report.

5.4.2.1. Use USMTF User formats (Pinnacle Annex) for OPREP-3 reports.

5.4.2.2. Addressees: In addition to the action addresses listed in AFMAN 10-206, table 3.1, include the following addresses as applicable:

Pinnacle:
NDOC OTTAWA ON CN//J3 OPS//
CMOC CHEYENNE MOUNTAIN AS CO//CC/J3O/CD/EA//
CONR TYNDALL AFB FL//ADD/EA// (for CONR units ONLY)
FGCANR HQ NORTH BAY ON CN//EA TEAM/DO// (for CANR units ONLY)
21 SQN NORTH BAY ON CN//SD// (for CANR units ONLY)
ANR ELMENDORF AFB AK//ADC/DOC// (for ANR units ONLY)
ANR RAOC ELMENDORF AFB AK//SD// (for ANR units ONLY)
NEADS ROME NY//DOC/SD// (for NEADS and CONR units ONLY)
WADS MCCHORD AFB WA//DOC/SD// (for WADS and CONR units ONLY)
SEADS TYNDALL AFB FL//DOC/SD// (for SEADS and CONR units ONLY)

Beeline and Homeline:

CMOC CHEYENNE MOUNTAIN AS CO//CC/J3O/EA//
CONR TYNDALL AFB FL//ADD/EA// (for CONR units ONLY)
FGCANR HQ NORTH BAY ON CN//EA TEAM/DO// (for CANR units ONLY)
21 SQN NORTH BAY ON CN//SD// (for CANR units ONLY)
ANR ELMENDORF AFB AK//ADC/DOC// (for ANR units ONLY)
ANR RAOC ELMENDORF AFB AK//SD// (for ANR units ONLY)
NEADS ROME NY//DOC/SD// (for NEADS and CONR units ONLY)
WADS MCCHORD AFB WA//DOC/SD// (for WADS and CONR units ONLY)
SEADS TYNDALL AFB FL//DOC/SD// (for SEADS and CONR units ONLY)

Note: ANG/Air Defence units will include ANGARC GDSS Anbrews AFB MD//XOOSO// on all reports.

5.4.3. Report Numbering. Number OPREP-3 reports consecutively, regardless of category, for the calendar year beginning with 001. Subsequent reports for the same incident will add sequential letters to the basic report number (e.g. 002A, 002B). After the number 999, revert to 001 for the next report.

5.4.4. Exercise Reports. Number exercise reports independently of "real world" reports using the same OPREP-3 formats. Begin exercise reports with 001 at the start of each exercise

5.4.5. Follow up Reports. Follow-up reports are essential to keep commanders informed of developing situations and to provide additional details as they are learned. Use follow-up reports as long as the immediacy of the situation warrants. When this timeliness is no longer required, SITREP reporting may be initiated provided the follow-up information is not being submitted in another report.

5.5. Report Indicator. N/A

5.6. Specific Reporting Instructions. See MIL STAND 60-40 (USMTF).

5.7. Report Content. See MIL STAND 60-40 (USMTF).

5.8. Sample Report. See MESSAGE MAP for USMTF format.

OPREP-3 VOICE TEMPLATE

THIS IS WITH A/AN

(ADDRESSEE) (ORIGINATOR)

FLASH IMMEDIATE PRIORITY ROUTINE

TOP SECRET SECRET CONFIDENTIAL UNCLASSIFIED

OPREP-3 REPORT.
(PINNACLE, PINNACLE FRONT BURNER, BEELINE, HOMELINE, ETC)

LINE 1 / SERIAL NUMBER

LINE 2 / INCIDENT

LINE 3 / NARRATIVE

LINE 4 / TIME OF REPORT (ZULU)

LINE 5 / AUTHENTICATION

Figure 5.1. Example of OPREP-3 VOICE TEMPLATE

OPREP-3 VOICE TEMPLATE

THIS IS WITH A/AN

(ADDRESSEE) (ORIGINATOR)

FLASH IMMEDIATE PRIORITY ROUTINE

TOP SECRET SECRET CONFIDENTIAL UNCLASSIFIED

OPREP-3 PINNACLE FRONT BURNER REPORT.
(PINNACLE, PINNACLE FRONT BURNER, BEELINE, HOMELINE, ETC)

LINE 1 / SERIAL NUMBER

LINE 2 / INCIDENT ALCM/SLCM SIGHTING 1700Z

LINE 3 / NARRATIVE 425 SQN / 2 CF-18S / SINGLE ALCM SIGHTED/

50 00 00 N / 60 00 00 W / LOW / HDG 225 / LOST VISUAL CONTACT AFTER

15 MINUTES

LINE 4 / TIME OF REPORT (ZULU)

LINE 5 / AUTHENTICATION

Figure 5.2. Example of OPREP-3 Cruise Missile Voice Template.

Chapter 6

TRACK REPORTING

6.1. Purpose. Track reporting provides significant air activity information to the NMCC and CINCNORAD through the NORAD Air Defense Operations Center (ADOC). The information is essential for the proper execution of NORAD's mission of warning and attack assessment, air sovereignty and air defense. In addition, the information is used for operational and intelligence analysis, as well as being up-channeled to appropriate agencies. Accurate and expeditious reporting is essential.

6.2. Tracks Reported. RAOC/SAOC file reports on reportable tracks within their AOR. Reportable tracks are Unknown, Special, Hostile/Faker, and any track believed to be a possible threat, regardless of classification. SAOCs will file reports on tracks detected by E-3, OTHR systems, or sensors under another non-NORAD agency control (e.g. JAITF-W) when the track enters the SAOC's AOR.

Note: Information on any military combat aircraft tracks belonging to a country of interest (as defined in NR 55-24) within or approaching the ADIZ will be dealt with IAW special ID procedures outlined in NI10-15. Furthermore, all potential and verified foreign combat capable aircraft tracks anywhere in the vicinity of the Cuban landmass will be forward told to the ADOC regardless of heading. All available amplifying data must be voice forwarded as rapidly as it becomes available to ensure the ADOC receives the most current information.

6.2.1 Additional guidance for Hostile, Faker, and Special 21 track reporting. If the track begins as an Unknown or Special 21 and becomes a Hostile/Faker, clarify what made the aircraft a Hostile/Faker and continue to pass track information to the ADOC as requested.

6.2.2. Additional guidance for Special Tracks (other than SP 7, 16, 17, 20, 21 and 23). Call ADOC within 15 minutes of Forward Tell and pass the following information: track number; special number; departure/arrival locations; estimated time of arrival; any additional pertinent information.

6.2.3. Additional guidance for Unknown tracks and tracks perceived to be a threat or of national interest. Information on all Unknown tracks must be immediately electronically forward told. The completed Form 61 will be forwarded NLT 1 hour after final action is completed unless otherwise directed by the ADOC. Information on any track, regardless of classification, perceived to be a threat (e.g. foreign military combat aircraft) or of national interest will immediately be electronically and voice forwarded to the ADOC. All amplifying data, that cannot be transmitted electronically must be voice forwarded as rapidly as it becomes available to ensure the RAOC receives the most current information. The ADOC will advise the ADOC whether or not a Form 61 will be required. The ADOC, to minimize repetitive comms, will strive to establish a consolidated information package when additional data is required.

6.2.4. The NORAD ADOC has no requirement to receive UNKNOWN track reports from the ICELAND RAOC on a day-to-day basis unless CINCNORAD OPLAN 3200 has been executed, or unless DEFCON 3 or higher has been declared, at which time Iceland RAOC will also report tracks identified or correlated as cruise missiles, cruise missile carriers, CIS military or threat aircraft.

6.2.5. NORAD agencies use Form 61 to record air activity information on Unknown, Special 17 and 21 tracks. The SAOC submits by voice to the RAOC the information in blocks 1-9, 23-27, 33-36, and 46 within 5 minutes after action is taken. The RAOC relays the information by voice immediately to the ADOC and forwards the completed Form 61 NLT 1 hour after final action is complete unless otherwise directed by the ADOC.

Note: If fighters are committed, their track information, for the duration of the mission, must be forward told to the ADOC once the fighters are airborne. Amplifying data on fighters, if required by ADOC, will be requested to be continually updated by voice.

6.2.6. If amplifying information, temporary or permanent, on any track is required, the ADOC will immediately advise the RAOC. If this new operational reporting requirement is permanent, HQ NORAD must be verbally advised by the ADOC within 24 hours followed by a suggested amendment to this instruction within 72 hours.

6.3. Reported By. NORAD Regions and Sectors, Iceland Air Defense Sector (ICADS), and E-3s. Amplifying data on Special 17's is normally available within 24 hours from the Domestic Air Interdiction Coordination Center (DAICC) Intelligence Section. Region/Sector intelligence sections will coordinate directly with the DAICC to obtain this information to ensure complete reporting.

6.4. Reported To. CANR SAOC, the Alaskan RAOC, CONUS RAOC and the ICADS report to NORAD ADOC. CONUS SAOCs report to the CONUS RAOC. E-3s will report to NORAD ADOC when not reporting to a SAOC, RAOC or Alternate Command Element (ACE). When a reportable track crosses between areas of responsibility, the forwarding SAOC will report the track to adjacent Sector, Region, and the NORAD ADOC. Reporting agencies also use the ADNET to report Special 17 tracks and follow up data in coordination with the Royal Canadian Mounted Police and the DIACC or appropriate Joint Interagency Task Force..

6.5. How Reported:

6.5.1. Initial Reporting. All reportable tracks, IAW para 6.2, will be immediately forward told electronically. In addition, Special 17 tracks will be transmitted over the ADNET system IAW NR55-23.
6.5.1.1. Classification. According to content.

6.5.1.2. Method of transmission:

6.5.1.2.1. Primary. Electronic high speed data forward tell all reportable tracks IAW para 6.2.

6.5.1.2.2. Secondary. Voice DSN or NTAS all reportable tracks IAW para 6.2.

6.5.1.3. Precedence. PRIORITY.

6.5.1.4. MINIMIZE. Unaffected by MINIMIZE.

6.5.1.5. Report Indicator. IN.

6.5.1.6. Report Content. See Attachment 4.

6.5.1.7. Sample Reports. See Attachment 4.

6.5.2. Follow up Reporting. When a track is classified as Unknown, Special 17, or Special 21, additional data is required. See paragraphs 6.2.1. to 6.2.3.

6.5.2.1. Classification:

6.5.2.1.1. According to content.

6.5.2.1.2. SAOC will mark Form 61 on Special 17 tracks as CONFIDENTIAL.

6.5.2.2. Method of Transmission: Secure lines will be used when dictated by report classification.

6.5.2.2.1. Primary voice. Secondary: any other means

6.5.2.3. Precedence:

6.5.2.3.1. Unknown Report: ROUTINE.

6.5.2.3.2. Special 17: ROUTINE.

6.5.2.3.3. Special 21 or any aircraft believe to be a threat, regardless of classification: IMMEDIATE.

6.5.2.3.4. Hostile: FLASH.

6.5.2.4. MINIMIZE: All track reports are unaffected by MINIMIZE.

6.5.2.5. Report Content: Using NORAD Form 61 at Figure 6.1, fill in blocks as the information becomes available. Use the following codes or guidelines to enter information in blocks 1, 7, 17, 27, 40, and 41, 42, 43:

6.5.2.5.1. Block 1: Check the appropriate type track report. For Unknowns which become SP-17, check both type track reports.

6.5.2.5.2. Block 7: Action Deferred reasons.

6.5.2.5.21. CC -Tactical action deferred by the Region commander or designated representative

6.5.2.5.2.2. ADRY -Action deferred due to runway condition.

6.5.2.5.2.3. ADTD -Action deferred due to tactical decision (give reason in Part E - Remarks Section i.e., for track speed, location, or possible ID such as "fits oil rig helicopter profile").
6.5.2.5.2.4. ADWX -Action deferred due to weather (give weather in Part E - Remarks Section).

6.5.2.5.2.5. CD -NORAD Command Director approval for taking no tactical action( ADOC will record reason in remarks section).

6.5.2.5.2.6. FA -Air traffic is such that the FAA/TC is unable to provide clearance for alert fighters within the ATC system.

6.5.2.5.2.7. HP -Higher priority.

6.5.2.5.2.8. IPTO -Identified prior to take-off.

6.5.2.5.2.9. IR -Intercept point is out of fighter range.

6.5.2.5.2.10. NF -No fighters available (give specific reason in Part E - Remarks Section).

6.5.2.5.2.11. NFSL -No fighters in suitable location (give bearing and range to nearest Alert location).

6.5.2.5.2.12. RR -Intercept point is out of ground radar and radio range.

6.5.2.5.3. Block 17:

6.5.2.5.3.1. NFP - No Flight Plan available.

6.5.2.5.3.2. PO - Point of Origin.

6.5.2.5.3.3. SC - Suspicious Characteristics (SP, HDG, and or ALT).

6.5.2.5.3.4. PI - Prior Intelligence.

6.5.2.5.3.5. OT - Other (Explain in Part E - Remarks).

6.5.2.5.4. Block 27:

6.5.2.5.4.1. ATC COR -Air Traffic Control correlation. (Includes ATC flights service information relayed by LEA)

6.5.2.5.4.2. BAD DAT -Spurious radar data.

6.5.2.5.4.3. CUSTOMS -Air or ground customs asset identification.

6.5.2.5.4.4. IFF/SIF -Identified by IFF/SIF procedures, including modes 1-4.

6.5.2.5.4.5. INTCP -Intercept by NORAD fighter.

6.5.2.5.4.6. OP AGRE -Operational agreement as reported by military controlling agency.

6.5.2.5.4.7. POS RPT -Position report by aircrew of unknown aircraft.

6.5.2.5.4.8. REM -Remaining Unknown -not identified.

6.5.2.5.4.9. V AUTH -Voice authentication, including unknown rider procedures.

6.5.2.5.4.10. VIS ID -Visual identification by qualified observers on the ground, ship, or airfield tower.

6.5.2.5.5. Block 40:

6.5.2.5.5.1. FPI -Faded prior to intercept.

6.5.2.5.5.2. IPI -Identified prior to intercept.

6.5.2.5.5.3. Kill.
6.5.2.5.5.4. MA -Mission accomplished.

6.5.2.5.5.5. MI -Missed intercept (ensure block 41 is completed).

6.5.2.5.5.6. OT -Other.

6.5.2.5.6. Block 41:

6.5.2.5.6.1. ACP -Aircraft performance.

6.5.2.5.6.2. AEF -Airborne equipment failure.

6.5.2.5.6.3. DE -Director error.

6.5.2.5.6.4. DK -Darkness.

6.5.2.5.6.5. EA -Electronic countermeasures.

6.5.2.5.6.6. GEF -Ground environment failure.

6.5.2.5.6.7. L -Late commit.

6.5.2.5.6.8. LS -Late scramble.

6.5.2.5.6.9. MP -Military prohibition.

6.5.2.5.6.10. OT -Other.

6.5.2.5.6.11. PE -Pilot error.

6.5.2.5.6.12. SF -Safety.

6.5.2.5.7. Block 42: Circle agency responsible for error: REG (Region or Sector); ARTC (any ATC Agency); PILOT (Pilot Error). Other reasons for responsibility include System Limitation or No Error. Details must be fully explained in Block 47.

6.5.2.5.8. Block 43: If further investigation is required, explain fully in Block 47.

6.5.2.5.9 Block 47, Remarks, will be used to amplify any data or information according to Region/Sector procedures or as directed by the ADOC. It is the RAOC/SAOC's responsibility to provide amplifying data in sufficient detail to ensure complete reporting and the ADOC's responsibility to ensure these remarks are provided and that they make sense. If tankers are used during the intercept, either to support the fighters or an E-3, include the tanker used, tanker hours used, and offload. This last item will allow HQ NORAD to capture data that must be reported to JCS without initiating a separate report.

6.5.2.6. Sample Report. See Figure 6.1.
6.5.2.7. Specific Reporting Instructions:

6.5.2.7.1. Submit report sequentially with reference to the appropriate item number. For example; Item 40, FOXTROT PAPA INDIA (FPI).

6.6. When Reported:

6.6.1. Initial Report -Forward Tell at all LERTCONS

6.6.1.1. Tracks will be reported immediately upon classification.

6.6.1.2. Tracks reports are automatically electronically forward told either every minute or every 6 minutes as directed by the ADOC.

6.6.1.3. If voice telling, track reports must be updated at least every 5 minutes or as directed by the ADOC.

6.6.1.4. Unless directed by the ADOC, mass track reporting (see A5.8.) commences at the declaration of DEFCON 3 or higher. E-3s may employ mass track reporting when required due to operational conditions.

6.6.2. Follow up Reports -NORAD Form 61 (See paragraph 6.2.3):

6.6.2.1. Special 21 Track Reports: Submit by voice the information in blocks 1-9, 23-27, 33-36, and 46 within 5 minutes of action taken unless otherwise directed by the ADOC. Regions forward Form 61 to the ADOC within 1 hour after final action or track fade during DEFCONs 5 and 4 only, voiced to ADOC as soon as the information becomes available, not to exceed 1 hour during DEFCONs 3, 2, 1 (unless otherwise directed by the ADOC).

Note: N/SP ANA maintains all completed reports for analysis and historical purposes.

CHAPTER 7

RADAR OUTAGE REPORT

7.1. Purpose: This report is sent via data circuit to the ADOC if NORAD region or sector radars experience outages rendering them non-mission capable.

7.1.1. DEFCONs 5 and 4. Report the following outages that affect search radar capability:

7.1.1.1. Two or more adjacent outlying radar site outages with concurrent estimated time return to operation (ETRO) greater than 1 hour.

Note: Coordinate radar outages occurring near common region/sector boundaries with the affected area.

7.1.1.2. Inoperative single surveillance radar site with an ETRO of 12 hours or more (1 hour for aerostat).

7.1.1.3. Inoperative single OTH-B segment with an ETRO of 5 minutes or more or any scheduled maintenance where system is unavailable.

7.1.1.4. All operational outages affecting aerostats (non-mission capable) with an ETRO greater than one (1) hour. This includes scheduled maintenance, ground-based equipment failure or any situation causing the aerostat to be non-mission capable.

7.1.1.5. Airborne radars OPCON to NORAD.

7.1.2. DEFCON 3, 2, 1. Report all outages that affect search or selective identification feature (SIF) radar capability.

Note: Radar outages which must be reported include complete loss (both channels) of search during DEFCONs 5 and 4, or search or SIF during DEFCON 3 and above. Regions are not required to report limited outages which do not significantly affect mission accomplishment (such as, electronic counter-countermeasures receiver).

7.2. Submitted by:

7.2.1. Radar units.

7.2.2. AWACS aircraft.

7.2.3. OTH-B operations centers.

7.2.4. Aerostat operations centers .

7.2.5. RAOCs and or SAOCs.

7.3. Submitted To:

7.3.1. NORAD regions.

7.3.2. NORAD ADOC.

7.4. When Submitted. Submit when an event or incident occurs as per paragraph 7.1 or any outage with an unknown ETRO after 12 hours.

7.5. How Submitted:

7.5.1. Classification:

7.5.1.1. Aerostat - Unclassified.

7.5.1.2. OTH-B - Secret.

7.5.1.3. AWACS (E-3) - Secret.

7.5.1.4. North Warning System (NWS) -Secret

7.5.1.5. ANR (Seek Igloo (AN/FPS-117)) - Secret

7.5.1.6. CONUS JSS - Unclassified.

7.5.1.7. Canadian Coastal Radars (CCRs) - Secret

7.5.1.8. Hawaii - Unclassified.

7.5.1.9. All others - Unclassified.

7.5.2. Method of Transmission:

7.5.2.1. Primary. Via RAOC/SAOC computer to ADOC.

7.5.2.2. Alternate. Voice; DSN, NTAS, and commercial phone lines.

Note: OTH-B sends information via the Advanced Interface Control Unit (AICU). Reporting requirements will commence for OTH-Bs upon reactivation from cold storage.

7.5.3. Precedence. Priority.

7.5.4. MINIMIZE. Unaffected by MINIMIZE.

7.6. Report Indicator. IN.

7.7. Specific Reporting Instructions. None.

7.8. Report Content. Show:

7.8.1. Date-Base Group.

7.8.2. Region. CONR, specify sector.

7.8.3. Surveillance radar affected.

7.8.4. Date-time group of outage.

7.8.5. Reason (be specific enough so that the nature and extent of the outage is easily understood).

7.8.6. ETRO.

7.9. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Warning Division (N/J3W).

Chapter 8

MANDATORY SCRAMBLE REPORT

8.1. Purpose. This report informs the region commander and NORAD ADOC when conditions at a particular air base are hazardous for takeoff and landing or have returned to normal. When a fighter unit or a NORAD OPCON E-3 is maintaining the directed Response Posture, but conditions exist per NR55-11(S), NORAD Air Defense Fighter Alert and Force Generation (U) (to be published as NI10-20(S)), or NR55-16(S), NORAD E-3 Operating Procedures (U), they allow scrambles for active air mission only.

8.2. Submitted By:

8.2.1. NORAD regions.

8.2.2. 552 ACW.

8.2.3. Active duty fighter squadrons and Air National Guard (ANG) alert units.

8.2.4. Augmentation units in mobilization or alert status.

8.3. Submitted To:

8.3.1. The region (or its alternate).

8.3.2. NORAD ADOC.

8.4. When Submitted:

8.4.1. DEFCONs 5 and 4 submit to ADOC only during execution of OPORD 3199 or when requested by ADOC during contingency operations.

8.4.2. DEFCON 3 or higher.

8.5. How Submitted:

8.5.1. Classification. Determined by contents; for example, reference to OPLANs or OPORDs could make the report SECRET.

8.5.2. Method of Transmission:

8.5.2.1. Primary. FORWARD TELL.

8.5.2.2. Alternate. Voice reporting.

8.5.3. Precedence. PRIORITY.

8.5.4. MINIMIZE. Unaffected by MINIMIZE.

8.6. Report Indicator. IN.

8.7. Specific Reporting Instructions. None.

8.8. Report Content. Show:

8.8.1. Date-time group.

8.8.2. Air base (name).

8.8.3. Status (mandatory or normal).

8.8.4. Reason.

8.8.5. ETRO.

8.9. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 9

COMMAND AND CONTROL IDENTIFIERS (CCI) REPORT

9.1. Purpose. This report provides the regions and sectors with a system to identify location of command and the source of tactical control for air defense forces to the NORAD ADOC. Five numbers are used to identify command and seven letters for tactical control.

9.2. Submitted By:

9.2.1. NORAD region.

9.2.2. NORAD OPCON E-3 (when in command of the region).

9.2.3. NORAD region alternate command element (ACE).

9.3. Submitted To. NORAD ADOC and MCCC, when in place.

9.4. When Submitted. Submit when a change in the CCI occurs.

9.5. How Submitted:

9.5.1. Classification. UNCLASSIFIED.

9.5.1. Method of Transmission:

9.5.1.1. Primary. DSN or NTAS (voice).

9.5.1.2. Alternate. AUTODIN.

9.5.2. Precedence. PRIORITY.

9.5.3. MINIMIZE. Unaffected by minimize.

9.6. Report Indicator. IN.

9.7. Specific Reporting Instructions. When submitting by voice, use phonetic identifiers for all letters and references made to line and field numbers to identify message content. NORAD regions report any degradation in their capability to expand into adjacent regions or among sectors to the NORAD ADOC. Command and control identifiers (CCI) are the method by which the NORAD air defense system report command and control structure within the regions. CCIs will be reported as follows:

9.7.1. Command Location. The location of region or sector command is identified numerically as follows:
9.7.1.1. 1 - (RAOC) The NORAD region commander or designated alternate.

9.7.1.2. 2 - (SAOC) The NORAD sector commander or designated alternate.

9.7.1.3. 3 - (NACC) The NORAD Airborne Command Center E-3 battle commander has control of the region and/or sector.

9.7.1.4. 4 - (ACE) The NORAD region and/or sector commander or designated alternate located at an alternate command element (ACE) has command of the region and/or sector.

9.7.1.5. 5 - Autonomous. Command is being exercised by individual unit commander operating autonomously.

9.7.2. Tactical Control Source. The facilities providing tactical control are identified alphabetically as follows:

9.7.2.1. A - Autonomous. Fighter squadrons are responsible for directing their own activities. Weapons controllers at selected sites are broadcasting bogey information on predesignated frequencies.

9.7.2.2. E - Adjacent region/sector. A region or sector is inoperative and the appropriate sectors have expanded into the inoperative region or sector.

9.7.2.3. N - NACC

9.7.2.4. P - Patrol E-3.

9.7.2.5. R - RAOC.

9.7.2.6. S - SAOC.

9.7.2.7. X - ACC, ANG, Navy, or Marine tactical air control system.

9.7.3. Examples of CCIs:

Command Location Tactical Control
ExampleIdentifiersSource Identifiers

A CCI 1 NPS
B CCI 2 S
C CCI 2 N
D CCI 5 A

Example A: CCI - 1NPS - Command retained at the region. NACC E-3, Patrol E-3, and the sectors are
providing control.

Example B: CCI - 2S - The sector has command and control.

Example C: CCI - 2N - Command retained at the sector. The NACC E-3 is providing control.

Example D: CCI - 5A - Individual unit commanders have command. Control is autonomous.

9.8. Report Content:

9.8.1. Region.

9.8.2. Date-time group (DTG).

9.8.3. Command and control identifier (region or sector).

9.9. Sample Report:

9.9.1. CONR.
9.9.2. DTG 010100Z Jan 95.

9.9.3. CCI -1E (SE AD Sector).

9.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Warning Division (N/J3W).

Chapter 10

COMPUTER OUTAGE REPORT

10.1. Purpose. This report informs the NORAD ADOC when RAOCs and/or SAOCs are non-mission capable (NMC).

10.2. Submitted By. NORAD RAOCs and SAOCs.

10.3. Submitted To:

10.3.1. NORAD region.

10.3.2. NORAD ADOC.

10.4. When Submitted. Submit when operational status changes and ETRO is expected to be 10 minutes or longer.

10.5. How Submitted:

10.5.1. Classification. Scheduled or prior-notice outages are CONFIDENTIAL until 30 minutes prior to the actual outage, then UNCLASSIFIED. No-notice outages with an ETRO of greater than 2 hours are CONFIDENTIAL.

10.5.2. Method of Transmission:

10.5.2.1. Primary is DSN or NTAS (secure voice).

10.5.2.2. Alternate is commercial telephone.

10.5.3. Precedence. PRIORITY

10.5.4. MINIMIZE. Unaffected by minimize.

10.6. Report Indicator. N/A

10.7. Specific Reporting Instructions. None.

10.8. Report Content. Show:

10.8.1. Date-time group (DTG).

10.8.2. System. CONR and CANR, specify sector.

10.8.3. Status (fully mission capable (FMC), or non-mission capable (NMC)).

10.8.4. Time of outage.

10.8.5. Reason for outage or actions which corrected the report.

10.8.6. ETRO.

10.9. Sample Report for RAOC or SAOC Outage:

10.9.1. 232210Z Jan 95.

10.9.2. NE SAOC.

10.9.3. NMC.

10.9.4. 232205Z.

10.9.5. Display controller failure.

10.9.6. Unknown.

10.10. Sample Report for Return to Operation:

10.10.1. 232330Z.

10.10.2. NE SAOC.

10.10.3. FMC.

10.10.4. 232205Z

10.10.5. System reload to correct.

10.10.6. Operational.

10.11. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Warning Division (N/J3W).

Chapter 11

FIGHTER STATUS REPORT

11.1. Purpose. This report provides planning information concerning fighters to the RAOCs, SAOCs and ADOC. This status report delineates fighters under the operational control of NORAD, including those OPCON to CINCNORAD at OPLAN 3200-95 (S) execution. To supplement this report, see NI20-1.

11.2. Submitted By:

11.2.1. NORAD regions or sectors.

11.2.2. Active duty squadrons and Air National Guard (ANG) fighter units

11.2.3. Augmentation fighter squadrons.

11.3. Submitted to: Fighter units forward to SAOC/RAOC (as applicable) or ACE. SAOCs consolidate unit reports and forward to their respective RAOC. RAOCs consolidate and forward to the ADOC.

11.4. When Submitted:

11.4.1. If a change occurs at the alert site but not more than every 15 minutes.

11.4.2. Changes in status of alert aircraft. NORAD ADOC does not need day-to-day practice scramble information on alert aircraft.

11.4.3. On attaining an actual or simulated Response Posture.

11.4.4. On relief, deployment, or resumption of Response Posture.

11.4.5. If a unit cannot meet the minimum assigned alert posture.

11.4.6. When NORAD ADOC requests the report.

11.4.7. By augmentation fighter squadrons immediately on notification of mobilization or when participating in an air defense exercise under NORAD control.

11.5. How Submitted.

11.5.1. Classification:

11.5.1.1. DEFCON 5 - UNCLASSIFIED

11.5.1.2. DEFCON 4 or higher, or at OPORD execution - SECRET

11.5.2. Method of Transmission:

11.5.2.1. From a unit:

11.5.2.1.1. Primary: DSN or NTAS (voice).

11.5.2.1.2. Alternate: TTY.

11.5.2.2. From a RAOC/SAOC - forward tell, voice, or teletype backup.

11.5.2.2.1. Primary: Forward tell circuits.

11.5.2.2.2. Alternate: DSN or NTAS (voice).

11.5.3. Precedence: PRIORITY for voice or teletype.

11.5.4. MINIMIZE: Unaffected by MINIMIZE.

Note: Voice reports to E-3 or ACE will be in TAB A format according to NR55-16(S), NORAD E-3 Operating Procedures.

11.6. Report Indicator. IN

11.7. Specific Reporting Instructions. Regions report number of aircraft OPCON to CINCNORAD.

11.7.1. The RAOC/SAOC reports when mission-capable fighter weapons systems are temporarily active outside of RAOC/SAOC AOR , but remaining under the operational control of the RAOC/SAOC.

11.7.2. The RAOC/SAOC reports when mission-capable fighter weapons systems are deployed outside of parent RAOC/SAOC AOR and placed under operational control of another RAOC/SAOC.

11.8. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 12

E-3 STATUS REPORT (AWACS)

12.1. Purpose. The E-3 Status report provides current status of the NORAD-airborne warning and control forces to the NORAD ADOC when NORAD has OPCON of E-3 assets.

12.2. Submitted By:

12.2.1. The 552 Air Control Wing (552 ACW) Command Post Operations Center (CPO).

12.2.2. NORAD regions.

12.3. Submitted To. NORAD regions or NORAD ADOC.

12.4. When Submitted. Submit:

12.4.1. By 0001Z daily or when a change occurs.

12.4.2. Regions report on NORAD OPCON E-3s at deployment or dispersal locations within the region (by sectors) to the NORAD ADOC.

12.5. How Submitted:

12.5.1. Voice reports classification - CONFIDENTIAL.

12.5.2. Method of Transmission:

12.5.2.1. From 552 ACW OC to NORAD ADOC.

12.5.2.1.1. Primary. DSN (secure voice).

12.5.2.1.2. Alternate. AUTODIN.

12.5.2.2. From 552 ACW CPO to NORAD regions.

12.5.2.2.1. Primary. DSN (secure voice).

12.5.2.2.2. Alternate. AUTODIN.

12.5.2.3. From NORAD regions to NORAD ADOC.

12.5.2.3.1. Primary. Forward Tell.

12.5.2.3.2. Alternate. DSN or NTAS (secure voice).

12.5.3. Precedence. PRIORITY.

12.5.4. MINIMIZE. Unaffected by MINIMIZE.

12.6. Specific Reporting Instructions:
12.6.1. This report reflects actual quantities of E-3 aircraft and their current status. Do not use plus or minus values.

12.6.2. Do not make changes upon direction of a new Response Posture. Wait until new posture is assumed and then update the status.

Note: All status changes are a real-time reflection of the actual Response Posture.

12.6.3. Use the phonetic alphabet to identify all letters and reference field numbers to identify message content.

12.6.4. Do not report aircraft in turn-around and/or maintenance status until the aircraft is repaired and/or assumes directed Response Posture.

12.6.5. During NORAD-wide live-fly exercises, report only those aircraft committed to exercise participation.

12.6.6. During NORAD-wide simulated exercises, report those aircraft committed to the exercise via the exercise node. Report real-world status via the live node.

12.7. Report Content. See Attachment 4, paragraph A4.2.

12.8. Sample Report. See Attachment 4, paragraph A4.2.

12.9. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 13

WEAPONS READINESS DEVIATION REPORT

13.1. Purpose. The Weapons Readiness Deviation Report is sent when a region, sector, or 552 Air Control Wing cannot maintain the armed fighter or NORAD E-3 readiness requirements per NI10-20(S) and NR55-16 (S).

13.2. Submitted By:

13.2.1. NORAD regions.

13.2.2. 552 ACW.

13.2.3. All fighter units committed to CONPLAN 3310 (S).

13.3. Submitted To. The region command post or its alternate command post. Regions will consolidate and submit to ADOC.

13.4. When Submitted. Submit only during DEFCONs 5 and 4 and if a change in status occurs or if requested by ADOC

13.5. How Submitted:

13.5.1. Classification:

13.5.1.1. Fighters: DEFCON 5 - UNCLASSIFIED; DEFCON 4 or higher or upon OPORD execution - SECRET.

13.5.1.2. NORAD E-3 - CONFIDENTIAL

13.5.2. Method of Transmission:

13.5.2.1. Primary: DSN or NTAS (secure or nonsecure, as appropriate).

13.5.2.2. Alternate: AUTODIN

13.5.3. Precedence: PRIORITY

13.5.4. MINIMIZE: Unaffected by MINIMIZE.

13.6. Report Indicator. N/A

13.7. Specific Reporting Procedures. Submit at time of deviation and when deviation is complete.

13.8. Report Content. Whenever a deviation occurs, the region provides ADOC with the following data:

13.8.1. Fighter Deviations. This is the numerical indication of those mission-capable aircraft generated to CINCNORAD that are unable to maintain the required alert status and or meet the required reaction time for the ordered weapons readiness state per NI10-20(S). Include affected aircraft type and location.

13.8.2. NORAD E-3 Deviations. This is a numerical indication of those mission-capable aircraft OPCON to CINCNORAD that are unable to maintain the required response status and or meet the required reaction time for the ordered Response Posture. Aircraft in turnaround status are not considered deviations unless they are unable to return to status in 3 hours. The data is provided by either the 552 ACW or the region in which E-3s are deployed or dispersed.

13.9. Sample Report. The following is an example of a region's weapons deviation report: "This is the Alaskan NORAD Region with a weapons deviation report. At 13/1700Z Galena minus one F-15 due to a hydraulic leak. The ETRO is 2130Z."

13.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 14

AIRCREW AND AIRCRAFT LOSS REPORT (LOSREP)

14.1. Purpose. This report provides follow-on information (after an OPREP-3 event or incident report) on loss of aircrew or aircraft due to:

14.1.1. Hostile or suspected hostile action.

14.1.2. Operational losses incurred by aircrews or aircraft engaged in combat operations or in direct support of combat operations.

14.2. Submitted By. NORAD-assigned units having operational control of aircrews or aircraft.

14.3. Submitted To:

14.3.1. ACTION Addressees:

14.3.1.1. For US aircraft, CSAF WASHINGTON DC//CC//

14.3.1.2. For CF aircraft:

14.3.1.2.1. NDHQ OTTAWA ON CAN//DGAD//.

14.3.1.2.2. CDN AIRCOM WINNIPEG MA CAN//DCOS OPS//.

14.3.1.2.3. CMOC CHEYENNE MOUNTAIN AS CO//CD/EA//.

14.3.1.2.4. Major command to which aircraft is assigned.

14.3.2. INFORMATION Addressees:

14.3.2.1. HQ AFISC NORTON AFB CA//IGDS//.

14.3.2.2. ALTN HQ USAF MAXWELL AFB AL//. (On DEFCON 2 or higher or as directed by HQ USAF.)

14.3.2.3. AFEOC FT RITCHIE MD//.

14.3.2.4. For CF aircraft, NDHQ OTTAWA ON CAN//ADM(MAT)//.

14.4. When Submitted. Submit:

14.4.1. An initial report within 3 hours after submission of the initial OPREP-3 incident report or in the event of a damaged aircraft determined to be unrepairable.

14.4.2. Follow-on reports as additional information becomes available or if a reported loss due to hostile action is changed to a loss due to operational causes (or vice versa).

14.4.3. The final report when all information on an aircrew or aircraft loss that is likely to become available has been reported.
14.5. How submitted:

14.5.1. Classification is SECRET RELCANUS. The originator may assign a higher classification if warranted by report contents.

14.5.2. Transmission:

14.5.2.1. Primary is AUTODIN.

14.5.2.2. Alternate is TTY.

14.5.3. Precedence:

14.5.3.1. For initial report is IMMEDIATE.

14.5.3.2. For follow-on reports is PRIORITY.

14.5.4. MINIMIZE. Unaffected by minimize.

14.6. Report Indicator. LO.

14.7. Specific Reporting Instructions:

14.7.1. Indicate whether the aircrew and aircraft were combat or operational.

14.7.2. For initial Aircrew and Aircraft Loss Report (LOSREP), reference OPREP-3 event or incident report.

14.7.3. For follow-on LOSREPs, reference previous LOSREPs.

14.8. Report Content. Include the following when known:

14.8.1. Report type (initial, follow-on, final).

14.8.2. Type loss (combat or operational).

14.8.3. Aircraft identification (type, serial number, call sign, operational base, and squadron).

14.8.4. Time and location of loss (Zulu).

14.8.5. Aircrew identification and status for each crew member.

14.8.6. Mission and target information (type mission, type target, target location in latitude and longitude, target area weather, day or night).

14.8.7. Tactics (cause of loss, altitude when hit, and weapons carried when hit).

14.8.8. Rescue information (ejection and chute information, environment at rescue site, agency directing SAR, when and why SAR terminated).

14.9. Sample Report. None.

14.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 15

NORAD REGION SITUATION REPORTING

Section A - General

15.1. Purpose. NORAD region situation reporting keeps CINCNORAD appraised of operational situations and the status of plans to include the readiness of assigned forces. The primary means of situation reporting is the Commander's Situation Report (SITREP); an indepth narrative report submitted on a routine basis (see section B). The Quick Look Capability Index (QLCI) Report (section C) is available for region commanders to keep CINCNORAD appraised of the current situation when the detail contained in a SITREP is not required.

Section B - Commander's SITREP

15.2. Purpose. The Commander's SITREP is an indepth report of the NORAD region commander's situation.

15.3. Submitted By. Region commanders (regions consolidate sector reports).

15.4. Submitted To:

15.4.1. DEFCONs 5 and 4 - ACTION. Submit to CMOC CHEYENNE MOUNTAIN AS CO//CC/J3/BATTLE STAFF// , MCCC PETERSON AFB CO//CC// and INFO other regions.

15.4.2. DEFCON 3, 2, 1 - ACTION. Submit to CMOC CHEYENNE MOUNTAIN AS CO//CC/J3/BATTLE STAFF/J3OA//, MCCC PETERSON AFB CO//CC//, USSPACECOM PETERSON AFB CO//J3CP/ J3CR/ J1//, and INFO other regions.

15.5. When Submitted. Submit:

15.5.1. DEFCONs 5 and 4. Monthly to arrive at CC by the first workday of the month. Region commanders may submit more frequent reports at their discretion. Daily reports are not required. The QLCI format may be used in lieu of a complete SITREP (see section C).

15.5.2. DEFCON 3 and higher. Daily as of 1900Z to arrive at the HQ NORAD/USSPACECOM Command Center by 2200Z, or when directed.

Note: If situations arise which change the SITREP between submission time and 2400Z, call HQ NORAD/USSPACECOM Command Center with secure voice update.

15.6. How Submitted:

15.6.1. Classification. Originator determines.

15.6.2. Method of Transmission. Record communications (TTY).

15.6.2.1. Primary. AUTODIN.

15.6.2.2. Alternate. GCCS.

15.6.3. Precedence. IMMEDIATE.

15.6.4. MINIMIZE. Unaffected by MINIMIZE.

15.7. Specific Reporting Instructions. This is a narrative report except for the operations and personnel sections which use a formatted text for SITREPs following ADW White or changes in NORAD continuity of operations. Do not include information previously reported. Reference previous reports when warranted.

15.8. Report Content:

15.8.1. Classification Line. This line contains the classification and the flagwords JOPREP JIFFY.

15.8.2. Report Numbers. Report numbers begin with 001 on 1 January and continue sequentially. Subsequent reports on the same situation contain original report number with alphabetical suffixes. Number exercise reports independently of real-world reports, beginning with 001 at the start of each exercise and continued sequentially until exercise termination.

15.8.3. Text:

15.8.3.1. Paragraph may be subdivided to any extent necessary by the originator.

15.8.3.2. Inappropriate paragraphs may be marked "N/A" or "no change".

15.8.3.3. Commanders may add additional paragraph headings as required.

15.8.4. Amplification:

15.8.4.1. Own Situation - (Disposition of Forces). Summary of changes to, or not previously reported, major combat and support force locations; significant mission readiness degradation at units; current deployments; proposed deployments; changes in task force designations, organization, or operational control; and projected requirements for additional forces. Do not number these paragraphs or subparagraphs.

15.8.4.2. Situation Overview. Contains brief, overall assessment of the current situation, to include circumstances or conditions which increase or materially detract from the capability and readiness of forces assigned.

15.8.4.3. Operations:

15.8.4.3.1. Brief description and results of air operations carried out since last report and report losses, if any. Include operations planned for the next 24 hours, objectives, and probable enemy reaction.

15.8.4.4. Intelligence. Include brief overview of the situation, including operations, order of battle, capabilities, and threat changes. Reference any significant Intelligence Reports (INTREP) submitted in previous 24 hours.

15.8.4.5. Logistics. Significant deficiencies affecting support for planned operations, and problem areas beyond the commander's capability to overcome or alleviate it in a timely manner.

15.8.4.6. Communications Connectivity. Include significant communications outages, degradations, and an assessment of the mission impact.

15.8.4.7. Personnel. Factors affecting status and readiness of troops either assigned to or under the OPCON of CINCNORAD (use the narrative portion to assess mission impact) to include:

15.8.4.7.1. Troop Strength/Casualties Reporting (battle and nonbattle). Include all services, nationalities, and US Civilians.

15.8.4.7.2. Personnel deployed outside the AOR. Include military and US civilians (for large numbers of personnel deployed outside the AOR, put the region or sector for location). Ensure a copy of your Commander's SITREP is sent to "USSPACECOM SPACE OPERATIONS CENTER PETERSON AFB CO//J1//."

15.8.4.8. Significant Political, Military, and Diplomatic Events:

15.8.4.8.1. Significant Events. Events not reported by OPREP-3 PINNACLE but which could result in local, US, Canadian, or international public reaction.

15.8.4.8.2. Security. Address any local or site civil unrest contemplated or implemented; agitational activity; subversion of military efforts; suspected terrorism; and suspected sabotage, hostile infiltration, and penetration efforts.

15.8.4.8.3. Civil Defense. Address civil defense measures contemplated or implemented.

15.8.4.9. Commander's Evaluation. Summarize key points from the first eight sections, highlighting areas requiring higher headquarters action or decisions.

15.9. Sample Report. See Figure 15.1.

Section C - Quick Look Capability Index (QLCI) Report.

15.10. Purpose. The QLCI report is an abridged version of the Commander's SITREP. It is designed to
provide region commanders with the ability to keep CINCNORAD appraised of their correct situation when detailed information of force postures or the status of plans is not available or not required.

15.10.1. The QLCI index shows the commander's estimate of their capabilities to CINCNORAD and the NORAD Battle Staff. It gives a RED, YELLOW, or GREEN index in these 10 functional areas: communications, sensors, E3s, fighters, munitions, bases, computers, personnel, ACE, and commander's estimate as a whole. The color criteria are:

15.10.1.1. RED - Region or unit is unable to accomplish the mission.

15.10.1.2. YELLOW - Region or unit has a degraded capability to accomplish the mission.

15.10.1.3. GREEN - Region or unit has the capability to accomplish the mission.

15.10.2. The QLCI is not intended to:

15.10.2.1. Provide exact percentages on which to base decisions.

15.10.2.2. Initiate requisitions or reconstitution actions.

15.11. Submitted By:

15.11.1. Region commanders.

15.11.2. Sectors submit to NORAD regions for consolidation.

(CLASSIFICATION) JOPREP JIFFY
EXER/OPER
MSGID/SITREP/( originator)/ (message serial number)/(month)/ /
REF/A/ (msg title)/(originator)/ ( date-time group)//
(Reference set to be used as necessary)
PERIOD/FROM:______ Z/TO:______ Z/AS OF:______ Z.//
HEADING/OWN SITUATION ( )(free text)//
5 UNIT
/UNITDES /UNIT LOC /CMNTS
/(unit 1) /(location) /(comments)
/(unit 2) /(location) /(comments)//
AMPN ( ) (enter disposition of forces information using free text)//
GENTEX/GENERAL/
1. ( ) SITUATION OVERVIEW. (free text)
2. ( ) OPERATIONS. (free text and/or format)
3. ( ) INTELLIGENCE. (free text)
4. ( ) LOGISTICS. (free text)
5. ( ) COMMUNICATIONS CONNECTIVITY. (free text)
6. ( ) PERSONNEL.
A. ( ) TROOP STRENGTH/CASUALTIES: (daily)
SERVICE START-GAIN-LOSS-ENDING-DH-DO-WH-IOI-MIA
USA
USMC
USN
USAF
CANFOR
US CIVILIANS
TOTAL
B. ( ) PERSONNEL DEPLOYED OUTSIDE THE AOR:
#s MILITARY #s US CIVILIAN REMARKS
LOCATION (S)
C. ( ) NARRATIVE COMMENTS: (free text to remark on any of the following), changes in personnel deployed, replacement actions, augmentation actions, callup actions, impact of losses on mission, explain losses/gains, any admin errors from previous reports, any other pertinent data.
7. ( ) SIGNIFICANT POLITICAL MILITARY DIPLOMATIC EVENTS.
A. ( ) SIGNIFICANT EVENTS. (free text)
B. ( ) SECURITY. (free text)
C. ( ) CIVIL DEFENSE. (free text)//
GENTEXT/COMMANDER'S EVALUATION/ (free text, enter CINC's assessment and concerns ) / /
DECL/OADR//
Figure 15.1. Example of a SITREP.

15.12. Submitted To:

15.12.1. DEFCONs 5 and 4 - ACTION. Submit to CMOC CHEYENNE MOUNTAIN AS CO//CC/J3/ BATTLE STAFF// , MCCC PETERSON AFB CO//CC// and INFO other regions.

15.12.2. DEFCON 3, 2, 1 - ACTION. Submit to CMOC CHEYENNE MOUNTAIN AS CO//CC/J3/BATTLE STAFF/J3OA//, MCCC PETERSON AFB CO//CC//, HQ USSPACECOM PETERSON AFB CO//J3CP/J3CR /J1//, and INFO other regions.

15.13. When Submitted:

15.13.1. During DEFCON 5 and 4. The QLCI report format may be used to meet commander's SITREP reporting requirements for these readiness conditions.

15.13.2. DEFCON 3, 2, 1. The QLCI report will be submitted as of 0400Z each day to arrive at the CC before 0500Z.

15.13.3. Changes in Continuity of Operations. The QLCI report will be submitted 1 hour after a significant change in the NORAD continuity of operations. This QLCI report will be amplified via the next commander's SITREP.

15.14. How Submitted:

15.14.1. Classification. Originator determines:

15.14.2. Method of Transmission:

15.14.2.1. Primary. AUTODIN.

15.14.2.2. Alternate. GCCS.

15.14.3. Precedence. During DEFCONs 5 and 4, precedence is determined by the originator to meet receipt time requirements. During DEFCON 3 and higher, FLASH precedence is authorized.

15.14.4. MINIMIZE. Unaffected by MINIMIZE.

15.15. Report Indicator. SR.

15.16. Specific Reporting Instructions. If a category is other than GREEN (for example, RED, YELLOW, or has changed) include a brief narrative for each deviation.

15.17. Report Content. During exercise play, QLCI message addresses should be checked against the exercise order to ensure actual message traffic is not routed to exercise-only players.

15.17.1. Report these functional areas separately, even though they overlap in some instances:

15.17.1.1. Communications. This index refers primarily to equipment capability to include parts, maintenance, destruction, and overall ability to communicate. See note below.

15.17.1.2. Sensors. This index refers to all optical and radar sensor coverage including AWACS capabilities. See note below.

15.17.1.3. E3s. This index refers to E3s under operational control of the region.

15.17.1.4. Fighters. This is a comparison of flyable aircraft with aircraft required for the mission.

15.17.1.5. Munitions. This index refers to the munitions available to support available aircraft.

15.17.1.6. Bases. This includes a consideration of the essentials other than those already mentioned above to maintain the fighter force; that is, base support.

15.17.1.7. Computers. The computer is NMC or FMC.

15.17.1.8. Personnel. Consideration should be given to any shortages that have an operational impact on the NORAD mission.

15.17.1.9. Alternate Command Element (ACE). Consideration must be given to required personnel and deployment conditions.

15.17.1.10. Commander's Estimate. This includes, in aggregate, all of the above, plus other factors influencing or affecting the overall region or unit mission. See note below.

Note: In instances in which availability of an operational or airborne E-3 permits the upgrading of a particular status (for example, sensors upgraded from RED to YELLOW because of the E-3) that line is transmitted in two elements. The first is the commander's appraisal which considers use of all available assets including the E-3; the second element is the posture if E-3 was not available; for example; line 1 - GREEN BREAK YELLOW.

15.17.2. Report areas by line number and use format below:

LINE CATEGORY

1 Communications. See note above.
2 Sensors. See note above.
3 E-3s.
4 Fighters.
5 Munitions.
6 Bases.
7 Computers.
8 Personnel.
9 ACE.
10 Commander's estimate. See note above.

Note: See CINCNORAD OPLAN 3200-95(S) for a discussion of specific actions.

15.18. Sample Report. None.

15.19. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 16

NUCLEAR DETONATION REPORT (NUDET)

16.1. Purpose. The NUDET report contains information about nuclear detonations on the North American Continent. It supports the JCS requirements in JCS Publication 6, Volume II(S), and CF requirements in ACDP 100, Annex N.

16.2. Submitted By:

16.2.1. NORAD reporting activities (RA) per NR55-39 (to be published as NI10-22).

16.2.2. NORAD region and sector nuclear, biological, chemical operations centers (NBCOC).

16.2.3. The HQ NORAD NBCOC, or MCCC team (when in control or monitor mode).

16.2.4. Units not tasked by NI10-22 report via OPREP-3 PINNACLE (see Chapter 5).

16.3. Submitted To:

16.3.1. NORAD region or sector NBCOCs.

16.3.2. HQ NORAD NBCOC or MCCC team.

16.3.3. NCAs of the US and Canada, MAJCOMs, and civilian agencies (see NR55-39) .

16.4. When Submitted. Submit as required on sighting or detecting a nuclear detonation.

16.5. How Submitted:

16.5.1. Classification. UNCLASSIFIED.

16.5.2. Methods of Transmission:

16.5.2.1. Primary:

16.5.2.1.1. Telephone from reporting agency (RA) to NORAD regions or sector NBCOCs.

16.5.2.1.2. Forward tell from NORAD regions or sector NBCOCs via the NORAD Computer System to HQ NORAD NBCOC.

16.5.2.1.3. Any communications means available to the MCCC.

16.5.2.1.4. Common use AUTODIN from the CMAS to selected military and civilian subscribers.

16.5.2.2. Alternate. DSN making sure priority is given to military targets.

16.5.3. Precedence:

16.5.3.1. Initial report. FLASH (or highest precedence available).

16.5.3.2. Subsequent reports. IMMEDIATE.

16.5.3.3. FLASH NUDET. Reporting procedures are reimplemented when NORAD reverts to ADW White, regardless of DEFCON status.

16.5.4. MINIMIZE. Unaffected by MINIMIZE.

16.6. Report Indicator. NN.

16.7. Specific Reporting Instructions. See NR55-39.

16.8. Report Content. See NR55-39.

16.9. Sample Report. See NR55-39.

16.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 17

ENVIRONMENTAL HAZARD REPORT

17.1. Purpose. The Environmental Hazard Report gives information about chemical or biological (CB) events and radiological hazards. It is used if the North American continent has been subject to the deliberate employment of CB agents; and to provide an indication of the location and degree of radiological fallout contamination.

17.2. Submitted By:

17.2.1. Reporting activity (RA) per NR55-39.

17.2.2. NORAD region or sector NBCOCs.

17.2.3. HQ NORAD NBCOC.

17.2.4. Units not tasked in NR55-39 report via OPREP-3 PINNACLE (see Chapter 5).

17.3. Submitted To:

17.3.1. NORAD region or sector NBCOCs.

17.3.2. HQ NORAD NBCOC or MCCC Team.

17.3.3. NCAs of US and Canada and all MAJCOMs.

Note: Submit CB and radiological hazard reports to the NORAD region or sector NBCOCs then to the HQ NORAD NBCOC and from there, it is automatically forward told to the US and Canadian NCAs, selected MAJCOMs, and civilian agencies (see NR55-39). CB and radiological hazard reports are laterally told to the Mobile Consolidated Command Center (MCCC) by the HQ NORAD NBCOC.

17.4. When Submitted. Submit as required when circumstances indicate unusual happenings possibly caused by CB agent or when radiation contamination is a known hazard.

17.5. How Submitted:

17.5.1. Classification. UNCLASSIFIED.

17.5.2. Method of Transmission:

17.5.2.1. Primary:

17.5.2.1.1. DSN from RAs to NORAD region or sector NBCOCs.

17.5.2.1.2. Forward tell from NORAD region or sector NBCOCs to the HQ NORAD NBCOC.

17.5.2.1.3. Dedicated TTY from CMAS to NCAs and other selected subscribers for:

17.5.2.1.3.1. Significant CB reports.

17.5.2.1.3.2. Radiological hazard reports (automatically forward told as received).

Note: The MCCC receives all environmental hazard reports.

17.5.2.2. Alternate. DSN or any communication means available to the MCCC.

17.5.3. Precedence. IMMEDIATE.

17.5.4. MINIMIZE. Unaffected by MINIMIZE.

17.6. Report Indicator:

17.6.1. NB for biological reports.

17.6.2. NC for chemical reports.

17.6.3. NR for radiological hazard reports.

17.7. Specific Reporting Instructions. See NR55-39.

17.8. Report Content. See NR55-39.

17.9. Sample Report. See NR55-39.

17.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 18

PILOT OBSERVATION REPORTS OF POST-ATTACK DAMAGE (GLASSEYE)

18.1. Purpose. This chapter tells how to report nuclear attack damage to surface targets. Reports are called GLASSEYE. These reports are plain language descriptions of apparent damage to NCAs, military facilities, or the civil sector.

18.2. Submitted By. Strategic Command (STRATCOM) Post-Attack Command and Control System (PACCS) and other military or civilian aircrews who are tasked to overfly and report apparent damage sustained on areas of national interest.

18.3. Submitted To:

18.3.1. FAA flight information service.

18.3.2. Air traffic control centers (ATCC).

18.3.3. State emergency operation centers (EOC).

18.3.4. NORAD RAOCs' or SAOCs' NBCOCs.

18.3.5. HQ NORAD NBCOC or MCCC.

18.4. When Submitted. Submit as required.

18.5. How Submitted:

18.5.1. Classification. UNCLASSIFIED.

18.5.2. Method of Transmission:

18.5.2.1. Primary:

18.5.2.1.1. Voice ( UHF or HF) from aircraft (while airborne).

18.5.2.1.2. Written GLASSEYE confirmation report (mission debrief).

18.5.2.1.3. TTY from NORAD region or sector NBCOCs to the HQ NORAD NBCOC.

18.5.2.1.4. Dedicated TTY from CMAS to the NCA and other selected subscribers.

18.5.2.2. Alternate. DSN or NTAS from the NORAD region or sector NBCOCs through the HQ NORAD NBCOC or MCCC to the NCA.

18.5.3. Precedence. IMMEDIATE.

18.5.4. MINIMIZE. Unaffected by MINIMIZE.

18.6. Report Indicator. Not applicable.

18.7. Specific Reporting Instructions. See NR55-39.

18.8. Report Content. See NR55-39.

18.9. Sample Report. See NR55-39.

18.10. Headquarters Functional Manager. HQ NORAD, Chief, Aerospace Control Division (N/J3O).

Chapter 19

ELECTRONIC COUNTERMEASURES STATUS REPORTS
ELECTRONIC COUNTERMEASURES TACTICAL ACTION REPORT (ECTAR)
AND
ELECTRONIC COUNTERMEASURES SUMMARY REPORT (ECSUM)

19.1. Purpose:

19.1.1. CINCNORAD requires all information which provides warning of a hostile attack to include Electronic Attack (EA) degradation of any portion of the C3 system where such degradation impedes or prevents NORAD forces from locating a hostile attack and/or conducting the air battle. The detection of EA may be the first indication of an attack. The direction of an attacking force may be determined from the azimuth of the hostile jamming.

19.1.2. ECTARs are used by NORAD facilities to report the initial presence and direction of an EA event in their areas of responsibility. ECSUMs are used to report further system degradation by EA events after the initial ECTAR report. Significant degradation to a C3 element, the inability of an element to continue its mission, and cessation of EA attack are also reported by ECSUM. The content of the ECTAR and ECSUM reports provide report origin, affected functions, EA azimuth (ECTAR only), level of degradation (ECSUM only), and report time information.

19.1.3. Reports submitted in this chapter do not supersede or cancel electronic magnetic interference (EMI) reporting.

19.2. Submitted By:

19.2.1. RAOCs or SAOCs.

19.2.2. NWS.

19.2.3. Air Forces Iceland (AFI).

19.2.4. E-3s.

19.2.5. OTH-B operations centers.

19.2.6. Radar sites with operators.

19.3. Submitted To:

19.3.1. NORAD ADOC.

19.3.2. SAOCs submit to NORAD regions.

19.4. When Submitted:

19.4.1. ECTAR. Submit when EA is first encountered by a NORAD C3 element. Reporting agencies report EA experienced by fighters under their control. Use ECSUM reports once the presence and location of a hostile EA force has been established near or in a region, North Warning System (NWS), or Greenland, Iceland, and Norway (GIN) sector.

19.4.2. ECSUM. Submit report when:

19.4.2.1. C3 element degradation due to EA and any changes in degradation.

19.4.2.2. Type of EA and any changes in EA type.

19.4.2.3. Cessation of EA activity; that is, when an element previously reporting EA is receiving no active EA and no new chaff drops are seen.

19.4.2.4. ECTAR and ECSUM. During exercise, do not submit to ADOC unless directed by the exercise fragmentary order.

19.5. How Submitted:

19.5.1. Classification. UNCLASSIFIED.

19.5.2. Method of Transmission:

19.5.2.1. Primary. Send ECTAR and ECSUM reports to ADOC by high speed forward tell.

19.5.2.2. Alternate. Use DSN or NTAS as an alternate means to ADOC. Exceptions:

19.5.2.3. Send ECTAR and ECSUM reports for AFI to NORAD ADOC via Rockville.

19.5.2.4. Send ECTAR and ECSUM reports from E-3 aircraft under the OPCON of a RAOC or SAOC to the NORAD ADOC.

19.5.2.5. Send ECTAR and ECSUM reports via high frequency radio-phone patch to the NORAD ADOC when AWACS aircraft are under the OPCON of CINCNORAD.

19.5.2.6. Sent ECTAR and ECSUM reports from OTH-B to ADOC via NORAD regions.

19.5.2.7. In the event of outages, send ECTAR or ECSUM reports to ADOC by voice. Do not sent an ECTAR or ECSUM when in autonomous operations.

Note: Radar sites with operators send ECTAR and ECSUM reports to the parent region or sector, by voice, when electrical communications are not available.

19.5.3. Precedence. IMMEDIATE.

19.5.4. MINIMIZE. Unaffected by MINIMIZE.

19.6. Report Indicator. Not applicable.

19.7. Specific Reporting Instructions:

19.7.1. Additional ECTARs may be sent to provide significant new information; ie., a new axis of attack.

19.7.2. After an ECSUM report is sent, a negate ECSUM must first be sent before the ECTAR message can be sent.

19.7.3. Voice reports follow SURTAC formats to expedite data entry at ADOC. Identify voice reports by the words "ECTAR" or "ECSUM" to help the recorder. Transmit all letter entries in the format phonetically.

19.8. Report Content. See paragraph 19.1.2.

19.9. Sample Report. None.

19.10. Headquarters Functional Manager. CMOC, Chief, Air Defense Operations Branch (J/3OA).

Chapter 20

LOGISTICS STATUS REPORT (LOGSTAT)

20.1. Purpose. This report contains information on the NORAD Regions ability to logistically support operations. It details the status of deployments, infrastructure, munitions, and logistics limiting factors. This report also serves as a mechanism for Regions to request assistance from HQ NORAD J4 on difficult issues which might be beyond their means to resolve.

20.2. Submitted By. NORAD regions.

20.3. Submitted To. CMOC CHEYENNE MTN AS CO//BSSC//.

20.4. When Submitted. See NI20-1.

20.5. How Submitted:

20.5.1. Classification. SECRET.

20.5.2. Method of Transmission:

20.5.2.1. Primary. AUTODIN.

20.5.2.2. Alternate. WIN.

20.5.3. Precedence. See NI20-1.

20.5.4. MINIMIZE. Unaffected by MINIMIZE.

20.6. Report Indicator. Not applicable.

20.7. Specific Reporting Instructions. See NI20-1.

20.8. Report Content. See NI20-1.

20.9. Sample Report. See NI20-1.

20.10. Headquarters Functional Manager. HQ NORAD/USSPACECOM, Director for Logistics (N/SPJ4).

PART THREE

SITUATION MONITORING

Chapter 21

INTELLIGENCE REPORT (INTREP)

21.1. Purpose. This report is designed to report essential intelligence that may have an immediate and significant effect on current defense planning and operation. In addition, it provides a summary of significant events of an overflight, interception, air battle, or hijacking.

21.2. Submitted By. All echelons under the operational control of CINCNORAD.

21.3. Submitted To:

21.3.1. COMBINED INTEL CENTER CHEYENNE MTN AS CO//J2FW//.

21.3.2. Units under operational control of NORAD regions report to the region headquarters.

21.3.3. U.S. regions forward INTREPs of interest to NORAD using AIG 910.

21.3.4. Canadian NORAD region replies only to addressees in ACDP 100.

21.3.5. HQ NORAD forwards INTREPs of national interest to AIG 930, and CDS,
Ottawa, Ontario, Canada.

21.3.6. Submit special intelligence (SI) information to HQ NORAD/J2FW. HQ NORAD submits SI INTREP information of national interest to DAG "KODAV."

21.4. When Submitted. Submit an INTREP promptly (within 1 hour after the information is received) whenever a critical development appears imminent or is of unusually high interest to decision makers; such as, air battles in progress, significant air intercepts and activities, or other significant air intercepts and activities, or other significant events. Regions may establish more specific reporting requirements for subordinate units as appropriate.

21.5. How Submitted:

21.5.1. Classification. Determined by content of report.

21.5.2. Method of Transmission:

21.5.2.1. Primary. TTY.

21.5.2.2. Alternate. DSN (secure or nonsecure voice).

Note: Urgency may dictate the use of telephone (unsecure or secure) consistent with the classification of the information. Follow-up with an AUTODIN message per paragraphs 23.3 and 23.4. Units without AUTODIN message capability transmit by voice to the parent operational facility.

21.5.3. Precedence. Use either FLASH or IMMEDIATE as determined by the sender.

21.5.4. MINIMIZE. Unaffected by MINIMIZE.

21.6. Report Indicator. SP.

21.7. Specific Reporting Instructions. When submitting:

21.7.1. Submit according to AFP102-2 VI.

21.7.2. Do not use the INTREP in lieu of critical intelligence reports (CRITIC).

21.7.3. Do not delay the report pending verification or the collection of more detail. Use a follow-up INTREP to send additional information. Make sure reference is made to previous reports of the same event.

21.8. Report Content. Include at least the following information (in the order listed) in the narrative:

21.8.1. What is the nature of the event?

21.8.2. When did the event occur? (Express by date-time group using Zulu time.)

21.8.3. Where did the event take place? (Express in geographic coordinates to nearest second. If above or below the surface, give best estimate of altitude or depth.)

21.8.4. What is the source of the information? (Include reliability data.)

Note: Include in the remarks only essential data pertaining directly to the event.

21.9. Headquarters Functional Manager. CMOC, Chief, Combined Intel Watch (J2W).

Chapter 22

DAILY INTELLIGENCE SUMMARY (DISUM)

22.1. Purpose. This report provides CINCNORAD with an analysis of the hostile situation and a summary of all significant intelligence produced during the preceding 24-hour period or after attack has ended.

22.2. Submitted By. Region intelligence staffs.

22.3. Submitted To. CMOC COMBINED INTEL CEN CHEYENNE MTN AS CO//J2FW// and AIG 910.

22.4. When Submitted:

22.4.1. Submit at 2300Z each day when one or more of the following conditions pertains:

22.4.1.1. When DEFCON 3 or higher degree of readiness is established Command wide or when there is a significant political-military situation developing which may require action by CINCNORAD or higher level.

22.4.1.2. When specifically directed by CINCNORAD.

22.4.1.3. At any other time considered appropriate by the reporting region.

22.4.2. Submit within 1 hour after the termination of any air battle phase by the region concerned. (On any Zulu day in which an end-of-battle DISUM has been submitted, the daily DISUM consists of updating information. lf no updating information exists, send a negative report.)

22.5. How Submitted:

22.5.1. Classification. Determined by contents.

22.5.2. Method of Transmission:

22.5.2.1. Primary. AUTODIN.

22.5.2.2. Alternate. DSN (secure voice). Transmit record copy to HQ NORAD/J2FW. However, if the report is not lengthy, a secure telephone may be used, consistent with the classification of the information.

22.5.3. Precedence. Use PRIORITY during DEFCON 5 or 4. At DEFCON 3 or higher condition of readiness, a higher precedence may be used if considered necessary by the originator.

22.5.4. MINIMIZE. Unaffected by MINIMIZE.

22.6. Report Indicator. DI.

22.7. Specific Reporting Instructions. Submit according AFP102-2V1.

22.8. Report Content. The report contains:

22.8.1. Significant intelligence generated by the reporting region in the preceding 24-hour period under DEFCON 3 or higher state of readiness.

22.8.2. Information to update the end-of-battle DISUM.

22.8.3. Amplification of information reported in INTREPs.

22.8.4. New and unreported information on enemy tactics and characteristics and performance of enemy equipment.

22.9. Headquarters Functional Manager. CMOC, Combined Intelligence Center (J2TW).

Chapter 23

REPORTING VITAL INTELLIGENCE SIGHTINGS (CIRVIS)

23.1. Purpose. This report provides for the peacetime reporting (DEFCONs 5 and 4) of intelligence sightings of vital importance to the security of the U.S. and Canada.

23.2. Submitted By. Any individual of NORAD-assigned units.

23.3. Submitted To. Nearest NORAD ground facility for relay to CMOC/J2W Combined Intelligence Watch. If sent to NORAD by message, the ACTION addressee is: CMOC COMBINED INTELLIGENCE CENTER CHEYENNE MTN AS CO//J2TW//.

23.4. When Submitted. Submit promptly after sighting.

23.5. How Submitted:

23.5.1. Classification. UNCLASSIFIED.

23.5.2. Method of Transmission:

23.5.2.1. Primary. DSN (secure or nonsecure voice).

23.5.2.2. Alternate. AUTODIN.

23.5.3. Precedence. FLASH. (Use the word "CIRVIS" three times preceding a radio message from an aircrew.)

23.5.4. MINIMIZE. Unaffected by MINIMIZE.

23.6. Report Indicator. CI.

23.7. Specific Reporting Instructions:

23.7.1. Report the following sightings:

23.7.1.1. Hostile or unidentified aircraft which appears to be directed against the US or Canada.

23.7.1.2. Hostile missiles.

23.7.1.3. Hostile or unidentified submarines.

23.7.1.4. Hostile or unidentified groups of military surface vessels.

23.7.2. Do not duplicate other operational requirements. Submit CIRVIS reports only on sightings not required to be reported through operational channels; for example, surveillance radar will not report aircraft.

23.8. Report Content. Use the following format when reporting identifiable objects:

23.8.1. Identity of observer.

23.8.2. Object sighted to include number of aircraft, missiles, and so forth.

23.8.3. Position in latitude, longitude, heading, and altitude, if appropriate.

23.8.4. Date and time of sighting.

23.9. Headquarters Functional Manager. CMOC, Combined Intelligence Center (J2W).

Chapter 24

CRITICAL INTELLIGENCE REPORT (CRITIC)

24.1. Purpose. This report is designed to report foreign developments believed to be of such potential importance to the US and Canadian Governments that it may require the immediate attention of the President or Prime Minister or other members of the National Security Council (NSC). It includes, but is not limited to, information about events, such as, outbreak of war, political and military upheavals, attacks, or major acts of sabotage against US or Canadian forces or installations, assassinations of key leaders, and decisions and actions by foreign governments which could significantly jeopardize US or Canadian interests.

24.2. Submitted By. HQ NORAD and all RAOCs and SAOCs.

24.3. Submitted To. Use Handbook of Standard Operating Procedures for Reporting of Critical Information, 1 November 1992.

24.4. When Submitted. See paragraph 24.3.

24.5. How Submitted:

24.5.1. Classification. Classification depends on content.

24.5.2. Method of Transmission. See paragraph 24.3.

24.5.3. Precedence. FLASH.

24.5.4. MINIMIZE. Unaffected by MINIMIZE.

24.6. Report Indicator. CR.

24.7. Specific Reporting Instructions. Number CRITIC messages in an annual sequence beginning with the number 1; for example, CRITIC 1-95.

24.8. Report Content. Use a narrative report and include:

24.8.1. Nature of the event.

24..8.2. When the event occurred.

24.8.3. Where the event took place (use geographic coordinates).

24.9. Headquarters Functional Manager. CMOC, Combined Intelligence Center (J2W).

RODNEY S. LUSEY, Colonel, USA
Joint Secretary

DISTRIBUTION: X

CANADIAN FORCES UNITS AND ORGANIZATIONS

CDS NDHQ 101 Colonel By Drive, Ottawa, ON Canada, K1A OK2 ........................................................... 1
NDHQ/CADO, 101 Colonel By Drive, Ottawa, ON, Canada K1A OK2 ....................................................... 4
Command Post, 5 Wing, Goose Bay Airport, Labrador, NFLD Canada AOP 1SO ..................................... 1
Wing Commander/Pubs General Stores (441 WCOC/QRA/WOPSO/INTEL), 1
19 Wing Comox, Lazo, BC Canada VOR 2KO
 
 
Wing Commander/WOpsO/CO 226 AC&W Sq 9 Wing Gander, PO Box 6000,
 
Gander, NFLD, Canada A1V 1X1 ................................................................................................. 1
Wing Commander/WOpsO-1/WCOC-3/CO 425 Sqn/CO 433 Sqn, 3 Wing, Alouette,
 
QB, Canada GOV 1AO ................................................................................................................ 2
425 TFS/CO, 3 Wing, Alouette, QUE Canada GOV 1AO .......................................................................... 2
433 TFS/CO, 3 Wing, Alouette, QUE Canada GOV 1AO .......................................................................... 2
410 TF(OTS)/CO, 4 Wing, Medley, AB Canada TOA 2MO ....................................................................... 2
416 TFS/CO, 4 Wing, Medley, AB Canada TOA 2MO ......... ...................................................................... 2
441 TFS/CO, 4 Wing, Medley, AB Canada TOA 2MO ............ .................................................................. 2
NDHQ/CADO, Ottawa, ON Canada K1A OK2 ........................................................................................... 2
CDS, NDHQ, ON Canada K1A OK2 .......................................................................................................... 2
AIRCOM HQ/SSO ACS, Westwin, MB Canada R3J OTO ........................................................................ 3
MARLANT HQ/N3, FMO Halifax, NS CN B3K 2XO ................................................................................... 1
NCOIC, Pubs DMCC, 42 Radar Squadron, Medley, AB Canada TOA 2MO .............................................
NCOIC, Pubs, 12 Radar Sqn, 3 Wing, Alouette, QUE Canada GOV 1AO ................................................
2
2

AIR COMBAT COMMAND ORGANIZATIONS

1 AF/DODA, 501 Illinois Avenue, Ste 2, Tyndall AFB, FL 32403-5548 ...................................................... 1
12 AF/DO, 5325 E. Kachina, Davis-Monthan AFB AZ 85707-4921 ............................................................ 2
57 WG/CP, 4370 N. Washington, Ste 14, Nellis AFB NV 89191-7076 ....................................................... 1
USAF WS/CO, 4325 Tyndall Ave, Nellis AFB NV 89191-6075 .................................................................. 1
4 FW/CP, 1055 Arnold Ave, Ste 118, Seymour-Johnson AFB NC 27531-2201 ......................................... 1

AIR NATIONAL GUARD AND AIR DEFENSE ORGANIZATIONS

NOTE: OGs are responsible for distribution within units and to associated alert detachments.
NGB/XO-2/CF-1/DAP-2, 2500 Army Pentagon, Wash DC 20310-2500 ..................................................... 5
101 ARW/OG, Bangor IAP (ANG) ME 04401-3099 ................................................................................... 2

NAVY/MARINE UNITS

Commanding Officer, VF-101, NAS Oceana, Virginia Beach VA 23460 .................................................... 2
Commanding Officer, VF-124, NAS Miramar, San Diego CA 93145 .......................................................... 2
Commanding Officer, VF-171, NAS Oceana VA 23460 ............................................................................. 1
Commanding Officer, MAG 31, MCAS Beaufort SC 29902 ....................................................................... 1
Commanding Officer, VMFA-251, MCAS Beaufort SC 29902 ................................................................... 1
Commanding Officer, VMFAT-101, MCAS El Toro, Santa Anna CA 92709 ............................................... 1

OTHER AGENCIES/ UNITS

Redistributed by: Secretary, JCS, Pentagon, RM 2E29 Wash DC 20318-7000 ......................................... 6
Chief of Naval Operations ....................................................................................................................... 2
Chief of Staff, USAF ............................................................................................................................... 2
Commandant, USMC .............................................................................................................................. 2
USCENTAF A3/5-DO, 524 Shaw Dr, Ste 204, Shaw AFB SC 29152-5029 ................................................ 2
JOINT STAFF/J3, Pentagon, RM 2D874, Wash DC 20318-3000 .............................................................. 2
JOINT STAFF/J36-1/DSOD-1/NOCCD-1, Pentagon, Wash DC 20318-3000 ............................................. 3
JCS, Joint War Room Agency (SAGA, Pentagon, Rm 10957), Wash DC 20318-3000 .............................. 1
AUL/SE, 600 Chennault Circle, Maxwell AFB AL 36112-6428 ................................................................... 1
HQ USAF/XO, 1630 Air Force Pentagon, Wash DC 20330-1630 ............................................................... 2
HQ USAF/XOOT, 1480 Air Force Pentagon, Wash DC 20330-1480 ......................................................... 1
FEMA, Classified Documents Control, Federal Center Plaza, 500 C St SW, Wash DC 20472 ................... 9
ANMCC/Ops, Site-R, 360 Banfill Ave, Fort Richie MD 21719-4000 ........................................................... 4
CINCLANTFLT/J3, 1562 Mitscher, Ste 250, US Naval Base Norfolk VA 23611-2487 ................................ 2
CINCPAC/J3, Camp H. M. Smith HI 96861-5025 ..................................................................................... 2
USCINCSO/J3, APO Miami FL 34003 ...................................................................................................... 2
437 AW/CP, 221 North Bates St, Charleston AFB SC 29404-2133 ........................................................... 2
HQ FORSCOM/AFDP-AV/, Fort McPherson, Maxwell AFB AL 30330-6000 .............................................. 1
COMICEDEFOR/J51, PSC 1003, PO Box 1, FPO AE 09728-0301 .......................................................... 1

Total: 100

ACRONYMS

ABO - airborne order
ACC - Air Combat Command
ACDP - Air Command General Defence Plan
ACE - alternate command element
AC&W - Air Control and Warning
ADOC - air defense operations center
ADW - air defense warning condition
AEW&C - airborne early warning and control (includes E-3 and E-2 aircraft)
AFI - Air Forces Iceland
AFOSC - USAF Operations Support Center
AICU - ADVANCED INTERFACE CONTROL UNIT
AIG - address indicating groups
AIRCOM - Canadian Air Command
ALCM - air launched cruise missile
ANG - Air National Guard
ANGRC - Air National Guard Readiness Center
ANR - Alaskan NORAD Region
ARS - aerospace reporting system
ARTCC - air route traffic control center
ATC - air traffic control
ATCC - air traffic control center
AUTODIN - automatic digital network
BSSC - battle staff support center
CAC - combat alert center
CANR - Canadian NORAD Region
CAP - combat air patrol
CB - chemical or biological
CCC - Combined Command Center
CCI - command and control identifier
CD - Command Director
CDS - Chief of Defence Staff
CE - Canada East
CF - Canadian Forces
CID - Central Intelligence Directive
CIRVIS - reporting vital intelligence sightings
CIS - Commonwealth of Independent States
CMAS - Cheyenne Mountain Air Station
CMOC - Cheyenne Mountain Operations Center
COC - combat operations center
COMSEC - communications security
CONR - CONUS NORAD Region
CP - command post
CRITIC - critical intelligence report
CRP - common reference point
CSAF - Chief of Staff Air Force
CW - Canada West
DEFCON - defense readiness condition
DIA - defense intelligence agency
DISUM - daily intelligence summary
DLRN - data link reference number
DMA - dangerous military activity
DSN - defense switching network
DTG - date-time group
EAC - emergency action controller
EMI - electromagnetic interference
EA - electronic attack
ECSUM - Electronic Countermeasures Summary Report
ECTAR - Electronic Countermeasures Tactical Action Report
EFTO - encrypt for transmission only
EMI - Electro-magnetic interference
EOC - emergency operations center
EP - electronic protection
ES - electronic support
ETIC - estimated time in commission
ETRO - estimated time return to operation
FAA - Federal Aviation Administration
FMC - fully mission capable
GCCS - global command and control system
GIN - Greenland, Iceland, and Norway
GLASSEYE - pilot observation reports of post-attack damage
GP - general purpose
GTACS - ground tactical air control system
HQDP - Canadian Forces General Defence Plan
ICADS - Iceland Air Defense Sector
ICAO - International Civil Aviation Organization
IFF/SIF - identification friend or foe/selective identification feature
INTREP - Intelligence Report
IP - initial penetration
JCS - Joint Chiefs of Staff
JMCIS - Joint Maritime Command Information System
JOTS - Joint Operations Tactical Systems
JRS - Joint Reporting System
JSS - Joint Surveillance System
JTF - Joint Task Force
KIA - killed in action
LERTCON - alert condition
LOGSTAT - Logistics Status Report
LOSREP - Aircrew and Aircraft Loss Report
LRR - long range radar
LRS - Logistics Reporting System
MAJCOM - major command
MCCC - mobile consolidated command center
MIA - missing in action
MSO - mandatory scramble order
NABS - NORAD Airborne Battle Staff
NAS - NORAD Alerting System
NBC - nuclear, biological, and chemical
NBCOC - nuclear, biological, and chemical operations center
NCA - National Command Authorities
NDHQ - National Defence Headquarters Canadian
NDOC - National Defence Operations Center Canadian
NMC - non-mission capable
NMCC - National Military Command Center
NSC - National Security Council
NSEWR - no site equipped within range
NTAS - NORAD Tactical AUTOVON Systems
NTDS - Naval Tactical Data Systems
NUDET - nuclear detonation

NWS - North Warning System
OC - operations center
ODC - operations dispatch center
OPCON - operational control
OPLAN - operation plan
Opord - operation order
OPREP - Commander's Operational Report
OSI - Office of Special Investigations
OTH-B - over-the-horizon backscatter radar
PACCS - Post-Attack Command and Control System
PMC - partially-mission capable
POW - prisoners of war
QLCI - quick look capability index
RA - reporting agency
RAF - Royal Air Force
RCC - rescue coordination center
RAOC - region operations control center
ROTHR - relocatable over-the-horizon radar
RP - Response Posture
RTB - return to base
STRATCOM - Strategic Command
SAR - search and rescue
SI - special intelligence
SIF - selective identification feature
SITREP - Commanders Situation Report
SAOC - sector operations control center
SORTS - Status of Resources and Training System
SPIREP - Spot Intelligence Report
SPOC Space operations Center
SRR - short range radar
SSO - special security office
SURTAC - Data Speed 40 Teletype System
TARS - tethered aerostat radar system
TEMPREP - temporary report
TOR - terms of reference
TTY - teletype
USMC - United States Marine Corps
USMTF - United States Message Text Formats
USN - United States Navy
WIA - wounded in action
WIN - WWMCCS Intercomputer Network
WWMCCS - World Wide Military Command and Control System

STANDARD CODES - DESIGNATORS AND IDENTIFIERS

A2.1. General. These designators and identifiers are used to identify the source of surveillance and tactical data. They apply to all sources which contribute to the NORAD systems; for example, NORAD regions and sectors, GIN, and airborne early warning and control (AEW&C) sources.

A2.2. Single-Letter Designators. These single-letter designators are assigned as follows:

DESIGNATORSOURCE

A OTH-B (ECRS) S CE SAOC
B NE SAOC T TEST TRACKS
C SE SAOC U NOT USED
D ROTHR MT V JVIDS
E ROTHR TX W CW SAOC
F WADS FTR STRG X CE AWACS
G ROTHR VA Y OTH-B (WCRS)
H CW AWACS Z ANR RAOC
I IADS AWACS 0 INVALID
J WADS SOUTHERN AACS 1 INVALID
K NE SAOC AWACS 2 PACCS AIRCRAFT
L NAVY 3 BATTLE MGMT INFO SYS (BMIS)
M ANR AWACS 4 NOT USED
N SE SAOC AWACS 5 NSSF ADNET INTERNAL TEST
O ICERAOC/IADS 6 NOT USED
P TRAINING TRACKS 7 NOT USED
Q WADS NORTHERN AWACS 8 NOT USED
R WADS OPS STRNG 9 NOT USED

A2.3. Facility Identifiers. ECTAR and ECSUM reports require identification of the facility involved or site submitting the report. These identifiers are:

A2.3.1. AEW&C Radars. The facility identifier consists of:

A2.3.1.1. Element one, single-letter designator of the region in which an AEW&C aircraft is operating

A2.3.1.2. Element two, "X" denotes an AEW&C aircraft.

A2.3.1.3. Element three as follows:

A2.3.1.3.1. Letter "A" - NORAD airborne control center (NACC).

A2.3.1.3.2. Letter "B" through "M" - E-3 patrol aircraft.

A2.3.1.3.3. Letter "N" through "Z" - E-2 patrol aircraft.

A2.3.2. Ground Radars. The facility identifiers for ground radar sites consist of three alphanumeric characters which are the assigned site designators for the affected site (i.e., J16, R06, A07, B41, NG1, etc.).

TRACK AND SOURCE DESIGNATORS

A3.1. General. Each track is assigned a track designator which consists of two letters (source designators) and three numbers (track numbers).

A3.2. Source Designators:

A3.2.1. For all tracks told to ADOC, the first letter is the single letter designator of the source reporting the track to ADOC, and the second letter is the single-letter designator of the originating source which initiated the track (see paragraph A2.2 for single-letter designators).

A3.2.2. For tracks up-told to the AEW&C, the single-letter designator of the originating source is converted to the AEW&C code (first number of the Data Link Reference Number (DLRN)) assigned below:

ORIGINATING
 
SOURCE DESIGNATOR
AEW&C CODE
W. L, U 1
S. E, P 2
C 3
B 4
R 5
F 6
Z. D, G. T. 7
 
 

A3.2.3. When an AEW&C aircraft is assigned to support NORAD, use the appropriate DLRN for all AEW&C aircraft operating within the region's area of responsibility. For down-told, AEW&C tracks, the code is converted to an AEW&C single-letter designator. The areas, AEW&C codes, and single-letter designators are assigned below:


AREA
AEW&C
CODE

DESIGNATOR
WADS SOUTHERN AREA 1 J
WADS NORTHERN AREA 2 Q
CE 3 X
CW 4 H
SE SAOC 5 N
ANR RAOC 6 M
IADS 6 I
NE SAOC 7 K

A3.2.4. Tracks up-told or down-told between ground facilities and AEW&C aircraft, and which are subsequently re-told to the ground facility or AEW&C aircraft, retain their original AEW&C or single-letter designator.

A3.2.5. For GIN tracks directly told to ADOC or RAOC/SAOC, the first letter is "T" and the second letter is the single-letter designator of the originating source.

A3.3. Track Numbers. Track numbers follow the two-letter designators to complete the track identification. Number assignments are:

A3.3.1. 001-677 (OCTAL). RAOC/SAOC initiated tracks.

A3.3.2. 700-776 (OCTAL). Navy initiated tracks.

A3.3.3. 001-776 (OCTAL). All GIN initiated tracks.

A3.3.4. 001-776 (OCTAL). All AEW&C initiated tracks.

A3.4. Examples of Surveillance Track Designators:

A3.4.1. ZZ 310:

A3.4.1.1. Z - ANR RAOC is reporting the track.

A3.4.1.2. Z - ANR RAOC is originating source.

A3.4.1.3. 310 - Track number.

A3.4.2. BS 210:

A3.4.2.1. B - NE SAOC is reporting the track.

A3.4.2.2. S - (CE) SAOC is originating source.

A3.4.2.3. 210 - Track number.

A3.5. Fighter Track Designators:

A3.5.1. All fighter track designators consist of three letters and two numbers. The first letter is the single-letter designator of the reporting source. The combination of the next two letters and two numbers indicate the fighter squadron's phonetics voice call sign and individual aircraft number. Any letters except "0" or PI" can be used to form the squadron call sign. A third letter in combination with any second letter indicates a "special designated fighter." The individual aircraft number can be 01 through 31 (decimal), inclusive.

A3.5.2. The following are standard callsign assignments for NORAD alert forces. Region or sector discretion applies whenever non-standard or rotating callsigns are used; however, the two letter assignment used to represent a non-standard or rotating callsign must be common among aircraft sharing that callsign and must not conflict with the following:

A D
CANR
Cold Lake
410 TSF
A K
NEADS
Otis
102 FW
A N
WADS
Fresno
144 FIW
A P ANR Elmendorf
Galena
King Salmon
3FW
3FW
3FW
C M
SEADS
New Orleans
159 FW
E H
SEADS

Jacksonville
Key West
125 FW
Det 2, 125FG
E L
NEADS
Atlantic City
177 FW
G N
CANR
Cold Lake
416 TFS
H G

CANR
Cold Lake
Comox
441 TFS
Det, 441 TFS
H F
CANR
Cold Lake
419 TFS
K N
CANR
Goose Bay
425 TFS
K P
ANR
Elmendorf
Galena
King Salmon
3FW
3FW
3FW
K U
CANR
Cold Lake
410 TFS
M L NEADS
SEADS
Duluth
Tyndall
148 FW
Det 1,148 FW
M P
WADS
WADS
Fargo
March
119 FW
Det 1, 119 FW
N L
WADS
WADS
Great Falls
Davis-Monthan
120 FW
Det 1, 120 FW
P G
WADS
Portland
142 FW
P N
WADS
Fresno
144 FW
T C
ANR

Elmendorf
Galena
King Salmon
3FW
3FW
3FW
U G
SEADS
Ellington
147 FW
V P

ANR

Elmendorf
Galena
King Salmon
3FW
3FW
3FW
V T SEADS Charleston Det, 158 FW

MESSAGE FORMATS - FORWARD TELL

A4.1. Line Check Message. Systems continuity between CMOC, NORAD regions and sectors, and GIN is monitored by means of a line check message. Except as noted below, the line check message is automatically generated.

A4.1.1. Message Content:

LINE
FIELD
FIELD NAME
RV
REMARKS
1
1
Msg Identifier
LCK
Line check.

2
Source Identifier
a
a - Region single-letter designator. (See attachment 4.)

3
Time
nnnn
0000-2359 (Zulu time to nearest minute.)

A4.1.2. Sample Message. Message from WADS to NORAD ADOC:

LINE 1 FIELD 1 - Line check (end of Field 1)

2 - WADS single-letter designator (end of Field 2)

3 - Zulu time of report (end of Field (3)/Line 1)

A4.1.3. Submission: NORAD RAOCs and or SAOCs send a line check message to the NORAD ADOC automatically when no other data has been sent in the last 5 minutes.

A4.2. E-3 (AWACS) Status Message. Message Content:

NO FIELD NAME SIZE RV AMPLIFYING DATA
 
 
 
 
 
1 Message Identifier 3 ASA Actual Data
 
 
XSA Exercise Data
 
 
 
 
 
 
2 Source and Type 1 a B = NE SAOC
 
 
 
 
C = SE SAOC
 
 
 
 
F = WADS FGTR STRNG
 
 
 
 
O =Iceland RAOC
 
 
 
 
R = WADS OPS STRNG
 
 
 
 
S= CE SAOC
 
 
 
 
W = CW SAOC
 
 
 
 
Z = Alaska RAOC
 
 
2 AT Invariant

Note: CINCNORAD E-3 status will be manually input by ADOC personnel.

3
Time
2
00-23
Hour (Zulu time to nearest minute)


2
00-59
Minute
4
Airborne
2
00-63
Number of E-3s Airborne.
5
Airborne Order
2
00-63
Number of E3s committed to Airborne Order (ABO).
6
Runway Alert
2
00-63
Number of E3s committed to Alert Runway.
7
Battle Stations
2
00-63
Number of E3s committed to Battle Stations.
8
RP 30
2
00-63
Number of E3s on 30 Minute Minutes Response Posture.
9
RP 1 HOUR
2
00-63
Number of E3s on One Hour Response Posture.
10
RP 3 HOURS
2
00-63
Number of E3s on Three Hour Response Posture.
11
RP 6 HOURS
2
00-63
Number of E3s on Six Hour Response Posture.
12
Generating
2
00-63
Number of Fully Mission Capable (FMC) E3s not on a Response Posture due to turn-around, crew rest, etc.
13
Non-Mission Capable
2
00-63
Number of Non-Mission Capable (NMC) E3s.

A4.3. Track Message - For voice reporting, use the Track/Point Report (TRKREP) message text format, reporting Weapons Committed and Kills in the narrative portion of the format. If the report contains classified information and secure communications are not available, encrypt using KL-43/AKAK-3868.

A4.4. Electronic Countermeasure Status (ECTAR and ECSUM) Messages - For voice reporting, use the EA Data Message (ECKDAT) message text format, reporting Type EA or Negate and (for ECSUM) degree of degradation in the narrative portion of the format. If the report contains classified information and secure communications are not available, encrypt using KL-43/AKAK-3868.

MESSAGE FORMATS - VOICE TELL

A5.1. Track/Point Report (TRKREP) Format. When a new track is voice told, use the following sequence in the NORAD environment:

A5.1.1. (Receiver) THIS IS (Sender). TRACK REPORT, OVER.
(Include classification if report is not UNCLASSIFIED)

A5.1.2. ID (Hostile/Faker/Unknown/Pending/Special 25, etc.).

A5.1.3. POSITION (latitude/longitude).

A5.1.4. TRACK (NORAD track number).

A5.1.5. HEADING (degrees).

A5.1.6. SPEED (knots).

A5.1.7. ALTITUDE (in hundreds of feet).

A5.1.8. ENGAGED (yes or no).

A5.1.9. NOTYPE (number and type of aircraft, or unknown).

A5.1.10. SQUAWK THREE (mode 3/A squawk, or negative).

A5.1.11. MODE FOUR (confirmed friend, no response, or not interrogated).

A5.1.12. CATEGORY (air, surface, or point).

A5.1.13. TIME (effective time of information reported).

A5.1.14. NARRATIVE (determined by sender).

A5.2. Revision Report. Using the TRKREP format, transmit only the ID, Position, Track Number, those portions of the TRKREP which have changed since last reported, and Time.
Example: BEST DEAL, this is OAK GROVE. Track Report, Over.
Go Ahead.
ID: Unknown. Position: Two Nine Four Five North, Zero Eight Zero Three West.
Track: Charlie Two Five Six. Altitude: One Two Zero. Time: Sixteen Forty Two. Narrative:
Rapidly Descending. Echo Hotels have positive radar contact.

A5.3. Drop Track Report. Using the TRKREP format, transmit only the ID, Position, Track Number, (Narrative: Drop Track,) and Time.

A5.4. Orbit Report. When a track appears to be orbiting, transmit a Revision Report, using the known/estimated center of the orbit for the position and including the phrase "Orbiting (Left or Right) in the Narrative. In automated systems, orbits are normally represented by zero velocity tracks.

A5.5. Split Track Report. If a track splits into two or more segments, the track with the greatest and most immediate threat potential retains the original track designator (regardless of the deviation from the original heading). Split tracks are reported as a new track, with the phrase, "Spawning from Track Number."

A5.6. Merged Track Report. When two or more tracks of the same classification (such as ID) merge to form one track, that track is reported as one track (with a change in the number of objects). If only one of the merge tracks is paired against, the merged track retains the track number against which the track was paired. If more than one of the merging tracks has been paired against, or if no merging track has been paired against, then retain the highest track number. The Narrative portion of the TEKREP for the retained track includes the phrase, "Merged Track from (Track Number(s)).

A5.7. Contact Lost Report. If an established track does not appear for a period of 2 minutes, use following format:

A5.7.1. Track designator.

A5.7.2. Contact lost.
Example: Charlie two four one, contact lost.

A5.8. Mass Track Report. Mass tracks result when a number of established tracks within a 10-mile radius and having similar characteristics are grouped under one track designator. Mass tracks are reported in the TRKREP format with the appropriate flight size in NOTYPE and the phrase, "MASS TRACK" in the Narrative.

A5.9. Emergency Report. When tracks display emergency IFF/SIF mode codes, transmit a Revision Report including the Squawk Three and include the nature of the emergency, if known, in the Narrative.

A5.10. Priority Telling Procedures:

A5.10.1. Use these general priorities for FORWARD TELL of track data:

A5.10.1.1. Priority 1 - Hostile or Faker.

A5.10.1.2. Priority 2 - Unknown or Pending.

A5.10.1.3. Priority 3 - Emergency or Hijack.

A5.10.1.4. Priority 4 - Special Tracks.

A5.10.1.5. Priority 5 - Fighter.

A5.10.1.6. Priority 6 - VIP Flights.

A5.10.1.7. Priority 7 - Other (as directed by ADOC or NCC).

A5.10.2. Priorities 1, 2, 3, and 4 are forward told unless the receiver authority directs cease tell. All other traffic is forward told on request only.

PERSONNEL REPORTING - SITREP

A6.1. Troop Strength/Casualty Reporting:

A6.1.1. General. This attachment provides information and guidance for in-theater strength and operational casualty reporting by the NORAD regions. In order to provide timely in-theater and operational casualty reporting to CINCNORAD, report data in the daily Commander's SITREP.
"In-theater" is defined as those forces which belong to or OPCON to the NORAD region commanders filing the SITREP. Forces OPCON or (chopped) to another region will be listed under "personnel deployed outside the AOR".

A6.1.2 Troop Strength/Casualty Report Format. Use the following format, reclassified SECRET when filled in:

CMD - ANR, CANR, CONR, ETC.
SERVICE START-GAIN-LOSS-ENDING-DH-DO-WH-IOI-MIA

USA
USMC
USN
USAF
CANFOR
US CIVILIANS

TOTAL

A6.1.3 Personnel deployed outside the AOR:

#s Military #s US Civilian Remarks
LOCATION(S)

NOTES:
1. Put numbers of personnel OPCON or deployed to another region in this section.

2. For small numbers of personnel put the specific location they are deployed to. For large numbers deployed, list the region as the location.

3. The reason for tracking US Civilians is to meet the Joint Staff's information requirements.

A6.1.4. Narrative Comments:. Free text to remark on any of the following:

A6.1.4.1. Changes in personnel deployed, replacement actions, callup actions, losses and gains, admin errors from previous reports, or other pertinent data.

A6.1.4.2. This narrative is also used to explain or amplify data contained in the statistical section and contains comments regarding the impact of casualties or key losses on mission attainment.

A6.1.5. Definitions:

A6.1.5.1. START. For the initial report, this number will represent the total personnel in the command. For subsequent reports the "start" figure will depict the number indicated in the previous day's "end" or end strength column. Numbers must not change between end strength on one day and start strength on the next day. Explain administrative corrections in the last paragraph of the message.

A6.1.5.2. GAIN. The number of personnel joining the command during the reporting period. Each transfer of personnel among components or regions must be reflected by a gain and a corresponding loss in the appropriate command lines.

A6.1.5.3. LOSS. The number of personnel lost from the components or regions during the reporting period, such as a transfer, a medevac, or death.

A6.1.5.4. END. The total end strength within the AOR at the end of the reporting period. Obtained by adding "start" + "gain" and subtracting "loss". This entry will match the beginning strength of the next day's report, unless administrative corrections are required. admin corrections must be explained in the narrative comments.

A6.1.5.5. DH. Death Hostile. Number of personnel who died as a result of hostile actions during the reporting period.

A6.1.5.6. DO. Death Other. Number of personnel who died as a result of accident or illness not related to hostilities during the reporting period.

A6.1.5.7. WH. Wounded Hostile. Number of personnel wounded as a result of hostile actions during the reporting period.

A6.1.5.8. IOI. Injured Other ill. Number of personnel who are injured as a result of an accident not related to hostilities or who became ill during the reporting period.

A6.1.5.9. MIA. Missing In Action. Any person whose whereabouts or actual fate can not be determined and who in not known to be in an unauthorized absence status (AWOL/desertion) following an engagement with enemy forces.

A6.1.5.10. Civilians. This is all DOD and non DOD civilians (i.e. contractors) supporting the regions. Combining the total figures for the military and civilian lines will give the total strength of all US personnel within the AOR.

A6.1.5.11. Deployment. The personnel deployed paragraph is used to report the number of personnel deployed outside the AOR (personnel who are in a deployed status outside the service members assigned region, include OPCON).