THE DOCUMENT
This briefing covers one continuous written record from the U.S. Department of War’s PURSUE Release 03, published at war.gov/ufo, cleared 12 June 2026, released in two parts. DOW-UAP-D087 (“Analysis of Flying Objects in the US, pages 1-100”) holds incident summaries 1 through 100; DOW-UAP-D088 (“Analysis of Flying Objects in the US, pages 101-172”) continues with incidents 101 through 172. It is a US Air Force compilation of unidentified-flying-object incident summaries, headed on each page “Check-List - Unidentified Flying Objects”, forwarded from the Air Materiel Command at Wright Field, Dayton, and bearing a Navy receipt stamp dated February 1950. The two files are the same document, split at incident 100.
Why this one is worth your time
This is one of the bulkier items in Release 03, and at first glance it looks like a single long study. It is something more concrete: a register. Across roughly a hundred and seventy entries the US Air Force recorded report after report of unidentified flying objects, each one logged against the same fixed list of questions, the same form repeated for every observer, so that one sighting could be set beside the next on identical terms. Many entries carry a short analyst note proposing what the object might have been. Read end to end, the document shows the Air Force trying to make a mass of disparate sightings comparable by forcing each into a standard shape. This briefing sets out what that compilation contains, how it is organised, what it does and does not state as a conclusion, and is plain about the quality of the scan.
What the document says
What kind of document this is. It is a compilation, not a narrative report. The Air Force gathered individual unidentified-flying-object reports and entered each as a standalone summary on a recurring form headed “Check-List - Unidentified Flying Objects”. The entries are numbered, running from incident 1 in DOW-UAP-D087 to incident 172 in DOW-UAP-D088, with the two files joined at incident 100. The cover and routing pages show the set being forwarded as “Incident Summaries of Unidentified Flying Objects” from the Air Materiel Command at Wright Field and received elsewhere in early 1950. The document is the working product of the early Air Force effort to collect and sort flying-object reports, rather than a finished public study with a single thesis.
The method: one fixed form per observer. Every entry answers the same numbered list of fields about a single observer’s report. The fields run, in order, through the date and time of the sighting; the location; the name, occupation and address of the observer and the place of observation; the number of objects; the distance of the object from the observer; the time in sight; the altitude; the speed; the direction of flight; the tactics; the sound; the size; the colour; the shape; any odour detected; the apparent construction; any exhaust trails; the weather conditions; any effect on clouds; any sketches or photographs; the manner of disappearance; and finally remarks. Where the observer could not supply a value the field is marked not stated. A single incident can run to several lettered sub-entries (for example 1, 1a, 1b, 1c) when more than one witness reported the same event, each witness logged on a separate form. The effect is that a balloon report, a meteor report and an unexplained report are all recorded against the identical template.
What the entries record. The summaries cover a wide spread of reports. Early entries include the well-known July 1947 sightings around Muroc Army Air Field in California, logged from several service-member observers; later entries range across the United States and beyond, including, in the second part, a 1948 meteor over northern Kansas recorded with the photograph of its vapour trail and the recovery of meteorite fragments, and a report by an American newspaper reporter of a long, narrow, brightly shining object seen northwest of Moscow. The recorded descriptions vary widely: discs and spheres, lights, long narrow shapes, objects “shining” or silver or bluish-white, silent or with no sound stated, at altitudes from a few thousand feet to tens of miles, some performing turns or circles, many simply disappearing into the distance. The document records what each observer said, field by field, in the observer’s own terms.
The analyst comments and references. Many entries are followed by a short analyst note, headed “Comment”, and sometimes a “Reference” line. In these notes the compiler offers a possible prosaic identification or weighs the report: a meteor, a balloon, an aircraft seen under unusual light conditions, and so on, often hedged. One representative comment, on the Moscow report, records that the object might have been a meteor, that its speed seemed insufficient for a guided missile, that it could have been a jet or conventional aircraft made to look unusual by light conditions and foreshortening, and that a dirigible could not be excluded. The comments are the analytical layer of the document: per-incident assessments attached to individual reports, recorded as the compiler’s own notes.
What it offers as a conclusion. The analysis in this document sits at the level of the individual entry. Each report is logged, and many carry an analyst’s comment proposing a candidate explanation or noting that none can be settled. The compilation as released here does not close with a separate overall summary, finding or recommendation across all 172 incidents; it ends at the last incident. Whatever conclusions it states are the per-incident comments, not a single verdict on the phenomenon as a whole.
What the document does not say
It does not, in the portion released here, deliver an overall conclusion about unidentified flying objects. It is organised as a register of individual reports with individual comments, and it stops at incident 172 without a closing assessment across the set. Readers looking for a single bottom-line finding will not find one stated in these pages.
It does not, for most entries, resolve what was seen. Where an analyst comment proposes a meteor, a balloon or an aircraft, it frequently does so as a possibility and hedges it; many fields in many entries are marked not stated; and a number of entries record the report without offering any identification at all. The document preserves these as logged, unresolved or only tentatively explained.
It is a scan of typewritten records and is unevenly legible. The pages are old carbon and typescript, photographed for declassification, and the machine-extracted text of both parts is heavily corrupted in places. Some entries read cleanly; others are broken by scanning noise. This briefing summarises what can be read with confidence and does not reconstruct passages that cannot.
It does not establish what any observer saw. The descriptions are the observers’ own, recorded as reported, with the analyst comments added separately. The document does not independently verify any sighting; it collects and sorts the reports.
From the record
Check-List - Unidentified Flying Objects The running header on every incident page of the compilation (read from the page image; see notes)
Where the case connects
This compilation is the Air Force’s own running collection of the same reports that the later, better-known studies drew on. Briefing R3-07 covers Project Blue Book Special Report No. 14, the large statistical study that classified and tabulated several thousand Air Force sightings; the check-list seen here is an earlier, rawer form of the same impulse to standardise and sort. Briefing R3-06 covers the 1953 Robertson Panel, the scientific advisory panel convened to review the Air Force’s accumulated sighting data and recommend what to do about it; this document is an example of the kind of case material that such reviews assessed. Briefing R3-04 covers the earliest Army, Navy and FBI handling of flying-disc reports, including the Navy directive that asked for exactly this kind of reporting; this Air Force compilation is the body of reports that the reporting machinery produced. Briefing 1 of Release 01 covers PURSUE and the tier system.
The document also leaves its own loose ends. It is presented here as incidents 1 through 172, but it carries no overall conclusion in these pages; any covering analysis, index or summary that accompanied it in the original files is not part of these two PDFs. The per-incident comments cite “references” that are not reproduced here. Names and details are redacted in places, and parts of the scan are illegible. Any later tranche that releases a cleaner scan, the accompanying summary, or the cited reference material lands in this series when it does.
Read it yourself
DOW-UAP-D087 (“Analysis of Flying Objects in the US, pages 1-100”) and DOW-UAP-D088 (“Analysis of Flying Objects in the US, pages 101-172”), the two parts of one US Air Force compilation, are hosted at war.gov in PURSUE Release 03.
Read the file. Decide for yourself.
Related wiki entries
The wiki entries below give background on the programme and the publisher behind this briefing.
References and further reading
- Primary document: DOW-UAP-D087, “Analysis of Flying Objects in the US, pages 1-100”, PURSUE Release 03, U.S. Department of War, hosted at war.gov/ufo
- Primary document: DOW-UAP-D088, “Analysis of Flying Objects in the US, pages 101-172”, PURSUE Release 03, U.S. Department of War, hosted at war.gov/ufo
- Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
- AARO UAP Records, All-domain Anomaly Resolution Office, aaro.mil/UAP-Records
- Briefing R3-07 in this series, on Project Blue Book Special Report No. 14
- Briefing R3-06 in this series, on the 1953 Robertson Panel
- Briefing R3-04 in this series, on the first official Army, Navy and FBI studies of 1948-1949
- Briefing 1 of Release 01, on PURSUE and the evidence tier system