Download as pdf or txt
Download as pdf or txt
You are on page 1of 169

CUI

OPNAVINST 3100.6K
10 Aug 2021

SPECIAL INCIDENT REPORTING


(OPREP-3 PINNACLE,
OPREP-3 NAVY BLUE AND
OPREP-3 NAVY UNIT SITREP)
PROCEDURES

Controlled by: CNO WASHINGTON DC


CUI Category: OPSEC
Limited Dissemination Control: FED ONLY
POC: CNO Battle Watch Captain, 703-692-9284

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

RECORD OF CHANGES

IDENTIFICATION DATE OF DATE OF ENTRY ENTERED BY


CHANGE
OF CORRECTION
OR CHANGE

CUI
CUI
DEPARTMENT OF THE NAVY
OFFICE OF THE CHIEF OF NAVAL OPERATIONS
2000 NAVY PENTAGON
WASHINGTON, DC 20350-2000

OPNAVINST 3100.6K
N3/N5
10 Aug 2021

OPNAV INSTRUCTION F3100.6K

From: Chief of Naval Operations

Subj: SPECIAL INCIDENT REPORTING PROCEDURES

Ref: See Appendix A

1. Purpose. This instruction publishes guidance, policy and procedures for special incident
reports outlined in references (a) and (b). These reports are used to provide timely information
on critical situations and military operations. This instruction has undergone numerous editorial
and technical changes and should be reviewed in its entirety. Major changes include:

a. Commanders are required to consult with a JAG in all alleged sexual harassment cases
and are required to consult a CCS in all alleged discrimination, harassment and sexual
harassment cases.

b. Bullying has been defined and is to be tracked per the Office of Secretary of Defense
Policy Memorandum on Hazing and Bullying Prevention and Response in the Armed Forces
(December 23, 2015). Bullying has been added as an incident that may require an OPREP-3
NAVY BLUE if there is possible media attention.

c. The definition of Sexual Harassment has been updated to align with Title 10 U.S.C. 1561.

d. “Suicide-Related Behavior” has replaced various terms relating to the topic to reflect
current terminology and policy. Suicide-Related Behavior is not considered misconduct as that
applies stigma and becomes contradictory to the Navy’s desire to promote help-seeking
behavior.

e. Unmanned Systems (to include UAS) hostile action and general reporting requirements
have been added to this instruction, with reference to the current NAVADMIN guidance for
report content and message addressees and with direction to utilize current Office of the Chief of
Naval Operations (OPNAV), COCOM or FLEET guidance for report content.

f. EAM requirements have been updated for NC3, FSBS. An OPREP-3 PINNACLE is
required for a complete loss of the ability to deliver EAMs via the FSBS transmitters supporting

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

either LANT or PAC AOR or both that has no identifiable resolution or has not been resolved in
15 minutes. An OPREP-3 NAVY BLUE is required for a complete loss of the ability to deliver
EAMs via the FSBS transmitters supporting either LANT or PAC AOR or both that is resolved
in more than three minutes but less than 15 minutes.

g. Changed PLADs:

(1) DIRSSP WASHINGTON DC added for many SSBN messages and CTF 134 and
CTF 144 were replaced with addresses CTG 114.3, CTG 114.4, CTF 114 and JFMCC STRAT.

(2) NAVORDSAFSECACT INDIAN HD was changed to NAVORDSAFSECACT


INDIAN HEAD MD

(3) CJFMCCNORTH deleted.

(4) CNO added to NAVY BLUE SENTINEL for UAS tracking.

(5) Reference to ‘MISHAP Addresses’ deleted.

(6) NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC added.

h. Changed paradigm for “assessed hoaxes.” Many false reports develop into larger public
relations issues than actual bomb threats or active shooters. Reports are still expected to be
submitted for false reports or hoaxes.

i. Reduced reporting for negligent discharge, including deletion of personally identifying


information requirements.

j. Reduced reporting for motorcycle incidents, including use of mishap classification as


decision criteria for reporting incidents.

k. Direct reporting to the NMCC was added for PINNACLE reports, to better align with
reference (a), with follow up reports to MOC and the NOC. This is tempered with the
understanding that ships at sea often do not have the ability to report directly to NMCC and have
to report through the chain of command.

l. Special emphasis on NMCC reporting is placed on PINNACLE EMPTY QUIVER


reports because of the specific need for timely action directed from NMCC.

m. Voice report timeline adjusted from five minutes to 15 minutes for most reports to align
with reference (a). Of note, PINNACLE NUCFLASH is still five minutes outlined in reference
(a) and EMPTY QUIVER is still five minutes for Navy emphasis.

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

n. FADED GIANT, PINNACLE BROKEN ARROW and BENT SPEAR narratives were
modified to cross reference the presence or status of nuclear reactors and weapons onboard. This
is intended to enable initial prioritization of actions in an event that could affect both a nuclear
propulsion plant and nuclear weapons.

o. Added NAVY BLUE personnel incident reporting for supremacist or extremist groups.

p. Thresholds for reporting MSLR and AA&E were adjusted to match changes to DoD
Guidelines.

q. Development has commenced on a Personnel Incident SITREP reporting database,


similar to the COVID-19 reporting database. Implementation and use of the database will be
announced with a NAVADMIN

2. Cancellation. OPNAVINST F3100.6J.

3. Scope and Applicability. Applies to all Navy commands, afloat and ashore, including
recruiting and training commands, FMF units under U.S. Navy cognizance, MSC shore
commands, U.S. Navy ships (less foreign manned ships) and bare boat chartered ships that have
been designated public vessels of the United States. This includes Selected Reservists even
when in a non-drilling status.

4. Discussion. This instruction was developed in compliance with references (a) and (b). It is
the only OPREP-3 PINNACLE, OPREP-3 NAVY BLUE, and OPREP-3 NAVY UNIT SITREP
guidance to be used by U.S. Navy commands. Supplemental instructions by subordinate
commands may amplify, but will not modify, the structure set forth in this instruction.

a. The OPREP-3 reporting system provides military units, at any level of command, a
system to report significant events and incidents to the highest levels of command.

b. The OPREP-3 PINNACLE series messages are used to report incidents that are of
national-level interest to the NMCC.

c. The OPREP-3 WHITE PINNACLE system is used to exercise and evaluate the
timeliness of OPREP-3 PINNACLE reporting procedures.

d. The OPREP-3 NAVY BLUE series messages are used to provide the CNO and other
naval commander’s notification of incidents that are of high Navy, as opposed to national-level,
interest.

e. The OPREP-3 NAVY UNIT SITREP series messages are used to inform the operational
commander or appropriate higher authority, of incidents not meeting OPREP-3 NAVY BLUE
criteria.

f. POC by area of interest:


3

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

AREA OF INTEREST POC TELEPHONE


ATFP ATFP - OPNAV N34 703-692-8350
Defense Switched Network
(DSN) 222-8350
Classified Material Issues Information and Personnel 202-433-8841
Security - OPNAV N09N2 DSN 288-8841
Communications Security NAVWARSYSCOM) 619-524-7812
Material System Issues OT4-2070-F DSN 524-7812
Computer Intrusion and Navy Cyber Defense 1-888-NAVCIRT
Network Operations Operations Command DSN 312-537-4024
COOP Navy COOP - OPNAV 703-697-3453
N35 DSN 213-227-3453
Critical Outages NNWC BWC 757-417-6777
DSN 312-537-6777
Defense Critical Infrastructure, OPNAV Mission 703-695-5521
Task Critical Assets Assurance - OPNAV N46 DSN 312-225-5521/5022
Marine Mammal Incidents Environmental Readiness - 703-602-3028
OPNAV N45 DSN 332-3028
Media and Public Affairs CHINFO 703-697-7391
DSN 227-7391
Mishap Line COMNAVSAFECEN 757-444-2929
DSN 564-2929
MLSR Arms, AA&E or Ordnance Management 703-695-4815 or 4819
Explosive Mishaps Branch - OPNAV N411 DSN 312-225-4815 or
4819
Naval Safety Center Liaison NAVSAFECEN - OPNAV 703-602-5030
N09FB DSN 332-5030
Navy Operations Center, CNO Operations and 703-693-2006
Pentagon Information Division - DSN 223-2006
OPNAV N30
Nuclear Reactors Director, Navy Nuclear 202-781-6030 or 5851 or
Propulsion Program - 6036
OPNAV N00N DSN 326-6030 or 5851 or
6036
Nuclear Weapons Surety OPNAV N00NW 571-481-7438
DSN 225-5548 or 5544

703-695-5548 or 5544
Nuclear Weapons Surety OPNAV N971 DSN 225-5548 or 5544
Personnel Issues: Deputy CNO for
Manpower, Personnel,
Training and Education -
OPNAV N1 or CNIC
4

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

AREA OF INTEREST POC TELEPHONE


Domestic Violence CNIC Fleet and Family 202-433-4646
Support Center, DSN 288-4646
Management Support
Division - CNIC N911
Child Abuse and Neglect CNIC N911 202-433-4361
DSN 882-4361
Child Sexual Abuse CNIC N911 202-433-4361
DSN 882-4361
Sexual Assault CNIC N911 202-433-4637
DSN 288-4637
Sexual Harassment, EO, OPNAV 21st Century 800-253-0931
Hazing, Bullying and Sailor Office - OPNAV DSN 882-2507
Fraternization N173 Overseas, collect:
901-874-2507
Suicide Prevention OPNAV 21st Century 901-874-6613
Sailor Office, Suicide DSN 882-6613
Prevention Branch –
OPNAV N171
Strategy and Policy Policy and Plans - OPNAV 703-697-3650
N5 DSN 227-3650
Strategic Mobility and Combat Strategic Mobility and 703-602-7142
Logistics Combat Logistics OPNAV DSN 332-7142
N42
USMTF Issues DISA – Navy POC 619-553-0045
DSN 553-0045

5. Acronyms and Definitions. Applicable acronyms and definitions are included in appendices
G and H, respectively.

6. Records Management.

a. Records created as a result of this instruction, regardless of format or media, must be


maintained and dispositioned per the records disposition schedules located on the Department of
the Navy Assistant for Administration, Directives and Records Management Division portal page
at https://portal.secnav.navy.mil/orgs/DUSNM/DONAA/DRM/Records-and-Information-
Management/Approved%20Record%20Schedules/Forms/AllItems.aspx.

b. For questions concerning the management of records related to this instruction or the
records disposition schedules, please contact the local records manager or the OPNAV Records
Management Program (DNS-16).

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

7. Review and Effective Date. Per OPNAVINST 5215.17A, CNO N3/N5 will review this
instruction annually around the anniversary of its issuance date to ensure applicability, currency
and consistency with Federal, Department of Defense, Secretary of the Navy and Navy policy
and statutory authority using OPNAV 5215/40 Review of Instruction. This instruction will be in
effect for 10 years, unless revised or cancelled in the interim and will be reissued by the 10-year
anniversary date if it is still required, unless it meets one of the exceptions in OPNAVINST
5215.17A, paragraph 9. Otherwise, if the instruction is no longer required, it will be processed
for cancellation as soon as the need for cancellation is known following the guidance in OPNAV
Manual 5215.1 of May 2016.

8. Report Control and Forms.

a. The reporting requirements contained in this instruction are exempt reports under part IV,
subparagraph 7(g) of SECNAV Manual 5214.1.

b. The forms listed in subparagraphs 8b(1) through 8b(3) are available for download from
Naval Forms Online, https://www.public.navy.mil/bupers-
npc/reference/forms/NAVPERS/Pages/default.aspx:

(1) NAVPERS 1752/1 Sexual Assault Disposition Report.

(2) NAVPERS 5354/2 EO Complaint Form.

(3) NAVPERS 1626/7 Report and Disposition of Offenses.

Releasability and distribution:


This instruction is not cleared for public release and is available electronically only via the
OPNAV DNS-15 SharePoint Portal to users with common access card authorization,
https://portal.secnav.navy.mil/orgs/OPNAV/DNS/DNS1/DNS15/FOUO%20Directives/Forms/Al
lItems.aspx?RootFolder=%2Forgs%2FOPNAV%2FDNS%2FDNS1%2FDNS15%2FFOUO%20
Directives%2FDirectives&FolderCTID=0x0120009220AC00C6A6C342931E74D5948CAF26&
View=%7B548ECDB9%2DB0C3%2D49C7%2D8C3F%2DC2C1EA086FC1%7D

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

TABLE OF CONTENTS

Chapter 1 SPECIAL INCIDENT REPORTING (OPREP-3) SYSTEM Page


Section I DESCRIPTION 1-1
Section II POLICY 1-3
Section III RELATED REPORTS 1-6

Chapter 2 GENERAL RULES FOR OPREP-3 REPORTING


Section I GENERAL GUIDANCE 2-1
Section II VOICE MESSAGE REPORTS 2-4
Section III RECORD MESSAGE REPORTS 2-7

Chapter 3 OPREP-3 PINNACLE REPORTS


Section I OPREP-3 PINNACLE 3-1
Section II OPREP-3 PINNACLE NUCFLASH 3-7
Section III OPREP-3 PINNACLE FRONT BURNER 3-13
Section IV OPREP-3 PINNACLE BROKEN ARROW 3-19
Section V OPREP-3 PINNACLE EMPTY QUIVER 3-25
Section VI OPREP-3 PINNACLE EMERGENCY DISABLEMENT 3-31
Section VII OPREP-3 PINNACLE EMERGENCY EVACUATION 3-36
Section VIII OPREP-3 WHITE PINNACLE 3-42
Section IX OPREP-3 PINNACLE SPECIAL REPORTS 3-48

Chapter 4 OPREP-3 NAVY BLUE REPORTS


Section I OPREP-3 NAVY BLUE 4-1
Section II OPREP-3 NAVY BLUE BENT SPEAR 4-12
Section III OPREP-3 NAVY BLUE FADED GIANT 4-18
Section IV OPREP-3 NAVY BLUE DULL SWORD 4-24
Section V OPREP-3 NAVY BLUE SENTINEL 4-28

Chapter 5 OPREP-3 NAVY UNIT SITREP REPORTS


Section I OPREP-3 NAVY UNIT SITREP 5-1

LIST OF FIGURES

Figure 1-1 Special Incident Decision Tree 1-1


Figure 1-2 OPREP-3 PINNACLE Series Flowchart 1-4
Figure 1-3 OPREP-3 NAVY BLUE Series Flowchart 1-5

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

LIST OF TABLES

Table 2-1 Message Precedence and Defense Messaging System


(DMS) Grade of Delivery Cross-Walk 2-2
Table 2-2 Voice Message Reports Contact Information 2-5
Table B-1 OPREP-3 Personnel Incident Reporting Matrix B-18

APPENDICES

A REFERENCES A-1

B PERSONNEL INCIDENT REPORTS B-1

C ARMS, AMMUNITION AND EXPLOSIVES (AA&E) INCIDENT REPORTS C-1

D MARINE MAMMAL INCIDENT REPORTS D-1

E COMMAND AND CONTROL AND INFORMATION NETWORK OUTAGE


INCIDENT REPORTS E-1

F TERRORIST-RELATED INCIDENT REPORTS F-1

G ACRONYMS G-1

H GLOSSARY OF TERMS H-1

ii

CUI
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHAPTER 1 - SPECIAL INCIDENT REPORTING SYSTEM

Section I – DESCRIPTION

1. Purpose. Incidents of national-level interest are to be reported to the NMCC using the
OPREP-3 PINNACLE message system. If in doubt about whether a situation is of national
interest, the originator should send an OPREP-3 PINNACLE series report. Incidents of high-
level U.S. Navy interest are to be reported to the MOC and the NOC using the OPREP-3 NAVY
BLUE reporting system. The OPREP-3 NAVY UNIT SITREP reporting system is used to
report significant events or incidents that do not meet the OPREP-3 PINNACLE or OPREP-3
NAVY BLUE reporting criteria or to augment these reports. See figure 1-1.

Figure 1-1 Special Incident Decision Tree

2. Applicability. See paragraph 4 of the cover letter to this instruction. OPREP-3 reports must
be submitted by the lowest level command that has knowledge of the event, except for those
incidents where provision for rapid notification by a higher command has been established by
separate directive. For reports involving nuclear weapons or nuclear weapons systems, the
commander of the organization having physical possession of the weapon or delivery system has
the final responsibility for ensuring that the initial report is made.

3. System Description.
CUI
1-1
CUI
OPNAVINST 3100.6K
10 Aug 2021

a. An initial voice report is normally the first indication to senior authority that an incident
has occurred.
b. The basis for the OPREP-3 reporting system is a set of jointly formatted reports used to
transmit notification of special incidents to higher authority.

c. The Joint Reporting Structure is designed to allow for consistent transmission of reports
by voice, electronic or electrical record communications.

d. The USMTF PROFORMA message is designed to allow for the Joint, Coalition and
Allied standardization of message reporting as outlined:

(1) Reference (b) provides templates and samples for the OPREP-3 reporting system's
voice and record message reports.

(2) This instruction is based on reference (b). Use the most current USMTF user formats
release, per reference (b), when generating voice or record message reports.

CUI
1-2
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section II - POLICY

1. The OPREP-3 reporting system will be the first system used by the reporting command for
official reporting of an incident. It will also be the primary form of reporting from the initial
report until the final OPREP-3 report is filed for the incident. In addition, significant programs
and events may require reporting through other means to inform appropriate entities to a
situation and are governed by their own instructions and requirements. CRITIC reports per
reference (c) and MISHAP reports per reference (d), constitute exceptions to this policy and
require additional reports in addition to the OPREP-3 report. CRITIC and MISHAP reports are
further addressed in section III of this chapter.

2. The OPREP-3 PINNACLE report is used by any unit to provide the NMCC and, as
appropriate, combatant commands and Services, with immediate notification of any incident or
event where national-level interest is indicated. Specific incidents are identified by a secondary
flagword, such as NUCFLASH. Figure 1-2 provides general guidance. Incidents that require
national-level notification which are not identified by a secondary flagword must be reported
using the generic OPREP-3 PINNACLE report.

3. Where doubt exists as to whether an incident is of national or Navy interest, use the
appropriate OPREP-3 PINNACLE series report.

4. The OPREP-3 NAVY BLUE report is used by Navy units to provide CNO and other naval
commanders with immediate notification of incidents of military, political or media interest that
are high Navy, vice national-level interest. Specific incidents are identified by a secondary
flagword, such as OPREP-3 NAVY BLUE FADED GIANT. Figure 1-3 provides general
guidance. Incidents that require U.S. Navy notification and which are not identified by a
secondary flagword, must be reported using the generic OPREP-3 NAVY BLUE report.

CUI
1-3
CUI
OPNAVINST 3100.6K
10 Aug 2021

Figure 1-2 OPREP-3 PINNACLE Series Flowchart


CUI
1-4
CUI
OPNAVINST 3100.6K
10 Aug 2021

Figure 1-3 OPREP-3 NAVY BLUE Series Flowchart

CUI

1-5
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section III – RELATED REPORTS

1. CRITIC Reports. OPREP-3 reports do not replace the procedures for reporting CRITIC
reports as defined in references (c) and (e).

2. Other Joint Reports. Addressed in reference (a), typically used by unified or combatant
commanders and summarized in chapter 3, section IX, include OPREP-3 PINNACLE
COMMAND ASSESSMENT, OPREP-3 PINNACLE LERTCON STATUS OF ACTIONS,
NUDETSUM reporting and OPREP-3 CRESCENT EDGE.

3. Loss or Compromise of Classified Information, Material or Equipment.

a. These incidents, including incidents involving laptop computers, must be reported per
chapter 4, section I and reference (f).

b. If the loss or compromise of classified information results in the loss of or significant


degradation to, operational capability, then senior naval leadership needs to be informed via an
OPREP-3 NAVY BLUE in addition to reports required by reference (f). Chapter 4 provides
additional guidance.

4. Routine Computer Intrusion Incidents.

a. Report per chapter 4, section I and reference (g).

b. All computer intrusion incidents are required to be reported to the Navy Cyber Defense
Operation Command (NCDOC) per reference (g), SECNAVINST 5239.19 and NCDOC
reporting requirements. If the intrusion incident results in a loss or significant degradation to
operational capability, then senior naval leadership should be informed via an OPREP-3 NAVY
BLUE in addition to NCDOC notification requirements. Chapter 4 provides additional guidance.

5. Personnel Incident Reporting. These requirements have been closely coordinated with CNO
(N1) and references (h) through (p). Appendix B provides a generic reporting format for
OPREP-3 NAVY BLUE or OPREP-3 NAVY UNIT SITREP personnel incident reports. If a
personnel incident meets the reporting criteria of an OPREP-3 NAVY BLUE or OPREP-3
NAVY UNIT SITREP, then the appendix B format will be used and no other messages are
required.

6. MISHAP Reports. A MISHAP report is often required in addition to an OPREP-3 report.


Requirements for mishap investigation and reporting are contained in references (d) and (q).

CUI

1-6
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHAPTER 2 - GENERAL RULES FOR OPREP-3 REPORTING

Section I – GENERAL GUIDANCE

1. Timeliness. The reporting standard for OPREP-3 PINNACLE, OPREP-3 NAVY BLUE and
OPREP-3 NAVY UNIT SITREP messages is:

a. Voice Report: within 5 minutes for PINNACLE NUCFLASH and EMPTY QUIVER and
15 minutes of the event for all PINNACLE, NAVY BLUE and FP related NAVY UNIT SITREP
reports. (See subparagraph 3a, chapter 5, section I, for further guidance.)

b. Voice reports for Class A mishaps may require a phone call to the NAVSAFECEN
Mishap Line within 60 minutes. References (d) and (q) contain specific requirements.

c. Record Message Report: within 60 minutes.

d. Exercise WHITE PINNACLE: within 20 minutes. Requires a voice or record message


response as directed in the WHITE PINNACLE exercise.

2. Initial Reports.

a. Initial reports are not required to be complete reports; the emphasis of the report is on
immediacy rather than content.

b. These reports should address as many of the known line items as possible, but do not
delay the report for lack of information.

c. Where real-time secure chat capability exists between a unit and the MOC, a
simultaneous chat report should be made with the initial voice report.

d. Jointly approved formats and templates for voice and record message reports are
provided in reference (b). In general, reports should address:

(1) What happened?

(2) Who is or was involved?

(3) Where did it happen?

(4) When did it happen?

(5) Why did it happen?

CUI
2-1
CUI
OPNAVINST 3100.6K
10 Aug 2021

(6) What action is ongoing?

(7) What future action is contemplated?

(8) What is the impact on the command's mission capability?

(9) Is any assistance required?

(10) Is media attention anticipated?

(11) Have additional required reports made through appropriate systems been made?

3. Delayed Reports. Explain any delay in voice or record message reporting in the RMKS data
set of the record message.

4. Precedence. DMS has standardized message addresses and grade of delivery across the
Services. Table 2-1 provides a reference between the former message precedence and DMS’
grade of delivery.

Precedence DMS Grade of Delivery (X.400) Speed of Service


FLASH Urgent 10 minutes
IMMEDIATE Normal 30 minutes
PRIORITY Normal 3 hours
ROUTINE Non-urgent 6 hours
Table 2-1. Message Precedence and DMS Grade of Delivery Cross-Walk

a. Initial Reports

(1) FLASH (Urgent): All OPREP-3 PINNACLE series reports and OPREP-3 NAVY
BLUE FADED GIANT.

(2) IMMEDIATE (Normal): All OPREP-3 NAVY BLUEs and OPREP-3 NAVY UNIT
SITREPs.

b. FOLUP Reports

(1) FLASH (Urgent): OPREP-3 PINNACLE NUCFLASH, OPREP-3 PINNACLE


FRONT BURNER and OPREP-3 NAVY BLUE FADED GIANT.

(2) IMMEDIATE (Normal): All others

5. Minimize. All OPREP-3 reports are exempt from “minimize” conditions.

CUI
2-2
CUI
OPNAVINST 3100.6K
10 Aug 2021

6. Classification. All OPREP-3 reports will be classified as identified in subparagraphs 6a


through 6c:

a. Overall Classification Level. Messages must be marked in a manner similar to


documents as required by reference (f). Reporting commands are responsible for ensuring that
the overall classification marking on the message is the same as the highest classification level of
the message content. Use the DECL set to provide downgrading or any DECL instructions.

(1) The reporting command is responsible for assigning the proper security classification
to each report, including downgrading or DECL instructions, according to the guidance in
reference (f) and as reflected in the DECL set.

(2) When combat or combat-related operational requirements make speed of delivery


paramount, reporting commands may modify transmission of classified information as necessary
to meet local conditions. Even under those conditions, the provisions of reference (f) must be
followed as closely as possible. If modified, cite this subparagraph as the authority.

b. Portion Markings. Add portion markings as required by reference (f). There is an


exception to portion marking for pre-formatted messages that do not lend themselves to portion
markings. However, when messages are merely free text, this exception would not apply. For
example, GENTEXT, AMPN, NARR and RMKS sets contain free text that permits portion
marking.

c. RD or FRD. OPREP-3 reports containing RD or FRD, as defined in reference (f), must


be identified in the classification line
(e.g., “CONFIDENTIAL FORMERLY RESTRICTED DATA”).

CUI
2-3
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section II – VOICE MESSAGE REPORTS

1. Voice reports must be made to the appropriate MOC, the NOC or the NMCC to meet the
requirements for making a voice message report. Contact information is provided in table 2-2.
Ships at sea should report via the most rapid means available, including the appropriate
SATHICOM.

2. OPREP-3 PINNACLE series voice reports must be made directly to the NMCC, then to the
appropriate MOC who will notify the NOC accordingly. NMCC will then coordinate the
appropriate voice report to USSTRATCOM, as required.

3. OPREP-3 NAVY BLUE series voice reports must be made to the appropriate MOC who will
then notify the NOC. The NOC will notify NMCC who will then coordinate the appropriate
voice report to USSTRATCOM, as required.

4. Forces not assigned to a fleet commander should make OPREP-3 NAVY BLUE series
reports to the NOC, who will then forward to NMCC and other appropriate commands.

5. USSTRATCOM requires a voice report by the U.S. Navy for appropriate OPREP-3
PINNACLE series, OPREP-3 NAVY BLUE BENT SPEAR and OPREP-3 NAVY BLUE DULL
SWORD reports.

6. Forces unable to reach the designated MOC or the NOC should make reports directly to the
NMCC and request the NMCC relay to the NOC and the NOC will relay to the designated MOC.

7. The voice message report may be abbreviated if operational security considerations make this
absolutely necessary; however, the reporting command must carefully weigh the security
considerations against the senior commands' need for timely information for each incident.
Refer to paragraph 6 of chapter 2, section I, for additional information.

CUI
2-4
CUI
OPNAVINST 3100.6K
10 Aug 2021

MOCs
COMUSFLTFORCOM DSN: BWC 312-836-5397 or 5398
DSRN: BWC 80-521-6039
Commercial 757-836-5397 or 5398
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
COMPACFLT DSN: BWC 315-474-5452
Commercial 808-474-5452
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
COMUSNAVCENT DSN: BWC 318-439-3879
DSRN: BWC 80-539-2442
Commercial 973-1785-3879
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
COMFIFTHFLT DSN: FWO 318-439-4577
- Primary POC for DSRN: FWO 80-539-2442
COMFIFTHFLT assets Commercial 973-17-85-4577
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
(973 is country code)
COMUSNAVEUR DSN: BWC 314-626-4552 or 4551
COMUSNAVAF Commercial: BWC +039-081-568-4552 or 4551
DSRN: FWO 80-626-2342 or 2383
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
COMUSNAVSO DSN: BWC 312-960-7216 or 7355
DSRN: BWC 80-567-6279
Commercial 904-270-7216 or 7355
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
COMTENTHFLT NATIONAL SECURE 962-2314 or 2236
TELEPHONE SYSTEM
COMM 240-373-2391
DSN 312-685-2391
STE 240-737-2391
DSRN 80-228-7688
CISCO TELEPRESENCE 730-1846
SYSTEM EX90
Unclassified e-mail FCC_C10F_NSAH_FLTCMDCNTR_
[email protected]
SIPRNET e-mail [email protected]
Table 2-2 Voice Message Reports Contact Information (1 of 2)
CUI

2-5
CUI
OPNAVINST 3100.6K
10 Aug 2021

NOC
Forces not assigned to a fleet commander should make reports to the NOC, who will then
forward to NMCC and other appropriate commands.

BWC DSN 312-222-9284


Commercial 703-692-9284
DSRN 228-2767
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]

NOC ASSISTANT DSN 312-223-2006


Commercial 703-693-2006
DSRN 228-2525
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]

NMCC
Forces unable to reach the designated MOC or the NOC should make reports directly to the
NMCC and request the NMCC relay to NOC.
BATTLE CAPTAIN Primary DSN 302-221-1149
Commercial 703-692-4598
DSRN 228-7056
Unclassified e-mail js.pentagon.j3.mbx.njoic-battle-captain-
[email protected]
SIPRNET e-mail js.pentagon.j3.mbx.njoic-battle-captain-
[email protected]
NAVNETWARCOM
For loss of critical communications and command and control and information network outages
altering, hindering or impacting current operations.
BWC Commercial 757-417-6777
DSN 312-537-6777
Unclassified e-mail [email protected]
SIPR e-mail [email protected]
USSTRATCOM
MOCs or the NOC will forward required voice reports to USSTRATCOM's Watch Officer
Primary DSN 271-1800
Secondary DSN 271-1804
Commercial 402-294-1800 or 1804
Unclassified e-mail [email protected]
SIPRNET e-mail [email protected]
Table 2-2 Voice Message Reports Contact Information (2 of 2)

CUI

2-6
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section III – RECORD MESSAGE REPORTS

1. Initial Report. The initial record message report of the event must reference the initial voice
message report and must be marked “INIT.”

2. OPREP-3 NAVY BLUE and OPREP-3 NAVY UNIT SITREP Reports. Once a voice report
is made to the MOC, an INIT or FOLUP record message report is required. The only exception
is if and only if, within 30 minutes of the initial voice report of the incident, it is determined that
a reportable event did not occur and only when no NOC, NMCC or combatant commander
notifications were made by the MOC. The unit concerned must contact the MOC and provide
the appropriate information. If the MOC agrees that these parameters are met, the event may be
closed out without a hardcopy message report.

3. References on the Message Report. FOLUP record message reports must reference the DTG
of previously sent voice or record message reports.

4. Follow-up Reports. The follow-up report includes only the sections of the report that require
additional information. The code word FOLUP must be placed in the third field of the
TIMELOC set and the initial voice or record report DTG must be referenced. Precedence for
FOLUP reports is addressed in paragraph 4 of chapter 2, section I.

5. Data Sets. Initial and FOLUP record message reports should address as many of the required
data sets as possible, but reports should not be delayed to gather additional information.

6. Corrections to Reports. The originator must submit a new corrected message if an error is
noticed after submitting a report. Identify a corrected report by placing "CORR" in the third
field of the TIMELOC set.

7. Additional Information. Additional information to be considered for the GENTEXT or


RMKS set follows:

a. CO’s Assessment. Include in the RMKS data set, the CO's estimate of the situation, the
impact of the incident on the mission capability of the reporting unit, the ability of the unit to
operate safely and if any assistance is required.

b. Serious Injury or Death of U.S. Military Personnel. Care must be taken to avoid
reporting sensitive personal information that might cause unwarranted invasion of personal
privacy of individuals.

(1) Generic identification such as “Petty Officer 1st Class” or “20 YR OLD FEMALE E-
3” will suffice. Do not use Social Security Numbers.

CUI
2-7
CUI
OPNAVINST 3100.6K
10 Aug 2021

(2) If detailed personal identity information is required, it should be provided separately


in other than general messages, such as amplifying voice reports or limited distribution
messages, such as "Personal For" or secure e-mail.

(3) In the case of injury or death of a Service member, names must be withheld pending
notification of next of kin, unless positive identification is deemed absolutely necessary. In such
cases, the names can be listed provided this statement is included: "FOR OFFICIAL USE
ONLY. NEXT OF KIN HAVE NOT BEEN NOTIFIED."

c. NCIS involvement and case number.

(1) Notify the nearest supporting NCIS element of all major criminal incidents meeting
the criteria contained in reference (r). Incidents requiring NCIS investigations include, but are
not limited to:

(a) Sexual assault or allegation of wrongful sexual acts or contact.

(b) Homicide or unattended death.

(c) Home invasion or allegations of burglary.

(d) Theft of a government-owned vehicle, weapons, explosives or significant


amounts of ammunition.

(e) Narcotics-related incidents, including paraphernalia and positive urinalysis tests.

(f) Counter-intelligence matters including potential espionage or suspicious activities


indicating involvement of a foreign government or mishandling or compromise of classified
information.

(g) Counter-terrorism matters and activities as delineated in chapter 4.

(h) All nuclear weapons accidents or incidents (BROKEN ARROW, EMPTY


QUIVER and BENT SPEAR).

(2) Notification statements must identify the NCIS element notified, i.e., “NORFOLK
FIELD OFFICE DUTY AGENT,” or “COMMAND SPECIAL AGENT AFLOAT.”

(3) NCIS participation statements must articulate the general action the local NCIS
element will take, such as “[NCIS ELEMENT]” INVESTIGATING MATTER” or “[NCIS
ELEMENT] DEFERS TO COMMAND INVESTIGATION.”

CUI
2-8
CUI
OPNAVINST 3100.6K
10 Aug 2021

(4) Reporting delays in cooperation with NCIS investigations. NCIS may request a
command to delay a report to avoid alerting a potential crime suspect. The CO may consider
delaying the report under these circumstances but should explain the reason for the delay once
reported.

d. Media Interest. Provide an assessment of whether the incident will likely result in media
interest or coverage. Consult a PAO or collateral duty PAO, if available, prior to making the
assessment of whether any incident is likely to generate significant public interest and provide
information on any proposed news release. Do not delay reporting to consult with a PAO if one
is not readily available. For all message reports, include one of these statements:

(1) “(NATIONAL or LOCAL) MEDIA INTEREST OBSERVED.” Provide AMPN of


which news outlet has started reporting if readily available. Of note, observed media interest
elevates reporting to NAVY BLUE.

(2) “MEDIA INTEREST ANTICIPATED.”

(3) “MEDIA INTEREST NOT ANTICIPATED.”

e. FOLUP Message Report Statement. A statement indicating if a FOLUP message report


is expected.

(1) The initial message will sometimes be the final message. Additional messages may
be required for amplifying information of the same significance.

(2) Amplifying information of lesser significance may be reported in OPREP-3 NAVY


BLUEs, OPREP-3 NAVY UNIT SITREPs or other reports applicable to the incident.

8. Final Record Message Report. Prior to submitting the “last report this incident,” units should
check with their operational chain of command to ensure there are no other requests for
information by higher authority. Review the MISHAP reporting guidance per references (d) and
(q) to determine if the incident meets MISHAP reporting requirements. Only the final record
message report must include a mandatory RMKS set, which must include one of these
statements, as appropriate:

a. “MISHAP REPORT NOT REQUIRED,” or

b. “MISHAP REPORT TO FOLLOW,” or

c. “MISHAP REPORT SUBMITTED.”

9. Serialization.

CUI
2-9
CUI
OPNAVINST 3100.6K
10 Aug 2021

a. Serialize all OPREP-3 report record messages using the message serial number field
(field 3) of the MSGID set.

b. Voice reports of an incident are not serialized.

c. All OPREP-3 report record messages, regardless of flagword, must be serialized in


sequence by incident, beginning with 001, which is assigned to the first incident of each calendar
year. OPREP-3 reports use the same series of SEQ serial numbers vice using one set of serial
numbers for OPREP-3 PINNACLE reports and a separate set for OPREP-3 NAVY BLUE or
OPREP-3 NAVY UNIT SITREP reports.

d. Additional record message reports concerning the same incident must be assigned
sequential letter suffixes, i.e., 001A, 001B, 001C, etc. For example, the first record message
report of a new incident must be serialized 002, with subsequent record message reports
concerning this incident assigned successive suffixes, i.e., 002A, 002B, 002C.

e. At the end of the calendar year, if an incident requires amplifying reports, it must
continue with the serialization suffixes (010A, 010B, etc.) until the final report of the incident.

f. If an initial report is subsequently upgraded to an OPREP-3 PINNACLE or OPREP-3


NAVY BLUE or downgraded to an OPREP-3 NAVY BLUE or OPREP-3 NAVY UNIT
SITREP, the numbering sequence remains the same since the report number indicates a single
the particular incident.

10. Record Message Addresses.

a. Units reporting under this instruction must report using their administrative title, e.g.,
“USS SHIP” vice “CTE XX.X.X.X,” in the "FROM" line of the message.

b. Action and information addresses should utilize those listed in the Plain Language
Address Directory. DMS users should utilize appropriate distinguished name equivalents from
the DMS Directory.

c. All record message reports must be addressed per the guidance provided in chapters 3, 4
and 5. Fleet assets must include their respective fleet ISIC as an INFO addressee on reports,
even when chopped to another fleet’s operation control.

d. Responsibility for ensuring that all affected commands are informed of an incident rests
with both the report originator and recipients.

e. Recipients should review each report to determine whether additional addresses are
required.

CUI
2-10
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHAPTER 3 – OPREP-3 PINNACLE REPORTS

Section I – OPREP-3 PINNACLE

1. Specific Reporting Instructions. The OPREP-3 PINNACLE must be used by any unit to
provide the NMCC and, as appropriate, services and combatant commands with immediate
notification of any incident or event where national-level interest is indicated, but is not
specifically covered by other OPREP-3 reports. It is not restricted to reporting only operational
information. OPREP-3 PINNACLE and their associated FLAGWORD reports have specific
reporting requirements which are described in paragraph 2 of this section. The event or incident
reported will fall within one of these categories:

a. An instance of such impact that it requires the immediate attention of the SECDEF and
CJCS. Included are those instances that have actual or potential international repercussions, such
as creation of tension or undesirable relations between the United States and other countries.

b. An instance having national-level interest that has changed or may significantly change,
current operations, involves natural or human-made disasters or civil disorders.

c. When directed by current DoD and Joint Chiefs of Staff EXORD, with specific attention
to EXORDs directing worldwide operations against terrorists.

d. A hostile incident that could attract national-level interest should be reported as an


OPREP-3 PINNACLE FRONT BURNER.

e. Any other incident when it is conceivable that the highest level of government will
require timely notification. These are provided as guidance and are not exhaustive in nature:

(1) Major military, missile or ordnance incidents (when nuclear warheads are not
present).

(2) Incidents involving reconnaissance activities.

(3) Hijacking and related incidents.

(4) Asylum incidents.

(5) Receipt of critical intelligence.

(6) U.S. SAR operations in foreign countries or foreign territorial waters.

(7) Confirmed or suspected electronic attack, sabotage and electromagnetic pulse events
at tactical warning sensor sites, specified communication nodes and command center locations.

CUI
3-1
CUI
OPNAVINST 3100.6K
10 Aug 2021

(8) Law of war reportable incidents. All reportable incidents must be promptly reported
via the operational chain of command and via service channels to the CNO. Per references (s),
(t) and (u), a reportable incident is a possible, suspected or alleged violation of the Law of War
for which there is credible information or conduct during military operations other-than-war that
would constitute a violation of the law of war if it occurred during an armed conflict. Reportable
incidents that could constitute grave breaches of the Geneva Convention per enclosure (1) of
reference (s) must be reported via OPREP-3 PINNACLE. To report a reportable incident that
does not apparently constitute a grave breach, use an OPREP-3 NAVY BLUE.

(9) Any incident (except against forces previously declared hostile by higher authority) in
which live ordnance is fired with the intent to destroy or disable, in response to a violation or
suspected attempt to violate a U.S. Navy perimeter or maritime warning zone, including events
in foreign ports. Regardless of intent, if personnel are injured or killed in the engagement,
OPREP-3 PINNACLE notification is required.

(10) Use of force against suspected pirates at sea.

(11) Territorial violations by U.S. forces, actual or presumed, except in confined water
or air spaces, such as the Arabian Gulf, even if the violation was unintentional, of a short
duration and there was no reaction from the affected nation.

(12) Defection of U.S. or foreign personnel.

(13) Loss of or substantial damage to, civilian property caused by military equipment,
such as aircraft or ships, when national-level interest is indicated.

(14) Loss of or substantial damage to, major military equipment, such as aircraft or
ships, when national-level interest is indicated.

(15) Significant and unorthodox changes in the composition or structure of foreign


governments.

(16) Any incidents indicating the use of chemical or biological agents.

(17) Any incident requiring the actual execution of an organization’s COOP plan.
Voice and written report should indicate the incident causing plan execution. OPREP-3 NAVY
BLUE reporting requirements should be used for follow-on reporting.

(18) A systemic loss of NC3 outages in the form of FSBS strategic communications
lasting greater than 15 minutes. Specifically, an OPREP-3 PINNACLE is required for a
complete loss of the ability to deliver EAM via the FSBS transmitters supporting either LANT or
PAC AOR or both that has no identifiable resolution or has not been resolved in 15 minutes.
The intent of this reporting requirement is for land-based strategic communication nodes to

CUI
3-2
CUI
OPNAVINST 3100.6K
10 Aug 2021

report system outages; reports from individual units are not required. NAVY BLUE messages
are required for lesser outages.

(19) For National Strategic Sites – In the event, at a covered asset, an Unmanned
System demonstrates a hostile act or hostile intent during an incursion specifically over the
limited area, waterfront restricted area or convoy route at a covered site.

f. If doubt exists as to whether an event or incident is developing or could possibly develop,


into a matter of White House, DoD, Joint Service or national media interest, submit an OPREP-3
PINNACLE report. Any instance reported as an OPREP-3 should be considered for submission
as an OPREP-3 PINNACLE report unless a positive determination can be made to the contrary.

2. Report Content.

a. The OPREP-3 PINNACLE is a USMTF report. Instructions on USMTF voice and record
message format and additional examples are contained in reference (b).

b. For peacetime reconnaissance reports, provide the nickname, mission number and track
number of the peacetime reconnaissance assignment being reported.

4. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I
directly to the NMCC.

b. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

Line Number Line Name Line Description


Line One Incident Enter the incident identification, location and details.
Line Two Narrative Enter any additional information about the incident.

c. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED

CUI
3-3
CUI
OPNAVINST 3100.6K
10 Aug 2021

OPREP THREE PINNACLE


LINE ONE AIRSPACE VIOLATION, SEOUL
LINE TWO AIRCRAFT EXPERIENCED NAVAID TROUBLE BREAK VIOLATED NORTH
KOREAN AIRSPACE
OVER

5. Record Message Reports

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. The OCC of a data set can be C, O or M. Formats for all data sets are contained in
reference (b). MTF data sets used in the OPREP-3 PINNACLE message are:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3P)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE)
6 M TIMELOC Event Time and Position
7 M GENTEXT Incident Identification and Details
8 O DECL Message Downgrading or DECL Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC//


(DMS: "JOINT STAFF J3 NMCC OPS")
USSTRATCOM OFFUTT AFB NE//
CDR USNORTHCOM PETERSON AFB CO (required)
Combatant Commander (as appropriate):
CDR USCENTCOM MACDILL AFB FL
CDR USCENTCOM MACDILL AFB FL
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USSOUTHCOM MIAMI FL
CDR USSOCOM MACDILL AFB FL
CDR USTRANSCOM WASHINGTON DC
HQ USAFRICOM STUTTGART GE

CUI
3-4
CUI
OPNAVINST 3100.6K
10 Aug 2021

CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA//
Component Commander (as appropriate):
COMPACFLT PEARL HARBOR HI//
COMUSNAVEUR COMUSNAVAF NAPLES IT//
COMUSNAVCENT//
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
DIRNAVCRIMINVSERV QUANTICO VA
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

Chain of Command
ONI WASHINGTON DC
CHINFO WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
COMNAVSAFECEN NORFOLK VA
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC
(if incident is potentially reportable as a mishap or is an actual mishap)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (ordnance incidents)
NAVORDSAFSECACT INDIAN HEAD MD
BUMED FALLS CHURCH VA
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
SOPA
Regional Commander
Installation Commander
Appropriate U.S. Coast Guard District

CUI
3-5
CUI
OPNAVINST 3100.6K
10 Aug 2021

(4) Message body:

EXER/OLIVE DRAB 2009//


MSGID/OPREP-3P, USMTF, YYYY/ USS SHIP/00l//
REF/A/DESC: INITIAL VOICE REPORT/-/041722ZJAN2009//
FLAGWORD/PINNACLE/-//
TIMELOC/04l7l5ZJAN2009/SEOUL/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/AIRCRAFT
EXPERIENCED NAVIGATION AID TROUBLE AND APPEARS TO HAVE
UNINTENTIONALLY VIOLATED NORTH KOREAN AIR SPACE.
PILOT AND INCIDENT REPORT NOT YET AVAILABLE.//

CUI
3-6
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section II – OPREP-3 PINNACLE NUCFLASH (OPREP-3 PNF)

1. Specific Reporting Instructions. The OPREP-3 PINNACLE NUCFLASH is used to report


an event, accident or incident that could create the risk of a nuclear war. This message has the
highest precedence in the OPREP-3 reporting structure. Require reports include:

a. Ballistic missile launch or space launch.

b. Reentering space object.

c. Loss, potential loss or degradation of U.S. military space capability when the loss or
degradation is caused by the actions of a suspected or known hostile source.

d. Reports of cruise missiles or non-friendly, non-U.S. or non-allied aircraft not on an


approved flight plan that could pose a threat to U.S. forces, territory or interests.

e. Accidental, unauthorized or any other unexplained incident involving possible detonation


of a nuclear weapon.

f. Unauthorized flight or deviation from an approved flight plan by a nuclear-armed or


nuclear-capable aircraft with the capability to penetrate the airspace of another nuclear-capable
country.

2. Report Content.

a. This time-sensitive report must be made no later than 5 minutes after the incident and
sent at FLASH or URGENT in DMS precedence. The record communication FOLUP message
must be sent at FLASH or URGENT in DMS precedence within 60 minutes of the incident.

b. The OPREP-3 PINNACLE NUCFLASH is a USMTF report. Instructions on USMTF


voice and record message format and additional examples are contained in reference (b).

c. USMTF set identifiers for required information, are included in parentheses for
applicable information in the report:

(1) Date and TIMELOC of the instance and report type.

(2) NUCTM and unit involved. Used in initial reports.

(3) NUCLOC of the nuclear incident.

(4) NUCTYP, armament status and warhead type (Used in initial reports).

CUI
3-7
CUI
OPNAVINST 3100.6K
10 Aug 2021

(5) NUCCRS, detonation location, aim point, travel direction, air speed, flight duration
time and time on target. (Used in amplifying reports)

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
NUCFLASH reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

Line Number Line Name Line Description

Line One Time Enter the day-time Zulu when nuclear weapon
event occurred.
Line Two Location Enter the detonation impact location, in LAT and LONG
or UTM coordinates, bearing and range or place name.
Line Three Unit Enter the unit designator of the friendly military
unit involved.
Line Four Report Enter whether the report is INITIAL, FOLUP,
or FINAL.
Line Five Type Enter the surface-to-surface, air-to-air, air-to-surface,
surface-to-air or general weapon type being reported on
or aircraft type involved in the incident.* The weapon
identification and configuration is classified. If the
report is submitted over unclassified communications,
use a line number in special weapons ordnance
publication SWOP 20-11.
Line Six NUC Enter “yes” or "no” - indicating whether or not a
nuclear weapon is on board.
Line Seven Mark Enter the mark or model number designator for the
nuclear warhead involved.
Line Eight Point Enter the coordinates identifying the nuclear weapon
aim point in LAT and LONG, or UTM, bearing and range
or place name.
Line Nine Travel Enter the direction of travel of direction the nuclear
weapon. (NUC course and speed)

CUI
3-8
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Ten Speed Enter the nuclear weapon's estimated true air speed
in knots.
Line Eleven Duration Enter the estimated flight duration time of the nuclear
weapon in hours and minutes.
Line Twelve Time Enter the estimated day-time Zulu on target if vehicle
or weapon not located.
Line Thirteen Narrative Enter additional information needed to clarify or
amplify information above.
Line Fourteen Time zone Enter the DTG for the message time of origin.

d. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE NUCFLASH OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE NUCFLASH OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE NUCFLASH
LINE ONE ONE EIGHT ZERO FOUR TWO NINER ZULU DECEMBER
LINE TWO FOUR ZERO FIVE ZERO NORTH ONE SEVEN NINE THREE FIVE WEST
LINE THREE UNIFORM SIERRA SIERRA GEORGE WASHINGTON
LINE FOUR INITIAL
LINE FIVE UNIDENTIFIED LONG RANGE BOMBER LAUNCHED CRUISE MISSLE
LINE NINE ZERO NINE ZERO
LINE TEN THREE HUNDRED KNOTS
LINE ONE TWO ESTIMATE CRUISE MISSLE TO ENTER UNITED STATES AIRSPACE
ONE EIGHT ONE ZERO THREE THREE ZULU DECEMBER
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE NUCFLASH message:

SEQ OCC SETID Set Format Name


1 C EXER Exercise Identification
2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3-PNF)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE/NUCFLASH)

CUI
3-9
CUI
OPNAVINST 3100.6K
10 Aug 2021

6 M TIMELOC Event Time and Location


7 O NUCTM Time of Nuclear Incident
8 O NUCLOC Nuclear Location
9 O NUCTYP Nuclear Weapon Type
10 O NUCCRS Nuclear Weapon Detonation Location or
Course Information
11 O DECL Message Downgrading or DECL Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC


USSTRATCOM OFFUTT AFB NE CDR USNORTHCOM PETERSON AFB CO
(required)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
CDR USSOCOM MACDILL AFB FL
CDR TRANSCOM WASHINGTON DC
HQUSAFRICOM STUTTGART GE
CNO WASHINGTON DC //
COMUSFLTFORCOM NORFOLK VA//
Component Commander (as appropriate):
COMPACFLT PEARL HARBOR HI//
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

Chain of Command
ONI WASHINGTON DC
CHINFO WASHINGTON DC

CUI
3-10
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMNAVSAFECEN NORFOLK VA
(if incident is potentially reportable as a MISHAP or an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine configured
TOMAHAWK missiles)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
DIRNAVCRIMINVSERV QUANTICO VA
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (ordnance incidents)
NAVORDSAFSECACT INDIAN HEAD MD (ordnance incidents)
BUMED FALLS CHURCH VA
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
CDR USSOCM MACDILL AFB FL
CDR USTRANSCOM SCOTT AFB IL
SOPA
Regional Commander
Installation Commander
Appropriate U.S. Coast Guard District

(4) Message body:

MSGID/OPREP-3PNF, USMTF, YYYY/USS SHIP/001//


REF/A/DESC: INITIAL VOICE REPORT TO NMCC/JTF SWA/180429DEC2005//
FLAGWORD/PINNACLE/NUCFLASH//
TIMELOC/180429ZDEC2005/4050N13235E/INIT//
NUCTM/ETOT: 180830Z/VAQ-130//
NUCLOC/4000Nl3400E//
NUCTYP/ACTYP: A6/NUCSTAT:Y/MARK:W632//
RMKS/AIRCRAFT LAST OBSERVED FLYING A COURSE TOWARD COUNTRY
ORANGE, A NUCLEAR CAPABLE COUNTRY. AIRCRAFT IS UNARMED. ON
PRESENT COURSE AND SPEED, AIRCRAFT WILL ENTER COUNTRY ORANGE
AIRSPACE AT 180830ZDEC2005. ADDITIONAL REPORTS TO FOLLOW.//

CUI
3-11
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section III – OPREP-3 PINNACLE FRONT BURNER

1. Specific Reporting Instructions. The OPREP-3 PINNACLE FRONT BURNER report must
be used to report:

a. Any pre-conflict occurrence of armed attack, harassment or hostile action against U.S.
forces, territory or interests.

b. Armed attack includes terrorist attacks, suspected terrorist attacks or hostile acts against
U.S. shipping, interests or U.S. forces.

c. Expenditure of ordnance, after warning protocols have been exhausted, directed at an


approaching vessel or aircraft with the intent to destroy or disable that vessel or aircraft (except
those previously declared hostile by higher authority).

d. An act, or attempted act, of sabotage by foreign nationals against U.S. forces or


installations.

e. Significant hostile action between two or more foreign forces regardless of the
nationalities involved.

f. Unmanned Systems incursions of assets covered under Title 10 U.S.C. section 130i when
based on the totality of circumstances indicate hostile intent.

2. Report Content.

a. The OPREP-3 PINNACLE FRONT BURNER is a USMTF report. Instructions on


USMTF voice and record message format and additional examples are contained in reference
(b).

b. The reporting activity must be sure to identify the type of event being reported (e.g., ship
harassment, aircraft accident, border violation, possible terrorist incident).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
FRONT BURNER reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line

CUI
3-12
CUI
OPNAVINST 3100.6K
10 Aug 2021

number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

Line Number Line Name Line Description

Line One Incident Enter information to identify incident and provide


details.
Line Two Narrative Enter additional information needed to clarify or
amplify information above. When reporting terrorist
incidents, include:

Date: Date the incident occurred.


Location: Where the incident occurred.
Short identifying title: What the report is about.
Details: Describe who, what, when, where, why and
how. Obtain all possible details for initial and
FOLUP reports.
Countries: What countries do the information in the
report relate to.
Actions taken.

Line Three Time Enter the day, hour, minute, time zone, month and year
(DTG) for the message time of origin.

d. Voice Message Report Example.

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE FRONT BURNER OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE FRONT BURNER OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE FRONT BURNER
LINE ONE YANKEE REPORTS MAIL HELO DITCHED
LINE TWO ORANGE FORCES TRAWLER NEARBY
OPERATION IMPEDED
LINE THREE ONE SEVEN ONE FIVE TWO FIVE ZULU MARCH
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

CUI
3-13
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE FRONT BURNER message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3 PFB)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE-FRONT BURNER)
6 M TIMELOC Event Time and Position
7 M GENTEXT INCIDENT IDENTIFICATION AND DETAILS

When reporting hostile incidents, use this format:

Date: Date the incident occurred.


Location: Where the incident occurred.
Short identifying title: What the report is about.
Details: Describe who, what, when, where, why and how.
Obtain all possible details for initial and FOLUP reports.
Countries: What countries does the information in the report relate to?
Actions taken.

8 O DECL Message Downgrading or DECL Data


* Repeatable set

c. Action and information plain language addresses will differ for terrorist incident
reporting. See subparagraphs 4d and 4e.

d. Record Message Example (not a terrorist incident).

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC//J3 NMCC// (DMS: "JOINT STAFF J3 NMCC


OPS")
USSTRATCOM OFFUTT AFB NE//J3/J31/J38//
CDR USNORTHCOM PETERSON AFB CO (required)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
HQUSAFRICOM STUTTGART GE

CUI
3-14
CUI
OPNAVINST 3100.6K
10 Aug 2021

CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
Component Commander (as appropriate)
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders (see appendix F – SSBN/UAS)
DIRNAVCRIMINVSERV QUANTICO VA
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) NFO addresses:

Chain of Command
ONI WASHINGTON DC
CHINFO WASHINGTON DC
COMNAVSAFECEN NORFOLK VA
(if incident is potentially reportable as a MISHAP or an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine configured
TOMAHAWK missiles)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (major fraud, waste or abuse)
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (ordnance incidents)
NAVORDSAFSECACT INDIAN HEAD MD (ordnance incidents)
BUMED FALLS CHURCH VA
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
SOPA
Regional Commander

CUI
3-15
CUI
OPNAVINST 3100.6K
10 Aug 2021

Installation Commander
Appropriate U.S. Coast Guard District

e. Record message plain language addresses for a terrorist incident.

(1) ACTION addresses:

CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
COMDT COGARD WASHINGTON DC
Combatant Commander
Component Commander
Fleet Commander
DIRNAVCRIMINVSERV QUANTICO VA//NCISMTAC//

(2) INFO addresses:

SECDEF WASHINGTON DC
CJCS WASHINGTON DC
JOINT STAFF WASHINGTON DC
WHITE HOUSE SITUATION ROOM WASHINGTON DC
HQ NORAD PETERSON AFB CO
HQ NORAD USNORTHCOM INTEL
PETERSON AFB CO
CDR USSTRATCOM OFFUTT AFB NE
CDR USPACOM HONOLULU HI
CDR USTRANSCOM SCOTT AFB IL
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
CDR USSOCOM MACDILL AFB FL
HQUSAFRICOM STUTTGART GE
CDRFORSCOM FT MCPHERSON GA
HQ FORSCOM-G3 FT MCPHERSON GA
CMC WASHINGTON DC
CG TECOM (USMC training unit incidents involving personnel or missions)
COMMARFORCOM
COMMARFORNORTH
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA
CDR ARNORTH FT MCPERSON GA
CJTFCS FT MONROE VA
CJTF 6 FT BLISS TX

CUI
3-16
CUI
OPNAVINST 3100.6K
10 Aug 2021

JTF ALASKA ELMENDORF AFB AK


JFHQ-NCR J3 FT MCNAIR DC
HQ ACC LANGLEY AFB VA
HQ NORAD COMMAND CTR CHEYENNE MOUNTAIN AFS CO
COMBINED INTEL AND FUSION CTR PETERSON AFB CO
DEPT OF HOMELAND SECURITY WASHINGTON DC
DEPT OF JUSTICE COMMAND CENTER WASHINGTON DC
CIA WASHINGTON DC
DIA WASHINGTON DC
FBI WASHINGTON DC
DIRNSA FT GEORGE G MEADE MD
ONI WASHINGTON DC
CHINFO WASHINGTON DC
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
Applicable Numbered Fleet Commander
Applicable Type Commander
Applicable Naval Regional Commander
Applicable Installation Commander
COMARFPCOM NORFOLK VA
COMNAVSEASYSCOM WASHINGTON DC
Local NAVCRIMINVSERV (NCIS) office
Appropriate U.S. Coast Guard District

(3) Message body:

EXER/OLIVE DRAB 2009//


MSGID/OPREP-3PFB, USMTF, YYYY/CTU22.02.01/001B//
REF/A/DESC: INITIAL VOICE REPORT/USS SHIP/171525ZMAR2009//
FLAGWORD/PINNACLE/FRONT BURNER//
TIMELOC/171525Z/773105N1602315W/FINAL//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/COD OPERATION
(MAIL HELO) DITCHED WITH FLOATATION GEAR ATTACHED. ORANGE FORCES
TRAWLER SERIOUSLY IMPEDED RECOVERY OPERATIONS BY TASK FORCE UNITS.
CREW RECOVERED SAFELY BY JRCC UNIT AT 171533Z.
HELO RECOVERED INTACT WITH ALL CARGO AT 171830Z
BY RECOVERER//
RMKS/INITIAL VOICE REPORT INITIATED 171528Z. THIS IS A FINAL REPORT.//

CUI
3-17
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section IV – OPREP-3 PINNACLE BROKEN ARROW

1. Specific Reporting Instructions. The OPREP-3 PINNACLE BROKEN ARROW report must
be used to report a U.S. nuclear weapon incident that does not create risk of nuclear war.
Included are:

a. Nuclear detonation of a U.S. nuclear weapon.

b. Nonnuclear detonation or burning of a nuclear weapon.

c. Radioactive contamination from a U.S. nuclear weapon or component.

d. The jettisoning of a U.S. nuclear weapon or component.

e. Public hazard, actual or implied, from a U.S. nuclear weapon or component.

2. Report Content. The OPREP-3 PINNACLE BROKEN ARROW is a USMTF report.


Instructions on USMTF voice and record message format and additional examples are contained
in reference (b).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
BROKEN ARROW reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

CUI
3-18
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Number Line Name Line Description

Line One Date and Time Enter the date-time Zulu that the
event took place.
Line Two Location Enter the location, in LAT and LONG
or UTM coordinates, or place name.
Line Three Quantity and Type Enter the quantity and type of weapons
and components.*
Line Four Casualties and Damage Enter the casualties and property damage.
Line Five Type Operation Enter the type of operation.
Line Six Cause Enter the cause of the accident or incident.
Line Seven Event Description Enter the full description of the event.
Line Eight Hazard and Radiation Enter an assessment of nuclear hazard and
radiation levels.
Line Nine Weapons Condition Enter the condition of the weapon(s).
Line Ten Safety and Security Enter the measures taken to ensure safety
and security.
Line Eleven News Releases Enter the text of the news releases and
responses to media requests.
Line Twelve Other Information Enter other pertinent information to amplify,
including known public reaction or political
implications. If applicable, address status of
reactor onboard.
Line Thirteen Corrective Action Enter corrective action taken or
recommended.

* The weapon identification and configuration are classified. If the report is submitted over
unclassified communications, a line number in reference (v) will be used.

d. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE BROKEN ARROW OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE BROKEN ARROW OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE BROKEN ARROW
LINE ONE ONE SEVEN ZERO SEVEN FOUR TWO ZULU DECEMBER
LINE TWO PEARL HARBOR COMMA HAWAII
LINE THREE ONE WHISKEY ZERO ZERO WARHEAD
LINE FOUR TWO KILLED COMMA THREE WOUNDED COMMA ONE TRUCK
DESTROYED BY FIRE COMMA ONE MISSILE EXPOSED TO GAS FIRE COMMA DID
NOT EXPLODE OR BURN

CUI
3-19
CUI
OPNAVINST 3100.6K
10 Aug 2021

LINE FIVE MISSILE TRANSPORT


LINE SIX TRUCK HAULING MISSILE EXPERIENCED ENGINE FLASH FIRE
LINE SEVEN ENGINE FIRE SPREAD TO MISSILE MOTOR AND ONE WHISKEY ZERO
ZERO WARHEAD
LINE EIGHT NO NUCLEAR OR RADIATION HAZARD
LINE NINER WHISKEY ZERO ZERO WITH EXTERNAL BURN DAMAGE CONDITION
UNKNOWN
LINE ONE ZERO FIRE IS OUT COMMA WEAPON IS BEING COOLED BY FIRE HOSES
LINE ONE ONE MEDIA IS EN ROUTE TO SCENE COMMA NO INFORMATION HAS
BEEN RELEASED
LINE ONE TWO NO PUBLIC REACTION HAS BEEN RECEIVED BREAK ADVERSE
PUBLICITY IS ANTICIPATED
LINE ONE THREE NOT YET AVAILABLE
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE BROKEN ARROW message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3PBA)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE-BROKEN
ARROW)
6 M TIMELOC Event Time and Position
7 M EVTYP * Nuclear Weapon Event Type
8 C HEADING Casualties and Damages
9 O CASUALTY Friendly Personnel Casualty Count
10 O GENTEXT DAMAGES
11 O GENTEXT Incident Cause and Details
12 C HEADING Radiation Information
13 O 5RAD Radioactivity Dose Rate Information
14 C 5STRKWRN Radiation Information
15 O GENTEXT Weapon Condition and Safety Measures
16 O GENTEXT News Releases
17 O GENTEXT Public and Political Implications

CUI
3-20
CUI
OPNAVINST 3100.6K
10 Aug 2021

18 O GENTEXT Corrective Action Recommended


19 O DECL Message Derivative or Original Source for
Classification, Reason for Classification and DECL and
Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC


USSTRATCOM OFFUTT AFB NE
CDR USNORTHCOM PETERSON AFB CO (required)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
HQUSAFRICOM STUTTGART GE
CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
Component Commander (as appropriate):
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

COMMARFORCOM (for USMC controlled items)


CMC PPO WASHINGTON DC (USMC personnel or mission incidents)
COMNAVSEASYSCOM WASHINGTON DC
COMNAVFACENGCOM WASHINGTON DC
NAVSURFWARCENDIV DAHLGREN VA
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC

CUI
3-21
CUI
OPNAVINST 3100.6K
10 Aug 2021

NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK


NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD
COMNAVAIRSYSCOM PATUXENT RIVER MD
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)
BUMED FALLS CHURCH VA (personnel injury or contamination)

(3) Message body:

MSGID/OPREP-3PBA, USMTF, YYYY/CTU122.3.1/001//


REF/A/DESC: INITIAL VOICE REPORT FROM USS NIMITZ/USS NIMITZ
/170755ZDEC2005//
FLAGWORD/PINNACLE/BROKEN ARROW//
TIMELOC/170742ZDEC2005/SHELBY NAVAL BASE/INIT//
EVTYP/QTY: l/WPNGEN: TRIDENT 1//
HEADING/CASUALTIES AND DAMAGES//
CASUALTY/KILLED: 2/WOUNDED:3/MISSING:0//
GENTEXT/DAMAGES/ONE TRUCK DESTROYED BY FIRE. WEAPONS EXPOSED TO
GAS FIRE BUT DID NOT DETONATE OR BURN.//
GENTEXT/INCIDENT CAUSE AND DETAILS/TRUCK EXPERIENCED ENGINE FLASH
FIRE. DRIVER AND ASST WERE KILLED AND THREE NAVPERS INJURED WHILE
ATTEMPTING TO SAVE TRUCK CREW AND RECOVER WPN. INJURED PERSONNEL
HAVE BEEN TRANSPORTED TO LOCAL HOSPITAL.//
HEADING/RADIATION INFORMATION//
5RAD
/DE/READ-LOC /READ-TIM /DOSE /DQFR /DCAY
/01/CORNER MCNAIRTYMES /171245Z /4500CPM /INIT / 0.0
/02/APPROACH RW23 /171315Z /1250CPM /DECR / 0.8
/03/HOUSING AREA /171330Z /5800CPM /DECR / 0.9//
GENTEXT/WEAPON CONDITION AND SAFETY MEASURES/SEVERE DAMAGE ON
W00 WARHEAD; RADIOACTIVE CONTAMINATION IS PRESENT. FIRE HAS BEEN
EXTINGUISHED. AREA HAS BEEN SECURED. ATTEMPTING TO DETERMINE
EXTENT OF CONTAMINATION. PREPARING FOR ARRIVAL OF RESPONSE TASK
FORCE. EVACUATED DOWNWIND AREA ON BASE AND HAVE NOTIFIED LOCAL
AUTHORITIES OF POSSIBLE DANGER. INVESTIGATION CURRENTLY UNDERWAY
TO DETERMINE THE CAUSE OF INCIDENT AND SAFETY MEASURES FOR FUTURE
OPNS.//
GENTEXT/NEWS RELEASES/INITIAL REPORT MADE TO LOCAL TELEVISION AND
RADIO//
GENTEXT/PUBLIC AND POLITICAL IMPLICATIONS/LOCAL MEDIA AT SCENE,
SPECIAL REPORT AIRING ON LOCAL TELEVISION STATION.//

CUI
3-22
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section V – OPREP-3 PINNACLE EMPTY QUIVER (OPREP-3 PEQ)

1. Specific Reporting Instructions. The OPREP-3 PINNACLE EMPTY QUIVER report must
be used to report the seizure, theft or loss of a nuclear weapon per reference (w). Prompt
reporting directly to NMCC is imperative to enable timely directed action from NMCC, followed
by reporting up the chain of command.

2. Report Content.

a. The OPREP-3 PINNACLE EMPTY QUIVER is a USMTF report. Instructions on


USMTF voice and record message format and additional examples are contained in reference
(b).

b. USMTF set identifiers for required information are included in parentheses, when
applicable, include:

(1) Date, TIMELOC and report status.

(2) EVTYP: quantity and type of weapons and ship or aircraft identification.

(3) Casualties and property damage (HEADING-CASUALTIES AND DAMAGES).

(4) Incident cause and details (GENTEXT-INCIDENT CAUSE AND DETAILS).

(5) Weapon condition and safety measures (GENTEXT-WEAPON CONDITION AND


SAFETY MEASURES).

(6) Amplifying information, including known or suspected route of diversion or escape,


composition of recovery force, controlling authority and communication links established with
hot pursuit (recovery) team (GENTEXT-SEIZURE, THEFT OR LOSS).

(7) News releases (GENTEXT-NEWS RELEASES).

(8) Public and political implications (GENTEXT-PUBLIC AND POLITICAL


IMPLICATIONS).

(9) Assistance required (GENTEXT-ASSISTANCE REQUIRED).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

CUI
3-23
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
EMPTY QUIVER reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

Line Number Line Name Line Description

Line One Date and Time Enter the date-time Zulu that the event took
place.
Line Two Location Location of the event, in LAT and LONG or
UTM coordinates, or the place name.
Line Three Quantity and Type Enter the quantity and type of weapons and
components.*
Line Four Casualties and Damage Enter the casualties and property damage.
Line Five Type Operation Enter the type of operation.
Line Six Cause Enter the cause of the accident or incident.
Line Seven Event Description Enter the full description of the event.
Line Eight Hazard and Radiation Enter an assessment of nuclear hazard and
radiation levels.
Line Nine Weapon Condition Enter the condition of the weapon(s).
Line Ten Safety and Security Enter the measures taken to ensure safety and
security.
Line Eleven News Releases Enter the text of the news releases and responses
to media requests.
Line Twelve Other Information Enter other pertinent information to amplify,
including known public reaction or political
implications.
Line Thirteen Corrective Action Enter corrective action taken or recommended.
Line Fourteen Known or Suspect Route Enter the known or suspected route of diversion
or escape.
Line Fifteen Recovery Measures Enter the recovery measures in progress.
Line Sixteen Recovery Forces Enter the composition of recovery forces and
augmentation or reinforcement plans.
Line Seventeen Controlling Authority Enter immediate controlling authority for
recapture or recovery actions (recapture is on a
U.S. facility and recovery is off a U.S. facility).

CUI
3-24
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Eighteen Communications Enter the communications established or


being established.
Line Nineteen Assistance Enter any assistance required.

* The weapon identification and configuration are classified. If the report is submitted over
unclassified communications, a line number in reference (v) must be used.

d. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE EMPTY QUIVER OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE EMPTY QUIVER OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE EMPTY QUIVER
LINE ONE ONE FIVE ZERO NINER FOUR FIVE ZULU DECEMBER
LINE TWO LOS CURSIS TEXAS
LINE THREE TWO WHISKEY ZERO ZERO WARHEADS
LINE FOUR NEGATIVE CASUALTIES AT THIS TIME BREAK NEGATIVE DAMAGES
AT THIS TIME
LINE FIVE WEAPON TRANSFER
LINE SIX POSSIBLE TERRORIST INFILTRATION
LINE SEVEN FIVE ARMED INDIVIDUALS PENETRATED WEAPONS STORAGE
EXCLUSION AREA COMMA INDIVIDUALS HAVE ACCESS TO WEAPONS AND
COMPONENT IN OPEN TRANSIT
LINE NINER NOT KNOWN
LINE ONE ZERO INCREASED SECURITY ALERT STATUS ACTIVATED
LINE ONE THREE SEARCH IN PROGRESS COMMA FBI NOTIFIED
LINE ONE FOUR SUSPECT ROUTE MEXICO OR SOUTH AMERICA
LINE ONE FIVE BACKUP FORCE ON STATION
LINE ONE SIX WEAPON TRANSFER TEAM AND DIVERS
LINE ONE SEVEN LOCAL AUTHORITY ADMIRAL SWARTZENGRUBER COMMA
CIVIL AUTHORITY MISTER DOLLIE
LINE ONE EIGHT COMMUNICATIONS ARE BEING ESTABLISHED
LINE ONE NINER REQUEST RESPONSE TASK FORCE
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

CUI
3-25
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE EMPTY QUIVER message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3PEQ)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE/EMPTY QUIVER)
6 M TIMELOC Event Time and Position
7 M EVTYP * Nuclear Weapon Event Type
8 C HEADING CASUALTIES AND DAMAGES
9 O CASUALTY Friendly Personnel Casualty Count
10 O GENTEXT DAMAGES
11 O GENTEXT INCIDENT CAUSE AND DETAILS
12 O GENTEXT WEAPON CONDITION AND SAFETY MEASURES
13 O GENTEXT SEIZURE, THEFT OR LOSS
14 O GENTEXT NEWS RELEASES
15 O GENTEXT PUBLIC AND POLITICAL IMPLICATIONS
16 O GENTEXT ASSISTANCE REQUIRED
17 O DECL Message Derivative or Original Source for Classification,
Reason for Classification and DECL and Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC


USSTRATCOM OFFUTT AFB NE CDR USNORTHCOM PETERSON AFB CO
(required for OPREP-3Ps)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
CDR USTRANSCOM WASHINGTON DC
HQUSAFRICOM STUTTGART GE
CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
Component Commander (as appropriate):

CUI
3-26
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMPACFLT PEARL HARBOR HI//MOC//


COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
DIRNAVCRIMINVSERV QUANTICO VA
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

COMMARFORCOM (for USMC controlled items)


CMC PPO WASHINGTON DC (USMC personnel or mission incidents)
COMNAVSEASYSCOM WASHINGTON DC
COMNAVFACENGCOM WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
NAVSURFWARCENDIV DAHLGREN VA
CDR USSOCOM MACDILL AFB FL
CDR USTRANSCOM SCOTT AFB IL
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD
COMNAVAIRSYSCOM PATUXENT RIVER MD
BUMED FALLS CHURCH VA (in case of personnel injury and contamination)

(3) Message body:

MSGID/OPREP-3PEQ, USMTF, YYYY/NWF LAS CURSIS, TX/001B//


REF/A/DESC: INITIAL VOICE REPORT TO NMCC/NWF LAS CURSIS/
151000ZDEC2005//
FLAGWORD/PINNACLE/EMPTY QUIVER//
TIMELOC/l50945ZDEC2005/ROBERTS AFB/FOLUP//
EVTYP/QTY: 2/WPNGEN: W80//
HEADING/CASUALTIES AND DAMAGES//
CASUALTY/KILLED: 0/WOUNDED: 3/MISSING: 0//
GENTEXT/DAMAGES/TWO W00 WARHEADS REMOVED BY TERRORISTS.//
GENTEXT/INCIDENT CAUSE AND DETAILS/STORAGE AREA PENETRATED BY 5-
ARMED TERRORISTS, WHO REMOVED TWO W00 WARHEADS. THREE SECURITY

CUI
3-27
CUI
OPNAVINST 3100.6K
10 Aug 2021

POLICE WERE WOUNDED IN THE ATTACK. TERRORISTS DEPARTED BY


HELICOPTER.//
GENTEXT/WEAPON CONDITION AND SAFETY MEASURES/UNKNOWN//
GENTEXT/SEIZURE, THEFT OR LOSS/HELICOPTER HEADED FOR MEXICAN COAST.
MEXICAN AUTHORITIES NOTIFIED. LOCAL FBI FIELD OFFICE IN AUSTIN, TEXAS
AND CIVILIAN AUTHORITIES NOTIFIED. AIR SEARCH PROCEDURES IN
PROGRESS.//
GENTEXT/NEWS RELEASES/NO PUBLIC NEWS RELEASES AT THIS TIME.//
GENTEXT/PUBLIC AND POLITICAL IMPLICATIONS/MEXICAN GOVERNMENT
NOTIFIED AND PROMISE FULL COOPERATION.//
GENTEXT/ASSISTANCE REQUIRED/REQUEST RESPONSE TASK FORCE AND
SEARCH TEAMS.//

CUI
3-28
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section VI – OPREP-3 PINNACLE EMERGENCY DISABLEMENT

1. Specific Reporting Instructions. The OPREP-3 PINNACLE EMERGENCY


DISABLEMENT report is used for reporting operations involving the command disablement or
nonviolent disablement of nuclear weapons.

2. Report Content. The OPREP-3 PINNACLE EMERGENCY DISABLEMENT is a USMTF


report. Instructions on USMTF voice and record message format and additional examples are
contained in reference (b).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
EMERGENCY DISABLEMENT reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

CUI
3-29
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Number Line Name Line Description

Line One Time Enter the date-time Zulu that the event took place.
Line Two Location Enter the location of the event, in LAT and LONG or
UTM coordinates, bearing and range or place
name. Place (installation) name is preferred entry.
Line Three Disabled Enter the quantity of weapons disabled.
Line Four Type Enter the surface-to-surface, air-to-air,
air-to-surface, surface-to-air or general weapon
type disabled.*
Line Five By Enter the unit designator of the unit that completed
the action.
Line Six Command Enter the identification of the commander
authorizing or conducting disablement of the
weapons.
Line Seven Reason Enter the reason for conducting disablement of the
weapons.
Line Eight Narrative Enter additional information needed to clarify or
amplify information above.
Line Nine Time Enter the DTG for the message time of origin.

* The weapon identification and configuration are classified. If the report is submitted over
unclassified communications, a line number in reference (v) must be used.

d. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE EMERGENCY DISABLEMENT


OVER
SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE EMERGENCY
DISABLEMENT OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE EMERGENCY DISABLEMENT
LINE ONE ONE SEVEN ONE FOUR THREE ZERO ZULU JANUARY
LINE TWO TWO SEVEN THREE ONE TWO ZERO NORTH ONE SIX ZERO TWO THREE
ONE FIVE WEST
LINE THREE THREE
LINE FOUR BRAVO SIX ONE
LINE FIVE CHARLIE TANGO FOXTROT TWO
LINE SIX CODENAME TANGO WHISKEY ALFA ONE
LINE SEVEN WEAPONS STORAGE FACILITY IN DANGER OF BEING OVERRUN BY
SUPERIOR FORCE

CUI
3-30
CUI
OPNAVINST 3100.6K
10 Aug 2021

LINE EIGHT NONE


OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE EMERGENCY DISABLEMENT message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3PED)
4 O REF * Reference
5 M FLAGWORD Flagword Information
(PINNACLE-EMERGENCY DISABLEMENT)
6 M TIMELOC Event Time and Position
7 M 5NWPN Information Respecting Quantity and Type
8 M CMDAUTH Authority Directing or Carrying Out EA
9 M GENTEXT REASON FOR DISABLEMENT
10 O DECL Message Derivative or Original Source for
Classification, Reason for Classification and
DECL and Downgrading Data

* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC


USSTRATCOM OFFUTT AFB NE CDR USNORTHCOM PETERSON AFB CO
(required for OPREP-3Ps)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
HQUSAFRICOM STUTTGART GE
CNO WASHINGTON DC

CUI
3-31
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMUSFLTFORCOM NORFOLK VA
Component Commander (as appropriate):
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

CMC PPO WASHINGTON DC (USMC personnel or mission incidents)


Chain of Command
ONI WASHINGTON DC
CHINFO WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (if incident is potentially reportable as a
MISHAP or is an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)

COMMARFORCOM (for USMC controlled items)

(3) Additional addresses:

(a) For LANTFLT, COMUSNAVEUR, COMUSNAVAF units:

ACTION addresses:

DTRA ABQ KIRTLAND AFB NM


COMUSFLTFORCOM NORFOLK VA (LANTFLT only)

INFO addresses:

COMSUBLANT NORFOLK VA//N3/N3IPS/N71// (TRIDENT incidents)


DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
SWFPAC BANGOR WA//00/01/050/30//

CUI
3-32
CUI
OPNAVINST 3100.6K
10 Aug 2021

FISC NORFOLK VA
DTRA ALEX WASHINGTON DC
SWFLANT KINGS BAY GA

(b) Message addresses for COMPACFLT units:

ACTION addresses:

DTRA ABQ KIRTLAND AFB NM


COMNAVSURFPAC SAN DIEGO CA

INFO addresses:

COMPACFLT PEARL HARBOR HI


COMNAVSURFPAC SAN DIEGO CA (surface ships only)
COMSUBPAC PEARL HARBOR HI (submarines only)
DIRSSP WASHINGTON DC
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
SWFPAC BANGOR WA//00/01/050/30//
DTRA ALEX WASHINGTON DC
BUMED FALLS CHURCH VA (in case of personnel injury and contamination)

(c) Message body:

EXER/OLIVE DRAB 2007//


MSGID/OPREP-3PED, USMTF, YYYY/CTF-2/00l//
REF/A/DESC: INITIAL VOICE REPORT TO NMCC/CTF-2/171430ZJAN2005//
REF/B/DESC: EXOPORD FOR EXERCISE OLIVE DRAB
200/USSOUTHCOM/171435ZJAN2005/-/-/0117001//
FLAGWORD/PINNACLE/EMERGENCY DISABLEMENT//
TIMELOC/l71435ZJAN2005/273120N1602315W/FINAL//
5NWPN/QTY /WPNSS/WPNAA/WPNAS/WPNSA/WPNTYP/3-/-/- /B61NB//
CMDAUTH/CTF-2, USMTF, 2007/MCMDAUTH: USSOUTHCOM//
GENTEXT/REASON FOR DISABLEMENT/WEAPONS HAZARD BY
ADVANCING SUPERIOR FORCE. //
RMKS/WEAPONS DISABLED AS DIRECTED. NO MORE EQUIPMENT IN
AREA. WITHDRAWAL COMPLETE 171540Z. THIS IS FINAL REPORT.//

CUI
3-33
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section VII – OPREP-3 PINNACLE EMERGENCY EVACUATION

1. Specific Reporting Instructions. The OPREP-3 PINNACLE EMERGENCY EVACUATION


report is used for the emergency evacuation of nuclear weapons.

2 Report Content.

a. The OPREP-3 PINNACLE EMERGENCY EVACUATION is a USMTF report.


Instructions on USMTF voice and record message format and additional examples are contained
in reference (b).

b. USMTF set identifiers for required information are included in parentheses, when
applicable, include:

(1) DTG when the evacuation was implemented and TIMELOC of the operation and
report.

(2) EVACTO:

(a) Unit evacuated to.

(b) Quantity of weapons evacuated.

(c) Type of weapons evacuated.

(3) Unit completing evacuation and CMDAUTH of the evacuation.

(4) Reason for evacuation (GENTEXT-REASON FOR EVACUATION).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. USSTRATCOM requires a voice report from Navy for all OPREP-3 PINNACLE
EMERGENCY EVACUATION reports.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information and do not wait to make a voice
report in order to pass all information. Each line in the main body of the message contains a line
number that enables the message to be transmitted faster. Line numbers may be skipped if
information is not available. Templates for all voice message reports are contained in reference
(b).

CUI
3-34
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Number Line Name Line Description

Line One Date Enter the date-time Zulu that the event took place.
Line Two Location Location of the event, in LAT and LONG or UTM
coordinates, bearing and range or place name.
Line Three Receiving Unit Enter the unit designator of unit receiving weapons.
Line Four Destination Enter the location to which the units were evacuated or
moved, in LAT and LONG or UTM coordinates, bearing
and range or place name.
Line Five Number Enter the quantity of surface-to-surface weapons
evacuated.
Line Six Type Enter the type of surface-to-surface weapon evacuated.
Line Seven Number Enter the quantity of air-to-air weapons evacuated.
Line Eight Type Enter the type of air-to-air weapon evacuated.
Line Nine Number Enter the quantity of air-to-surface weapons evacuated.
Line Ten Type Enter the type of air-to-surface weapon evacuated.
Line Eleven Number Enter the quantity of surface-to-air weapons evacuated.
Line Twelve Type Enter the type of surface-to-air weapon evacuated.
Line Thirteen Number Enter the quantity of general weapons evacuated.
Line Fourteen Type Enter the general weapon type if other than above.
Line Fifteen By Enter the evacuation unit designator of the unit that
completed the evacuation.
Line Sixteen Authority Enter the identification of the commander authorizing
conduct of weapons evacuation.
Line Seventeen Reason Enter the reason for conduct of weapons evacuation.
Line Eighteen Narrative Enter additional information needed to clarify or
amplify information above.
Line Nineteen Time Enter the DTG for the message origin.

* The weapon identification and configuration are classified. If the report is submitted over
unclassified communications, a line number from reference (v) must be used.

d. Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE PINNACLE EMERGENCY EVACUATION


OVER
SHIP THIS IS HOMEPLATE SEND OPREP THREE PINNACLE EMERGENCY
EVACUATION OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE PINNACLE EMERGENCY EVACUATION
LINE ONE ONE SEVEN ZERO FOUR FIVE ZERO ZULU DECEMBER

CUI
3-35
CUI
OPNAVINST 3100.6K
10 Aug 2021

LINE TWO ZERO SEVEN THREE ONE ZERO TWO NORTH ONE SIX ZERO TWO
THREE ONE FIVE WEST
LINE NINE FIVE
LINE TEN BRAVO SIX ONE
LINE ONE THREE TWO ZERO
LINE ONE FOUR ONE THREE ZERO MEDIUM MACHINE GUN
LINE ONE FIVE CHARLIE TANGO ONE ONE ONE DECIMAL THREE DECIMAL ONE
LINE ONE SIX CHARLIE TANGO UNIFORM ONE THREE ONE ALFA WHISKEY
LINE ONE SEVEN FIRE IN VICINITY OF WEAPONS STORAGE
LINE ONE NINER ONE SEVEN ZERO FOUR FIVE FIVE ZULU
OVER

CUI
3-36
CUI
OPNAVINST 3100.6K
10 Aug 2021

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 PINNACLE EMERGENCY EVACUATION message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3PEV)
4 O REF * Reference
5 M FLAGWORD Flagword Information (PINNACLE
EMERGENCY EVACUATION)
6 M TIMELOC Event Time and Position
7 M EVACTO Evacuation Location Destination
Information
8 M CMDAUTH Authority Directing or Carrying Out
Emergency Action
9 M GENTEXT REASON FOR EVACUATION
10 O DECL Message Derivative or Original Source
for Classification, Reason for
Classification and DECL and Downgrading Data

* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC


(DMS: "JOINT STAFF J3 NMCC OPS")
USSTRATCOM OFFUTT AFB NE//J3/J31/J38//
CDR USNORTHCOM PETERSON AFB CO (required for OPREP-3Ps)
Combatant Commander (as appropriate):
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
CDR USCENTCOM MACDILL AFB FL
CDR USSOUTHCOM MIAMI FL
HQUSAFRICOM STUTTGART GE
CNO WASHINGTON DC

CUI
3-37
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMUSFLTFORCOM NORFOLK VA
Component Commander (as appropriate):
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
DIRNAVCRIMINVSERV QUANTICO VA
COMDT COGARD WASHINGTON DC
COMLANTAREA COGARD PORTSMOUTH VA
COMPACAREA COGARD ALAMEDA CA

(2) INFO addresses:

Chain of Command
ONI WASHINGTON DC
CHINFO WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (if incident is potentially reportable as a
MISHAP or is an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)

(3) Additional addresses:

(a) Message addresses for LANTFLT, COMUSNAVEUR, COMUSNAVAF


units:

ACTION addresses:

DTRA ABQ KIRTLAND AFB NM


COMUSFLTFORCOM NORFOLK VA

INFO addresses:

CMC PPO WASHINGTON DC (USMC personnel or mission incidents)


COMSUBFOR NORFOLK VA
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
SWFPAC BANGOR WA

CUI
3-38
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMMARFORCOM (for USMC controlled items)


FISC NORFOLK VA
DTRA ALEX WASHINGTON DC
SWFLANT KINGS BAY GA

(b) Message addresses for COMPACFLT units:

ACTION addresses:

DTRA ABQ KIRTLAND AFB NM


COMPACFLT PEARL HARBOR HI

INFO addresses:

CMC PPO WASHINGTON DC (USMC personnel or mission incidents)


COMNAVSURFPAC SAN DIEGO CA (surface ships only)
COMSUBPAC PEARL HARBOR HI (submarines only)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
SWFPAC BANGOR WA
COMMARFORCOM (for USMC controlled items)
DTRA ALEX WASHINGTON DC

(4) Message body:

MSGID/OPREP-PEV, USMTF, YYYY/CTU111.3.1/001//


REF/A/DESC: INITIAL VOICE REPORT TO NMCC/CTU111.32 /170455ZDEC2005//
FLAGWORD/PINNACLE/EMERGENCY EVACUATION//
TIMELOC/170754ZDEC2005/SHELBY/FOLUP//
5EVACTO
/DE/EVACTO /EVACLOC /QTY /WPNTYP
/01/CTU133.1.4 /LAMA LAMA BOMB DEPOT /5 /B61-4
/02/CTU133.1.4 /LAMA LAMA BOMB DEPOT /20 /130MMG//
CMDAUTH/CTU 131 AW/MCMDAUTH: NAVPACCO//
GENTEXT/REASON FOR EVACUATION/FIRE NEAR WEAPONS STORAGE.//

CUI
3-39
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section VIII – OPREP-3 WHITE PINNACLE

1. Specific Reporting Instructions. The OPREP-3 WHITE PINNACLE is an unclassified


exercise flagword used in exercise messages that contain simulated, CRITIC from operating
forces to the NMCC. This exercise is used to measure the timeliness of the OPREP-3
PINNACLE report.

a. Upon receipt of a WHITE PINNACLE tasking, units must submit a WHITE PINNACLE
acknowledgement report to the NMCC EA cell by either voice or record copy, whichever is
fastest.

b. The time standard for WHITE PINNACLE exercises is 20 minutes, measured from the
communications origination time, i.e. , when the unit operations center or command center or
duty officer receives the WHITE PINNACLE tasking, to time of receipt by the NMCC.

c. Direct voice contact between the tasked units and the NMCC is the goal when voice
circuits are used using the NMCC phone numbers listed in the phone matrix in table 2-2.

d. No record copy message traffic is required when the WHITE PINNACLE exercise is
successfully completed using voice contact.

e. When a WHITE PINNACLE acknowledgement report is received by multiple methods,


the exercise will be considered successful as long as at least one acknowledgement meets the 20-
minute time criteria.

f. NMCC-EA will investigate all unsatisfactory exercise WHITE PINNACLEs and provide
a copy of the results of their investigation to the Regional Operations Support Division,
Operations, Training and Evaluation Branch prior to the on-duty shift change.

g. NMCC-EA will notify the originating command center when the WHITE PINNACLE
exercise is completed.

2. Report Content. OPREP-3 WHITE PINNACLE report must include:

a. Unit tasked to exercise WHITE PINNACLE procedures.

b. Location (if not classified). This information may assist in determining locations that
may preclude timely reporting.

c. Tasking combatant commander.

d. DTG of the tasking message or voice notification to unit.


e. Unit time of receipt.

CUI
3-40
CUI
OPNAVINST 3100.6K
10 Aug 2021

f. Message acknowledgement that exceeds the 20-minute time criteria will contain
information addressing any known delays or initiate tracer action, as appropriate. A FOLUP
message to the NMCC EA will provide results on any tracer action initiated.

g. Use precedence of FLASH or URGENT in DMS for all record copy transmissions.

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description


For NMCC-EA:

Line One Exercise Enter “EXERCISE WHITE PINNACLE.”


Line Two Tasking Enter “This is NMCC with Exercise
OPREP-3 WHITE PINNACLE Tasking.”
Line Three Unit Tasked Enter the name of the "Tasked Unit.”
Line Four Unit Enter the “Unit location (if not classified).”
Standort
Line Five Combatant Enter the tasking combatant command
Command
Line Six DTG of Enter the DTG of the tasking message or voice
Tasking notification to the tasked unit.
Line Seven DTG of Enter the DTG of receipt.
Receipt If Line Eight is not used, transmit “OVER.”
Line Eight Special Enter any additional instructions Instructions
required. Transmit “OVER.”

For Tasked Unit:

Line Nine Unit Call Up Enter “This is (Unit Name) with


EXERCISE OPREP-3 WHITE PINNACLE
acknowledgement.”

CUI
3-41
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Ten Command Enter “EXERCISE WHITE PINNACLE was


Center initiated by (command center) at (DTG ZULU).”
Line Eleven Unit Time Enter “The time of receipt at this location is
Of Receipt (DTG ZULU).”
Line Twelve Time of Enter “The time of receipt for acknowledgement
Acknow- to NMCC-EA is(DTG ZULU).” Transmit
ledgement “OVER.”

For NMCC-EA:

Line Thirteen NMCC EA Enter “This is NMCC EA, (concur or


Concur or nonconcur) with NMCC EA time of
Nonconcur receipt of (DTG ZULU).”
Line Fourteen NMCC EA UP Enter “This is NMCC EA, this
SAT or UNSAT exercise is (satisfactory or unsatisfactory).”
Line Fifteen NMCC Call Enter “This is NMCC EA. Please
Up Reason reply with record copy of reasons(s)
for late acknowledgement.”
Line Sixteen Authen- Enter the appropriate authentication code(s) for
tication this message if message authentication is required.
Authentication will be per established procedures.
Line Seventeen Exercise Enter “EXERCISE WHITE PINNACLE.”

c. Voice Message Report Example

(1) For NMCC-EA:

HOMEPLATE THIS IS SHIP OPREP THREE WHITE PINNACLE OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE WHITE PINNACLE OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE WHITE PINNACLE
LINE ONE EXERCISE WHITE PINNACLE
LINE TWO THIS IS NOVEMBER MIKE CHARLIE CHARLIE WITH WHITE PINNACLE
TASKING
LINE THREE SHIP
LINE FOUR NORTH ISLAND CALIFORNIA
LINE SIX TWO EIGHT ONE SIX ZERO ZERO ZULU JULY TWO ZERO ZERO THREE
LINE SEVEN TWO EIGHT ONE SIX ZERO TWO ZULU JULY TWO ZERO ZERO THREE
OVER

(2) For Tasked Unit:

CUI
3-42
CUI
OPNAVINST 3100.6K
10 Aug 2021

LINE NINER SHIP THIS IS HOMEPLATE WITH ACKNOWLDGEMENT OF EXERCISE


WHITE PINNACLE
LINE ONE ZERO EXERCISE WHITE PINNACLE INITIATED BY NOVEMBER MIKE
CHARLIE CHARLIE AT TWO EIGHT ONE SIX ZERO TWO ZULU JULY TWO ZERO
ZERO THREE
LINE ONE ONE THE TIME OF RECEIPT AT THIS LOCATION IS TWO EIGHT ONE SIX
ZERO ZERO ZULU JULY TWO ZERO ZERO THREE
LINE ONE TWO THE TIME OF RECEIPT FOR ACKNOWLEDGMENT TO NOVEMBER
MIKE CHARLIE CHARLIE ECHO ALPHA IS TWO EIGHT ONE SIX ZERO FOUR ZULU
JULY TWO ZERO ZERO THREE
OVER

(3) For NMCC-EA:

LINE ONE THREE THIS IS NOVEMBER MIKE CHARLIE CHARLIE ECHO ALFA
CONCUR WITH ACKNOWLEDGEMENT TWO EIGHT ONE SIX ZERO TWO ZULU JULY
TWO ZERO ZERO THREE
LINE ONE FOUR THIS IS NOVEMBER MIKE CHARLIE CHARLIE COMMA EXERCISE
WHITE PINNACLE IS SATISFACTORY
LINE ONE SIX AUTHENTICATION IS BRAVO JULIET BRAVO
LINE ONE SEVEN EXERCISE WHITE PINNACLE
OUT

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. Formats for all data sets are contained in reference (b). MTF data sets used in the
OPREP-3 WHITE PINNACLE message:

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3WP)
4 O REF * Reference

CUI
3-43
CUI
OPNAVINST 3100.6K
10 Aug 2021

SEQ OCC SETID Set Format Name


5 M WPTASK WHITE PINNACLE Tasking
7 O GENTEXT SPECIAL INSTRUCTIONS
8 M HEADING UNIT ACKNOWLEDGEMENT
9 O UNITACK Unit Acknowledgement
10 O GENTEXT REASON FOR EXCEEDING TIME CRITERIA
11 O GENTEXT TRACER ACTION
12 O POC * Point of Contact Information
13 O DECL Message Derivative or Original Source
for Classification, Reason for Classification and
DECL and Downgrading Data

* Repeatable set

c. Record Message Example

(1) ACTION addresses:

JOINT STAFF WASHINGTON DC//NMCC-EA//


Tasking Combatant Command

(2) INFO addresses:

Appropriate Chain of Command


DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Tasking Message Example (from tasking combatant commander to tasked command):

EXER/OPREP-3 WHITE PINNACLE//


MSGID/OPREP-3WP, USMTF, YYYY/NMCC/3788/JUN//
HEADING/WHITE PINNACLE TASKING//
DIEGO/NIMITZ//
GENTEXT/SPECIAL INSTRUCTIONS/DO NOT INITIATE TRACE
ACTION.//
POC/BROWN/MAJ/NMCC-EA/LOC: PENTAGON EAST/TEL: 757-825-
5555//

(4) Acknowledgement Message Example (from tasked command to NMCC-EA):

EXER/OPREP-3 WHITE PINNACLE//


MSGID/OPREP-3WP, USMTF, YYYY/3RD FTG GP/0021/JUN//
HEADING/UNIT ACKNOWLEDGMENT//

CUI
3-44
CUI
OPNAVINST 3100.6K
10 Aug 2021

UNITACK/NIMITZ/NASNI SAN DIEGO/ACK/32ND COMM CP /UNIT:


231602ZJUN2005/NMCC: 231605ZJUN2005//

CUI
3-45
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section IX – OPREP-3 PINNACLE SPECIAL REPORTS

Additional information and reporting requirements for these reports are contained in references
(a) and (b).

1. OPREP-3 PINNACLE-COMMAND ASSESSMENT (OPREP-3PCA). Used by a combatant


commander to report the assessment of a developing or potential crisis situation.

2. OPREP-3 PINNACLE-LERTCON STATUS OF ACTION (OPREP-3LSOA). Used to


immediately notify the NMCC of a combatant commander's actions relative to changes in the
LERTCON of forces.

3. OPREP-3 CRESCENT EDGE (OPREP-3CE). Used by any unit to advise SAP program
managers of events or incidents that meet OPREP-3 reporting criteria outlined in reference (x).

4. NUDETSUM Reporting Procedures. Used to report information pertaining to nuclear


detonations in areas outside the North American continent. Nuclear detonations on the North
American continent must be reported by USSTRATCOM.

CUI
3-46
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHAPTER 4 – OPREP-3 NAVY BLUE REPORTS

Section I – OPREP-3 NAVY BLUE

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE report is used by any unit to
provide the CNO and other naval commanders with immediate notification of incidents of
military, political or media interests that are of high Navy, vice national level, interest and have
been categorized into operational incidents, personnel incidents and other incidents. The reports
are submitted to provide “as-it-happens” information to the chain of command.

a. Major Incidents.

(1) For the purpose of this instruction, a major incident is defined as an incident that
results in loss or degradation in the ability of a command to perform its mission, degradation,
destruction or non-availability of a Task Critical Asset published by OPNAV N46 or as
determined by the CO. If in doubt, report as an OPREP-3 NAVY BLUE.

(2) An OPREP-3 NAVY BLUE is required for “major” incidents such as fire, flooding,
loss of communications, network outages, computer intrusion, loss and or compromise of
classified information and instances that involve critical personnel, their families or equipment.

(3) For major computer intrusion events, refer to SECNAVINST 5239.19 and reference
(g) for guidance. In addition to the line items required by reference (g), include a plain language
executive summary of the incident, providing incident details and operational impacts, at the
beginning of the message.

b. Operational Incidents.

(1) Fires, flooding, explosions, collisions, allisions, groundings or other major incidents
to Navy ships, submarines, aircraft or MSC vessels resulting in major damage to spaces,
equipment, injury or death to personnel.

(2) Near or actual collisions or allisions of minor significance involving Navy ships or
aircraft. (For near or actual collisions of major significance, report as an OPREP-3
PINNACLE.) Devices attached to, deployed from or towed by a ship or aircraft are considered
an extension of the reporting unit. Such devices include, but are not limited to, communication
buoys, towed arrays, Nixie, dipping sonar, magnetic anomaly detectors and objects or vessels
under tow.

(3) Any other major incidents, as defined in subparagraph 1a, involving damage to Navy
or MSC ships and aircraft.

(4) Class A or B aircraft mishaps (if not reportable by an OPREP-3 PINNACLE).

CUI
4-1
CUI
OPNAVINST 3100.6K
10 Aug 2021

(5) The loss at sea of any Navy vessel, rigid hull inflatable boat or other small craft.

(6) Aggressive actions by foreign entities toward U.S. Navy ships or aircraft.

(7) Any incident (except against forces previously declared hostile by higher authority) in
which live ordnance is expended with the intent to hit but not disable in response to a violation or
suspected attempt to violate a U.S. Navy perimeter or maritime warning zone, including events
in foreign ports. Regardless of intent, if personnel are injured or killed in the engagement or the
vessel is disabled, an OPREP-3 PINNACLE notification is required.

(8) Any incident where warning shots are fired in support of counter drug operations.

(9) SAR incident's initial report, to include SARs that are in the alert or uncertainty
phase. (The OPREP-3 NAVY UNIT SITREP will be used to provide daily updates to the chain
of command.)

(10) Unintentional launch of a conventional missile, torpedo or other live ordnance.

(11) Any discharge of a government weapon that causes a fatality or injury to


personnel. (Negligent discharges that do not meet these criteria must be reported as an OPREP-3
NAVY UNIT SITREP.)

(12) Acts or attempts to willfully destroy property of the Navy.

(13) Any loss of communications and control networks that significantly alters,
hinders or impacts current operations or missions. Specific guidance for NC3 FSBS Outage
Reports: An OPREP-3 NAVY BLUE is required for a complete loss of the ability to deliver
EAM via the FSBS transmitter supporting either LANT or PAC AOR or both that is resolved in
greater than 3 minutes but less than 15 minutes. A PINNACLE report is required for outages
exceeding 15 minutes or with no identifiable cause.

(14) Computer intrusion events that result in the loss of or significant degradation to,
operational capability. Reference (g) reporting requirements also remain in effect.

c. Personnel Incidents.

(1) Death of, critical injury to or missing COs or senior officials (flag officer or
equivalent).

(2) Death or serious injury to personnel embarked on Navy or MSC ships and aircraft –
or while on government property both on and off duty.

CUI
4-2
CUI
OPNAVINST 3100.6K
10 Aug 2021

(3) Death, serious injury or serious illness in which survivability or full recovery with
currently available medical care is reasonably in question.

(4) Death or serious personal injury of a civilian caused by a Service member, including
civilian traffic accident deaths.

(5) Significant incidents committed by military personnel including, but not limited to
(refer to appendix B for additional guidance, action and or information addresses and specific
message format requirements):

(a) Death by suicide of military service members, their dependents or civilian DoN
employees.

(b) Murder.

(c) Sexual Assault.

(d) Armed robbery.

(e) Aggravated assault or assault with a deadly weapon.

(f) Kidnapping.

(g) Carjacking.

(h) Burglary of an occupied dwelling.

(i) Child sexual abuse.

(k) Supremacist activities, as defined in reference (y).

(k) Extremist groups, as defined in reference (l).

(6) Lesser incidents may require an OPREP-3 NAVY BLUE report. Incidents must be
reported using an OPREP-3 NAVY BLUE report if there is media attention. If there is no media
attention, then report using an OPREP-3 NAVY UNIT SITREP (refer to appendix B for
additional guidance):

(a) Domestic violence or abuse. Any report of domestic violence or domestic abuse
must include the date and location of the Service member’s most recent operational,
expeditionary or individual augmentee deployment.

(b) Child abuse and or neglect.

CUI
4-3
CUI
OPNAVINST 3100.6K
10 Aug 2021

(c) Suicide Related Behaviors. Any report of suicide related behaviors must include
date and location of most recent operational, expeditionary or individual augmentee deployment.

(d) EO incidents – formal complaint or report. Allegation submitted in writing via


NAVPERS 5354/2, UCMJ article 92 for violation of EO or Sexual Harassment policy, UCMJ
Article 138, US Navy Regulation Article 1150, communication with Inspector General or
Elected Official, (NAVPERS 1627/7 report or any other communication the Commander deems
appropriate) of sexual harassment, unlawful discrimination based on race, color, religion, sex (to
include gender identity), national origin or sexual orientation or harassment based on race, color,
religion, sex (to include gender identity), national origin or sexual orientation. Commanders
must consult with a JAG in all alleged sexual harassment cases and must consult a CCS in all
alleged discrimination, harassment and sexual harassment cases. The final OPREP-3 report must
include the name, command name and contact information of the JA and CCS consulted.

(e) Hazing – report all substantiated and unsubstantiated incidents. Include these data
elements: relationship between complainant and alleged offender, general nature of the alleged
hazing incident (physical, psychological, verbal, technological, a combination, etc.), location of
the hazing incident (on-duty, off-duty, etc.), duty status of both the complainant and alleged
offender at the time of the alleged hazing incident (training, temporary duty, present for duty,
leave, etc.).

(f) Bullying – report all substantiated and unsubstantiated incidents. Include these
data elements: relationship between complainant and alleged offender, general nature of the
bullying incident (physical, psychological, verbal, technological, a combination, etc.), location of
the bullying incident (on-duty, off-duty, etc.), duty status of both the complainant and alleged
offender at the time of the alleged bullying incident (training, temporary duty, present for duty,
leave, etc.).

(g) Motor vehicle accidents related to the use of alcohol or illegal substances.

(h) Any incident involving a firearm, regardless of whether or not the firearm was
discharged.

Note: Definitions of the listed crimes can be found in reference (h). General guidance is
included in appendix B.

d. Incidents of MLSR or AA&E. See reference (z) and appendix C for amplifying
guidance.

e. Marine Mammal Incidents. See reference (aa) and appendix D for amplifying guidance
to report confirmed or unconfirmed ship-whale strike, stranding or other marine mammal
incidents. The marine mammal incidents include:

CUI
4-4
CUI
OPNAVINST 3100.6K
10 Aug 2021

(1) Whale strike by a U.S. Navy vessel.

(2) Stranding event within 100 nautical miles (NM) of Navy vessels, Navy homeports or
Navy ranges or operating areas.

(3) Stranding event that has occurred within 100 NM and within 3 days after the start of
naval operations, exercises or training involving active sonar or weapons impact.

(4) Stranding event or claims of unusual marine mammal behavior for which naval
operations, exercises or training have been implicated or are likely to be implicated, as the cause
of the event.

f. Other Incidents.

(1) Discharges or spills of material or fluids that might be considered pollutants, which
endanger critical water areas, have the potential to generate public concern, become the focus of
enforcement action or pose a threat to public health or welfare.

(2) Loss or possible compromise of Top Secret, secret or confidential material or


equipment, to include information technology equipment such as a laptop or personal digital
assistant, that results in the loss of or significant degradation to, operational capability or could
possibly impact other U.S. Forces. Reporting requirements as identified in reference (f) also
remain in effect.

(3) All serious events or incidents in foreign countries involving military personnel, their
dependents, US government civilian personnel and contractors; or events or incidents involving
host nation personnel that could generate media or political interest.

(4) Violation of the letter or spirit of the U.S.-Russia agreement for prevention of
incidents on and over the high seas per reference (ab).

(5) Significant damage to civilian property resulting from actions by members of the
Department of the Navy.

(6) Labor strikes which may significantly impair operational readiness, high priority
industrial production for U.S. Navy projects or mobility.

(7) Disorders or natural disasters of minor significance, if naval assistance is provided or


requested.

(8) Disease diagnosis of potential epidemic significance or the presumptive diagnosis of


any disease that could result in a quarantine of naval personnel to the extent that it may have an
operational impact. Refer to reference (ac) for additional information on disease reporting.

CUI
4-5
CUI
OPNAVINST 3100.6K
10 Aug 2021

(9) Fraud, waste, abuse, gross inefficiency or mismanagement that could involve high-
level Navy interest or national media inquiry.

(10) An event involving radioactive material or radiation exposure which is not


classified as a reactor accident under section III of chapter 4 of this instruction, but which
presents or is expected to present a hazard to public health and safety or is of such a nature as to
warrant immediate notification of cognizant higher commands. Included in this category are
those events having domestic or international implications and those that are likely to give rise to
inquiries by the public or press. Inadvertent discharges of reactor coolant from naval nuclear
propulsion plants do not warrant notification under this section, but should be reported under
reference (ad) or reference (ae).

(11) Law of war reportable incidents. All reportable incidents must be promptly
reported via the operational chain of command and via service channels to the CNO. Per
references (s), (t) and (u), a reportable incident is a possible, suspected or alleged violation of the
law of war for which there is credible information or conduct during military operations other
than war that would constitute a violation of the law of war if it occurred during an armed
conflict. Reportable incidents that could constitute grave breaches of the Geneva Convention per
enclosure (1) of reference (s) must be reported via OPREP-3 PINNACLE. To report a reportable
incident that does not apparently constitute a grave breach, use an OPREP-3 NAVY BLUE.

(12) Any incident requiring the actual execution of an organization’s COOP plan.
Voice and written reports should indicate the event causing plan execution. Follow-on reporting
should indicate the location and contact information of the command center, senior leadership
and the status of the organization.

(13) Incidents in an OCONUS environment: All incident reports involving the public
or host nationals should include as much information as possible, to include suspected drug and
alcohol abuse, host national or civilian police involvement and whether media interest is
anticipated. Incidents, especially those involving physical assault and sexual assault by Navy
members on civilians or host nationals, will typically garner significant media coverage and will
reflect negatively on the Navy. Commanders should consider OPREP-3 NAVY BLUE
REPORTS for these incidents of high media interest. The command PAO is required to notify
respective ISIC PAO via telcon (or e-mail if telcon is not possible) within one hour of learning of
the incident in order to coordinate a media response. All OCONUS incident reports should
consider the PLAD for the local American Embassy.

g. Any incident of high-level Navy interest which does not fall into the category of any
other report in the OPREP-3 PINNACLE or OPREP-3 NAVY BLUE series.

2. Report Content. The OPREP-3 NAVY BLUE report is a USMTF based report that is being
incorporated into reference (b). It is based on the OPREP-3 message. The message example is
edited accordingly.

CUI
4-6
CUI
OPNAVINST 3100.6K
10 Aug 2021

a. In general, voice and record message reports should address:

(1) What happened?

(2) Who is or was involved?

(3) Where did it happen?

(4) When did it happen?

(5) Why did it happen?

(6) What action is ongoing?

(7) What future action is contemplated?

(8) What is the impact on the command's mission capability?

(9) Is any assistance required?

(10) Is media attention anticipated?

(11) Command POC and 24-hour contact (command duty officer (CDO) or similar)
information.

b. Incident reports require additional specific information in the GENTEXT-INCIDENT


IDENTIFICATION AND DETAILS section of the record message:

(1) Aircraft incident reports must include:

(a) Aircraft model, bureau number, reporting custodian and custodian location.

(b) Pilot’s rank, injury code (if known) and the number of other persons on board and
their injuries.

(c) Mission and phase of operations, e.g. , taxi, take-off, in flight, approach, landing.

(2) Personnel Incident Report. See appendix B.

(3) AA&E Incident Report. See appendix C.

(4) Marine Mammal Incident Report. See appendix D.

CUI
4-7
CUI
OPNAVINST 3100.6K
10 Aug 2021

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. Include as much of the information in paragraph 2a in the initial voice report as possible,
but do not delay the initial report to gather additional information. The information must be
addressed in the initial and amplifying record messages.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description

Line One Incident Enter the incident identification, location and details.
Line Two Narrative Enter any additional information about the incident.

d. Voice Message Report Example

STARBURST THIS IS MOONGLOW OPREP THREE NAVY BLUE


OVER
MOONGLOW THIS IS STARBURST SEND OPREP THREE NAVY BLUE
OVER
THIS IS MOONGLOW
NORMAL
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE POSSIBLE HOMICIDE BREAK NAHA OKINAWA JAPAN
LINE TWO ECHO THREE APPREHENDED BY SHORE PATROL WHILE
ATTEMPTING TO DISPOSE OF BLOOD-STAINED UNIFORM
BREAK
MAY HAVE KILLED FEMALE FOREIGN NATIONAL
BREAK
INCIDENT UNDER INVESTIGATION BY NOVEMBER CHARLIE INDIA
SIERRA AND LOCAL AUTHORITIES
OVER

4. Record Message Reports.


a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

CUI
4-8
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. OPREP-3 NAVY BLUE MTF data sets are the same as for the generic OPREP-3
message report contained in reference (b), with the addition of the flagword set after the REF set.

SEQ OCC SETID Set Format Name


1 C EXER Exercise Identification
2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3)
4 O REF * Reference
5 M FLAGWORD Flagword Information (NAVY BLUE)
6 M TIMELOC Event Time and Position
7 M GENTEXT INCIDENT IDENTIFICATION AND DETAILS
8 O DECL Message Derivative or Original Source for Classification,
Reason for Classification and DECL and Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC
USSTRATCOM OFFUTT AFB NE (for all SSBNs, fleet and shore
installations that support the nuclear deterrence program)
COMUSFLTFORCOM NORFOLK VA
Component Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders

(2) INFO addresses:

Chain of Command
CHINFO WASHINGTON DC
CNIC WASHINGTON DC
ONI WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (incident potentially reportable as a
MISHAP or an actual MISHAP or involved a firearm)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore
installations that support the nuclear deterrence program)

CUI
4-9
CUI
OPNAVINST 3100.6K
10 Aug 2021

DIRNAVCRIMINVSERV QUANTICO VA

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


CNO WASHINGTON DC (loss or compromise of classified information)
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC
NAVORDSAFSECACT INDIAN HEAD MD (ordnance incidents)
COMNAVNETWARCOM VIRGINIA BEACH VA (loss of communications)
BUMED FALLS CHURCH VA
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
SOPA
Regional Commander
Installation Commander
Local American Embassy, if overseas
Appropriate U.S. Coast Guard District
NAVCYBERDEFOPSCOM NORFOLK VA (computer intrusion)

(4) For personnel incident reports, use the addresses and format listed in appendix B.

(5) Message body:

MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//


FLAGWORD/NAVY BLUE/-//
TIMELOC/110429ZMAY2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: POSSIBLE HOMICIDE
2. DATE OF INCIDENT: 11MAY2005
3. TIME OF INCIDENT: 0128L
4. LOCATION OF INCIDENT: OLONGAPO CITY, REPUBLIC OF
THE PHILLIPPINES.
5. INCIDENT: MALE E-3 APPREHENDED BY SHORE PATROL
WHILE ATTEMPTING TO DISPOSE OF BLOOD-STAINED
UNIFORM. SVCM MAY HAVE KILLED FEMALE FOREIGN
NATIONAL. INCIDENT UNDER INVESTIGATION BY
NAVCRIMINVSERV AND LOCAL AUTHORITIES.

CUI
4-10
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section II – OPREP-3 NAVY BLUE BENT SPEAR

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE BENT SPEAR report is used
by any unit to report to the CNO and appropriate naval commanders any U.S. nuclear weapons
or nuclear weapons system incident, not reportable as an OPREP-3 PINNACLE NUCFLASH,
BROKEN ARROW or EMPTY QUIVER, that could:

a. Bring the safety or control of a nuclear weapon into doubt.

(1) Increases the probability of explosion or radioactive contamination.

(2) Requires assessment, examination or recertification by Department of Energy or


NNSA.

(3) Results in the partial or complete unauthorized arming or initiation of a firing


sequence.

(4) Results in the knowledge or suspicion that a nuclear weapon has been partially or
fully armed.

b. Require immediate action in the interest of safety or nuclear weapon security (e.g.,
weapon security incidents such as a permissive action link anomaly).

c. Result in or have the potential to result in, adverse public reaction.

d. Lead to nuclear weapon incident category events or warrant the informational interest or
action of any of these officials or agencies:

(1) Joint Forces Commander.

(2) Appropriate Military Department or Service.

(3) Under Secretary of Defense (Acquisition, Technology and Logistics).

(4) Assistant Secretary of Defense (International Security Affairs).

(5) Assistant Secretary of Defense (Public Affairs).

(6) Federal Emergency Management Agency (incident located in the United States).

(7) NNSA.

(8) USSTRATCOM.

CUI
4-11
CUI
OPNAVINST 3100.6K
10 Aug 2021

2. Report Content.

a. The OPREP-3 NAVY BLUE BENT SPEAR is a USMTF based report that is being
incorporated into reference (b). It is based on the OPREP-3BS report. The message example is
edited accordingly.

b. Per reference (a), the flagword PINNACLE may be added at any level of command to
expedite forwarding of this message to the J3.

c. The weapon identification and configuration are classified. If this report is submitted
over unclassified communications, a line number in reference (v) must be used.

d. If applicable, the status of a reactor onboard should be addressed to assist in prioritization


of actions.

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description

Line One Time Enter the DTG of the reported event’s occurrence
Line Two Location Enter the event location using LAT and LONG or UTM
coordinates, bearing and range or place name.
Line Three Number Enter the quantity of weapons involved in the incident
being reported.
Line Four Type Enter the type weapon being reported (Surface-to
Surface, Air-to-Air, Air-to-Surface, Surface-to-Air,
or General Weapon Type).*
Line Five Ship If nuclear-capable ship is involved, enter designation
of the ship.
Line Six Type Enter the aircraft type that is being reported on.
Line Seven Damages Enter damages being reported
Line Eight Casualties Enter the number of persons killed during the reported
event.

CUI
4-12
CUI
OPNAVINST 3100.6K
10 Aug 2021

Line Number Line Name Line Description

Line Nine Wounded Enter the number of persons wounded during the
reported event.
Line Ten Missing Enter the number of persons missing as a result of the
reported event.
Line Eleven Incident Enter the cause of the event and details.
Line Twelve Condition Enter the weapon condition and safety measures.
Line Thirteen Narrative Enter additional information needed to clarify or
amplify information above. If applicable, address the
status of a reactor onboard.
Line Fourteen Time Enter the DTG for the message time of origin.

* The weapon identification and configuration are classified. If the report is submitted over
unclassified communications, a line number in reference (v) must be used.

c. Voice Message Report Example

STARDUST THIS IS MOONGLOW OPREP THREE NAVY BLUE BENT SPEAR OVER
MOONGLOW THIS IS STARDUST SEND OPREP THREE NAVY BLUE BENT SPEAR
OVER
THIS IS MOONGLOW
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE BENT SPEAR
LINE ONE ZERO ONE ZERO SIX TWO FIVE ZULU JANUARY TWO ZERO ZERO NINER
LINE TWO THREE NINER ZERO FOUR ZERO SEVEN NORTH ONE ZERO NINER
THREE FOUR ONE ONE EAST
LINE THREE ONE
LINE FOUR AIR TO GROUND MISSILE FOUR FIVE BRAVO
LINE SIX AIRCRAFT TYPE FOXTROT ONE ONE ONE GOLF
LINE SEVEN DAMAGE LOWER RIGHT FIN ASSEMBLY
LINE ONE FOUR ZERO ONE ZERO SIX THREE ZERO ZULU JANUARY
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. The OPREP-3 NAVY BLUE BENT SPEAR MTF data sets are the same as for the
OPREP-3 BENT SPEAR message report contained in reference (b).

CUI
4-13
CUI
OPNAVINST 3100.6K
10 Aug 2021

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3BS)
4 O REF * Reference
5 M FLAGWORD FLAGWORD Information (NAVY BLUE or BENT SPEAR)
6 M TIMELOC Event Time and Position
7 M EVTYP Nuclear Weapon Event Type
8 C HEADING Casualties and Damages
9 O CASUALTY Friendly Personnel Casualty Count
10 O GENTEXT Damages
11 O GENTEXT Incident Cause and Details
12 O GENTEXT Weapon Condition and Safety
13 O GENTEXT News Releases
14 O DECL Message Downgrading or DECL Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC
USSTRATCOM OFFUTT AFB NE
COMUSFLTFORCOM NORFOLK VA
Component Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (for ordnance related
incidents)

(2) INFO addresses:

JOINT STAFF WASHINGTON DC


Chain of Command
CHINFO WASHINGTON DC
CNIC WASHINGTON DC

CUI
4-14
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMNAVAIRSYSCOM PATUXENT RIVER MD


COMNAVSAFECEN NORFOLK VA
COMNAVSEASYSCOM WASHINGTON DC
DIRSSP WASHINGTON DC
NAVEODTECHDIV INDIAN HEAD MD
DTRA ABQ KIRTLAND AFB NM
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
BUMED FALLS CHURCH VA (personnel injuries and contamination)
ONI WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (incident potentially reportable as a
MISHAP or an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)
DIRNAVCRIMINVSERV QUANTICO VA

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC (ship or ship's system incidents)
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (ordnance incidents)
BUMED FALLS CHURCH
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
CNIC WASHINGTON DC
SOPA
Regional Commander
Installation Commander
Appropriate U.S. Coast Guard District
NAVCYBERDEFOPSCOM NORFOLK VA (computer intrusion)

(4) Message body:

EXER/OLIVE DRAB 2009//


MSGID/OPREP-3BS, USMTF, YYYY/CTF-2/001//
REF/A/DESC:INITIAL VOICE REPORT TO NMCC/CTF-

CUI
4-15
CUI
OPNAVINST 3100.6K
10 Aug 2021

2/010630ZJAN2009//
FLAGWORD/NAVY BLUE/BENT SPEAR//
TIMELOC/010652ZJAN2009/390407N1093411E/FINAL//
EVTYP/QTY: 1/WPNAS:AGM45B/-/ACTYP:F111G//
GENTEXT/CASUALTIES AND DAMAGES//
CASUALTY/KILLED: 0/WOUNDED:0/MISSING:0//
GENTEXT/INCIDENT CAUSE AND DETAILS/DETROIT 01 (F-
111) FO RTB FM MSN 37123 EXPERIENCED HVY TURB.
RESULT IN DAMAGED RT LOWER FIN ASSEMBLY ON WPN.//
GENTEXT/WEAPON CONDITION AND SAFETY MEASURES/NO
SAFETY MEASURES REQUIRED.//
RMKS/VOICE REPORT INITIATED 010630Z. THIS IS THE
FINAL REPORT.//

CUI
4-16
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section III – OPREP-3 NAVY BLUE FADED GIANT

1. Specific Reporting Instructions.

a. The NAVY BLUE FADED GIANT report is used by any unit to provide the CNO and
other naval commanders with immediate notification of any nuclear reactor accident involving
naval nuclear propulsion reactors under custody of the U.S. Navy. Such accidents are defined in
references 1b and 1c:

b. Nuclear reactor accident. An uncontrolled reactor criticality resulting in damage to the


reactor core or an event such as a loss of coolant which would likely result in the release of
fission products from the reactor core.

c. Radiological accident. A loss of control of radioactive material, which presents a hazard


to life, health or property or which may result in a member of the general population exceeding
exposure limits for ionizing radiation. Radiological accidents involving naval nuclear reactors,
other naval nuclear energy devices or radioactive materials under the custody of the U.S. Navy
or an event involving radioactive material or radiation exposure that does not constitute a
radiological accident but is of such a nature as to warrant immediate notification of cognizant
higher commands, must be reported by OPREP-3 NAVY BLUE per chapter 4, section I.

d. For SSBNs, there is an expectation that the presence and any potential effect on nuclear
weapons be addressed in the voice and record message reports for clarity on the event and to
help set priorities of response.

2. Report Content.

a. Per reference (a), the flagword PINNACLE may be added at any level of command to
expedite forwarding of this message to NMCC J3.

b. The OPREP-3 NAVY BLUE FADED GIANT (FG) is a USMTF based report that is
being incorporated into reference (b). It is based on the OPREP-3FG message. The message
example is edited accordingly.

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b). Voice reports for this section do not

CUI
4-17
CUI
OPNAVINST 3100.6K
10 Aug 2021

require the use of line 3 and lines 8 through 16, however these lines may be included if the
information is available and is of sufficient importance.

Line Number Line Name Line Description


Line One Time Enter the day, hour, minutes and time zone of the reported
event's occurrence.
Line Two Location Enter the location of the event using LAT and LONG or UTM
coordinates, Bearing and Range or the place name.
Line Three Damages Enter the damage resulting from the event.
Line Four Casualties Enter the number of persons killed during the reported
event.
Line Five Wounded Enter the number of persons wounded during the reported
event.
Line Six Missing Enter the number of persons missing as a result of the
reported event.
Line Seven Incident Enter the cause of the accident and associated details.
Specifically report reactor power and operating history at
time of accident, status of primary and secondary
containment, status of immediate actions, functioning of
reactor plant systems, fission product release inside the
ship and to the environment, significant Navy authorities
notified, etc. Identify affected ship, if other than originator.
Line Eight Radiation Enter radiation information.
Line Nine Location Enter the location of the radiation reading using
LAT and LONG or UTM coordinates, Bearing and Range or
the place name.
Line Ten Time Enter the day and time that the radiation reading was taken.
Line Eleven Direction Enter the wind direction in degrees from true north.
Line Twelve Speed Enter the effective wind speed affecting the movement of a
nuclear cloud, expressed in kilometers per hour, miles per
hour or knots.
Line Thirteen Condition Enter information on the system condition and safety
measures.
Line Fourteen News Enter information on prepared and approved news releases,
Releases potential public and political implications. Include extent
of notification to civilian authorities.
Line Fifteen Narrative Enter additional information needed to clarify or amplify
information above. Address presence of weapons
potentially affected onboard.
Line Sixteen Time Enter the DTG for the message time of origin.

CUI
4-18
CUI
OPNAVINST 3100.6K
10 Aug 2021

c. Voice Message Report Example

THIS MESSAGE IS FOUO, BUT MARKED “CONFIDENTIAL - RESTRICTED DATA” FOR


TRAINING PURPOSES ONLY

MARITIME OPERATIONS CENTER THIS IS USS CARRIER OPREP THREE NAVY BLUE
FADED GIANT
OVER
USS CARRIER THIS IS MARITIME OPERATIONS CENTER SEND OPREP THREE NAVY
FLUE FADED GIANT
OVER
THIS IS USS CARRIER.
FLASH
CONFIDENTIAL RESTRICTED DATA
OPREP THREE NAVY BLUE FADED GIANT
LINE ONE ONE THREE ONE ZERO TWO ONE ZULU
LINE TWO NORFOLK NAVAL SHIPYARD
LINE SEVEN MAJOR LOSS OF COOLANT CASUALTY OCCURRED WHILE
OPERATING AT TWO THREE PERCENT POWER BREAK
REACTOR PLANT IS SHUTDOWN BREAK
PRIMARY CONTAINMENT IS SET BREAK
SETTING SECONDARY CONTAINMENT IN PROGRESS BREAK
IMMEDIATE ACTIONS IN PROGRESS AND WITH ALL REACTOR PLANT SYSTEMS
FUNCTIONING PROPERLY BREAK
SURVEYS TO DETERMINE IF FISSION PRODUCTS WERE RELEASED IN PROGRESS
BREAK
NO AFFECTED WEAPONS
LINE ONE SIX ONE THREE ONE ZERO THREE ZERO ZULU
OVER.

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. OPREP-3 NAVY BLUE FADED GIANT MTF data sets are the same as for the OPREP-
3FG message report contained in reference (b). The primary flagword NAVY BLUE, must be
manually added to the message. Initial message reports for this section do not require the use of
SEQ numbers 11 through 15, however these lines may be included if information is available.
SEQ numbers 11 through 15 should be included in FOLUP message reports as the information
becomes available.

CUI
4-19
CUI
OPNAVINST 3100.6K
10 Aug 2021

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3FG)
4 O REF * Reference
5 M FLAGWORD FLAGWORD Information (NAVY BLUE or FADED
GIANT)
6 M TIMELOC Event Time and Position
7 C HEADING Casualties and Damages
8 O CASUALTY Friendly Personnel Casualty Count
9 O GENTEXT DAMAGES
10 O GENTEXT For incident cause and details report: reactor
power and operating history at time of accident, status of
primary and secondary containment, status of immediate
actions, functioning of reactor plant systems, fission
product release inside the ship and to the environment,
significant Navy authorities notified. Identify affected
ship, if other than originator. Address presence of weapons
potentially affected onboard.
11 C HEADING METEOROLOGY. Effective wind speed and direction
from true north
12 O 5RAD Radioactivity Dose Rate Information
13 O 5STRKWRN Radiation Information
14 O GENTEXT System Condition and Safety Measures
15 O GENTEXT News Release
16 O DECL Message Derivative or Original Source for Classification,
Reason for Classification and DECL and Downgrading Data
*Repeatable set

c. Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC
USSTRATCOM OFFUTT AFB NE (for SSBNs)
COMUSFLTFORCOM NORFOLK VA
Component Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander

CUI
4-20
CUI
OPNAVINST 3100.6K
10 Aug 2021

Type Commander
Other Operational and Administrative Commanders
Commander of Local Activity or Facility:
Shipyard, base, station, post or supervisor of shipbuilding, as appropriate, who is
designated to provide assistance.
Area Commander, Deputy Primary Commander, Primary Commander, if initial report
submitted by nuclear-powered ship.
COMNAVSEASYSCOM WASHINGTON DC

(2) INFO addresses:

JOINT STAFF WASHINGTON DC


COMNAVSAFECEN NORFOLK VA
BUMED FALLS CHURCH VA
COMNAVSEASYSCOM WASHINGTON DC
Chain of Command
CHINFO WASHINGTON DC
CNIC WASHINGTON DC
ONI WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (incident potentially reportable as a
MISHAP or an actual MISHAP)
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)
DIRSSP WASHINGTON DC (for SSBNs)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
DIRNAVCRIMINVSERV QUANTICO VA
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC (ship or ship's system incidents)
BUMED FALLS CHURCH VA
CNIC WASHINGTON DC
SOPA
Regional Commander
Installation Commander

(4) Message body:

CUI
4-21
CUI
OPNAVINST 3100.6K
10 Aug 2021

THIS MESSAGE EXAMPLE IS UNCLASSIFIED BUT MARKED “SECRET” FOR


TRAINING PURPOSES ONLY.

SECRET
SECINFO/S/NOFORN//
EXER/LABRADOR RISING//
MSGID/OPREP-3FG, USMTF, YYYY/USS SHIP/001//
FLAGWORD/NAVY BLUE/FADED GIANT//
TIMELOC/131021ZMAY2005/NORFOLK NAVAL SHIPYARD/INIT//
HEADING/CASUALTIES AND DAMAGES//
CASUALTY/KILLED: 0/WOUNDED: 0/MISSING: 0//
GENTEXT/DAMAGES/SEVERE DAMAGE TO NUMBER ONE REACTOR
PLANT//
GENTEXT/INCIDENT CAUSE AND DETAILS/MAJOR LOSS OF
COOLANT CASUALTY OCCURRED WHILE OPERATING AT 23%
POWER. REACTOR HAD BEEN OPERATING FOR LAST 12 DAYS
AT POWER LEVELS FROM 20-45%.//
GENTEXT/SYSTEM CONDITIONS AND SAFETY MEASURES
/REACTOR IS VERIFIED SHUTDOWN. AFFECTED LOOP IS ISOLATED.
ALL IMMEDIATE ACTIONS COMPLETED AND REACTOR PLANT
SYSTEMS FUNCTIONING PROPERLY. RADIATION LEVELS AT
SURVEY POINTS A1 AND A2 ARE [X] AND [Y] MR/HR,
INDICATING FISSION PRODUCT RELEASE WITHIN REACTOR
COMPARTMENT. PRIMARY CONTAINMENT IS SET. SETTING
SECONDARY CONTAINMENT IN PROGRESS. SURVEYS IN
PROGRESS TO DETERMINE EXTENT OF FISSION PRODUCT
RELEASE TO THE REMAINDER OF THE SHIP AND THE
ENVIRONMENT. NO WEAPONS POTENTIALLY AFFECTED ONBOARD.//
GENTEXT/NEWS RELEASE/MEDIA INTEREST ANTICIPATED.//
RMKS/ PRIMARY COMMANDER AND COMNAVAIRLANT HAVE BEEN
NOTIFIED BY VOICE REPORT. VOICE REPORT INITIATED
131030Z. ADDITIONAL REPORTS TO FOLLOW.//
DECL/DERI: CG-W-5/-/INST: DO NOT DECLASSIFY//

d. RD or FRD. If this message contains RD or FRD, it must be identified in the


classification line as required in reference (f). The DECL set must include the source of the
classification and instructions not to declassify.

CUI
4-22
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section IV – OPREP-3 NAVY BLUE DULL SWORD

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE DULL SWORD report is used
by any unit to provide CNO and other naval commanders with immediate notification of any
unexpected event involving a nuclear weapon or component (including war reserve, test, training
weapons or associated test and handling equipment).

a. This report is for any unexpected occurrence involving nuclear weapons or nuclear
components that is not a nuclear incident but are characterized by:

(1) Errors are committed in the assembly, testing, loading or transporting of equipment
which could lead to reduced yield, increased dud probability or to unintentional operation of all
or part of a weapon's arming or firing sequence.

(2) The malfunctioning of equipment and material which could lead to a reduced yield,
increased dud probability or to unintentional operation of all or part of a weapons arming or
firing sequence.

(3) Any natural phenomenon over which man has no control that results in damage to a
weapon or component.

(4) Any unfavorable environment or condition, however produced, which subjects a


nuclear weapon to vibration, shock, stress, extreme temperature or other environment sufficient
to cause questioning of the reliability or safety of the weapon. This includes exposure or
suspected exposure of the weapon or major components to electrical or electromagnetic energy
that could energize or damage weapon components.

b. This message format is the same as the OPREP-3 PINNACLE BROKEN ARROW.
Thus, the flagword PINNACLE may be added at any level of command to expedite forwarding
of this message to NMCC J3.

2. Report Content.

a. The OPREP-3 NAVY BLUE DULL SWORD is a USMTF based report that is being
incorporated into reference (b).

b. The weapon identification and configuration are classified. If this report is submitted
over unclassified communications, a line number in reference (v) must be used.

3. Voice Message Report.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

CUI
4-23
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. Voice message formats are the same as for the OPREP-3 PINNACLE BROKEN
ARROW.

c. Voice Message Report Example

STARDUST THIS IS MOONGLOW OPREP THREE NAVY BLUE DULL SWORD OVER
MOONGLOW THIS IS STARDUST SEND OPREP THREE NAVY BLUE DULL SWORD
OVER
THIS IS MOONGLOW
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE DULL SWORD
LINE ONE TWO NINER ONE NINER FIVE NINER ZULU
LINE TWO THREE ZERO ONE ZERO ZERO ZERO NOVEMBER ZERO FOUR FIVE ZERO
FIVE ZERO FIVE WHISKEY
LINE THREE ONE
LINE FOUR ALPHA SIERRA ROMEO OSCAR CHARLIE
LINE ONE ONE SEALED CONTAINER ACCIDENTALLY OPENED DURING ROUTINE
MAINTENANCE
LINE ONE TWO WEAPON OPERATIONAL PERIOD NO RADIATION LEAK
LINE ONE THREE NO MEDIA INVOLVEMENT OR PUBLIC REACTION ANTICIPATED
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. MTF data sets are the same as for the OPREP-3 PINNACLE BROKEN ARROW. The
secondary flagword in the FLAGWORD set, DULL SWORD, must be manually selected in
common message processor.

c. Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC
USSTRATCOM OFFUTT AFB NE
COMUSFLTFORCOM NORFOLK VA
Component Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT

CUI
4-24
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMUSNAVSO
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
NAVSURFWARCENIHEODTECHDIV DET MCALESTER OK
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (for ordnance related
incidents)

(2) INFO addresses:

JOINT STAFF WASHINGTON DC


COMNAVSAFECEN NORFOLK VA
BUMED FALLS CHURCH VA
Chain of Command
CHINFO WASHINGTON DC
CNIC WASHINGTON DC
ONI WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (incident potentially reportable as a MISHAP
or an actual MISHAP)

COMNAVAIRSYSCOM PATUXENT RIVER MD


COMNAVSEASYSCOM WASHINGTON DC
NAVEODTECHDIV INDIAN HEAD MD
DTRA ABQ KIRTLAND AFB NM
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
BUMED FALLS CHURCH VA
COMSUBFOR NORFOLK VA (All TRIDENT and submarine-configured
TOMAHAWK missiles)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
DIRNAVCRIMINVSERV QUANTICO VA
Local NAVCRIMINVSERV (NCIS) office
NAVINSGEN WASHINGTON DC (fraud, waste or abuse)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC (ship or ship's system incidents)
NAVSURFWARCENIHEODTECHDIV INDIAN HEAD MD (ordnance incidents)

CUI
4-25
CUI
OPNAVINST 3100.6K
10 Aug 2021

BUMED FALLS CHURCH VA


CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
CNIC WASHINGTON DC
SOPA
Regional Commander
Installation Commander
Appropriate U.S. Coast Guard District
NAVCIRT NORFOLK VA (computer intrusion)

(4) Message body:

EXER/OLIVE DRAB 2009//


MSGID/OPREP-3DS, USMTF, YYYY//USS SHIP/001A/MAY// Secondary
FLAGWORD/NAVY BLUE/DULL SWORD// FLAGWORD field
TIMELOC/291959Z/301000N045050W/FOLUP// must be manually
EVTYP/QTY: 1/WPNAS:AGM86/-/ACTYP:F-18E// selected.
EVTYP/QTY: 1/WPNGEN: ASROC//
GENTEXT/INCIDENT CAUSE AND DETAILS/DURING ROUTINE
MAINTENANCE IN THE MAGAZINE, A SEALED CONTAINER IN THE WEAPON
WAS ACCIDENTALLY OPENED.//
GENTEXT/WEAPON CONDITION AND SAFETY MEASURES/WEAPON
CHECKED. STILL OPERATIONAL. NO RADIATION LEAK. NO SAFETY
MEASURES REQUIRED.//
RMKS/CORRECTIVE ACTION: MAINTENANCE FEEDBACK REPORT
SUBMITTED. PERSONNEL TO REVIEW MAINTENANCE PROCEDURES.//
GENTEXT/NEWS RELEASES/NO MEDIA INVOLVEMENT OR PUBLIC
REACTION ANTICIPATED.//

CUI
4-26
CUI
OPNAVINST 3100.6K
10 Aug 2021

Section V – OPREP-3 NAVY BLUE SENTINEL

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE SENTINEL report is used by
any unit to provide the CNO and other naval commanders with immediate notification of any
hostile incidents of military, political or media interest that are of high Navy interest but do not
meet the criteria for OPREP-3 PINNACLE FRONT BURNER. The reports are submitted to
provide “as-it-happens” information to the chain of command. Reportable hostile incidents can
include, but are not limited to:

a. Willful breech of a security perimeter.

b. Confirmed swimmer sightings near U.S. vessels.

c. Warning shots or use of non-lethal weapons in the execution of the continuum of force.

d. Bomb threats that are initially evaluated by the reporting officer as a valid threat.

e. Elicitation attempts, suspicious questioning, surveillance or other suspected collection


attempts.

f. Suspected or confirmed tests of security.

g. Unmanned Systems activity in proximity to Navy assets.

h. Any other suspected hostile activity that could facilitate base access and serve as a
precursor to future hostile incidents.

2. Report Content. The OPREP-3 NAVY BLUE SENTINEL report is a USMTF based report
that is being incorporated into reference (b). It is based on the OPREP-3 message. The message
example is edited accordingly.

a. In general, voice and record message reports should address:

(1) What happened?

(2) Who is or was involved?

(3) Where did it happen?

(4) When did it happen?

(5) Why did it happen?

CUI
4-27
CUI
OPNAVINST 3100.6K
10 Aug 2021

(6) What action is ongoing?

(7) What future action is contemplated?

(8) What is the impact on the command's mission capability?

(9) Is any assistance required?

(10) Is media attention anticipated?

(11) Command POC and 24-hour contact (CDO or similar) information.

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I
and should be made to the first MOC or ROC in the TACON for FP chain of command.

(1) Example: If an incident happens at Naval Base Norfolk then the report would be
made to the Commander, Navy Region Mid-Atlantic ROC, who would then report to the United
States Fleet Forces MOC, who would then report to the NOC.

(2) Example: If an incident happens at a non-Navy controlled port then the report would
be made from the afloat unit to the Numbered Fleet MOC who would then report it to respective
Fleet Commander MOC, who would then report to the NOC.

b. Include as much of the information in paragraph 2a in the initial voice report as possible,
but do not delay the initial report to gather additional information. The information must be
addressed in the initial and amplifying record messages.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description

Line One Incident Enter the incident identification, location and details.
Line Two Narrative Enter any additional information about the incident.

d. Voice Message Report Example

STARBURST THIS IS MOONGLOW OPREP THREE NAVY BLUE SENTINEL OVER

CUI
4-28
CUI
OPNAVINST 3100.6K
10 Aug 2021

MOONGLOW THIS IS STARBURST SEND OPREP THREE NAVY BLUE SENTINEL


OVER
THIS IS MOONGLOW
NORMAL
UNCLASSIFIED
OPREP THREE NAVY BLUE SENTINEL
LINE ONE BREACH OF SECURITY PERIMETER BREAK NAVSTA NORFOLK
LINE TWO SINGLE MALE SUSPECT APPREHENDED BY BASE SECURITY WHILE
ATTEMPTING TO CUT THROUGH CHAIN LINKED PERIMETER SECURITY FENCE
BREAK ADDITIONAL SUSPECTS MAY HAVE FLED THE SCENE BREAK INCIDENT
UNDER INVESTIGATION BY NOVEMBER CHARLIE INDIA SIERRA AND LOCAL
AUTHORITIES
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. OPREP-3 NAVY BLUE MTF data sets are the same as for the generic OPREP-3
message report contained in reference (b), with the addition of the FLAGWORD set after the
REF set.

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3)
4 O REF * Reference
5 M FLAGWORD FLAGWORD Information (NAVY BLUE
SENTINEL)
6 M TIMELOC Event Time and Position
7 M GENTEXT INCIDENT IDENTIFICATION AND DETAILS
8 O DECL Message Derivative or Original Source
for Classification, Reason for Classification and DECL and Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:


CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
Component Commander:

CUI
4-29
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMPACFLT PEARL HARBOR HI


COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
Fleet Commander
Type Commander
Regional Commander
Installation Commander
Other Operational and Administrative Commanders
Local NAVCRIMINVSERV (NCIS) office

(2) INFO addresses:

Tactical Control (TACON) for FP Chain of Command


CHINFO WASHINGTON DC
CNIC WASHINGTON DC
ONI WASHINGTON DC
HQ USNORTHCOM
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
Incident addresses
DIRNAVCRIMINVSERV QUANTICO VA
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


CMC WASHINGTON DC (USMC personnel or mission incidents)
SOPA
Appropriate U.S. Coast Guard District

(4) For personnel incident reports, use the addresses and format listed in appendix B.

(5) Message body:

MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//


FLAGWORD/NAVY BLUE SENTINEL/-//
TIMELOC/110429ZMAY2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: BREACH OF PERIMETER SECURITY
2. DATE OF INCIDENT: 11MAY2009
3. TIME OF INCIDENT: 0128L
4. LOCATION OF INCIDENT: NAVSTA NORFOLK, VA

CUI
4-30
CUI
OPNAVINST 3100.6K
10 Aug 2021

5. INCIDENT: MALE SUSPECT APPREHENDED BY BASE SECURITY WHILE


ATTEMPTING TO CUT THROUGH CHAIN LINKED PERIMETER SECURITY
FENCE. ADDITIONAL SUSPECTS MAY HAVE FLED THE SCENE. INCIDENT
UNDER INVESTIGATION BY NCIS AND LOCAL AUTHORITIES.

CUI
4-31
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHAPTER 5 – OPREP-3 NAVY UNIT SITREP REPORTS

Section I – OPREP-3 NAVY UNIT SITREP

1. Specific Reporting Instructions.

a. The OPREP-3 NAVY UNIT SITREP is used by any U.S. Navy CO, officer-in-charge or
other commander (as directed or appropriate) to provide the ISIC and appropriate Navy
operational commanders and higher authority with timely notification of any incident not
meeting OPREP-3 PINNACLE or OPREP-3 NAVY BLUE special incident reporting criteria.

b. The decision to submit an OPREP-3 NAVY UNIT SITREP vice an OPREP-3 NAVY
BLUE report for the list of personnel incident reporting criteria is driven by potential media
interest. For clarification of definitions for potentially reportable crimes refer to reference (h).
For general guidance see appendix B.

c. Major Incidents. Any incident such as fire, flooding, computer intrusion and loss or
compromise of classified information require an OPREP-3 NAVY BLUE if that incident is
considered to be "major." If it is not "major," then it is to be reported as an OPREP-3 NAVY
UNIT SITREP. For the purposes of this instruction, a major incident is defined as an incident
that results in loss or degradation in the ability of a command to perform its mission,
degradation, destruction or non-availability of a Task Critical Asset published by OPNAV N46,
or as determined by the CO. If in doubt, report as an OPREP-3 NAVY BLUE.

d. Hostile incidents that do not meet the criteria for an OPREP-3 PINNACLE FRONT
BURNER or OPREP-3 NAVY BLUE SENTINEL must be reported using an OPREP-3 NAVY
UNIT SITREP SENTINEL per appendix F.

e. The listed incidents warrant an OPREP-3 NAVY UNIT SITREP submitted to the ISIC:

(1) When considered appropriate by the reporting activity.

(2) When directed.

(3) To update incidents previously reported via OPREP-3 NAVY BLUE when the update
information does not meet OPREP-3 NAVY BLUE criteria.

(4) Operational incidents that do not attract media attention.

(a) Any firearm discharge that is unauthorized, accidental or negligent that does not
result in injury or death.

CUI
5-1
CUI
OPNAVINST 3100.6K
10 Aug 2021

(b) Floods or fires resulting in minor damage or does not cause significant personnel
injury or loss of combat capability. This includes all unintentional fires occurring on any naval
installation, ship, submarine or aircraft (to include small fires in which no personnel were injured
and the material property damage was limited). Fires are states, processes or instances of
combustion in which fuel or other material is ignited and combined with oxygen, giving off
smoke, sparks or flame. Smoke or sparks may not be present. However, if smoke or sparks
exist, a fire should be assumed to exist (this is specifically relevant to Class “C” fires when the
smoke or spark cease after power is secured). Evidence of previously unreported combustion or
explosion should also be reported. Reports solely based on acrid odor (no evidence of
combustion upon inspection) are not required.

(c) Any incident (except against forces previously declared hostile by higher
authority) in which live ordnance warning shots, excluding pyrotechnics, are fired without the
intent to hit or disable, in response to a violation or suspected attempt to violate a U.S. Navy
perimeter or maritime warning zone, including events in foreign ports. Regardless of intent, if
personnel are injured or killed in the engagement or the vessel is disabled, OPREP-3
PINNACLE notification is required. If the vessel is hit but not disabled, an OPREP-3 NAVY
BLUE notification is required. Fleet commanders will determine if events are of sufficient
significance to issue an OPREP-3 NAVY BLUE based on similar previous events in that AOR.

(d) Minor liberty incidents in which a Service member is arrested or held for non-
serious offenses by local or foreign authorities.

(e) Minor liberty incidents in a foreign port that may result in payment of a foreign
claim.

(5) Personnel Incidents. See also appendix B for amplifying guidance and action and or
information addresses. If media interest is anticipated in any of the listed personnel incidents, it
should be reported via an OPREP-3 NAVY BLUE. If media interest is not anticipated, an
OPREP-3 NAVY UNIT SITREP will be used.

(a) Domestic violence or abuse. Any report of domestic violence or domestic abuse
must include the date and location of the Service member’s most recent operational,
expeditionary or IA deployment. Additionally, if the Service member’s last deployment was an
expeditionary or IA deployment after 19 March 2004, include whether he or she completed a
Post Deployment Health Reassessment between 90 and 180 days after their return.

(b) Child abuse and or neglect.

(c) EO incidents – formal complaint or report. Allegation submitted in writing via


NAVPERS 5354/2, UCMJ article 92 for violation of EO or Sexual Harassment policy, UCMJ
Article 138, US Navy Regulation Article 1150, communication with Inspector General or
Elected Official, NAVPERS 1627/7 report or any other communication the Commander deems

CUI
5-2
CUI
OPNAVINST 3100.6K
10 Aug 2021

appropriate) of sexual harassment, unlawful discrimination based on race, color, religion, sex (to
include gender identity), national origin or sexual orientation or harassment based on race, color,
religion, sex (to include gender identity), national origin or sexual orientation. Commanders must
consult with a JAG in all alleged sexual harassment cases and must consult a CCS in all alleged
discrimination, harassment and sexual harassment cases. The final OPREP-3 report must include
the name, command name and contact information of the JA and CCS consulted.

(d) Suicide Related Behaviors. Any report of suicide related behaviors must include
date and location of most recent operational, expeditionary or individual augmentee deployment.
Behavior that has not been deemed suicide-related behavior by a competent authority does not
need to be reported.

(e) Hazing – report all substantiated and unsubstantiated incidents. Include these data
elements: relationship between complainant and alleged offender, general nature of the alleged
hazing incident (physical, psychological, verbal, technological, a combination, etc.), location of
the hazing incident (on-duty, off-duty, etc.), duty status (training, temporary duty, present for
duty, leave, etc.) of both the complainant and alleged offender at the time of the alleged hazing
incident.

(f) Bullying - report all substantiated and unsubstantiated incidents. Include these
data elements: relationship between complainant and alleged offender, general nature of the
alleged bully incident (physical, psychological, verbal, technological, a combination, etc.),
location of the bullying incident (on-duty, off-duty, etc.), duty status (training, temporary duty,
present for duty, leave, etc.) of both the complainant and alleged offender at the time of the
alleged bullying incident.

(g) DUI.

(h) Serious injury to Navy personnel.

(i) Any incident involving a firearm, regardless of whether or not the firearm was
discharged.

(j) Fraternization – formal complaint or report. Upon completion of an investigation,


provide final SITREP indicating if the incident was substantiated or unsubstantiated.

(6) Other incidents:

(a) FOLUP reports of labor strikes affecting Navy facilities or the construction of a
ship.

(b) Minor fraud, waste or abuse.

CUI
5-3
CUI
OPNAVINST 3100.6K
10 Aug 2021

2. Report Content. The OPREP-3 NAVY UNIT SITREP is a USMTF-based report that is
being incorporated into reference (b). It is based on the OPREP-3 message. The message
example is edited accordingly.

a. In general, voice and record message reports should address:

(1) What happened?

(2) Who is or was involved?

(3) Where did it happen?

(4) When did it happen?

(5) Why did it happen?

(6) What action is ongoing?

(7) What future action is contemplated?

(8) What is the impact on the command's mission capability?

(9) What assistance is required?

(10) What media attention is anticipated?

(11) Who is the command POC information?

b. Additional specific information is required in the GENTEXT-INCIDENT


IDENTIFICATION AND DETAILS section of the record messages when reporting incidents of:

(1) Personnel incident reports. Appendix B refers.

(2) Negligent discharge of a firearm. For a negligent, inadvertent or justified discharge of


a government-owned firearm, which does not result in injury or death to personnel, must include
the type of investigation being conducted.

(3) Motorcycle mishap related incident. An OPREP-3 report is required for all class “A”
and class “B” motorcycle mishap related incidents. OPREP-3 reporting for class “C” mishap
related incidents is at the discretion of the CO, unit commander or officer-in-charge, as
applicable.

c. Serious injury of U.S. military personnel:

CUI
5-4
CUI
OPNAVINST 3100.6K
10 Aug 2021

(1) Avoid reporting sensitive personal information. Privacy of the individual is to be


respected at all times.

(2) Generic identification such as “PO1” or “20 YR OLD FEMALE E-3” will suffice.

(3) If detailed personal identity information is required, it should be provided separately


in other than general messages, such as amplifying voice reports or limited distribution messages
such as "Personal For" or secure e-mail.

(4) Names must be withheld pending notification of next of kin, unless positive
identification is deemed necessary. In such cases, the names can be listed provided the statement
includes: "FOR OFFICIAL USE ONLY. NEXT OF KIN HAVE NOT BEEN NOTIFIED."

d. In some cases, an OPREP-3 NAVY UNIT SITREP will be used to amplify an OPREP-3
NAVY BLUE report.

3. Voice Message Reports.

a. Voice reports within 15 minutes of the event are required for FP related OPREP-3 NAVY
UNIT SITREP. OPREP-3 NAVY UNIT SITREP reports for personnel incidents require a voice
message report. See appendix B for a message example.

b. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of
the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description

Line One Incident Enter the incident identification, location and details.
Line Two Narrative Enter any additional information about the incident.

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. OPREP-3 NAVY UNIT SITREP MTF data sets are the same as for the generic OPREP-3
message report contained in reference (b), with the addition of the FLAGWORD set after the
REF set.

CUI
5-5
CUI
OPNAVINST 3100.6K
10 Aug 2021

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3)
4 O REF * Reference
5 M FLAGWORD FLAGWORD Information (NAVY UNIT SITREP)
6 M TIMELOC Event Time and Position
7 M GENTEXT INCIDENT IDENTIFICATION AND DETAILS
8 O DECL Message Derivative or Original Source for Classification,
Reason for Classification and DECL and Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

ISIC
Local NAVCRIMINVSERV (NCIS) office

(2) INFO addresses, as appropriate:

Chain of Command (up through ECHELON II Commander)


CNO WASHINGTON DC
CNIC WASHINGTON DC
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC
DIRNAVCRIMINVSERV QUANTICO VA
NAVPERSCOM (appropriate code per appendix B)
NAVY JAG WASHINGTON DC
NAVINSGEN WASHINGTON DC (fraud, wasteor abuse)
CHINFO WASHINGTON DC
COMNAVSAFECEN NORFOLK VA (incident reportable as a MISHAP, is an actual
MISHAP, including motorcycle MISHAPs or involved a firearm)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)

BUMED FALLS CHURCH VA


CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
SOPA
HQ USNORTHCOM (ATFP incident)
Regional Commander
Installation Commander

CUI
5-6
CUI
OPNAVINST 3100.6K
10 Aug 2021

Appropriate US Coast Guard District


Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (aircraft incidents)
COMNAVSEASYSCOM WASHINGTON DC (ship or ship's system incidents)
NACYBERDEFOPSCOM NORFOLK VA (computer intrusion incidents)
COMNAVNETWARCOM VIRGINIA BEACH VA (loss of communications)

(3) For negligent discharge of a firearm incident report, use:

(a) ACTION addresses:


SIC

(b) INFO addresses: as applicable:

COMUSFLTFORCOM NORFOLK VA
COMNAVSAFECEN NORFOLK VA
Applicable Fleet Commander
Numbered Fleet Commander
Regional Commander
CNIC WASHINGTON DC
TYCOM
DIRSSP WASHINGTON DC (for all SSBNs, Fleet and Shore Installations that
support the Nuclear Deterrence Program)

(4) Message body:

MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//


FLAGWORD/NAVY UNIT SITREP/-//
TIMELOC/010429ZAPR2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
INCIDENT: NEGLIGENT DISCHARGE OF A GOV’T OWNED FIREARM
1. DATE/TIME/LOCATION OF INCIDENT:
01APR2010/0235L/SHIP’S QUARTERDECK, NORFOLK, VA
2. WEAPON TYPE/NO. ROUNDS: 9 MM/ ONE ROUND/ SIG SAUER SIG P226
3. DAMAGE: NONE, SHOT INTO AIR
4. LOCATION FIREARM NORMALLY STORED: SHIPS ARMORY
5. RATE/RANK/GRADE/NEC/DUTY POSITION OF PERSON
DISCHARGING WEAPON/PARENT COMMAND: ET2 / E-5 / 731A/
GUARD / OPNAV
6. RACE/GENDER: WHITE/MALE
7. DATE LAST QUAL’D/TYPE OF TRAINING/YRS EXP:
11NOV2019/ BASIC PISTOL/ 02
8. DATE LAST USE OF FORCE TRAINING COMPLETED: 15JUN2019

CUI
5-7
CUI
OPNAVINST 3100.6K
10 Aug 2021

9. DATE RETURNED FROM DEPLOYMENT: 26MAR2018


10. ALCOHOL/DRUG USE: 9 BEERS 6 HRS EARLIER/ NONE
11. TYPE INVESTIGATION: INTERNAL
12. NARRATIVE OF INCIDENT: DURING DUTY ROUNDS, MEMBER
UNHOLSTERED HIS WEAPON TO EXAMINE IT. SAFETY WAS OFF
AND GUN ACCIDENTALLY DISCHARGED INTO THE AIR.
13. POC: LT BROWN, COMM 555-555-5555, DSN 555-5555,
[email protected]//

d. For personnel incident reports, use the addresses and format listed in appendix B.

CUI
5-8
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX A – REFERENCES

(a) CJCSM 3150.03D, Joint Reporting Structure Event and Incident Reports (NOTAL)

(b) MIL-STD 6040 B CH-1, Department of Defense Interface Standard, U.S. Message Text
Formatting Program, January 31, 2011

(c) Intelligence Community Directive 190: (ICD 190) Critical Information (CRITIC), of
2/15/2015

(d) OPNAVINST 5102.1 or MCO P5102.1 Navy and Marine Corps Mishap and Safety
Investigation Reporting and Record Keeping Manual

(e) Handbook of Standard Operating Procedures for Reporting Critical Information (CRITIC
Handbook), NSA Supplement to DCID 7/4 of 31 Oct 00. SIPR URL: (NOTAL)
http://dia.smil.mil/intel/DIA/13/1308/855/DIA-13-1308-855.html/

(f) SECNAV M-5510.36B, Department of the Navy Information Security Program Manual

(g) CJCSM 6510.01 Cyber Incident Handling Program

(h) Manual for Courts-Martial (MCM), United States

(i) OPNAVINST 1752.1C, Sexual Assault Prevention and Response Program

(j) OPNAVINST 1752.2, Family Advocacy Program

(k) SECNAVINST 5350.16 Equal Opportunity (EO) Within the Department of the Navy

(l) OPNAVINST 5354.1, Navy Equal Opportunity Policy

(m) SECNAVINST 1610.2, DON Policy on Hazing

(n) SECNAVINST 1752.4, Sexual Assault Prevention and Response

(o) SECNAVINST 1752.3, Family Advocacy Program

(p) OPNAVINST 1720.4, Suicide Prevention Program

(q) OPNAVINST 3750.6, Naval Aviation Safety Program

(r) SECNAVINST 5430.107, Mission and Functions of the Naval Criminal Investigative Service

CUI
A-1 Appendix A
CUI
OPNAVINST 3100.6K
10 Aug 2021

(s) SECNAVINST 3300.1, Department of the Navy Law of War Program

(t) OPNAVINST 3300.52, Law of Armed Conflict (Law of War) Program to Ensure
Compliance by the U.S. Navy and Naval Reserve

(u) DoD Directive 2311.01, DoD Law of War Program

(v) Special Weapons Ordnance Publication (SWOP) 20-11, General Guidance and Hazard
Information for Nuclear Weapons, Components and Nonnuclear Weapons Designations

(w) CJCSI 3261.01 Series, Recapture and Recovery of Nuclear Weapons

(x) SECNAVINST S5460.3H dated 3 Jan 2019, Management and Administration of Special
Access Programs and Compartmented Information

(y) United States Navy Regulations

(z) OPNAVINST 5530.13, Department of the Navy Physical Security Instruction for
Conventional Arms, Ammunition and Explosives

(aa) OPNAVINST 5090.1, Environmental and Natural Resources Program Manual

(ab) OPNAVINST 5711.96, United States/Russian Federation Incidents at Sea and Dangerous
Military Activities Agreements

(ac) BUMEDINST 6220.12, Medical Surveillance and Notifiable Event Reporting

(ad) OPNAVINST N3040.5, Procedures and Reporting Requirements for Nuclear Reactor and
Radiological Accidents (NOTAL)

(ae) NAVSEA S9213-33-MMA-000/(V), Radiological Controls for Ships (NOTAL)

(af) OPNAVINST 5350.4D Navy Alcohol and Drug Abuse Prevention And Control

(ag) Deputy Secretary of Defense Policy Memorandum, Hazing and Bullying Prevention and
Response in the Armed Forces

(ah) OPNAVINST 5370.2, Navy Fraternization Policy

(ai) OPNAVINST 5300.13, Navy Sexual Harassment Prevention and Response Program Manual

CUI
A-2 Appendix A
CUI
OPNAVINST 3100.6K
10 Aug 2021

(aj) DODM 5100.76, Physical Security of sensitive Conventional Arms, Ammunition and
Explosives

(ak) OPNAVINST 6100.2, Health Promotion Program

(al) OPNAVINST 2201.2, Navy and Marine Corps Computer Network Incident Response

CUI
A-3 Appendix A
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX B - PERSONNEL INCIDENT REPORTS

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE and OPREP-3 NAVY UNIT
SITREP must be used to report any personnel incident that could attract high level Navy interest.
The decision to submit an OPREP-3 NAVY UNIT SITREP vice an OPREP-3 NAVY BLUE
report is driven by potential media interest. Reportable personnel incidents normally fall within
one of these categories:

a. OPREP-3 NAVY BLUE. Significant incidents to include any government civilian or


service member death, murder, suicide, sexual assault, armed robbery, aggravated assault, assault
with a deadly weapon, kidnapping, carjacking, child sexual abuse, supremacist activity, extremist
group activity and burglary of an occupied dwelling. Incidents involving death or serious injury
to personnel embarked on Navy or MSC ships and aircraft; or while on government property
both on and off duty require an OPREP-3 NAVY BLUE.

b. OPREP-3 NAVY UNIT SITREP. Lesser incidents to include domestic violence,


domestic abuse, child abuse and or neglect, discrimination, harassment, sexual harassment,
hazing, bullying, fraternization, DUI, motorcycle mishaps, suicide-related behavior and
workplace violence.

(1) Automated Reporting. The development of an online SITREP database has


commenced that is planned to replace personnel incident SITREP reporting. The completion of
the database will be announced by NAVADMIN with further details.

c. Sexual assault incidents (with exception of child sexual abuse) require these additional
information elements:

(1) Incident description: Contact or Penetration or UKN (if UKN at time of initial report,
an update report must be submitted once known);

(2) NCIS case number assigned (if UKNat time of initial report, an update report must be
made with case number once known – typically the NCIS case number is assigned immediately –
usually no late than 96 hours);

(3) Continue reporting by exception through case disposition. A list of non-exhaustive


examples of reasons an update is required are: expedited transfer of the victim, removal of the
alleged offender from the command, clarification of alcohol involvement, civilian or military
protective order issued, normal transfer of either victim or alleged offender, learning that the
incident is linked to other allegations of sexual assault, closure of investigation, receipt of legal
recommendation or upon the final case disposition.

(4) It is natural to hand over reporting responsibility from command to command as the
preponderance of information and responsibility may shift. For example, most initial reporting

CUI
B-1 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

requirements are associated with immediate victim care. After the first 30 days, primary
reporting requirements become associated with the alleged offender’s command. Shifting of
reporting is reasonable and expected, but requires close command to command coordination and
in compliance with the applicable instructions governing the subject matter of the report, i.e. the
sexual assault reporting requirements under reference (i).

d. Motorcycle mishap-related incidents and other mishaps, require a MISHAP report in


addition to an OPREP-3 report. Requirements for mishap investigations and reporting are
contained in reference (d). Ensure the OPREP-3 report includes whether the rider had attended
the appropriate motor cycle safety course.

e. Reports of suicides, suicide-related behavior, domestic violence and any incident


involving a firearm, whether the firearm was discharged or not discharged, must include the date
and location of the Service member’s last deployment and whether they are enrolled in the
Personnel Reliability Program. Annotate whether that deployment was operational,
expeditionary or an IA deployment.

f. Negligent discharge of a firearm must include the type of follow-on investigation to be


conducted.

g. EO, Unlawful Discrimination, Sexual Harassment, Hazing reporting follow-up


requirements. A follow up message reporting the investigation results and final disposition is
required within 20 days of the initial report and every 14 days thereafter, until the complaint is
resolved (indicating whether allegations were substantiated or unsubstantiated).

2. Report Content.

a. The OPREP-3 NAVY BLUE and OPREP-3 NAVY UNIT SITREP are USMTF based
reports that are being incorporated into reference (b). They are based on the OPREP-3 message.
The message examples are edited accordingly.

b. For all personnel incidents, report the specific information in the GENTEXT-INCIDENT
IDENTIFICATION AND DETAILS section of the report (these reporting elements are
automated in pull down menus in the SITREP data tool):

(1) Incident (incidents listed in subparagraphs 1a through 1e).

(2) Date of incident.

(3) Time of incident. Local time; specify the time zone.

(4) Location of incident (e.g. underway; onboard in port; in port overseas; residence;
barracks; Public Private Venture housing; on base; Temporary Duty; etc.)

CUI
B-2 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

(5) Suspect or alleged offender information: military (identify by pay grade: E-4, PO1,
O-1), civil service (identify by pay grade: GS-5), civilian, foreign national, UNK; if applicable,
include relationship to victim (spouse, child, etc.).

(6) Command and UIC.

(7) Sex.

(8) Age.

(9) Race (American Indian or Alaskan Native; Asian; Black or African American; Native
Hawaiian or Other Pacific Islander; Hispanic; White; multiple, UKN, decline to respond.).

(10) Weapon (firearm, knife, bottle, etc.). For firearm, list specific model and
manufacturer of the firearm.

(11) Firearm specifications. For a negligent, inadvertent or justified discharge of a


government-owned firearm, which does not result in injury or death to personnel, the report must
include the type of investigation being conducted.

(12) Alcohol and or drug (blood alcohol content, type and amount, if known).

(13) Victim or complainant information. Military (identify by pay grade: E-4, PO1,
O-1), civil service (identify by pay grade: GS-11), civilian, foreign national, UNK; if applicable,
include relationship to victim (spouse, child, etc.), Command and UIC.

(14) Victim or complainant information: Sex.

(15) Victim or complainant information: Age.

(16) Victim or complainant information:

(a) Race (American Indian or Alaskan Native; Asian; Black or African American;
Native Hawaiian or Other Pacific Islander; Hispanic; White; etc.).

(b) Relationship of offender to complainants (military coworker, chain of command,


military subordinate, military higher rank and grade not in chain of command, other military
person, person in local community, civilian, contractor, anonymous).

(17) NCIS notified and involvement. Identify the NCIS element notified, i.e.,
“NORFOLK FIELD DUTY OFFICE,” “NCISRA DUBAI,” or “COMMAND SPECIAL
AGENT AFLOAT,” if applicable. Additionally, articulate the general action the local NCIS
element will take, i.e., “[NCIS ELEMENT] INVESTIGATING MATTER” or “[NCIS

CUI
B-3 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

ELEMENT] DEFERS TO COMMAND INVESTIGATORS.” Include NCIS case number. If not


immediately available in time to support the initial personnel incident report, provide in a report
update as soon as feasible.

(18) Installation family advocacy representative notified (yes, no, not applicable).

(19) Summary or brief description of incident. For all OPREP-3 reports of suicides,
suicide-related behavior, domestic violence and any incident involving a firearm, whether the
firearm was discharged or not discharged, include the date and location of the Service member’s
most recent operational, expeditionary or IA deployment.

(20) Media interest (anticipated or not anticipated; if local or national media interest
observed, submit NAVY BLUE).

(21) POC (name, phone number and e-mail).

c. For initial sexual assault incident reporting, use subparagraph 2b, with specific attention
to subparagraphs (1) through (18).

(1) The GENTEXT-INCIDENT IDENTIFICATION AND DETAILS section of follow


up and final OPREP-3 NAVY BLUE or OPREP-3 NAVY UNIT SITREP must include
additional information:

(a) The name, command and contact information of the JAG consulted. (required)

(b) The disposition resolution category as provided by the NAVPERS 1752/1.

(c) Status of MPOs (e.g., duration, issuance, termination, violation, etc.).

(d) Status of transfer or reassignment (permanent and or temporary) of victim and or


alleged offender.

(e) Status of victim's collateral misconduct investigation and or disposition.

(f) Information pertinent to ongoing incident response.

(2) Due to the nature of sexual assault crimes, care should be given to limit the narrative
information to specific requirements and not include details that do not add to the report and
could result in re-victimization. A balance needs to be struck between information sharing and
potential re-victimization. If the CO deems that the SITREP could further victimize the victim
or identify the victim or alleged offender, consider having the ISIC release the SITREP on behalf
of the command.

CUI
B-4 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

d. Avoid reporting sensitive personal information or identifying demographic information


that could lead to the identity of the individual (typically at smaller commands). Privacy of the
individual is to be respected at all times. If detailed personal identity information is required, it
should be provided separately in other than general messages, such as amplifying voice reports
or limited distribution messages, such as "Personal For" or secure e-mail.

e. For DUI, DWI and ALCOHOL INCIDENTS SITREPs include BAC level in reports, if
available. FOLUP reports should also provide adjudication or civilian court results for DUI or
DWI incidents. Note: The specific BAC criteria for a DUI or DWI is determined by the local
jurisdiction and should be reported as a DUI even if the BAC is below typical CONUS criteria.
Outlined in reference (af) OPNAV 5350/7, a DAR is required for reporting all alcohol incidents
to OPNAV/N170A ADMITS.

f. SUBSTANCE ABUSE OPREP-3 REPORTING REQUIREMENTS. Although SITREPs


are not required for positive urinalysis results from the Navy's standard urinalysis program, due
to the new threat posed by less traditional substances, CO are encouraged to report the wrongful
use, possession, manufacture or distribution of controlled substances or non-traditional
substances such as natural substances (e.g., salvia divinorum, psychoactive mushrooms),
chemicals abused by inhaling or huffing (e.g., Dust-Off, glue, paint thinner, gasoline or
prescribed or over-the-counter drugs or pharmaceutical compounds) with the intent to induce
intoxication, excitement or stupefaction of the central nervous system. These reports alert
leadership and stakeholders to new trends and problems associated with drug usage. Per
reference (af), OPNAV 5350/7 DAR is required for reporting drug incidents to OPNAV N170A
ADMITS.

3. Voice Reports for OPREP-3 NAVY BLUE and OPREP-3 NAVY UNIT SITREPs

a. OPREP-3 NAVY BLUE incidents require voice report to the appropriate MOC within
the timeframe specified.

b. OPREP-3 NAVY UNIT SITREP incidents require voice report to the command's ISIC, if
required.

d. Voice message formats are the same for the OPREP-3 NAVY BLUE or the OPREP-3
NAVY UNIT SITREP. See examples:

(1) Non-Sexual Assault OPREP-3 NAVY BLUE Voice Message Report Example:

HOMEPLATE THIS IS SHIP OPREP THREE NAVY BLUE


OVER
SHIP THIS IS HOMEPLATE SEND OPREP THREE NAVY BLUE
OVER

CUI
B-5 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE MURDER SUICIDE BREAK NAVAL BASE SAN DIEGO
LINE TWO MALE MILITARY MEMBER KILLED SPOUSE THEN KILLED HIMSELF
BREAK SAN DIEGO POLICE ON SITE BREAK NOVEMBER CHARLIE INDIA SIERRA
NOTIFIED BREAK LOCAL MEDIA ON SITE.
OVER

(2) Sexual Assault OPREP-3 NAVY UNIT SITREP Voice Message Report Example:

HOMEPLATE THIS IS SHIP OPREP THREE NAVY BLUE


OVER
SHIP THIS IS HOMEPLATE SEND OPREP THREE NAVY BLUE
OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE SEXUAL ASSAULT BREAK NAVAL BASE SAN DIEGO
LINE TWO FEMALE ENLISTED SERVICE MEMBER SEXUALLY ASSAULTED IN HER
CAR AT ZERO NINER ZERO TWO THREE ZERO MARCH TWO ZERO ZERO FIVE
BREAK SAN DIEGO POLICE ON SCENE BREAK LOCAL MEDIA ON SITE BREAK
NOVEMBER CHARLIE INDIA SIERRA NOTIFIED
OVER

4. Record Message Reports for OPREP-3 NAVY BLUE and OPREP-3 NAVY UNIT SITREPs

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. MTF datasets are the same as for the OPREP-3 NAVY BLUE or the OPREP-3 NAVY
UNIT SITREP. Addresses for OPREP-3 NAVY BLUE and NAVY UNIT SITREPs are
provided in subparagraphs 4c and 4d.

c. OPREP-3 NAVY BLUE Record Message Example:

(1) ACTION addresses:

CNO WASHINGTON DC//


COMUSFLTFORCOM NORFOLK VA//

CUI
B-6 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

Component Commander:
COMPACFLT PEARL HARBOR HI//
COMUSNAVEUR COMUSNAVAF NAPLES IT//
COMUSNAVCENT//
COMUSNAVSO//
Fleet Commander
Type Commander
GCMA
Other Operational and Administrative Commanders
Local NAVCRIMINVSERV (NCIS) office

(2) NFO addresses for all personnel incidents:

Chain of Command
CHINFO WASHINGTON DC//
DIRSSP WASHINGTON DC// (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


DIRNAVCRIMINVSERV QUANTICO VA
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)

(4) Additional addresses for domestic violence:

COMNAVPERSCOM MILLINGTON TN//


CNIC WASHINGTON DC//
Regional Commander
Installation Commander

(5) Additional addresses for child abuse, child neglect or child sexual abuse:

COMNAVPERSCOM MILLINGTON TN//


CNIC WASHINGTON DC//
CNIC MILLINGTON TN//
Regional Commander
Installation Commander
(6) Additional addresses for sexual assault:

NAVY JAG WASHINGTON DC//


Victim’s and alleged Offender’s Chain of Command

CUI
B-7 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMNAVPERSCOM MILLINGTON TN//


CNIC WASHINGTON DC//
Regional Commander
Installation Commander

(7) Additional address for suicide:

COMNAVPERSCOM MILLINGTON TN//

(8) Additional addresses for EO incidents to include discrimination, harassment, sexual


harassment, hazing and bullying:

CNO WASHINGTON DC//


CHNAVPERS WASHINGTON DC//
COMNAVPERSCOM MILLINGTON TN//
NAVY JAG WASHINGTON DC//
NAVINSGEN WASHINGTON DC//

(9) Additional addresses for firearms incidents:

COMNAVSAFECEN NORFOLK VA//

(10) Additional INFO addresses for supremacist activities:

CHNAVPERS WASHINGTON DC//


COMNAVPERSCOM MILLINGTON TN//
NAVY JAG WASHINGTON DC//
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC//
DIRNAVCRIMINVSERV QUANTICO VA//
NAVINSGEN WASHINGTON DC//
Local NAVCRIMINVSERV (NCIS) Office

(11) Additional INFO addresses for motorcycle mishap related incidents:

COMNAVSAFECEN NORFOLK VA//

(12) Message body:

OPREP-3 NAVY BLUE Example:


MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//
REF/A/DESC: INITIAL VOICE REPORT TO MOC/USS
NEVERSAIL/110020ZMAR2005//

CUI
B-8 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

FLAGWORD/NAVY BLUE/-//
TIMELOC/102330ZMAR2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: MURDER-SUICIDE
2. DATE OF INCIDENT: 10MAR2010
3. TIME OF INCIDENT: 2330L (TANGO TIME ZONE)
4. LOCATION OF INCIDENT: BASE HOUSING, SAN DIEGO, CA
5. SUSPECT OR ALLEGED OFFENDER: E-3
6. GENDER: MALE
7. AGE: 20 YR OLD
8. RACE: DECLINE TO RESPOND
9. WEAPON: HAND GUN
10. FIREARM SPECS: SMITH AND WESSON P365
11. ALCOHOL/DRUG: NONE
12. VICTIM OR COMPLAINANT: CIVILIAN SPOUSE
13. GENDER: FEMALE
14. AGE: 19 YR OLD
15. RACE: DECLINE TO RESPOND
16. NCIS NOTIFIED/INVOLVEMENT: YES, NOTIFIED
17. FAMILY ADVOCACY REP NOTIFIED: YES
18. SUMMARY/BRIEF DESCRIPTION OF INCIDENT: VICTIM HAD
RESTRAINING ORDER AGAINST SUSPECT. SUSPECT ENTERED
VICTIM’S HOUSE BY FORCE, KIDNAPPED VICTIM’S CHILD AND
HELD CHILD HOSTAGE IN BASE HOUSING PARKING LOT. WHEN
VICTIM TRIED TO RECOVER CHILD, SUSPECT SHOT VICTIM
DEAD IN FRONT OF WITNESSES, THEN KILLED HIMSELF.
MEMBER RETURNED FROM IA DEPLOYMENT TO IRAQ ON 01
JANUARY 2015.
19. MEDIA INTEREST: ANTICIPATED
20. POC: LT MORTON, COMM 555-555-5555, DSN 555-5555,
[email protected]//

d. OPREP-3 NAVY UNIT SITREP Record Message Example

(1) ACTION addresses:

ISIC
CNO WASHINGTON DC//
CHINFO WASHINGTON DC//
GCMA

(2) INFO addresses for all personnel incidents:

CUI
B-9 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

Chain of Command (up through ECHELON II Commander)


CHINFO WASHINGTON DC//
CNIC WASHINGTON DC//
DIRSSP WASHINGTON DC// (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


DIRNAVCRIMINVSERV QUANTICO VA
Local NAVCRIMINVSERV (NCIS) office
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)

(4) Additional addresses for domestic violence:

COMNAVPERSCOM MILLINGTON TN//


CNIC WASHINGTON DC//

(5) Additional addresses for child abuse, child neglect or child sexual abuse:

COMNAVPERSCOM MILLINGTON TN//


CNIC WASHINGTON DC//
CNIC MILLINGTON TN//N913B//
Regional Commander
Installation Commander

(6) Additional addresses for sexual assault:


CNO WASHINGTON DC//
NAVY JAG WASHINGTON DC//
Victim’s/Accused’s Chain of Command
COMNAVPERSCOM MILLINGTON TN//
CNIC WASHINGTON DC//
Regional Commander
Installation Commander

(7) Additional address for suicide:

COMNAVPERSCOM MILLINGTON TN//


(8) Additional addresses for EO incidents to include unlawful discrimination,
harassment, sexual harassment, hazing and bullying:

CNO WASHINGTON DC//

CUI
B-10 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHNAVPERS WASHINGTON DC//


COMNAVPERSCOM MILLINGTON TN//
NVY JAG WASHINGTON DC//
NAVINSGEN WASHINGTON DC//

(9) Additional addresses for firearms incidents:

COMNAVSAFECEN NORFOLK VA//

(10) Additional INFO addresses for supremacist activities:

CHNAVPERS WASHINGTON DC//


COMNAVPERSCOM MILLINGTON TN//
NAVY JAG WASHINGTON DC//
NAVY INSIDER THREAT HUB ELEMENT WASHINGTON DC//
DIRNAVCRIMINVSERV QUANTICO VA//
NAVINSGEN WASHINGTON DC//
Local NAVCRIMINVSERV (NCIS) Office

(11) Additional INFO addresses for motorcycle mishap related incidents:

COMNAVSAFECEN NORFOLK VA//

(12) Message body:

OPREP-3 NAVY UNIT SITREP Motorcycle Mishap Example:


MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//
REF/A/DESC: INITIAL VOICE REPORT TO ISIC/USS
NEVERSAIL/160529ZJUN2020//
FLAGWORD/NAVY UNIT SITREP/-//
TIMELOC/160430ZJUN2005/4050N13235E/FINAL//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: NON-HOSTILE DEATH (MOTORCYCLE ACCIDENT)
2. DATE OF INCIDENT: 16JUN2020
3. TIME OF INCIDENT: 0430L
4. LOCATION OF INCIDENT: INTERSECTION OF
HAMPTON BOULEVARD AND INTERSTATE 564, NORFOLK, VA
5. SUSPECT OR ALLEGED OFFENDER: NONE
6. GENDER: N/A
7. AGE: N/A
8. RACE: N/A
9. WEAPON: N/A
10. FIREARM SPECS: N/A

CUI
B-11 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

11. ALCOHOL/DRUG: BEER, 6-PACK


12. VICTIM OR COMPLAINANT: E-4
13. GENDER: MALE
14. AGE: 24 YEARS OLD
15. RACE: WHITE
16. NCIS NOTIFIED: YES
17. INSTALLATION FAMILY ADVOCACY REP NOTIFIED: N/A
18. SUMMARY/BRIEF DESCRIPTION OF INCIDENT: MOTORCYCLE
ACCIDENT RELATED FATALITY. SM AND MOTORCYCLE FOUND ALONG
THE SIDE OF THE ROAD AT THE INTERSECTION OF HAMPTON BLVD AND
INTERSTATE 564 AT APPROXIMATELY 0430L. MEDICAL ASSISTANCE WAS
RENDERED BY A PASSING MOTORIST UNTIL ARRIVAL OF EMERGENCY
MEDICAL STAFF. SERVICE MEMBER WAS PRONOUNCED DEAD ON
ARRIVAL AT PORTSMOUTH NAVAL HOSPITAL. MEMBER RETURNED FROM
IA DEPLOYMENT TO IRAQ ON 01 MAY 2005. TYPE/MODEL OF MOTORCYCLE
INVOLVED: SPORTBIKE/SUZUKI GSX-R1000. USE OF PPE: HEAD
PROTECTION: YES, EYE PROTECTION: YES, FOOT PROTECTION: YES,
PROTECTIVE CLOTHING: BOOTS, GLOVES AND HELMET: YES, JACKET:
NOVALID MOTORCYCLE LICENSE OR PERMIT: NO. MOTORCYCLE SAFETY
COURSES AND DATES ATTENDED: BASIC RIDER COURSE (BRC) – 04012020.
19. MISHAP REPORT TO FOLLOW.
20. MEDIA INTEREST: NOT ANTICIPATED.
21. POC: LT BROWN, COMM 555-555-5555, DSN 555-5555,
[email protected]//

OPREP-3 NAVY UNIT SITREP Example:


MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//
REF/A/DESC: INITIAL VOICE REPORT TO ISIC/USS
NEVERSAIL/160529ZJUN2009//
FLAGWORD/NAVY UNIT SITREP/-//
TIMELOC/160430ZJUN2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: ROBBERY (ATTEMPTED)
2. DATE OF INCIDENT: 16JUN2020
3. TIME OF INCIDENT: 0430L
4. LOCATION OF INCIDENT: OFF BASE, NORFOLK, VA
5. SUSPECT OR ALLEGED OFFENDER: USN, AD, E4
6. GENDER: MALE
7. AGE: 27 YR OLD
8. RACE: UNKNOWN
9. WEAPON: N/A
10. FIREARM SPECS: N/A
11. ALCOHOL/DRUG: BEER, TWO 6-PACKS

CUI
B-12 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

12. VICTIM OR COMPLAINANT: E-4


13. GENDER: FEMALE
14. AGE: 24 YR OLD
15. RACE: WHITE
16. NCIS NOTIFIED: YES
17. INSTALLATION FAMILY ADVOCACY REP NOTIFIED: N/A
18. SUMMARY/BRIEF DESCRIPTION OF INCIDENT: WHILE IN RESTAURANT
BATHROOM, VICTIM WAS GRABBED BY ALLEGED OFFENDER WHO TRIED
TO ROB HER. VICTIM STRUGGLED AND SCREAMED WHICH ALERTED
RESTAURANT STAFF WHO DETAINED ALLEGED OFFENDER UNTIL LOCAL
POLICE ARRIVED AND TOOK HIM INTO CUSTODY. VICTIM IS PRESSING
CHARGES. VICTIM IS RECEIVING CIVILIAN COUNSELING. MPO ISSUED FOR
72 HOURS. ALLEGED OFFENDER TEMPORARILY REASSIGNED TO TENANT
COMMAND. NO COLLATERAL MISCONDUCT BY VICTIM NOTED.
COMMAND CONSULTED BASE RLSO, POC: LCDR J. BROWN, JAG, TEL:
(757)555-5555.
19. MEDIA INTEREST: NOT ANTICIPATED.
20. POC: LT A. GREEN, COMM 555-555-5555, DSN 555-
5555, [email protected]//

5. Definitions and Guidance. These paragraphs outline general guidance to assist in a


command’s determination as to whether a reportable personnel incident has occurred and
whether that incident should be reported via OPREP-3 NAVY UNIT SITREP or OPREP-3
NAVY BLUE. For official legal definitions of offenses, refer to reference (h).

a. Bullying: Per reference (ag) is an act of aggression by a military member or members or


DoD civilian employee or employees, with a nexus to military service or DoD civilian
employment, with the intent of harming a military member, DoD civilian or any other persons,
either physically or psychologically, without a proper military or other governmental purpose.

(1) Bullying may involve the singling out of an individual from their co-workers or unit,
for ridicule because he or she is considered different or weak. It often involves an imbalance of
power between the aggressor and the victim.

(2) Bullying includes, but is not limited to, these aspects when performed without a
proper military or other governmental purpose: physically striking another in any manner or
threatening to do the same; intimidating; teasing; taunting; oral or written berating of another for
the purpose of belittling or humiliating; encouraging another to engage in illegal, harmful,
demeaning or dangerous acts; playing abusive or malicious tricks; branding, handcuffing, duct
taping, tattooing, shaving, greasing or painting; subjecting to excessive or abusive use of water;
the forced consumption of food, alcohol, drugs or any other substance; and degrading or
damaging the person or their property or reputation. Bullying can be conducted through the use
of electronic devices or communications and by other means, as well as in person.

CUI
B-13 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

b. Child Abuse: The physical abuse, sexual abuse, emotional abuse or neglect of a child by
a parent, guardian, foster parent or by a caregiver, whether the caregiver is intra-familial or extra-
familial, under circumstances indicating the child’s welfare is harmed or threatened. Such acts
by a sibling, other family member or other family member must be deemed to be child abuse
only when the individual is providing care under express or implied agreement with the parent,
guardian or foster parent, as defined in reference (j). The term encompasses both acts and
omissions on the part of such a responsible person. This term includes alleged offenders whose
relationship is outside the family and includes, but is not limited to, individuals known to the
child and living or visiting in the same residence who are unrelated to the victim by blood or
marriage and individuals UKN to the victim. Specific types of child abuse and or neglect are:

(1) Child Emotional Abuse: Acts or a pattern of acts, omissions or a pattern of omissions
or passive or passive-aggressive inattention to a child’s emotional needs resulting in an adverse
effect upon the child’s psychological well-being, including intentional berating, disparaging or
other verbally abusive behavior toward the child and violent acts which may not cause
observable physical injury.

(2) Child Neglect: The negligent treatment of a child through actions or omissions by a
parent, guardian or caretaker, for the child’s welfare under circumstances indicating the child’s
welfare is harmed or threatened to include but is not limited to abandonment, deprivation of
basic necessities (nourishment, shelter, clothing and health care), educational neglect, lack of
supervision, medical neglect or non-organic failure to thrive.

(3) Extra-Familial Child Abuse: Includes any type of child abuse by strangers or persons
in loco parentis (a teacher or other adult responsible for children in place of a parent).

c. Child Sexual Abuse: The employment, use, persuasion, inducement, enticement or


coercion of any child to engage in or assist any other person to engage in, any sexually explicit
conduct or simulation of such conduct for the purpose of producing a visual depiction of such
conduct; or the rape and in cases of caretaker or inter-familial relationships, statutory rape,
molestation, prostitution or other form of sexual exploitation of children or incest with children.

d. Domestic Abuse: Domestic violence or a pattern of behavior resulting in emotional or


psychological abuse, economic control or interference with personal liberty that is directed
toward a person who is:

(1) A current or former spouse.

(2) A person with whom the abuser shares a child in common.

(3) A current or former intimate partner with whom the abuser shares or has shared a
common domicile.

CUI
B-14 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

e. Domestic Violence: An offense under the USC, UCMJ or State law which involves the
use, attempted use or threatened use of physical force against a person and is committed by a
current or former spouse, parent or guardian of the victim; by a person with whom the victim
shares a child in common; by a person who is cohabitating with or has cohabitated with the
victim as a spouse, parent or guardian; or by a person who similarly situated to a spouse, parent
or guardian of the victim.

f. EO: The right of all persons to participate in and benefit from programs and activities for
which they are qualified, as defined in reference (k). These programs and activities will be free
from social, personal or institutional barriers that prevent people from rising to the highest level
of responsibility possible. Persons will be evaluated on individual merit, fitness and capability;
regardless of race, ethnicity, national origin, sex (including gender identity), sexual orientation or
religion.

g. Extremist Group: Per reference (l), an organization that espouses supremacist causes;
attempts to create illegal discrimination based on race, creed, color, ethnicity, national origin,
sex, sexual orientation or religion; advocates using force or violence; or otherwise engages in
efforts to deprive individuals of their civil rights.

h. Fraternization: Per reference (ah) is a gender-neutral concept used to identify personal


relationships that do not respect the bounds of acceptable senior-subordinate relationships.
Although it has most commonly been applied to officer-enlisted relationships, fraternization also
includes improper relationships and social interaction between officer members as well as
between enlisted members, regardless of the Service affiliation of the other officer or enlisted
member, including members of foreign military services.

i. Harassment: A form of discrimination that is unwelcomed conduct based on race, color,


religion, sex (including gender identity), national origin or sexual orientation. Harassment
occurs when the conduct is severe or pervasive enough to create a work environment that a
reasonable person would consider intimidating, hostile or abusive.

j. Hazing per reference (ag) is any conduct through which a military member or members
or a DoD civilian employee or employees, without a proper military or other governmental
purpose but with a nexus to military service or DoD civilian employment, physically or
psychologically injure or create a risk of physical or psychological injury to one or more
members, DoD civilians or any other persons for the purpose of: initiation into, admission into,
affiliation with, change in status or position within or as condition for continued membership in
any military or DoD organization.

(1) Hazing includes, but is not limited to, the these aspects when performed without a
proper military or other governmental purpose: any form of initiation or congratulatory act that
involves physically striking another in any manner or threatening to do the same; pressing any
object into another person’s skin, regardless of whether it pierces the skin, such as “pinning” or

CUI
B-15 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

“tacking on” of rank insignia, aviator wings, jump wings, diver insignia, badges, medals or any
other object; oral or written berating of another for the purpose of belittling or humiliating;
encouraging another to engage in illegal, harmful, demeaning or dangerous acts; playing abusive
or malicious tricks; branding, handcuffing, duct taping, tattooing, shaving, greasing or painting;
subjecting to excessive or abusive use of water; and the forced consumption of food, alcohol,
drugs or any other substance. Hazing can be conducted through the use of electronic devices or
communications and by other means, as well as in person.

k. Sexual Assault: Intentional sexual contact, characterized by use of force, threats,


intimidation, abuse of authority or when the victim does not or cannot consent. “Consent”
means words or overt acts indicating a freely given agreement to the sexual conduct at issue by a
competent person. An expression of lack of consent through words or conduct means there is no
consent. Lack of verbal or physical resistance or submission resulting from the accused’s use of
force, threat of force or placing another person in fear does not constitute consent. A current or
previous dating relationship by itself or the manner of dress of the person involved with the
accused in the sexual conduct at issue will not constitute consent. Sexual assault includes but is
not limited to rape, forcible sodomy (oral or anal sex) and other unwanted sexual contact that is
aggravated, abusive or wrongful (to include unwanted and inappropriate sexual contact) or
attempts to commit these acts. For definitions of these crimes and related offenses, see the
UCMJ in reference (h).

l. Sexual Harassment is conduct that:

(1) involves unwelcome sexual advances, requests for sexual favors and deliberate or
repeated offensive comments or gestures of a sexual nature when:

(a) submission to such conduct is made either explicitly or implicitly a term or


condition of a person’s job, pay or career;

(b) submission to or rejection of such conduct by a person is used as a basis for career
or employment decisions affecting that person; or

(c) such conduct has the purpose or effect of unreasonably interfering with an
individual’s work performance or creates an intimidating, hostile or offensive working
environment.

(2) Is so severe or pervasive that a reasonable person would perceive and the victim does
perceive, the environment as hostile or offensive.

(3) Any use or condonation, by any person in a supervisory or command position, of any
form of sexual behavior to control, influence or affect the career, pay or job of a member of the
armed forces or a civilian employee of the DoD.

CUI
B-16 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

(4) Any deliberate or repeated unwelcome verbal comment or gesture of a sexual nature
by any member of the Military Services or civilian employee of the DoD; and

(5) While it is not possible to list all of those additional circumstances that may constitute
sexual harassment, reference (ai) provides some examples of conduct, which, if unwelcome,
constitutes sexual harassment and is unacceptable.

m. Suicide: A leading cause of death among Service members. All suicides and suicide-
related behavior must be reported as outlined in reference (p). Suicide-related behavior includes
both suicidal ideation and suicide attempt. These definitions qualify as suicide-related behavior:

(1) Suicidal Ideation- Thinking about, considering or planning for suicide.

(2) Suicide Attempt - A non-fatal self-directed potentially injurious behavior with any
intent to die as a result of the behavior, may or may not result in injury.

(3) Suicide (Death by Suicide) - Death caused by self-directed injurious behavior with
any intent to die as a result of the behavior.

(4) Whether behavior qualifies as suicide-related behavior is a determination to be made


by an appropriate competent authority.

n. Supremacist Activities: Per reference (y), no person in the naval service will actively
advocate supremacist or extremist doctrine, ideology or causes, including those that advance,
encourage or advocate illegal discrimination based on race, creed, color, sex, religion, ethnicity,
sexual orientation or national origin or that advance, encourage or advocate the use of force,
violence or criminal activity or otherwise advance efforts to deprive individuals of their civil
rights. Additionally, no person in the naval service will actively participate in criminal gangs or
in any other organization that: advocates supremacist or extremist doctrine, ideology or causes;
attempts to create illegal discrimination based on race, creed, color, sex, religion, ethnicity,
sexual orientation or national origin; advocates the use of force, violence or criminal activity; or
otherwise engages in efforts to deprive individuals of their civil rights. The term “actively
participate,” as used in reference (y), includes, but is not limited to, acts or conduct, performed
alone or in concert with another, such as: fundraising; demonstrating or rallying; recruiting,
training, organizing or leading members; distributing material, including posting on-line; or
otherwise engaging in any other activities in relation to such criminal gangs or organizations or
in furtherance of the objectives of such criminal gangs or organizations, when such conduct or
activity is detrimental to good order, discipline or mission accomplishment or is service
discrediting.

o. Unlawful Discrimination: The disparate treatment or harassment of an individual or


group based on a prohibited factor contrary to Federal law or regulation per reference (l).

CUI
B-17 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

p. Workplace Violence: Defined by Federal Department of Labor's Occupational Safety and


Health Administration (OSHA) as "any physical assault or acts of aggressive behavior occurring
where employees perform any work-related duty in the course of their employment.

q. Table B-1 (pages B-18 – B-20) can be used as aid for commands in determining if an
OPREP-3 message should be a NAVY BLUE or NAVY UNIT SITREP.

Personnel Incident Category NAVY NUS Additional reporting requirements


BLUE
Death of, critical injury to or
missing COs or senior officials X
(flag officer or equivalent)
Death or injury to personnel
embarked in navy or MSC X
ships and aircraft
Death, serious injury or serious
illness in which the adequacy
X
of medical care is reasonably
in question
Death or serious injury of a
civilian, including civilian
X
traffic accident deaths caused
by a service member.
Continue reporting through case
X disposition if Service member
Murder subject
Continue reporting through case
X disposition if Service member
Armed Robbery subject
Continue reporting through case
Aggravated assault or assault X disposition if Service member
with a deadly weapon subject
Continue reporting through case
X disposition if Service member
Kidnapping or carjacking subject
Continue reporting through case
Burglary of an occupied X disposition if Service member
dwelling subject
Annotate Sexual Assault-
Penetration or Sexual Assault-
X Contact; If UKN at initial report:
Sexual Assault-UKN; Update
Sexual Assault report with NCIS Case Number
CUI
B-18 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

Personnel Incident Category NAVY NUS Additional reporting requirements


BLUE
Update report with incident type
(contact or penetration) when
known; Continue reporting
through case disposition to include
a final report upon case
disposition.
Include date, location and type of
Service member's most recent
X deployment (operational,
expeditionary, individual
Domestic Violence or Abuse augmentee).
Child abuse and or neglect X
Continue reporting through case
X disposition if Service member
Child sexual abuse subject
Sexual Harassment X
Include date, location and type of
Service member's most recent
X deployment (operational,
expeditionary, individual
Suicide augmentee).
Include date, location and type of
Service member's most recent
X deployment (operational,
expeditionary, individual
Suicide Related behavior augmentee).
EO Incidents X
Unlawful discrimination X
Hazing or Bullying X
Motor Vehicle accidents
involving alcohol or illegal X
substances
Negligent discharge of a Report type of follow investigation
X
firearm to be conducted.
Report whether the rider had
X completed appropriate motorcycle
Motor cycle accidents safety course.
Personnel Incident with Media
X
Attention
Personnel incidents in foreign
X
countries involving military
CUI
B-19 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

Personnel Incident Category NAVY NUS Additional reporting requirements


BLUE
personnel and their dependents
Personnel incidents involving
host nation personnel that
X
could generate media or
political interest
Personnel incidents in foreign
countries, involving US
X
government civilian personnel
and contractors
Personnel incident in the
judgement of the CO requires
X
elevation from SITREP to
OPREP NAVY BLUE
Continue reporting through case
Supremacist or Extremist X disposition of service member(s) in
Group Activity subject.
Table B-1

CUI
B-20 Appendix B
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX C – ARMS, AMMUNITION AND EXPLOSIVES (AA&E) INCIDENT REPORTS

1. Specific Reporting Instructions.

a. Per reference (aj), all significant incidents of confirmed theft or loss of AA&E, including
inventory adjustment losses must be reported as soon as possible, but not later than 72 hours
after occurrence or discovery, to the Office of the Under Secretary of Defense for Intelligence,
Director of Security. Incidents to be reported include those identified in subparagraphs a(1)
through a(5) and 1d(1) through 1d(8) of this appendix.

(1) Attempted or armed robberies of AA&E facilities.

(2) Forced entries or attempted forced entries into AA&E facilities.

(3) Evidence of theft of AA&E.

(4) Incidents involving AA&E that cause significant news coverage or appear to have the
potential to cause such coverage.

(5) Evidence of trafficking or bartering involving AA&E, illegal drugs, etc., regardless of
the quantity of AA&E involved.

b. An OPREP-3 NAVY BLUE report is used to provide the CNO and other naval
commanders with immediate notification of:

(1) Incidents of MLSR AA&E.

(2) Weapon discharge incidents resulting in media interest or injury to personnel.

(3) Explosive incidents resulting in damage to publicly or privately-owned property or


personnel injury or death.

(4) As indicated in chapter 4, subparagraph 1b, any incident in which live ordnance is
launched, fired or expended unintentionally but does not qualify as an explosive incident but
could garner media attention. Examples include a weapon landing off of government-owned
property or outside the boundaries of the target range or a vehicle accident involving ammunition
or explosive materiel being transported between military installations.

c. An OPREP-3 NAVY UNIT SITREP is used to provide the ISIC with notification of:

(1) Weapon discharge incidents that do not result in media interest or injury to personnel.

(2) Any negligent discharge of a weapon that does not cause injury to personnel.

CUI
C-1 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

d. The confirmed theft, loss, recovery or inventory adjustment of AA&E items listed in
subparagraphs 1d(1) through 1d(8) must be reported to Director, Logistics-Supply Chain
Operations, OPNAV N41, using OPREP 3 NAVY BLUE voice and record message reporting
requirements.

Note: Security risk categories I through IV are defined in reference (z).

(1) Any missiles, rockets or arms.

(2) 5,000 rounds or more of ammunition smaller than 40 mm or 20,000 rounds or more
of .38 caliber or 9 mm.

(3) Five rounds or more of ammunition 40 mm and larger.

(4) Individual mortar, grenade and missile rounds.

(5) One or more mines (antipersonnel or antitank).

(6) Items with 10 or more pounds of net explosive weight.

(7) Silencers, mufflers, noise suppression devices and sniper rifle systems.

(8) Demolition explosives including detonation cord, blocks of explosives and other
explosives.

e. Incidents that result in significant news coverage or appear to have the potential to cause
such coverage, must be reported.

f. Reporting requirements begin when a loss is discovered, whether by discovery of an


incident, receipt of a loss claim, completion of an inventory or any other means.

2. Report Content. The OPREP-3 NAVY BLUE is a USMTF-based report that is incorporated
into reference (b). It is based on the OPREP-3 message. The message examples are edited
accordingly.

a. The specific information must be included in the GENTEXT-INCIDENT


IDENTIFICATION AND DETAILS section of the OPREP-3 NAVY BLUE report, except as
annotated:

(1) TIMELOC.

(2) Description of the event (e.g., MLSR items).

CUI
C-2 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

(3) AA&E item identification and material description (nomenclature, mark, model and
modification, lot number, serial number (if applicable) and quantity).

(4) Incident cause and details.

(5) Investigation information, include the status of NCIS notification or participation, if


any.

(6) POC (name, phone number and e-mail).

3. Voice Message Reports.

a. Initial voice message reports must be made within the timeframe specified in chapter 2,
section I.

b. OPREP-3 NAVY BLUE voice message formats for AA&E incidents are the same as for
OPREP-3 NAVY BLUE reports. OPREP-3 NAVY UNIT SITREP voice reports are not
required by CNO.

c. OPREP-3 NAVY BLUE Voice Message Report Example

HOMEPLATE THIS IS SHIP OPREP THREE NAVY BLUE OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE NAVY BLUE OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE MISSING ONE MIKE FOUR SERVICE RIFLE
LINE TWO BEFORE STARTING DAILY INVENTORY DOOR TO WEAPONS STORAGE
FACILITY FOUND UNLOCKED BREAK ALL ITEMS ACCOUNTED FOR EXCEPT THIS
ONE BREAK NOVEMBER CHARLIE INDIA SIERRA NOTIFIED
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified chapter 2,
section I.

b. MTF data sets are the same as used for OPREP-3 NAVY BLUE or NAVY UNIT
SITREP, as appropriate. Addresses for OPREP-3 NAVY BLUE and NAVY UNIT SITREPs are
provided in subparagraphs 4c and 4d.

c. OPREP-3 NAVY BLUE Record Message Example

CUI
C-3 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

(1) ACTION addresses:

CNO WASHINGTON DC//


Combatant Commander:
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
HQ USNORTHCOM//
Fleet Commander:
COMUSFLTFORCOM NORFOLK VA//
COMPACFLT PEARL HARBOR HI//
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVSO
COMUSNAVCENT
Type Commander
Other Operational and Administrative Commanders
NAVSURFWARCENDIV CRANE IN//
NAVAMMOLOGCEN MECHANICSBURG PA//
Local NAVCRIMINVSERV (NCIS) office

(2) INFO addresses:

Chain of Command
CHINFO WASHINGTON DC
NAVY JAG WASHINGTON DC
NAVINSGEN WASHINGTON DC
DIRNAVCRIMINVSERV QUANTICO VA
COMNAVSAFECEN NORFOLK VA
NAVORDSAFSECACT INDIAN HEAD MD
CMC WASHINGTON DC (USMC personnel or mission incidents)
CG TECOM (USMC training unit incidents involving personnel or missions)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
SOPA
Regional Commander, as appropriate
Installation Commander, as appropriate

(3) Message body:

MSGID/OPREP-3NB, USMTF, YYYY/USS SHIP/001//


FLAGWORD/NAVY BLUE/-//
TIMELOC/100429ZMAR2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. DESCRIPTION: MISSING ONE MACHINE GUN

CUI
C-4 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

2. AA&E ITEM SERIAL NUMBER, IDENTIFICATION AND MATERIAL


DESCRIPTION: N/A
3. INCIDENT CAUSE AND DETAIL: BEFORE STARTING DAILY
INVENTORY, DOOR TO WEAPONS STORAGE FACILITY FOUND UNLOCKED.
ALL ITEMS ACCOUNTED FOR EXCEPT THIS ONE.
4. INVESTIGATION INFO: NCIS NOTIFIED
5. POC: LT BROWN, COMM 555-555-5555, DSN 555-5555,
[email protected]//

d. OPREP-3 NAVY UNIT SITREP Record Message Example:

MSGID/OPREP-3NUS, USMTF, YYYY/NAS CECIL FIELD/001//


FLAGWORD/NAVY UNIT SITREP/-//
TIMELOC/100429ZMAR2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. DESCRIPTION: POST PLACED HIS M-4 INTO AN IMPROPER READINESS
POSTURE AND ONE ROUND FIRED.
2. AA&E ITEM IDENTIFICATION AND MATERIAL DESCRIPTION: SAF202B US
ARMY SA80 L85A1 WITH 25 ROUND MAGAZINE CLIP. SERIAL 11235679-AM-
M4345.
3. INCIDENT CAUSE AND DETAIL: MARINE SECURITY FORCE, SOG
AND POST 13 WHILE IN THE PROCESS OF CLEARING WEAPON FOR
POST TURNOVER DISCHARGED ONE M-4 ROUND INTO A SAFETY
BARREL. POST 13 REPORTED TO THE SOG “CHAMBER CLEAR” DURING
POST TURN OVER PROCEDURES, SPECIFICALLY WEAPONS CLEAR
INSPECTION. BEFORE SOG COULD COMPLETE HIS INSPECT OF THE
BREECH, CHAMBER AND BARREL, POST 13 PLACED MUZZLE INTO
CLEARING BARREL AND PULLED TRIGGER, DISCHARGING ONE ROUND.
INVESTIGATION INFO: ONE BULLET FOUND INSIDE THE CLEARING
BARREL. NO INJURIES TO REPORT. NO DAMAGE TO REPORT.
POC: LT BROWN, COMM 555-555-5555, DSN 555-5555,
[email protected]//

e. OPREP-3 NAVY BLUE Non-Explosive Mishap Record Message Example:

(1) TO (Action) addresses:

CNO WASHINGTON DC//


CMC WASHINGTON DC// (for USMC personnel or mission incident)
COMUSFLTFORCOM NORFOLK VA//
Component Commander:
COMPACFLT PEARL HARBOR HI//
COMUSNAVEUR COMUSNAVAF NAPLES IT

CUI
C-5 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

COMUSNAVCENT
COMUSNAVSO
COMMARFORCOM (for USMC personnel or mission incident)
COMMARFORPAC (for USMC personnel or mission incident)
Fleet Commander
Type Commander
Other Operational and Administrative Commanders
Local NAVCRIMINVSERV (NCIS) office

(2) INFO addresses:

Chain of Command
CHINFO WASHINGTON DC//
ONI WASHINGTON DC
COMNAVSAFECEN NORFOLK VA//
NAVORDSAFSECACT INDIAN HEAD MD //
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


DIRNAVCRIMINVSERV QUANTICO VA
COMDT COGARD WASHINGTON DC (for port or ship mishap)
Appropriate SYSCOM:
COMNAVAIRSYSCOM PATUXENT RIVER MD (for air launched
weapon)
COMNAVSEASYSCOM WASHINGTON DC
COMNAVSEASYSCOM WASHINGTON DC (for SSN, SSBN, SSGN,
CVN)
COMMARCORSYSCOM QUANTICO VA (for USMC mishap)
DIRSPP WASHINGTON DC (for SSBN conventional explosive mishap)
BUMED FALLS CHURCH VA (for personnel injury or death)
CG TECOM (USMC training unit incidents involving personnel or missions)
CNIC WASHINGTON DC (for explosive mishap at Navy shore facility)
Navy CNI Regional Commander (for Navy shore activity)
Marine Corps Regional Commander (for Marine Corps unit)
Appropriate U.S. Coast Guard District (for port or ship explosive mishap)
SOPA

(4) Message body:

MSGID/OPREP-3NB, USMTF, YYYY/NAVY ACTIVITY/SERIAL NUMBER//

CUI
C-6 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

FLAGWORD/NAVY BLUE/NON EXPLOSIVE MISHAP//


GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: NON EXPLOSIVE MISHAP
2. DATE OF INCIDENT: DDMMMYYYY
3. TIME OF INCIDENT: HHMML (local time using 24 hour clock)
4. LOCATION OF INCIDENT: (brief description of where mishap occurred)
5. INCIDENT: (brief description of the mishap).
6. AMMUNITION/EXPLOSIVES INVOLVED: (indicate if known)
A. NOMENCLATURE
B. MARK/MODEL
C. QUANTITY
D. LOT NUMBER
E. SERIAL NUMBER (if applicable)
7. ADDITIONAL INFORMATION TO BE PROVIDED USING REPORTING
PROCEDURES CONTAINED IN OPNAVINST 8000.16C (or applicable Marine Corps
Order)
8. MEDIA INTEREST: (YES OR NOT ANTICIPATED)
9. NCIS INVOLVEMENT: (YES OR NOT ANTICIPATED)
10. POC: NAME OF INDIVIDUAL, COMMAND, PHONE NUMBER, E-MAIL
ADDRESS//

f. OPREP-3 NAVY BLUE Explosive Mishap Record Message Example:

(1) TO (Action) addresses:

CNO WASHINGTON DC// /


CMC WASHINGTON DC// (for USMC personnel or mission incident)
COMUSFLTFORCOM NORFOLK VA//
Fleet Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
COMMARFORCOM (for USMC personnel or mission incident)
COMMARFORPAC (for USMC personnel or mission incident)
Type Commander
Other Operational and Administrative Commanders
Local NAVCRIMINVSERV (NCIS) office

(2) INFO addresses:

Chain of Command

CUI
C-7 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

CHINFO WASHINGTON DC//


ONI WASHINGTON DC
COMNAVSAFECEN NORFOLK VA//
NAVORDSAFSECACT INDIAN HEAD MD //
NAVORDSAFSECACT ESSOLANT NORFOLK VA//
NAVORDSAFSECACT ESSOPAC SAN DIEGO CA//
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


DIRNAVCRIMINVSERV QUANTICO VA//
COMDT COGARD WASHINGTON DC (for port or ship explosive mishap)
Appropriate Systems Command (SYSCOM):
COMNAVAIRSYSCOM PATUXENT RIVER MD// (for air launched weapon)
COMNAVSEASYSCOM WASHINGTON DC//
COMNAVSEASYSCOM WASHINGTON DC// (for SSN, SSBN, SSGN, CVN)
COMMARCORSYSCOM QUANTICO VA// (for USMC explosive mishap)
BUMED FALLS CHURCH VA// (for personnel injury or death)
CG TECOM (USMC training unit incidents involving personnel or missions)
CNIC WASHINGTON DC// (for explosive mishap at Navy shore facility)
Navy CNI Regional Commander// (for Navy shore activity)
Marine Corps Regional Commander// (for Marine Corps unit)
Appropriate U.S. Coast Guard District (for port or ship explosive mishap)
SOPA

(4) Message Body:

MSGID/OPREP-3NB, USMTF, YYYY/NAVY ACTIVITY/SERIAL NUMBER//


FLAGWORD/NAVY BLUE/EXPLOSIVE MISHAP//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: EXPLOSIVE MISHAP
2. DATE OF INCIDENT: DDMMMYYYY
3. TIME OF INCIDENT: HHMML (local time using 24 hour clock)
4. LOCATION OF INCIDENT: (brief description of where mishap occurred)
5. INCIDENT: (brief description of the explosive mishap – what occurred and estimated
extent of personnel injury and property damage).
6. AMMUNITION/EXPLOSIVES INVOLVED: (indicate if known)
A. NOMENCLATURE
B. MARK/MODEL
C. QUANTITY
D. LOT NUMBER

CUI
C-8 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

E. SERIAL NUMBER (if applicable)


7. INJURIES: (YES OR NO - if no, go to 8)
A. DEATHS
B. INJURED
8. PROPERTY DAMAGE ON BASE (YES OR NO – if no, go to 9)
A. BUILDING(S)
B. EQUIPMENT (CLASS 7 - MAJOR END ITEMS)
9. PROPERTY DAMAGE OFF BASE (YES OR NO – if no, go to 10)
A. BUILDING(S)
B. EQUIPMENT (CLASS 7 - MAJOR END ITEMS)
10. ADDITIONAL INFORMATION TO BE PROVIDED USING
REPORTING PROCEDURES CONTAINED IN (state whether OPNAVINST 5102.1D,
OPNAVINST 8000.16E or applicable Marine Corps Order)
11. MEDIA INTEREST: (YES OR NOT ANTICIPATED)
12. NCIS INVOLVEMENT: (YES OR NOT ANTICIPATED)
13. POC: NAME OF INDIVIDUAL, COMMAND, PHONE NUMBER,
E-MAIL ADDRESS//

CUI
C-9 Appendix C
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX D - MARINE MAMMAL INCIDENT REPORTS

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE must be used to report any
marine mammal incident.

a. This guidance applies to all Navy commands, including any Navy installation, ship or
aircraft under contract to or conducting research and development or test and evaluation
activities for the Navy. OPNAV (N45) is the clearinghouse for all Navy information related to
marine mammal strike or stranding occurrences worldwide. CNO N3/N5 will support OPNAV
N45 directly in coordinating these marine mammal incident reports.

b. In the event of a marine mammal strike or stranding, OPNAV (N45) is the sole POC for
liaison activities with the NOAA Fisheries Headquarters. Coordination with OPNAV (N45) is
required prior to or immediately after the fleet or regional commander has engaged regional
NOAA Fisheries offices with regard to a stranding or strike incident.

c. The CNO BWC in the NOC, Washington, DC, is responsible for collecting and
disseminating operational and ashore information to CNO leadership. The NOC must receive all
voice and message reports related to marine mammal incidents so that it can notify appropriate
OPNAV action officers and leadership. Marine mammal incidents by their very nature require
coordination of information across commands, both afloat and ashore. Fleet commanders have
the lead for information coordination and will support the NOC. Regional commanders will
support the fleet commanders by coordinating shore command marine mammal incident
information.

2. Report Content. The OPREP-3 NAVY BLUE is a USMTF based report that is incorporated
into reference (b). It is based on the OPREP-3 message and the message examples are edited
accordingly.

a. Initial Report. The initial voice must conform to the requirements of chapter 2, sections I
and II, of this instruction. The initial voice and record message report is intended to inform the
chain of command expeditiously of the existence of the marine mammal event within the
timeframe specified.

b. FOLUP reporting. Not all reportable marine mammal events require FOLUP reporting.
Based on the initial report and the attendant facts and circumstances surrounding the event,
OPNAV N45 will coordinate with the NOC to determine whether FOLUP reporting is required.
Factors such as proximity of naval forces, physical condition of the animal, congressional
interest, other agency interest, media interest and other pertinent information will be considered
in making the determination.

CUI
D-1 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

(1) If required, FOLUP reports must be made via naval message to CNO N3/N5 and
OPNAV N45 and the NOC within 24 hours following the initial report. Negative reports are
required.

(2) Contents of FOLUP Reports. FOLUP reports will only contain information not
included in the initial report. The report must be submitted within 24 hours following the initial
report even if not all information is available. Additional FOLUP reports must be submitted
every 24 hours thereafter until all information has been forwarded to CNO N3/N5 and OPNAV
N45.

(3) Under certain circumstances, more comprehensive reporting may be appropriate. In


such instances, especially if litigation is anticipated, an investigation may be directed pursuant to
section 0209 of reference (aa). Close coordination between the cognizant fleet commander and
OPNAV N45 will be essential in these situations.

c. Include TIMELOC.

d. These specific information components must be included in the GENTEXT-INCIDENT


IDENTIFICATION AND DETAILS section of the report:

(1) Type of Marine Mammal Incident (strike or stranding).

(2) Date of incident.

(3) Time of incident (local vice Zulu time).

(4) Location of incident (include LAT and LONG).

(5) Whale Strike Details:

(a) Identity of person who discovered event (e.g., military, civilian, other government
personnel).

(b) Circumstances surrounding the discovery (e.g., NOAA survey flight, normal
steaming operations, press coverage, local agency notification).

(c) Description of animal, including species, size and length, location (LAT and
LONG) of the animal (or strike if the animal has disappeared) and injury status, to the extent
known.

(d) Existence of photographs or video.

CUI
D-2 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

(e) Description of the class, type and operational status of the vessel involved in the
strike.
(6) Stranding Details (if available):

(a) Time stranding commenced.

(b) Time of last stranding.

(c) Where stranding occurred (geographical name of location and LAT and LONG).

(d) How many marine mammals stranded and apparent condition (alive, dead,
severely decayed, etc.).

(e) Species type(s).

(f) How many marine mammals died.

(g) Whether necropsies performed.

(h) Who performed the necropsy.

(7) Identity of any naval units (surface, subsurface or air) in the region potentially
involved.

(8) Acoustic activity. If active sonar or explosive devices employed by any units listed
under subparagraph 2d(7), provide:

(a) Sonar employed.

(b) Ship's tracks and heading.

(c) Time of employment (72 hours leading up to and following initial stranding).

(d) Power levels used.

(e) Explosives used, type and how many.

(9) Oceanographic details (these factors are key to any assessment of whether sonar may
have contributed to this stranding event).

(a) Meteorological information (surface winds, sea states).

(b) Sound velocity profiles, bathythermograph observations, thermal profiles.

CUI
D-3 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

(c) Bathymetry, bottom composition.

(d) Surface ducts.

(10) Any mitigation measures in effect (steps taken by naval units identified in
subparagraph 2d(7), to mitigate against impacts on marine mammals), including:

(a) Lookouts (training, if any, in marine mammal sighting).

(b) Marine mammal pre-exercise surveys.

(c) Coordination with air assets.

(d) Marine mammals spotted prior to and during exercise.

(e) Steps taken to avoid marine mammals.

(11) The existence, if any, of environmental planning documents (e.g., National


Environmental Policy Act documents, Protective Measures Assessment Protocol reports)
relevant to the naval activity described in subparagraph 2d.

(12) Location of relevant documents, logs and records (in addition to the information
delineated in subparagraph 2d, retain all associated documents, logs and records relating to ship
movement, sonar usage, weather and environmental observations, bathythermograph
observations for units identified in subparagraph 2d(7).

(13) Additional information (e.g., possible difficulties in obtaining information from a


foreign navy or government, media attention anticipated).

(14) Command POC (name, phone number and e-mail).

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. Once received from the MOC, the NOC will notify the OPNAV N45 Marine Mammal
POC.

c. Voice message formats for marine mammal incidents are the same as for the OPREP-3
NAVY BLUE.

d. Voice Message Report Example

CUI
D-4 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

HOMEPLATE THIS IS SHIP OPREP THREE NAVY BLUE OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE NAVY BLUE OVER
THIS IS SHIP
ROUTINE
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE WHALE STRIKE OFF SOUTH COAST OF JAPAN
LINE TWO SHIP CONDUCTING ROUTINE OPERATIONS WHEN SPERM WHALE HIT
SHIP’S SCREW BREAK WHALE SWAM AWAY TRAILING BLOOD BREAK UNABLE
TO FOLLOW
OVER

4. Record Message Report.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I. Updated reports are required per subparagraph 2b.

b. MTF data sets are the same as for the OPREP-3 NAVY BLUE.

c. OPREP-3 NAVY BLUE Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC//


Combatant Commander:
CDR USPACOM HONOLULU HI
CDR USEUCOM VAIHINGEN GE
HQ USNORTHCOM//
Fleet Commander:
COMUSFLTFORCOM NORFOLK VA (All marine mammal incidents)
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVSO
COMUSNAVCENT
Type Commander
Other Operational and Administrative Commanders

(2) INFO addresses:

Chain of Command
CHINFO WASHINGTON DC
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)

CUI
D-5 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

SOPA

d. Message body:

MSGID/OPREP-3NB, USMTF, YYYY/USS SHIP/001//


REF/A/DESC: INITIAL VOICE REPORT TO MOC/USS
NEVERSAIL/100429ZMAR2005//
FLAGWORD/NAVY BLUE/-//
TIMELOC/0901245ZAUG2005/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. MARINE MAMMAL INCIDENT: WHALE STRIKE
2. DATE OF INCIDENT: 09AUG2005
3. TIME OF INCIDENT: 0753L
4. LOCATION OF INCIDENT: OFF JAPAN’S SOUTHERN COAST
5. WHALE STRIKE DETAILS:
A. PERSON DISCOVERING EVENT: SN SMITH, LOOKOUT
B. CIRCUMSTANCES SURROUNDING DISCOVERY: NORMAL
STEAMING OPS
C. DESCRIPTION OF ANIMAL: SPERM WHALE
D. PHOTOS/VIDEOS: NONE
6. STRANDING DETAILS: N/A
7. NAVAL UNITS INVOLVED: NONE
8. ACOUSTIC ACTIVITY: NONE
9. OCEANOGRAPHIC DETAILS: SEA STATE 1
10. MITIGATION MEASURES IN EFFECT: ALL LOOKOUTS QUALIFIED IN
MARINE MAMMAL SIGHTING
11. ENV PLANNING DOCS: NONE
12. LOCATION OF RELEVANT DOCS: LOGS RETAINED ONBOARD
13. ADDITIONAL INFO: MEDIA ATTENTION ANTICIPATED
14. POC: LT BROWN, COMM 555-555-5555, DSN 555-5555,
[email protected]//

5. Guidance and Definitions.

a. Reportable Marine Mammal Events. Due to the nature, location and visibility of certain
events involving marine mammals, expeditious reporting is required.

(1) Whale strikes. Whale strikes continue to be reportable events per reference (aa).

(2) Strandings. The NOAA Fisheries definition of stranding includes not only those
animals found alive or dead on beaches, but also those floating dead in open water. Strandings
that occur on or near Navy Installations require reporting to the NOC.

CUI
D-6 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

(3) Other. Claims of unusual marine mammal behavior reported in the media or by
National Marine Fisheries Service, a private party or non-governmental entity in which naval
operations, exercises or training have been implicated are reportable events. Any other incident
involving marine mammals, which have significant media interest and may implicate naval
operations at sea are also reportable events. Examples of such marine mammal events might
include manatee strandings or mass strandings (two or more) of dolphins, seals, sea lions, otters,
etc.

b. For purposes of this section, “naval operations at sea” means surface and subsurface
activities involving one or more units engaged in operations, exercises or training. It also
includes air operations that may have an effect on the marine environment.

c. NMMSRT. The NMMSRT is responsible for marine mammal incident management


including notification of their chain of command, incident analysis and incident response. For all
events resulting in FOLUP reporting, OPNAV N45 will coordinate efforts of the NMMSRT.
The NMMSRT will include CNO N3/N5 and OPNAV N45, CHINFO, Office of Legislative
Affairs-Navy and the cognizant fleet commander.

d. The CNO BWC will contact the appropriate fleet BWCs to obtain information on Navy
units that may have been in the vicinity (within 50 NM and 24 hours) of the incident. Submarine
or aircraft information may not be immediately available and will be provided as an update to the
NMMSRT as soon as the information is available. In addition, sonar use information for units so
equipped and identified as being in the vicinity of the event will be obtained and forwarded to
the NOC BWC as rapidly as possible. No interim commands will issue any press releases or
otherwise comment on stranding or strike incidents unless directed by the NMMSRT.

CUI
D-7 Appendix D
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX E - COMMAND AND CONTROL AND INFORMATION NETWORK OUTAGE


INCIDENT REPORTS

1. Specific Reporting Instructions. The OPREP-3 NAVY BLUE must be used to report any
command and control network or information network outage. For the purposes of this
instruction, information networks include, but are not limited to Non-secure Internet Protocol
Router Network (NIPRNET), SIPRNET, GCCS and JWICS. These reports are submitted to
provide “as it happens” information on these types of incidents:

a. Command and control and information networks critical to current operations or critical
to support current operations, in a theater of engagement that are down and alternative
communication is limited.

b. Any network outage in-theater that severely diminishes or renders a critical operational
capability inoperable.

c. Any network outage that severely diminishes the ability to support operations in-theater.

d. Loss of the FSBS and nuclear command and control incidents are addressed in
PINNACLE and NAVY BLUE guidance on pages 3-3 and 4-2.

2. ES. ES is defined as data placed on an information system possessing insufficient security


controls to protect the data at the required classification level, thus posing a risk to national
security. An ES must be treated as a potential loss or compromise of classified information.
Any ES involving Top Secret data (collateral and above) must be reported as an OPREP-3
NAVY BLUE. An ES involving secret and below data must be reported as an OPREP-3 only if
the incident meets the conditions outlined in chapters 1 and 4. Additional ES reporting
requirements outlined in ALCOM 156/08/NTD 11-08 (COMNAVNETWARCOM VIRGINIA
BEACH VA 032052Z NOV 08) still apply and can be found at NAVNETWARCOM’s
Classified Spillage Center Web site:
https://www.fleetforces.navy.mil/netwarcom/PlansPolicy/PolicyAndDoctrine/spillage/default.asp
x.

3. Report Content. The OPREP-3 NAVY BLUE is a USMTF based report that is incorporated
into reference (b). It is based on the OPREP-3 message and the message examples are edited
accordingly. This specific information must be included in the GENTEXT-INCIDENT
IDENTIFICATION AND DETAILS section of the OPREP-3 NAVY BLUE report:

a. Identification of the type of outage being reported, e.g., NIPRNET, SIPRNET, GCCS,
JWICS, etc.

b. Reference to the voice report in the record communications report of the event.

CUI
E-1 Appendix E
CUI
OPNAVINST 3100.6K
10 Aug 2021

c. Description of the incident or event, including what, when, where, why and how, if
known.

d. Any pertinent information concerning the operational impact of the outage, specifying
what can and cannot be done, back-up plans and expected duration of the outage.

e. A statement in the record message report must be made as to whether FOLUP OPREP-3
NAVY BLUE reports of this incident are anticipated.

f. A FOLUP report containing the missing information must be submitted if all information
was not reported in the initial record message report.

4. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I.

b. Voice reports must be made to the appropriate MOC and or NOC. Ships at sea should
report via SATHICOM or secure telephone to the phone numbers listed in table 2-2 in chapter 2,
section II. Report all outages that significantly alter, hinder or impact current operations to
NAVNETWARCOM via secure telephone due to no SATHICOM access. Reports made by
secure telephone will include caller's name, phone number and where they can be reached.

c. Initial voice report. The initial voice report will be identified by the phrase "OPREP-3
NAVY BLUE," indicating that the communication is of high significance and must be
transmitted or relayed without delay as a matter of unquestioned priority. This IMMEDIATE
precedence message is transmitted by voice when means for record transmission of the
information are not available or when a transmission by voice is required to provide a timely
dissemination of information. OPREP-3 NAVY BLUE voice message formats are the same as
for OPREP-3 NAVY BLUE reports. Originators of this voice message should complete only
those lines required to pass the essential information in each voice message.

d. OPREP-3 NAVY BLUE Voice Message Report Example:

HOMEPLATE THIS IS SHIP OPREP THREE NAVY BLUE OVER


SHIP THIS IS HOMEPLATE SEND OPREP THREE NAVY BLUE OVER
THIS IS SHIP
IMMEDIATE
UNCLASSIFIED
OPREP THREE NAVY BLUE
LINE ONE NIPRNET AT (LOCATION, ACTIVITY, UNIT, ETC) DOWN AT 1600 ZULU.
LINE TWO IMPACT NO ELECTRONIC DATA CONNECTIVITY FROM BWC TO
OPERATING UNITS. CAUSE OF LOSS UNKNOWN. NMCI/EDS INVESTIGATING.
OVER

CUI
E-2 Appendix E
CUI
OPNAVINST 3100.6K
10 Aug 2021

5. Record Message Reports.

a. The initial voice must be made within the timeframe specified in chapter 2, section I.
The amplifying voice report(s) may be followed by amplifying message report(s).

b. MTF datasets are the same as used for OPREP-3 NAVY BLUE. Addresses for OPREP-3
NAVY BLUE are provided in subparagraphs 5c and 5d. Message precedence for all OPREP-3
NAVY BLUE reports must be IMMEDIATE.

c. OPREP-3 NAVY BLUE Record Message Example

(1) ACTION addresses:

CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
COMNAVNETWARCOM VIRGINIA BEACH VA
NCTAMS LANT NORFOLK VA
NCTAMS PAC HONOLULU HI
COMMUNICATIONS CONTROL SHIP (if applicable)

(2) INFO addresses:

Numbered Fleet Commander


Strike Group Commander
Type Commander
COMNAVSEASYSCOM WASHINGTON DC (ship or ship’s system incidents)
NAVCYBERDEFOPSCOM NORFOLK VA (for Computer Intrusion incidents)
DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that
support the nuclear deterrence program)
Other addresses as applicable

d. Record Message Example

UNCLAS
MSGID/OPREP-3NB, USMTF, YYYY/PWC NORFOLK/001/JUN//
FLAGWORD/NAVYBLUE/-//
TIMELOC/241600Z/NORFOLK VA//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/NIPRNET AT
(LOCATION, ACTIVITY, UNIT, ETC) DOWN AT 1600. IMPACT: NO
ELECTRONIC DATA CONNECTIVITY FROM BWC TO OPERATING UNITS.
RELIABLE PHONE CONNECTION IN PLACE. CAUSE OF LOSS UNKNOWN.
NMCI/EDS INVESTIGATING//
RMKS/VOICE REPORT INITIATED 241602Z. NMCI INVESTIGATING AND

CUI
E-3 Appendix E
CUI
OPNAVINST 3100.6K
10 Aug 2021

COOPERATING WITH NNWC. COMMANDERS ESTIMATE: COMMAND AND


CONTROL REQUIREMENTS CANNOT BE MET. BACK-UP PLAN AND
RESTORATION PLAN ACTIVATED. AMPLIFYING INFO TO FOLLOW.//

CUI
E-4 Appendix E
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX F – HOSTILE INCIDENT REPORTS

1. Specific Reporting Instructions. The OPREP-3 NAVY UNIT SITREP SENTINEL report is
used by any unit to provide the TACON for FP chain of command with immediate notification of
possible hostile incidents of military, political or media interests that do not meet the criteria for
OPREP-3 PINNACLE FRONT BURNER or OPREP-3 NAVY BLUE SENTINEL. (e.g., are not
of national or Navy-level interest but warrant reporting to the operational commander or
appropriate higher authority, such as: unauthorized access or events that have been initially
evaluated as a likely non-threat or hoax.) The reports are submitted to provide “as-it-happens”
information to the chain of command. Reportable hostile incidents, include, but are not limited
to:

(a) Any breach of security perimeter or unauthorized access.

(b) Suspected swimmer sightings near U.S. vessels and other U.S. owned watercraft.

(c) Bomb threats initially evaluated by the reporting officer as likely a hoax.

(d) Blocking of Military convoys.

(e) Threats to the President or Vice President of the United States.

(f) Any other suspected hostile incident that could facilitate base access and serve as a
precursor to future hostile incidents, such as the theft of materials to manufacture false
identification cards, stolen identification cards, stolen government license plates, etc.

(g) Unmanned Systems activity in proximity to Navy assets. All Navy installations and
facilities are directed to report any Unmanned System observed flying within the airspace above
the installation or facility or operating on or in close proximity to the installation or facility via
OPREP-3 NAVY BLUE SENTINEL or NAVY UNIT SITREP. All tenant commands and
activities located at U.S. Navy installations must report any observed Unmanned System activity
within the airspace above the host installation or operating on or in close proximity to the host
installation to base security as outline in their installation security plan. While operating
Unmanned Systems in proximity of Navy installation is not a hostile act in and of itself,
ambiguity of who is operating the Unmanned System and their intent, whether it be surveillance
or other malicious intent warrants reporting under TACON FP chain of command. Reference the
current FLEET, COCOM and OPNAV message guidance for report content and message
addressees.

2. Report Content. The OPREP-3 NAVY UNIT SITREP SENTINEL report is a USMTF based
report that is being incorporated into reference (b). It is based on the OPREP-3 message. The
message example is edited accordingly.

CUI
F-1 Appendix F
CUI
OPNAVINST 3100.6K
10 Aug 2021

a. In general, voice and record message reports should address:

(1) What happened?

(2) Who is or was involved?

(3) Where did it happen?

(4) When did it happen?

(5) Why did it happen?

(6) What action is ongoing?

(7) What future action is contemplated?

(8) What is the impact on the command's mission capability?

(9) Is any assistance required?

(10) Is media attention anticipated?

(11) Command POC and 24-hour contact (CDO or similar) information.

3. Voice Message Reports.

a. Initial voice reports must be made within the timeframe specified in chapter 2, section I
and should be made to the first MOC or ROC in the TACON for FP chain of Command.

(1) Example: if an incident happens at Naval Base Norfolk then the report would be
made to the Commander, Navy Region Mid-Atlantic ROC, who would then report to the
respective Fleet Commander MOC, who would then report to the NOC.

(2) Example: if an incident happens at a non-Navy controlled port then the report would
be made from the afloat unit to the Numbered Fleet MOC, who would then report it to United
States Fleet Forces MOC, who would then report to the NOC.

b. Include as much of the information in subparagraph 2a in the initial voice report as


possible, but do not delay the initial report to gather additional information. The information
must be addressed in the initial and amplifying record messages.

c. The voice formats contain only the most important information and may not resemble the
entire record version. For brevity, send only needed information. Each line in the main body of

CUI
F-2 Appendix F
CUI
OPNAVINST 3100.6K
10 Aug 2021

the message contains a line number that enables the message to be transmitted faster. Templates
for all voice message reports are contained in reference (b).

Line Number Line Name Line Description

Line One Incident Enter the incident identification, location and details.
Line Two Narrative Enter any additional information about the incident.

d. Voice Message Report Example

STARBURST THIS IS MOONGLOW OPREP THREE NAVY UNIT SITREP SENTINEL


OVER
MOONGLOW THIS IS STARBURST SEND OPREP THREE NAVY UNIT SITREP
SENTINEL OVER
THIS IS MOONGLOW
NORMAL
UNCLASSIFIED
OPREP THREE NAVY UNIT SITREP SENTINEL
LINE ONE POSSIBLE SURVEILLANCE OF NAVSTA NORFOLK GATE 5
LINE TWO SINGLE MALE SUSPECT SEEN BY BASE SECURITY OBSERVING NAVSTA
NORFOLK GATE FIVE BREAK SUSPECT DEPARTED PRIOR TO LOCAL LAW
ENFORCEMENT ARRIVAL BREAK INCIDENT UNDER INVESTIGATION BY
NOVEMBER CHARLIE INDIA SIERRA AND LOCAL AUTHORITIES
OVER

4. Record Message Reports.

a. Initial record message reports must be made within the timeframe specified in chapter 2,
section I.

b. OPREP-3 NAVY UNIT SITREP SENTINEL MTF data sets are the same as for the
generic OPREP-3 message report contained in reference (b), with the addition of the
FLAGWORD set after the REF set.

SEQ OCC SETID Set Format Name

1 C EXER Exercise Identification


2 O OPER Operation Identification Data
3 M MSGID Message Identification (OPREP-3)
4 O REF * Reference
5 M FLAGWORD FLAGWORD Information (NAVY UNIT SITREP
SENTINEL)
6 M TIMELOC Event Time and Position

CUI
F-3 Appendix F
CUI
OPNAVINST 3100.6K
10 Aug 2021

7 M GENTEXT INCIDENT IDENTIFICATION AND DETAILS


8 O DECL Message Derivative or Original Source for Classification,
Reason for Classification and DECL and Downgrading Data
* Repeatable set

c. Record Message Example

(1) ACTION addresses:

Numbered Fleet Commander


Regional Commander
Installation Commander
Other Operational and Administrative Commanders

(2) INFO addresses:

CNO WASHINGTON DC
COMUSFLTFORCOM NORFOLK VA
Geographic Combatant Commander
Component Commander:
COMPACFLT PEARL HARBOR HI
COMUSNAVEUR COMUSNAVAF NAPLES IT
COMUSNAVCENT
COMUSNAVSO
CNIC WASHINGTON DC
Type Commander
Incident Addresses
DIRNAVCRIMINVSERV QUANTICO VA DC
Local NAVCRIMINVSERV (NCIS) office
In the event of a Unmanned System incursion into Strategic Weapons Facilities
Prohibited Areas, also include:
DIRSSP WASHINGTON DC
HQMC DC PPO (PS)
CTF 114.3
CTF 114.4
CTF 114
JFMCC STRAT
COMMARFORCOM
OFFUTT AFB NE//J3/J31/J38//
MCSF REG
COMDT COGARD WASHINGTON DC
COGARD MARITIME FORCE PROTECTION UNIT KINGS BAY GA
COGARD MARITIME FORCE PROTECTION UNIT BANGOR WA

CUI
F-4 Appendix F
CUI
OPNAVINST 3100.6K
10 Aug 2021

(3) Additional addresses to be considered:

NAVY JAG WASHINGTON DC


CMC WASHINGTON DC (USMC personnel or mission incidents)
SOPA
Appropriate U.S. Coast Guard District

(4) Additional addresses to be considered for all SSBNs, fleet and shore installations that
support the nuclear deterrence program:

DIRSSP WASHINGTON DC (for all SSBNs, fleet and shore installations that support
the nuclear deterrence program)
HQMC DC PPO (PS)
CTF 114.3
CTF 114.4
CTF 114
JFMCC STRAT
COMMARFORCOM
OFFUTT AFB NE//J3/J31/J38//
MCSF REG
COMDT COGARD WASHINGTON DC
COGARD MARITIME FORCE PROTECTION UNIT KINGS BAY GA
COGARD MARITIME FORCE PROTECTION UNIT BANGOR WA

(5) For personnel incident reports, use the addresses and format listed in appendix B.

(6) Message body:

MSGID/OPREP-3, USMTF, YYYY/USS SHIP/001//


FLAGWORD/NAVY UNIT SITREP SENTINEL/-//
TIMELOC/110429ZMAY2009/4050N13235E/INIT//
GENTEXT/INCIDENT IDENTIFICATION AND DETAILS/
1. INCIDENT: SUSPICIOUS OBSERVATION OF PERIMETER SECURITY
2. DATE OF INCIDENT: 11MAY2009
3. TIME OF INCIDENT: 0128L
4. LOCATION OF INCIDENT: NAVSTA NORFOLK, VA
5. INCIDENT: MALE SUSPECT SEEN BY BASE SECURITY OBSERVING
NAVSTA NORFOLK GATE 4. SUSPECT DEPARTED THE SCENE PRIOR TO
LOCAL LE ARRIVAL. INCIDENT UNDER INVESTIGATION BY NCIS AND
LOCAL AUTHORITIES.

CUI
F-5 Appendix F
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX G – ACRONYMS

Acronyms Meaning
AA&E ARMS, AMMUNITION & EXPLOSIVES
ADMITS ALCOHOL AND DRUG MANAGEMENT INFORMATION
TRACKING SYSTEM
AMPN AMPLIFICATION
AOR AREA OF RESPONSIBILITY
ATFP ANTITERRORISM AND FORCE PROTECTION
BAC BLOOD ALCOHOL CONTENT
BWC BATTLE WATCH CAPTAIN
C CONDITIONAL (USMTF DATA SET OCCURRENCE)
CCS COMMAND CLIMATE SPECIALIST
CDO COMMAND DUTY OFFICER
CHINFO CNO CHIEF OF INFORMATION
CJCS CHAIRMAN, JOINT CHIEFS OF STAFF
CJCSM CHAIRMAN, JOINT CHIEFS OF STAFF MANUAL
CMDAUTH COMMAND AUTHORITY
CNIC COMMANDER, NAVY INSTALLATIONS
CNO CHIEF OF NAVAL OPERATIONS
CO COMMANDING OFFICER
COCOM COMBATANT COMMANDER
COMFIFTHFLT COMMANDER, FIFTH FLEET
COMNAVSAFECEN COMMANDER, NAVAL SAFETY CENTER
COMPACFLT COMMANDER, U.S. PACIFIC FLEET
COMUSFLTFORCOM COMMANDER, U.S. FLEET FORCES COMMAND
COMUSNAVAF COMMANDER, U.S. NAVAL FORCES AFRICA
COMUSNAVCENT COMMANDER, U.S. NAVAL FORCES CENTRAL
COMMAND
COMUSNAVEUR COMMANDER, U.S. NAVAL FORCES EUROPE
COMUSNAVSO COMMANDER, U.S. NAVAL FORCES SOUTH
COOP CONTINUITY OF OPERATIONS PLAN
CORR CORRECTION
CTF COMBINED TASK FORCE
CTG COMBINED TASK GROUP
CRITIC CRITICAL INFORMATION
DAR DRUG AND ALCOHOL ABUSE REPORT
DECL MESSAGE DOWNGRADING AND DECLASSIFICATION
DATA
DESC DESCRIPTION
DISA DEFENSE INFORMATION SYSTEMS AGENCY
DMS DEFENSE MESSAGING SYSTEM
DoD DEPARTMENT OF DEFENSE

CUI
G-1 Appendix G
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX G – ACRONYMS

Acronyms Meaning
DON DEPARTMENT OF THE NAVY
DSN DEFENSE SWITCHED NETWORK
DSRN DEFENSE SWITCHED RED NETWORK
DTG DATE AND TIME GROUP
DUI DRIVING UNDER THE INFLUENCE
DWI DRIVING WHILE INTOXICATED
EA EMERGENCY ACTION
EAM EMERGENCY ACTION MESSAGE
ES ELECTRONIC SPILLAGE
EO EQUAL OPPORTUNITY
EVACTO EVACUATION INFORMATION
EVTYP EVENT TYPE
EXER EXERCISE IDENTIFICATION
EXORDS EXECUTION ORDERS
FAR FAMILY ADVOCACY REPRESENTATIVE
FLAGWORD FLAGWORD INFORMATION
FMF FLEET MARINE FORCE
FOLUP FOLLOW UP
FP FORCE PROTECTION
FRD FORMERLY RESTRICTED DATA
FSBS FIXED SUBMARINE BROADCAST SYSTEM
FWO FLEET WATCH OFFICER
GCCS GLOBAL COMMAND AND CONTROL SYSTEM
GCMA GENERAL COURTS MARTIAL AUTHORITY
GENTEXT GENERAL TEXT
IA INDIVIDUAL AUGMENTEE
INFO INFORMATION
INIT INITIAL
ISIC IMMEDIATE SUPERIOR IN COMMAND
JAG JUDGE ADVOCATE GENERAL
JTF JOINT TASK FORCE
JWICS JOINT WORLDWIDE INTELLIGENCE
COMMUNICATION SYSTEM
J3 JOINT STAFF OPERATIONS DIRECTORATE
KTS KNOTS
LANT ATLANTIC
LANTFLT ATLANTIC FLEET
LAT LATITUDE
LONG LONGITUDE
LERTCON ALERT CONDITIONS

CUI
G-2 Appendix G
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX G – ACRONYMS

Acronyms Meaning
M MANDATORY (USMTF DATA SET OCCURRENCE)
MLSR MISSING, LOST, STOLEN OR RECOVERED
mm MILLIMETER
MOC MARITIME OPERATIONS CENTER
MPO MILITARY PROTECTIVE ORDER
MSC MILITARY SEALIFT COMMAND
MSGID MESSAGE IDENTIFICATION
MTF MESSAGE TEXT FORMAT
NARR NARRATIVE
NAS NAVAL AIR STATION
NAVADMIN NAVAL ADMINISTRAION MESSAGE
NAVCRIT NAVY COMPUTER NETWORK INCIDENT RESPONSE
TEAM
NAVNETWARCOM NAVAL NETWORK WARFARE COMMAND
NAVSAFECENT NAVAL SAFETY CENTER
NCIS NAVAL CRIMINAL INVESTIGATION SERVICE
NC3 NUCLEAR COMMAND, CONTROL AND
COMMUNICATIONS
NAVWARSYSCOM NAVAL INFORMATION WARFARE SYSTEMS
COMMAND
NIPRNET NONSECURE INTERNET PROTOCOL ROUTER
NETWORK
NM NAUTICAL MILES
NMCC NATIONAL MILITARY COMMAND CENTER
NMCI NAVY MARINE CORPS INTRANET
NMFS NATIONAL MARINE FISHERIES SERVICE
NMMSRT NATIONAL MARINE MAMMAL STRANDING
RESPONSE TEAM
NNSA NATIONAL NUCLEAR SECURITY ADMINISTRATION
NNWC NAVAL NETWORK WARFARE COMMAND
NOAA NATIONAL OCEANOGRPHIC AND ATMOSPHERIC
ADMINISTRATION
NOAA FISHERIES NATIONAL OCEANOGRAPHIC AND ATMOSPHERIC
ADMINISTRATION NATIONAL MARINE FISHERIES
SERVICE
NOC NAVY OPERATIONS CENTER
NOCWO NAVY OPERATIONS CENTER WATCH OFFICER
NUC NUCLEAR
NUCCRS NUCLEAR COURSE, RATE AND SPEED
NUCLOC NUCLEAR DETONATION LOCATION

CUI
G-3 Appendix G
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX G – ACRONYMS

Acronyms Meaning
NUCTM NUCLEAR WEAPON TIME ON TARGET
NUCTYP NUCLEAR WEAPON TYPE
NUDESTSUM NUCLEAR DETONATION SUMMARY REPORT
NWP NAVAL WARFARE PUBLICATION
N411 LOGISTICS – SUPPLY CHAIN OPERATIONS,
ORDNANCE MANAGEMENT BRANCH
O OPTIONAL (USMTF DATA SET OCCURRENCE)
OCA ORIGINAL CLASSIFICATION AUTHORITY
OCC OCCURRENCE
OCONUS OUTSIDE THE CONTINENTAL UNITED STATES
ONI OFFICE NAVAL INTELLIGENCE
ONR OFFICE OF NAVAL RESEARCH
OPER OPERATION IDENTIFICATION DATA
OPNAV OFFICE OF THE CHIEF OF NAVAL OPERATIONS
OPNAVINST OFFICE OF THE CHIEF OF NAVAL OPERATIONS
INSTRUCTION
OPREP OPERATIONAL REPORT
PAC PACIFIC
PAO PUBLIC AFFAIRS OFFICER
PID PERSONNEL INJURY OR DEATH
PLAD PLAIN LANGUAGE ADDRESS DESIGNATOR
POC POINT OF CONTACT
PROFORMA PRE-FORMATTED
RD RESTRICTED DATA
REF REFERENCE
RMKS REMARKS
ROC REGIONAL OPERATIONS CENTER
ROE RULES OF ENGAGEMENT
SAP SPECIAL ACCESS PROGRAM
SAR SEARCH AND RESCUE
SATHICOM SATELLITE HIGH COMMAND NETWORK
SECDEF SECRETARY OF DEFENSE
SECNAVINST SECRETARY OF THE NAVY INSTRUCTION
SEQ SEQUENTIAL
SETID SET IDENTIFICATION
SIC SUBJECT IDENTIFIER CODE
SIC SUPERIOR IN COMMAND
SIPRNET SECRET INTERNET PROTOCOL ROUTER NETWORK
SITREP SITUATION REPORT
SM STATUTE MILES

CUI
G-4 Appendix G
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX G – ACRONYMS

Acronyms Meaning
SOPA SENIOR OFFICER PRESENT-ASHORE or AFLOAT
SSBN SHIP, SUBMERSIBLE, BALLISTIC, NUCLEAR
SSN SHIP, SUBMERSIBLE, NUCLEAR
SWOP SPECIAL WEAPONS ORDNANCE PUBLICATION
SYSCOM SYSTEM COMMAND
TACON TACTICAL CONTROL
TELCON TELEPHONE CONFERENCE
TIMELOC EVENT TIME AND POSITION
UAS UNMANNED AERIAL SYSTEM
UCMJ UNIFORM CODE OF MILITARY JUSTICE
UIC UNIT IDENTIFICATION CODE
UNK UNKNOWN
USS UNITED STATES SHIP
USMTF UNITED STATES MESSAGE TEXT FORMAT
USSTRATCOM UNITED STATES STRATEGIC COMMAND
UTM UNIVERSAL TRANSVERSE MERCATOR

CUI
G-5 Appendix G
CUI
OPNAVINST 3100.6K
10 Aug 2021

APPENDIX H - GLOSSARY OF TERMS

Term Definition
Alphabetic Character One of the letters from A to Z.
Alphanumeric Character A combination of alphabetic or numeric characters.
Alternative Content Field A field offering a choice between two or more
specified field formats.
Alternative Field Prefix A combination of a letter and a colon which may
precede a field content to identify the alternative
chosen from two or more specified field formats.
Amplification Set A Free-Text set (set identifier AMPN) that is used to
insert an explanation of additional information
concerning only the preceding set.
Blank Character See "Space Character."
Character A letter, digit or other symbol that is used to represent
data.
Columnar Set A formatted set having an ordered collection of data
aligned vertically under a horizontal array of Column
Headers.
Column Header A keyword that describes the type of information
contained within a column of a Columnar Set.
Composite Field A field, comprised of two or more subfields, the
content of which represents a chain or linked data
items.
Composite Field Format A field format comprised of two or more subfield
formats that specify the sequences of character types
required to complete a composite field.

Data Base A collection of data, or a part of the whole of another


collection of data, consisting of at least one file, that is
sufficient for a given purpose or for a given data
processing system.
Data Chain The combination of two or more data elements linked
together in a specified order for a particular purpose or
use.
Data Code A number, letter or symbol or any combination
thereof, used to represent a data item of a data element.
Data Element A class (or unit) of information that has a unique
meaning. The members (or subunits) of the class are
data items.

CUI
H-1 Appendix H
CUI
OPNAVINST 3100.6K
10 Aug 2021

Data Entry (DE) Column A two-digit data field within a selected Columnar set
used to relate data lines (1) with data lines within
another Columnar set or (2) with amplifying
information contained in Free-Text sets in the same
message.
Data Item A subunit of information within a class of data (data
element). Each data item has some unique feature that
distinguishes it from other data items classified under
the same data element. However, each data item also
has characteristics, conditions or properties that
determine the class, i.e., the data element of which it is
a member.
Delimiter A character (normally a space or special character)
used to provide separation and distinction between two
linked data codes.
End-of-Set Marker Two consecutive slant symbols (//) that terminate a set.
Extended Special Character Explanation point (!), at symbol (@), number symbol
(#), dollar sign ($), percent sign (%), caret (^),
ampersand (&), asterisk (*), equal sign (=), underscore
(_), plus sign (+), left bracket([), right bracket(]), left
brace({), right brace(}), backward slant(\), quote (“),
apostrophe(‘), semi-colon (;), less than symbol (<),
greater than symbol (>), tilde (~), vertical bar(|) and
backward accent(/). Lower case letters (a-z) are also
allowable. (Also see Special Character).
Field An area within a set designated for the entry of
characters.
Field Content A combination of characters which represents either a
specific data item or a chain of linked data items
Field Descriptor A keyword (which may be a word, an abbreviation or
an acronym) composed of one to eight alphanumerics
that, when used, describes the type of information in a
field of a set.
Field Marker A slant symbol (/) that is used to indicate the start of a
field.
Fixed-Length Field Format A field format that requires an invariable (fixed)
number of characters.
Formatted Message A message in which the text is organized in a
predetermined sequence of standard formatted
subdivisions, suitable for human and automatic
interpretation and processing.

CUI
H-2 Appendix H
CUI
OPNAVINST 3100.6K
10 Aug 2021

Free-Text Set A set having the set identifier AMPN, GENTEXT,


NARR or RMKS and containing a Free-Text field
format of unlimited length.
General Text A Free-Text set (set identifier GENTEXT) consisting
of one formatted field and one Free-Text field, used to
introduce specific information that is not directly
related to one or more formatted sets of a message.
Group of Fields A collection of fields at the end of a set format
designated to enable its repetition as a group.
Header Line The second line of a columnar set. It contains
appropriately spaced column headers separated by
field markers.
Keywords Message Identifiers, Set Identifiers, Field Descriptors
or Column Headers that identify specific messages,
sets or the type of information contained in fields or
subfields. They assist both the human and computer in
understanding and in processing messages.
Left-Justify To position data within the space allocated so that the
first data character occupies the left-most character
position of the field or subfield.
Line A horizontal array of not more than 69 characters.
Linear Set A formatted set having an ordered collection of data
fields presented in a horizontal manner.
Mandatory The occurrence categorization of those field formats
and set formats which are related to essential
information.
Message Text That part of a message that contains the information to
be conveyed. It is comprised of introductory, main and
closing text sections.
Message Text Format (MTFs) Structured PROFORMA messages in keyword format
using alphanumeric, special and blank characters
suitable for both human and machine use. MTFs may
be transmitted over a variety of communication link
types, including digital data links.
Narrative Set A Free-Text set (set identifier NARR) used to insert an
explanation or additional information concerning two
or more immediately preceding sets.
Nested Segment A segment embedded in another, larger segment or
nested segment.
Numeric Character One of the digits from 0 to 9.

CUI
H-3 Appendix H
CUI
OPNAVINST 3100.6K
10 Aug 2021

Occurrence Category The class assigned to field formats and set formats that
determine whether the formats are to be included in the
message text. Occurrence categories are mandatory,
operationally determined or conditional.
Operationally Determined The occurrence categorization of those field formats
and set formats, related to information, which,
although pertinent, is not essential. Inclusion of
operationally determined set or field information is
operationally determined by the message drafter.
Remarks Set A Free-Text set (set identifier RMKS) used to insert an
explanation or additional information concerning the
entire message.
Right-Justify To position data within the space allocated so that the
last data character occupies the right-most character
position of the field or subfield (applies only to
columnar sets).
Sectioning A communications system procedure to limit
transmission times by breaking a lengthy message into
numbered sections.
Segment A group of set formats related by their content that is
designated in a message format to enable its repetition
as a group.
Set A predetermined field or sequence of fields, preceded
by a Set Identifier, containing all the required
information concerning an aspect of the subject
addressed by a formatted message.
Set Format A unique set format identifier followed by specified
sequence of one or more field formats.
Set Identifier (Columnar Set) One numeric followed by two to seven alphabetic
characters used as a key to the structure of a columnar
set.
Set Identifier (Linear and Free-Text Three to eight alphabetic characters used as a key to
Sets) the structure of a linear or free-text set.
Space Character A normally nonprinting character. Same as a blank
character.
Special Character A graphic character that is not a letter nor a number
nor a space character. Allowable special characters for
USMTF messages are: . , : - / ( ) ? (Also see extended
character).
Subfield An area within a composite field designated for the
entry of specified information (data code).
Subfield Content A combination of characters that represent a specific
data item.

CUI
H-4 Appendix H
CUI
OPNAVINST 3100.6K
10 Aug 2021

Subfield Format A field format that is used as part of a composite field


format.

Variable Length Field Format A field format that allows use of a variable number of
characters within prescribed limits.

CUI
H-5 Appendix H

You might also like