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

FBI Photo B1

Official Release 01 PDF: Open Sky release file copy · official WAR.GOV PDF

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

FBI Photo B1

Evidence media

Derived official PDF page render for FBI Photo B1

Derived render of the one-page official PDF. The page contains a redacted monochrome still image with a central reticle and the visible but source-disclaimed timestamp 12/31/99 18:11:19.

Extracted embedded raster from the FBI Photo B1 PDF

Extracted raster from the official PDF image object. The small dark mark slightly above and right of the reticle center remains unresolved in this public release image; the surrounding redactions and missing collection metadata prevent scene or object identification from this frame alone.

Investigation reading

This Release 01 item is a one-page FBI PDF containing a redacted still image, not a mission report packet. The official release record describes it as a still image derived from a U.S. military system and submitted by the Federal Bureau of Investigation to AARO. The release description says the original imagery was altered with redactions before submission, that no accompanying mission report was provided, and that the operator reported they could not positively identify the object.

The Open Sky release-file copy was checked against release metadata: 613116 bytes, SHA-256 6c47098b047b4cce59129072df1a7eeb5b6602da7ef209fa9dc1299e13622199, one PDF page, and one embedded RGB image at 1280 x 960. The visible page has no selectable body text; the OCR layer only preserves redaction placeholders and the burned-in timestamp 12/31/99 18:11:19. The official description states that the displayed date is incorrect because the source system date/time was not set, so that timestamp should not be treated as the incident date.

What the file appears to contain

The visible source image is monochrome and grainy, with multiple black redaction bars obscuring parts of the top, side, and lower portions of the display. A white reticle is visible near the center, with horizontal and vertical tick marks and numeric labels such as 5, 10, and 15 along the horizontal scale. The lower-left corner contains the timestamp 12/31/99 18:11:19.

A small dark unresolved feature is visible slightly right of the vertical reticle line and above the horizontal reticle line. In the reviewed render, it appears as a tiny compact dark speck against a noisy gray background. A few other faint dark specks are present elsewhere, but they are not reliably separable from image noise or display/compression artifacts. The official narrative describes a small dark circular object in the upper-right quadrant near the center of the frame, with a background that may show an indistinct mountain range or cloud formation. The visual pass supports the presence of a small dark unresolved feature, but the background remains too indistinct on this released image to classify as terrain, cloud, or another scene element.

No caption, coordinates, platform label, altitude/speed field, map, radar plot, track history, operator note, or separate sensor readout is visible in the released page. The page also does not include the underlying mission report that would normally supply collection geometry, sensor mode, platform, weather, range, timestamp correction, or follow-up identification work.

Source custody and provenance

The source-custody issue to keep front and center is that the released image is already redacted and detached from its mission report. The public file can support a provenance claim that an official Release 01 PDF exists and contains the image described above; it cannot by itself establish the original collection context or identify the unresolved feature.

Graph context

The graph currently has the PDF asset and the corresponding WAR.GOV release-record node for this item. The semantic extraction attached to the asset is narrow: 23 extracted claims, 15 entity mentions, 4 sensor-event records, and no table rows. Those records mainly reflect the official manifest language: FBI, AARO, still image, U.S. military system, the operator's inability to positively identify the object, redactions, Late 2025, and Western United States.

The sensor-event records should be read as navigation cues, not as independent raw instrument evidence. They are derived from release-description terms such as still image and military system; the PDF itself does not show a radar return, telemetry table, track file, or sensor-mode page. The graph also links this item near other FBI photo items, including related B-series still-image records. Those relationships are useful for batch comparison, but they are not corroboration of this specific frame.

Leads to check

  • Locate any unredacted or less-redacted source imagery, if officially available, and compare it with this released PDF.
  • Find the missing mission report or collection log that would establish platform, sensor mode, corrected time, range, pointing angle, weather, and follow-up identification notes.
  • Compare FBI Photo B1 with the adjacent FBI Photo B-series images to determine whether they are sequential frames, alternate crops, or separate stills from the same collection event.
  • Confirm how the official release row, thumbnail, and PDF metadata were generated, especially because the visible timestamp is explicitly unreliable.
  • Check whether the indistinct background described in the release record can be matched to terrain/cloud context only after the unredacted scene or collection metadata is available.

Lead check notes

  • Blocked — unredacted source image: The Open Sky release-file copy matches the official PDF hash and exposes one redacted 1280 x 960 embedded image. No unredacted or less-redacted B1 image is present in the current Release 01 file.
  • Blocked — missing mission report or collection log: The release record states that no accompanying mission report was provided. The PDF has no embedded attachments and no visible sensor/platform fields beyond the reticle overlay and source-disclaimed timestamp, so platform, sensor mode, corrected time, range, pointing geometry, weather, and follow-up identification notes need an external official source or later supplement.
  • Partial — B-series comparison: Current Release 01 metadata includes FBI Photo B1 through B24 as separate one-page PDF assets, and available graph context links B1 near other FBI photo items. That confirms a comparison set, but it does not establish whether the B-series images are sequential frames, alternate crops, or separate stills from the same collection event.
  • Checked — visible timestamp and background: The image shows 12/31/99 18:11:19, but the release description says the date is incorrect because the source system date/time was not set. The background remains too indistinct and redacted to match to terrain or cloud context without unredacted imagery or collection geometry.

Limits

This page does not identify the feature, classify it, or resolve the report. The released file is a single redacted still image with no accompanying mission report, no readable collection metadata beyond the visible reticle/timestamp, and no raw sensor packet. The tiny dark feature is visually real in the released frame, but it remains unresolved at the image quality available here. Redactions may hide important context, and the timestamp visible in the image is not reliable as an incident time.

Deep investigation — graph + web reconnaissance

Source reread

A fresh source pass keeps this item in the still-image lane. The release-file copy is a one-page, copy-restricted PDF (613116 bytes, SHA-256 6c47098b047b4cce59129072df1a7eeb5b6602da7ef209fa9dc1299e13622199) whose page is a single embedded 1280 x 960 RGB raster inside a 640 x 480 point PDF page. The PDF metadata title/subject is FBI Photo B1; the OCR text does not add narrative content beyond redaction placeholders and the visible timestamp 12/31/99 18:11:19.

Visual review of the page render and extracted raster confirms that the public file shows a noisy grayscale display frame, a central reticle with tick marks and horizontal 5/10/15 labels, multiple black redaction blocks, and a small dark unresolved mark slightly above and right of the reticle center. The render does not add a caption, coordinates, platform label, sensor mode, range, altitude, or track information around the image. The official release text says the displayed date is incorrect because the system date/time was not set, so the burned-in timestamp is useful only as a visible image feature, not as collection time.

Graph connections and custody checks

Read-only graph review finds one stable exact asset node for the B1 PDF by URL and SHA-256, with three text chunks: the linked-PDF manifest text, the official manifest-description text, and the frontier OCR chunk. The semantic layer contains 23 machine-extracted claims, 15 entity mentions, and 4 sensor-event records for this source asset. Those claims mostly restate the manifest language: FBI/AARO custody, still image from a U.S. military system, redaction before submission, no accompanying mission report, Late 2025, Western United States, and the operator's report that the UAP was not positively identified.

The SensorEvent records should remain machine_extracted_needs_human_review. Their modalities are STILL IMAGE or unknown, derived from words like still image and military system; they are not independent radar, telemetry, track, or multi-sensor evidence. No CANDIDATE_CROSSLINK relationships were found for the exact B1 asset. Direct graph relationships do show a secondary UFO-USA markdown conversion and nearby manifest-row drift: the stable B1 asset is related to a current row-112 B1 release record, while another non-current row relationship associates the B1 PDF URL with a B12-titled record. That is a provenance/index-cleanup lead, not corroboration and not a separate event.

External provenance and official-source reconnaissance

The source of record remains the official WAR.GOV/PURSUE Release 01 PDF and release manifest entry for FBI Photo B1. Live official probes for the PDF, thumbnail, Release 01 CSV, and WAR.GOV landing page returned Akamai 403 responses during this check, so the live site could not be used to refresh the file directly. That is not a content blocker because the archived Open Sky release-file copy still matches the expected byte count, SHA-256, PDF structure, and OCR/render evidence. Internet Archive availability/CDX probes for the exact PDF URL were rate-limited or unavailable during this pass, so they remain a follow-up custody check rather than a citation.

A local mirrored CSV row for B1 preserves the same core description: FBI submission to AARO, a still image derived from a U.S. military system in 2025, altered/redacted imagery, no mission report, the operator unable to positively identify the UAP, the bad system date/time, and a narrative note describing a small dark circular object near the upper-right/near-center portion of the frame. That mirrored row is useful for comparison, but the official PDF URL plus hash remain the stronger identity anchor.

Prosaic checks and unresolved limits

No meaningful astronomy, weather, launch, satellite, aircraft, or balloon correlation can be run from this public file alone because the exact collection time, corrected date, location, sensor platform, look direction, field of view, range, and environmental context are absent or redacted. The ordinary prosaic lanes therefore stay image-centered: sensor/display noise, compression artifacts, dust or debris on optics, distant aircraft/bird/balloon, terrain or cloud contrast, and redaction/scan-generation artifacts. A single redacted still frame cannot establish motion, speed, acceleration, altitude, size, distance, or object class.

The current public evidence supports only a cautious statement that a small dark unresolved mark is visible in the released image. It does not resolve whether that mark is an external object, image artifact, sensor/display artifact, or ordinary aerial/scene feature.

Follow-up leads

  • Locate any official unredacted or less-redacted B1 image, original raster export, thumbnail lineage, adjacent frames, or video segment.
  • Locate the missing mission report, operator log, AARO submission packet, platform/sensor metadata, corrected timestamp, and collection geometry.
  • Reconcile the B1/B12 row-link drift in the graph and manifest-description chunks using exact URL/hash/title as the primary identifiers.
  • Compare B1 against adjacent B-series images only after row alignment, timestamps, and source-frame sequence are verified.
  • Re-run official WAR.GOV, Internet Archive, FBI/AARO/Defense, and any future PURSUE supplement checks for exact B1 URL/hash custody, not broad title-only matches.

Audit note

This section adds source reread, graph-context, and external-reconnaissance detail only. It does not create a finding, hypothesis, or resolution decision. Machine-extracted claims remain unreviewed unless they are independently verified against the source text or image.

Sources

  • Official Release 01 PDF: FBI Photo B1
  • Open Sky release-file copy: war-gov-fbi-photo-b1-1e63919c
  • WAR.GOV Release 01 CSV row 112 / FBI Photo B1 release record
  • Open Sky semantic graph context for the Release 01 PDF asset and release-record node