DOW-UAP-D16, Mission Report, Syria, July 2022

Evidence media

Official PDF: open released mission report PDF (official WAR.GOV PDF).
Paired release video: open PR22 video file, with its separate PR22 evidence page.
The images below are derived page renders from the official PDF. They show source-document context only; this PDF contains text/form pages, not object imagery.

Derived page render from official PDF: page 1 mission narrative

Page 1 preserves the mission narrative and high-level timeline, including departure from OJMS, LRE handover, SIGINT collection, arrival/on-station/check-in, the 310239ZJUL22 UAP observation line, return-to-base, and landing times.

Derived page render from official PDF: page 5 ISR metadata and GENTEXT/ISR opening

Page 5 shows the ISR section with the 302028:00ZJUL22 ISR time-on-station field, 310000:00ZJUL22 ISR time-off-station field, activity description, and the start of the GENTEXT/ISR narrative.

Derived page render from official PDF: page 7 weather and UAP block

Page 7 shows the weather and UAP form fields: weather was recorded as not a factor; initial contact is 310239:00ZJUL22; friendly aircraft altitude is 19,359 FT; speed is 116 KTS; UAP Signatures is marked No; RF fields are dashes; location strings are partial/redacted 37SFU... entries; and the UAP description says the event lasted less than one minute with north-to-south motion.

Investigation reading

This released file is a seven-page MISREP-style mission report associated with a July 2022 Syria UAP record. The document is text/form evidence, not an image exhibit: every rendered page is a scanned or captured report page with classification markings, declassification stamps, form fields, redactions, and narrative text. No UAP photo, video still, radar plot, map, sketch, or embedded sensor frame appears inside this PDF.

The highest-signal UAP language appears twice. Page 1's mission narrative says that at 310239ZJUL22 a redacted element observed an unidentified aerial phenomenon in the vicinity of a partially redacted 37SFU27... grid reference and points the reader to SEE UAP 1. Page 7's UAP section gives the structured follow-up: initial contact 310239:00ZJUL22, friendly aircraft altitude 19,359 FT, friendly aircraft speed 116 KTS, UAP Signatures: No, RF fields left as dashes, effects-on-persons blank, and a GENTEXT/UAP description stating that the event occurred in less than one minute with the UAP moving from north to south.

The report should be read as an operational form packet. It gives mission timing, tasking, ISR narrative, and a short UAP field entry; it does not itself supply the paired video. The release manifest links this PDF to the separate PR22 Syria video record, which should be reviewed as its own source when that item is selected.

What the file appears to contain

Page	Public reading
1	Front narrative and administrative metadata. The visible narrative says TF CHOSIN tasked a redacted element with IMINT via 7-line at `301639ZJUL22`; the element departed Muwaffaq Salti AB (`OJMS`) at `301822ZJUL22`; handed over from the LRE at `301829ZJUL22`; began SIGINT collect at `301925ZJUL22`; arrived/check-in language appears at `302028ZJUL22`; observed an unidentified aerial phenomenon at `310239ZJUL22`; returned to base at `311343ZJUL22`; terminated SIGINT collect at `311409ZJUL22`; handed back to the LRE at `311458ZJUL22`; and landed at `OJMS` at `311519ZJUL22`. The same page states that full-motion video was exploited by `DGS1`, with `20.9` mission hours, `17.2` IMINT hours, `18.7` SIGINT hours, and two total taskings prosecuted. Operation metadata lists Operation Inherent Resolve, air domain, AFCENT, and USCENTCOM.
2	Report provenance and workflow fields: report type `MISREP`, originator `89 ATKS`, mission type `ARMED RECCE`, Air Force service tasking, POC/QC/approver sections, and personal data redacted under FOIA/exemption markings.
3	Ingest and aircraft/equipment prompts. It lists aircraft callsign plus radar, RWR, MWS, IRCM, ECM, chaff, flare, towed decoy, and missile/weapon fields; most of those fields are blank or redacted. These form prompts should not be mistaken for populated sensor evidence.
4	Timeline and continuation of equipment fields. The form lists one aircraft, redacted asset/tail data, takeoff location `OJMS`, takeoff time `301822:00ZJUL22`, mission type `AREC`, off-station time `311409:00ZJUL22`, and total on-station time `18 hours 44 minutes`.
5	Landing plus ISR metadata and the beginning of the GENTEXT/ISR narrative. It lists landing at `OJMS`, total mission time `20 hours 57 minutes`, ISR time-on station `302028:00ZJUL22`, ISR time-off station `310000:00ZJUL22`, redacted callsign, mux type `ARIC`, planned tasking, activity description `ISR`, and a long text narrative of scans and observations.
6	Continuation of the ISR narrative. The page describes a time-ordered sequence of vehicle/personnel observations, convoy or vehicle follow activity, a possible shooting-range assessment in the source text, a possible artillery-system object in a truck bed, possible mounted AAA, a Bongo carrying possible barrels, COI scans with `NSTR`, and a Dayr Az Zawr parking-airfield entry stating that two TELARs with three rockets loaded were inactive. These are contextual ISR entries in the same mission report, not UAP-resolution evidence by themselves.
7	ISR asset utilization, weather, effectiveness, and the UAP block. Weather is recorded as not a factor. The UAP block lists initial contact `310239:00ZJUL22`; redacted tail/location fields; friendly aircraft altitude `19,359 FT`; speed `116 KTS`; UAP physical state blank/dash; number sighted blank; `UAP Signatures: No`; RF frequency and duration as dashes; effects on persons blank; first-seen location partly visible as `37SFU2...`; trajectory field as a dash; and GENTEXT/UAP text saying the event occurred in less than one minute and moved from north to south.

The official release description says a military operator reported one UAP moving north to south for under one minute. The form itself leaves Number of UAP Sighted blank while the narrative uses singular language (an UAP event) and the release description says one UAP. That count should stay source-qualified until the paired video and any underlying operational record are reviewed together.

Source custody and provenance

Official/source URL: https://www.war.gov/medialink/ufo/release_1/dow-uap-d16-mission-report-syria-july-2022.pdf
Open released file: war-gov-dow-uap-d16-mission-report-syria-july-2022-4555d94d
SHA-256: b3b3f023d70bcce3178de9fe6a019ea6db5e5145bc7e28a49308442e190ef817
File reviewed: PDF, 6,999,240 bytes, 7 pages; all seven pages have OCR text and were checked as page images.
Agency/source lane: Department of War / PURSUE Release 01.
Release rows carried by Open Sky release metadata: 38, 79.
Release record context: row 38 is the DOW-UAP-D16 mission report; the graph also relates this file to PR22, the July 2022 Syria video record. A separate PR27/UAE neighbor appears in graph context and should be treated as a relationship-review item, not as part of this PDF.
Declassification markings visible on the pages name MG Richard A. Harrison, USCENTCOM Chief of Staff, with declassification dates on 8-9 October 2025 and release markings approved for AARO.

Graph context

The graph has an official Document node for the PDF asset and an official release-record Document node for the corresponding WAR.GOV release row. It preserves the PDF hash above, the canonical WAR.GOV media URL, the official release-page URL, and the relationship to the PR22 video evidence record.

Structured extraction currently reports 169 claim records, 134 entity mentions, 4 sensor-event records, and 0 table rows for this page. Those records are useful navigation aids, but several require careful reading against the rendered pages. For example, the extraction sees sensor terms such as IR, Aircraft IR, and Aircraft FMV; in the PDF, some of that signal comes from aircraft/equipment form prompts and the ISR/mission narrative rather than a displayed radar plot or embedded sensor image. Page 1 does say full-motion video was exploited by DGS1, and the release manifest points to a separate PR22 video, but the PDF itself contains no video frame.

Candidate crosslinks should also be kept modest. Most candidate links shown for this PDF are anchored on broad terms such as Syria, so they are leads for later source comparison rather than corroboration of the July 2022 event.

Leads to check

Review the paired PR22 Syria video record with the PDF open beside it. The public release description says the video shows an object at about the five-second mark and that the mission report describes north-to-south motion; that comparison belongs on the video page or a later case-cluster page after both sources are reviewed.
Reconcile row/link metadata: Open Sky release metadata carries rows 38 and 79, while the manifest prose and graph neighborhood also surface nearby related-row information. Keep D16/PDF, PR22/video, and any unrelated row neighbor separate.
Compare the form's timing fields: page 1 narrative and page 5 ISR metadata use 302028Z for the ISR/on-station activity, while page 4's timeline field lists 301925:00ZJUL22 as time on station. This may be a form/narrative distinction rather than a contradiction, but it should be tracked.
Confirm partial grid strings only from rendered pages. OCR/text extraction can misread 37SFU as 375FU and can distort some redacted coordinate fragments. Public analysis should avoid overusing partial grids until a human checks the page images.
Run ordinary correlation checks before escalation: known aircraft activity, drones, balloons, astronomical/meteor sources, local air-defense or military activity, and sensor/display artifacts for the 310239ZJUL22 Syria window. Redactions and partial coordinates will limit any external match.
Check whether the source phrase UAP Signatures: No means no signature observed, no populated signature field, or a form-specific checkbox state. The report does not provide RF frequency, RF duration, physical state, altitude/velocity, or effects-on-persons details for the UAP.

Lead check notes

Partial — paired PR22 video. The release metadata, graph context, and paired PR22 page all identify DOW-UAP-PR22, Unresolved UAP Report, Syria, July 2022 as the video counterpart to this D16 PDF. The PR22 MP4 is available through the Open release-file link above, but frame-level review still belongs on the PR22 video page or a later source-comparison page.
Partial — row/link metadata. The D16 PDF is anchored to release row 38; the PDF release metadata also carries row 79 as paired-video context. The PR22 video record is separately present, while a PR27/UAE neighbor remains a row-mapping review item, not part of this PDF.
Checked — timing fields. Rendered-page review supports page 1 timeline values of 301829ZJUL22 handover from LRE, 301925ZJUL22 SIGINT collection start, 302028ZJUL22 arrival/on-station/check-in, and 310239ZJUL22 UAP observation. Page 4 separately lists 301925:00ZJUL22 as the timeline Time On Station DTG, and page 5 lists 302028:00ZJUL22 as ISR Time-on Station DTG; treat these as distinct form/narrative fields unless an underlying mission log resolves them.
Partial — grid strings. Page-image review favors 37SFU... rather than the OCR variant 375FU; page 7 shows partial/redacted friendly-aircraft and first-seen strings around 37SFU41...78... and 37SFU27...74.... The current linked corpus also has broader 37SFU hits in other Syria mission reports, so these fragments should not be promoted to an exact location without an unredacted source or a verified grid reconstruction.
Blocked — ordinary correlation checks. The PDF gives the 310239ZJUL22 time window and says weather was not a factor, but it does not provide an unredacted coordinate, raw weather table, azimuth/elevation, sensor-frame metadata, or object altitude/velocity. Aircraft/drone/balloon/astronomy/meteor checks need the PR22 video review and additional source data before they can be meaningful.
Checked — UAP Signatures: No. Page 7 shows UAP Signatures: No, RF frequency and duration as dashes, physical state as a dash, and Number of UAP Sighted blank. The source does not define whether No is a checkbox state, absence of a reported signature, or a form-specific value, so public wording should keep it as a quoted field value rather than an analysis result.

Deep investigation — graph + web reconnaissance

Source reread

A fresh source pass treated the rendered PDF pages as authoritative where OCR is ambiguous. The verified released PDF is a seven-page, text/form MISREP packet with no embedded object imagery. Page 1 supports the main mission timeline: TF CHOSIN tasking at 301639ZJUL22; departure from Muwaffaq Salti AB (OJMS) at 301822ZJUL22; LRE handover at 301829ZJUL22; SIGINT collection beginning at 301925ZJUL22; arrival/on-station/check-in at 302028ZJUL22; UAP observation at 310239ZJUL22; return-to-base at 311343ZJUL22; SIGINT termination at 311409ZJUL22; LRE hand-back at 311458ZJUL22; and landing at OJMS at 311519ZJUL22. The same page says full-motion video was exploited by DGS1, with 20.9 mission hours, 17.2 IMINT hours, and 18.7 SIGINT hours.

Page 7 is the highest-signal UAP source page. It lists Initial Contact DTG: 310239:00ZJUL22, friendly-aircraft location as a redacted 37SFU41...78... grid fragment, friendly-aircraft altitude 19,359 FT, speed 116 KTS, UAP Signatures: No, RF frequency and duration as dashes, and first-seen location as a redacted 37SFU27...74... fragment. The GENTEXT/UAP line says that at 310239Z a redacted observer saw AN UAP EVENT in the vicinity of the 37SFU27...74... fragment, that it occurred in less than one minute, and that the UAP moved from N TO S. Weather is recorded separately as WEATHER WAS NOT A FACTOR.

The render-vs-OCR gap matters here. Stored OCR/graph chunks sometimes read 375FU instead of 37SFU, and the page-1 OCR distorts several time/location strings, including the UAP line. Public quotation should prefer the rendered pages for 37SFU fragments, 310239ZJUL22, and the page-7 UAP field values. The PDF's aircraft/equipment prompts and blank fields should not be read as populated radar/RF/weapon evidence.

Paired PR22 media and official web check

The paired visual source is the separate PR22 DVIDS video, not imagery embedded in this PDF. The official DVIDS page was live during this check at https://www.dvidshub.net/video/1006060/dow-uap-pr22-unresolved-uap-report-syria-july-2022 with title DOW-UAP-PR22, Unresolved UAP Report, Syria, July 2022. DVIDS metadata visible during the check lists video ID 1006060, VIRIN 220701-D-D0360-5363, filename DOD_111688775, category B-Roll, length 00:00:14, date taken 07.01.2022, date posted 05.07.2026 23:22, location SYRIA, and courtesy/unit attribution to the All Domain Anomaly Resolution Office. The official MP4 endpoint answered a range request with 206 and bytes 0-15/3982264, and the returned header bytes include an MP4 ftyp box. Direct WAR.GOV PDF and release-page fetches returned 403 during this check, so the public page relies on the already verified Open Sky release-file copy plus recorded WAR.GOV release metadata.

The PR22 source description says the video consists of 14 seconds from infrared (left) and electro-optical (right) sensors aboard a U.S. military platform, and that at about the five-second mark an object moves right-to-left across the top-right quarter of the sensor field of view. That screen-motion description should not be automatically equated with the D16 report's north-to-south geographic wording: the public clip lacks in-frame timestamp, sensor orientation, map orientation, range, field of view, platform position, and raw telemetry. DVIDS also carries a custody/date tension: 07.01.2022 and VIRIN 220701-D-D0360-5363 versus the D16 UAP entry at 310239ZJUL22 and release incident date of July 31, 2022.

Graph connections

Read-only Neo4j review found the exact D16 PDF asset node, the Release 01 row-38 record node, and the paired PR22 VideoEvidence node for DVIDS 1006060. The D16 asset node preserves the canonical WAR.GOV PDF URL and SHA-256 b3b3f023d70bcce3178de9fe6a019ea6db5e5145bc7e28a49308442e190ef817; it currently has 14 text chunks, 169 machine-extracted claim records, 4 machine-extracted sensor-event records, and 0 candidate crosslinks attached directly to the asset. The PR22 video node preserves the official DVIDS URL, MP4 URL, full-download hash 17106a65c823fb0c4c55f41be31f863f18300bd858f536726ea6f9f3cf35ac8c, two manifest-description chunks, 18 machine-extracted claim records, and 0 sensor-event records.

The graph is useful for source custody but still has row-linkage cleanup issues. The D16 PDF release record is row 38 and carries DVIDS video ID 1006060; the asset inventory/page carries row context around 38, 79, and 82; a PR22 release-record neighbor currently surfaces a suspicious D10 final URL; and a PR27/UAE row neighbor surfaces the D16 PDF URL. Treat those as release-metadata mapping problems, not evidentiary links between separate cases.

The four D16 sensor-event nodes are explicitly machine-extracted, machine_extracted_needs_human_review, and not_a_finding. Two Aircraft IR entries come from aircraft/equipment or IR-guided-weapon form prompts, one Aircraft FMV entry comes from ISR text, and one generic aircraft entry comes from the page-7 UAP block. The source-backed sensor context is narrower: D16 states that full-motion video was exploited by DGS1, and PR22 is the public IR/EO video clip. The graph does not expose raw radar, raw RF, original full sensor telemetry, or an identification.

Prosaic checks and limits

The first ordinary-explanation lanes remain open rather than resolved: aircraft or drone activity, balloon/debris, local Operation Inherent Resolve military activity, munitions or ground activity in the operating area, terrain/parallax, sensor-display artifact, compression/annotation artifact, weather/visibility, and astronomical or meteor sources. Page 7 says weather was not a factor, but the public packet does not include a weather table or independent environmental data.

Robust correlation is blocked by redactions and media limits. The public record gives the UAP timestamp and partial 37SFU grid fragments, but not the unredacted coordinate, platform identity, altitude above terrain, sensor mode/calibration, range, look angle, field of view, object altitude/velocity, or original unannotated FMV. Until those details are available, external astronomy/weather/launch/satellite/air-traffic checks would be generic and should not be promoted as analysis.

Follow-up leads

Correct or annotate the OCR/text-layer discrepancies for 37SFU vs 375FU, the page-1 UAP time, and other distorted page-1 timeline values.
Reconcile the D16/PR22/PR27 row-number and final-URL tensions in release metadata and graph relationships without converting them into case findings.
Seek an authoritative source export or release note that maps the PR22 annotated clip to the D16 310239ZJUL22 entry and explains the DVIDS 07.01.2022/VIRIN date tension.
Look for unredacted or less-redacted platform/sensor metadata: exact grid, field of view, sensor orientation, range, altitude, look angle, frame timestamp, and whether the PR22 clip is cropped or annotated from a longer FMV sequence.
If higher-fidelity location/geometry becomes available, rerun ordinary correlation checks for aircraft, drones, balloons, weather, meteors/astronomy, satellite/launch/reentry possibilities, and sensor/display artifacts before escalation.

Audit note

This section was added from the current wiki page, verified release-file metadata, OCR text, rendered page images, the paired PR22 DVIDS/source-media page, read-only Neo4j review, and official web checks. No Neo4j writes were made, and no Finding, Hypothesis, or ResolutionDecision conclusion is asserted here.

Limits

This page is an investigation draft, not an adjudication. The PDF gives a mission-report record and a short UAP field entry, but it does not resolve what the object was.

The file is heavily redacted. Tail number, callsign, many coordinates, names, contact details, and some operational details are obscured. The UAP description is brief: less than one minute, north-to-south motion, with no populated physical-state, altitude/depth/velocity/trajectory, RF, or effects fields. The document says weather was not a factor, but it does not provide a weather table or independent environmental analysis.

The embedded PDF pages are text/form pages only. Any visual interpretation of the object must come from the paired video or other source media, not from this PDF.

Sources

Department of War / WAR.GOV PURSUE Release 01, DOW-UAP-D16, Mission Report, Syria, July 2022, official PDF URL above.
Open released-file copy for this evidence page, SHA-256 b3b3f023d70bcce3178de9fe6a019ea6db5e5145bc7e28a49308442e190ef817.
WAR.GOV release record context for CSV row 38 and related PR22 video row context preserved in the Open Sky graph.
OCR/text coverage: seven page markers, seven pages with text, checked against rendered page images for the high-signal narrative and UAP fields.