AARO-23-F-1423 — FOIA: Joint Staff GENADMIN message on UAP reporting procedures
File AARO-23-F-1423 is a declassified pdf from AARO. This page carries the original file, its official summary and its full text.
- File
- AARO-23-F-1423
- Agency
- AARO
- File type
Open original file · AARO.MIL page
TL;DR
May 23, 1914522—so futuristic they needed a time‑travel clause.
- FOIA Joint Staff GENADMIN message, Joint Staff J3, Washington D.C., May 23, 1914522, AARO pdf
- Outlines UAP reporting templates, counterintelligence routing, data transfer to AARO, defines UAP detections
- No official conclusion in the file
AI summary
A Joint Staff GENADMIN message outlines procedures for reporting Unidentified Anomalous Phenomena (UAP) worldwide. It directs Combatant Commands and Services to use standardized templates, notify counterintelligence elements, and transfer UAP data and materials to AARO. The document defines terms related to UAP, including objects, incidents, and reporting procedures, and specifies required data such as detection times, locations, and observer details. It outlines deadlines for submitting reports and includes templates for standardized UAP incident documentation. The text also describes UAP reporting procedures for military commands, including documentation requirements, chain of custody, and data transfer protocols, with tasks for commanders and deadlines for reporting UAP incidents. The message was issued by the Joint Staff and includes contact information for AARO.
Full text
Page 1
PAGE 1 OF 9
Unidentified Anomalous Phenomena Reporting and Material
Disposition GENADMIN
Originator: JOINT STAFF J3 WASHINGTON DC//J36 Homeland Defense Division
Office: J36 Homeland Defense Division
DTG: 1914522 May 23
Pree: Routlne
CNO WASHINGTON DC, HQDA CSA WASHINGTON DC, CSAF WASHINGTON DC, CMC CMC WASHINGTON DC, COMDTCOGARD
WASHINGTON DC, CDR USCENTCOM MACDlll AFB FL, CDR USAFRICOM STUTTGART GE, CDR USNORTHCOM PETERSON AFB CO, CDR
To: USPACOM HONOLULU HI , HQ USSPACECOM COLORADO SPRINGS CO, CDR USEUCOM VAIHINGEN GE, CDR USSOUTHCOM MIAMI Fl,
CDR USTRANSCOM SCOTT AFB IL, CDR USSTRATCOM OFFUTT AFB NE, USCYBERCOM FT GEORGE GMEADE MD, CDR NORAD PETERSON
AFB CO, JOINT STAFF DJ2 WASHINGTON DC, JOINT STAFF DB WASHINGTON DC, JOINT STAFF DJS WASHINGTON DC, JOINT STAFF DJS
WASHINGTON DC, OSD ASO HOMELAND DEF AND GLOBAL SEC WASHINGTON OC
CC: OSD USO INTEL WASHINGTON DC
SUBJ / Unidentified Anomalous Phenomena Reporting and Material
Disposition
GENADMIN//MSGID/ORDER/CJCS//
REF/A/ MEMO/DEPSECDEF/1SJUL22//
REF/8/ MEMO/USD{l&S )/20JUL22//
REF/C/MSG/OCS/172100ZDEC21//
REF/D/DOC/DOODS-3325.01/30DEC11//
REF/E/DOC/DOOI5200.39/ 10CT20//
REF/F/ DOC/ DOOD5148.13/ 26APR17//
REF/G/MEMO/USO{I&S)AARO/ UNDATEO//
APN/(U) REF A is the Deputy Secretary of Defense Memorandum for
Senior Pentagon Leadership, Commanders of the Combatant Coffllllands
(CCMDS), and Defense Agency and DoD Field Activity Directors
directing establishment of the All-domain Anomaly Resolution Office
(AARO) to detect, identify, attribute and -as necessary-mitigate
anomalous and unidentified spaceborne, airborne, seaborne, and
transmedium objects.
REF Bis the Under Secretary of Defense for Intelligence and Security
Memorandum for Senior Pentagon Leadership, Convnanders of the
Combatant Co11mands, and Defense Agency and OoD Field Activity
Directors that establishes AARO and its lines of efforts as including
surveillance, collection, and reporting; systems capabilities and
design; intelligence operations and analysis; mitigation and defeat;
governance; and science and technology .
REF C is the EXORO message that directs CCMOs and Services to report
small unmanned aircraft systems (sUAS) incidents, incursions, and
engagements worldwide.
REF o is t he 000 Directive for Foreign Materiel Program (FMP) and is
a controlled document.
REF Eis the 000 Instruction for Critical Program Information (CPI)
Identification and Protection Within Research, Development, Test, and
Evaluation ( RDT&E). This document reissues DoDI 5200.29 in accordance
with authorities in DoDI 5143 .01 and DoDD 5134 .01; establishes policy
and assigns responsibilities for the identification and protection of
CPI; establishes policy in accordance with DoDD 5000.01 and DoOI
5000.02; and incorporates and
Page 2
PAGE 2 OF 9
cancels the Under Secretary of Defense for Acquisition, Technology,
and Logistics memorandum.
REFF is the 000 Directive for Intelligence Oversight that
establishes polices, assigns responsibilities, and provides
procedures for identifying, investigating, and reporting
questionable intelligence activities and significant or highly
sensitive matter; describes
functions, relationships, and authorities of the DoD Senior
Intelligence Oversight Official; and prescribes responsibilities and
relationships of the Under Secretary for Intelligence, the General
Counsel of the DoD, and the DoD Component heads regarding
intelligence oversight.
ORDTYP/GENADMIN/CJCS//
NARR/ (U) This Joint Staff J3 GENADMIN message provides guidance to
CCMDs and Services 1) to report UAP worldwide, using the reporting
template standards as prescribed below; 2) to report UAP to their
respective counterintelligence element; and 3) to transfer UAP and
UAP-related material to AARO. This GENAOMIN is effective
immediately.
GENTEXT/SITUATION/1. (CUI) The US Government has observed UAP in or
near the territory and/or operating areas of the United States, of
its allies, and of its adversaries, and observing, identifying, and
potentially mitigating UAP has become a growing priority for us
policymakers, laWllakers, and warfighters. The potentially ubiquitous
presence of UAP defines the national security implications of those
anomalies, which range from operational hazards and threats to
technological and intelligence surprise to adversaries' strategic
miscalculations. It is imperative that DoD provide UAP incident,
incursion, and engagement-as defined in paragraph 3.B . - reporting,
data, and material for the Department's detection and mitigation of
potential threats; exploitation of advanced technologies; and
informing policymaker and warfighter decisions. The Chairman of the
Joint Chiefs of Staff (CJCS) sets the appropriate Chairman's
Critical InforMation Requirement (CCIR) criteria and ensures each
CCMD and Service is in receipt of the Reporting Matrix. Incursions,
incidents, and engagements that meet CCIR criteria are reported in
accordance with CJCS and CCMO reporting requirements. Each CCMD and
Service ensures the appropriate guidance is in place to receive the
respective reports from Service Component Commands and subordinates.
GENTEXT/MISSION/2,
2.A. (CUI) CCMOs and Services report all UAP incidents, incursions,
and engagements using the below, standardized reporting requirements
and templates; transfer all data from UAP incidents , incursions, and
engagements, as described; and recover and transfer all UAP objects
and materials, as described. Additionally, all CCMOs and Services
notify thei r counterintelligence element of UAP events, in
accordance with their respective counterintelligence reporting
r equirements.
2.8 . {CUI) Incidents, incursions, and engagements by identifiable,
non-anomalous phenomena (e .g., sUAS and other capabilities or
materials that do not exceed known or predicted performance
envelopes) continue to be reported through established processes and
mechanisms.
Page 3
PAGE 3 OF 9
REF c provides i nstructions to CCMOs and Services for reporting sUAS
2.C. (CUI) Recovery and transfer of identifiable, non-anomalous
items of foreign origin that have military potential or applications
continue to be managed by the DoD FMP. REF D provides
responsibilities for the management and operation of the DoD FMP.
GENTEXT/EXECUTION/3.
3.A. (U) CONCEPT OF OPERATIONS
3.A.l. (CUI) Respective subordinates of DoO, CCMDs, and Services
will r eport all observed UAP incidents, incursions, and engagements
to AARO, through their respective Combatant Co1M1and Joint Operations
Center and Service Watch Cells. AARO receives, databases, and
analyzes UAP reporting, and AARO provides stakeholders its peer
reviewed analytic conclusions.
3,A.2. (CUI) Respective subordinates of DoD, CCMDs, and Services
send notification of all UAP incidents, incursions, and engagements
to their respective counterintelligence elements.
3.A.3. (CUI) Respective subordinates of DoD, CCMDs, and Services
coordinate with AARO to determine the appropriate location and
entity to transfer all UAP data for incidents, incursions, and
engagements in raw, unedited, unmodified form and in a manner
consistent with the data's classification.
3.A.4. (CUI) Respective subordinates of DoD, CCMOs, and Services
coordinate with AARO to determine the appropriate location(s) and
entities to transfer all UAP objects and material of incidents,
incursions, and engagements in un~odified form, in a manner
consistent with the objects' and materials' classification and
applicable hazardous-materials transport requirements .
3.A.5. (CUI) AARO coordinates across the US Government to identify
the appropriate agency to assist in shipping, transferring,
receiving, storing, examining, etc., of material and data associated
with the UAP incident.
3.8. (U) DEFINITIONS
3.8.1. (U) UNIDENTIFIED ANOMALOUS PHENOMENA (UAP) are sources of
anomalous detections in one or more domain (i.e., airborne,
seaborne, spacebor ne, and/or transmedium) that are not yet
attributable to known actors and that demonstrate behaviors not
readily understood by sensors or observers. "Anomalous detections"
include but are not limited to phenomena that demonstrate apparent
capabilities or material t hat exceed known performance envelopes. A
UAP may consist of one or more unidentified anomalous objects and
may persist over an extended period of time.
3.8.1.A. (U) SPACEBORNE UAP are sources of anomalous detections
above the Karman Line (i.e., 100km above Earth's mean sea level).
3.8.1.8. (U) AIRBORNE UAP are sources of anomalous detections
between Earth's mean sea level and the Karman Line.
3.8.1.C. (U) SEABORNE UAP are sources of anomalous detections at or
below Earth's mean sea level.
3.8.1.D. (U) TRANSMEOIUM UAP are sources of anomalous detections
that transit more than one domain.
Page 4
PAGE 4 OF 9
3.8.2. (U) UAP OBJECTS are corporeal artifacts of unidentified
anomalous phenomena. UAP may contain one or more UAP objects (e.g.,
airborne craft exhibiting apparent an0111alous capabilities) . UAP
material are samples, in whole or in part, of UAP objects (e . g . ,
debris).
3.8.3. {U) UAP DATUM is any record of UAP detection, observation,
identification, effects (on persons or equipment), mitigation, and
material-exploitation. UAP datum includes but is not limited to
observer, debri efer, and investigator notes and reports; still
photographs and full-motion video; audio recordings; and platform
and sensor- instrument recordings.
3.8.4.A. (U) A UAP INCIDENT is any occurrence where UAP is detected
by persons or sensors.
3.8.4.8. (U) A UAP INCURSION is any UAP incident in, on, or near US
military installations, operating areas, training areas, special use
airspace (SUA), proximity operations, and/or other areas of
interest. Other areas of interest include but are not limited to US
critical infrastructure and national defense equities of Allied
military and intelligence coalitions (e.g., FIVE EYE).
3.8.4.C. (U) A UAP ENGAGEMENT is a kinetic or non-kinetic response
to a UAP, intended to deny, disrupt, or destroy the phenomenon and/
or its object{s).
3.B.5. {U) A UAP INTERROGATION is the elicitation of UAP location,
capabilities , characteristics, and/or intent using passive and/or
active sensing capabilities-including but not limited to electro?
optical/imagery, infrared/thermal, radiofrequency/radar,
light/laser/lidar/ladar, electromagnetic, gravitational, and
radioactive means.
3.8.6. (U) UAP ATTRIBUTION is the assessed natural or artificial
source of the phenomenon and includes solar, weather, tidal events;
US government, scientific, industry, and private activities; and
foreign (allied or adversary) government, scientific, industry, and
private activities.
3.B.7. (U) A UAP HAZARD is a safety risk to persons, materiel, or
information (e.g., from collision) by UAP that do not demonstrate
hostile intent.
3.8.B. {U) A UAP THREAT is a force-protection and/or national
security risk to persons, materiel, or information by UAP that
demonstrate hostile intent.
3.B.9. {U) A UAP-REACTION is the apparent UAP response to stimuli,
including but not limited to UAP detection, observation,
interrogation and/or engagement .
3.8.18. (U) DATE(S) OF DETECTION is the period when t he UAP was
detected by persons and/or sensors.
3.8.11. {U) DATE OF ACQUISITION is the date when the UAP data and/or
material was made available to the reporting element. When the
reporting element, itself, detects the UAP, then the date of
detection corresponds with the date of acquisition.
3.C. {U) UAP REPORTING
3.C.1. {U) UAP INCIDENT AND INCURSION REPORTS are completed and
securely transmitted to Combatant Command Joint Operations Centers
and Service Watch Centers no later than 96 hours after the event.
Details of UAP-related health incidents (e.g., physiological,
psychological effects and whether persistent or transitory) will be
retained in service members' medical records but shall not/not be
transmitted with the UAP report .
3.C.2. (U) UAP ENGAGEMENT REPORTS are completed and securely
transmitted to Combatant Command Joint Operations Centers and
Service
Page 5
I
CUI
PAGES OF 9
Watch Centers no later than 12 hours after the event or upon receipt
of report from Allied/ Partner/Host nation.
3.C.3. (U) The below template will be used to report UAP incidents,
incursions, and engagements (• denotes a required response, and••
denotes a required response with additional reporting requirements) :
Line 1 . •(u) REPORT CLASSIFICATION AND HANDLING INSTRUCTIONS:
Line 2. •(U) DATE-TIME OF DETECTION Date Time Group (DTG) (i.e.,
DDHHHHZ/9"1'1YYYY; indicate whether estimated or precise):
Line 3.A. •(u) UAP-EVENT TYPE (i .e . , UAP incident, UAP incursion,
and/or UAP engagement):
Line 3.B. •(U) UAP-EVENT DESCRIPTION NARRATIVE (i.e., concise summary
of the UAP event):
Line 4.A. •(U) NUMBER OF UAP OBJECTS DETECTED AND METHOD (e.g., three
UAP objects detected with r adar, one of which was observed visually):
Line 4.8. •cu) UAP GEOLOCATION (i.e., where UAP was first sighted;
specify coordinate standard used; indicate whether estimated or
precise) :
Line 4.C. (U) UAP OBJECT(S) ALTITUDE, DEPTH, VELOCITY, AND TRAJECTORY
(indicate estimated or measured):
Line S.A. ••(CUI) UAP ANOMALOUS CHARACTERISTICS/BEHAVIORS (e.g., no
apparent control surfaces, extreme acceleration / direction change,
detection by certain sensors but not others) :
Line 5.8. •(U) UAP OBJECT(S) OESCRIPTION (e .g. , size, shape, color,
markings, recognizable features) AND PHYSICAL STATE (i.e., solid,
liquid, gas, plasma):
Line 5.C. (CUI) UAP OBJECT(S) SIGNATURE (S) (e.g., acoustic, radio
frequency, light, thermal, gravitational , radioactive-with
identification of detecting sensor):
Line 5.D. {U) UAP OBJECT(S) PROPULSION MEANS (e .g., none observed,
rotary wing/propeller):
Line 5.E. (U) UAP OBJECT(S) MANEWERABILITY OBSERVATIONS:
Line 5. F. (U) UAP OBJECT(S) PAYLOAD:
Line 5.G. (U) UAP OBJECT(S) UNDER APPARENT INTELLIGENT CONTROL
(yes/ no; if yes, describe):
Line 7.A. •(U) UAP OBSERVER GEOLOCATION (Latitude-Longitude or MGRS
of the observer and/or sensor; specify coordinate standard used):
Line 7.8 . •(U) OBSERVER ALTITUDE /DEPTH, VELOCITY, AND TRAJECTORY:
Line 7,C. (U) OBSERVER INTERROGATION OF UAP (yes/no; if yes list
sensor(s) used and describe returns):
Line 7.D. •(U) OBSERVER ASSESSMENT OF UAP (i.e., benign, hazard,
threat):
Line 7.E. • (u) OBSERVER ENGAGEMENT OF UAP (yes/no; if yes, describe):
Line 7.F. •(u) UAP REACTION TO OBSERVATION, INTERROGATION, ENGAGEMENT
(yes/no; if yes, what preceded the reaction (e.g,. observer's active
sensing, communication, weapons arllling, engagement)):
Line 8.A. (U) UAP EFFECTS ON EQUIPMENT (e.g., mechanical, electrical
controls and weapons systems and whether persistent or transitory):
Line 8.8 . (U) UAP EFFECTS ON PERSONS (yes/no):
Line 9. (U) UAP FINAL GEOLOCATION (i.e., where UAP was last sighted;
specify coordinate standard used):
Line 10. •(U) UAP OBJECTS/MATERIAL RECOVERED (yes/no; if yes,
describe the objects/111aterial recovered):
Line 11.A. (U) CALLSIGN AND MISSION NUMBER/ IDENTIFIER (of Do0
observer):
Line 11.B. •(U) REPORTING UNIT, POC CONTACT INFORMATION
(unit/organization, name, rank/ grade, email, phone number ):
Line 11.C. •(U) DATE OF DOD ACQUISITION: (i.e., DD""11'1YVVV)
Page 6
PAGE 6 OF 9
Line 11.D. (U) THIRD-PARTY OBSERVERS AND/OR REPORTERS (e .g., other
US and/or foreign national persons or sensors):
Line 11.E. •(U) REPORTING ORGANIZATION UAP-EVENT SERIAL NU,,BER
(format: [Geographic CCMD of event (abbreviation)]·[Detection Oate)
[ three-digit, CCf,O assigned numerical sequence) (e . g., USNORTHCOM/
NORAD- 20JUL2022?009)):
3.D. (U) COUNTERINTELLIGENCE NOTIFICATION
3.D.1. {CUI) DoD counterintelligence elements perform operations and
investigations to protect the OoO from espionage and other foreign
intelligence activities, sabotage, and assassinations conducted by
or on behalf of foreign governments. As potential foreign
intelligence threats to DoD persons, material, and information, DoD,
CCMDs, Services, and their subordinates notify their respective
counterintelligence element as soon as practicable and within 24
hours of a UAP incident. Counterintelligence elements may be
notified of UAP incidents before the UAP incident, incursion, and
engagement report is published.
3.0.2. (CUI) DoD counterintelligence elements assess reported UAP
for foreign intelligence attribution and conduct their related
operational and investigative activities, accordingly. DoD
counterintelligence elements report UAP information of foreign
intelligence and/or counterintelligence value by way of their
Component's intelligence reporting and/or case management systems.
All UAP-related intelligence information reports (IIRs) are
addressed to AARO and reference the applicable UAP-incident serial
number (Line 12.D) . UAP intelligence and counterintelligence
reporting compleinent but do not replace requirements set in
paragraph 2.
3.E. (U) REQUIRED DOCUMENTATION FOR DATA TRANSFERS
3.E.1. (CUI) DoD, CCMOs, Services, and their subordinates securely
transfer UAP DATA to the appropriate location(s) and entit(ies)
following coordination with AARO and no later than 30 days after a
UAP incident. The below template wil l be used to document UAP dat a
retained, a copy of which will accompany electronic or physical data
transport: (•denotes a required response):
Line 1. *(U) UAP DATA CLASSIFICATION AND SPECIAL HANDLING
INSTRUCTIONS:
Line 2.A. •(U) DATE AND TIME OF DATA RECORDED {DTG) (Zulu): (i.e.,
DDHHHHZ""'1MYYYY)
Line 2.8. *{U) REPORTING ORGANIZATION UAP -EVENT SERIAL NUMBER
(format: [Geographic CCMO of event (abbreviation))-[Detection Date] •
[three-digit, CCf,O assigned numerical sequence) (e.g. , USNORTHCOM/
NORA0 -20JUL2022?009)):
Line 3. *(U) DATA DESCRIPTION NARRATIVE {i . e., concise summary of
the UAP data) :
Line 4.A. *(CUI) DATA SENSOR TYPE (e.g., acoustic, radiofrequency,
light, thermal, gravitational, radioacti ve, with identification of
detecting sensor):
Line 4.8. {U) COLLECTION ASSET'S DATA SENSOR MODEL OR NATIONAL STOCK
NUMBER (NSN):
Li ne 4.C. {U) COLLECTION ASSET'S DATA SENSOR SERIAL NUMBER:
Line 4.0. (U) COLLECTION ASSET 'S SENSOR PLATFORM (e.g., handheld,
Page 7
PAGE 7 OF 9
aircraft):
Li ne 4 .E . {U) SENSOR MAINTENANCE RECORO POINT OF CONTACT:
Line 5, •(U) DATA OWNER {ORGANIZATION) INFORMATION (i .e., Combatant
Command, Service):
Li ne 6. •(U) UAP DATA CHAIN OF CUSTODY {Unit/Organization, Name,
Rank/Grade, Phone Number):
3.F. (U) REQUIRED DOCUMENTATION FOR MATERIAL TRANSFERS:
3.F.1. {U) UAP OBJECTS AND MATERIAL are secured in a manner
consistent with DoD Foreign Material Exploitation policies and
doctrine and are transferred to appropriate location(s) and
entit(ies) following coordination with AARO no later than 30 days
after the event. The
below template will be used to record recovered UAP objects and
material recovered, a copy of which will accompany object and
material transport: (•denotes a required response):
Line 1. •(U) UAP OBJECT AND/OR MATERIAL CLASSIFICATION AND SPECIAL
HANDLING INSTRUCTIONS:
Line 2. •(U) UAP OBJECT AND/OR MATERIAL HAZARDOUS -MATERIAL CATEGORY:
Line 3. •(U) REPORTING ORGANIZATION UAP-EVENT SERIAL NUMBER (format :
[Geographic CCMD of event (abbreviation)J·[Detection Date]- [three
digit, CCMO assigned numerical sequence] (e.g., USNORTHCOM/ NORAD20JUL2022 ?009)) :
Line 4 .A. "(U) DATE UAP OBJECT AND/ OR MATERIAL RECOVERED: (i. e.,
DDMMMYYYY)
Line 4 .8 . *{U) UAP OBJECT ANO/OR MATERIAL DESCRIPTION NARRATIVE
(i.e., concise su111111ary of the UAP object and/or material):
Line 5. • (U) UAP OBJECT AND/OR MATERIAL CHAIN OF CUSTODY
{Unit/Organization, Name, Rank/Grade, Phone Number):
3.G. {U) TASKS
3.G .1 . {U) Co111mander, USAFRICOM (CDRUSAFRICOM); Corrvnander, USCENTCOM
(CDRUSCENTCOM); Commander, USEUCOM {CORUSEUCOM); Corm,ander,
USINOOPACOM (CDRUSIMXJPACOM); Co11111ander, USNORTHCOM (CORUSNORTHCOM);
Co111111ander, USSOUTHCOM (CDRUSSOUTHCOM); Co111111ander, USSPACECOM
(CDRUSSPACECOM); Commander, North American Aerospace Defense Corm,and
{CORNORAD) .
3.G.1 . A. (U) Ensure every UAP incident, incursion, and engagement in
your respective Area of Responsibility (AoR) is r eported IAW para
3.C. and 3.D.
3.G. l.A.l. {U) Ensure appropriate guidance is in place and
disseminated to Services and their respect ive subordinates to
r eceive, l og, and t ransmit to the CCMO Joint Operations Center and
to the Service Watch Cells all UAP Incident, Incursion, and
Engagement Reports from Service Co111ponent Commands and subordi nates
and from third parties-to include civil and foreign partners.
3.G.l . A. 2. {U) Securely transmit to AARO all UAP I ncident,
Incursion, and Engagement Reports received by the CCMD Joint
Operations Center from your subordinate commands within 48 hours of
receipt, copying relevant Service Watch Cells.
3.G.l.B. {U) Ensure all UAP data from incidents, incursions, and
engagements in your respective AoR is retained and transferred IAW
para 3. E.
3.G.l.C. (U) Ensure all UAP obj ects and material from incidents,
incursions, and engagements in your respective AoR is secured and
transf erred !AW para 3 . F.
3.G.l.D. {U) Ensure CCMD UAP-Mission guidance and points of contact
are provided to AARO (osd.aaro.reports@mail.mil).
3.G.l.E , {U) Provide mission support to AARO, as requested.
Page 8
PAGE 8 OF 9
3.G.1.E.1. (CUI} Enable deployment of specialized sensors within the
AoR for the detection, observation, and identification in sensitive
areas, and during testing or deployment of special capabilities. All
collection within sensitive areas during testing or deployment
capabilities must be conducted !AW with Intelligence Conwnunity
Directives as well as per REF E.
3.G.1.E.2, (CUI} Enable UAP-related counterintelligence activities,
to include ensuring enjoined UAP observers are available for
debriefing by Counterintelligence Agents.
3.G.1.E.3. (CUI) Inform AARO operational, intelligence, and
scientific analyses with CCMO incident context and UAP trend
analysis, identification, attribution, and technical exploitation.
3.G.1.F. (U) Ensure installations follow processes for UAP reporting.
3.G.1.G. (CUI) Ensure proper security of all UAP data, information,
and material within the AoR.
3.G.1.H. (CUI) USNORTHCOM AoR, Alaska, Hawaii, and Guam instructions
See 3.G.2.
3.G.2. (U) MILITARY DEPARTMENTS
3.G.2.A.1. (CUI} Ensure the Services and their respective
subordinates have the mechanisms necessary to receive, log, and
transmit to the CCMO Joint Operations Center, to the Service Watch
Cells, and to their counterintelligence element all UAP Incident,
Incursion, and Engagement Reports from Service Component Commands and
subordinates and from third parties, to include civil and foreign
partners. When practicable and when consistent with Service Component
Command and subordinate doctrine, existing processes and mechanisms such as incorporating UAP reporting into mission report systems
(e.g., MARAUDER) • is encouraged.
3.G.2.A.2. (U) Securely transmit to AARO all UAP Incident, Incursion,
and Engagement Reports received by the Service Watch Cells from your
Service(s) and their respective subordinates within 48 hours of
receipt, copying relevant CCMO Joint Operations Center.
3.G.2.A.3. (U) Promulgate appropriate reporting procedures to
installations and assets in the USNORTHCOM and USINDOPACOM AoR,
Alaska, Hawaii, and Guam, in accordance with this GENAOMIN,
3.G. 2.8.1. (CUI) Include CORUSNORTHCOM and CORUSINDOPACOM in UAP
incident, incursion, and engagement reporting.
3.G.2.B.2. (CUI) Ensure all UAP data from incidents, incursions, and
engagements involving your forces, materiel, and/or installations is
retained and transferred IAW para 3.E.
3.G.2.B.3. (CUI) Ensure all UAP objects and material from incidents,
incursions, and engagements involving your forces, materiel, and/or
installations is retained and transferred IAW para 3.F.
3.G . 2.C. (CUI) Provide mission support to AARO, as requested and as
described in para 3.G.1.E.
GENTEXT/AOMIN ANO LOGISTICS/4.
4.A. (CUI) Each CCMO, Service, and Service Component Cowrnands ensures
that the appropriate guidance and mechanisms are in place to receive
the respective reports and related material from subordinates.
Standardizing the reporting and material-disposition of UAP
incidents, incursions, and engagements provides DoO leadership and
Commander's with quality, empirically-supported analyses for adapting
to and neutralizing and/or exploiting the evolving threat.
4.B. (U) FUNDING. The Joint Staff will not provide funding.
4.C. (U) AARO UAP INCIDENT, INCURSION, AND ENGAGEMENT REPORTING
ADDRESSES
Page 9
PAGE 9 OF 9
4.C. 1. (CUI) Unclassified UAP reporting may be subNitted by CCMO
Joint Operations Centers to AARO via POC in S.B.
4.C .2. (CUI) Collateral Secret UAP reporting may be submitted by
CCMD Joint Operations Centers to AARO via POC in S.B.
4.C.3. (CUI) Top Secret and/or Sensitive Compartmented Information
UAP reporti ng may be submitted by CCMO Joint Operations Centers to
AARO via POC in s.e.
4.C.4, (CUI) Any Special Access Program required data should be
properly coordinated with AARO via POC in S.B.
4.C.5 . (CUI ) UAP IIRs may be submitted by CCMD Joint Operations
Centers to AARO via POC in 5.B.
4 . D. (CUI) SECURITY/CLASSIFICATION. Follow the Unidentified
Anomalous Phenomena Security Classification Guide (SCG), other SCG,
and other applicable guidance, to properly classify UAP reports,
data, and material. Overall classification of the reports, data, and
material should be no less than the most restrictive classification
within the report's, data's, or material 's constituent parts. Any
information requiring retention and/ or transmittal that exceeds the
classification allowed by storage and/or transmission mode,
annotate "information exceeds the classification of the transmission
mode - on file with the reporting organization" next to the
appropriate paragraph, and coordinate secure transmittal with the
intended recipient.
GENTEXT/C~ND AND SIGNALS/5.
5.A. (U) COMMAND RELATIONSHIPS
5.A.1. (U) Geographic Combatant Commands are the Supported Combatant
Commander within their respective AoR.
5.A.2. (U) The Military Departments are the supporting
organizations.
s.e. (U) The OSD PoC is AARO: Comm: 783-693-3810, SVOIP
302-221-3806, TSVoIP: 982-0521. NIPR email at osd.pentagon.ousd
intel -sec .mbx.aaro@mail.mil. SIPR email at osd.pentagon.ousd-intel
sec.mbx.aaro@mail.smil.ml. JWICS email at OSDPentagonOUSDintel
Sec.MailboxAARO-Reports@osdj.ic.gov .
Staff J-36 PoC is Homeland Defense Division:
OSN (225). SVoIP:-Declassification
5.C.
Comm:
N/A
Previous: AARO-23-F-0740 — FOIA: AARO release (scanned, no extracted text)