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

DOW-UAP-D32, Mission Report, Syria, October 2024

Open Sky release file copy of the official D32 PDF — verified as a 651,740 byte, ten page PDF with SHA 256 fd4deb1e48fcfa7fd2370b6459877882e6d6fdd0226ecaa881a45fba690172df. Paired Release 01 video records: PR31, PR32, and PR33. The release descriptions tie these short FMV clips…

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

DOW-UAP-D32, Mission Report, Syria, October 2024

Evidence media

  • Open Sky release-file copy of the official D32 PDF — verified as a 651,740-byte, ten-page PDF with SHA-256 fd4deb1e48fcfa7fd2370b6459877882e6d6fdd0226ecaa881a45fba690172df.
  • Paired Release 01 video records: PR31, PR32, and PR33. The release descriptions tie these short FMV clips to D32; they still need their own frame-level review before any clip-to-timestamp alignment is treated as checked.

Derived page renders from the official PDF are included below for source-document orientation. They are page renders from the PDF, not standalone object imagery.

Derived page render from the official D32 PDF: page 1 mission narrative and administrative opening Page 1 places the UAP line inside a longer Operation Inherent Resolve ISR mission narrative and records mission-hour, FMV, and SIGINT totals.

Derived page render from the official D32 PDF: page 6 ISR-to-UAP bridge Page 6 is the ISR bridge page that points from the mission tasking block to OBSERVED UAP ACTIVITY (SEE UAP 1).

Derived page render from the official D32 PDF: page 7 UAP form start Page 7 starts the UAP form and carries the rendered/selectable 201559:00ZOCT24 initial-contact field plus the FMV light/glare wording.

Derived page render from the official D32 PDF: page 8 UAP form continuation Page 8 continues the UAP form with the source entries for Plasma, UNKNOWN propulsion, LIGHT signatures, event serial, no reported effects, no recovered material, and the not-a-lasing-event note.

Derived page render from the official D32 PDF: page 9 UAP narrative and ISR continuation Page 9 contains the quoted MISHAPEN AND UNEVEN BALL OF WHITE LIGHT wording and the 1559Z-1644Z glare/halo timeline before the report moves into the next ISR block.

Investigation reading

This is a ten-page Department of War mission report for a Syria event on 20 October 2024. The reviewed release file is a 651,740-byte PDF with SHA-256 fd4deb1e48fcfa7fd2370b6459877882e6d6fdd0226ecaa881a45fba690172df. The file is a structured MISREP-style form: narrative, administrative fields, equipment prompts, ISR tasking blocks, UAP form fields, and a GENTEXT/UAP narrative. Rendered-page review found no embedded object photograph, map, radar plot, FMV still, or other sensor frame inside this PDF. The visual evidence for the event appears to be in the paired short DVIDS videos, not in this document.

The main UAP entry is on pages 7-9. The rendered and selectable PDF text read the initial-contact field as 201559:00ZOCT24 and the event serial as 201559ZOCT2024. The UAP form says a light/glare of unknown origin flashed across the FMV camera feed, that observer actions produced NO CHANGE, that the observer assessment was Benign, and that observation interrogation of the UAP was NO. Page 8 adds that the listed physical state is Plasma, propulsion is UNKNOWN, signatures are LIGHT, no intelligent control is assessed, no advanced capabilities/materials are listed, RF fields are blank/dashed, no effects on persons or equipment are recorded, no material was recovered, and the aircrew assessed the event as not a lasing event.

The strongest descriptive source language is on page 9. It describes the UAP as MISHAPEN AND UNEVEN BALL OF WHITE LIGHT and says that from 1559Z-1644Z personnel observed multiple glares or lights from an unknown origin at different angles and directions. The same paragraph says light/glare crossed directly on the FMV camera at 1559Z, 1602Z, and 1644Z, and that a light/glare halo effect appeared at the top of the FMV feed at 1609Z and 1620Z. It closes by saying the aircrew considered there to be no mission impact or change and that the UAP was benign. Those are source statements, not a resolution.

A full-text pass over the PDF and stored OCR surfaced several OCR/text tensions. The rendered/selectable page text reads takeoff from OJMS at 0823Z, first 7-line at 0649Z, arrivals at 1102Z, 1230Z, and 2318Z, return at 0124Z, and landing at OJMS at 0447Z. Stored OCR variants misread some of these fields as OIMS, 0852Z, 0609Z, 1101Z, 1203Z, 2316Z, and 0132Z. The public reading above follows the rendered/selectable source text and treats the OCR variants as extraction-quality leads.

What the file appears to contain

PageWhat is on the pageUAP relevance
1Mission narrative and classification/admin start. It states takeoff, three FMV/SIGINT taskings, a UAP observation at 1559Z, return/landing, and mission totals: 20:24 mission hours, 14:22 FMV hours, 3 FMV taskings, 13:02 SIGINT hours, and 3 SIGINT taskings.Establishes the event within a longer Operation Inherent Resolve ISR mission.
2Administrative MSGID/POC/QC form fields for the MISREP.Mostly custody/context, not observation evidence.
3Approver/ingest and aircraft-equipment prompts, including radar/RWR/MWS/IRCM/ECM fields that are mostly blank.Important for graph cleanup: equipment prompts should not be treated as populated sensor returns.
4Equipment/timeline form. Populated fields include target pod AN/DAS-4, avionics AH/GMESH/SANTA FE, LINK 16, one aircraft, takeoff from OJMS, takeoff time 200823:00ZOCT24, Mode 3 33300, and on-station time 201102:00ZOCT24.Establishes platform/sensor context but still no raw image frame.
5Off-station and landing fields, then ISR 1. It records off-station 210124:00ZOCT24, landing 210447:00ZOCT24, engine shutdown 210457:00ZOCT24, ISR time 201102:00ZOCT24 to 201200:00ZOCT24, primary sensor FMV, sensors available SANTA FE, and a GENTEXT/ISR note about observed local activity and NSTR.Context before the UAP block.
6Weather/effectiveness and ISR 2. It records clear weather, FMV / SANTA FE, dynamic target development, one EEI, and a GENTEXT/ISR sentence: FROM 1559Z-1644Z, OBSERVED UAP ACTIVITY (SEE UAP 1).First page-level bridge from ISR tasking into the UAP entry.
7Start of the UAP form. It records initial contact 201559:00ZOCT24, event type UAP Incident, light/glare flashing across the FMV camera feed, no change to observer actions, friendly aircraft altitude about 20,088FT, orbit trajectory, observer assessment Benign, speed 144 KNOTS, and observation interrogation NO.Core structured UAP report fields.
8Continuation of the UAP form. It records physical state Plasma, propulsion UNKNOWN, signatures LIGHT, no intelligent control, no advanced capabilities/materials, RF blank/dashed, event serial 201559ZOCT2024, no effects, no recovery, no engagement, and the not-a-lasing-event note.Core structured UAP report fields and source-level limitations.
9GENTEXT/UAP plus ISR 3. It gives the descriptive phrase MISHAPEN AND UNEVEN BALL OF WHITE LIGHT and the detailed glare/halo timeline from 1559Z-1644Z. It then continues into a later ISR block.Main descriptive narrative for the event.
10Closing weather/effectiveness fields: clear weather, intel gap filled Yes, and effectiveness SATISFACTORY.End-of-report context; no additional object imagery.

Across the full document, targeted term review found repeated FMV, SIGINT, SANTA FE, LIGHT, GLARE, HALO, PLASMA, BENIGN, and CLEAR WX language. It did not find explicit balloon, meteor, drone, UAV, birds, or reflection terms in this PDF. That absence does not eliminate those checks; it only means the document itself does not spell them out.

Source custody and provenance

The release identifies this as an official Department of War / PURSUE Release 01 file. The official PDF URL is:

The Open Sky release-file endpoint for the public explorer is:

The Open Sky release-file copy was verified against SHA-256 fd4deb1e48fcfa7fd2370b6459877882e6d6fdd0226ecaa881a45fba690172df and file size 651,740 bytes. PDF metadata reports title/subject DOW-UAP-D32, Mission Report, Syria, October 2024, ten letter-size pages, encrypted copy restrictions, and no image objects listed by PDF image inspection. Stored Frontier OCR covers 10 of 10 pages, and the PDF also has a selectable text layer that is useful for correcting several OCR misreads.

This PDF is tied in the release materials to the short Syria October 2024 video records DOW-UAP-PR31, DOW-UAP-PR32, and DOW-UAP-PR33. The paired DVIDS video pages are useful next sources because the PDF itself does not contain the FMV frames described by the UAP narrative:

Graph context

The graph has this item as an official primary Document with associated release-record context, OCR/text chunks, extracted claims, entities, and sensor-event records. The current semantic counts attached to the page are 231 extracted claims, 168 entity mentions, and 31 sensor-event records. Those counts are navigation aids, not findings.

The most useful graph signals are the repeated source-backed references to FMV/SIGINT collection, SANTA FE, Operation Inherent Resolve, USCENTCOM, AARO release custody, and the page 7-9 UAP form fields. The main caution is that the graph can over-surface sensor language from form prompts. Page 3 contains radar, RWR, MWS, IRCM, ECM, chaff, flare, and weapon prompts, but those fields are blank or not populated as UAP sensor returns. The source-backed observation language is FMV-centered, and the UAP form explicitly says observation interrogation of the UAP was NO.

Related graph records include the paired DVIDS videos for PR31-PR33 and other Release 01 mission reports from Syria, Greece, and the Middle East. Any location-only Syria crosslinks to older archives or prosaic-correlation sources should be treated as leads for later checking, not as same-event matches.

Leads to check

  • Review PR31, PR32, and PR33 directly as video items, frame by frame if possible, and compare each clip's visible timing with the PDF's 1559Z, 1602Z, 1609Z, 1620Z, and 1644Z source statements.
  • Reconcile the row numbering across release materials before using CSV row numbers in public-facing citations. The release metadata for this PDF lists rows 47, 85, 86, and 87, while the paired video pages expose rows 48/88, 49/89, and 50/90.
  • Treat the page 7 Initial Contact DTG and page 8 event serial as 201559... based on the rendered/selectable PDF, and keep the stored OCR variant 201350... as an extraction-quality issue to repair or annotate.
  • Check whether the MISHAPEN source spelling on page 9 is a form typo for the manifest's misshapen wording; do not silently normalize it when quoting the document.
  • Run optical/sensor-artifact checks against the video evidence: lens flare, glare, sensor saturation, top-edge frame artifacts, platform motion, sun/moon geometry, and any known FMV display overlays. The PDF itself says the aircrew did not assess the event as lasing, but that is not a full optical analysis.
  • External astronomy, weather, satellite, launch/reentry, and aircraft/drone checks need unredacted geometry or defensible approximations. The PDF preserves only partial MGRS-like grid fragments and redacted platform details.

Lead check notes

  • Partial — PR31/PR32/PR33 video pairing: The current linked corpus includes separate PR31, PR32, and PR33 Release 01 video pages and playable release-file endpoints. Their descriptions tie short FMV clips to D32, but the clips still need dedicated frame-level review before the PDF's five timeline statements are matched to specific frames.
  • Partial — row-number reconciliation: The PDF release metadata carries row 47 with related rows 85, 86, and 87; the paired video pages carry 48/88, 49/89, and 50/90. Treat that as a citation/provenance cleanup issue, not as evidence of separate events.
  • Checked — source-text timing field: Selectable PDF text and the page-7 render support 201559:00ZOCT24; the stored OCR variant 201350:00ZOCT24 was not found in the selectable PDF text and remains an extraction-quality issue.
  • Checked — source spelling: Selectable PDF text contains MISHAPEN AND UNEVEN BALL OF WHITE LIGHT; the release description uses misshapen. Public quotations should preserve the page text and keep the normalized spelling as manifest wording.
  • Checked — PDF media scope: The verified ten-page PDF and derived page renders show source-document pages, not embedded object imagery, maps, radar plots, or FMV stills. The visual evidence to inspect is in PR31-PR33, not inside the PDF.
  • Needs external source — prosaic and environment checks: Lens/glare/sensor-display checks require direct video review; astronomy, weather, satellite, launch/reentry, aircraft, and drone checks require unredacted geometry or defensible approximations that the PDF does not provide.

Deep investigation — graph + web reconnaissance

Source reread

A second source pass rechecked the official D32 PDF text layer, the stored OCR, and the rendered pages. The UAP form fields on pages 7-8 read as a 201559:00ZOCT24 initial contact / event serial / DoD acquisition time, LIGHT/GLARE FLASHED OF UNK ORIGIN FLASHED ACCROSS FMV CAMERA FEED, friendly-aircraft trajectory ORBIT, friendly-aircraft speed 144 KNOTS, observer assessment Benign, physical state Plasma, propulsion UNKNOWN, signature LIGHT, no intelligent control, no effects on persons, no recovered material, no engagement, and no lasing. Page 9 then gives the key narrative: MISHAPEN AND UNEVEN BALL OF WHITE LIGHT; from 1559Z-1644Z multiple glares or light were observed from unknown origin; at 1559Z, 1602Z, and 1644Z one light/glare crossed directly on the FMV camera; and at 1609Z and 1620Z a light/glare halo effect was observed at the top of the FMV feed. The source says aircrew assessed no mission impact or change and the UAP was benign.

The OCR remains useful for search but not authoritative where it conflicts with the rendered page. In particular, OCR variants around the UAP block can misread the 201559 timestamp and some form labels; public quoting should follow the PDF text/render review above.

Graph connections checked

Read-only graph reconnaissance matched the canonical D32 asset as an official primary Document with the same official PDF URL and SHA-256 already shown on this page. The asset is connected to 16 text chunks, 231 machine-extracted claim records, 31 machine-extracted sensor-event records, related release-record documents, and the PR31/PR32/PR33 DVIDS video records. Those graph records are navigation aids only: the claim and sensor-event nodes remain machine extracted and do not create a conclusion.

The strongest graph-supported cluster is narrow and source-backed: D32 plus the three paired Syria October 2024 DVIDS videos, PR31, PR32, and PR33. Frame/contact-sheet review keeps that cluster unresolved but useful: PR31 preserves a tiny first-second reddish/orange top-band mark near black masks and magenta interface marks; PR32 preserves the official 00:02-00:04 top-edge red/white highlight window; and PR33 preserves semi-transparent orange/red overlay-like regions during roughly the first 2.5 seconds. None of those public clips provide enough metadata, resolution, or unredacted geometry to measure distance, speed, altitude, or cause.

Two graph-provenance cautions remain. First, the D32 asset uses release rows 47, 85, 86, and 87, while the video pages carry 48/88, 49/89, and 50/90; treat that as citation cleanup, not event-resolution evidence. Second, exact-hash checking surfaced several release-record nodes for other Release 01 rows carrying the D32 PDF body hash. The canonical D32 asset URL/title/hash still identify this PDF, but those release-record hash echoes should not be treated as independent duplicate documents without row and URL reconciliation.

Official web reconnaissance

The direct WAR.GOV/PURSUE PDF and CSV URLs returned access-denied responses from this cron environment, so the locally archived official release file remains the verified copy for text and hash review. The paired DVIDS pages were reachable and preserve official custody for the videos: PR31 is DVIDS 1006076, DOD_111688970, length 00:00:05, date posted 05.07.2026 23:35; PR32 is DVIDS 1006078, DOD_111688997, length 00:00:06, date posted 05.07.2026 23:28; PR33 is DVIDS 1006079, DOD_111689005, length 00:00:05, date posted 05.07.2026 23:35. DVIDS lists SY as the location and a 10.01.2024 date-taken/VIRIN cue for the three videos, while D32's internal UAP fields point to 20 OCT 2024. That date tension is a provenance issue to reconcile before using the DVIDS date as event timing.

Prosaic checks and open limits

The source itself gives one useful environmental clue: the ISR blocks report CLEAR WX. That is not enough to clear weather, astronomy, aircraft, drone, launch/reentry, or satellite possibilities, because exact coordinates, platform geometry, look angle, sensor settings, and raw FMV are redacted or absent. The first prosaic lane remains optical/display/sensor handling: lens or sensor glare, top-edge frame effects, false-color or thermal processing, black masking/redaction boundaries, magenta display symbology, compression/resampling, and platform/sensor motion. The page should therefore preserve the D32 source language and paired-video visual cues, but not escalate this cluster beyond unresolved source evidence.

Audit note

This deep pass added no Neo4j writes and made no finding. It tightened the source-text hierarchy: PDF render/text first, OCR second, graph extraction third, and DVIDS video pages as paired official media context. Follow-up work should reconcile row/date provenance, compare PR31-PR33 against the five D32 timeline statements, and seek higher-fidelity or less-redacted FMV/metadata before attempting a prosaic resolution.

Limits

This page is an investigation draft, not a finding. The PDF is a structured source document and does not include the underlying FMV frames. Many operational details are redacted, including identities, callsigns, exact coordinates, and parts of platform information. Some fields are form prompts rather than populated observations. The terms Plasma, Benign, LIGHT, and UNKNOWN are preserved as source entries, not adopted as Open Sky conclusions.

The source includes classified/declassification markings and FOIA exemption text, but those markings do not by themselves adjudicate what the visual feature was. The report supplies a mission context, a UAP form entry, and a narrative of light/glare seen on an FMV feed. It does not supply enough unredacted geometry or raw sensor data to resolve the event from the PDF alone.

Sources