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

DOW-UAP-D55, Mission Report, Syria, November 2016

Official Release 01 PDF copy.

Release 01#war-gov#pursue#release-01#official-source#evidence#pdf#mission-report#syria

DOW-UAP-D55, Mission Report, Syria, November 2016

Evidence media

Derived official PDF page render: DOW-UAP-D55 mission report page 1

Derived page render from the official PDF. The page shows a USCENTCOM briefing-style summary with the BLUF, two-step timeline, weather note, flight-path graphic, and low-resolution annotated EO/IR-style still insets labeled U/I OBJ, (RUS) INGUL ARS, and U/I VESSEL. The inset imagery is part of the released page and is not enough by itself to identify the object or reconstruct the redacted video.

Investigation reading

This is a one-page USCENTCOM briefing-style mission report dated 18 Nov 2016. The visible title reads that a P-8A observed an unidentified low-flying object 55 nautical miles northwest of Latakia, Syria. The document is not a full video release or a full sensor packet; it is a single declassified page with a short narrative, a two-step timeline, a weather note, a flight-path graphic, and several small grayscale sensor-style stills.

The report's own wording is careful but mixed. The BLUF calls the target an unidentified low-flying object from an unknown origin. The timeline then says the P-8 observed a possible missile launch via EO/IR at 18/1310Z, and the later line says the P-8 lost visual at 18/1312Z around 40 NM northwest of Latakia. The same page also says the possible missile appeared to be in sea skim mode, traveling approximately 500 knots on a southeasterly heading outbound from KCTG. The source text says the P-8 was 26 NM south of the object detection and at 16,121 FT; nearby location or operational details are redacted under 1.4a boxes.

The visible page includes a right-side FLIGHT PATH map with a north arrow, markers for roughly 1310Z and ~1312Z, a callout for the P-8A location, and a distance marker of 26 NM. The bottom-left inset and two small right-side thumbnails are low-resolution grayscale images. Labels visible on the page include UI OBJ, (RUS) INGUL ARS, and U/I VESSEL. The image stills are useful as release context, but they do not provide enough visible detail on this page to independently identify the object.

What the file appears to contain

The released file appears to preserve a short operational summary of a P-8A EO/IR observation in the Eastern Mediterranean, not an adjudicated case report. The high-signal source claims are:

  • Platform and sensor: P-8A, EO/IR sensor, visual/contact language.
  • Time window: about two minutes, from 18/1310Z to 18/1312Z.
  • Location framing: 55 NM northwest of Latakia in the title/BLUF; approximately 40 NM northwest of Latakia at loss of visual; several exact or operational locations redacted.
  • Motion description: approximately 500 KTS, southeasterly heading, described as sea-skimming in the timeline.
  • Context: monitoring KCTG activity in the Eastern Mediterranean.
  • Nearby maritime references: the timeline says the object or missile passed between (RUS) INGUL ARS and 1x U/I vessel.
  • Weather: the P-8 aircrew characterized visibility as clear with no range limitations.
  • Command comment: CTG 67.1 says the mission commander characterized the interaction as safe and assessed the possible missile activity as standard activity consistent with assessed KCTG activity.

The page also states that video footage could be found at a redacted link. The link itself is not released in this PDF, and this asset does not provide a separate public video file for this item.

Source custody and provenance

A provenance cleanup lead remains: the embedded PDF metadata title/subject reads DoW-UAP-D32, while the official URL, visible page title, release record, and page content identify this asset as DOW-UAP-D55. That mismatch should be treated as metadata carryover or release-pack cleanup until the source record is reconciled.

Graph context

The graph currently models both the release-record document and the PDF asset document. The release-record side carries the row-level incident fields: 11/18/16, Syria, redaction true, and CSV row 61. The asset side carries the official file URL, file hash, and extracted OCR/semantic links.

The semantic layer has 59 source-text claim records, 52 entity mentions, 7 sensor-event records, and 0 table rows for this asset. These graph records are useful navigation aids, but several are repeated variants of the same short page text. The sensor-event records mainly come from phrases such as P-8A, EO/IR, and P-8 lost visual; they should not be read as seven independent sensor systems or seven independent observations.

Candidate crosslinks are present, but they are review leads only. The broad Syria and Pacific Time Zone text anchors can pull in unrelated archive records, so cross-case interpretation should wait for human review and source-by-source comparison.

Leads to check

  • Locate whether the redacted video reference corresponds to a releasable MDR/AARO media item, DVIDS item, or withheld operational video.
  • Reconcile the D55 official title with embedded DoW-UAP-D32 PDF metadata before using metadata fields for automated grouping.
  • Clarify the source meaning of KCTG and compare the report's “standard activity consistent with assessed KCTG activity” wording against contemporaneous Eastern Mediterranean/Russian task-group context.
  • Compare the visible map labels and maritime references, especially (RUS) INGUL ARS and U/I vessel, with contemporaneous vessel tracks or order-of-battle sources where available.
  • Treat the small stills as low-resolution page insets unless a higher-quality original EO/IR clip or still frame is located.
  • Preserve the source's internal wording tension: the BLUF says unidentified low-flying object, the timeline says possible missile launch/possible missile, and the comments assess possible missile activity as standard activity.

Lead check notes

  • Blocked — redacted video reference: The D55 release record and PDF asset expose the PDF only; no DVIDS URL or paired public video field is present for row 61, and the page's video link remains redacted. Frame-level review needs a separate MDR/AARO/DVIDS record or the underlying operational video.
  • Checked — D55/D32 metadata tension: The visible page title, official URL, release row, and source page text identify this file as DOW-UAP-D55. The embedded PDF title/subject fields read DoW-UAP-D32, so metadata-driven grouping should keep this as a provenance cleanup item until an official corrected file or manifest history resolves it.
  • Partial — KCTG/KTG activity context: The current linked Release 01 OCR corpus finds the KCTG and map KTG anchors in this D55 page only; the Syria cluster page repeats them as regional context. Expanding the acronym or activity context needs external military/naval source material.
  • Partial — maritime labels: The page render supports the visible annotations (RUS) INGUL ARS, U/I VESSEL, and U/I OBJ. Exact INGUL search hits outside D55 were ordinary-word OCR false positives, so vessel identification or track comparison still needs contemporaneous order-of-battle/AIS/naval sources.
  • Partial — Latakia/Eastern Mediterranean context: The linked corpus has separate Latakia/Eastern Mediterranean mentions in D14 and the Syria cluster page, but those are regional context only, not same-event evidence. Exact redacted coordinates, platform geometry, and look direction remain missing.
  • Checked — source wording tension: Page-image and text review confirm the page uses all three phrasings: unidentified low-flying object, possible missile launch/possible missile, and standard activity consistent with assessed KCTG activity. Preserve that as source-language tension; it is not a resolution decision.
  • Checked — image/still limits: The PDF contains a single rendered page image with low-resolution annotated insets and no embedded attachments. The stills should remain page-inset evidence unless a higher-quality EO/IR clip or source still is released.

Limits

This draft is not a finding and does not identify the object. The released PDF is a single page, heavily redacted in operational fields, and the public video link is redacted. The map and image insets are visible but low-resolution; they support the page's narrative layout but do not independently resolve object identity, size, range, or origin. The page contains an official assessment that the activity was consistent with KCTG activity, but the underlying evidence for that assessment is not included in this released file.

Deep investigation — graph + web reconnaissance

Source reread

A source-page reread confirms this is a one-page, copy-restricted PDF package: 207,227 bytes, SHA-256 f5885b95b57a81c08f0595c02950a07c250db050562520c52fb74f2195787166, with one embedded page image and one public derived page render. The PDF metadata still says DoW-UAP-D32, but the visible page title, file URL, manifest text, OCR, and page render identify the asset as DOW-UAP-D55. The top-right release stamp is visually consistent with MG Richard A. Harrison, USCENTCOM Chief of Staff, and the footer reads USCENTCOM MDR 26-0038 to MDR 26-0046, Approved for Release to AARO, 03/27/26 000001. OCR can misread both the officer name and the BLUF distance; page-image review supports 55 NM northwest of Latakia, not the 86 nm value produced by one selectable-text extraction.

The high-signal source facts remain tightly bounded. At 18/1310Z on 18 Nov 2016, the page says a P-8/P-8A observed a possible missile launch via EO/IR sensor while monitoring KCTG activity. The object or possible missile is described as in sea skim mode, moving approximately 500 KTS on a southeasterly heading outbound from KCTG; the P-8 was 26 NM south of object detection at 16,121 FT. At 18/1312Z, the P-8 lost visual at approximately 40 NM northwest of Latakia, and the source says the missile passed between (RUS) INGUL ARS and 1x U/I vessel. Weather is source-reported as clear with no range limitations. The page also says the mission commander characterized the interaction as safe and assessed the possible missile activity as standard activity consistent with assessed KCTG activity. The video link remains redacted, so the public asset does not expose the underlying EO/IR footage.

Graph connections and provenance tensions

Read-only graph checks match the stable evidence asset by exact official URL and hash, but they also expose row/relationship drift that should stay in the provenance-cleanup lane. The stable asset node carries the D55 title, exact PDF URL, hash, and 207,227-byte content length. Nearby release-record nodes still surface inconsistent row metadata: one current D55-titled record carries stale D51 file fields, while a D58-titled row record carries the D55 final URL and byte count. Separately, the cached CSV/converted-metadata lane places D55 at data row 64, while this page's current inventory/frontmatter records row 61. Until the official manifest history is reconciled, the exact file URL, title text, and hash are stronger identifiers than row number alone.

The semantic layer for this asset contains 59 machine-extracted claims, 52 entity mentions, and 7 sensor-event records. Those records are useful for navigation, not adjudication: the sensor-event records are repeated variants of P-8/P-8A, EO/IR, and lost visual language from the same page, not seven independent sensors or observations. Targeted graph text checks keep the exact title and KCTG anchors confined to this D55 asset and its secondary converted copy; INGUL appears in D55 but also in unrelated OCR snippets, so non-D55 INGUL hits should not be treated as same-event evidence without page-level review. Candidate crosslinks are broad/stale-text leads, not corroboration.

External provenance and official-source checks

Direct WAR.GOV probes for the PDF, the Release 01 landing page, and the official CSV returned 403 Forbidden during this check, which is consistent with prior WAR.GOV access behavior and is not by itself a custody failure because the cached official-primary file verifies by size and hash. Internet Archive CDX returned exact-URL snapshots of the D55 PDF from 2026-05-08 with 200 / application/pdf, supporting public provenance for the same canonical URL. DVIDS/AARO/Defense public search probes did not surface a usable public video pairing for this D55 title; the row-level release fields also have no DVIDS video ID or video title.

Prosaic checks and unresolved questions

The source's own wording keeps the first prosaic lane open: it calls the observation an unidentified low-flying object in the title/BLUF, but the timeline repeatedly says possible missile, and the command comment assesses the activity as safe and standard for the assessed KCTG context. Clear-weather reporting reduces one simple visibility concern, but it does not supply range, look angle, raw EO/IR frames, platform geometry, vessel tracks, or the redacted video. Read-only graph probes did not surface exact-date launch, weather, astronomy, or satellite records for 2016-11-18; that is graph-coverage information, not an external exclusion.

The next evidence checks are therefore concrete: locate the redacted MDR 26-0038 to MDR 26-0046 video/reference package if it becomes public; reconcile the D55/D32 PDF metadata and row-number drift; identify KCTG and (RUS) INGUL ARS from official naval/order-of-battle or vessel-track sources rather than OCR snippets; and preserve the page's source-language tension until raw footage or higher-quality source material is available.

Audit note

No finding, hypothesis, or resolution decision is created here. The added material separates verified source text and page-image observations from machine-extracted graph leads, external provenance checks, prosaic lanes, and unresolved follow-up work.

Sources