← Back to Files & Wiki
Wiki page · asset · graph_investigation_draft

DOW-UAP-D50, Email Correspondence, INDOPACOM, April 2025

Official release file PDF: Open Sky release file copy.

Release 01#war-gov#pursue#release-01#official-source#evidence#email-correspondence#pdf

DOW-UAP-D50, Email Correspondence, INDOPACOM, April 2025

Evidence media

Official PDF page render: D50 page 1 email classification context

Page 1 render from the official D50 PDF. The page is email correspondence about confirming the tearlines and the INDOPACOM AOR as unclassified, with privacy/classification redactions; it contains no object imagery, map, radar display, or sensor frame.

Official PDF page render: D50 page 2 UAP tearlines

Page 2 render from the official D50 PDF. The visible tearlines say a U.S. aircraft observed one possible UAP for 12 seconds at 2353Z on 10APR25 and one possible UAP for 23 seconds at 0007Z on 11APR25, with unknown altitude/speed and no interference noted; the page is still correspondence text, not released object imagery.

Investigation reading

This released file is a two-page PDF email chain about whether two short UAP-related tearlines can be treated as unclassified and whether the area of responsibility can be identified publicly as INDOPACOM. It is not the underlying mission report and it does not contain imagery, a map, radar plot, sensor frame, aircraft track, or raw instrument return.

The strongest source content is on page 2. The page preserves two unclassified lines saying that a U.S. aircraft observed one possible UAP twice across the 10-11 April 2025 UTC boundary: once for 12 seconds at 2353Z on 10APR25, and once for 23 seconds at 0007Z on 11APR25. Both lines say altitude and speed were unknown and that no interference was noted. The observer/unit and some operational context are redacted.

Page 1 is administrative context. It records a request to confirm that the tearlines below are at the UNCLASSIFIED level and asks whether the AOR can be given as INDOPACOM. A later message on the same page says the sender had spoken with the unit that flies the redacted platform and that the two lines and the AOR wording were unclassified.

What the file appears to contain

PagePublic reading
1Email correspondence with privacy and classified-information redactions. The visible text asks for confirmation that the redacted tearlines are unclassified and that the AOR can be identified as INDOPACOM. It includes a visible role/signature block for a PAROC Intel Data Analysis Technician Team Lead, 12 AF / DET 3.
2Reply email confirming the tearlines are approved at the UNCLASSIFIED level. It contains the two UAP tearlines: US AIRCRAFT OBSERVED 1X POSS UAP FOR 12 SECONDS AT 2353Z on 10APR25, and US AIRCRAFT OBSERVED 1X POSS UAP FOR 23 SECONDS AT 0007Z on 11APR25. Both state unknown altitude, unknown speed, and no noted interference.

The rendered pages show text and redaction blocks only. There are no object photographs, video stills, maps, diagrams, radar scopes, infrared frames, or other released visual exhibits in this PDF. The redaction labels visible on the rendered pages include (b) (6) and 1.4(a). Both pages also show CLASSIFICATION: SECRET//NOFORN lines, with the released correspondence discussing which extracted lines can be treated as unclassified.

The file gives a narrow reportable fact pattern: two brief possible-UAP observations by a U.S. aircraft in the INDOPACOM AOR, separated by roughly fourteen minutes, with unknown altitude/speed and no interference noted. It does not provide enough information to identify the aircraft, exact location, sensor mode, object appearance, distance, weather, astronomical context, satellite/launch correlation, or whether both lines refer to the same object/event sequence.

Source custody and provenance

This is an official Release 01 Department of War PDF asset tied to CSV row 57. The release record lists incident dates 4/10/2025-4/11/2025, incident location N/A, redaction TRUE, and the title DOW-UAP-D50, Email Correspondence, INDOPACOM, April 2025.

The cached release-file copy was verified as a 312,451-byte PDF with SHA-256:

10c11e9bf4d6686159da48e3d9388e7d3afe4ae8b1e79725ec6c63ccc491e537

Text coverage is complete for this small file: two PDF pages, two OCR pages with text, and a selectable text layer that agrees with the core OCR reading. Rendered-page inspection confirms that the available source is email/text correspondence rather than a media exhibit.

One provenance cleanup lead is worth preserving: embedded PDF metadata reports title/subject values that appear to reference DoW-UAP-D28, while the release URL, visible release record, and page content identify this file as D50. That mismatch should be checked against the original release packaging before anyone uses embedded PDF metadata as an identifier.

Graph context

The graph currently models both the release-row record and the PDF asset as official-primary Document records. The D50 asset has extracted source-text claims for the two observation lines, time references (2353Z, 0007Z), INDOPACOM/Department of War organization mentions, redaction context, and platform wording derived from US AIRCRAFT.

The semantic graph reports 29 extracted claims, 24 entity mentions, 2 sensor/platform events, and 0 table rows for this item. The two sensor/platform events are best read cautiously: they are triggered by the text phrase US AIRCRAFT OBSERVED, not by a released sensor product. The PDF itself does not show an aircraft display, radar return, telemetry plot, or optical/IR frame.

No candidate crosslinks are recorded for this page. Related graph neighbors include the D50 release-row record and nearby Release 01 records/assets; those are navigation context, not corroboration of the two tearlines.

Leads to check

  • Locate the underlying mission report or operational record described by the email chain, if released separately, to determine aircraft type, exact location, sensor mode, and whether the two tearlines are from one continuous sortie.
  • Check whether the INDOPACOM AOR wording is the only releasable location, or whether a less-redacted source gives a narrower airspace/sea region.
  • Compare the 2353Z and 0007Z observations against astronomy, aviation, satellite, launch, missile-test, balloon, and weather context for 10-11 April 2025 once a location or track area is available.
  • Resolve the embedded-PDF metadata mismatch that appears to reference D28 instead of D50.
  • Review whether US AIRCRAFT OBSERVED should remain modeled as a generic platform cue rather than a sensor event until a source names a sensor or observation method.

Lead check notes

  • Blocked — underlying mission record: The D50 PDF and release-row record preserve the correspondence and two approved tearlines, not the underlying mission report. The exact 12-second and 23-second tearline wording appears in the current Release 01 OCR only for this D50 text, so aircraft type, sensor mode, and whether the two lines come from one sortie still need a separate source.
  • Checked — releasable location wording: Page 1 visibly supports that adding the AOR as INDOPACOM was approved at the unclassified level. The release record still lists incident location as N/A, and the PDF gives no narrower airspace, sea region, coordinates, or track.
  • Needs external source — environmental/prosaic checks: Astronomy, aviation, satellite, launch, missile-test, balloon, and weather checks are not meaningful from this PDF alone because exact location/track, platform, look direction, altitude, and sensor mode are redacted or absent.
  • Checked — embedded metadata mismatch: The verified PDF metadata reports title/subject values referencing DoW-UAP-D28, while the official URL, release record, visible title, and source text identify the file as D50. Keep that as a provenance cleanup item, not a content change to the tearlines.
  • Partial — platform/sensor modeling: The source phrase is US AIRCRAFT OBSERVED; no camera, radar, IR, SIGINT, or other sensor method is named in the released text. Until another source names an observation method, the graph cue should stay generic rather than being treated as raw sensor evidence.

Limits

This draft does not resolve what was observed. The file is correspondence about classification/release handling and contains only two short unclassified tearlines from a separate mission-report context. Names, platform details, and parts of the operational content are redacted. Altitude and speed are explicitly unknown in both tearlines. The source says no interference was noted, but it does not provide supporting sensor data, video, imagery, or environmental context.

The public record should therefore be treated as an official, redacted documentary pointer to two brief possible-UAP observations, not as standalone proof of object characteristics or performance.

Deep investigation — graph + web reconnaissance

Source reread

The canonical WAR.GOV PDF is currently reachable as a direct application/pdf response and re-downloads as the same 312,451-byte file with SHA-256 10c11e9bf4d6686159da48e3d9388e7d3afe4ae8b1e79725ec6c63ccc491e537. The local release-file copy, PDF metadata, OCR text, selectable text, and rendered page review all agree that this is a two-page email-correspondence packet rather than the underlying mission report.

Page 1 is classification/release coordination: the visible text asks whether redacted tearlines can be treated as UNCLASSIFIED and whether the AOR can be publicly described as INDOPACOM; a later visible line says the unit that flies the redacted platform confirmed both the two lines and the AOR wording at the unclassified level. Page 2 contains the only UAP-specific source text: a U.S. aircraft observed 1X POSS UAP for 12 SECONDS AT 2353Z on 10APR25, and a second 1X POSS UAP for 23 SECONDS AT 0007Z on 11APR25; both lines state unknown altitude, unknown speed, and no noted interference.

The rendered pages show redacted email text only. There are no released object images, video frames, maps, track plots, radar scopes, infrared frames, telemetry tables, or weather/astronomy context in this PDF.

Graph connections

Read-only graph review finds two official-primary Document records for this item: the PDF asset at the canonical media URL and the Release 01 row record at https://www.war.gov/UFO/#release-01-record-57-current-row. The asset has three text chunks, 29 machine-extracted claims, 24 entity mentions, and two SensorEvent nodes. Those two sensor-event nodes are still machine_extracted_needs_human_review; their own source quote is the phrase US AIRCRAFT OBSERVED, and their modality is unknown, so they should be treated as platform/observation cues rather than proof of a named sensor return.

No CANDIDATE_CROSSLINK relationships are modeled for this page. A secondary DERIVED_FROM neighbor points to a public GitHub markdown conversion; that is useful only as a mirror/formatting lead, not as an independent source. One stale provenance-cleanup issue remains visible in the graph: the D50 asset is correctly related to current CSV row 57, but it also has an older RELATED_TO relationship to a D54/Mediterranean Sea row 60 record with current_in_official_csv: false. That should be handled as graph hygiene, not as evidence that D50 and D54 describe the same event.

External provenance and context

The official media URL itself is the strongest live provenance check: it currently returns the PDF with the expected size and hash. The broader WAR.GOV landing page and CSV endpoint returned 403 during this check, so row-level confirmation still rests on the verified release inventory/graph record until the public CSV is reachable again. Internet Archive availability also shows an archived WAR.GOV copy for the exact PDF URL with a 200 snapshot timestamped 20260508200659, which is a useful custody fallback for the released file URL.

Official companion-source probes did not confirm a separate public media packet or mission report. DVIDS search returned an AWS/WAF interstitial rather than searchable results, and Defense.gov/AARO search probes returned 403. Those access results do not prove that no companion source exists; they only mean this check did not verify one from official public search surfaces.

Prosaic checks and limits

The file does not give an exact location, aircraft type, sensor mode, look angle, altitude, range, object appearance, or track. Because the only location is AOR-level INDOPACOM, meaningful astronomy, weather, aircraft, balloon, satellite, missile-test, or launch correlation is blocked. A read-only graph probe found no modeled LaunchEvent on the exact 10-11 April 2025 UTC dates, but that is only a graph-coverage note and should not be used as an external exclusion.

The proper evidentiary posture is narrow: D50 documents two brief possible-UAP tearlines approved for unclassified release, not a resolved sighting, performance claim, or sensor-data case. The unknown altitude/speed and NO INTERFERENCE WAS NOTED language should be preserved exactly as source text until the underlying mission report or raw sensor/flight context is available.

Follow-up leads

  • Recheck the WAR.GOV CSV/landing page when direct access allows it, especially to confirm row 57 and clear the stale row-60 D54 relationship from the graph model.
  • Search for the underlying mission report, sortie record, or redacted platform/unit context that generated the two tearlines; without it, the two observations cannot be correlated against sky, traffic, weather, or satellite context.
  • Re-run DVIDS, Defense.gov, and AARO official searches if their public search surfaces become reachable, but treat any secondary mirrors as provenance leads only.
  • Keep the two machine-extracted SensorEvent nodes marked as unreviewed/generic unless a source names a sensor or provides an actual sensor product.

Audit note

This section separates verified source text, graph inventory, access/provenance checks, and unresolved leads. It does not add a finding, hypothesis, or resolution decision.

Sources