← Back to Files & Wiki
Wiki page · asset · graph_investigation_draft

FBI Photo B21

Official PDF: Open Sky release file copy

Release 01#war-gov#pursue#release-01#official-source#evidence#pdf#still-image

FBI Photo B21

Evidence media

Derived official PDF page render: FBI Photo B21

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

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

The extracted raster is the actual 1280 x 960 image object embedded in the PDF. It shows the same reticle/redaction layout and a compact dark unresolved mark just right of the vertical reticle and slightly above the horizontal line; the public still alone does not identify the mark or provide motion, range, platform, or collection geometry.

Investigation reading

FBI Photo B21 is a one-page Release 01 PDF containing a redacted monochrome still image. The release record says the FBI submitted the report to AARO, that the still image came from a U.S. military system in 2025, and that no accompanying mission report was provided. The operator statement preserved in the release metadata is narrow: the operator was unable to positively identify the UAP. That is a source statement, not an Open Sky finding.

The verified release copy is 592,551 bytes with SHA-256 52b81ee21a3bfc5ecce1777d6e91d85aabe8bb905dab1963a793dd4787005214. The PDF has one 640 × 480 point page and embeds a 1280 × 960 RGB image. OCR for the page contains only the visible timestamp, 12/31/99 18:19:06; a selectable-text pass did not recover a narrative layer from the PDF. The release description itself warns that the date in the image is incorrect because the system date/time was not set.

What the file appears to contain

The rendered page shows a grainy gray image field with a white crosshair-style reticle near the center. The horizontal reticle has tick marks and visible numeric labels stepping out from the center, including 5, 10, and 15 on both sides. Several solid black redaction blocks cover large parts of the top, side, and lower portions of the frame. A white blocky timestamp in the lower-left corner reads 12/31/99 18:19:06.

The visible unresolved feature is compact and dark, positioned just to the right of the vertical reticle line and slightly above the horizontal reticle line. In the render it appears primarily as one short, irregular, horizontally elongated dark mark with a darker core and uneven edges. Because the image is noisy and pixelated, the mark can also look like two very close dark lobes inside the same small feature. The available page does not provide enough context to separate those possibilities or identify the feature.

No map, mission narrative, range/rate table, altitude data, platform details, unredacted frame, or multi-frame sequence is visible in this PDF.

Source custody and provenance

The PDF metadata title and subject are both FBI Photo B21. The rendered file and OCR agree on the only visible text recovered from the image: 12/31/99 18:19:06. Because the release says the system date/time was not set, that overlay should not be treated as the incident date.

Graph context

The graph currently has an official PDF asset record for FBI Photo B21 and a separate Release 01 record node for the current CSV row. The semantic extraction attached to this item is small: 22 extracted claims, 14 entity mentions, 4 sensor-event records, and no table rows. Those extracted claims mainly restate the release description: FBI/AARO custody, a still image from a military system, the operator's inability to identify the UAP, the 2025 incident window, and Western United States location.

The four sensor-event records should be read as indexing aids for the still-image and military-system language in the release metadata. They are not independent instrument returns, telemetry packets, or a mission-report sensor log. The graph also links this item near other FBI Photo B-series records, including B19 and B24, but no candidate crosslinks are asserted for this page. One review item remains: release metadata identifies the current row as 125, while one derived manifest-description fragment appears to carry a different row association. That should be checked against the current official CSV before using row numbers for batch-level analysis.

Review status: graph_investigation_draft; investigation status: needs_human_review; finding status: not_a_finding.

Leads to check

  • Compare B21 against adjacent FBI Photo B-series stills to see whether the reticle, redaction pattern, timestamp range, and compact dark marks belong to one image sequence or to separate source events.
  • Check whether AARO, FBI, or the release custodian can provide the missing mission report, original frame, unredacted still, or adjacent frames.
  • Verify the current CSV row mapping and any stale row associations before treating B21 as part of a row-numbered cluster.
  • Reassess the compact dark mark with the best available original image quality; the current PDF render is noisy and redacted.
  • Run ordinary image-quality checks before escalation: compression artifacts, display reticle overlay, scan/render artifacts, sensor noise, dust/speck artifacts, and redaction-side effects.

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, original frame export, adjacent frames/video, mission report, collection log, platform/sensor geometry, and AARO/FBI source package are not present in the released PDF or record.
  • Partial — The visible 12/31/99 18:19:06 overlay is present in the PDF/OCR, but the release description says the image date is incorrect because the system date/time was not set; the collection window remains only Late 2025 in the release record.
  • Partial — Current source records place B21 at CSV row 125; a separate manifest-description fragment surfaced row 128, which appears as nearby FBI Photo B24 context, so row numbering remains a provenance-cleanup lead before sequence analysis.
  • Checked — Rendered-page and embedded-raster review confirm one compact dark unresolved mark just right of the vertical reticle and slightly above the horizontal reticle line, with a possible two-lobed appearance caused by noise/pixelation. The released still does not support distance, motion, identity, or source-cause determination.
  • Needs external source — Sensor blemish, dust/debris, compression/display/redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight checks require unredacted imagery, adjacent frames, source metadata, exact location/time, or environmental data.

Deep investigation — graph + web reconnaissance

Source reread

The source object still verifies as the official one-page PDF for FBI Photo B21: 592,551 bytes, SHA-256 52b81ee21a3bfc5ecce1777d6e91d85aabe8bb905dab1963a793dd4787005214, PDF title/subject FBI Photo B21, one 640 × 480 point page, and one embedded 1280 × 960 RGB image. The rendered page and extracted image agree on the visible evidence: a noisy monochrome frame with a large top redaction, side redactions, a central reticle, the lower-left overlay 12/31/99 18:19:06, and one compact dark unresolved mark just right of the vertical reticle and slightly above the horizontal line. OCR contributes only the timestamp line; it does not add a mission narrative, location, sensor settings, or track data. The release description's warning that the image date is incorrect remains controlling, so the overlay is a visible artifact of the image, not an incident time.

Graph connections

The graph has two exact official records for this item: the Release 01 row-level document for current row 125 and the PDF asset document at the official fbi-photo-b21.pdf URL. The semantic layer is bounded and should remain in human-review posture: 22 machine-extracted claims, 14 entity mentions, 4 sensor-event rows, and no table rows. The claims repeat source metadata such as FBI/AARO custody, Late 2025, Western United States, still image, military system, and the operator statement that the UAP could not be positively identified. The four sensor-event rows are still-image / military-system indexing aids, not independent telemetry, radar, FLIR footage, or a mission log.

No CANDIDATE_CROSSLINK is asserted for B21. Direct related-document context includes nearby FBI Photo B-series material, especially B19/B24-style row-navigation edges, plus a secondary UFO-USA Markdown conversion. Those are provenance/navigation leads only. One graph edge still preserves a non-current row 128 association that points into the B24 row area; current graph identity should be anchored by the exact PDF URL, hash, and row 125 until the official table drift is reconciled.

External provenance/context

Live official probes to the WAR.GOV PDF, WAR.GOV release page, and WAR.GOV CSV returned HTTP 403, but the Internet Archive availability record exposes an exact official-PDF snapshot from 20260508200711. A range check against that archived capture returned 206 application/pdf, Content-Range: bytes 0-15/592551, and the expected %PDF-1.7 header bytes, matching the verified Open Sky release-file size. An archived official uap-release001.csv snapshot from 20260515033121 also contains the B21 row family: it spells this entry as FBI Photo B021, gives the same official PDF URL, lists image VIRIN 260508-O-D0360-1049, and describes the image as a redacted sensor image with a targeting reticle centered on an object.

That archived CSV snapshot adds a useful but unresolved catalog lead: B020 through B024 are shown with PDF Pairing: USPER Statement about UAP Sighting. The current graph row for B21 has blank PDF/video pairing fields, while the graph separately contains the USPER statement as row 153 / asset usper-statement-redacted.pdf. Until the official live table, graph reconciliation, and source text prove the relationship, this is a provenance lead rather than evidence that the B21 still and the USPER statement are the same event. The USPER page should be read separately: USPER Statement about UAP Sighting.

Targeted DVIDS/FBI/AARO/Defense-style web checks did not provide a public mission packet, original frame, adjacent-frame sequence, or authoritative sensor log for B21 during this pass. A DVIDS title search returned an empty/challenge-style response, and FBI/AARO official pages were not directly accessible from the same probe set.

Prosaic checks and constraints

The available public evidence does not support a resolved cause check. With only Late 2025, Western United States, and a generic U.S. military system, there is no precise time, location, line of sight, platform track, altitude, range, azimuth/elevation, weather, aircraft/balloon traffic, launch, satellite, or astronomy window to correlate. The most responsible prosaic lanes are therefore image/source-quality checks: redaction effects, display or reticle overlay artifacts, compression/rasterization, sensor noise, dust or blemish, image-export artifacts, and comparison with adjacent B-series frames. None of those can be closed from the one redacted PDF alone.

Follow-up leads

  • Reconcile the B21/B021 title spelling, row 125 graph/current-row identity, older row 128 manifest fragment, archived CSV record ordering, and the USPER Statement about UAP Sighting pairing field before using B21 in sequence or companion-document analysis.
  • Seek the original frame export, less-redacted image, adjacent frames/video, collection log, platform/sensor metadata, and any mission report or AARO/FBI source package.
  • Compare B20–B24 visually and by release metadata only as a lead; do not assert one continuous event sequence unless an authoritative source links the frames.
  • Keep the compact dark mark described as an unresolved image feature unless higher-quality source material or source metadata supports more.

Audit note

This section separates source facts, machine-extracted graph claims, archived official-table metadata, and unresolved leads. It does not create a finding, hypothesis, or resolution decision.

Limits

This page is a source-reading draft, not a resolution. The released evidence for B21 is a single redacted still inside a one-page PDF. There is no accompanying mission report, no unredacted imagery, no documented object track, no range or altitude data, no platform identifier beyond the general phrase U.S. military system, and no independent witness statement beyond the operator identification statement in the release metadata. The visible feature remains an unresolved mark in a low-context, noisy frame.

Sources

  • WAR.GOV/PURSUE Release 01 official PDF: FBI Photo B21
  • Open Sky release-file endpoint: war-gov-fbi-photo-b21-c304734c
  • Release 01 CSV/release record: row 125, FBI, PDF, redacted, Late 2025, Western United States.
  • Frontier OCR page text: === Page 1 === / 12/31/99 18:19:06.
  • Open Sky Release 01 semantic graph records for the B21 PDF asset and matching release record.