DOW-UAP-D51, Email Correspondence, Pacific Time Zone, March 2023

Evidence media

• Official PDF: Open Sky release-file copy · official/source URL.
• Derived page renders from the official PDF:
  • 
  • 
  • 

These renders show source-document pages, not object imagery. The PDF contains correspondence, redactions, and a summarized reported-observation text; pdfimages found no embedded image objects, and the release row does not expose a paired DVIDS video or still image.

Investigation reading

This released file is a short, redacted PDF correspondence packet about handling an unclassified summary of a reported UAP incident. It is not the underlying mission report, not the full IIR, and not a sensor or imagery exhibit. The visible thread shows an information-disclosure/classification-review exchange: a requester asks about using an unclassified summary because full IIR declassification would be slow, and the reply approves use of the provided summary at the unclassified level.

The substantive UAP description appears on pages 4-5. Rendered-page review and selectable text show that the summary describes a civilian report from the Pacific Time Zone in March 2023, at night, with an approximate duration of eight minutes. The reported object is described as a large, blue, featureless triangular object with a solid, unwavering silhouette and powerful "whitish blue" light from multiple points along its perimeter. The report says the object was near silent, hovered above or near a national-security facility for roughly three minutes, moved higher in the observer's field of view, and appeared to move backward in a "jerking" or "jumping" way that the reporter considered unlike smooth jet propulsion.

The file should be read as source-preserved testimony and release correspondence. It does not resolve what was observed. It also records negative or missing-characteristic fields: altitude and speed are not reported; material is not reported; the observer did not know how the object was controlled, what propulsion it used, or whether it had a front or rear.

What the file appears to contain

The PDF contains no visible object photograph, no map, no radar plot, no sensor frame, and no embedded video still. pdfimages found no embedded image objects. The visible evidence in this release item is text correspondence plus the summarized reported-observation language.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/dow-uap-d51-email-correspondence-pacific-time-zone-march-2023.pdf
• Open released file: war-gov-dow-uap-d51-email-correspondence-pacific-time-zone-march-2023-71758de4
• SHA-256: f21f4ae91e51810bfa8a6fce6c422f2bbf99c6277871846c642f987954c042f6
• File type and size: PDF, 76,470 bytes.
• Page coverage: 6 PDF pages; current OCR text reports 6 page markers with text on 5 pages.
• Release row: CSV row 58 in Release 01.
• Agency: Department of War.

Two provenance issues need cleanup before this item is used in cross-case analysis. First, the visible title and URL identify this as DOW-UAP-D51, while embedded PDF metadata reports title/subject DoW-UAP-D29. Second, the released page body and title point to March 2023, while a structured release-record date field surfaced as 3/23/26; that date should be checked against the source CSV and any revised manifest fields.

Graph context

The graph has a primary PDF-asset document record for this file and a separate Release 01 record tied to the current row. The semantic layer currently lists 33 extracted claims, 18 entity mentions, 0 sensor events, and 0 table rows for this item. Those claims are useful as a navigation layer, but the source itself is still a short redacted correspondence packet.

The most important extraction-quality issue is page 4 wording. Rendered-page and selectable-text review read "solid, unwavering silhouette" and "powerful "whitish blue" light from multiple points along its perimeter." Some OCR-derived graph text has surfaced a different phrasing, such as "unmoving" and "pulsing" blue light. That should be treated as an OCR/extraction review issue, not as a separate witness claim.

No released sensor record is present here. The phrase "Obtained by: Personal cellular device" appears in the summary, but the released PDF does not include the cellular media, an image frame, metadata from a phone, or the underlying IIR attachment in readable form. Related graph links to other Release 01 records should be treated as navigation/provenance context unless a human review confirms a substantive connection.

Leads to check

• Locate the underlying IIR, draft report, and any personal-cellular-device media referenced by the correspondence, if those were separately released or can be requested.
• Verify the date mismatch between the title/body March 2023 and the structured release-record field that surfaced as 3/23/26.
• Correct or annotate the graph/OCR discrepancy on the page 4 appearance language: unwavering / powerful "whitish blue" light from multiple perimeter points versus OCR-derived variants.
• Determine whether the national-security facility, exact observation time, and more precise location remain withheld or are available in another release item.
• If authorized details become available, run ordinary context checks before escalation: aircraft traffic, drone activity, astronomy, weather/visibility, local lighting, and possible camera/phone-artifact explanations.

Lead check notes

• Blocked — underlying IIR, draft report, and phone media: page 5 says the IIR and draft report are attached, and page 4 says the observation was obtained by personal cellular device. The released PDF itself has no embedded files, no embedded image objects, and no video/still pairing in the Release 01 row, so the underlying report and phone media remain missing from this Open Sky release-file copy.
• Checked — date/provenance mismatch: the official title, URL, and visible page 4 event summary support March 2023; the current Release 01 CSV row still stores Incident Date: 3/23/26, and the embedded PDF metadata title/subject reads DoW-UAP-D29. Treat this as release-metadata tension until an official manifest correction or source-history note resolves it.
• Checked — page 4 wording: selectable PDF text and the rendered page support solid, unwavering silhouette and powerful "whitish blue" light from multiple points along its perimeter. The current OCR text has solid, unmoving silhouette and "pulsing" blue light, so that difference is an OCR/text-extraction quality issue, not a second reported description.
• Partial — related-source search: exact anchors including Pacific Time Zone, personal cellular device, national security facility, and The IIR and draft report are attached currently appear only in this D51 OCR text inside the linked Release 01 corpus. The INDOPACOM/Pacific cluster page is useful navigation context, but it does not supply the missing IIR, phone media, facility name, or exact observation time.
• Needs external source — ordinary context checks: aircraft, drone, astronomy, weather, local-lighting, and phone-artifact checks remain unavailable until a source exposes at least an exact or safely bounded location, clock time, viewing direction, and the referenced phone media or original report.

Deep investigation — graph + web reconnaissance

Source reread

The official PDF recheck supports the existing custody baseline: 76,470 bytes, SHA-256 f21f4ae91e51810bfa8a6fce6c422f2bbf99c6277871846c642f987954c042f6, six PDF pages, no embedded image objects, and no embedded attachments. PDF metadata still reports title/subject DoW-UAP-D29, which conflicts with the visible D51 title, URL, and release-row title.

Rendered-page and selectable-text review confirms that pages 4-5, not the email thread alone, carry the substantive reported-observation summary. Page 4 reads solid, unwavering silhouette and powerful "whitish blue" light from multiple points along its perimeter; the Frontier OCR phrase solid, unmoving silhouette / "pulsing" blue light is therefore a text-extraction variant, not a separate witness description. Page 5 confirms Speed: Not reported, Size: Large, Shape: Triangular, Color: Blue, Material: Not reported, Markings: Featureless, Behavior: Emitting light, erratic movement, and the line The IIR and draft report are attached. The released PDF itself still does not include those attachments or the referenced personal-cellular-device media.

Graph connections and extraction quality

Read-only graph checks found three matching document records: the official PDF asset, the current Release 01 row record, and a secondary UFO-USA GitHub Markdown conversion linked back to the official asset. The official PDF asset carries the correct D51 URL, byte count, and full-download hash. The row-58 release record has the current D51 title and row metadata, but still shows a stale D49 final URL/content-length trail from an earlier manifest revision; public interpretation should anchor on the D51 asset URL, title, visible page text, and SHA-256 until the row-record drift is cleaned up.

The semantic layer for the official D51 asset contains 33 machine-extracted Claim nodes and 18 EntityMention nodes, with 0 SensorEvent nodes and no table rows. These graph claims are marked as unreviewed machine extraction / not_a_finding; they are useful navigation aids, not conclusions. The extracted claims reproduce the OCR wording issue above, so any graph-level unmoving/pulsing phrasing should be treated as an extraction-quality lead unless checked against the rendered source page.

Exact-anchor graph/corpus checks keep the strongest source-specific terms confined to D51 and its derived conversion: personal cellular device, national security facility, and The IIR and draft report are attached matched the D51 official/derived records. Broader terms such as Pacific Time Zone are not source-specific and also appear in unrelated historical corpus material.

External provenance and official-source checks

The current Release 01 CSV row 58 still lists the D51 title, PDF type, blank video/DVIDS pairing fields, Incident Date: 3/23/26, Incident Location: Pacific Time Zone, the D51 official PDF URL, and the thumbnail URL. That preserves the same date tension already noted: the visible PDF body says March 2023, while the structured row field says 3/23/26.

Direct official WAR.GOV/PURSUE checks against the PDF URL, CSV URL, and landing page returned 403 responses from Akamai during this check, including byte-range attempts. That is an access/custody limitation, not a source-content contradiction, because the official-primary PDF copy verifies by hash and size. Internet Archive availability/CDX probes for the exact PDF were not usable in this run (429/503 responses), so they do not establish whether an archived public snapshot exists.

A secondary GitHub conversion in DenisSergeevitch/UFO-USA at commit 49f78498f323bcba625fd96b7283cbe5779349d6 was reachable and its page-4/page-5 Markdown aligns with the rendered PDF on the high-signal wording. It remains a derived/community mirror only; the official PDF and Release 01 row remain the source of record.

Prosaic checks and follow-up leads

Ordinary context checks are still blocked. The released text gives only Pacific Time Zone, March 2023, night, approximate eight-minute duration, civilian reporter, and the broad phrase above or near a national security facility; it withholds exact time, location/facility, viewing direction, phone-media metadata, aircraft/sensor context, and the underlying IIR/draft report. Without those fields, aircraft, drone, astronomy, weather, satellite/launch, local-lighting, and phone-camera artifact checks cannot be run responsibly.

Read-only graph context does not add a source-backed prosaic correlation. The graph has no D51 sensor event, no local weather record for the hidden observation context, no modeled 2023 launch event tied to this report, and only generic global astronomy/fireball records for 2023 that cannot be linked to the redacted Pacific Time Zone observation. The highest-value next source work is to locate the referenced IIR, draft report, and personal-cellular-device media; obtain or verify an official manifest correction for 3/23/26 versus March 2023; and, if location/time are lawfully releasable, run aircraft/drone/astronomy/weather/local-lighting and phone-artifact checks before any escalation.

Audit note

This deep pass does not create a finding, hypothesis, or resolution decision. It narrows the public record to source-confirmed correspondence, a summarized report, verified OCR/rendering discrepancies, unreviewed graph-extraction leads, and blocked follow-up checks.

Limits

This page does not make a finding. The released file preserves correspondence and a summarized report, not the original observation package. It is heavily redacted on pages 1-3 and in the signature block. It does not provide exact location, exact clock time, altitude, speed, sensor data, raw phone media, photographs, radar, video, chain-of-custody metadata for the personal device, or independent corroboration. The available text is enough to describe what the released PDF says; it is not enough to decide what the object was.

Sources

• Department of War, PURSUE Release 01, DOW-UAP-D51, Email Correspondence, Pacific Time Zone, March 2023 official PDF: official/source URL.
• Open Sky release-file view for this asset: release file.
• Open Sky Release 01 graph context for the D51 PDF asset and release-row record.
• OCR, selectable-text, PDF metadata, and rendered-page checks performed against the released six-page PDF; source hash verified as f21f4ae91e51810bfa8a6fce6c422f2bbf99c6277871846c642f987954c042f6.