Documents / FOIA release
This is a Joint Staff J3 GENADMIN message from the J36 Homeland Defense Division, dated 19 May 2023 and released by the Office of the Secretary of Defense under FOIA 24-F-0067. It tells the combatant commands and the Services to report all UAP incidents, incursions and engagements to AARO on a standard template, to notify counterintelligence within 24 hours, and to transfer UAP data and material to AARO within 30 days. It also defines UAP terms and sets reporting deadlines.
C.Ui PAGE 6 OF 9 Line 11.0. (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 NUMBER (format: [Geographic CCMD of event (abbreviation)]-[Detection Date]- [three-digit, CCMD assigned numerical sequence] (e.g., USNORTHCOM/ NORAD-203UL2022?009)): 3.D.(U) COUNTERINTELLIGENCE NOTIFICATION 3.D.1.4iiii*DoD counterintelligence elements perform operations and investigations to protect the DOD 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.D.2.04.041.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 complement but do not replace requirements set in paragraph 2. 3.E.(U) REQUIRED DOCUMENTATION FOR DATA TRANSFERS 3.E.1.411.191110o0, CCMDs, 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 will be used to document UAP data 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., DDHHHHZMMMYYYY) Line 2.6. *(U) REPORTING ORGANIZATION UAP-EVENT SERIAL NUMBER (format: [Geographic CCMD of event (abbreviation)]-[Detection Date]- [three-digit, CCMD assigned numerical sequence] (e.g., USNORTHCOM/ NORAD-203UL2022?009)): Line 3. *(U) DATA DESCRIPTION NARRATIVE (i.e., concise summary of the UAP data): Line 4.A. ij.DATA SENSOR TYPE (e.g., acoustic, radiofrequency, light, thermal, gravitational, radioactive, with identification of detecting sensor): Line 4.6. (U) COLLECTION ASSET'S DATA SENSOR MODEL OR NATIONAL STOCK NUMBER (NSN): Line 4.C. (U) COLLECTION ASSET'S DATA SENSOR SERIAL NUMBER: Line 4.D. (U) COLLECTION ASSET'S SENSOR PLATFORM (e.g., handheld, 1'1 II vim) ANor II
Not linked to a story yet.
FOIA release, from the osd 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.