FBI Photo B23

Evidence media

• Official PDF release-file copy

The page render and extracted raster come from the official one-page PDF. They show the same redacted monochrome still: a wide top redaction band, smaller side/lower redactions, a central reticle/crosshair with 3 marks, lower-left timestamp 12/31/99 18:19:33, and one compact dark unresolved feature slightly right of center near the horizontal reticle. The release description says the image date is incorrect because the system date/time was not set; the visible timestamp should not be treated as the incident date.

Investigation reading

FBI Photo B23 is a one-page PDF container for a single redacted still image released in WAR.GOV/PURSUE Release 01. The release description says the FBI submitted the image to AARO as part of a report of an unidentified anomalous phenomenon, that the still image was derived from a U.S. military system in 2025, and that an accompanying mission report was not provided. The same description says the operator could not positively identify the object and warns that the timestamp printed in the image is incorrect because the system date/time was not set.

The source file is not a narrative report packet. It is a still-image PDF: one page, one embedded RGB image, and no visible captions, narrative text, page labels, maps, diagrams, radar plots, or sensor readout tables beyond markings inside the image itself. OCR contains only the visible image timestamp: 12/31/99 18:19:33.

Visually, the frame is monochrome/grayscale and noisy. A large black redaction band covers the top of the frame, with additional black rectangular redactions around the left, right, and lower portions of the image. A white central reticle/crosshair overlays the scene. Near the center-right, close to the horizontal reticle line, there is one compact dark elongated unresolved feature. It is visible, but too small and indistinct in this released frame to identify from image content alone.

What the file appears to contain

• Container: one-page PDF, 423,857 bytes.
• Embedded image: one RGB image, 1280 × 960 pixels; the rendered page is 640 × 480 points.
• Visible timestamp: 12/31/99 18:19:33. The release description says the image date is incorrect because system time was not set, so this should not be treated as the incident date.
• Visible scene elements: monochrome noisy frame, top redaction band, multiple smaller redaction blocks, central reticle/crosshair, and one compact dark elongated feature near the center-right reticle area.
• Not present in this file: no accompanying mission report, no witness interview, no full video, no unredacted frame sequence, no map, no altitude/speed/range fields, no weather context, and no raw radar/telemetry plot.

The official narrative phrase is that “a single dark, elongated object is visible near the edge of the reticle to the right of center.” The visual pass broadly matches that description: the only high-signal image feature is a small dark elongated mark close to the right side of the central reticle. This page does not identify the mark or treat it as a finding.

Source custody and provenance

The official/source URL for this asset is:

• https://www.war.gov/medialink/ufo/release_1/fbi-photo-b23.pdf

Open Sky’s release-file route for the verified copy is:

• /api/explore/war-gov/release-file/war-gov-fbi-photo-b23-a417f61b

The Open Sky release-file copy is 423,857 bytes with SHA-256:

• ddd839e52ad4d98986a25a760d0040c475d4c43fb7a52cf4c817aa87f51d9271

The exact release record for this asset lists the title as FBI Photo B23, agency FBI, redaction TRUE, incident date Late 2025, and incident location Western United States. The file itself does not independently show the late-2025 date or the Western United States location; those values come from the release metadata, not from visible image text.

One provenance issue should stay visible for review: row numbering is inconsistent across release-derived metadata. The exact release record and source metadata associate this selected asset with CSV row 127, while a manifest-description chunk and a direct CSV-order check can surface FBI Photo B23 at row 130. The file title, official URL, hash, and image content all point to the same B23 asset, but the row-number discrepancy should be cleaned up before relying on row number alone.

Direct official media requests may be access-controlled by the WAR.GOV server. This page cites the verified release-file copy by hash while retaining the official URL as the primary source citation.

Graph context

The graph currently models two exact document records for this item: the Release 01 record page entry and the linked PDF asset. The semantic extraction attached to the asset has 22 extracted claims, 14 entity mentions, 4 sensor-event records, and 0 table rows.

The useful graph context is narrow:

• Claim extraction repeats the release description: FBI/AARO, a still image from a U.S. military system in 2025, no mission report, operator unable to positively identify the UAP, date/time not set, and a single dark elongated object near the reticle right of center.
• The four sensor-event records are extraction cues from phrases such as “still image” and “military system.” They are not independent tracks, radar returns, telemetry, or multiple corroborating sensor records.
• Related graph links point to nearby FBI Photo records, including B20 and B4, plus the B23 release record. Treat those as navigation through the B-series photo set, not as evidence that the same object or event is confirmed across files.
• There are no candidate crosslinks for this item in the current context output.

Leads to check

• Compare B23 against adjacent FBI Photo B-series images to see whether timestamp order, reticle placement, redaction layout, and compact dark-feature position suggest a sequence, duplicate, or independent still. Do this as an image-sequence review, not as an identification claim.
• Resolve the CSV row-number mismatch (127 vs 130) in the release metadata and derived graph chunks.
• If official access permits, compare the current WAR.GOV PDF and thumbnail byte-for-byte or visually against the verified release-file copy to detect any server-side version drift.
• Look for any separately released mission report, operator statement, image sequence, or unredacted source frame. The current release description says no accompanying mission report was provided.
• Review scan/compression/noise/redaction artifacts and reticle overlay behavior before escalating the compact dark mark as anything more than an unresolved image feature.

Lead check notes

• Checked — The verified Open Sky release-file copy is a one-page PDF, 423,857 bytes, with SHA-256 ddd839e52ad4d98986a25a760d0040c475d4c43fb7a52cf4c817aa87f51d9271. The PDF contains one RGB embedded image object (1280 × 960) and no embedded attachments; the derived page render and extracted raster come from that PDF.
• Checked — Rendered-page and embedded-raster review confirm a redacted monochrome still with a central reticle, lower-left 12/31/99 18:19:33 timestamp, and one compact dark unresolved feature slightly right of center near the horizontal reticle. The released still does not establish distance, motion, identity, or source cause.
• Partial — B-series comparison remains an image-sequence review lead. Current graph links to nearby FBI Photo records are useful navigation through the B-series set, not evidence that B23 shares the same object, event, or source frame with another file.
• Partial — The visible timestamp is present in the PDF render and OCR, but the release description says the image date is incorrect because system time was not set. The collection window remains only Late 2025 from release metadata.
• Partial — The selected release record and source metadata associate B23 with row 127; a manifest-description chunk/direct CSV-order check can surface row 130. The title, URL, hash, and image content anchor the B23 asset, but row numbering remains a provenance-cleanup lead.
• Blocked — Direct WAR.GOV HEAD and byte-range PDF requests currently return 403 text/html, so server-side version-drift comparison against the verified release-file copy is not complete.
• Needs external source — Less-redacted source imagery, original frame export, adjacent frames/video, mission report, collection log, platform/sensor geometry, exact time/location, and environmental data are needed for scan/compression, redaction, aircraft, bird, balloon, terrain, illumination, weather, or line-of-sight checks.

Limits

This is a redacted still-image page, not a complete case file. The released evidence does not include a mission report, original system metadata, sensor calibration, full-motion video, altitude/range/speed data, weather, aircraft/platform identity, or chain-of-custody details beyond the release record and file hash. The image timestamp is explicitly unreliable according to the release description.

Because the visible feature is small, dark, and unresolved in a noisy redacted frame, this page makes no identification and no finding. It preserves the source, the visible image content, the graph context, and the follow-up checks needed for human review.

Deep investigation — graph + web reconnaissance

Source reread

A fresh source pass confirmed that B23 is a one-page, copy-restricted PDF titled FBI Photo B23. The verified release-file copy is 423,857 bytes with SHA-256 ddd839e52ad4d98986a25a760d0040c475d4c43fb7a52cf4c817aa87f51d9271. PDF metadata shows one 640 × 480 point page and one embedded RGB raster image at 1280 × 960 pixels; there are no embedded attachments. OCR still contains only the page marker and the visible timestamp 12/31/99 18:19:33.

Rendered-page and embedded-raster review support the existing visual description: a noisy monochrome still with a broad top redaction band, smaller side/lower redactions, a central white reticle/crosshair with 3 markings, the lower-left timestamp, and one compact dark elongated unresolved mark slightly right of the reticle center near the horizontal line. The source image does not provide distance, motion, scale, platform geometry, or object identity. The release description says the system date/time was not set, so the printed 12/31/99 timestamp remains a visible overlay, not an incident date.

Read-only graph connections

Read-only graph checks found the same exact PDF asset by URL and SHA-256, plus the corresponding Release 01 record page entry. The semantic layer for the asset contains 22 machine-extracted Claim nodes, 14 EntityMention nodes, and 4 SensorEvent nodes. The useful extraction content repeats the source description: FBI/AARO provenance, still image from a U.S. military system in 2025, no accompanying mission report, operator unable to positively identify the UAP, unreliable image date/time, and a single dark elongated mark near the right-of-center reticle area.

The sensor-event rows are not independent sensor corroboration. They are machine extraction/navigation cues from phrases such as still image and military system, marked as needing human review and not_a_finding; they should not be read as radar, telemetry, full-motion-video tracking, or a resolved sensor event.

The strongest graph/provenance issue is row drift in the FBI B-series records. The selected asset inventory and exact B23 release record associate the page with row 127, while the B-series source-pack table places the fbi-photo-b23.pdf file at row 130. A nearby graph release record titled FBI Photo B4 also points at the B23 PDF URL/byte count, while the row-127 B23 record carries a stale B20 PDF URL. This is a metadata-cleanup lead, not evidence for a separate event or a reassignment of the image content. For B23, the stable identifiers remain title, canonical PDF URL, size, and SHA-256.

No CANDIDATE_CROSSLINK relationship was found for this asset. A derived UFO-USA GitHub markdown conversion is reachable as a secondary mirror/processing lead only; it does not add source authority or object identification. Related B20/B4/B-series graph links should be treated as navigation through adjacent photo records until a page-by-page sequence review proves a real image relationship.

Official and external reconnaissance

Official WAR.GOV/PURSUE remains the primary source spine for this item: the landing page, CSV manifest, and canonical PDF URL are the authoritative citations. During this check, direct WAR.GOV HEAD and byte-range requests for the PDF, landing page, and both observed CSV paths returned 403 text/html access-denied responses. That is an access/version-drift limitation, not a contradiction of the verified copy, because the Open Sky release-file copy matches the expected PDF size and SHA-256.

Internet Archive availability/CDX probes for the exact B23 PDF URL were rate-limited or timed out during this pass, so archive confirmation remains open. DVIDS exact-title probing returned an empty/indeterminate response, and Defense.gov/AARO exact-title search probes returned 403; no public video, mission report, DVIDS media item, or AARO case page was surfaced for B23. Secondary/community mirrors can help discover file naming or row-order drift, but they should remain leads until checked back against the official PDF, CSV, or another canonical government record.

Prosaic checks and open questions

The first prosaic lane is image provenance, not sky correlation: redaction geometry, scan/compression noise, reticle overlay behavior, frame export settings, and whether adjacent B-series stills show the same mark, a moving mark, or a fixed artifact. Astronomy, weather, launch, satellite, aircraft, balloon, and line-of-sight checks are not meaningful yet because the public source lacks a reliable timestamp, exact location, platform, sensor model, look direction, and original frame sequence. Late 2025 and Western United States are release metadata fields, not independently visible image facts.

Follow-up should prioritize: resolving the B20/B23/B4 row and URL drift; obtaining any less-redacted original frame, adjacent frames/video, collection log, or mission report; comparing the official WAR.GOV PDF against an archived snapshot once access permits; and checking whether the compact dark mark persists, shifts, or disappears across the B-series image set. Until those materials exist, B23 stays an unresolved, redacted still-image source with no finding or hypothesis attached.

Sources

• WAR.GOV/PURSUE Release 01 official PDF: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b23.pdf
• Open Sky release-file route: /api/explore/war-gov/release-file/war-gov-fbi-photo-b23-a417f61b
• SHA-256 verified release-file copy: ddd839e52ad4d98986a25a760d0040c475d4c43fb7a52cf4c817aa87f51d9271
• Release metadata: FBI Photo B23; FBI; PDF; redaction TRUE; incident date Late 2025; incident location Western United States; official description notes no accompanying mission report and unreliable image date/time.
• OCR coverage: one page; OCR text only 12/31/99 18:19:33.