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

DOW-UAP-D58, Range Fouler Debrief, NA, October 2020

Official PDF via Open Sky release file endpoint: DOW UAP D58, Range Fouler Debrief, NA, October 2020.

Release 01#war-gov#pursue#release-01#official-source#evidence#range-fouler#pdf

DOW-UAP-D58, Range Fouler Debrief, NA, October 2020

Evidence media

Derived page render from the official D58 PDF: Range Fouler Debrief form page 1

This derived page render shows the complete one-page range-fouler form. It is a source-document render, not object imagery: the released PDF contains no standalone photograph, map, radar plot, or video frame. The visible narrative records radar lock and target-pod video, 2 IR SIGNIFICANT CONTACTS, red blinking strobes, and noise-jamming language, but the underlying target-pod video or display-tape file is not included in this PDF.

Investigation reading

This is a one-page Range Fouler Debrief form released in WAR.GOV/PURSUE Release 01. I read the complete OCR text, compared it against a rendered page image, checked the PDF metadata/page structure, and verified the released file hash. The draft status is graph_investigation_draft; the investigation status remains needs_human_review; this page asserts not_a_finding.

The source file is a 301,419-byte PDF with one scanned page image. Its SHA-256 is c2bd370cdadc2f17649830713d55731aa22ceb76940fd64ae7ffc86fc0559261. The official row identifies the incident date as 10/27/20 and the location as N/A. The PDF metadata title/subject reads DoW-UAP-D35, which does not match the D58 title, URL, or visible page content; that looks like a provenance/metadata cleanup lead rather than evidence that this page is D35.

What the file appears to contain

The form records a nighttime detection on 10/27/20 at 01:12:21 Z. Visible form fields show rank O-3, squadron 77 EFS, mission description DCA, LFE? No, contact altitude 26000, altitude constant No, and the contact moving Yes. Direction/speed is entered as 060/20; the form shows the example format but does not define units on the visible page.

The tracking fields are narrow but important. The form says Radar Equipped: Other, Stable Trackfile?: Yes, # of Contacts in "Group": 2, and Tally Achieved is checked. AIM-9x self-track and ATFLIR autotrack are not checked. In the electronic-attack indications row, the rendered page shows the Other/Ambiguous option checked. The appearance checkboxes visible on the rendered page mark Balloon-shaped, Other Shape, Metallic, Opaque, and Reflective; Round, Square, Wings/Airframe, Moving Parts, Markings, Translucent, and Apparent Propulsion appear unchecked.

The free-text narrative says KINGPIN directed identification of an unknown contact, followed by a 1.4a redaction. It states that radar lock and target-pod video were obtained, but the aircraft could not get closer than 16.9NM for better identification. It says the target pod showed 2 IR SIGNIFICANT CONTACTS, that one range fouler was circling around the other, and that they were gone in 1/30TH OF A SECOND. The rendered page reads: TALLY ACHIEVED WAS 2X RED BLINKING STROBES AND NOISE JAMMING WAS RECIEVED. NOISE JAMMING WAS INDICATED BY TWO CHEVRONS. A final line gives first detection at B/E ZIM 248/17 followed by another 1.4a redaction.

There are no object photographs, maps, radar plots, target-pod stills, or video frames visible in this PDF page. The source is a text/form record that references sensor/video material; it is not itself the underlying radar return, target-pod video, or display-tape evidence.

Source custody and provenance

The page is tied to official CSV row 64 and the official file URL:

https://www.war.gov/medialink/ufo/release_1/dow-uap-d58-range-fouler-debrief-na-october-2020.pdf

A browser-like byte-range request to the official URL returned 206 with Content-Range: bytes 0-0/301419, while a direct HEAD request returned 403. The verified Open Sky release-file endpoint is:

/api/explore/war-gov/release-file/war-gov-dow-uap-d58-range-fouler-debrief-na-october-2020-9a3f23d9

The scan has visible redaction boxes marked 1.4a in the narrative and (b)(6) redactions in the administrative contact/link area. The footer reads as a USCENTCOM MDR release to AARO, dated 03/27/26, page 000001. The rendered footer appears to say MDR 26-0038 to MDR 26-0046, while OCR can surface a slightly different ending number; that should be checked against the rendered page if the MDR range matters.

Graph context

The graph has an exact D58 asset document and a separate official release-record document for CSV row 64. The semantic layer currently preserves 39 extracted claims, 20 entity mentions, and 3 sensor-event records. Those records are useful navigation, not adjudication.

The three sensor-event cues come from: the form field Radar Equipped: Other, the narrative phrase about obtaining radar lock and target-pod video, and the phrase 2 IR SIGNIFICANT CONTACTS. This is stronger than a blank equipment prompt, because the narrative itself references radar lock, target-pod video, IR contacts, tally, and noise jamming. Still, the released page does not include the raw plots, target-pod frames, display tape, measurement trail, or operator logs needed to independently validate those sensor claims.

Related graph links to other Release 01 records should be treated as navigation only. The candidate crosslink count is not a case connection by itself; some shared-anchor snippets surfaced unrelated Syria/D55 material and should not be used as D58 corroboration without a human review pass.

Leads to check

  • Locate whether the referenced target-pod video, display tapes, or .wmv uploads were released under another row, withheld, or only referenced by this form.
  • Review the redacted 1.4a sections after UNKNOWN CONTACT and after B/E ZIM 248/17 if an authorized source version becomes available.
  • Resolve the OCR/rendered-page discrepancies: rendered text reads 1/30TH OF A SECOND and 2X RED BLINKING STROBES, while OCR can misread or normalize those lines.
  • Determine the intended units/context for 060/20, 26000, 16.9NM, B/E ZIM 248/17, and the noise jamming / two chevrons language.
  • Check whether balloon-shaped, metallic, opaque, reflective, red blinking strobes, and circling behavior point to an identifiable airborne object, training artifact, target, drone, balloon, aircraft-light pattern, sensor artifact, or electronic-warfare/tracking issue.
  • Correct or annotate the embedded PDF metadata mismatch that labels the file as DoW-UAP-D35 despite the D58 release identity.

Lead check notes

  • Blocked — target-pod video / display-tape trail: The current Release 01 record for row 64 and the D58 asset expose this PDF with no DVIDS/video pairing. The .wmv display-tape instruction appears as range-fouler boilerplate in multiple linked forms, so it is a source-discovery lead rather than a D58-specific released media file.
  • Blocked — redacted location and routing: The 1.4a blocks after UNKNOWN CONTACT and B/E ZIM 248/17 remain unavailable in the Open Sky release-file copy. An unredacted official source is still needed for exact location, bullseye/airspace context, and sensor geometry.
  • Checked — page-render OCR quality: The derived page render supports 1/30TH OF A SECOND, 2X RED BLINKING STROBES, and TWO CHEVRONS; stored OCR can misread the timing and strobe wording. The footer visually favors USCENTCOM MDR 26-0038 to MDR 26-0046, while OCR can surface a different ending number, so the MDR range remains a transcription-sensitive citation.
  • Partial — linked-corpus anchor search: Searches for ZIM 248/17, 2 IR SIGNIFICANT CONTACTS, NOISE JAMMING, and TWO CHEVRONS found those anchors confined to the D58 OCR in the current linked Release 01 corpus. Broader .wmv and display-tape wording appears in other range-fouler forms without resolving this event's missing media.
  • Needs external source — units and prosaic checks: The form preserves 060/20, 26000, 16.9NM, red strobes, circling behavior, radar lock, target-pod video, and noise-jamming/two-chevron language, but it does not expose the raw radar return, pod frames, aircraft logs, weather, traffic, astronomy, satellite, or EW context needed to identify the contacts.
  • Partial — D58/D35 metadata mismatch: The title, URL, row 64, visible page, size, and SHA-256 identify this as D58; the embedded PDF metadata says DoW-UAP-D35. That remains a release-metadata cleanup lead unless official manifest history or corrected metadata resolves it.

Limits

This draft is limited to the released one-page form, its OCR, the rendered page image, and the current graph context. It does not include the underlying target-pod video, radar data, display tapes, aircraft logs, KINGPIN communications, weather, airspace deconfliction, satellite/launch checks, or a full prosaic-correlation pass. The form is a source-level report, not a resolution of what the contacts were.

Deep investigation — graph + web reconnaissance

Source reread

The verified release-file copy remains a one-page PDF (301,419 bytes; SHA-256 c2bd370cdadc2f17649830713d55731aa22ceb76940fd64ae7ffc86fc0559261). PDF metadata still says Title: DoW-UAP-D35 / Subject: DoW-UAP-D35, while the visible page, D58 title, official D58 URL, row 64, content length, and hash identify this file as D58. Treat the D35 metadata as a packaging/provenance-cleanup issue, not a source reassignment.

The page render is stronger than the stored OCR for checkboxes. Visible source review supports Tally Achieved checked, Other/Ambiguous checked under EA indications, and the appearance boxes Balloon-shaped, Other Shape, Metallic, Opaque, and Reflective checked; AIM-9X self-track and ATFLIR autotrack are not checked. OCR can flatten checkbox marks into empty-square text, so checkbox claims should be pinned to the page render rather than to OCR alone.

The narrative source text remains the key evidence. It says KINGPIN directed identification of an unknown contact, then a redacted 1.4a section, followed by OBTAINED RADAR LOCK AND TARGET POD VIDEO but no closer than 16.9NM; it says the target pod showed 2 IR SIGNIFICANT CONTACTS, with one range fouler circling the other, then IN 1/30TH OF A SECOND, THEY WERE GONE. The render supports 2X RED BLINKING STROBES, misspelled RECIEVED, and NOISE JAMMING WAS INDICATED BY TWO CHEVRONS. The first-detection line remains B/E ZIM 248/17 followed by another 1.4a redaction.

Graph connections

The graph has an exact official-primary asset record for this PDF plus a separate WAR.GOV release-row record. The asset record is the stable anchor: exact official URL, content length 301419, SHA-256 above, one OCR page, 39 machine-extracted claims, 20 entity mentions, and 3 sensor-event records. Those semantic nodes are navigation and audit material, not findings.

The three sensor-event records are source-text cues: one from the Radar Equipped: Other / stable-trackfile form region, one from the narrative sentence about radar lock and target-pod video, and one from 2 IR SIGNIFICANT CONTACTS. This is stronger than a blank form-label hit because the narrative itself names radar lock, target-pod video, IR contacts, tally, and noise jamming; however, the public PDF still does not contain the raw radar data, target-pod frames, display tape, operator log, geometry, or signal trace needed to independently validate those sensor claims.

Graph provenance needs cleanup. The current row-64 release-record node has the D58 title and D58 pdf_image_url, but stale final_url/byte/hash fields from a D55 row state also appear; a neighboring D61 row record can carry the D58 final URL/body hash with a relationship marked non-current for this asset. Candidate crosslinks on the release-row side are likewise contaminated by stale Syria/D55 anchors. These are row-reconciliation leads, not D58 corroboration and not separate events.

External provenance and context checks

The canonical public source remains WAR.GOV/PURSUE Release 01: https://www.war.gov/medialink/ufo/release_1/dow-uap-d58-range-fouler-debrief-na-october-2020.pdf. Direct live requests to the WAR.GOV PDF, landing page, and CSV returned 403 Access Denied during this check, so the verified release-file copy and source manifest remain the custody anchors. Internet Archive availability for the exact PDF reported a 200 snapshot at 20260508200701; a ranged archived-PDF fetch returned %PDF-1.7, Content-Range: bytes 0-15/301419, and original last-modified metadata Thu, 07 May 2026 23:54:59 GMT.

DVIDS search for the D58 title returned no usable result body, and AARO/Defense.gov search probes returned 403 during this check. The release row has no DVIDS/video pairing fields populated. Corpus anchor searches for ZIM 248/17, 2 IR SIGNIFICANT CONTACTS, NOISE JAMMING, and CHEVRONS remain confined to this D58 OCR/page record in the current Release 01 source corpus.

The graph has no useful exact-date astronomy/weather/launch context for 2020-10-27, and the public source withholds location in the key 1.4a blocks. That is a blocker, not a clearance: weather, traffic, satellite/launch, and astronomy checks need the unredacted location, platform position, look direction, sensor settings, and time standard before they can be meaningful.

Prosaic checks and follow-up leads

The first prosaic lanes are ordinary aircraft/drone or training-target lights, balloon/reflective-object interpretations, electronic-warfare or display/symbology behavior tied to the reported two chevrons, sensor/target-pod geometry, compression/display artifacts, and platform motion. The source's own strongest obstacle is missing evidence: the form references radar lock, target-pod video, display tapes/.wmv handling, and a repository upload process, but none of that underlying media or telemetry is included in the released one-page PDF.

Follow-up priorities are therefore: locate any associated target-pod video or display-tape source packet; reconcile the D35 metadata and D55/D61 row-field drift; obtain lawful unredacted geometry if released; verify the 060/20, 26000, 16.9NM, and B/E ZIM 248/17 context; and only then run weather, traffic, satellite/launch, astronomy, EW, and sensor-geometry checks.

Audit note

This section adds graph-and-web reconnaissance only. It does not create a finding, hypothesis, or resolution. The public source supports a reported two-contact range-fouler incident with radar/target-pod/IR/noise-jamming language; it does not provide the raw sensor products or enough context to identify the contacts.

Sources