FBI Photo B11

Evidence media

• Official PDF: Open Sky release-file copy

The page render shows the released one-page PDF as public viewers receive it: a grainy monochrome still with black release/source redaction bars, a white reticle with numeric tick marks, and the visible lower-left timestamp 12/31/99 18:11:06.

The extracted raster is the real 1280 × 960 image object embedded in the PDF. It shows the same reticle/redaction layout and a tiny unresolved dark speck slightly right of the reticle's vertical axis and above the horizontal line; the release record says the displayed date is incorrect and supplies no public motion, range, altitude, platform, or scene-geometry data.

Investigation reading

FBI Photo B11 is a one-page Release 01 PDF containing a monochrome still image. 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, that the original 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 object. The current Release 01 record places the incident window in late 2025 and the incident location in the Western United States.

The source file was checked as the released PDF, not just from the graph text. The PDF is 582,514 bytes, one page, and contains a single embedded RGB image. The PDF has no useful selectable text layer; the available OCR only captures the visible timestamp, 12/31/99 18:11:06. The release description explicitly says the date in the image is incorrect because the system date/time was not set, so that visible timestamp should not be treated as the incident time.

What the file appears to contain

The rendered page shows a grainy, low-resolution, grayscale sensor-style frame. A central white reticle is visible with vertical and horizontal axes and tick marks. The horizontal scale has readable numbers on both sides of center. The lower-left corner shows the timestamp 12/31/99 18:11:06.

The background is low contrast and noisy. The lower portion looks like an indistinct dark terrain or ridgeline area, while the upper and central field is a relatively uniform gray. The official narrative description says the background appears to show an indistinct mountain range; the visual review is consistent with that cautious reading, but the frame does not provide enough detail to establish exact terrain or location.

A tiny isolated dark mark is visible slightly to the right of the reticle's vertical axis and above the horizontal reticle line, in the upper-right/center-right portion of the frame. In close inspection it appears as a very small dark speck or short dash against the gray background. It is separated from the surrounding redaction blocks and does not show clear attached structure, shadow, plume, wake, or resolved shape in this still. The page should therefore describe it neutrally as an unresolved dark feature visible in a single still frame, not as an identified object.

Several solid black rectangular redaction bars obscure parts of the image, including a large band across the top and additional blocks along the sides. These appear to cover symbology or other image content. The redactions are part of the released image context and should be kept separate from the original scene content.

Source custody and provenance

• Official source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b11.pdf
• Open Sky release-file route: war-gov-fbi-photo-b11-19d8e1d5
• SHA-256: ff3909ff0fa5f99ee6da291d9241b9cd57b24f2889fcead89d8ae37a753d6c1c
• File size: 582,514 bytes
• Container: one-page PDF; page size 640 x 480 points; embedded image 1280 x 960 pixels
• PDF metadata title/subject: B11 FBI Photo
• Current Release 01 row: 114
• Agency: FBI
• Incident date/location in current release record: Late 2025, Western United States

The PDF is the released public container for the still image. The release text says no mission report accompanied this image. The file therefore preserves source custody for one redacted still and the official manifest description, but it does not by itself provide a full event narrative, a sensor log, platform details, range, altitude, motion sequence, or environmental data.

Graph context

The graph currently has an exact document node for the B11 PDF asset and an exact release-record node for current row 114. It also preserves text chunks for the official description and the single-page OCR. The semantic extraction attached to this asset has 22 claim records, 14 entity mentions, 4 sensor-event records, and 0 table rows.

Those graph records are useful navigation, but they should be read narrowly. The sensor-event records are triggered by source phrases such as still image and military system; they are not four independent sensor tracks or a released raw sensor data package. The related-record neighborhood includes B11 itself, a nearby FBI Photo B14 record, and an FBI Photo A8 image record. Those links are photo-set or release-neighborhood context unless a later review proves a stronger case relationship.

A provenance cleanup lead remains in the semantic layer: one preserved description chunk associates B11 text with row 117, while the current exact release record and current release metadata place FBI Photo B11 at row 114; row 117 is FBI Photo B14. This should be reconciled as an indexing/custody issue before using row numbers for cross-page claims.

Leads to check

• Locate any unredacted or pre-redaction version if legally available, or confirm that the released PDF is the only public artifact.
• Determine whether a mission report, operator log, metadata export, or adjacent frame sequence exists, since the release says no accompanying mission report was provided.
• Verify the true incident time/date independently; the visible 12/31/99 timestamp is explicitly marked unreliable by the release description.
• Identify what symbology was redacted and whether any remaining reticle scale can support a non-sensitive measurement.
• Compare this image with the other FBI Western United States photo records in Release 01, especially B14 and A8, without assuming they show the same event.
• Run ordinary prosaic checks if more context becomes available: aircraft/balloon/bird/debris possibilities, terrain/line-of-sight, weather, illumination, sensor artifacts, compression artifacts, and frame-to-frame motion.
• Reconcile the row 114/117 semantic mismatch before building automated crosslinks from this page.

Lead check notes

• Blocked — less-redacted source frame: The Open Sky release-file copy is a single-page PDF with one embedded 1280 × 960 image and no embedded attachments. A less-redacted or pre-redaction source frame, if releasable, is not present in Release 01.
• Blocked — mission report and adjacent frames: The release description says no accompanying mission report was provided. The PDF exposes no video sequence, operator log, metadata export, adjacent frame sequence, or raw sensor package.
• Partial — date/time: The page render, extracted raster, and OCR all preserve the lower-left 12/31/99 18:11:06 display, but the release record says the system date/time was not set. The actual collection time remains missing outside the broad Late 2025 release field.
• Partial — redacted symbology and reticle meaning: The redaction bars, reticle, tick marks, and horizontal scale numbers are visible in the official image, but the public file does not explain the symbology, field of view, range, altitude, or whether the remaining scale can support any non-sensitive measurement.
• Partial — adjacent FBI-photo comparison: Current graph/wiki navigation links B11 with FBI Photo B14 and FBI Photo A8 as nearby photo-set context. That is useful for comparison, but it does not establish that the images are one sequence or one event without source-row and image-level review.
• Needs external source — ordinary image checks: Aircraft, balloon, bird, debris, terrain contrast, sensor blemish, compression/noise, weather, illumination, and line-of-sight checks require unredacted imagery, collection geometry, or another authoritative source before they can be responsibly narrowed.
• Partial — row-number cleanup: The exact release record and current release metadata identify B11 at row 114, while one semantic description chunk associates the same B11 text with row 117, which is FBI Photo B14. The title, official PDF URL, and SHA-256 identify this B11 file; the row conflict remains a custody/indexing cleanup lead.

Deep investigation — graph + web reconnaissance

Source reread

The deep reread confirms that B11 is source-backed as a still-image PDF, not as a complete mission packet. The official release description says the FBI supplied AARO with a still image derived from a U.S. military system in 2025, that the imagery was redacted before submission, that no accompanying mission report was provided, and that the operator could not positively identify the UAP. The PDF itself is one encrypted/copy-disabled page, 582,514 bytes, with SHA-256 ff3909ff0fa5f99ee6da291d9241b9cd57b24f2889fcead89d8ae37a753d6c1c. It contains one embedded RGB raster (1280 × 960) and no useful selectable text; OCR captures only the visible overlay timestamp 12/31/99 18:11:06, which the release description says is not the real collection date because the system clock was not set.

Visual review of the extracted raster supports only a cautious scene description: a noisy grayscale frame, central white reticle and numeric scale overlay, black redaction blocks, a visible timestamp overlay, a low-contrast darker lower background, and a tiny dark mark slightly right of center and above the horizontal reticle line. A second small speck-like mark is also visible lower/right of center. These marks are scene/raster observations, not identifications. The reticle, timestamp, and redaction bars are overlays or release handling artifacts and should not be treated as physical scene content.

Graph connections

Neo4j has two exact B11 identity records: the current Release 01 row 114 record and the exact PDF asset node at https://www.war.gov/medialink/ufo/release_1/fbi-photo-b11.pdf with the matching SHA-256 above. The asset has three text chunks: the official manifest-style description, a preserved manifest-description chunk with the row-number tension, and the OCR timestamp chunk. Semantic extraction is present but remains machine-review material: 22 machine claim records, 14 entity mentions, and 4 sensor-event records. The sensor-event records are triggered by phrases such as still image and military system; they are not four independent tracks, not radar confirmation, and not a raw sensor package.

The graph neighborhood is useful for custody cleanup but weak for case-level corroboration. It links B11 to the row 114 release record, a B14 row 117 record, an A8 image record, and a secondary GitHub/UFO-USA conversion of B11. Those are photo-set, release-neighborhood, and derivative-conversion leads. The exact PDF URL and hash identify the B11 source; the B14/A8/row 117 connections should not be used as proof of one event, one sequence, or corroboration unless a future source packet provides image-level continuity.

External provenance and web reconnaissance

Direct official WAR.GOV fetches for the B11 PDF, the Release 01 landing page, and the public CSV returned 403 Access Denied during this check. That does not invalidate the already verified official-primary asset in Open Sky, but it means the current public page should continue to cite the exact official URL, hash, file size, and Open Sky release-file endpoint rather than implying a fresh live download succeeded. An Internet Archive availability probe for the exact PDF was rate-limited (429), so Wayback confirmation remains a follow-up lead, not a provenance source for this page.

The graph also points at a secondary UFO-USA GitHub conversion for B11. That conversion can help find OCR/markdown drift, but it is derivative and should not override the official PDF, release record, or verified image render. No official mission report, operator log, metadata export, adjacent frame sequence, or raw video/sensor package was found in the source material checked here.

Prosaic checks and open questions

The strongest ordinary-check lane is image provenance and image quality: sensor noise, compression, redaction-edge artifacts, tiny scene specks, reticle/symbology masking, possible terrain contrast, and single-frame ambiguity. Aircraft, balloon, bird, debris, atmospheric/illumination, weather, and line-of-sight checks remain blocked because the public record gives only Late 2025, Western United States, and an unspecified military system—not the true collection time, coordinates, platform, sensor mode, range, altitude, look direction, frame sequence, or weather.

Until those missing fields or a less-redacted source package are released, B11 should remain a single-frame unresolved image record with official custody, not an analytical finding. The next useful checks are exact WAR.GOV/Wayback availability for the PDF and CSV row, any AARO/FBI release-note counterpart that identifies the underlying source package, and row/hash reconciliation for the B11/B14/A8 neighborhood.

Audit note

No graph writes were made for this review. The section above separates source facts, visual observations, machine-extracted graph leads, secondary/derivative context, prosaic blockers, and unresolved questions; it does not create a Finding, Hypothesis, or ResolutionDecision.

Limits

This draft does not identify the dark feature and does not make a finding. The public file is a single redacted still in a PDF container. There is no released video sequence, no range or altitude readout, no platform identity, no confirmed event time from the image timestamp, no mission report, and no raw sensor data. The feature is only a few pixels across in a noisy monochrome frame, so shape, distance, speed, and behavior cannot be determined from this source alone.

The visual description above separates what is visible in the still from the official narrative description and from graph-extracted claim categories. Any stronger interpretation requires additional source material and human review.

Sources

• WAR.GOV / PURSUE Release 01 official PDF: FBI Photo B11
• Open Sky release-file endpoint for the same PDF: war-gov-fbi-photo-b11-19d8e1d5
• Current Release 01 record metadata: row 114, FBI, late 2025, Western United States
• Verified file hash: ff3909ff0fa5f99ee6da291d9241b9cd57b24f2889fcead89d8ae37a753d6c1c
• Source-file review: one-page PDF render, embedded-image inspection, and OCR timestamp check