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

DOW-UAP-D74, Mission Report, Syria, November 2023

Official PDF release file view: DOW UAP D74, Mission Report, Syria, November 2023

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

DOW-UAP-D74, Mission Report, Syria, November 2023

Evidence media

Derived page render from the official DOW-UAP-D74 PDF: page 1 mission narrative

Page 1 is a derived render from the official PDF. It shows the mission-narrative timeline, including the 2153Z UAP observation line and the later RTB/handback/landing context; it is not object imagery or a sensor frame.

Derived page render from the official DOW-UAP-D74 PDF: page 9 UAP fields

Page 9 is a derived render from the official PDF. It shows the structured UAP fields, including initial contact 092153:00ZNOV23, observer assessment Benign, redacted signatures, estimated kinetic altitude, and the source spelling CONSISTANTLY in the advanced-capabilities line.

Derived page render from the official DOW-UAP-D74 PDF: page 10 UAP narrative

Page 10 is a derived render from the official PDF. It preserves the GENTEXT/UAP narrative for the bouncy-ball-shaped probable UAP, including the ~424KN / 7MIN wording and the statement that no emissions came from the probable UAP.

Investigation reading

This released file is a ten-page USCENTCOM MISREP-style form packet. It is not an image or video exhibit. The rendered PDF pages show typed form text, redactions, release markings, and structured reporting fields; no page contains a photo, map, radar plot, sensor still, or embedded video frame.

The UAP-relevant material is concentrated at the end of the packet. The mission narrative says that on 9 November 2023, while returning to base, a redacted operator observed an unidentified aerial phenomenon at a partly redacted coordinate. The structured UAP block gives the initial contact as 092153:00ZNOV23, event type UAP Incident, observer assessment Benign, physical state Solid, propulsion means UNK, maneuverability observations NONE, response to observer action NO, no third-party observers, no RF frequency, no recovered material, no effects on persons, and no effects on equipment.

The clearest narrative line appears in the GENTEXT/UAP section: while RTB at 2153Z, a redacted observer saw 1X PROB HC UAP shaped as a bouncy ball come from the south at near co-altitude, drop altitude, safely pass the aircraft, and maintain ~424KN for about seven minutes before becoming out of range. The same page says no emissions came from the probable UAP, it was not considered a threat to the aircraft or public safety, and it had no effects on the aircrew.

Two cautions matter for reading this page. First, the source itself spells CONSISTANTLY; the corrected word consistently appears in the public release description, but the visible form uses the misspelling. Second, the phrase PROB HC UAP is visible but unexplained in the released text, so this draft does not expand the acronym or treat it as an identification.

What the file appears to contain

PagesContents observed in the rendered/source text
1-2Mission narrative and administration. The narrative gives takeoff/handover/tasking, FMV/SIGINT collection, a 2153Z UAP observation, RTB at 1933Z, handback at 2254Z, landing, and full-motion-video exploitation by a redacted party. Page 2 identifies INHERENT RESOLVE, domain AIR, USCENTCOM, report type MISREP, mission type ISR, and Air Force tasking.
3POC/QC/approver/ingest contact fields. Names, units, phone numbers, and email fields are redacted or unavailable.
4-5ACEQUIP and timeline fields. The form shows one aircraft, redacted callsign/asset details, takeoff time 090217:00ZNOV23, redacted takeoff/landing fields, and the first on-station block.
6ISR block from 090431:00ZNOV23 to 090554:00ZNOV23. Primary sensor is listed as FMV; tasking is dynamic target development; FMV or Image File Name is blank/dash; weather is clear. The ISR narrative describes ordinary target-development observations, not the UAP event.
7-8Second ISR block from 090805:00ZNOV23 to 091933:00ZNOV23, also target development with clear weather and satisfactory effectiveness. The bottom of page 8 begins the UAP section.
9Main UAP fields: initial contact 092153:00ZNOV23; friendly aircraft location and coordinates partly redacted; friendly aircraft trajectory SOUTHEAST; observer assessment Benign; UAP physical state Solid; propulsion UNK; intelligent control NO; signatures redacted; RF frequency NONE; event serial 092153ZNOV2023-CENTCOM; visible coordinate prefixes include 37DST69 and 37SFT28; kinetic altitude 170 with estimated accuracy.
10UAP continuation and narrative: kinetic velocity accuracy Estimated; kinetic velocity 424KN; acquisition date 092153:00ZNOV23; reaction to observation/interrogation/engagement NO; anomalous characteristics/behaviors N/A; UAP description partly redacted; event text describes the bouncy-ball-shaped probable UAP, southward approach, altitude drop, safe pass, ~424KN, seven-minute watch, no emissions, no threat/public-safety concern, and no aircrew effects.

The form mentions FMV/SIGINT collection and full-motion-video exploitation in the mission context, but the released PDF itself does not include the exploited video, a still image, a radar return, a map, or a raw sensor display.

Source custody and provenance

A provenance cleanup lead remains: the PDF's embedded metadata title/subject reads DoW-UAP-D42, while the official URL, visible release title, file title, and release record identify this asset as DOW-UAP-D74. That mismatch should be treated as a custody/metadata issue, not as a reason to reassign the document without checking the release manifest and the original PDF.

Graph context

The evidence graph has two exact records for this item: a release-record document for WAR.GOV row 73 and a linked PDF-asset document for the official PDF URL. The semantic layer currently surfaces 141 extracted claim records, 113 entity mentions, and 12 sensor/platform events.

Those graph rows are useful for navigation, but they need careful reading. The sensor/platform events mostly come from form labels and mission-context language: FMV, SIGINT, Aircraft, and full-motion-video exploitation. They are not the same thing as released raw sensor evidence. The PDF does not expose a radar plot, FMV frame, sensor still, or original video file.

The graph also relates this record to nearby WAR.GOV Release 01 records, including DOW-UAP-D64, Mission Report, Iran, November 2020 and DOW-UAP-PR19, Unresolved UAP Report, Middle East, May 2022. Those are navigation links only at this stage; this draft does not assert that the cases describe the same object, same platform, or same explanation.

The rendered-page pass corrected several OCR rough edges that matter for public reading: page 1 shows 0217Z, 0229Z, 0355Z, 0431Z, 0539Z, 0805Z, 2153Z, and 1933Z; page 9 shows friendly aircraft trajectory SOUTHEAST, not the rough OCR phrase SOUTHWARD AT; page 9 shows event serial 092153ZNOV2023-CENTCOM; and pages 9-10 show the source spelling CONSISTANTLY.

Leads to check

  • Locate whether any releasable underlying FMV, still frame, tasking record, or exploitation note exists for the 2153Z observation. The PDF says full-motion video was exploited, but this released file does not include the video or a still.
  • Verify the visible phrase 1X PROB HC UAP and whether HC is an acronym, OCR artifact, or redaction-adjacent form language.
  • Reconcile the release title/URL DOW-UAP-D74 with the embedded PDF metadata value DoW-UAP-D42.
  • Clarify whether Kinetic Altitude: 170 and Kinetic Velocity: 424KN are observer estimates, platform-derived estimates, or form-entered values from another source field.
  • Preserve the form's limits around emissions and signatures: the narrative says no emissions, while the UAP Signatures field is redacted.
  • Run ordinary prosaic correlation checks before any escalation: military/coalition traffic, drones or aircraft, balloons or other aerial objects, local mission geometry, weather/visibility, and sensor/exploitation context. No such check is completed by this page.

Lead check notes

  • Partial — underlying media trail: The current Release 01 record exposes the D74 PDF only, with no DVIDS/video/still pairing in the checked release metadata. The PDF references FMV/SIGINT collection and says full-motion video was exploited, but the ISR fields leave FMV or Image File Name blank/dash and the PDF has no embedded files or image exhibits; any underlying FMV, still, tasking record, or exploitation note remains a missing external source.
  • Partial — 1X PROB HC UAP: Page-10 render review supports the visible phrase 1X PROB HC UAP; the stored OCR can misread that token as PROB UC. The linked Release 01 OCR corpus search found the 092153, bouncy ball, and 424KN anchors confined to this D74 packet, and the source does not define HC, so the acronym expansion remains unresolved.
  • Checked — D74 versus embedded metadata: The official URL, visible title, release row, file size, and SHA-256 identify this file as DOW-UAP-D74. The embedded PDF title/subject still reads DoW-UAP-D42; resolving why requires official manifest-history or corrected-source metadata, not reinterpretation from this page alone.
  • Partial — estimated altitude and velocity: Page 9 marks Kinetic Altitude Accuracy: Estimated and gives Kinetic Altitude: 170; page 10 marks Kinetic Velocity Accuracy: Estimated and gives Kinetic Velocity: 424KN. The released PDF does not show whether those are observer estimates, platform-derived estimates, or values copied from another source field.
  • Checked — emissions versus signatures: Page 10 says no emissions came from the probable UAP, while page 9 keeps UAP Signatures redacted. Those are separate source fields and should stay separate in any public summary.
  • Blocked — ordinary prosaic checks: Page renders support 092153:00ZNOV23, clear weather fields, and partial coordinate prefixes such as 37DST69 and 37SFT28, but the full coordinates, platform geometry, raw FMV, flight tracks, and external traffic/weather/balloon/space-object data are not present in the released PDF.

Limits

This draft is not a finding and does not identify the object. The source is heavily redacted, gives only partial coordinates, does not release the underlying FMV, and provides no raw radar, imagery, map, or independent witness packet. Several key fields are blank, redacted, estimated, or unexplained. The official description's mph conversion and polished wording should be kept separate from the visible form text, which records 424KN and uses the misspelling CONSISTANTLY.

Deep investigation — graph + web reconnaissance

Source reread and media check

The official-primary PDF copy verifies as a 719044-byte, ten-page PDF with SHA-256 30708df4aa8484c668d3c3694560f5b57d5a10b6b3da1cfb826a925d9cc806e1. PDF metadata still reports title/subject DoW-UAP-D42, while the release title, URL, row, cached bytes, and page renders identify the file as DOW-UAP-D74; that remains a metadata/custody cleanup issue, not a content reassignment. The PDF is copy-restricted/encrypted, has no embedded image objects in pdfimages, and has 0 embedded files by pdfdetach, so the public evidence packet is a text/form MISREP rather than released object imagery, radar, FMV, or telemetry.

Representative render review tightened several OCR-sensitive details. Page 1 is mission-narrative text only and shows the UAP observation line in the broader ISR timeline, including takeoff/handover/tasking anchors, 2153Z, an OCR-sensitive RTB time rendered around 1933Z/1935Z, 2254Z, 2319Z, and the statement that full-motion video was exploited by a redacted party. Page 9 visibly gives Initial Contact DTG: 092153:00ZNOV23, friendly-aircraft trajectory SOUTHEAST, event serial 092153ZNOV2023-CENTCOM, first/last coordinate fragments 37DST69... and 37SFT28..., Kinetic Altitude Accuracy: Estimated, and Kinetic Altitude: 170. Its advanced-capabilities line reads YES, TRAVELED ~424KN CONSISTANTLY FOR AT LEAST 7MINS IN THE SHAPE OF A BOUNCY BALL. Page 10 supports the narrative phrase 1X PROB HC UAP shaped as a bouncy ball, coming from the south near co-altitude, dropping altitude, safely passing the aircraft, maintaining ~424KN, going out of range after 7MIN, and producing no emissions, threat assessment, equipment effects, or aircrew effects. The earlier OCR variant PROB UC should be treated as an OCR error unless another source proves otherwise.

Graph connections and extraction limits

The graph has a stable exact asset record for the official PDF URL and hash, plus release-record/navigation nodes. Semantic material attached to the asset currently includes 141 machine-extracted Claim nodes, 113 EntityMention nodes, and 12 SensorEvent nodes. The claim/entity records are useful as an index into the text, but their status remains machine-extracted and not a finding. The sensor-event records mostly come from source words such as FMV, SIGINT, and Aircraft in ordinary ISR/tasking fields, plus the narrative statement that full-motion video was exploited. They do not mean that a raw FMV clip, radar plot, image still, or sensor return has been released for this D74 event.

Graph provenance also shows row/record drift that should stay out of analytic interpretation: one D74-titled release-record node carries a stale D64 final-file URL, while a PR19-titled release-record node carries the D74 PDF URL/byte length. The exact asset URL/hash is the reliable anchor. RELATED_TO links to D64/D74/PR19 and low-score CANDIDATE_CROSSLINK records into broad CIA/AMS documents are audit/navigation leads only; they do not corroborate this sighting or imply a shared object, platform, explanation, or historical source.

External provenance and web reconnaissance

The cached release CSV row for D74 lists Release Date 5/8/26, Type PDF, Department of War, incident date 11/9/23, incident location Syria, blank video/PDF-pairing fields, and no DVIDS video ID. During this check, direct WAR.GOV PDF, thumbnail, landing-page, and CSV probes returned 403 Access Denied from the official server, which is an access/custody condition rather than a contradiction of the verified cached official-primary file. The Internet Archive Wayback availability API returned an exact-URL closest snapshot for the official PDF at timestamp 20260508200703. DVIDS search returned an AWS/WAF interstitial rather than a usable result, and AARO/Defense.gov search probes returned 403; none of those probes surfaced a public companion video, still, or mission packet.

Prosaic checks and blockers

The source itself supplies clear-weather fields for the ISR blocks and repeatedly places the event inside a redacted USCENTCOM ISR mission, but it withholds the pieces needed for ordinary correlation: full coordinates, platform identity, look direction, sensor settings/FOV, raw FMV, track history, external aircraft/drone/balloon traffic, local weather at the exact geometry, satellite/space-object context, and any exploitation product. Exact graph context probes for 2023-11-09 did not return modeled same-day astronomy, weather, launch, or satellite-reentry records, but that is only a graph-coverage note and not an external exclusion. The 424KN velocity and 170 altitude entries are marked estimated in the source and should not be promoted into performance claims without the missing geometry and raw sensor/source packet.

Follow-up leads and audit note

  • Seek any official follow-on release for the underlying FMV/exploitation record, tasking record, or still frame referenced by the MISREP.
  • Reconcile the D74 content identity against the embedded DoW-UAP-D42 PDF metadata and the graph row drift around D64/PR19.
  • Preserve 1X PROB HC UAP, CONSISTANTLY, 424KN, and the estimated altitude/velocity fields as source text; separate those from the polished release blurb's mph conversion and corrected spelling.
  • Keep the case unresolved: this page documents source facts, graph provenance, and blocked prosaic checks only. It does not create a finding, hypothesis, or resolution decision.

Sources