The UAP Space Tiger Team appears in a Joint Staff Action Processing Form dated 20 November 2023. The released record describes an AARO-led coordination framework for spaceborne and transmedium UAP; it is not an incident report demonstrating unusual technology.
Correction, 7 October 2026: This article now distinguishes the document’s 2023 date from its 2026 public release and removes unsupported claims about incidents, participants’ findings and a confirmed meeting.
In this article
Read the source record
The Black Vault’s 1 May 2026 release page reproduces the document and identifies FOIA case 24-F-1205, originally filed with U.S. Space Command as 24-R-020. Consult the reproduced pages before relying on a summary.
What the form establishes
AARO was to convene and chair the team. Its remit included opportunities for space-based detection, reporting and deconfliction. Participation was requested from commands, services and intelligence organisations. The form references section 6802 of the FY2023 National Defense Authorization Act.
| Date or identifier | Meaning |
|---|---|
| 20 November 2023 | Date of the action form. |
| Around 12 December 2023 | Planned first event; scheduling alone does not prove it occurred. |
| 1 May 2026 | Date of the recipient’s public release account. |
| 24-F-1205 / 24-R-020 | Request identifiers for following the release’s provenance. |
What it does not establish
The record does not disclose particular encounters, datasets or detection technologies. A coordination plan cannot establish an object’s origin, the performance of a sensor or the outcome of an investigation. Requested representation should also remain distinct from documented attendance.
How to investigate further
Keep a copy of the form and cite its page number. For a follow-up records request, identify the team, date range and specific record types sought: agendas, attendance, minutes, action lists or later guidance. Ask the likely custodian for existing records rather than an explanation of a theory. A response can then be compared with the original plan.
When discussing a later release, identify its request number and publication date separately. Do not treat this planning document as a substitute for records of the team’s subsequent work.