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

FBI Photo B3

Open Sky release file copy of the official PDF

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

FBI Photo B3

Evidence media

Derived official PDF page render: FBI Photo B3

Derived page render from the official one-page PDF. The rendered page shows a grainy monochrome still with a central reticle, heavy black redactions, and the visible lower-left timestamp 12/31/99 18:11:34; the release description says the image date is incorrect because the system date/time had not been set. A compact dark unresolved feature appears slightly right of the reticle center, but the released page does not support identification, distance, speed, or motion.

Extracted embedded raster from FBI Photo B3 PDF

Extracted main image object from the same PDF. It preserves the reticle and redaction layout as a raster image object; the page render above remains the best representation of the released PDF page because it includes the visible timestamp and rendered overlay context.

Investigation reading

This Release 01 item is a one-page FBI still-image PDF, not a mission report packet. The verified released file is 167,999 bytes with SHA-256 4a23e128950c1c45cf2f9e32c588088155e63e056d96f09ec94ddaa73ff0cccb. PDF inspection shows one page, an encrypted/copy-disabled PDF container, and embedded JPEG image objects including a main 1338 x 1003 frame plus redaction/overlay components. The stored OCR for the page contains only one readable line: 12/31/99 18:11:34.

The Release 01 record identifies this as FBI Photo B3, CSV row 129, agency FBI, incident window Late 2025, location Western United States, and redacted. The official description says the FBI submitted a still image derived from a U.S. military system to AARO; an accompanying mission report was not provided; the operator reported being unable to positively identify the object; and the visible date in the image is incorrect because the system date/time had not been set.

What the file appears to contain

The rendered page shows a monochrome, grainy still frame with a central white reticle. The reticle has a vertical and horizontal axis with tick marks; the horizontal axis has numeric labels including 15, 10, and 5 on the left and 5, 10, and 15 on the right. The bottom-left timestamp reads 12/31/99 18:11:34, matching the OCR text.

The page is heavily redacted. In the rendered PDF view, a large black horizontal redaction spans most of the upper frame, with additional black redaction rectangles on the left, right, lower-left, and lower-right parts of the image. These redactions remove much of the source context and may cover labels, sensor readouts, or portions of the scene.

The visible background is mostly a mottled gray sensor-like field. The official narrative mentions an indistinct mountain range or cloud formation, but the rendered frame available here does not provide enough visual context to establish a horizon, terrain, scale, distance, or weather. The most notable unresolved feature is a compact dark speck or small dark cluster slightly to the right of the vertical reticle and above or near the horizontal reticle line. It has no clear internal structure in the released image. Other tiny dark specks are also visible in the noisy frame, so this draft treats the central-right mark as an unresolved visual feature rather than an identified object.

Source custody and provenance

The cited source is the official WAR.GOV Release 01 PDF: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b3.pdf. The Open Sky public release-file route is war-gov-fbi-photo-b3-0e3b3ec1. Current byte-range checks against the official media URL return 403 Forbidden, so this page uses the verified Open Sky release-file copy and its matching SHA-256 hash.

The source itself is limited to a still-image container and manifest/release metadata. It does not include the underlying mission report, a video sequence, telemetry, sensor logs, targeting metadata beyond what is visible in the frame, or a statement from the operator beyond the release description that they could not positively identify the object. The visible timestamp should not be read as the incident date because the release description states that the date/time display was not set correctly.

Graph context

The graph has two exact provenance records for this item: the PDF asset record and the Release 01 CSV record. The current exact release record ties B3 to CSV row 129, the FBI, Late 2025, and Western United States. The semantic graph currently reports 22 extracted claims, 14 entity mentions, 4 sensor-event records, and 0 table rows for the asset.

Those graph sensor events are navigation context, not independent corroborating tracks. They are generated from source text such as still image and military system, plus the release description. They do not add a radar return, second sensor stream, motion measurement, or object identification beyond what the released still image and manifest text already provide.

A derived manifest-description chunk in the graph appears to carry a different related-row number than the exact source-pack and release-record context. The verified page and inventory for this asset point to row 129; the row mismatch should be treated as a provenance-cleanup lead before using row-level relationships for B-series comparison. Related B-series records such as FBI Photo B6 and FBI Photo B22 should likewise be used as navigation leads, not as evidence that the same object or event has been established.

Deep investigation — graph + web reconnaissance

Source reread

This item still reads as a single redacted still-image exhibit, not as a mission report or multi-sensor case file. The verified Release 01 PDF is 167,999 bytes with SHA-256 4a23e128950c1c45cf2f9e32c588088155e63e056d96f09ec94ddaa73ff0cccb; PDF metadata labels it FBI Photo B3, shows one encrypted/copy-disabled page, and contains no embedded file attachments. Image-object inspection finds one main 1338 x 1003 RGB image plus seven smaller JPEG objects that line up with redaction/overlay pieces. The only OCR text is the visible timestamp 12/31/99 18:11:34, and the release description says that date/time display was not set correctly.

The page render and extracted raster support a cautious visual description only: a grainy monochrome frame, central reticle and scale ticks, heavy black redactions, and a compact dark unresolved mark slightly right of the vertical reticle and slightly above or near the horizontal reticle line. The visible frame does not establish terrain, horizon, scale, range, speed, motion, weather, platform, sensor model, or object identity. The official narrative's small, dark, circular object wording is a release description, not an analytical conclusion.

Read-only graph connections

Read-only graph checks found two current exact provenance records: the official PDF asset record for https://www.war.gov/medialink/ufo/release_1/fbi-photo-b3.pdf and the Release 01 current-row record at https://www.war.gov/UFO/#release-01-record-129-current-row. The stable source identifiers are the exact URL, title, file size, and full-download SHA-256. The record row preserves FBI, Late 2025, Western United States, redaction TRUE, no DVIDS/video pairing, and CSV row 129.

The semantic graph currently carries three text chunks for the asset context and 22 machine-extracted claims, 14 entity mentions, and 4 sensor-event records. Those entries are useful for navigation but remain machine_extracted_needs_human_review / not_a_finding: the sensor events come from words such as still image and military system, not from an independent radar, infrared track, video sequence, telemetry log, or second sensor stream. No CANDIDATE_CROSSLINK relationships were returned for this asset in the exact-document check.

Graph provenance still has row-drift cleanup leads. The asset's exact source-pack relationship points to row 129, while one manifest-description path stores row 132; direct graph relationships can also surface non-current navigation edges to FBI Photo B6 and FBI Photo B22. Those are B-series comparison and manifest-hygiene leads only, not proof that the same object, frame sequence, or event has been established.

External provenance and official-web checks

Live official WAR.GOV checks for the PDF URL, thumbnail URL, landing page, and current/legacy CSV URLs returned 403 Forbidden during this review. AARO and Defense.gov search probes for the exact title also returned 403, while FBI Vault search pages were reachable and reported 0 items matching exact FBI Photo B3 / fbi-photo-b3 searches. Internet Archive CDX for the exact official PDF URL returned several 200 application/pdf captures on 2026-05-08 and 2026-05-14 with payload lengths around the same 167k-byte range; those captures are useful custody/versioning leads, but the verified Open Sky release-file copy and hash remain the source-of-record for this page until the official server is directly accessible.

No public mission report, less-redacted image, original frame export, operator statement beyond the release description, adjacent frame/video, platform record, or AARO/FBI source package was confirmed in this check. Any outside copy or mirror should be treated as a discovery lead unless it can be matched back to the official URL and hash.

Prosaic checks and limits

The ordinary checks for a still frame remain image-first and source-limited: sensor/display blemish, dust or debris, compression artifact, redaction/overlay artifact, terrain contrast, bird, balloon, aircraft, or other line-of-sight object all remain possible lanes to evaluate, but this released image does not provide the necessary geometry or sequence data. The incorrect timestamp prevents astronomy, weather, satellite, aircraft, and launch correlation from being run responsibly from the visible frame alone; the release record supplies only a broad Late 2025 / Western United States context.

Follow-up leads

  • Recheck the official PDF, thumbnail, and CSV when WAR.GOV access no longer returns 403, then compare bytes and hashes against the verified Release 01 copy.
  • Obtain the AARO/FBI submission packet, mission report, original image export, or adjacent frames/video if released, especially anything that explains the military system, camera settings, date/time error, and redaction process.
  • Compare B3 against adjacent B-series stills only after row and relationship drift are reconciled, looking for reticle alignment, timestamp sequence, redaction pattern, and whether the compact dark mark persists, moves, or disappears.
  • Treat all graph sensor-event and B-series relationship material as review leads until checked against primary source text or imagery.

Audit note

This deep review used the public wiki page, verified release-file bytes/hash, OCR text, rendered page media, extracted image objects, read-only Neo4j context, and official/archive web probes. It adds provenance and checkability, not a finding, hypothesis, or resolution decision.

Leads to check

  • Compare the verified 167,999-byte Release 01 copy with the official server payload if WAR.GOV media access becomes available without 403 responses.
  • Locate any unredacted or less-redacted source still, operator log, mission report, or AARO submission packet that explains the military system, date/time error, and observation context.
  • Compare FBI Photo B3 against adjacent FBI B-series stills for timestamp sequence, reticle alignment, redaction pattern, and whether the compact dark feature persists, moves, or disappears across frames.
  • Resolve the row-number mismatch seen in one derived graph description before treating B3/B6/B22 links as source-custody relationships.
  • Check whether the official thumbnail or any higher-quality released derivative contains more background detail than the PDF render.

Lead check notes

  • Checked — The verified Open Sky release-file copy is a one-page PDF (167,999 bytes; SHA-256 4a23e128950c1c45cf2f9e32c588088155e63e056d96f09ec94ddaa73ff0cccb) with a main RGB image object (1338 x 1003) plus seven smaller JPEG objects that correspond to redaction or overlay pieces; pdfdetach reports 0 embedded files.
  • Checked — The derived page render and extracted main raster now appear in the evidence media section. The rendered page shows black redactions and the visible timestamp 12/31/99 18:11:34; the extracted raster preserves the reticle/redaction image object but does not resolve the compact dark feature.
  • Partial — The visible timestamp is present in the PDF render and OCR, but the release description says the image date is incorrect because the system date/time was not set. The release record supports only the broader incident window Late 2025 and location Western United States.
  • Partial — Current source records place B3 at CSV row 129; a derived manifest-description path can surface row 132, which maps to FBI Photo B6. B3/B6/B22 sequence comparisons remain provenance-cleanup leads until record-level and page-level relationships are reconciled.
  • Blocked — Current checks against the official PDF URL and the likely official thumbnail URL return 403 Forbidden, and the current linked corpus does not expose a higher-quality official derivative. Less-redacted imagery, original frame export, adjacent frames or video, mission report, collection log, platform/sensor geometry, and the AARO/FBI source package remain missing source materials.
  • Needs external source — Sensor blemish, dust or debris, compression/display/redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight checks require unredacted imagery, adjacent frames, exact time/location, collection geometry, or environmental data.

Limits

This page is a graph investigation draft and not a finding. The released source is a single redacted still frame with no accompanying mission report, no released video, no scale reference, no known range, no confirmed object motion, and no independent sensor data. The visible dark mark near the reticle remains unresolved in the released image. The incorrect timestamp, redactions, compression/noise, and lack of scene context prevent reliable identification, distance estimation, speed estimation, or event reconstruction from this file alone.

Sources