FBI Photo B20

Evidence media

• Open Sky release-file PDF

The page render shows the official one-page PDF still-image sheet, including the redacted top/side blocks, reticle overlay, and lower-left displayed timestamp.

The extracted image object is the actual 1280 × 960 raster embedded in the PDF. It shows a noisy grayscale frame with a central reticle and one compact dark unresolved mark slightly right of the reticle center, plus additional specks/noise that should not be treated as separate objects without comparison frames.

Investigation reading

FBI Photo B20 is a one-page PDF still-image container in WAR.GOV/PURSUE Release 01. The release record says the FBI submitted a report to AARO consisting of a still image derived from a U.S. military system in 2025. The source record also says the original imagery was altered with redactions before submission to AARO, that no accompanying mission report was provided, and that the operator reported being unable to positively identify the UAP.

This draft treats the file as a still-image evidence item only. It does not resolve what the visible mark is. The release text's narrative description says the monochrome image shows a grainy frame with a central crosshair reticle and “one to two small, dark, objects” just above and to the right of reticle center. Direct visual review supports a narrower public reading: the frame contains one comparatively prominent small dark unresolved feature near the reticle center-right area, plus many smaller specks/noise artifacts across the image. Those marks are not enough by themselves to identify an object, vehicle, artifact, bird, debris, sensor artifact, or any other cause.

The timestamp visible in the image is 12/31/99 18:18:58. The release text warns that the image date is incorrect because the system date/time was not set. The release-record metadata, separate from the visible image timestamp, gives the incident window as Late 2025 and the incident location as Western United States.

What the file appears to contain

The PDF contains one still frame. The embedded image is a 1280 × 960 RGB image displayed as a monochrome/noisy scene with a black top band, side redaction blocks, and a central measurement/crosshair overlay. The frame has a mostly uniform gray background with no clear horizon, terrain, aircraft silhouette, instrument panel, map, or environmental context visible.

Visible page/image elements:

The visual reading separates the official description from what the still itself can support. The official description uses “one to two small, dark, objects.” The visible image supports “one prominent small dark unresolved feature near the center-right reticle area, with additional specks/noise visible.” That distinction is a review lead, not a contradiction or finding.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b20.pdf
• Open released file: war-gov-fbi-photo-b20-bdf033d4
• Agency: FBI
• Release: WAR.GOV/PURSUE Release 01
• Official CSV row: 124
• File type: one-page PDF still-image container
• Verified file size: 577,784 bytes
• SHA-256: d5f7a811de98462378fb4b61beeeb107bd2aa58d32b0a0d3a7788e1457b3593f
• PDF metadata title/subject: B20 FBI Photo
• PDF page count: 1
• Embedded image: 1280 × 960 RGB image
• OCR coverage: one OCR page; extracted text is only 12/31/99 18:18:58

The official WAR.GOV URL is the canonical source pointer. Direct server requests for the official media URL can be access-controlled, so this page relies on the verified Open Sky release-file copy and its matching SHA-256. No mission report, transcript, raw sensor packet, comparison frames, or operator narrative is included in this released PDF.

Graph context

The graph has two exact Release 01 records relevant to this item: the PDF asset record for FBI Photo B20 and the current WAR.GOV release-record row for CSV row 124. The release-record row carries the useful incident metadata: Late 2025, Western United States, FBI, redacted true, and the B20 official PDF link.

The semantic graph currently summarizes this file with 22 extracted claims, 14 entity mentions, 4 sensor-event records, and 0 table rows. Those graph records are navigation context. The sensor-event records come from source wording such as “still image” and “military system”; they are not independent radar tracks, telemetry, multiple sensor returns, or a raw measurement package.

Related graph links point toward adjacent FBI Photo records, including FBI Photo B18 and FBI Photo B23. Treat those as sequence/provenance navigation until each frame is reviewed on its own. One derived manifest-description chunk for this asset surfaces Related CSV rows: 127, while the verified release record and asset inventory for B20 point to row 124. That row mismatch should be cleaned up or explained before any automated cross-page sequence analysis uses it.

Leads to check

• Locate any unredacted or less-redacted source frame, if it is legally releasable, to determine what the black side blocks and top band obscure.
• Compare B20 against adjacent FBI Photo items frame-by-frame, especially neighboring timestamps and CSV rows, without merging their facts prematurely.
• Verify the actual collection time/date from source-system metadata, since the visible 12/31/99 timestamp is explicitly unreliable.
• Look for original mission-report, platform, or operator notes that might explain the sensor mode, pointing geometry, range, weather, and whether the visible mark persisted across frames.
• Compare the prominent center-right dark feature against background noise, compression artifacts, reticle overlay behavior, and any available before/after frames.
• Resolve the graph/provenance mismatch where a derived manifest-description chunk points to row 127 even though B20's verified release row is 124.

Lead check notes

• Blocked — unredacted frame: The released B20 PDF contains one redacted still-image page and no embedded attachments; the less-redacted frame, top-band labels, and side-label content are not present in the public file.
• Partial — adjacent-frame comparison: Current linked context points to neighboring FBI Photo records, including B18 and B23, and B20's verified release record is row 124. Those links are useful for sequence review, but B18/B23 need frame-level review before facts are merged.
• Blocked — collection time and platform context: The visible 12/31/99 18:18:58 timestamp remains unreliable per the release description, and the released file does not include source-system metadata, mission report, platform notes, range, geometry, or weather context.
• Partial — visible mark review: Page/render inspection supports one compact dark unresolved feature slightly right of the reticle center with additional specks/noise. Distinguishing object, noise, compression, redaction/overlay behavior, or sensor artifact requires original/adjacent frames or sensor metadata.
• Partial — row/provenance cleanup: The verified B20 release record and PDF asset point to CSV row 124; one related manifest-description record points toward row 127, which appears to belong to FBI Photo B23 and needs metadata cleanup before sequence analysis relies on it.

Deep investigation — graph + web reconnaissance

Source reread

The released source remains a single encrypted/copy-disabled one-page PDF still-image container, not a mission report or a sensor-data packet. The verified release-file copy is 577,784 bytes with SHA-256 d5f7a811de98462378fb4b61beeeb107bd2aa58d32b0a0d3a7788e1457b3593f; the embedded image inventory shows one RGB 1280 × 960 raster and no embedded attachments. OCR from the PDF contributes only the displayed timestamp, 12/31/99 18:18:58.

The current release CSV row for B20 says FBI supplied a still image from a U.S. military system in 2025, that the imagery was altered with redactions before submission to AARO, that no accompanying mission report was provided, and that the operator could not positively identify the UAP. It also warns that the image date is incorrect because the system date/time was not set. Direct visual review of the embedded raster supports a cautious source-level reading: a heavily redacted grayscale/noisy frame with a central reticle, side/top black masks, the visible timestamp, and one comparatively prominent compact dark unresolved mark slightly right of the reticle center, with many smaller specks/noise artifacts elsewhere. The still does not provide enough visible context to infer identity, size, distance, altitude, speed, motion, or cause.

Graph connections

The graph has an exact B20 asset node matching the official PDF URL and SHA-256, plus the current WAR.GOV release-record row 124. The same source-asset id currently has 22 machine-extracted claims, 14 entity mentions, and 4 sensor-event records; these are marked as machine-extracted context and remain not_a_finding. The sensor-event records are generated from phrases such as still image and military system, not from independent radar, telemetry, multi-sensor track data, or a raw measurement package.

The direct graph neighborhood also exposes provenance-cleanup leads. One current B20-titled release-record node still carries a stale B18 final-file URL, while a B23-titled release-record node carries the B20 final-file URL and byte count. Related-document edges point to B18 and B23, which are useful for sequence navigation only after each still is reviewed on its own. No CANDIDATE_CROSSLINK relationship was found for the B20 source asset during this check.

External provenance and official-source checks

The canonical WAR.GOV PDF, thumbnail, UFO landing page, and both checked CSV URL variants returned 403 from direct official web probes, so the public page continues to rely on the verified Open Sky release-file copy and matching hash rather than live re-downloading the official asset. The Internet Archive availability API reported an archived 200 snapshot for the exact official PDF URL at timestamp 20260515085946; the CDX endpoint was temporarily unavailable during this check. A DVIDS title search returned an empty 202 response, and the WAR.GOV CSV row has blank DVIDS video, video-pairing, and PDF-pairing fields. Defense.gov search access also returned 403. These checks support a narrow provenance posture: B20 is an official WAR.GOV/PURSUE file with a verified local release copy, but no public companion video, mission report, or alternate official case packet was located here.

Prosaic checks, limits, and follow-up

The strongest near-term prosaic checks are image-quality and source-context checks, not astronomy or launch correlation. The visible date is explicitly unreliable, the location is only Western United States, and the released PDF withholds platform, sensor mode, look direction, range, weather, sky background, and adjacent-frame context. That prevents meaningful weather, astronomy, aircraft, balloon, satellite, launch, or range/geometry correlation from this page alone.

Follow-up should prioritize: acquiring any legally releasable less-redacted frame or source-system metadata; verifying the actual collection time and place; comparing B18, B20, and B23 frame-by-frame without merging their facts; checking whether the center-right mark persists before/after the still; and cleaning the B18/B20/B23 row/URL drift in graph records before automated sequence analysis treats the adjacent stills as a coherent event.

Audit note

This section adds graph and web reconnaissance only. It does not create a finding, hypothesis, or resolution decision. The operator non-identification statement, manifest narrative, machine-extracted graph claims, and direct visual read remain separate evidence layers.

Limits

This page is not an identification and not a conclusion. The released file is a single redacted still-image container with minimal OCR text and no accompanying mission report. The image does not provide enough standalone context to determine size, distance, altitude, speed, heading, sensor mode, or cause. The visible reticle suggests an instrument-style overlay, but the released PDF does not provide enough technical metadata to treat the overlay as a calibrated measurement record. Redactions may hide labels that would materially change the reading. The operator's inability to positively identify the UAP is a source statement, not an independent finding by Open Sky.

Sources

• WAR.GOV/PURSUE Release 01 official PDF: FBI Photo B20
• Open Sky release-file endpoint: war-gov-fbi-photo-b20-bdf033d4
• WAR.GOV Release 01 CSV record row 124 for FBI Photo B20.
• Open Sky semantic graph records for FBI Photo B20, used here as context only; this draft keeps review_status: graph_investigation_draft, investigation_status: needs_human_review, and finding_status: not_a_finding.