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

FBI Photo B5

Open Sky release file copy of the official PDF

Release 01#war-gov#pursue#release-01#official-source#evidence#fbi#still-image#pdf

FBI Photo B5

Evidence media

Derived official PDF page render: FBI Photo B5

Derived page render from the official one-page PDF. The render shows a grayscale, low-contrast still with a central white reticle, heavy black redactions, and the visible lower-left timestamp 12/31/99 18:12:20; the release description says the image date is incorrect because the system date/time had not been set. No clearly distinct object is visible near the central reticle in the released image.

Extracted embedded raster from FBI Photo B5 PDF

Extracted main image object from the same PDF. It preserves the reticle and redaction layout at 1280 x 960; it is source-media context, not a separate unredacted frame.

Investigation reading

This Release 01 item is a one-page FBI still-image PDF. The release record says the FBI submitted a report to AARO consisting of a still image derived from a U.S. military system in 2025; it also says the original imagery was altered with redactions before submission, no accompanying mission report was provided, and the operator reported being unable to positively identify the object. The current release record ties this item to CSV row 131, incident window Late 2025, and incident location Western United States.

The rendered PDF page contains only the image frame. There is no visible caption, narrative paragraph, map, mission-report page, sensor log, or explanatory text outside the image itself. Frontier OCR for the page contains only the visible timestamp text: 12/31/99 18:12:20.

What the file appears to contain

The visible source is a grainy monochrome frame with a white central reticle/crosshair. The horizontal and vertical reticle lines have short tick marks, and the horizontal scale includes labels such as 15, 10, and 5 on both sides of center. A black band spans the top of the frame. Several solid black rectangular blocks cover parts of the upper-left, upper-right, lower-left, and lower-right portions of the image; these should be treated as release/source redactions or overlays, not as scene content.

The lower-left timestamp reads 12/31/99 18:12:20. The release description says the system date/time was not set, so this visible timestamp should not be treated as the actual incident date. The frame background is noisy and low contrast. The lower portion has darker, indistinct bands or terrain-like shapes, consistent with the release description's note that the background may show an indistinct formation. Around the center reticle, no clearly distinct object is visible in the released image. A tiny bright speck appears lower-left of center, but it is too small and context-poor to identify from this still alone.

This draft does not identify the feature, infer motion, infer range or altitude, or treat the still as proof of a resolved object. The useful observation is narrower: Release 01 provides a redacted still image with a reticle and a bad visible timestamp, while the accompanying release text reports that an operator could not positively identify the object.

Source custody and provenance

  • Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b5.pdf
  • Open Sky release-file copy: war-gov-fbi-photo-b5-36bcfe2c
  • Agency: FBI
  • Release: WAR.GOV / PURSUE Release 01
  • Current release CSV row: 131
  • Current release record incident window/location: Late 2025, Western United States
  • File type and size reviewed: one-page PDF, 580,719 bytes
  • SHA-256: 032b86473fefc250def77d3904c381dad010e34390d58de54fd560054127936c
  • PDF structure observed: encrypted/copy-disabled PDF, one page, one embedded RGB image at 1280 x 960
  • OCR coverage: one OCR page with only 12/31/99 18:12:20

One provenance cleanup item is visible in the graph context: a derived manifest-description chunk can surface Related CSV rows: 134, while the verified release metadata and release record for this PDF use row 131. In the same release sequence, row 134 belongs to FBI Photo B8, not this B5 PDF. That should be treated as indexing/custody cleanup, not as a content change to the B5 image.

Graph context

The graph has an official release-record document for FBI Photo B5 and a separate PDF-asset document for the canonical file URL. The current semantic extraction attached to this asset reports 22 extracted claims, 14 entity mentions, 4 sensor/platform events, and 0 table rows. The claim categories are mostly narrow provenance and release-text facts: FBI/AARO references, the still-image source type, the military-system wording, the Late 2025 / Western United States release-record fields, the operator's inability to positively identify the object, and the release caveat that the description is not an analytical determination.

The four sensor/platform events should be read as navigation cues from source language such as still image and military system. They are not independent radar returns, telemetry, multi-sensor tracks, or a released mission-report sensor table. The graph also surfaces related FBI Photo B-series records, including B8 and B24, which are useful comparison targets but do not by themselves establish a shared event, sequence, or identification.

No candidate crosslinks are attached for this item in the current context.

Leads to check

  • Confirm the actual collection date/time from source metadata outside the visible 12/31/99 18:12:20 timestamp, since the release states the system clock was not set.
  • Locate any unavailable mission report, operator notes, platform/sensor metadata, field-of-view/range information, or unredacted frame that would explain the reticle and redacted areas.
  • Compare the official thumbnail, the extracted image raster, and adjacent FBI Photo B-series items for shared cropping, redaction style, timestamp sequence, or repeated background patterns.
  • Run ordinary image-quality checks before escalation: sensor blemish, dust/debris, compression/noise, terrain contrast, distant aircraft/bird/balloon, or other optical artifacts.
  • Clean up the row-number mismatch between the verified B5 row 131 and the derived manifest text that can incorrectly surface row 134.

Lead check notes

  • Checked — The Open Sky release-file copy matches current Release 01 release metadata: one-page PDF, 580,719 bytes, SHA-256 032b86473fefc250def77d3904c381dad010e34390d58de54fd560054127936c, and official row 131.
  • Checked — PDF inspection reports one embedded RGB image at 1280 x 960 and zero embedded file attachments. The derived page render and extracted main raster now appear in the evidence media section.
  • Partial — The page render, extracted raster, and OCR preserve the visible timestamp 12/31/99 18:12:20, but the release description says the image date is incorrect because the system date/time was not set. The actual collection date/time remains missing from the released file.
  • Partial — Visual review of the extracted raster supports the existing caution: no clearly distinct object is visible near the central reticle in this released B5 image, while the current graph context preserves related B-series records only as comparison targets.
  • Partial — Current release metadata and exact release-record context identify row 131; a derived manifest-description chunk can surface row 134, which belongs to FBI Photo B8. That remains a provenance-cleanup issue before row sequence is used for B-series comparisons.
  • Blocked — The current linked release materials do not expose a less-redacted frame, adjacent frames/video, mission report, operator notes, source logs, platform/sensor geometry, range, altitude, field of view, or environmental context.
  • Needs external source — Image-noise, compression, display-overlay, redaction-artifact, sensor-blemish, aircraft, bird, balloon, terrain, weather, illumination, range, line-of-sight, and motion checks require unredacted imagery, adjacent frames, exact time/location, collection geometry, or environmental records.

Limits

This page is an investigation draft, not a finding. The released file is only a redacted still-image PDF. It does not provide the original video, mission report, platform identity, sensor model, range, altitude, speed, weather, collection geometry, or contemporaneous operator log. The image is low contrast and noisy, and redactions obscure portions of the frame. From the released still alone, no distinct object is clearly visible at the central reticle, and no identity or prosaic resolution should be asserted.

The visible timestamp is not reliable as an incident date because the release text says the system date/time was not set. The release-record Late 2025 / Western United States fields are stronger custody metadata than the embedded 12/31/99 timestamp, but they still do not provide a precise collection time or location.

Deep investigation — graph + web reconnaissance

Source reread

The official-primary source reread still supports a narrow reading: this is a one-page still-image PDF, not a mission report, video packet, radar product, or resolved case file. The release-file copy verifies as 580,719 bytes with SHA-256 032b86473fefc250def77d3904c381dad010e34390d58de54fd560054127936c. PDF metadata identifies the title/subject as FBI Photo B5; the file is encrypted/copy-disabled, has one 640 x 480 pt page, and contains one RGB embedded image at 1280 x 960.

The source text remains minimal. Frontier OCR for the page contains only 12/31/99 18:12:20. Visual review of the page render and the extracted embedded raster shows a grainy grayscale frame with a central white reticle, horizontal 15 / 10 / 5 scale marks, heavy black redactions or overlays, and low-contrast background texture. The lower-left timestamp is best read as 12/31/99 18:12:20, but the release record says the system date/time was not set, so it should not be treated as the incident date. No clearly distinct object is visible around the central reticle in the released B5 still.

Graph connections

Read-only graph checks found the expected official PDF asset and the current Release 01 row record. The stable identifiers for this item are the B5 canonical PDF URL, row 131, 580,719-byte file size, and the SHA-256 above. The semantic layer currently has 22 machine-extracted claims, 14 entity mentions, 4 sensor/platform events, and no candidate crosslinks for the B5 asset. Those graph claims mostly duplicate the release-manifest facts: FBI/AARO, still image, U.S. military-system source wording, Late 2025, Western United States, redactions, and the operator's reported inability to positively identify the UAP.

The SensorEvent nodes are machine-extracted navigation cues from phrases such as still image and military system; they are not independent radar, telemetry, EO/IR track, or multi-sensor corroboration. The graph also preserves a custody/indexing issue: B5 is current row 131, while stale manifest-description or related-record fields can point at nearby FBI Photo B-series rows such as B8 or carry older file-pointer drift. Use the exact B5 URL/hash/row before doing any B-series comparison.

External provenance and context

During this check, live WAR.GOV probes for the B5 PDF, the Release 01 CSV, and the B5 thumbnail returned Akamai 403 responses, and the Internet Archive availability probe returned 429 Too Many Requests. That is an access/provenance limitation, not a content contradiction: the cached official-primary release file matches the inventory and graph by URL, byte size, and hash. The release record has no DVIDS video ID or video/PDF pairing beyond this still-image PDF.

No stronger external official source was found in the available release context that supplies the missing mission report, platform identity, sensor model, exact collection time, exact location, adjacent frames, or raw video. Secondary mirrors or B-series adjacency should therefore be treated only as discovery/provenance leads until pinned to an official record.

Prosaic checks before escalation

The public file does not expose enough geometry for astronomy, weather, launch, satellite, aircraft, or balloon correlation. The only date-like value visible in the image is explicitly unreliable, and the release location is only Western United States. With no exact time, viewing direction, sensor field of view, platform track, range, altitude, or adjacent-frame motion, those checks remain blocked.

The first ordinary checks are image/source-quality checks: redaction and display-overlay effects, compression/noise, sensor blemish or dust, low-contrast terrain or illumination, and whether a tiny speck is scene content or artifact. The released B5 still alone does not support object identity, motion, speed, range, altitude, or cause.

Follow-up leads and limits

  • Obtain the actual collection date/time outside the bad 12/31/99 18:12:20 overlay.
  • Locate any mission report, operator note, platform/sensor metadata, reticle scale, field-of-view, range, altitude, or unredacted/less-redacted frame sequence.
  • Reconcile B5 row 131 against stale graph/file-pointer drift before using neighboring FBI Photo B-series pages as comparison evidence.
  • Keep the graph semantic material marked as machine-extracted and not a finding unless individual claims are checked against the source image or official release text.

Audit note

This deep check adds source, graph, and web-provenance context only. It does not create a finding, hypothesis, or resolution decision. The public posture remains: official Release 01 contains a redacted still image and source/manifest testimony that the operator could not positively identify the UAP, but the released B5 image does not show a clearly distinct object near the central reticle and lacks the context needed for prosaic correlation or escalation.

Sources