FBI Photo B16

Evidence media

• Official PDF: Open Sky release-file copy

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

The extracted raster is the real 1280 × 960 image object embedded in the PDF. It shows the same reticle/redaction layout and a small dark unresolved feature slightly right of center; the release record says the displayed timestamp is incorrect and supplies no public motion, range, altitude, platform, or scene-geometry data.

Investigation reading

FBI Photo B16 is a one-page Release 01 PDF containing a redacted still image. The Release 01 description identifies the submitting agency as FBI and says the item was a still image derived from a U.S. military system in 2025, submitted to AARO after redactions had already been applied. The same description says no accompanying mission report was provided and that the operator reported being unable to positively identify the UAP.

The source file was reviewed as a PDF container and as a rendered/extracted image, not only as graph text. The Open Sky release-file copy verifies as 433,987 bytes with SHA-256 76bc12588922fca7ef9019f1c809a07e3a159cb1d789013f6acbfcd893935b6a. PDF inspection shows one encrypted/copy-restricted page, page size 640 x 480 points, metadata title/subject B16 FBI Photo, and one embedded RGB image measuring 1280 x 960 pixels. The selectable text layer is effectively empty. The OCR pass captures only the visible lower-left overlay timestamp: 12/31/99 18:20:41.

That displayed timestamp should not be treated as the incident time. The official release description says the date in the image is incorrect because the system date/time was not set. The release-record context available here is broader: Late 2025 and Western United States. The public image does not expose the exact collection date, platform, sensor model, range, altitude, field of view, location, or mission context.

What the file appears to contain

The rendered page and extracted raster show a grainy monochrome sensor-style frame. A bright white reticle is centered in the scene, with a vertical line and a horizontal line crossing near the middle, small tick marks, and the number 3 visible on both sides of the horizontal reticle. Multiple hard-edged black redaction blocks cover the top band and several left/right display regions. These redaction blocks are separate from the original scene content and may obscure telemetry, labels, or other source information.

The lower-left overlay reads 12/31/99 18:20:41. The unredacted background is mostly noisy gray texture with no clear horizon, terrain, building, vehicle, person, aircraft, star field, cloud form, or landmark. Slightly right of the vertical reticle line and above the horizontal reticle line, two dark features are visible close together. The larger feature is an irregular dark blob or cluster just right of center; a smaller dark spot sits slightly above and to its right. Both are unresolved and blurred against the noisy background. The official narrative description calls them two dark, irregular-shaped objects visible just right of center in the upper-right quadrant, but the released still alone does not provide enough detail to infer true shape, size, distance, motion, or identity.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b16.pdf
• Open released file: war-gov-fbi-photo-b16-3b36f3dc
• Release 01 row currently associated with this page: 119
• Agency: FBI
• Source/container kind: one-page PDF still-image container
• Verified file size: 433,987 bytes
• Verified SHA-256: 76bc12588922fca7ef9019f1c809a07e3a159cb1d789013f6acbfcd893935b6a
• Embedded image: one RGB image, 1280 x 960 pixels
• Release-record incident context: Late 2025, Western United States

This file preserves custody for one public, redacted still frame and the official release description. It does not include the underlying mission report, raw sensor package, adjacent frames, operator log, platform identification, collection geometry, environmental context, or unredacted display fields. The official URL remains cited; the Open Sky Release 01 file copy and verified hash identify the public-file copy reviewed for this draft.

Graph context

The graph has exact source records for the B16 PDF asset and a Release 01 record for the same title/URL. The semantic layer currently carries 22 extracted claim records, 14 entity mentions, 4 sensor-event records, and no table rows for this asset. The strongest source-backed points are narrow: this is a still image from a U.S. military system; it was redacted before submission to AARO; no accompanying mission report was provided; the operator reportedly could not positively identify the UAP; and the visible image clock is unreliable.

The sensor-event records are navigation cues triggered by phrases such as still image and military system. They are not four independent sensor tracks and do not represent released radar, telemetry, range, altitude, or multi-sensor corroboration. Related graph records point to nearby FBI B-series photo items such as B13 and B19, but those links are release-neighborhood context unless URL, row, hash, and image-level review establish a stronger relationship.

One linked manifest-description entry surfaces row 122 for B16, while another release-record index associates B16 with row 119. Treat this as a release-index provenance cleanup lead, not a content conclusion about the image.

Leads to check

• Locate any less-redacted source frame, original image export, adjacent frames, video sequence, operator log, mission report, or AARO submission metadata.
• Verify the actual collection date/time outside the invalid 12/31/99 display clock.
• Identify the platform, sensor type, reticle meaning, field of view, range scale, altitude context, and whether redactions hide telemetry or classification markings.
• Compare B16 with official thumbnails and nearby FBI B-series photo records only after checking each record's row number, URL, hash, and visible frame content item by item.
• Run ordinary image-quality and prosaic checks before escalation: sensor blemish, dust/debris, compression or display artifact, redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight.
• Reconcile the row 119 / row 122 metadata mismatch before using row numbers or related-record links for cross-page analysis.

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 original, adjacent frames, source video, operator log, mission report, or AARO submission package is not present in Release 01.
• Partial — date/time: The rendered page, extracted raster, and OCR all preserve the lower-left 12/31/99 18:20:41 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 — platform/sensor metadata: The source language says only that the still image came from a U.S. military system. The reticle and redactions are visible, but the public PDF does not expose field of view, range, altitude, platform identity, original video, mission report, or sensor logs.
• Partial — adjacent FBI-photo comparison: Current release/graph navigation links B16 with nearby FBI B-series items such as B13 and B19. That is useful context 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: Dust/debris, sensor blemish, compression/noise, distant aircraft/bird/balloon, terrain contrast, illumination, weather, and line-of-sight checks need unredacted imagery or collection geometry before they can be responsibly narrowed.
• Partial — row-number cleanup: The current release record places this B16 page at row 119, while one linked manifest-description entry surfaces row 122 for the same title/URL family. The title, URL, and SHA-256 identify this B16 PDF, so the row difference remains an indexing cleanup lead rather than an image-content conflict.

Limits

This page does not identify the two dark features and does not assert a finding. The public file is a single redacted still-image PDF, not a full event package. There is no released motion sequence, no platform identity, no confirmed incident timestamp from the visible clock, no raw sensor data, no range or altitude measurement, no weather or astronomy context, and no independent corroborating source in the file. The visible marks are documented only as unresolved features in a noisy, redacted image pending review and additional source material.

Deep investigation — graph + web reconnaissance

Source reread

The stable source identity for this page is the official PDF URL https://www.war.gov/medialink/ufo/release_1/fbi-photo-b16.pdf, the title FBI Photo B16, the one-page PDF container, and SHA-256 76bc12588922fca7ef9019f1c809a07e3a159cb1d789013f6acbfcd893935b6a. Rechecking the source file confirmed 433,987 bytes, one encrypted/copy-restricted PDF page, metadata title/subject B16 FBI Photo, and one embedded RGB image at 1280 × 960 pixels. The text/OCR layer remains minimal: page 1 only preserves the visible overlay timestamp 12/31/99 18:20:41.

Visual review of the extracted embedded image supports the existing page description: a grainy monochrome frame, a white central crosshair/reticle, side 3 marks, hard-edged black redaction bars, and a compact unresolved dark mark slightly right of the vertical reticle and above the horizontal reticle, with a smaller dark speck or extension just above/right of it. There is still no visible horizon, terrain, landmark, platform readout, range scale, altitude, or sensor label. The official description's warning that the image date is incorrect remains essential; the displayed 12/31/99 clock is not treated as the incident time.

Graph connections

Read-only graph checks found two matching records in the Release 01 graph family: a PDF asset node carrying the exact B16 URL, 433,987-byte length, and matching SHA-256, and a current Release 01 record node titled FBI Photo B16. The asset node has three text chunks: the linked-PDF asset description, the manifest-description text, and the one-line OCR timestamp. The semantic layer attached to the exact asset contains 22 machine-extracted claims, 14 entity mentions, and 4 sensor-event records.

Those graph claims remain machine-extracted review aids, not findings. The source-backed claims are narrow: FBI submitted a still image derived from a U.S. military system in 2025; the imagery was redacted before AARO submission; no mission report accompanied the image; the operator reportedly could not positively identify the object; and the image clock was not set. The sensor-event records are generated from phrases such as still image and military system, so they do not represent four independent sensor tracks, radar returns, telemetry channels, or raw motion data.

The graph also surfaces release-index drift worth preserving for audit: one current record titled FBI Photo B16 carries a stale final-file pointer to the B13 PDF, while another current record titled FBI Photo B19 carries the B16 PDF pointer. These are provenance-cleanup leads around the manifest/release-record layer. They do not change the identity of the reviewed B16 asset, which is anchored by the exact official URL, byte length, and SHA-256.

External provenance and official-source checks

Direct live checks of the WAR.GOV PDF URL, thumbnail URL, Release 01 CSV URL, and release landing page returned 403 responses from the official server during this review. That access behavior is treated as official-source access/custody context, not as a contradiction of the cached official-primary file, because the reviewed file matches the release inventory URL, byte length, and hash. A Wayback availability probe for the exact official PDF returned 429, so archived confirmation remains a follow-up rather than a completed corroboration in this pass.

A secondary GitHub conversion page for 086-FBI_Photo_B16 was reachable and matches the graph's derived-source lead, but it is only a derived/community mirror. It can help locate alternate text conversions or row-order history; it should not replace the official PDF, release inventory, or exact-hash custody chain.

Prosaic checks and unresolved questions

The public file does not contain enough geometry to run meaningful astronomy, weather, launch, satellite, aircraft, balloon, bird, debris, or line-of-sight correlation. The broad release context says Late 2025 and Western United States, but the exact time, location, platform, sensor mode, field of view, and look direction are absent. At the image level, ordinary explanations remain open and should be checked before escalation if fuller source data becomes available: sensor blemish, dust/debris, compression or display artifact, redaction/display artifact, distant aircraft, bird, balloon, weather/illumination contrast, terrain/background contrast, or another mundane object in a noisy low-context still.

Follow-up leads

• Reconcile the B16/B13/B19 final-file pointer drift in the Release 01 graph and manifest-derived records without changing the exact B16 asset identity.
• Locate a less-redacted original frame, adjacent frames, source video, operator log, mission report, AARO submission record, or official thumbnail that hash/row-checks against the B16 file family.
• Verify the real collection date/time and the collection location independently of the invalid visible clock.
• Identify the platform, sensor, reticle scale, field of view, range/altitude context, and whether the redactions hide telemetry or classification fields.

Audit note

This deep review adds provenance and graph-web context only. It does not classify the dark marks, create a finding, or resolve the case. The reviewed evidence remains a single official-primary still-image PDF with unresolved visual features and substantial missing context.

Sources

• WAR.GOV / PURSUE Release 01 official PDF: FBI Photo B16
• Open Sky release-file endpoint for the same PDF: war-gov-fbi-photo-b16-3b36f3dc
• Release 01 record metadata used for this page: row 119, FBI, late 2025, Western United States
• Verified file hash: 76bc12588922fca7ef9019f1c809a07e3a159cb1d789013f6acbfcd893935b6a
• Source-file review: one-page PDF inspection, embedded-image inspection, rendered-page visual check, and Frontier OCR timestamp check