Documents / FOIA release
This FOIA release from the All-domain Anomaly Resolution Office contains a Joint Staff J3 GENADMIN message from the J36 Homeland Defense Division, dated 19 May 2023. It tells the combatant commands and the military services to report every UAP incident, incursion and engagement to AARO on standardized templates within set deadlines, and to notify counterintelligence within 24 hours. UAP data and recovered objects or material must be transferred to AARO within 30 days. The message also defines UAP categories and related terms.
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, Not linked to a story yet.
FOIA release, from the aaro collection. The PDF is mirrored here; the original link is above. 9 pages are in the text index: search them above, or from the library's search.