Operations Event Incident Reporting
OPREP-3 PINNACLE and National-Level Interest Reporting
Submit OPREP-3 PINNACLE reports to the National Military Command Center (NMCC) within 15 minutes of awareness for events at the national-level interest threshold per MCO 3504.2A.
T&R Event Details
- Event Code
- 0102-OPER-1101
- Source Policy
- MCO 3504.2A
- MOS Performing
- 0102, 0111, 0170
- Grades
- GySgt, MSgt, MGySgt
- Sustainment Interval
- 12 months
- Evaluation-Coded
- No
- Readiness-Coded
- No
Role and responsibility
The unit watch officer or operations duty officer owns the OPREP-3 PINNACLE synchronous voice report at the moment of event awareness. The commander assesses the national-level interest threshold. The S-3 operations staff drafts the asynchronous message report within the 1-hour timing window. The S-1 officer and adjutant support records retention.
Source documents flow from the event or incident notification, the duty officer report, the commander assessment of national-level interest, the Enclosure 1 OPREP-3 PINNACLE flag word matrix, and the Enclosure 3 NMCC contact information. Outputs include the synchronous voice report log, the OPREP-3 PINNACLE message report, the supplemental reports, and the retained record per SECNAV M-5210.1.
OPREP-3 PINNACLE is the highest-priority OPREP-3 report category. The 15-minute synchronous timing window applies from the moment of event awareness. Reports route directly to NMCC, bypassing the MCOC.
Trigger events
- Nuclear weapons accident, incident, or significant deficiency.
- Loss of nuclear weapons custody or unauthorized nuclear weapons handling.
- Outbreak of war between major powers.
- Significant US military operation or imminent military operation.
- Loss of a major weapon system with national-level implications.
- Significant terrorism event with national-level implications.
- Other event meeting the national-level interest threshold per MCO 3504.2A.
OPREP-3 PINNACLE flag words
OPREP-3 PINNACLE reports use specific flag words tied to event type per MCO 3504.2A Enclosure 1:
- OPREP-3 PINNACLE (OPREP-3P). Immediate notification of any incident or event where national-level interest is determined.
- OPREP-3 PINNACLE LERTCON STATUS OF ACTIONS. Alert condition status report.
- OPREP-3 NUCFLASH. Nuclear weapons accident or incident.
- OPREP-3 PINNACLE LERTCON. Alert condition declaration.
- OPREP-3 OPSCRITICAL. Operational critical event.
Flag words drive the routing priority and the addressee list. Use the correct flag word per the Enclosure 1 matrix.
Processing workflow
- Identify the national-level interest. The commander assesses the event against the national-level interest threshold per MCO 3504.2AMCO 3504.2A Paragraph 3c(1).
- Determine the OPREP-3 PINNACLE flag word. Match the event type against the Enclosure 1 flag word matrix.
- Submit the synchronous voice report to NMCC. The unit watch officer calls NMCC via the voice number in Enclosure 3 within 15 minutes of awareness per MCO 3504.2AMCO 3504.2A.
- Submit the synchronous chat report (secondary method). Broadcast on the NMCS command net chat room on DISA Defense Connect Online Jabber Chat via the SIPR network as a backup or supplementary synchronous channel.
- Draft the OPREP-3 PINNACLE message. Use the standard OPREP-3 message format with the flag word in the identification line per MCO 3504.2A.
- Apply Joint Reporting Structure addressing. Include NMCC, the affected combatant command, and the appropriate Service operations centers per Enclosure 1.
- Route the message report. Submit within the 1-hour asynchronous timing window per MCO 3504.2AMCO 3504.2A Enclosure 1.
- Submit supplemental reports. Supplemental reports update or correct the initial report. Submit as required to keep NMCC and the combatant command informed.
- Coordinate with the Marine Corps Operations Center (MCOC). Notify MCOC of the PINNACLE report routing for HQMC awareness.
- Retain the record. Archive the OPREP-3 PINNACLE report per SECNAV M-5210.1 and NAVMC DIR 5210.11E records retention rules.
Systems of record and forms
Systems
- National Military Command Center (NMCC). OPREP-3 PINNACLE receiving authority.
- Marine Corps Operations Center (MCOC). HQMC awareness channel for PINNACLE reports routed by Marine Corps units.
- NMCS command net chat room on DISA Defense Connect Online Jabber Chat (SIPR). Backup synchronous channel.
- Combatant command operations centers. Information addressees per Enclosure 1.
Forms
- OPREP-3 PINNACLE Message. The standard OPREP-3 message format with the PINNACLE flag word.
- Voice Report Log. Local log capturing the synchronous voice report content and time.
- Enclosure 1 OPREP-3 Reporting Requirements Matrix. Flag word matrix.
- Enclosure 3 OPREP-3 Reporting Contact Information.
Common pitfalls
- 15-minute window missed. The initial voice report exceeds the 15-minute timing per MCO 3504.2AMCO 3504.2A. Submit the voice report at the moment of awareness with the information on hand.
- Wrong flag word applied. The OPREP-3 PINNACLE routing fails to align with the event type. Match the event against the Enclosure 1 flag word matrix before submission.
- MCOC unnotified on PINNACLE routing. HQMC loses awareness on the Marine Corps unit PINNACLE submission. Notify MCOC after the NMCC voice report.
- Synchronous chat used instead of voice. Voice is the primary synchronous channel. Use chat as backup per Paragraph 4a(2)(a)1.
- National-level interest threshold under-assessed. The commander treats a significant incident as SIR when it meets PINNACLE criteria. Apply MCO 3504.2A thresholds (originally derived from CJCSM 3150.03D) at the commander assessment.
Decision points
- National-level interest determination. The commander assesses the event against MCO 3504.2A thresholds (originally derived from CJCSM 3150.03D). When in doubt, escalate to PINNACLE rather than SIR per MCO 3504.2AMCO 3504.2A "when in doubt, submit a report" framing.
- Flag word selection. Match the event type against the Enclosure 1 matrix. NUCFLASH, OPSCRITICAL, and LERTCON have distinct trigger criteria.
- Sister Service operational control PINNACLE routing. When operating under a sister Service component headquarters, route PINNACLE per Paragraph 5d with CMC WASHINGTON DC PPO as an information addressee.
Authority
This sub-page maps to NAVMC 3500.3E T-R event 0102-OPER-1101 Supervise Operations Event Incident Reporting. The processing workflow sits under MCO 3504.2AMCO 3504.2A Paragraph 3c(1) Reports to the National Military Command Center and Enclosure 1 OPREP-3 Reporting Requirements, CJCSM 3150.01B Joint Reporting Structure General Instructions, and CJCSM 3150.03D Joint Reporting Structure Event and Incident Reports (superseded, no direct successor in the 3150 series, current Marine Corps source is MCO 3504.2A). SECNAV M-5210.1 governs records retention.
Related references
- MCO 3504.2A Operations Event/Incident Report (OPREP-3) Reporting. Primary order.
- CJCSM 3150.01B Joint Reporting Structure General Instructions.
- CJCSM 3150.03D Joint Reporting Structure Event and Incident Reports (superseded, no direct successor in the 3150 series, current Marine Corps source is MCO 3504.2A). Flag word rules.
- SECNAV M-5210.1 DON Records Management Manual.
- NAVMC DIR 5210.11E Marine Corps Records Management Program.
Same topic, other roles
References
Related Pages
- Admin
Operations Event/Incident Reporting (OPREP-3) - S-1 Procedural Page
same topic - same function - MCO 3504.2A - same T&R event - 3 shared references
- Admin
OPREP-3 SIR Serious Incident Reporting
same topic - same function - MCO 3504.2A - same T&R event - 2 shared references
- Admin
Sister Service OPREP-3 and WHITE PINNACLE Exercise
same topic - same function - MCO 3504.2A - same T&R event - 2 shared references
- Admin
Reportable Events and Incidents (Enclosure 2)
same topic - same function - MCO 3504.2A - same T&R event
- Admin
Sexual Assault and Hazing Report Protocol
same topic - same function - MCO 3504.2A - same T&R event