FBI Photo B9

Evidence media

Open Sky release-file PDF — official one-page PDF copy verified against the SHA-256 listed below.

Derived official PDF page render for FBI Photo B9

The derived PDF page render shows the full released still-image sheet, including the central reticle, black redaction blocks, lower-left displayed timestamp 12/31/99 18:10:26, and the small unresolved dark mark just below-left of the reticle center. The release description says the displayed date/time is incorrect because the system date/time was not set.

Extracted embedded image object from FBI Photo B9 PDF

The extracted embedded image object shows the same grayscale reticle view without adding interpretive overlay. It is included to separate the image content from the PDF container; the public source does not identify the dark mark or establish a cause.

Investigation reading

This Release 01 item is a one-page FBI PDF containing a single monochrome still image. The release description says the image was derived from a U.S. military system in 2025 and submitted by the Federal Bureau of Investigation to AARO. It also says the imagery was altered with redactions before submission, that no accompanying mission report was provided, and that the operator reported being unable to positively identify the UAP.

The verified Open Sky release-file copy is 588,086 bytes and matches SHA-256 e61a49212bb82cfc9a6e7627a2291c9159bbbb2272fb995e45411a48e44eb0b1. The PDF has one page and one embedded 1280 × 960 RGB image. The available OCR for the page contains only the visible timestamp text, 12/31/99 18:10:26; there is no body narrative, transcript, table, mission report, or telemetry text inside the PDF itself.

The release description warns that the displayed image date is incorrect because the system date/time was not set. For this draft, the 12/31/99 string is treated only as text visible in the released frame, not as the incident date. The release-record incident fields give the broader window and location as Late 2025 and Western United States.

What the file appears to contain

The visible frame is grayscale, low-contrast, and grainy. A white crosshair or measurement reticle is centered in the image, with horizontal and vertical tick marks. The horizontal scale shows numeric labels stepping outward from the center, including 15, 10, and 5 on the left and 5, 10, and 15 on the right. The background is mostly mottled gray with faint banding and darker texture near the lower portion; it does not resolve identifiable buildings, vehicles, people, roads, or a clear horizon line.

Several black rectangular blocks obscure portions of the frame. One long black bar covers much of the upper image area, and additional black rectangles appear along the left, right, and lower portions. These should be read as release/source redactions or obscurations, not as natural scene content.

A small dark unresolved feature is visible slightly left of the vertical reticle line and slightly below the horizontal reticle line. In the full embedded image and an enlarged crop, it appears as a compact, slightly irregular dark spot or pixel cluster against the noisy gray background. It has no resolved structure, no visible trail, no clear shadow, no visible appendages, and no public scale, distance, altitude, motion, or range information in this file. The release narrative describes a small dark circular object just below-left of reticle center; the visual read-through supports the limited point that a compact dark mark is present there, but this page does not identify the mark or assign a cause.

Source custody and provenance

Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b9.pdf
Open Sky release-file route: war-gov-fbi-photo-b9-fd8286ff
Agency: FBI
Release: WAR.GOV/PURSUE Release 01
Source/container type: PDF containing a still image
Verified Open Sky release-file size: 588086 bytes
Verified Open Sky release-file SHA-256: e61a49212bb82cfc9a6e7627a2291c9159bbbb2272fb995e45411a48e44eb0b1
PDF page count: 1
Embedded image dimensions: 1280 x 960
OCR coverage: one page; OCR text contains only 12/31/99 18:10:26
Release-record incident fields: Late 2025, Western United States
Release-record redaction flag: TRUE

One custody note needs follow-up. The verified Open Sky asset and release-record context list CSV row 135, while another manifest-derived text record for the same title and official URL surfaces row 138. The title, URL, agency, visible timestamp, and Open Sky release-file hash identify this B9 PDF; the row-number difference should be treated as a release-indexing cleanup lead rather than a separate image-content conflict.

A current browser-style byte-range request to the official URL also served a smaller one-page PDF variant of the same visible image content: 125,010 bytes with SHA-256 86017c6972e7e6e110d86be0667a324d28b8d6c3e37d9fdb8acedddf3fd9dd02. The visible timestamp, reticle layout, redaction pattern, and below-left dark feature match the Open Sky release-file copy. This looks like an official-server PDF version/compression issue to reconcile before using byte identity across mirrors.

Graph context

The graph currently models this item as an official primary Document asset and a separate official release-record Document. The release-record node carries row-level context such as FBI, Late 2025, Western United States, and redaction marked true. The PDF asset node carries the canonical file URL, PDF asset type, and Open Sky release-file SHA-256.

Machine extraction attaches 22 claim records, 14 entity mentions, and 4 sensor/platform event records to this item, with no table rows. The useful source-backed claims are narrow: this is a still image, the source language mentions a U.S. military system, the operator reportedly could not positively identify the UAP, and the release names FBI and AARO. The sensor-event records come from phrases such as still image and military system; they should not be read as independent radar, telemetry, motion-track, or multi-sensor evidence.

The current context reports no candidate crosslinks for this item. Related graph navigation points include adjacent Release 01 image records such as FBI Photo B6 and a NASA Apollo debriefing record. Those links are useful only as navigation and comparison leads unless a reviewer confirms a source-level relationship.

Leads to check

Compare B9 against adjacent FBI B-series photo pages to determine whether the reticle layout, redaction pattern, and timestamp sequence belong to one sensor series or separate submissions.
Locate any original unredacted or less-redacted frame, if one exists and can be lawfully released.
Identify the collection platform, sensor mode, field of view, reticle meaning, range, altitude, and whether any obscured telemetry is hidden behind the black bars.
Reconcile the broad Late 2025 release-record window with the incorrect visible 12/31/99 18:10:26 timestamp.
Test ordinary image explanations before escalation: sensor blemish, compression/noise, dust or debris in the optics, distant aircraft/bird/balloon, terrain contrast, or other optical effects. The released still alone does not provide enough information to narrow these responsibly.
Reconcile the CSV row-number discrepancy and the official-server smaller-PDF variant with the Open Sky release-file copy.

Lead check notes

Partial — Adjacent B-series comparison: B9 shares the same broad still-image pattern as nearby FBI B-series pages — grayscale reticle view, black redaction blocks, and an unreliable 12/31/99 displayed timestamp — but confirming whether those pages are one sensor series still requires source-level comparison of adjacent frames, collection logs, or the original submission package.
Blocked — Mission/source package: the release description says no accompanying mission report was provided, and the public PDF does not expose platform identity, sensor mode, range, altitude, field of view, collection geometry, adjacent frames, or a less-redacted original image.
Partial — Mark persistence: both the derived PDF page render and the extracted embedded image object show the compact unresolved dark mark below-left of the reticle center. The one-page release file does not provide a higher-quality source frame or time sequence to test whether the mark persists across frames.
Checked — Timestamp caveat: the visible 12/31/99 18:10:26 string is carried as displayed-image text only. The release description says the system date/time was not set, so this page should not use it as the incident time.
Partial — Release-file/versioning cleanup: the verified Open Sky release-file PDF remains the 588,086-byte file with SHA-256 e61a49212bb82cfc9a6e7627a2291c9159bbbb2272fb995e45411a48e44eb0b1. A current browser-style official-server fetch returned a smaller 125,010-byte PDF with SHA-256 86017c6972e7e6e110d86be0667a324d28b8d6c3e37d9fdb8acedddf3fd9dd02; visual review showed the same timestamp, reticle/redaction layout, and below-left mark, so this remains a custody/versioning lead rather than an image-content difference.

Limits

This page is an investigation draft for review, not a finding. The file is a single still frame, not a mission report or video sequence. It provides no public motion track, platform identity, range, altitude, weather, collection geometry, operator transcript, original unredacted image, or independent corroborating source. Redactions obscure portions of the frame, and the only OCR text recovered from the PDF page is the unreliable displayed timestamp.

The release narrative is useful for source custody and visual orientation, but it explicitly cautions that its description should not be treated as an analytical judgment or factual determination about the event's nature or significance. The dark mark near the reticle therefore remains an unresolved visual feature in a redacted still image.

Deep investigation — graph + web reconnaissance

Source reread

The source remains a one-page encrypted/copy-restricted PDF with title/subject B9 FBI Photo, file size 588086 bytes, SHA-256 e61a49212bb82cfc9a6e7627a2291c9159bbbb2272fb995e45411a48e44eb0b1, and one embedded 1280 × 960 RGB image. pdfdetach reports no embedded attachments, and the OCR text is limited to the displayed timestamp 12/31/99 18:10:26.
Visual review of both the derived PDF page render and the extracted embedded raster confirms the same basic scene: a grayscale noisy frame, central reticle with 15 / 10 / 5 scale marks, multiple black redaction blocks, and a compact dark unresolved mark slightly left of the vertical reticle line and slightly below the horizontal reticle line. A still frame alone does not establish scale, range, altitude, motion, platform, sensor mode, or object identity.
The release description is useful source context, but it is not an analytical finding. It states that FBI submitted a still image derived from a U.S. military system to AARO, that the image was redacted before submission, that no mission report was provided, that the operator could not positively identify the UAP, and that the displayed date/time is incorrect because the system date/time was not set.

Graph connections and provenance audit

Read-only graph review finds a stable exact asset node for the PDF URL/hash plus a separate Release 01 row-record node for FBI Photo B9. The semantic layer attached to the asset contains 22 machine-extracted claims, 14 entity mentions, and 4 sensor/platform event records; these remain machine_extracted_needs_human_review / not_a_finding and are only navigation cues until checked against the source.
The graph's source-backed material is narrow: still image, military system, FBI, AARO, Late 2025, Western United States, and the operator's inability to positively identify the UAP. The STILL IMAGE and military system SensorEvent records are not radar, telemetry, speed, maneuver, or multi-sensor corroboration.
Provenance cleanup remains needed. The exact PDF asset points to current row 135, while a manifest-description chunk and a neighboring current row 138 relationship also surface the same B9 PDF URL. The row-record neighborhood also shows shifted/stale final_url values across adjacent B-series/NASA rows. The safe identity anchor for this page is therefore the exact official URL plus SHA-256 hash, not row number alone.
A derived UFO-USA GitHub Markdown conversion is linked in the graph as a secondary conversion of the official asset. It is a discovery/provenance lead only; the official WAR.GOV/PURSUE PDF and Open Sky release-file copy remain the source of record.

External provenance and web checks

Direct WAR.GOV landing-page, CSV, and PDF requests during this check returned Akamai 403 responses, so the live official server could not be used as the only custody check. The verified Open Sky release-file copy still matches the archived official-primary PDF byte-for-byte.
Internet Archive CDX lists exact-URL WAR.GOV captures for fbi-photo-b9.pdf, including 20260508142920, 20260508180815, and 20260508200714 application/pdf captures near the 588 kB original size, plus a later 20260514084111 capture near 124 kB. Fetching the 20260508142920 archived copy returned 588086 bytes and the same SHA-256 as the Open Sky release-file copy, strengthening custody for the larger official-primary version.
The later smaller PDF capture remains a versioning/compression lead, not a scene-content change. Without fetching and comparing that exact later snapshot in the same evidentiary chain, it should not replace the verified 588,086-byte source copy.

Prosaic checks before escalation

Meaningful astronomy, weather, launch, satellite, and aircraft/balloon correlation is blocked because the public record gives only Late 2025, Western United States, and an unreliable displayed timestamp. Those checks need the actual collection time, platform position, look angle, field of view, sensor mode, and less-redacted telemetry.
Ordinary image explanations remain open and should be tested before escalation: sensor blemish or hot/cold pixel behavior, display/compression artifact, dust/debris or optical contamination, a distant bird/aircraft/balloon, terrain/background contrast, or a redaction/processing artifact. The released still does not contain enough context to rank those explanations responsibly.
Adjacent B-series pages remain useful for sequence comparison, especially reticle layout, redaction placement, timestamp progression, and whether similar compact marks persist across frames. That comparison requires source-level frame/package evidence rather than title adjacency alone.

Follow-up leads and limits

Highest-value follow-ups: original unredacted or less-redacted frame, adjacent frames or video, the missing mission/source package, platform and sensor identity, reticle/FOV documentation, collection geometry, and official reconciliation of the row-number/final-URL drift.
This deep check did not create or alter graph records and does not assert a finding, hypothesis, or resolution decision. The public status remains an unresolved redacted still-image record with a compact dark visual feature near the reticle and insufficient context for identification.

Sources

WAR.GOV/PURSUE Release 01 PDF: FBI Photo B9
WAR.GOV/PURSUE Release 01 CSV/manifest description for FBI Photo B9
Internet Archive CDX / archived exact-URL capture for https://www.war.gov/medialink/ufo/release_1/fbi-photo-b9.pdf
Open Sky release-file record: /api/explore/war-gov/release-file/war-gov-fbi-photo-b9-fd8286ff
Open Sky Release 01 graph context for official:doc:war-pursue-uap-release:asset:fbi-photo-b9-pdf:fd8286ffc6fb