FBI Photo B18

Evidence media

Official PDF: Open Sky release-file copy

Derived official PDF page render: FBI Photo B18

The page render shows the one-page released still-image PDF: a noisy monochrome frame with a central reticle, top and side redactions, and the visible 12/31/99 18:21:02 overlay. The official release description says that image date is incorrect because the system date/time was not set.

Embedded image object extracted from the official PDF: FBI Photo B18

The embedded raster is the actual 1280 x 960 image object inside the PDF. It shows two compact dark marks slightly right of the central vertical reticle and below the horizontal reticle; the released still alone does not identify them or provide motion, range, platform, or collection geometry.

Investigation reading

FBI Photo B18 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 file was reviewed as a PDF container, as its embedded raster image, as a rendered page image, and against the available OCR text. The Open Sky release-file copy verifies as 429,941 bytes with SHA-256 5e8801ee956ccb3aed9c605cd9e1d097b2abfd379d3d6e84d4c09a080aa570fd. PDF inspection shows one encrypted/copy-restricted page, page size 640 x 480 points, PDF metadata title/subject B18 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 timestamp and six redaction placeholders.

The displayed timestamp should not be treated as the incident time. The visible lower-left overlay reads 12/31/99 18:21:02, and the official release description says the image date is incorrect because the system date/time was not set. The broader release-record context currently available here is Late 2025 and Western United States. The public file does not expose exact collection date, platform, sensor model, range, altitude, field of view, location, mission track, or frame-sequence context.

What the file appears to contain

The rendered page shows a noisy monochrome sensor-style frame with a central white reticle. A vertical reticle line and a horizontal reticle line cross near the center; small side tick marks and a 3-like marking are visible near both ends of the horizontal line. A large black redaction band covers most of the top of the image, and several smaller black redaction blocks cover left and right display regions. These blocks are release/source redactions or display overlays, not original scene content, and they may hide labels, telemetry, or other source fields.

The background is a mottled gray texture with no clear horizon, terrain, waterline, building, vehicle, person, aircraft silhouette, star field, cloud form, or landmark visible in the public frame. The two high-contrast features of interest are small, dark, elongated marks in the lower portion of the reticle area. In the rendered image they appear below the horizontal reticle and slightly to the right of the vertical reticle, close together and separated by a narrow gap. The official narrative description says two small, dark, elongated objects are visible near the center of the frame in the lower left quadrant; that quadrant wording should be checked against the source display orientation and any coordinate convention before it is reused analytically.

The released still alone does not establish true shape, size, distance, motion, identity, or whether the marks are external objects versus image/sensor/display artifacts. No adjacent frames, video sequence, raw telemetry, mission report, operator log, or unredacted display fields are included in this PDF.

Source custody and provenance

Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b18.pdf
Open released file: war-gov-fbi-photo-b18-c568aea2
Release 01 row currently associated with this page: 121
Agency: FBI
Source/container kind: one-page PDF still-image container
Verified file size: 429,941 bytes
Verified SHA-256: 5e8801ee956ccb3aed9c605cd9e1d097b2abfd379d3d6e84d4c09a080aa570fd
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, platform identification, collection geometry, environmental context, or unredacted display fields. The current official server blocked HEAD and full GET requests but allowed a ranged retrieval of a 61,286-byte PDF with the same visible title/page count and a different SHA-256 (64c4b8d8df93af933cc16efc183c27a4262284d0dffe2ca5f6479a32fa536eb0) from the verified 429,941-byte Open Sky release-file copy. Treat that as a custody/versioning lead until official change history or a full-source comparison resolves whether it is only server-side optimization/compression or a materially different served file.

Graph context

The graph has exact source records for the B18 PDF asset and for the Release 01 record with the same title. The selected release record associates this page with row 121, FBI, Late 2025, and Western United States; the PDF asset record carries the official PDF URL and the verified SHA-256. 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 release describes a still image from a U.S. military system; the file was redacted before submission to AARO; no mission report accompanied it; 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, including B15 and B20, but those links are release-neighborhood context unless each related item is checked by row number, URL, hash, and visible image content. One derived manifest-description chunk for this title surfaces row 124, while the selected release record and release metadata associate B18 with row 121; treat that 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 18:21:02 display clock and the broad Late 2025 release field.
Identify the platform, sensor type, reticle meaning, field of view, range scale, altitude context, location, and whether redactions hide telemetry or classification markings.
Reconcile the row 121 / row 124 manifest-description mismatch before using row numbers or related-record links for cross-page analysis.
Compare the official narrative's lower-left-quadrant wording with the rendered image orientation and any sensor coordinate convention.
Compare the current official-site served file, if obtainable, against the verified 429,941-byte Open Sky release-file copy and hash.
Run ordinary image-quality and prosaic checks before escalation: sensor blemish, dust/debris, compression artifact, display artifact, redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight.

Lead check notes

Checked — The verified Open Sky release-file copy contains one embedded RGB image object (1280 x 960) and no embedded attachments; the derived page render and extracted raster above come from that PDF.
Blocked — Less-redacted source imagery, adjacent frames or video, original export, operator log, mission report, and AARO submission metadata are not present in the public PDF or release record checked here.
Partial — The visible 12/31/99 18:21:02 overlay is present in the PDF/OCR, but the official release says the image date is incorrect because the system clock was not set; the collection window remains only Late 2025 in the release record.
Partial — Open Sky source records and release metadata associate B18 with row 121; a separate manifest-description chunk surfaced row 124, which is also represented as nearby FBI Photo B20 context, so row numbering should remain a provenance-cleanup lead.
Partial — Rendered-page and embedded-raster review confirm the two dark marks are visible slightly right of the central vertical reticle and below the horizontal line. The release description's lower-left-quadrant wording remains display-orientation dependent until a source coordinate convention is available.
Needs external source — Sensor blemish, dust/debris, compression/display/redaction artifact, distant aircraft, bird, balloon, terrain, weather, illumination, and line-of-sight checks require unredacted imagery, source metadata, adjacent frames, exact location/time, or environmental data.

Deep investigation — graph + web reconnaissance

Source reread and visual audit

The source-file recheck confirms a one-page, copy-restricted PDF still-image container: 429,941 bytes, SHA-256 5e8801ee956ccb3aed9c605cd9e1d097b2abfd379d3d6e84d4c09a080aa570fd, PDF title/subject B18 FBI Photo, and one embedded RGB image object at 1280 x 960 pixels. OCR adds almost no scene context: it captures the visible 12/31/99 18:21:02 overlay plus redaction placeholders. That overlay remains unreliable because the Release 01 description says the image date is incorrect due to the system date/time not being set.

Rendered-page and embedded-raster review support only a narrow visual statement. The public frame is a noisy monochrome reticle image with top/side redactions, small reticle tick marks, and two compact adjacent dark marks slightly right of the central vertical reticle and below the horizontal reticle. The single still does not establish whether those marks are external objects, image/sensor artifacts, compression/display artifacts, redaction-side effects, or something else; it also provides no usable scale, motion, range, altitude, heading, sensor model, platform, or location.

Graph connections and extraction limits

Read-only graph checks match the exact official PDF asset by URL and verified hash and link it to the current Release 01 row 121 record for FBI Photo B18. The same graph neighborhood also preserves a row/provenance drift lead: the B18 asset has related_csv_row_numbers: [121], but a manifest-description path also lists row 124, and a stale RELATED_TO edge points to the FBI Photo B20 row with current_in_official_csv: false. Treat row 121, the B18 title, the official PDF URL, and the verified SHA-256 as the stable identifiers until the manifest-row mismatch is cleaned up.

The semantic layer currently contains 23 machine-extracted claims, 15 entity mentions, and 4 sensor-event records for this asset. Those records are navigation aids, not findings: the sensor-event nodes are triggered by source phrases such as still image and military system, while the strongest source-backed claims remain the release description's own statements that the still came from a U.S. military system in 2025, had redactions before AARO received it, had no accompanying mission report, and was not positively identified by the operator. A secondary UFO-USA GitHub Markdown conversion repeats the visible redactions/crosshair/timestamp and is useful as a search lead only; it is not replacement custody for the WAR.GOV/PURSUE file.

External provenance and web reconnaissance

Direct checks of the live WAR.GOV PDF, Release 01 CSV, Release 01 landing page, and WAR.GOV press-release page returned 403 access-denied responses during this check, which is consistent with prior Release 01 access-control behavior and does not override the verified Open Sky release-file copy. Internet Archive availability for the exact PDF URL returned a closest archived snapshot at 20260514084025; that archived PDF is 61,286 bytes with SHA-256 64c4b8d8df93af933cc16efc183c27a4262284d0dffe2ca5f6479a32fa536eb0, the same B18 FBI Photo title, one page, and one 1280 x 960 embedded image. Because that archived/current-server version differs in file size and hash from the verified 429,941-byte Open Sky copy while preserving the same basic page identity, it should remain a custody/versioning lead until a full official change-history or frame-level comparison resolves whether the difference is only PDF optimization/compression.

Internet Archive also has an archived WAR.GOV press-release page at 20260512044008 titled Department of War Releases Unidentified Anomalous Phenomena Files in Historic Transparency Effort, dated May 8, 2026; its description frames the release as the initial PURSUE release of new UAP files. That press item supports the release-spine provenance, not the identity of the two dark marks in B18. The Release 01 record and graph show no DVIDS video pairing or mission-report attachment for this page.

Prosaic checks and open questions

No meaningful astronomy, weather, launch, satellite, aircraft, balloon, or line-of-sight correlation can be run from the public B18 source alone: the exact collection time, location, platform, sensor, field of view, look direction, altitude, range, and adjacent frames are absent, and the only displayed clock is officially unreliable. The first ordinary-check lanes therefore remain image/source-quality lanes: sensor blemish, dust/debris, compression or resampling artifact, display artifact, redaction/masking artifact, distant aircraft, bird, balloon, terrain/weather contrast, illumination, or other single-frame ambiguity.

Follow-up should stay evidence-bound: obtain a less-redacted original export or adjacent-frame/video sequence; reconcile row 121 versus the manifest-description row 124/B20 drift; compare the archived 61,286-byte optimized PDF against the verified Open Sky release-file copy at the image-object level; and locate any operator log, mission report, AARO submission metadata, or source telemetry before creating findings, hypotheses, or resolution decisions.

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.

Sources

WAR.GOV / PURSUE Release 01 official PDF: FBI Photo B18
Open Sky release-file endpoint for the same PDF: war-gov-fbi-photo-b18-c568aea2
Release 01 record metadata used for this page: row 121, FBI, late 2025, Western United States
Verified file hash: 5e8801ee956ccb3aed9c605cd9e1d097b2abfd379d3d6e84d4c09a080aa570fd
Source-file review: one-page PDF inspection, embedded-image extraction, rendered-page visual check, direct OCR text check, and graph-context review