FBI Photo B14

Evidence media

• Official PDF container: Open Sky Release 01 file copy

Derived page render from the official one-page PDF. The image shows a grainy monochrome sensor-style frame with a central reticle, black redaction blocks, the visible overlay timestamp 12/31/99 18:20:08, and two small unresolved dark marks near the reticle. The release description says the displayed date/time is incorrect because the system date/time was not set.

Extracted raster from the PDF image object. It is included to show the real embedded still apart from the rendered PDF page; it is not a separate source or an identification of the visible marks.

Investigation reading

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

The source file was checked directly as a PDF container, not only through graph text. The Open Sky release-file copy verifies as 448,290 bytes with SHA-256 54f36aa547dd25b7c099a66b2c5f52c951315906a704d6b215cb1651e7dc92f2. PDF inspection shows one encrypted/copy-disabled page, page size 640 x 480 points, metadata title/subject B14 FBI Photo, and one embedded RGB image measuring 1280 x 960 pixels. There is no useful selectable text layer; the OCR pass only captures redaction labels and the visible lower-left overlay timestamp 12/31/99 18:20:08.

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 current Release 01 record supplies only the broad incident context Late 2025 and Western United States; the image itself does not independently verify the exact date, time, platform, sensor, or location.

What the file appears to contain

The rendered page and embedded raster show a grainy monochrome sensor-style frame. A bright white central reticle is visible, with a vertical line and horizontal line crossing near the center, small tick marks, and the number 3 visible near both sides of the horizontal reticle. Multiple hard-edged black redaction blocks cover the top band and several left/right display areas. Some lighter gray rectangular patches appear adjacent to the redactions, so the release masking and any original scene content should be kept separate.

The lower-left overlay reads 12/31/99 18:20:08. The unredacted background is mostly noisy gray with blocky texture and no clear terrain, building, vehicle, horizon, person, or landmark. Slightly right of the vertical reticle line and just above the horizontal reticle line, two small dark rounded features are visible. The left feature appears smaller and more circular; the right feature is darker and a little more vertically irregular. The official narrative description calls out two small, dark, circular objects near the center of the frame. On the released still alone, these remain unresolved visual features with no public scale, range, altitude, motion sequence, or source geometry.

A conspicuous speckled artifact region is visible around the lower-right/mid-right redaction area. It has a jagged, noisy edge and looks visually distinct from both the clean black redaction bars and the smoother gray background. That artifact should be treated as an image/redaction-quality lead unless the source system or a less-redacted frame explains it.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b14.pdf
• Open released file: war-gov-fbi-photo-b14-7d1b5016
• Release 01 CSV row: 117
• Agency: FBI
• Source/container kind: one-page PDF still-image container
• Verified file size: 448,290 bytes
• Verified SHA-256: 54f36aa547dd25b7c099a66b2c5f52c951315906a704d6b215cb1651e7dc92f2
• 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, range/altitude readout, or unredacted telemetry.

Graph context

The graph has exact source records for the B14 PDF asset and the current Release 01 row-117 record. The semantic layer currently carries 23 extracted claim records, 15 entity mentions, 4 sensor-event records, and no table rows for this asset. The strongest source-backed points are narrow: the file is a still image from a U.S. military system; it was redacted; the operator reportedly could not positively identify the UAP; and the visible image date/time 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 photo items such as B11 and B17, but those links are release-neighborhood context unless source-row and image-level review establishes a stronger relationship.

One semantic description chunk for this asset appears to cite related CSV row 120, while the current exact release record and selected asset metadata place B14 at row 117; row 120 is surfaced elsewhere as FBI Photo B17. Treat that as a custody/indexing cleanup lead, not a content conclusion about B14.

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 B14 with official thumbnails and nearby FBI 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 117 / row 120 semantic mismatch before using row numbers or related-record links for cross-page analysis.

Lead check notes

• Blocked — less-redacted source package: The released record exposes a one-page still-image PDF and says no accompanying mission report was provided. No source video, adjacent frames, operator log, original export, or AARO submission package is present in the current public release.
• Blocked — platform and sensor details: The source description only says the still image came from a U.S. military system. Platform identity, sensor mode, field of view, reticle scale, range, altitude, and collection geometry all require a less-redacted source.
• Partial — displayed timestamp and event context: The visible overlay reads 12/31/99 18:20:08, but the release description says the image date/time is incorrect because the system date/time was not set. The current release record gives only Late 2025 and Western United States; exact time and place remain external-source leads.
• Partial — neighboring still-image comparison: Nearby FBI B-series records can be compared only after each title, URL, row number, hash, and visible frame content is checked. For B14, the current release row is 117; one semantic description chunk still cites row 120, so that remains an indexing cleanup item rather than a content conclusion.
• Needs external source — ordinary image checks: Sensor blemish, dust/debris, compression, display or redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight cannot be tested from this redacted single frame alone. Those checks need unredacted imagery, adjacent frames, source video, or collection geometry.

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 therefore documented only as unresolved features in a noisy, redacted image pending human review and additional source material.

Deep investigation — graph + web reconnaissance

Source reread

The source reread confirms this is a one-page FBI PDF still-image container, not a mission report. The verified public file is 448,290 bytes with SHA-256 54f36aa547dd25b7c099a66b2c5f52c951315906a704d6b215cb1651e7dc92f2. PDF inspection shows one encrypted/copy-disabled page, metadata title/subject B14 FBI Photo, and one embedded RGB image at 1280 x 960 pixels. Selectable text extraction is effectively blank; the OCR layer captures redaction labels and the visible overlay timestamp 12/31/99 18:20:08.

Visual review of both the rendered PDF page and the extracted embedded raster matches the earlier page read: a grainy monochrome frame, central white reticle with 3 markers on the horizontal line, multiple black redaction blocks, two small unresolved dark marks just right of the reticle center, and a speckled/jagged artifact region along the mid-to-lower-right redaction area. The release description states the displayed date/time is incorrect because the system date/time was not set, so the overlay should not be used as the event time.

Graph connections

Neo4j read-only checks found exact records for the PDF asset and the current Release 01 row-117 record. The exact asset URL/hash is the stable identity; the row record supplies the broad public context Late 2025 and Western United States. The semantic layer currently attaches 23 machine-extracted claims, 15 entity mentions, and 4 sensor-event records to this asset, with all graph claims requiring human review and marked as not findings.

The graph sensor records are source-navigation cues from phrases such as still image and military system; they are not independent radar, telemetry, range, altitude, or multi-sensor tracks. Direct text chunks preserve the official manifest description and the OCR redaction/timestamp text. A second manifest-description chunk still cites related row 120 while the current exact release record places B14 at row 117; row 120 appears as FBI Photo B17, so that remains a provenance/indexing cleanup lead rather than evidence that B14 and B17 are the same event. No CANDIDATE_CROSSLINK edge was found for this asset.

External provenance and official-source checks

Official WAR.GOV/PURSUE direct probes for the PDF, the release landing page, and release CSV endpoints returned 403 Forbidden during this check, which is consistent with prior Release 01 access behavior from this environment and is not treated as a source invalidation because the cached official-primary file verifies by size and hash. The Internet Archive Wayback availability API reported an exact-URL archived PDF snapshot with status 200 at timestamp 20260508200709: web.archive.org snapshot.

DVIDS, AARO, and Defense.gov public search probes did not surface a usable independent public companion record in this run: DVIDS returned an API-key-gated response, while AARO and Defense.gov search pages returned 403. No released companion mission report, video sequence, raw sensor package, adjacent frame set, platform ID, range/altitude readout, or unredacted telemetry was identified through the official-first checks available here.

Prosaic checks and open questions

The available public packet is too redacted and too sparse for meaningful astronomy, weather, satellite, launch, aircraft, or balloon correlation. The public record lacks the actual collection date/time, precise location, platform track, sensor model, field of view, look angle, range scale, and adjacent frames. The broad Late 2025 / Western United States context is not enough to run responsible environmental correlation.

The immediate prosaic lanes remain image-quality and scene-context checks: sensor blemish or dust, compression/display artifact, redaction-edge artifact, distant aircraft, bird, balloon, terrain or background contrast, and illumination effects. Those checks require the original or less-redacted image export, adjacent frames or video, source-system metadata, and collection geometry before the two visible dark marks can be escalated beyond unresolved features in a redacted still.

Audit note

This deep pass adds provenance and graph/web context only. It does not identify the visible marks, create a finding, or resolve the case. The strongest public statement remains narrow: FBI Photo B14 is a verified official Release 01 still-image PDF whose release description says the operator could not positively identify the UAP, while the public file itself does not provide the data needed to test motion, scale, range, altitude, timestamp, platform, or ordinary environmental explanations.

Sources

• WAR.GOV / PURSUE Release 01 official PDF: FBI Photo B14
• Internet Archive exact-URL availability lead: 2026-05-08 archived PDF snapshot
• Open Sky release-file endpoint for the same PDF: war-gov-fbi-photo-b14-7d1b5016
• Current Release 01 record metadata: row 117, FBI, late 2025, Western United States
• Verified file hash: 54f36aa547dd25b7c099a66b2c5f52c951315906a704d6b215cb1651e7dc92f2
• Source-file review: one-page PDF inspection, embedded-image inspection, rendered-page visual check, Frontier OCR timestamp check, Neo4j exact-record/semantic read-only queries, and official-first web provenance probes