Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save Pantheon-Investigations/77e9d88041a0a60e45a650eded607cf1 to your computer and use it in GitHub Desktop.

Select an option

Save Pantheon-Investigations/77e9d88041a0a60e45a650eded607cf1 to your computer and use it in GitHub Desktop.
PURSUE Release 01 — Top 10 Findings From a 36-Hour Primary-Source Deep Dive

PURSUE Release 01 — Top 10 Findings From a 36-Hour Primary-Source Deep Dive Leveraging Artificial Intelligence

Plain-language (TL;DR) summary (skip the technical detail below)

The Pentagon released its first batch of UFO files on May 8, 2026, under the program name PURSUE. Most news coverage just summarized the official Pentagon press release. I read the actual PDFs. Here's what's in there, in plain English:

  1. Multiple documents describe UFO activity at what appears to be one specific government facility in Utah — Dugway Proving Ground / Granite Peak Installation. (Dugway is a 1.25-million-acre US Army test facility, primarily for chemical and biological weapons defense testing; Granite Peak is the higher-classification inner enclave.) No major news outlet has named a site yet. Researchers at The Black Vault separately obtained Army records showing Dugway was running monthly UFO-detection exercises in 2023.

  2. One classified document describes US intelligence officers in helicopters being followed by orbs. The document is marked SECRET//NOFORN — the classification level used when revealing how information was collected would compromise sources or methods. The document says the orbs "broke off" the helicopter and "pursued the military aircraft." 2025, Western US, multiple senior intelligence officials as eyewitnesses.

  3. Seven federal law enforcement agents over two days saw "orbs launching orbs" — orange "mother" orbs emitting smaller red orbs, repeated at least 5 times. AARO (the Pentagon's UFO/UAP investigation office, established 2022) sent investigators to the site and took follow-up measurements.

  4. An AC-130 gunship in Iraq, September 2024: while firing a Griffin missile at a ground target, a fast-moving hot object flew through the gunship's targeting sensors. The aircrew flagged that an object may have split off from the primary object before leaving the field of view. Same "splitting" behavior as #3 above, in active combat 7,000 miles away.

  5. The Pentagon's transparency claim about the FBI files actually checks out: they added 1,015 new pages of FBI UFO records compared to what was already publicly available since 2011, with real reductions in redactions. Substantive disclosure, not a re-release.

  6. The famous "Roswell hexagonal disc" memo (Guy Hottel, 1950) that news coverage keeps citing is NOT in this release. It's in a different FBI file. News coverage saying otherwise is repeating an error.

  7. Three FBI witnesses to a September 2023 sighting at a US test site reported a 130-195 foot bronze metallic object. The base's main gate malfunctioned that morning only — never before, never after — which is consistent with electromagnetic interference from an unidentified source.

  8. A 1994 State Department cable contains the first time American commercial pilots officially used the words "extraterrestrial and under intelligent control" about a UFO, after watching it for 40 minutes maneuvering at extreme G-forces over Kazakhstan.

  9. NASA itself flagged unidentified objects in Apollo lunar mission photographs with their own yellow callout boxes — Apollo 12 and Apollo 17, similar blue/cyan glowing objects. Agency-level acknowledgment, not just speculation by outsiders.

  10. The Pentagon's own catalog has at least 5 distinct data-quality bugs. The most important: State Department UFO-related cables seem to have been pulled by keyword match on "UFO" or "UAP" — meaning real UFO-related cables that used different words like "anomalous," "unusual airspace activity," or "object" are likely missing from this release.

What's NOT in this release: 46 specific videos that Rep. Anna Paulina Luna formally requested in March 2026, including the famous February 2023 Lake Huron F-16 missile shootdown of an "octagonal object." Luna confirmed those are coming in "drop B." Zero of the 46 are in this first batch. Rep. Eric Burlison described this batch as "low-hanging fruit."

Why this matters in plain terms: The US government is now publicly documenting UFO encounters in active combat zones, at classified test facilities, by senior intelligence officials, and during civilian commercial flights. Multiple incidents share specific behaviors (orbs that split into smaller objects, objects that pursue military aircraft, formation displays in the sky). Whether these objects are exotic foreign technology, classified American technology, natural phenomena yet to be characterized, or something else entirely — the documents don't say. What they DO establish is that the US government considers the encounters anomalous enough to keep investigating, classify, and now release.


(The detailed findings below use technical language for journalists and UAP researchers who need exact source quotes. The plain-language summary above covers the substance.)


Public release context: On May 8, 2026, the U.S. Department of War (rebranded DoD) published the first batch of declassified UAP files at war.gov/UFO/ under the program name PURSUE — Presidential Unsealing and Reporting System for UAP Encounters. 161 files. Officials: Pete Hegseth (Sec of War), Tulsi Gabbard (DNI), Kash Patel (FBI), Jared Isaacman (NASA).

This document: A research analyst's structured findings from 36 hours of primary-source extraction starting the night of release. ~25 of the 161 files read in detail; the remaining ~135 surveyed indirectly via 9 parallel research passes against the corpus and external mirrors. All quotes verified against original PDFs unless noted.

Methodology note: Most major news outlets are reporting from the Pentagon press release. This document reports from inside the actual PDFs. Five of my own pre-data assumptions were wrong and corrected by primary-source extraction over the course of the investigation — those self-corrections are flagged in the relevant items.


1. The recurring Western U.S. UAP cluster appears to be at Dugway Proving Ground / Granite Peak Installation, Utah (~65-70% confidence)

Multiple PURSUE documents describe activity at what appears to be one classified federal facility across multiple years (2023, 2025, Late 2025):

  • FBI September 2023 Sighting (3 witness 302s + FBI Lab composite sketch)
  • Western U.S. Event 2023 (4-slide briefing, "Orbs Launching Orbs," 7 federal LE agents over 2 days)
  • USPER Statement Late 2025 (SECRET//NOFORN, senior intelligence officials in helicopter aerial response)
  • FBI Photo A series (8 stills, government system, date/location withheld) and Photo B series (24 stills, military targeting pod, "Western United States")

The convergence of geographic features (mountain range with cavern entrance, rock pinnacle, desert+restricted-zone road, federal LE jurisdiction, civilian-contractor LiDAR program, state-partner aviation) most closely fits Dugway Proving Ground (Utah), with Granite Peak Installation as the higher-classification inner enclave.

Independent corroboration: The Black Vault has obtained Army Counterintelligence records documenting August 2023 spectrum-analysis testing at Dugway, plans for visual and radar correlation of UAP sightings, and monthly planning meetings to develop a response matrix for incursions. The stated goal: "to identify a way to obtain visual observation of a UAP and then correlate this visual sighting with radar data." The FBI September 2023 incident (LiDAR-testing convoy at a US test site) lands inside that timeframe.

Additional fits: Utah DPS Aero Bureau is the only state-LE-aviation that matches "STATE PARTNER ORGANIZATION" pilots in the USPER document; Dugway uniquely runs civilian-contractor LiDAR programs (Joint Ambient Breeze Tunnel + Raman-shifted eye-safe LiDAR with Jacobs and others); Dugway's pre-existing public nickname is "Area 52."

No major news outlet has named any specific facility as the underlying site. This remains an open question — primary-source confirmation (an unredacted coordinate, a peak name, a base callsign) would seal it.

Source links:


2. SECRET//NOFORN narrative: orbs broke off from helicopter and pursued military aircraft

The single most consequential document in PURSUE Release 01 is the USPER Statement — a classified SECRET//NOFORN narrative by a senior US intelligence official describing a multi-hour orb encounter at a Western US federal facility in 2025. The release lists this as an "FBI 302 interview," but the underlying document is the witness's after-action statement, not a 302 form.

Key elements:

  • Senior intelligence officials, federal+state law enforcement, multiple helicopters, FLIR + NVG sensor corroboration, Joint Operations Center coordination
  • An aerial search responding to "thuds as if something had fallen and hit the ground" at the same site as a same-day successful test of [redacted]
  • Spotting "a large cavern entrance" at coordinates during daytime search
  • After dark, an LP/OP picked up an orb under FLIR described as "super-hot," hovering at ground level
  • Orb broke into two objects, one came within 10 feet of the helicopter, then under NVG something emerged from the two objects and traveled separately at high speed
  • Coordinated swarm formations at 2227-2257 — orbs flaring up one-at-a-time in horizontal lines, holding 10-15 seconds, flaring down in reverse order, with naked-eye description "oval shaped, orange in color with a white or yellow center and emitting light in all directions"
  • Closing line — direct quote, exactly as it appears in the document:

"The orbs appeared to break off from [CALL SIGN 1] and pursue the [MILITARY AIRCRAFT]."

Most news coverage has quoted helicopter-chase fragments without flagging the SECRET//NOFORN classification or this closing aircrew assessment of orbs interacting with US military aircraft.

Source link: USPER Statement PDF


3. "Orbs Launching Orbs" briefing — 7 federal LE agents, 2 days, 4 categories, AARO field-investigated

The catalog entry titled "Western US Event" is a 4-slide briefing summarizing statements by seven federal law enforcement special agents (USPER1–USPER7) who independently witnessed UAP at a Western U.S. federal facility over two consecutive days in 2023. AARO sent personnel to the site for follow-up measurements that refined witness distance and size estimates.

Four distinct categories:

  1. "Orbs Launching Orbs" — Three two-agent teams independently saw orange "mother" orbs emit/launch smaller red orbs in groups of 2-4 (general consensus: 3); occurred at least 5 times across the 2 days
  2. "Large, Fiery Orb" — Glowing orange orb perched near a "rock pinnacle" for ~1 minute. Witnesses estimated 500-600m distance and "small helicopter cockpit" size; AARO follow-up measurement: ~1050m distance, 12-18 meters in diameter (40-60 ft). Witness vernacular: "similar to the Eye of Sauron from Lord of the Rings, except without the pupil, or maybe an orange Storm Electrify bowling ball"
  3. "Dark Kite" — Pre-dawn. Initially mistaken for a car (red+white lights at 2-3 ft height) on a road in a restricted zone, then revealed itself by moving laterally over the desert at 15-20 mph "with zero resistance" without changing orientation. Under NVG: ill-defined dark kite shape
  4. "Transparent Kite" — 30 minutes later, kite-shaped object 6m off ground, partially transparent under NVG, with the report that a spotlight beam was being partially blocked at a specific intermediate distance by something invisible to the naked eye

This is the primary source for the "orbs launching orbs" claim that has circulated in AARO-adjacent reporting for months. AARO's direct field investigation (with measurements that doubled witness distance estimates and tripled size estimates) is itself a substantive institutional admission.

Source link: Western US Event slides PDF


4. FBI September 2023 Sighting: bronze 130-195 ft cigar-shaped object at a US test site, 3 witnesses, gate malfunction same morning only

September 1, 2023, ~9:00 AM, at a US test site with controlled-access gates. A three-vehicle convoy (F-150 + GMC AT4 + sprinter van) of contractors and a senior base official driving east for LiDAR data acquisition observed an unidentified object visible 5-10 seconds before disappearing. Three FBI 302 interview transcripts plus an FBI Lab composite sketch produced eight months later (April 30, 2024).

Witness 1 (in-person interview) — Female senior base official with 15+ years of experience identifying U.S. military aircraft and drones who had restricted the airspace that morning for the contractors' tests:

"Cigar shaped object with an extremely bright light southwest of them approximately 500 to 3000 feet above the nearest tree line... The object was 'metallic bronze in color' and was the length of two or three Blackhawk helicopters lined up nose to tail. The width of the object was approximately one and a half Blackhawks... The object was completely silent."

"Several of her co-workers subsequently made fun of her due to her report."

Witness 2 (FaceTime interview) — Male drone-pilot contractor, passenger in the lead vehicle:

"A linear object with a super bright light on the east side of the object. The light was bright white and bright enough to see bands within the light. The object was metallic / gray in color. It did not have any wings or exhaust... approximately 5000 feet above ground level, and moved east to west parallel to the ground. The object was visible for five to ten seconds and then the light went out and the object vanished."

Both close witnesses independently report the access gate malfunctioned that specific morning — opened slightly then closed on three tries, opened on the fourth. Specifically noted in Witness 1's account: "there were no prior operational problems with that particular gate and there were no operating issues with the gate after September [redacted]."

FBI Lab composite synthesis (April 30, 2024): "Apparent ellipsoid bronze metallic object materializing out of a bright light in the sky, 130-195 feet in length, and disappearing instantaneously." The 130-195 ft figure is derived directly from Witness 1's 2-3-Blackhawk measurement (Blackhawk = 64 ft).

Source links:


5. AC-130 gunship in active combat: solid IR-flare UAP transited sensor between weapons release and missile impact

DOW-UAP-D28, classified SECRET//REL TO USA, FVEY, declassified by USCENTCOM Chief of Staff MG Richard A. Harrison on 24 October 2025, approved for AARO release 10/28/2025.

September 20, 2024. An AC-130 gunship from the 16th Special Operations Squadron / 27th Special Operations Wing (Cannon AFB AFSOC) was conducting Armed Overwatch during Operation INHERENT RESOLVE in Restricted Operating Zone "RAINDROP" at Ayn al-Asad Airbase, Iraq. After firing 20×105mm + 101×30mm calibration rounds and one AGM-176 Griffin missile in calibration, the crew received a Call for Fire to employ another Griffin against a target.

After weapons release, with the Griffin in flight toward target, the Weapons Systems Officer and Combat Systems Officer observed:

"AN UNIDENTIFIED OBJECT 'FLY' THROUGH THE AIRCRAFT SENSORS AT A HIGH RATE OF SPEED. THE UAP CREATED AN IR LENS FLARE ON THE MX-20 & MX-25 SENSORS, WHICH INDICATED A SIGNIFICANT HEAT SIGNATURE COMING FROM THE OBJECT. IT IS UNKNOWN AT THIS TIME WHETHER AN OBJECT DETACHED ITSELF FROM THE PRIMARY UAP IMMEDIATELY BEFORE LEAVING THE SENSOR FIELD OF VIEW. THE CREW MAINTAINED LASER ENERGY UNTIL THE MUNITION IMPACTED ITS DESIRED TARGET. [aircraft] DID NOT REOBSERVE THE UAP."

AARO form fields:

  • UAP Physical State: Solid (compare to D32 Syria, classified Plasma)
  • UAP Reaction to Observation: "Path of movement appeared predetermined and not in response to [aircraft]'s detection"
  • First and Last Accuracy: Precise (high-confidence sensor track, not estimated)

The "possible object detachment" phrasing matches the same orb-launching-orb morphology described in the 2023 Western U.S. Event briefing. Two events 7,000 miles apart documenting a similar signature class. CENTCOM declassified this for AARO release.

Catalog data-quality note: PURSUE's URL/filename for this document erroneously says "east-china-sea-2024.pdf"; the actual document content is unmistakably Iraq (Ayn al-Asad / 38S MGRS coordinates).

Source link: DOW-UAP-D28 Mission Report PDF (note: filename says East China Sea but content is Iraq)


6. Pentagon's "newly declassified pages, only minor redactions" claim about the FBI 62-HQ-83894 series is quantitatively accurate

The PURSUE catalog blurb on the 17 FBI 62-HQ-83894 files admits the series is partially on the FBI Vault but claims newly declassified material is included.

Quantitative diff against the FBI Vault version (Vault has had 62-HQ-83894 publicly available since 2011):

FBI Vault (2011) PURSUE Release 01 (May 2026)
Containers 16 Parts 18 files (10 Sections + 7 Serials + 1 SUB_A)
Total pages 1,616 2,631
Net new +1,015 pages (+63%)

Sampled diff comparisons confirm real redaction reductions on shared memos. The August 5, 1947 Hoover memo is fully redacted in FBI Vault Part 1; in PURSUE Section 1 it appears with the recipient unredacted: "Director, War Department General Staff, Attention: Colonel L. R. Forney, Chief, Security Group." The 7 individual serial PDFs (130, 153, 164, 220, 403, 438, 449) and the SUB_A subfile are not on FBI Vault.

Note on my own analytical track record: This was one of five places in this investigation where my pre-data first-pass framing was wrong and was corrected by primary-source verification. On the night of release, I dismissed the FBI material as "largely cosmetic re-release"; the quantitative diff shows it is materially new. PURSUE catalog claims about itself test surprisingly accurate against ground truth.

Source link: FBI Vault UFO index (compare against PURSUE 62-HQ-83894 sections at war.gov)


7. The most-famous FBI UFO memo (Guy Hottel's 1947 hexagonal disc memo) is NOT in PURSUE Release 01

Multiple major news outlets covering PURSUE have referenced or implied that the famous Guy Hottel memo (March 22, 1950) — the most-downloaded item on FBI Vault since 2011, the "hexagonal disc / 20-foot UFO recovered" memo associated with Roswell speculation — is part of the PURSUE FBI release.

It is not. A ripgrep across all 4,197 OCR'd pages of PURSUE's 17-file 62-HQ-83894 series (via the github.com/DenisSergeevitch/UFO-USA Gemini-OCR mirror) returned zero hits on Hottel-related content. The Hottel memo lives in a separate FBI Vault collection at vault.fbi.gov/hottel_guy, not in 62-HQ-83894.

Other famous FBI-era UFO documents also absent from PURSUE Release 01:

  • Washington National 1952 "merry-go-round" — the era's biggest radar/visual event
  • Robertson Panel 1953 — CIA scientific panel; not in the FBI corpus
  • Lonnie Zamora / Socorro 1964 — most physically-evidenced FBI-era case
  • Kecksburg PA 1965 — "acorn-shaped" object recovery
  • Levelland TX 1957, RB-47 1957, Trindade 1958, Father Gill 1959, Villas-Boas 1957 — all absent

What IS in PURSUE's 62-HQ-83894: Kenneth Arnold (1947 — dominant subject, dedicated Serial 130), Maury Island (1947 — most thoroughly investigated, ~20 pages of Dahl/Crisman investigation in Section 3), Mantell (1948), Lubbock Lights (1951), Project Blue Book (18 pages of Hoover-signed punt-to-USAF redirects), Hopkinsville goblins (1955), Adamski + Keyhoe correspondence to Hoover. Plus Serial 403 contains the literal dust-jacket scan of Gray Barker's 1956 They Knew Too Much About Flying Saucers — the book that originated Men in Black lore.

This is another self-correction — on the night of release, my Round 1 framing said the Hottel memo was in PURSUE as recycled content. Wrong. News coverage repeating that line is repeating an error.

Source link: vault.fbi.gov/hottel_guy — for the actual Hottel memo, NOT in PURSUE


8. Tajik Air 747 / Captain Ed Rhodes 1994: three American pilots officially logged "extraterrestrial and under intelligent control"

State Department UAP Cable 2 (drafted from Embassy Dushanbe, Tajikistan, January 31, 1994) documents an incident over Kazakhstan three days earlier. Three American ex-Pan Am pilots flying a Tajik Air 747SP at 41,000 ft observed an unidentified object for 40 minutes near the Aral Sea, performing circles, corkscrews, and 90-degree turns at high G. Forty-five minutes later they flew under contrails Captain Ed Rhodes estimated at 100,000 ft.

Direct quote from the cable (verified against original PDF):

"ON THE BASIS OF ITS SPEED AND MANEUVERABILITY, RHODES EXPRESSED THE OPINION, WHICH HIS CREW SEEMED TO SUPPORT, THAT THE OBJECT WAS EXTRATERRESTRIAL AND UNDER INTELLIGENT CONTROL."

"4. COMMENT: WE HAVE NO OPINION AND REPORT THE ABOVE FOR WHAT IT MAY BE WORTH."

Signed: ESCUDERO

This is the only document in PURSUE Release 01 containing an aircrew "extraterrestrial and under intelligent control" attribution that the Embassy chose to log without dispute (just "we have no opinion"). Distribution of the cable in 1994 included CIA WASHDC and DIA WASHDC as direct addressee copies.

Captain Rhodes took photos with a pocket Olympus during the encounter and promised to send them to the Embassy and to the Tajikistan Desk officer Lowry Taylor at State. Those photos are NOT in PURSUE Release 01. They are an open known unknown.

Source link: Cable 2 — Kazakhstan / Dushanbe PDF


9. NASA itself has formally annotated Apollo-era unidentified phenomena with yellow callout boxes — institutional acknowledgment, not just recycled lore

PURSUE includes 6 NASA-archived Apollo lunar surface photographs (NASA-UAP-VM1 through VM6, Apollo 12 + Apollo 17) with yellow callout boxes drawn by NASA itself highlighting unidentified phenomena above the lunar horizon. The callouts target a consistent blue/cyan chromatic signature across both missions:

  • VM1 (Apollo 12, 1969): A vertically-elongated blue/cyan luminous structure with multiple internal bright points
  • VM6 (Apollo 17, 1972): Multiple discrete cyan/blue points clustered together — different morphology, same chromatic family
  • VM2-VM5 (Apollo 12) include additional callout areas

NASA has historically been conservative about Apollo-era anomalies. The institutional methodology of officially highlighting these in agency-released archival photographs is itself a meaningful shift.

This is paired with the Apollo 11 Technical Crew Debriefing (NASA-UAP-D4, July 31, 1969), in which all three crew (Armstrong / Aldrin / Collins) discuss an unidentified bright object 1 day out from the Moon. Aldrin: "It seemed to have a bit of an L shape to it." Armstrong: "Like an open suitcase." Crucially, the crew explicitly notes: "We weren't sure but what it might be the S-IVB. We called the ground and were told the S-IVB was 6,000 miles away." That direct exclusion of the standard skeptical explanation is now in the publicly-released formal debrief.

Source links:


10. The catalog has at least five distinct data-quality bug classes, including evidence that State Department cable selection was keyword-driven (suggesting real UAP cables NOT using "UFO/UAP" exact strings are systematically missing)

Plain-language version: Think of the Pentagon's PURSUE release as a library of 161 documents. Along with the documents, the Pentagon published a spreadsheet listing each one. When I cross-checked the spreadsheet against the actual documents, I found 5 different ways it gets things wrong:

  1. Wrong dates — sometimes the listed date is when someone emailed about a document rather than when the UFO event happened. One document is labeled "March 2026" but the event was actually in March 2023.

  2. Wrong locations — one document's filename says "East China Sea" but the content is unmistakably about Iraq.

  3. Non-UFO documents bundled in as if they were UFO incidents — two of the 161 files are actually a 1996 rocket safety study and a Vandenberg launch history book. Zero UFO content. Probably bundled as background reference material but labeled as incidents.

  4. The State Department cables look like they were picked by keyword search on "UFO" or "UAP" — not by whether the cable is actually about UFOs. One cable labeled "UFO incident in Georgia" is actually a sarcastic Russian government cable about an airspace dispute. This is the operationally significant one — if the Pentagon's process only catches cables with those exact keywords, real UFO-related cables that used other words ("anomalous," "unusual airspace activity," "object," "phenomenon") are systematically being left out of this release.

  5. One cable is attributed to the wrong embassy — labeled as Tbilisi, actually from Moscow.

Bottom line: the Pentagon's catalog is buggy enough that you can't fully trust the metadata, and the bugs suggest the Pentagon's filtering process is leaving out relevant material that doesn't use the right keywords.

(Technical table follows for researchers and journalists who want the formal classification of each bug type.)

Across primary-source verification of ~25 PURSUE files plus 9 parallel research passes, the catalog metadata showed five distinct error patterns:

Bug Description Confirmed examples
A Email-correspondence header bleed into incident date/location DOW-UAP-D51 (catalog says "3/23/26"; incident actually March 2023) and Mexico Cable 5 (catalog says 2003; cable actually 2023)
B URL filename derived from non-authoritative source DOW-UAP-D28 (URL says East China Sea; document is Iraq)
C Publication/cutoff date of reference document mis-mapped as incident date DOW-UAP-D48 + D49 (zero-UAP range-safety reference docs with publication dates listed as incident dates)
D Keyword-driven cable selection includes non-UAP cables State Cable 3 ("Tbilisi 2001" — actually an Embassy Moscow cable using "UFO" rhetorically about a Russia-Georgia airspace dispute); State Cable 4 (Ashgabat 2004 — civil-society report on a Turkmen NGO named "Union of UFOlogists")
E Cable mis-attribution by drafting embassy State Cable 3 (catalog lists Tbilisi; cable was drafted Embassy Moscow)

Bug D is the operationally significant one. If PURSUE State Department selection was performed by keyword match on subject/body text containing "UFO" or "UAP," then real UAP-relevant State cables that happened to use other terminology — "anomalous," "unusual airspace activity," "object," "phenomenon" — are systematically missing from this release. That's a sizable known-unknown blind spot.

Two of the five State cables in PURSUE turn out not to be substantively about UAP. Of the original 161-file count, the effective UAP-incident corpus is closer to ~115-130 records once you remove zero-UAP reference documents (D48, D49), keyword-matched non-UAP cables (Cable 3, Cable 4), and ancillary administrative material.

Bonus context — also held back from this release (per Rep. Anna Paulina Luna's March 31, 2026 letter to Sec of War Hegseth): The 46 specific UAP videos identified by whistleblowers, including the AESIR11 / Lake Huron F-16 shootdown of February 12, 2023 (where the pilot described the object as "octagonal and unlike any balloon he had seen"), AFSOC Kabul 2017 footage, MQ-9 East China Sea January 2023 footage, hi-res Hackney 4X 2019 footage, USCG Tic Tac IR April 2024, and 41 other named-callsign incidents. Zero of the 46 are in Release 01. Luna has confirmed: "Our requested docs/vids will be in second drop b." Rep. Eric Burlison has framed Release 01 as "low-hanging fruit."

Source links:


What's still hidden

  • Captain Ed Rhodes' 1994 pocket-Olympus photos (promised in Cable 2, not in PURSUE)
  • The 46 videos identified by Luna's whistleblowers (zero of 46 in Release 01; Luna says "drop b")
  • AESIR11 Lake Huron F-16 shootdown footage (Feb 12, 2023) — most operationally consequential held-back item
  • Specific identification of the Western U.S. classified facility (Dugway/Granite Peak hypothesis at ~65-70%; needs unredacted coordinate, peak name, or callsign in a future drop)
  • Famous FBI UFO documents (Hottel memo, Washington National 1952, Robertson Panel, Socorro 1964, Kecksburg 1965) — none in PURSUE Release 01
  • Apollo 17 D6 Schmitt corroboration of Grimaldi flash + Evans reentry "tunnel" detail (in PURSUE D6, originally CONFIDENTIAL with auto-90-day declassification clause from January 1973)
  • State cables not using exact "UFO/UAP" keyword strings — systematically missing per Bug D
  • Grusch's named-program physical-recovery substrate (Lockheed/Battelle/contractor references) — entirely absent
  • The Wilson-Davis memo — entirely absent
  • High-resolution signature footage congressional disclosure advocates have been promising — almost entirely absent (PURSUE visuals are mostly grainy/distant)

Methodology notes

This document was produced by a single research analyst over ~36 hours starting May 8, 2026 evening through May 9, 2026 mid-morning, using primary-source PDF extraction (PDF.js text layer + screenshot fallback for image-only PDFs), nine parallel OSINT passes against external mirrors and reference sources, and verification of all directly-quoted material against original documents. War.gov direct fetching is blocked by Akamai for non-browser clients; the open-source GitHub mirrors at github.com/ckpxgfnksd-max/uap-release-01 (PDF LFS) and github.com/DenisSergeevitch/UFO-USA (Gemini-OCR markdown) are useful access paths.

Self-corrections made over the course of the investigation (each subsequently corrected by primary-source verification):

  1. Pre-data dismissal of PURSUE as "controlled limited hangout" — wrong; corrected by pulling the actual catalog (May 8 evening)
  2. Initial framing of FBI 62-HQ-83894 as "largely cosmetic re-release" — wrong; quantitative diff shows +1,015 pages with real redaction reductions (May 9)
  3. Repeated assumption that the Hottel memo was in PURSUE — wrong; not in 62-HQ-83894 per ripgrep (May 9)
  4. Provisional acceptance of "URL slug authoritative" rule for D28 — wrong; document content settled it as Iraq, not East China Sea (May 9)
  5. Treated DOW-UAP-D48 and D49 as UAP incident reports based on catalog framing — wrong; both are zero-UAP range-safety reference documents (May 9)

Pattern: pre-data assumptions consistently wrong; primary-source verification consistently right. Lesson for downstream researchers: defer judgment on Pentagon/agency claims until primary-source data is in hand, and do not extrapolate from catalog blurbs — verify against document content.


Where to find the full documents


About Pantheon Investigations: https://gist.github.com/Pantheon-Investigations/5ddfe2663527fb6fe138b0081cbfd77c — independent research practice, primary-source analysis of public government documents. Free for use; corrections welcome.

This document is provided as a research artifact for journalists, UAP researchers, and the general public. All quotes verified against original PDFs; all data-quality bugs replicable. Corrections welcome.

USPER Statement about UAP Sighting — Full Extracted Text

Source: https://www.war.gov/medialink/ufo/release_1/usper-statement-redacted.pdf Catalog title: "USPER Statement about UAP Sighting" (FBI / Late 2025 / United States) Classification (in document): SECRET//NOFORN Pages: 3 Note: PDF text-layer extraction has OCR-like artifacts (broken words, "Igence" for "ligence", etc.) due to redaction-bar overlap. Text reconstructed below.

Significance

This is the most operationally specific, incident-level UAP document in PURSUE Release 01. SECRET//NOFORN classification, 2025 incident, senior US intelligence officials as direct witnesses, multi-agency aerial response with federal+state partners, FLIR/NVG sensor corroboration, military aircraft involvement. Describes coordinated swarm behavior at a (redacted) Western US test facility, including objects that "broke off from" the helicopter and "pursued the military aircraft."

Reconstructed timeline

Earlier that day — Office completed a successful test of [redacted] at [SITE CODE NAME] ([COORDINATES]) on [FACILITY]. Personnel near [COORDINATES] reported observing orbs/lights and hearing "thuds as if something had fallen and hit the ground." This is what triggered the aerial search.

Personnel:

  • WITNESS 1 — senior US intelligence official (naked eye observer)
  • WITNESS 2 — senior US intelligence official
  • FEDERAL PARTNER 1, 2, 3, 4
  • Pilots from STATE PARTNER ORGANIZATION
  • CALL SIGN 1 — primary helicopter
  • CALL SIGN 2 — secondary helicopter (state partner)
  • LP/OP — Listening Post/Observation Post (FEDERAL PARTNER 4 personnel) using FLIR + NVG
  • 5 MILITARY AIRCRAFT (training mission)
  • FEDERAL PARTNER AIRCRAFT (later response)
  • JOC — Joint Operations Center coordinating

Timeline (all on the same day, 2025):

Time Event
~1700 Departure from OPERATIONS CENTER for daytime aerial search of MOUNTAIN RANGE west of SITE CODE NAME
1751 CALL SIGN 1 spotted large cavern entrance at [COORDS], conducted short orbit
2050 CALL SIGN 1 landed west of mountains, dropped off WITNESS 2 with FEDERAL PARTNER 3
2052 CALL SIGN 1 headed to refuel; CALL SIGN 2 briefly landed then returned to base
2141 CALL SIGN 1 lifted off, headed toward debris spotted by LP/OP via FLIR+NVG ~4 miles east of SITE CODE NAME in the mountains. Searched with NVG, naked eye, spotlight in near-full-darkness — negative results
2149 Returning to base when LP/OP reported "hits, bearing ~4 miles out." JOC provided coords. Moved to intercept
2202 Arrived at coords. Spotted possible aircraft on horizon moving west. LP/OP reported orb under FLIR, "super-hot," hovering at ground level, then heading east. Then south at high rate of speed. Then orb broke into TWO OBJECTS. LP/OP directed intercept
2207 JOC reported 5 MILITARY AIRCRAFT in airspace on training mission. CALL SIGN 1 searched with FLIR/NVG/naked eye — did not locate orb
LP/OP: orb gained elevation, came within ten feet of CALL SIGN 1, then headed east. Continued southeast ~20 miles past ROAD NAME. Co-pilot reported under NVG: something emerged from the two objects and traveled in a different direction at high speed
2218 Pilots (NVG) and WITNESS 1 (naked eye) spotted a swarm of lights, "too many to count," moving in all directions, generally west and headed south
2227 Lost visual of swarm. (Possibly out of order:) WITNESS 1 + pilots spotted two large orbs west and above rotor disk. Naked eye: "oval shaped, orange in color with a white or yellow center and emitting light in all directions." Flared up, stationary, side by side. A third orb flared up below, then a fourth, then a fifth — until there were 4-5 total below the original two. Flared down in reverse order, stationary, until visual lost
2228 Spotted 4-5 orbs west over the mountains above the MILITARY AIRCRAFT. Flared up one at a time in horizontal formation, 10-15 sec, flared down in opposite order
2233 Same formation east near NEARBY TOWN NAME. Same flare pattern
2241 Similar orb flare up west of SITE CODE NAME over the mountain
2249 Swarm of lights west, with three distinct orbs in a triangle formation
2252 ~10 miles north of SITE CODE NAME. Spotted 5-6 orbs flare up IVO LOCAL TOWN (east of SITE CODE NAME). Horizontal formation, 10 sec, reverse-order flare down
2257 Same position. 4 orbs flared up OVER the MILITARY AIRCRAFT as they descended to land. Horizontal formation, 10 sec, reverse-order flare down
~2306 [content redacted/missing]
2316 Low on fuel, CALL SIGN 1 returned to OPERATIONS CENTER
2320 CALL SIGN 1 headed southbound, in air-to-air contact with FEDERAL PARTNER AIRCRAFT. Passed each other as FEDERAL PARTNER AIRCRAFT headed north toward SITE CODE NAME

WITNESS 1 closing comments

Pilots indicated they were recording however many sightings were above the helicopter which was outside of the helicopter's FLIR camera angle.

Some things I could not see with the naked eye, but I recall the pilots calling out sightings.

The orbs appeared to break off from [CALL SIGN 1] and pursue the [MILITARY AIRCRAFT].

Key analytic points

  1. Recurring phenomenon, not one-off. The aerial search was responsive to previously observed orbs/lights at known coordinates and to thud sounds suggesting fallen objects. The site has a history.
  2. Same-day defense test. A successful test of [redacted] at the site preceded the orb activity. Possible correlation worth probing in subsequent releases.
  3. Coordinated formation behavior. Repeating pattern: orbs flare up one at a time in horizontal line, hold ~10-15 sec, flare down in reverse order. Triangle formation also observed. Consistent with intentional display, inconsistent with natural phenomena.
  4. Multi-modal sensor confirmation. FLIR ("super-hot" hovering at ground level), NVG (multiple), naked eye (multiple), helicopter spotlight. Not a single-sensor artifact.
  5. Active interaction with assets. Object came within 10 feet of helicopter; orbs broke off helicopter and pursued military aircraft; orbs flared up directly over military aircraft as they descended to land.
  6. Object splitting / emergence. Two distinct events: (a) single orb broke into two objects under FLIR; (b) co-pilot reports under NVG something emerged from the two objects and traveled separately.
  7. Cavern entrance spotted during initial daytime search. Unknown significance — could be incidental geography or operationally relevant. Cavern feature plus thuds-as-if-something-fell hints at recovery-scenario investigation.
  8. The sweep was originally for downed object debris. They were searching for what had hit the ground. The orbs appeared during/after that search.

Geographic candidates (Western US, ~2025)

Clues: mountain range with caverns, classified test facility ("SITE CODE NAME"), state-partner aviation (state law enforcement or state National Guard), nearby town, federal partner aircraft response, military aircraft training airspace.

Candidates considered:

  • Dugway Proving Ground (UT) — high desert, classified, Utah DPS Aero Bureau aviation, civilian-contractor LiDAR programs, Granite Peak Installation as inner classified enclave; corroborated by Black Vault Army CI records on August 2023 spectrum-analysis testing + monthly UAP planning meetings at Dugway
  • Nevada Test and Training Range / Tonopah / Nellis — caverns, mountains, classified, military training, state DPS aviation
  • Nevada National Security Site (NNSS, formerly NTS) — Rainier Mesa tunnels, caverns, classified
  • White Sands Missile Range (NM) — mountains, classified, NM State Police aviation
  • China Lake NAWS (CA) — mountains, classified, CA aviation
  • Plant 42 / Edwards AFB (CA) — Skunk Works, mountains nearby

Dugway / Granite Peak Installation is the strongest candidate (~65-70% confidence) given the convergence of features: civilian-contractor LiDAR program (uniquely at Dugway), Utah DPS Aero Bureau (the only state-LE aviation matching "STATE PARTNER ORGANIZATION"), Granite Peak Mountain west of the main cantonment, and the publicly-documented Army CI UAP-detection coordination at the site in 2023.

Provenance / classification interpretation

The PURSUE catalog labels this an "FBI 302 interview" but the document itself is plainly an intelligence community summary, not a 302 form. SECRET//NOFORN is the document's classification at time of authorship; for it to appear in PURSUE it must have been declassified or downgraded. The lack of a 302 form layout and the prose style suggest this is WITNESS 1's after-action statement, possibly attached to a 302 (which is what the catalog described) but the underlying narrative document is what's posted.

Cross-reference

This event likely connects to:

  • FBI Sept 1, 2023 sighting (different file, same Western US "US test site" pattern, also "orb"/"bright light" terminology, also bronze ellipsoid composite). Same site? Plausible but not confirmed in this document.
  • FBI Photo A1-A8 (Late 2025, "still image derived from a U.S. government system, date and location not provided") — could be imagery from this incident
  • FBI Photo B1-B24 (Late 2025, Western United States, "still image derived from a U.S. military system in 2025, redacted before submission") — could be imagery from this incident
  • AARO — document explicitly notes FBI submitted to AARO

Open follow-up questions

  1. Date this incident more precisely. Range Fouler Debrief logs and AARO case numbers may show in subsequent releases.
  2. Identify SITE CODE NAME — once geographic candidates narrow, the cavern feature + state-partner pilots may anchor it.
  3. Compare with the Late 2025 FBI Photo A and B series — if those are imagery from THIS event, the metadata in their PDFs may carry overlapping coordinates or timestamps.
  4. Watch for follow-on releases addressing the same SITE CODE NAME — recurring phenomenon means more docs almost certainly exist.

Western US Event — "Orbs Launching Orbs" Briefing

Source: https://www.war.gov/medialink/ufo/release_1/western_us_event_slides_5.08.2026.pdf Filename note: western_us_event_slides_5.08.2026.pdf — the briefing slides were prepared on the day of release (May 8, 2026), specifically for PURSUE Release 01 Pages: 4 Format: Briefing slide deck with witness narrative + recreation drawings Agency: Department of War Incident date: 2023 (two consecutive days) Location: Western United States AARO involvement: Direct (AARO took follow-up measurements)

What this is

A briefing summary of statements by seven US PERSONs (USPER1-USPER7) employed by the federal government as law enforcement special agents, who separately reported observing multiple distinct UAPs in the western United States over the course of two days in 2023. The summary identifies four distinct categories of phenomena. AARO subsequently took follow-up measurements that refined witness distance and size estimates.

Category 1: "Orbs Launching Orbs"

  • Time of day: Dusk (on two separate days)
  • Witnesses: USPER1-USPER6 — three teams of two federal LE special agents each, independently
  • Phenomenon:
    • Orange "orbs" appear in the sky and emit/launch smaller red "orbs" in groups of 2-4 (general consensus: 3)
    • Occurred at least 5 times across the 2-day period
    • Each event: orange orb appears → launches red orbs → orange orb disappears
    • Orange orb visible only 1-2 seconds
    • Red orbs typically moved horizontally away from the orange "mother" orb
    • Some witnesses saw red orbs move "heading up at an angle"; others saw them "swoop down"
    • Witnessed from varying locations and vantage points across the 2-day period
  • Open question: "Due to the sequential nature of the events, it is not known whether there was a single orange 'mother' orb that released the groups of red orbs or whether there were multiple orange orbs at play."

Category 2: "Large, Fiery Orb"

  • Time of day: Dusk
  • Witnesses: USPER5 + USPER6
  • Phenomenon:
    • Glowing orange orb perched close to a rock pinnacle
    • Witness-estimated distance: 500-600 meters
    • AARO follow-up measurement: ~1050 meters (witnesses underestimated by half)
    • Witness-estimated size: similar to "small helicopter cockpit"
    • AARO follow-up measurement: 12-18 meters in diameter (40-60 ft) — these orbs are LARGE
    • Witnesses unable to clearly see structure other than the glowing orb
    • USPER6 noted: "did almost appear it might have had a small spindle or something connecting it from underneath to the rock formation"
    • Object did not emit any noticeable sound
    • Witnesses' vernacular descriptions:

      "similar to the Eye of Sauron from Lord of the Rings, except without the pupil, or maybe an orange Storm Electrify bowling ball"

    • USPER6: "seemed to be hovering with zero resistance or movement, or to be suspended..."
    • Sighting duration: ~1 minute

Category 3: "Dark Kite"

  • Time of day: Pre-dawn hours
  • Witnesses: USPER5 + USPER6
  • Phenomenon:
    • Initially thought to be a car traveling along a road in a restricted zone
    • "Car" had two lights (one red, one white) about 2-3 feet off the ground
    • Agents pursued
    • As they got within a few hundred feet, the object suddenly moved off the road over the desert without changing its orientation (i.e., moved laterally rather than turning)
    • Estimated speed: 15-20 mph
    • Did not change height, "zero resistance"
    • Stopped about 100 meters off the side of the road and turned off its lights
  • Once stopped:
    • USPER6 (NVG): observed the object for "a split second in the NVGs before the light turned off" — once lights off, a "very thin line" remained
    • Estimated 4 feet wide, positioned horizontally to the ground (drawing recreation = Image 1)
    • USPER6 description from the back: "thin line"
    • USPER5 description: "ill-defined, dark kite shape that had some rounded width to the sides"
    • In later discussions with AARO, the object is described as triangular
  • Then resumed motion:
    • 15-20 mph again
    • Appeared to "move up in height... but [remain] a flat line"
    • Lost sight after a few seconds

Key insight: The object mimicked a car along a road, then revealed itself when approached — that's deliberate camouflage behavior or a happenstance that yields camouflage.

Category 4: "Transparent Kite"

  • Time of day: Pre-dawn hours, ~30 minutes after Dark Kite
  • Witnesses: USPER5 + USPER6, plus USPER7 (who did NOT see the object)
  • Location: Within a few hundred meters of the Dark Kite sighting; same general area
  • Phenomenon:
    • Returned to area in response to a report of another unauthorized object
    • Two team members observed a kite-shaped object with lighting pattern similar to the Dark Kite
    • About 6 meters off the ground
    • Canted at an angle from lower-right to upper-left (drawing recreation = Image 2)
    • Appeared to be floating slowly with the wind
    • USPER5 was using NVGs; USPER6 used bare eye; USPER7 did not see
    • USPER5 (NVG): "vaguely see a bright star or two in the distance through the object, though somewhat more faint" — i.e., the object was somewhat transparent
  • The spotlight test:
    • After losing sight of the object, USPER5 tried using a spotlight to find it again
    • "At one point my beam went from shining far into the distance to stopping about 50 yards away on nothing in particular, it just was not projecting into the distance and then it was."
    • When the witness pointed the light at the spot where the light had appeared to be blocked by something, the light was "projecting into the distance again"
    • Team unable to reacquire visual

Key insight: The beam was being partially blocked by an apparently invisible-to-eye object at a specific intermediate distance. Either an optical illusion, a transparent material, or active light-absorption.

Why this is significant

  1. "Orbs launching orbs" has been alluded to in AARO testimony and Hollywood Reporter coverage for months as a major UAP claim. This briefing is the actual primary source of that phrase. Multiple independent witness teams over two days, ≥5 instances. Not a single anecdote — a documented pattern.

  2. AARO directly investigated the event. They sent personnel to take follow-up measurements that REFINED witness estimates. AARO's measurement gave 12-18m diameter for the fiery orb (vs. witness "small helicopter cockpit") and 1050m distance (vs. witness 500-600m). AARO is doing field investigation, not just paper review.

  3. Federal law enforcement special agents as witnesses. Trained observers, presumably in tactical gear with NVGs. Seven of them. This is the strongest witness pool quality possible short of military aviators with sensor systems.

  4. A "restricted zone" with controlled access — suggests this is a federal facility, not generic public land. The cars-on-roads + access restrictions match a base or major test range.

  5. Multiple object morphologies in one cluster:

    • Orange mother orbs (fast, brief)
    • Red baby orbs (formation behavior)
    • Large fiery orb (perched, ~12-18m, near rock pinnacle)
    • Dark kite (~4 ft, triangular, road-mimicking)
    • Transparent kite (semi-transparent, beam-blocking)

    That's at least 4-5 different object classes in two days at the same area. Either an extremely active site, a coordinated event, or multiple unrelated phenomena clustering temporally.

  6. The "Eye of Sauron / orange bowling ball" descriptions are vernacular field-agent voice — colorful, specific, and credibly first-hand. Not the kind of language that gets through editorial filtering if this were curated for press release.

  7. The beam-blocking observation (Category 4) is potentially the most empirically interesting single claim. If verified, "object that partially blocks light beams while being mostly transparent" doesn't have a conventional explanation. Could be:

    • Atmospheric distortion at a specific distance (unlikely to be that localized)
    • A reflective/refractive material with low albedo
    • Active light absorption (exotic)
    • Optical illusion / witness misperception (most likely conventional explanation)

Connection to other PURSUE Release 01 documents

  • USPER Statement (2025): Different year, same general "Western US classified test facility" pattern, also "orbs," recurring observations. The 2023 Western US Event and the 2025 USPER Statement are likely at the same general site. The "rock pinnacle" mentioned here matches the geography described in the 2025 USPER's "mountain range west of SITE CODE NAME."

  • FBI September 2023 sighting: Different witness type (civilian LiDAR contractors vs. federal LE), different time of day (9 AM vs. dusk/pre-dawn), different object (130-195 ft bronze cigar vs. orbs and kites). Possibly same general region but different incidents — or possibly the FBI Sept 2023 incident is one of the four categories of the broader two-day event.

  • FBI Photo A series + B series (Late 2025): Likely visual records from related/subsequent activity at the same site.

If the connection holds: multi-year, multi-agency, multi-modality investigation of a recurring UAP cluster at one specific Western US classified federal facility — the largest publicly-released body of evidence for sustained localized UAP activity that the US government has produced.

Geographic candidates (refined)

The Western US Event narrative adds geography clues:

  • "Restricted zone" with road and access
  • "Rock pinnacle" — distinctive geological feature
  • Desert ("moved off the road over the desert")
  • "Mountains" (per USPER doc, presumably same area)

Strongest candidate set:

  • Dugway Proving Ground (UT) with Granite Peak Installation as the inner classified enclave — uniquely fits the civilian-contractor LiDAR program, Utah DPS Aero Bureau as state-partner aviation, Granite Peak Mountain west of the main cantonment, and 2023 Army CI UAP-detection coordination documented via Black Vault FOIA records (~65-70% confidence)
  • Nevada Test and Training Range (NTTR) / Nellis sub-ranges — desert, rock pinnacles (e.g., Tikaboo Peak area), restricted zones, federal LE presence
  • Nevada National Security Site (NNSS, formerly NTS) — Rainier Mesa tunnel portals match "cavern entrance," classified, federal LE
  • White Sands Missile Range (NM) — desert, restricted, mountains, federal LE
  • Tonopah Test Range — desert, restricted, mountains nearby

Dugway is the highest-probability candidate given the combination of state-LE-aviation specifically (Utah DPS Aero Bureau is a true state law enforcement aviation unit, while Nevada Army National Guard UH-72s at North Las Vegas are Title-32 federal), civilian-contractor LiDAR field-testing program (uniquely Dugway), and the Black Vault's Army CI records on Dugway's 2023 UAP detection exercises.

Open follow-up questions

  1. Identify the site definitively. Cross-reference the Image 1/Image 2 drawings (Dark Kite, Transparent Kite recreations) with the FBI Photo B series mountain silhouettes. Same terrain features?
  2. Check AARO public reporting for any prior reference to "orbs launching orbs" with measurements matching 12-18m diameter at ~1050m — the AARO measurement specificity should be searchable.
  3. What federal agency are USPER1-USPER7 from? Restricted-zone access, NVG-capable, working dusk-to-pre-dawn, two-person teams. Plausible candidates: FBI HRT/SWAT, USMS, ATF, BIA, DoE/NNSA-OSE (Office of Secure Transportation), CBP, USAFOSI Field. Any of these would have FBI/DoD interest.

FBI September 2023 Sighting — Three-Witness Account Reconciled

Catalog labels: "FBI September 2023 Sighting - Serial 3 / Serial 4 / Serial 5" Catalog labeling note: PURSUE catalog has the serial numbers misordered relative to the actual files. File names track real serial numbers. See per-witness section below. Form type: All three are FBI FD-302 (Rev. 5-8-10) "OFFICIAL RECORD" interview reports Date of entry: All three October 2023 (about 1 month after Sept 1, 2023 incident) Cataloged location: "United States" (precise location redacted)

Per-witness account summary

Witness Serial 3 — Female, female senior base official, 15+ yrs aircraft-recognition experience

  • File: serial-3_redacted.pdf (cataloged as "Serial 4" — wrongly)
  • Interview: In-person at Building [redacted] (so FBI came onsite)
  • Background: Has authority to restrict airspace at the base. Long base tenure ("fifteen years working at [redacted]"). "Had seen most of the aircraft and drones used by the US military" through her career.
  • Role on the day: She was the one who had restricted the airspace for the contractors' tests that morning.
  • Perspective: Driver of the lead vehicle; convoy of three vehicles (matches Serial 4's account)
  • Day timeline:
    • 7:02 AM: Contractors received the base's standard entry brief
    • 7:15-7:30 AM: Three-vehicle convoy began driving south to gate
    • Gate malfunction: Tried to open with fob, "gate opened just a little and then closed on three separate tries. On the fourth attempt the gate opened completely and stayed open." No prior or subsequent operational problems with that gate — anomaly only on this morning.
  • Sighting (after gate, while driving through):
    • Looked up and saw a cigar-shaped object with extremely bright light
    • Direction: southwest
    • Altitude: 500-3,000 feet above the nearest tree line (tree line ~1 mile SW of her position per agent note)
    • Object already there when she looked up
    • Almost hovering, slowly moving east to west
    • Bright light: intense diamond-white with what appeared to be a ring around the light
    • Light located on the eastern end of the object, pointing southeast
    • "Looking at the light was like looking into the sun"
    • Object color: "metallic bronze"
    • Length: two to three Blackhawk helicopters lined up nose to tail (~128-192 ft)
    • Width: approximately one and a half Blackhawks (~96 ft); hard to determine due to light obscuring eastern end
    • Completely silent
    • No contrails (clear sky)
    • Initial reaction: annoyance (thought it was violating her airspace restriction), then realized it was not aircraft or drone
    • Watched for 5-10 seconds
    • "Just disappeared"
    • Searched sky after — could not find object again
    • No engine interference noted while object was visible
    • "Felt it left when it saw them" — subjective sense of being noticed
  • Aftermath:
    • Drove on to test site; passenger in second vehicle confirmed they saw it too
    • "Would not have reported the object if she had seen it by herself"
    • "Several of her co-workers subsequently made fun of her due to her report"
  • Documentation: No photos or video taken by witness or contractors

Witness Serial 4 — Male, drone pilot contractor (10-15 hrs flight time as drone pilot)

  • File: serial-4-redacted_redacted.pdf (cataloged as "Serial 5" — wrongly)
  • Interview: Via Facetime video (witness located elsewhere)
  • Background: A drone pilot with 10-15 hours of drone flight experience; working as contractor on the LiDAR project
  • Role on the day: Passenger in lead vehicle (Serial 3's vehicle) — they were together
  • Day timeline:
    • "On [redacted] September [redacted] 2023" (likely Sept 1, 2023, day-redacted)
    • Five people total in convoy: female base official (driver) + this witness as passenger + 3 contractors in vehicles 2 and 3
    • 7:30 AM: Three vehicles began driving south
    • Sun was in the east with good visibility
    • Gate trouble: Confirms Serial 3's gate-malfunction observation independently
  • Sighting:
    • At about three-quarters of the windshield up, saw a linear object with super bright light on east side
    • Light was bright white and bright enough to see bands within the light ← internal structure visible
    • Object color: "metallic / gray" (different from Serial 3's "bronze")
    • Did not have any wings or exhaust
    • Smaller than a 737, one to two Blackhawk helicopters in length (~64-128 ft) (smaller estimate than Serial 3's 2-3 Blackhawks)
    • Definitely bigger than a drone
    • Approximately 5,000 feet above ground level (higher estimate than Serial 3)
    • Moved east to west parallel to the ground
    • Visible 5-10 seconds, then the light went out and the object vanished
    • Sky clear
    • Could not find object again

Witness Serial 5 — Male, in convoy (different vehicle)

  • File: serial 5 redacted_redacted.pdf (cataloged as "Serial 3" — wrongly)
  • Interview: Via Facetime video
  • Role on the day: Behind the lead vehicle (Serial 3 + Serial 4); driver of either the GMC AT4 or sprinter van
  • Day timeline:
    • 9:00 AM (so likely a different reference point — could be later in the morning when the sighting occurred, vs. Serial 3/4's earlier 7:15-7:30 AM gate-passage time)
    • Driving east to test site for LiDAR data acquisition
    • Three vehicles: F150 (lead) + GMC AT4 (with passenger) + sprinter van
    • Drove through "a couple of gates"
  • Sighting:
    • Bright light over the horizon through top-right of windshield
    • Stationary in the air, then started moving to the right, then disappeared
    • Bright white
    • Visible for ten seconds before disappearing
    • Stayed the same size throughout
    • Estimated 10-20 miles away
    • No interference with vehicle
  • Aftermath:
    • Pointed light out to passenger but passenger looked wrong direction
    • Witness was indifferent to the light until first test site
    • At first test site, two other people confirmed they saw it too
    • Working hypothesis at the time: a meteor coming straight toward them, burning up in the atmosphere

Reconciliation

Where the witnesses agree

Detail Agreement
Date September 2023 (specific day redacted in all three)
Convoy structure Three vehicles, ~5 people
Gate malfunction Serial 3 + Serial 4 both report; Serial 5 doesn't mention but doesn't contradict
East-side bright light All three describe a bright light, with shape-perceiving witnesses placing it on the east end
White light color All three
Disappearance pattern All three: object vanished within 5-10 seconds (Serial 4's "light went out, object vanished" gives the most explicit mechanism)
Motion direction Westbound (Serial 3 + Serial 4 explicit; Serial 5 "moved to the right" depending on facing direction could be west)
Silent Serial 3 explicit
No contrails / clear sky Serial 3 + Serial 4
No vehicle interference Serial 3 + Serial 5

Where the witnesses differ

Detail Serial 3 Serial 4 Serial 5
Color Metallic bronze Metallic gray (didn't perceive shape/color)
Length 2-3 Blackhawks (128-192 ft) 1-2 Blackhawks (64-128 ft) (didn't perceive)
Altitude 500-3,000 ft above tree line ~5,000 ft above ground "10-20 miles away" (range, not altitude)
Shape "Cigar shaped" "Linear" "Bright light" only
Light detail "Diamond white with ring around it" "Bands within the light" "Bright white" only
Initial state Almost hovering, slowly moving E→W Already moving E→W "Stationary then moved right"

How the FBI Lab composite was constructed

The catalog blurb describes:

"ellipsoid bronze metallic object materializing out of a bright light in the sky, 130-195 feet in length, and disappearing instantaneously"

Inputs that survive in the composite:

  • "Bronze metallic" ← from Serial 3 (the gray color from Serial 4 is dropped in favor of the more colorful description)
  • "130-195 feet" ← averaging Serial 3's 128-192 ft estimate with Serial 4's 64-128 ft estimate (or biasing toward Serial 3's higher number)
  • "Ellipsoid" ← Serial 3 said "cigar"; Serial 4 said "linear"; an ellipsoid is the formal-geometry compromise between cigar (rounded ends) and linear (long axis)
  • "Materializing out of a bright light" ← all three describe a bright light first; Serial 3's "ring around the light" + Serial 4's "bands within the light" suggest internal structure within the light source
  • "Disappearing instantaneously" ← Serial 4's "light went out and the object vanished" + Serial 5's "just disappeared"

Differences that survive scrutiny

The key debate is between bronze (Serial 3, close-up senior official) and gray (Serial 4, drone pilot contractor). Both close witnesses, both seeing same object same time, different color reports. Possible explanations:

  • Lighting angle: Sun was in east; the object's east end had a bright light. Light angles could produce different surface color appearances at slightly different viewing angles.
  • Color memory differences between witnesses
  • Object reflective surface that genuinely shows different colors depending on viewing angle (e.g., iridescent/dichroic materials)

Serial 3's "ring around the light" detail is unusual — distinctive enough to be retained from a 5-10 second observation. Serial 4's "bands within the light" suggests multiple distinct light sources within what appeared as a unified glow at lower resolution.

What we definitively learned

  1. Multi-witness, multi-perspective corroboration of a daytime UAP at a controlled-access US test site.
  2. Witness with 15 years of military aircraft recognition experience explicitly classified the object as "not an aircraft or drone."
  3. Gate malfunction on the day of incident only — supports an EM-anomaly correlation, though doesn't prove causation.
  4. The FBI took it seriously enough to conduct multiple 302 interviews (in-person + Facetime), produce a Lab composite 8 months later, and release the file 26 months later via PURSUE.
  5. The witness's senior position + 15 years of aircraft expertise are the load-bearing credibility anchor. Her description and measurements drove the FBI Lab composite. Witnesses being "made fun of by co-workers" is consistent with how UAP reports get socially handled even at federal facilities.

Open questions

  • What facility? "Test site," controlled access, LiDAR testing, female senior official with airspace authority, base in a tree-line + open-area environment. Most likely candidate: White Sands Missile Range (NM), Edwards AFB / Plant 42 (CA), Tonopah, China Lake, or a similar major DOD test range with civilian-contractor LiDAR programs.
  • What's the connection to the Western US Event two-day briefing? Both 2023, both Western US, both at federal facilities. Could be same site / different time of day / different week. Or could be different sites in same general region.
  • What's the connection to the USPER 2025 incident? USPER's "mountain range west of SITE CODE NAME" + "cavern entrance" + recurring orb observations sounds like potentially the same general area.

DOW-UAP-D28, Mission Report — Ayn al-Asad / Iraq, 20 SEP 2024 (catalog mis-titled)

Source: https://www.war.gov/medialink/ufo/release_1/dow-uap-d28-mission-report-east-china-sea-2024.pdf Catalog title: "DOW-UAP-D28, Mission Report, Iraq, September 2024" (CORRECT) URL filename + PDF tab title: "East China Sea, 2024" (BOTH WRONG) Actual content location: Ayn al-Asad Airbase, Iraq, ROZ RAINDROP Catalog QA finding: Yet another systematic data-quality error — this one in the URL/file-naming pipeline rather than the metadata pipeline. The catalog title and incident_location were correct; the URL slug used a different (wrong) source and that propagated to the PDF tab title.

Original classification: SECRET//REL TO USA, FVEY Declassified by: MG Richard A. Harrison, USCENTCOM Chief of Staff, 24 October 2025 Approved for AARO release: 10/28/2025 USCENTCOM MDR 25-0100 thru 25-0103 / JS-250710-TM8S Pages: 6 Form type: MISREP

Mission identifying data

  • Operation: INHERENT RESOLVE
  • Domain: AIR
  • Operations Center: 609th CAOC
  • MAJCOM: AFSOC
  • COCOM: USCENTCOM
  • Originator unit: SOTU 016 (Special Operations Task Unit 016)
  • POC unit: 16 SOS (16th Special Operations Squadron) under 27 SOW (Cannon AFB) — AC-130 gunship squadron
  • Mission Type: ARMED OVERWATCH
  • Tasking Order: HM
  • Misrep ID: undefined-10431840

Aircraft + armament

The equipment list confirms this is an AC-130 gunship:

  • Radar: AN/APN-241 (AC-130 nav radar)
  • Targeting pods: MX-20 & MX-25 (electro-optical/IR sensors common to AC-130)
  • Guns: 30MM + 105MM (AC-130 signature armament)
  • Air-to-ground: AGM-176 (Griffin missile)
  • Self-defense: ALR-56M RWR, AAR-47 MWS, AAQ-24B IRCM/ECM, ALE-47 dispenser
  • Chaff: RR180, 716 cartridges. Flares: MJU-71/MJU-66/M206, 240
  • Data Link: GATEWAY

Mission timeline (20-21 SEP 2024 Z-time)

Time Event
201740Z Takeoff from OKAS (Ali Al Salem AB, Kuwait)
201930Z On station, conducting Armed Overwatch IVO 38SKC63
~1930Z Entered AYN AL ASAD AIRBASE (AAAB) Restricted Operating Zone "RAINDROP" to conduct weapons calibration
Released 20x 105mm, 101x 30mm, 1x AGM-176 Griffin (calibration fire)
~2025Z Received CALL FOR FIRE: directed to employ AGM-176 against a target
Weapons release
202027:59Z UAP first observed (Initial Contact DTG)
UAP flew through aircraft sensors between munition release and munition impact
Crew maintained laser energy until munition impacted target
Did not re-observe the UAP
202323Z Off station
210046Z Landed at OKAS
200101Z Engine shutdown
Total mission time: 7 hours 6 minutes; Time on station: 3:53

UAP detail (AARO form fields)

  • Initial Contact DTG: 202027:59ZSEP24
  • UAP Event Type: UAP Incident
  • UAP Event Serial Number: 202027ZSEP2024-CENTCOM
  • UAP Maneuverability Observations: "UAP FLEW THROUGH [redacted] SENSOR IN BETWEEN MUNITION RELEASE AND MUNITION IMPACT"
  • UAP Response to Observer Actions: NONE OBSERVED
  • UAP Reaction to Observation, Interrogation, Engagement: "NONE OBSERVED; PATH OF MOVEMENT APPEARED PREDETERMINED AND NOT IN RESPONSE TO [aircraft]'s DETECTION"
  • Friendly Aircraft Location: 38SKC55 ___ (b)(1)1.4a
  • Friendly Aircraft Altitude: FL130 (13,000 ft)
  • Friendly Aircraft Trajectory: 096 STRAIGHT AND LEVEL
  • Friendly Aircraft Speed: 170 KIAS
  • Observer Assessment of UAP: Benign
  • Observation Interrogation: NO
  • Third-party Observers: "NO PARTIES REPORTED AN ADDITIONAL AIRCRAFT IN THE AIRSPACE WITH [aircraft]"
  • Training Range: YES — AYN AL ASAD ROZ RAINDROP
  • UAP Physical State: SOLID (← critically different from D32's "Plasma")
  • UAP Signatures: "IR SIGNATURE DETECTABLE BY MX-20 & MX-25"
  • UAP Advanced Capabilities And/Or Materials: NONE OBSERVED
  • UAP Effects on Persons: NO
  • UAP Effects on Equipment: NONE
  • UAP Objects/Material Recovered: NO
  • First Coordinate: 38SKC59 ___ (b)(1)1.4a
  • Last Coordinate: 38SKC59 ___ (b)(1)1.4a
  • First Accuracy: Precise
  • Last Accuracy: Precise (note: First and Last Accuracy are PRECISE, not Estimated like D32 and D75 — this is a high-confidence sensor track)
  • UAP Date of DoD Acquisition: 210000:00ZSEP24

UAP description (gentext)

"UAP CREATED IR LENS FLARE ON MX-20 & MX-25 SENSORS, INDICATING A SIGNIFICANT HEAT SOURCE. THE UAP MOVED AT A HIGH RATE OF SPEED THROUGH THE SENSOR FIELD OF VIEW. THE CREW MAINTAINED LASER ENERGY UNTIL THE MUNITION IMPACTED ITS DESIRED TARGET. [aircraft] DID NOT REOBSERVE THE UAP."

UAP Anomalous Characteristics/Behaviors

"IT IS UNKNOWN AT THIS TIME WHETHER AN OBJECT DETACHED ITSELF FROM THE PRIMARY UAP IMMEDIATELY BEFORE LEAVING THE SENSOR FIELD OF VIEW."

UAP Event Description (gentext)

"[aircraft] ENTERED AYN AL ASAD AIRBASE's (AAAB) RESTRICTED OPERATING ZONE (ROZ) RAINDROP AT APPROXIMATELY 1930Z TO CONDUCT A WEAPONS CALIBRATION. [aircraft] RECEIVED A CALL FOR FIRE AT APPROXIMATELY 2025Z TO EMPLOY AN AGM-176. AFTER WEAPONS RELEASE, THE WEAPONS SYSTEMS OFFICER (WSO) AND COMBAT SYSTEMS OFFICER (CSO) OBSERVED AN UNIDENTIFIED OBJECT 'FLY' THROUGH THE AIRCRAFT SENSORS AT A HIGH RATE OF SPEED. THE UAP CREATED AN IR LENS FLARE ON THE MX-20 & MX-25 SENSORS, WHICH INDICATED A SIGNIFICANT HEAT SIGNATURE COMING FROM THE OBJECT. IT IS UNKNOWN AT THIS TIME WHETHER AN OBJECT DETACHED ITSELF FROM THE PRIMARY UAP IMMEDIATELY BEFORE LEAVING THE SENSOR FIELD OF VIEW. THE CREW MAINTAINED LASER ENERGY UNTIL THE MUNITION IMPACTED ITS DESIRED TARGET. [aircraft] DID NOT REOBSERVE THE UAP."

Key analytic points

  1. AC-130 gunship in active fire mission. This isn't a passive ISR observation — this is a strike asset mid-engagement. Griffin missile in flight when the UAP appeared.
  2. Solid object, not plasma. D32 (Syria) classified its UAP as plasma. D28 (Iraq) classifies as Solid. Different physical-state assessments by the AARO form.
  3. IR lens flare = significant heat signature. Hot enough to bloom an MX-20/MX-25 sensor — that's a genuinely thermal source, not a sensor artifact.
  4. Possible "object detachment" event. The crew couldn't confirm but flagged the possibility that a smaller object detached from the primary UAP just before it exited frame. This is the same morphology as the Western US Event "Orbs Launching Orbs" category.
  5. Predetermined flight path. "Path of movement appeared predetermined and not in response to [aircraft]'s detection" — explicit aircrew assessment that the UAP wasn't reacting to them. Counters reflexive "drone reacting to its operator" explanations.
  6. Precise track accuracy. Both First and Last accuracy fields are "Precise" (not "Estimated" like D32 and D75). The sensor lock was good enough that the coordinates aren't a guess.
  7. Critical timing. UAP transited DURING a live air-to-ground engagement. Crew did not break off lasing. Munition still hit target. Operationally consequential UAP encounter that did not impact mission completion — but a future incident at slightly different timing could.

Catalog data-quality finding

PURSUE has at least three layers of metadata for each record:

  1. The CSV catalog (title + incident_location + incident_date)
  2. The URL slug / filename
  3. The PDF document's internal title bar

For D28, layer (1) is correct ("Iraq, September 2024"), but layers (2) and (3) say "East China Sea, 2024." This indicates the URL/filename pipeline was fed from a different source than the catalog. The mistake propagates to anyone who reads the file name first and assumes it's authoritative.

This is distinct from the D51 / Mexico Cable error class, where layer (1) had a 20-year typo. D28's layer (1) is right; layers (2)/(3) are wrong. So PURSUE has at least two distinct data-quality bugs at play:

  • Bug A: Email-correspondence-header bleed into incident_date / incident_location (D51, Mexico Cable)
  • Bug B: Filename slug derived from a non-authoritative source (D28)

Treating the URL slug as authoritative when it conflicts with the title would be wrong for D28 — the document content settles it (Ayn al-Asad Iraq, not East China Sea).

Cross-references

  • D32 Syria Oct 2024 (plasma ball): Same MAJCOM (AFSOC), same MDR series, declassified same day. Different sensor outcome (plasma vs. solid IR-lens-flare).
  • Western US Event 2023 "Orbs Launching Orbs": D28's possible-detachment language matches the 2023 Western US Event's signature observation. AARO has documented this morphology in multiple contexts.
  • Ayn al-Asad airbase: Site of multiple Iranian ballistic missile attacks (Jan 2020 retaliatory strike for Soleimani; 2024 Houthi/Iran-aligned drone attacks). The base sees high-tempo air ops including AC-130 gunship operations from Cannon-deployed units.

Open follow-up questions

  1. Identify the AGM-176 target. ROZ RAINDROP at Ayn al-Asad is set up for friendly weapons calibration, but the "call for fire at 2025Z to employ AGM-176" suggests an actual TIC (troops in contact) or strike task. What was being struck? An ISIS-aligned target near AAAB? An Iran-aligned militia position?
  2. The AC-130's MX-20/MX-25 footage from this event may be among the 28 PURSUE videos — search for D28's paired PR-series record.
  3. Compare to PR31 (D32 Syria) video. If D28 has video footage in the release, side-by-side viewing of plasma-ball-glare (D32) vs. solid-IR-flare (D28) would show how AARO's "physical state" classification correlates with sensor signature.
  4. Add D28 to the catalog QA bug class (filename-vs-title mismatch) as the canonical example of Bug B.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment