DOW-UAP-D7, Mission Report, Arabian Gulf, 2020

Evidence media

• Official PDF: Open Sky release-file view

Page 6 is the only substantive visible page in the released PDF. The render shows redacted form text and the GENTEXT/UAP block describing a balloon-like UAP, movement with the winds at 31,000 FT MSL, and a TFLIR visual-identification reference; it is a source-document page render, not an object image, map, radar plot, or sensor frame.

Investigation reading

This Release 01 item is a short, heavily redacted six-page MISREP-style PDF. The useful public content is concentrated on page 6. Pages 1 through 5 render as full-page black redaction/withholding pages with only the visible 1.4(a) marking. Page 6 contains redacted form material and a visible GENTEXT/UAP block.

The visible GENTEXT says the UAP description was: “LOOKS LIKE A BALLOON, SIMILAR TO PREVIOUSLY REPORTED UAP FROM 48FW.” The event text says an observer “OBSERVED A WEAPONS QUALITY 1 TRACK OF A UAP TRAVELING WITH THE WINDS AT 31,000 FT MSL IVO 323'S.” A redacted party then “WAS ABLE TO MAKE A NEXT TO SHOOT ON THE TRACK AND VISUALLY ID THE UAP IN THE TFLIR.” The official manifest summarizes the same point more plainly: a military operator reported a balloon-like UAP traveling with the winds at approximately 31,000 feet and visually tracked it via onboard infrared sensor.

That is the source-backed reading only. The page does not contain a released infrared frame, map, radar plot, photograph, video still, or underlying track display. The balloon-like description and “traveling with the winds” language are important prosaic-check leads, not a completed identification.

What the file appears to contain

The file is therefore documentary/form evidence rather than released visual evidence. It references tracking and TFLIR viewing, but the released PDF does not show the track, target-pod image, or any instrument display.

Source custody and provenance

• Official PDF: https://www.war.gov/medialink/ufo/release_1/dow-uap-d7-mission-report-arabian-gulf-2020.pdf
• Open Sky release-file copy: /api/explore/war-gov/release-file/war-gov-dow-uap-d7-mission-report-arabian-gulf-2020-6fc64196
• Official CSV row: 72
• Agency: Department of War
• Release: PURSUE Release 01
• Source type: PDF
• File size reviewed: 27,337 bytes
• Page count reviewed: 6
• SHA-256 verified: c4cae44b6ac7b4f4916ddff140d47b1e2a6ddc80ed72985877c07401d17fd76a
• PDF metadata title/subject: DOW-UAP-D7, Mission Report, Arabian Gulf, 2020
• CSV incident date/location fields: N/A; the Arabian Gulf, 2020 label comes from the release title and file name.

Text extraction and rendered-page review agree on the basic structure: the first five pages are redaction-only, and the sixth page carries the visible GENTEXT/UAP block. The PDF image inventory does not show embedded image objects.

Graph context

Open Sky currently models this item as both a Release 01 record and a linked PDF asset. The asset record has 31 extracted claim records, 23 entity mentions, 0 extracted sensor-event records, and 0 extracted table rows. The useful extracted claims mostly repeat the same source text: balloon-like description, movement with winds at 31,000 feet MSL, TFLIR visual identification, Arabian Gulf/2020 title context, Department of War/AARO provenance, and redaction limitations.

Related graph links to other Release 01 documents should be treated as navigation and source-custody context only. The current relationship set includes the D7 manifest record and a non-current D8 manifest-file relation; that does not establish a shared event or finding for D7. The absence of a sensor-event record is consistent with the released PDF: it mentions TFLIR/track language but does not release raw sensor imagery or a plotted return.

Leads to check

• Locate any associated display tape, TFLIR frame, or track record referenced by the GENTEXT; none is visible in this released PDF.
• Clarify the redacted actor/action around the phrase rendered as “MAKE A NEXT TO SHOOT ON THE TRACK,” because the released page leaves the operational sequence incomplete.
• Identify what 323'S refers to in context and whether it is a location, track, unit, or mission-specific shorthand.
• Compare this with the “previously reported UAP from 48FW” noted in the source text; that phrase points to a possible related reporting chain, not a conclusion.
• If a date/time becomes available from an unredacted source or adjacent record, check winds at approximately 31,000 FT MSL in the Arabian Gulf area before escalating beyond a balloon/prosaic lead.

Lead check notes

• Checked — release-file and visible page content: The Open Sky release-file copy matches the expected D7 PDF SHA-256 and page count. The page-6 render confirms that the public source has redactions plus the GENTEXT/UAP text only; it does not release an object photograph, video still, map, radar scope, or track display.
• Partial — TFLIR / track source trail: Current release metadata for row 72 exposes the PDF only, with no DVIDS video or separate still/media pairing. The report text references a weapons-quality track and TFLIR visual identification, but the raw track, TFLIR frame, display recording, or sensor-log packet remains missing from released sources.
• Partial — 48FW related-report chain: Exact searches of the linked Release 01 text corpus found 48FW, PREVIOUSLY REPORTED UAP FROM 48FW, WEAPONS QUALITY 1 TRACK, 323'S, NEXT TO SHOOT, and 31,000 FT MSL only in this D7 text. The broader phrase LOOKS LIKE A BALLOON appears in a few other Release 01 files, but without the D7-specific 48FW / 31,000-foot / 323'S anchors, so it does not by itself identify the prior report.
• Needs external source — redacted operational wording: The page render supports the OCR reading MAKE A NEXT TO SHOOT ON THE TRACK, but redaction leaves the actor, exact action, and meaning unclear. An unredacted MISREP, operator notes, or source-system log is needed before rewriting that phrase as a resolved operational step.
• Blocked — wind/prosaic checks: The source-backed balloon/wind lead is important, but the release provides no public date, time, precise location, platform geometry, or unredacted coordinates. Winds near 31,000 FT MSL, ordinary balloon traffic, and other environmental checks remain blocked until those source details are available.

Deep investigation — graph + web reconnaissance

Source reread and media check

• The verified source is a six-page, copy-restricted PDF with title/subject DOW-UAP-D7, Mission Report, Arabian Gulf, 2020, size 27,337 bytes, and SHA-256 c4cae44b6ac7b4f4916ddff140d47b1e2a6ddc80ed72985877c07401d17fd76a. The PDF has no embedded image objects; its public evidence value comes from the page text and redaction pattern, not from a released still, map, sensor frame, or radar plot.
• A direct WAR.GOV range request to the official PDF returned 206 Partial Content with Content-Range: bytes 0-63/27337, matching the reviewed bytes. Direct official HEAD/landing/CSV/thumbnail probes returned 403 access responses during this check, so the strongest public custody anchors are the exact official URL, the matching release-file copy, the verified hash/size, and the successful official range response.
• The rendered page-6 review confirms the visible GENTEXT/UAP block: LOOKS LIKE A BALLOON, SIMILAR TO PREVIOUSLY REPORTED UAP FROM 48FW; a WEAPONS QUALITY 1 TRACK; movement WITH THE WINDS AT 31,000 FT MSL; and visual identification IN THE TFLIR. The phrase rendered as MAKE A NEXT TO SHOOT ON THE TRACK remains visibly present but operationally ambiguous because the actor/action immediately before it is redacted.

Graph connections and extraction quality

• Neo4j read-only checks matched the exact D7 asset by official URL, title, and full_download_sha256. The semantic layer currently has 31 machine-extracted Claim nodes, 23 EntityMention nodes, and 0 SensorEvent nodes for this asset. The extracted claims are still machine_extracted_needs_human_review / not_a_finding; they mostly repeat the source text and release manifest rather than adding independent corroboration.
• Direct graph neighbors include the D7 release record, the official source node, a secondary UFO-USA GitHub markdown conversion, and row/manifest relationships that can point at nearby D8/D63 records through stale or non-current file fields. Those links are provenance-navigation and cleanup leads only; they do not establish that D7 shares an event with D8, D63, or the secondary conversion.
• Exact phrase checks found the 48FW, WEAPONS QUALITY 1 TRACK, 31,000 FT MSL, 323'S, and NEXT TO SHOOT anchors only in the D7 official OCR/chunk and the derived UFO-USA conversion of the same file. Broader ATFLIR/TFLIR checklist language appears in other Release 01 reports, but without the D7-specific 48FW and 31,000-foot wording.

External provenance and official-source checks

• The cached official CSV snapshots preserve the same title, Department of War agency, redaction flag, N/A incident date/location, PDF URL, thumbnail URL, and description blurb. Row references differ by snapshot/line counting, so the stable identifiers for this page are the exact title, official PDF URL, SHA-256, and 27,337-byte size rather than a single line number.
• Internet Archive availability for the exact official PDF URL reports an archived 200 snapshot at timestamp 20260508200703. That supports the public availability trail for the same WAR.GOV URL, but it is provenance support, not a source expansion.
• The release CSV fields show no DVIDS video ID or separate video/still pairing for D7. DVIDS API search without an API key was not usable, and Defense/AARO search probes returned access-denied responses, so no public companion media or agency explainer was added from web reconnaissance.

Prosaic checks, follow-up leads, and limits

• The first prosaic lane is the source's own wording: balloon-like appearance plus movement with winds at about 31,000 FT MSL. Before escalation, a future reviewer needs unredacted date/time, precise location, platform track, look direction, altitude reference, and meteorological upper-air winds; only then can balloon traffic, weather, military training, aircraft, launch/satellite, or other environmental correlations be tested responsibly.
• WEAPONS QUALITY 1 TRACK and TFLIR show that a track and onboard infrared viewing are referenced, but no raw track, display tape, TFLIR frame, telemetry, or sensor log is released here. The released evidence therefore preserves a report of tracking/visual identification; it does not provide the underlying instrument product needed to measure object size, range, speed, or identity.
• Audit status: this section adds source/graph/web provenance and prosaic-check context only. It does not create a finding, hypothesis, or resolution decision, and it leaves the machine-extracted graph claims as unreviewed until a human reviewer can compare them against source text or additional official material.

Limits

This draft does not identify the object and does not resolve the event. The official release provides no public incident date, no precise public location, no unredacted observer identity, and no released still/video/sensor display. Five of six pages are effectively unavailable due to redaction. The visible text is enough to preserve the report, the balloon-like description, the altitude/wind language, and the TFLIR reference, but not enough to adjudicate cause.

All structured graph claims for this page remain investigation context. They are not findings, and the page should stay in graph_investigation_draft / needs_human_review / not_a_finding status until a human reviewer or additional source material supports a stronger conclusion.

Sources

• Department of War, PURSUE Release 01 PDF: https://www.war.gov/medialink/ufo/release_1/dow-uap-d7-mission-report-arabian-gulf-2020.pdf
• Open Sky release-file route: /api/explore/war-gov/release-file/war-gov-dow-uap-d7-mission-report-arabian-gulf-2020-6fc64196
• PURSUE Release 01 CSV record row 72 as modeled in Open Sky source custody.
• Open Sky OCR/semantic graph context for DOW-UAP-D7, Mission Report, Arabian Gulf, 2020.