PURSUE Record — 38_143685_box_Incident_Summaries_101-172

Released as part of the May 8, 2026 PURSUE Release 01 declassification, document 38_143685_box_Incident_Summaries_101-172 is a single-part PDF originating from the U.S. Department of War. It is an archival compilation — not a single incident report — collecting standardized UAP case summaries numbered 101 through 172. That means this one file contains material spanning 72 discrete incidents, each processed through an identical bureaucratic intake form. It is one of 120 PDFs in the release and arguably one of the more structurally significant: a window into how systematically the U.S. military was documenting aerial anomalies during an earlier era.

What this record contains

The Department of War's release entry for this document is spare by design. No incident date is listed, no geographic location is specified, and no individual case is singled out in the public metadata. What is confirmed: this is a single-part PDF, released May 8, 2026, classified under archival identifier 38_143685, described as originating from a physical archive box. The official description blurb states that "each of these incident summaries includes a 'Check-List — Unidentified Flying Objects' that contains details about the incident. Many summaries also include witness lists or statements and other narrative reports or descriptions." That checklist format is the key detail. It points to a standardized intake protocol — a form-driven process that required observers and investigators to answer the same structured questions across every case.

The range "101–172" refers to the sequential numbering of summaries within the box, not case identifiers from a master database. Seventy-two individual summaries, each potentially carrying its own witness statement, narrative description, and completed checklist, are bundled here into a single PDF as they were likely stored together in a physical archive container. The public release does not include a case-by-case breakdown or index of those 72 incidents beyond what the description blurb conveys.

Historical & documentary context

The "Check-List — Unidentified Flying Objects" form is a document type directly associated with the U.S. Air Force's formal UAP investigation programs of the late 1940s through late 1960s — most prominently Project Blue Book (1952–1969), which itself followed Project Sign (1947–1949) and Project Grudge (1949–1952). These programs mandated that military personnel use standardized reporting forms when documenting aerial phenomena they could not immediately explain. The checklist format was intentional: by forcing observers through the same set of questions — object shape, duration, flight path, atmospheric conditions, number of witnesses — analysts could compare cases across geography and time without relying solely on freeform narrative. The "box" terminology in the title is archival language for a physical storage container, meaning this PDF was almost certainly digitized from a bound or loose-leaf collection held in a numbered box within a federal records repository.

The inclusion of witness lists and narrative statements alongside the structured checklists reflects the investigative posture of the era. These were not purely bureaucratic forms — the programs actively sought corroborating testimony, and many summaries that survive from this period include signed statements from military pilots, ground radar operators, and civilian observers. The 1947–1968 window was one of extraordinary institutional attention to UAP: Cold War anxieties about Soviet aircraft, ballistic missile technology, and atmospheric surveillance programs created a genuine operational incentive to identify unknown objects, not merely catalog them.

What this does and does not prove

What the document establishes, based on the metadata alone, is that 72 incidents were formally logged, assigned summary numbers, and processed through a standardized investigative intake protocol by U.S. military personnel. That is a documented institutional fact. What it does not establish — and what the public release metadata cannot tell us — is the resolution status of any individual case within the batch, the time period covered, the geographic distribution of incidents, or whether any of the 72 were subsequently explained. The PURSUE release as a whole is investigative material, not a verdict. Cases marked as resolved (balloon, birds, sensor artifact) appear alongside unresolved ones to demonstrate analytical discipline, not to sensationalize. Without reviewing the full PDF, it is not possible to characterize the contents of any single summary within this batch, and nothing in the public metadata supports claims about anomalous phenomena beyond the fact that the incidents were, at the time of logging, unidentified.

How it fits PURSUE Release 01

This document belongs to the historical archive tier of PURSUE Release 01 — the layer of the release drawn from digitized military records predating the modern AARO era. Alongside other PDF compilations in the 120-document PDF subset, it provides the longitudinal backbone of the release: evidence that systematic UAP documentation was not a post-2017 phenomenon but an institutional practice with roots in the earliest years of the Cold War. Taken together with the contemporary Department of War mission reports and sensor video files also present in the release, records like this one are what make PURSUE Release 01 a cross-era archive rather than simply a snapshot of recent military sensor data. Further context on how this document sits within the full 162-item release is available in SkyLens PURSUE coverage.

Editorial note: This analysis is independent commentary on a publicly released document. The original record, source links, and full release metadata are catalogued on the SkyLens UAP files page alongside every other case in the PURSUE Release 01 set.