United States.PURSUE · rocketry reference documents (launch failures, PURSUE)

Not every document the PURSUE system labeled 'UAP' in its first tranche of May 8, 2026 is a sighting report. Two of them, catalogued as DOW-UAP-D48 and DOW-UAP-D49, are USAF technical reports whose content is aerospace engineering, not anomalous phenomena. The corpus gathers them in a single file precisely to make explicit that distinction, which the common label tends to erase.

The first, DOW-UAP-D48 (September 10, 1996), is a 'Department of the Air Force Report' devoted to modeling unlikely space-booster failure modes in risk calculations: it documents launch-failure histories and recommends corrective actions through novel modeling techniques. The second, DOW-UAP-D49 (February 3, 2000), is a Vandenberg Air Force Base 'Launch Summary' that summarizes the historical record of launches conducted there between 1958 and 2000. Neither describes an unidentified object; both are rocketry and range-operations references.

Their inclusion under the 'DOW-UAP' designation is better understood by their explanatory function than by their content. A significant fraction of UAP reports —especially those observed near test ranges, coastlines with space activity or reentry corridors— correspond to rocket launches, stage separations, on-orbit fuel venting, controlled reentries or booster failures, phenomena that produce conspicuous lights, trails and trajectories easily confused with anomalous objects. Documents like these two are the reference pieces with which an analyst rules out that family of causes. That is why they appear in the same body of files as the sightings: they are part of the resolution apparatus, not the catalog of mysteries.

This file's usefulness is methodological and almost pedagogical: a reminder that 'appearing in the UAP archive' is not the same as 'being a UAP'. PURSUE's administrative label groups, under the DOW-UAP designation, both sighting reports and technical reference material; treating both as equivalent —counting every PDF in the release as a 'case' of anomalous phenomenon— is a frequent reading error in coverage, and these two documents are the cleanest counterexample. Their anomaly probability is, for practical purposes, nil: they are rocket-reliability calculations and a launch history.

That said, their value to the corpus is real and twofold. First, they make the resolution apparatus visible: the less glamorous but more substantive side of any serious UAP-study program is the library of known mundane causes —rocketry, balloons, air traffic, atmospheric phenomena— against which reports are checked. That the state releases these materials alongside the sightings confirms that the 'unidentified' category is, in large part, a problem of pending identification, not of exotic technology. Second, they empirically anchor the corpus's mundane narrative: many coastal and range cases that resolve into launches or reentries find their documentary substrate here. The file enters as a tier-B document-case with a deliberately low anomaly probability, not because its content is weak, but because its content is, quite intentionally, prosaic: it is the rule against which the exception is measured. Distinguishing the report of the phenomenon from the technical reference that explains it is, at bottom, the minimal discipline separating a reasoned catalog of anomalies from a pile of PDFs unified only by a common administrative label. These two documents, prosaic by design, are the permanent reminder of that boundary: they belong on the side of known causes, and the corpus keeps them there, navigable and correctly sourced, as part of the toolkit with which mystery is resolved —not multiplied—.