DOW-UAP-D75, Mission Report, Gulf of Aden, July 2024

Evidence media

Official PDF release-file view: DOW-UAP-D75, Mission Report, Gulf of Aden, July 2024

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

Page 1 is a derived render from the official PDF. It shows the mission narrative, including takeoff/on-station timing, NAVCENT target-development context, the 140517ZJUL24 UAP observation line, later AFCENT retasking, and the statement that full-motion video was exploited; it is not object imagery or a sensor frame.

Derived page render from the official DOW-UAP-D75 PDF: page 5 NAVCENT ISR/UAP line

Page 5 is a derived render from the official PDF. It preserves the NAVCENT ISR block, the 38P MT tasking/start-point fragments, the 140517ZJUL24 1X UAP line, and the source statement that weather was not a factor.

Derived page render from the official DOW-UAP-D75 PDF: page 7 UAP form fields

Page 7 is a derived render from the official PDF. It shows the structured UAP fields, including initial contact 140517:00ZJUL24, maneuverability text beginning STRAIGHT FLIGHT PATH AT SAME ALTI, observer assessment Benign, observation interrogation NO, unknown propulsion/intelligent-control fields, and no reported effects on persons.

Derived page render from the official DOW-UAP-D75 PDF: page 8 UAP continuation

Page 8 is a derived render from the official PDF. It preserves the UAP continuation fields: no recovered material, no equipment effects, no observer engagement, partial 38P MT first/last coordinates, estimated low altitude and northwest trajectory, the followed-until-too-far line, and a speed comparison to a redacted flying-speed reference.

Investigation reading

This is an eight-page USCENTCOM MISREP-style PDF in the first PURSUE release. The file is not an imagery packet: the reviewed PDF pages are typed form pages with redactions, release markings, and no visible object photo, map, radar plot, FMV still, track display, or sensor-frame exhibit. The report nevertheless says full-motion video was exploited during the mission and uses FMV as the primary sensor in the ISR sections.

I read all eight OCR page sections, compared them with the selectable PDF text layer, and visually checked rendered pages. The text layer corrects several OCR rough edges: the main narrative reads as NAVCENT, not “NASCENT”; the UAP time is visible as 140517ZJUL24; page 6’s retasking precoordination appears as 30 minutes, not the 90-minute OCR variant; and the MGRS-style coordinate fragments use 38P, while OCR in places damages that prefix.

This draft does not identify the object and does not assert a finding. It records what the released file appears to say, what the graph has already modeled, and what a human investigator should verify next.

What the file appears to contain

At packet level, D75 is a redacted Air Force / USCENTCOM mission report tied by the Release 01 record to the Gulf of Aden and July 14, 2024. The report number visible on page 1 is Misrep 10194673. The form shows the mission in the AIR domain, operations-center references to the 609th, and administrative release/recommendation markings dated June 2, 2025. The PDF metadata title/subject reads DoW-UAP-D43, which does not match the visible/public file title DOW-UAP-D75; that is a custody-cleanup lead, not a reason to reassign the record.

Page	Reading notes
1	Narrative summary. A redacted aircraft took off at `140222ZJUL24`, arrived on station at `140300ZJUL24`, conducted target development for NAVCENT, and the narrative states that `1X UAP` was observed at `140517ZJUL24` in the vicinity of a partially redacted `38P MT...` coordinate. It then describes a later AFCENT retasking window, handback, landing, and says full motion video was exploited by a redacted party. No imagery is shown.
2	Administrative MSGID/MSNID page: MISREP, originator `124 ATKS`, `ACC`, `USCENTCOM`, country tasked United States, service tasked Air Force, and redacted POC/QC/approver fields.
3	Personnel/ingest/ACEQUIP page with unit/wing/operations-center fields and redacted aircraft callsign/equipment content. No visual exhibit appears in the large redacted box.
4	Timeline form. It preserves that one aircraft is involved and that the ISR primary sensor is `FMV`, while callsign, aircraft type, takeoff/landing locations, and several times are redacted on the form page.
5	NAVCENT ISR detail. Tasking type is planned; activity is ISR; task start point begins `38P MT 51...`; the GENTEXT says coordination occurred 124 minutes prior to takeoff, the asset arrived on target at about `140334ZJUL24`, observed `1X UAP` at `140517ZJUL24` near `38P MT 53...`, and was cleared off target at about `140925ZJUL24`. Weather was not a factor.
6	AFCENT retasking detail. Tasking type is dynamic; start point begins `38P MV 24...`; GENTEXT says the later tasking was coordinated 30 minutes before retasking, reports `NSTR`, and says the asset was cleared off target / returned to base at `142130ZJUL24`.
7	UAP form. Initial contact is `140517:00ZJUL24`; event type is `UAP Incident`; maneuverability is rendered as `STRAIGHT FLIGHT PATH AT SAME ALTI...`; response to observer actions is unknown; observer assessment is `Benign`; observation interrogation is `NO`; propulsion and intelligent control are unknown; advanced capabilities/materials are unknown; effects on persons are `NO`. Several key fields are blank or redacted.
8	UAP continuation. Objects/material recovered: `NO`; effects on equipment: `NONE`; observer engagement: `NO`; first/last MGRS-style coordinates are partially redacted; radii are listed as `5` with unit not visible; altitude/depth/velocity/trajectory fields are estimated where visible, with kinetic altitude `LOW`, depth `UNKNOWN`, velocity redacted, and trajectory `NW`. The visible reaction text says the observer followed the UAP until distance became too far to follow. The visible anomalous-characteristics line says the UAP’s speed was faster than a redacted flying-speed reference. The description begins `UAP HAD`, but the actual descriptive continuation and GENTEXT are redacted.

The file’s strongest source-backed content is therefore narrow: a single reported UAP line during a NAVCENT ISR tasking; FMV as mission/sensor context; estimated low/NW kinematic fields; and a short redacted UAP form indicating no observation interrogation, no engagement, no recovered material, no equipment effects, and no reported effects on persons.

Source custody and provenance

Official file title: DOW-UAP-D75, Mission Report, Gulf of Aden, July 2024
Agency: Department of War
Release: PURSUE Release 01
CSV/source-pack row: 74
Official URL: https://www.war.gov/medialink/ufo/release_1/dow-uap-d75-mission-report-gulf-of-aden-july-2024.pdf
Open Sky release-file route: /api/explore/war-gov/release-file/war-gov-dow-uap-d75-mission-report-gulf-of-aden-july-2024-852224ee
Verified source size: 792,150 bytes
Verified SHA-256: 672b79390fe6595828c71e1f3df8cb0a2290f0658c36ed724e17ea167233b771
PDF page count: 8
OCR coverage: 8 / 8 pages with text

Direct WAR.GOV HEAD and browser-style byte-range GET checks returned 403 during this review, so the page relies on the verified Release 01 file copy and hash while citing the official URL. The PDF itself is an encrypted/copy-restricted Acrobat Paper Capture file with a selectable text layer. The visible PDF metadata title/subject mismatch (DoW-UAP-D43) should be reviewed against the WAR.GOV manifest and any source-pack revision history.

Graph context

The graph has two exact records for this item: the Release 01 record node and the linked PDF asset node. The asset node carries the official/canonical PDF URL and the verified SHA-256 above. The release record carries the current-row reference for row 74, the incident date 7/14/24, incident location Gulf of Aden, and redaction flag TRUE.

Semantic extraction currently models 101 source-text claims, 66 entity mentions, 8 sensor events, and 0 table rows for this page. Treat those as navigation and audit cues, not findings. The sensor events are mostly produced by the form’s Aircraft and FMV language. The released PDF states FMV was exploited and lists FMV as the primary ISR sensor, but it does not release an FMV clip, still frame, radar return, map, object photograph, or raw sensor display for this item.

Related/candidate graph links should be used conservatively. The D75 record is naturally related to its own asset/record pair and to nearby Release 01 mission-report material. Geography-based crosslinks, including Gulf of Aden or broader regional anchors, are leads for later comparison only; they do not corroborate this event without separate source review.

Leads to check

Locate any paired or withheld FMV/source media referenced by the mission report. The PDF says FMV was exploited, but the released packet does not show the actual imagery.
Reconcile OCR/text-layer discrepancies before using exact times in analysis. The visible text layer supports 140517ZJUL24, 140334ZJUL24, 140925ZJUL24, 142130ZJUL24, and a 30-minute AFCENT retasking precoordination line; the stored OCR damages several of those fields.
Clarify the partially redacted MGRS-style coordinates: first/last locations appear as 38P MT... fragments, with exact digits redacted. Do not geocode the event from the visible fragments alone.
Review the UAP count fields. Narrative and manifest language say one UAP, while the UAP form’s Number of UAP Sighted field appears blank/redacted in the visible page.
Check whether WEATHER DID NOT PREVENTED IMINT is a source typo, OCR artifact, or form-language issue. Page 5 separately says weather was not a factor.
Review the speed sentence. The visible line only says the UAP’s speed was faster than a redacted flying-speed reference; it does not give a released measured speed.
Reconcile the PDF metadata mismatch (DoW-UAP-D43) against the visible D75 title and Release 01 record.
Run prosaic/context checks only after source-media questions are resolved: air traffic, airborne debris/balloon/UAS possibilities, sensor/FMV acquisition geometry, weather, and any known activity in the relevant 38P MT / Gulf of Aden area and time window.

Lead check notes

Partial — underlying media trail: The current Release 01 record exposes the D75 PDF only, with no DVIDS, video, or still-media pairing in the checked release metadata. The PDF says full-motion video was exploited and lists FMV as the primary ISR sensor, but the released PDF has no embedded files, image exhibits, object photograph, or video frame; any underlying FMV, still, tasking record, or exploitation note remains a missing external source.
Checked — text-layer timing and OCR quality: Rendered/selectable PDF text supports the main D75 timings used on this page: takeoff 140222ZJUL24, on station 140300ZJUL24, NAVCENT window 140334ZJUL24 to 140925ZJUL24, UAP observation 140517ZJUL24, AFCENT retasking 141041ZJUL24 to 142130ZJUL24, called-off-station 142142ZJUL24, handback 142238ZJUL24, and landing 142259ZJUL24. The current OCR can damage several of those values and can misread NAVCENT as NASCENT, so exact timeline work should cite the PDF text/rendered pages rather than OCR alone.
Partial — coordinate fragments: Page-render/text review supports partial 38P MT and 38P MV coordinate strings, including 38P MT 51..., 38P MT 53..., 38P MT 22..., and 38P MV 24..., but redactions remove the full grid values. Searches of the linked Release 01 OCR corpus found the 38P MT 51 and 38P MV 24 anchor phrases confined to D75, while broader NAVCENT/Gulf-region labels appear in other mission reports without resolving this event.
Partial — count, description, and speed fields: The narrative/release description report one UAP, and pages 1/5 visibly state 1X UAP; the structured Number of UAP Sighted field on page 7 is blank/redacted. Page 8 gives an estimated trajectory and redacted velocity field, then says the UAP's speed was faster than a redacted flying-speed reference; it does not release a measured speed, complete description, or frame-level object data.
Checked — weather wording: Page 5 states WEATHER WAS NOT A FACTOR; page 7 separately preserves the awkward source wording WEATHER DID NOT PREVENTED IMINT. Treat the latter as source-form wording or transcription-quality review material, not as an analytical weather check.
Checked — D75 versus embedded metadata: The official URL, visible title, release row 74, file size, and SHA-256 identify this file as DOW-UAP-D75. The embedded PDF title/subject reads DoW-UAP-D43, so the mismatch remains a release-metadata/source-history lead requiring manifest history or corrected-source metadata.
Blocked — ordinary prosaic checks: The released PDF does not provide full coordinates, platform geometry, raw FMV, flight tracks, sensor settings, traffic data, weather data beyond the form line, or a targetable time/location package. Regional graph links and nearby mission-report records are navigation context only until exact source pages and external data are compared.

Deep investigation — graph + web reconnaissance

Source reread and media check

The source package was reread against the verified eight-page PDF, the existing OCR text, and the rendered page images. The official PDF is still identified by SHA-256 672b79390fe6595828c71e1f3df8cb0a2290f0658c36ed724e17ea167233b771, size 792,150 bytes, PDF version 1.7, eight pages, and embedded metadata title/subject DoW-UAP-D43. The PDF is encrypted/copy-restricted and has no image objects listed by the PDF image inventory; the public evidence remains a form/MISREP packet rather than a released FMV frame, object photograph, map, radar plot, or raw track display.

The strongest new transcription check is the coordinate-prefix issue. The OCR layer still damages several page-5/page-8 strings as 30P MT / 30P MV, but the rendered pages visually support 38P MT for the NAVCENT tasking, first coordinate, last coordinate, and friendly-aircraft-location fields. Page 5 reads as a NAVCENT planned ISR task with ARRIVED ON TARGET AT 140334ZJUL24, OBSERVED 1X UAP AT 140517ZJUL24 IVO 38P MT..., and WEATHER WAS NOT A FACTOR. Page 7 preserves Initial Contact DTG: 140517:00ZJUL24, STRAIGHT FLIGHT PATH AT SAME ALTI..., Observer Assessment of UAP: Benign, Observation Interrogation ... NO, unknown propulsion/intelligent-control fields, redacted signatures, and UAP Effects on Persons: NO. Page 8 preserves 38P MT... first/last coordinate prefixes, estimated LOW kinetic altitude, UNKNOWN depth, redacted velocity, NW trajectory, no recovered material, no equipment effects, no observer engagement, the line FOLLOWED THE UAP TILL THE DISTANCE BECAME TOO FAR TO FOLLOW, and the redacted comparison sentence UAP'S SPEED WAS FASTER THAN THE [redacted] FLYING SPEED. The substantive GENTEXT/UAP narrative remains redacted after the incomplete phrase UAP HAD.

Read-only graph connections

Read-only graph checks found the expected exact PDF asset node and Release 01 record node. The asset node carries the stable official PDF URL, hash, size, and row relation. The row/record node carries current row 74, incident date 7/14/24, location Gulf of Aden, and redaction flag TRUE, but also shows a stale final_url/content-length drift pointing at a D65/Persian Gulf file. Treat the exact asset URL/hash/title as the stable identity; treat the D65 row-field drift as a provenance-cleanup item.

Graph semantic coverage for this asset is 101 machine-extracted claims, 66 entity mentions, 8 sensor events, and 10 text chunks. The sensor events are marked machine_extracted_needs_human_review / not_a_finding and are mostly source-word cues from Aircraft and FMV; they are not released radar/IR/telemetry proof. Direct graph neighbors include the D75 release record and a stale/non-current relation to DOW-UAP-PR20, Unresolved UAP Report, Kuwait, May 2022, apparently through shared content-length/provenance drift rather than source-level event corroboration. No CANDIDATE_CROSSLINK records were returned for this exact D75 asset.

Exact text-anchor checks are useful but show why page-image review matters: 38P MT, FOLLOWED THE UAP TILL, and the 140517...ZJUL24 timing anchors are confined to D75/derived D75 records, while the OCR-damaged 30P MT also appears in the D75 asset text. The graph has no exact modeled same-day LaunchEvent, AstronomyEvent, or Aden-specific WeatherEvent match for 2024-07-14, and the Satellite label currently has no nodes. This is graph-coverage context only, not an exclusion of launch, satellite, weather, balloon, aircraft, or maritime explanations.

External provenance and official-source checks

A direct official PDF byte-range request to WAR.GOV succeeded during this check: 206 Partial Content, application/pdf, Content-Range: bytes 0-15/792150, with PDF magic bytes %PDF-1.7. The WAR.GOV landing page and both checked CSV paths returned 403 Access Denied, so the page still relies on the verified official-primary PDF bytes plus the preserved Release 01 source-pack row metadata for manifest context.

Internet Archive availability/CDX checks were not usable during this pass (429 Too Many Requests / timeout). DVIDS title search returned an empty 202 response, and AARO/Defense.gov title searches returned 403 from this environment. No public DVIDS video/still pairing was found in the checked release metadata or graph fields. These are negative/blocked provenance checks, not evidence that no underlying FMV exists.

Prosaic checks and follow-up leads

Prosaic evaluation is still blocked by source limits. The public file gives a date/time, Gulf of Aden label, partial 38P MT grid fragments, FMV mission context, and the source's own low/NW/faster-than-redacted-reference wording, but it withholds the full coordinates, platform identity, look direction, sensor settings, raw FMV, target track, traffic/maritime context, weather data beyond the form line, and any exploitation product. The first follow-up should be a custody/media search for the referenced FMV/exploitation material, followed by targeted checks for ordinary aircraft, UAS, balloon/debris, maritime activity, sensor/display artifacts, weather/cloud visibility, satellites/space debris, and launch events using the unredacted geometry if it is ever released.

Audit note

This section does not identify the object, resolve the case, or promote graph machine extractions into findings. It narrows the public record to source-backed D75 facts, separates OCR damage from page-render readings, flags stale graph provenance fields, and records which official web checks succeeded or were blocked.

Limits

This file is heavily redacted. Exact platform, tail number, aircraft type, most coordinates, speed reference, UAP physical state, signatures, event serial, and the substantive GENTEXT/UAP description are missing or withheld. The PDF contains no released object imagery, no FMV frame, no radar plot, no map, no raw track display, no independent witness statement, and no post-event technical analysis. The Benign, UNKNOWN, NO, LOW, and NW fields are source-form entries, not an independent resolution.

The graph’s extracted claims are useful for finding passages, but repeated form text and redaction language can inflate counts. This page should remain a graph_investigation_draft until a human reviewer checks the full release record, any available official manifest revisions, and any linked or withheld media.

Sources

Official WAR.GOV PDF: https://www.war.gov/medialink/ufo/release_1/dow-uap-d75-mission-report-gulf-of-aden-july-2024.pdf
Open Sky release-file route: /api/explore/war-gov/release-file/war-gov-dow-uap-d75-mission-report-gulf-of-aden-july-2024-852224ee
PURSUE Release 01 source record: DOW-UAP-D75, Mission Report, Gulf of Aden, July 2024, CSV/source-pack row 74.
Verified PDF hash: 672b79390fe6595828c71e1f3df8cb0a2290f0658c36ed724e17ea167233b771.
Review basis for this draft: complete 8-page OCR text, selectable PDF text, rendered-page visual checks, and existing graph records for the Release 01 record/PDF asset.