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

FBI Photo B2

Official PDF: FBI Photo B2 release file copy Derived page render from the official PDF:

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

FBI Photo B2

Evidence media

Official PDF page render for FBI Photo B2

The page render shows the released one-page still-image PDF with black redactions, a centered reticle, and the lower-left overlay timestamp. This is a render of the official PDF page, not a separate source image.

  • Extracted embedded raster from the official PDF:

Extracted embedded still-image raster for FBI Photo B2

The extracted raster preserves the same redactions and reticle. A small unresolved dark feature is visible slightly above and to the right of the reticle center; the single public still does not identify it.

Investigation reading

This Release 01 item is a one-page FBI PDF containing a single still-image exhibit. The official release record says the FBI submitted a report to AARO consisting of a still image derived from a U.S. military system in 2025. It also says the original imagery was altered with redactions before submission, no accompanying mission report was provided, and the operator reported they could not positively identify the object.

The release record gives the incident window as Late 2025 and the incident location as Western United States. The image itself displays the overlay timestamp 12/31/99 18:11:27, but the release text says the date in the image is incorrect because the system date/time was not set. For this draft, the overlay timestamp is treated as visible image text only, not as the event date.

The verified released PDF is 583,544 bytes, one page, with SHA-256 e55d5cab5063153c6f2f27314c47b9e4a7f4938f2cefc6bfecf7eb6264b0a07b. The embedded page image is 1280 x 960 pixels. OCR coverage is complete for the one-page file, but the OCR text contains only the timestamp line.

What the file appears to contain

The page image is monochrome and grainy, with a central white crosshair/reticle and a horizontal numbered scale labeled 5, 10, and 15 on both sides of center. A vertical reticle line runs through the center with tick marks. Large black redaction blocks cover the top of the frame and several left/right side areas, obscuring metadata or image content around the frame edges.

The visible scene behind the reticle is low-contrast and noisy. The lower part of the frame has a darker, uneven band or shape that could be terrain, cloud, horizon, or sensor/background structure, but the public still is too degraded and redacted to read confidently. The released narrative describes an indistinct mountain range or cloud formation in the background; the rendered image supports only that an indistinct darker background band is present.

The prominent unresolved feature is a small dark compact dot slightly right of the vertical reticle and above the horizontal reticle line. In visible-position terms, that places it in the upper-right quadrant relative to the reticle, matching the release description. There are also tiny speckles elsewhere in the frame, consistent with image noise or compression/scan artifacts. This draft does not identify the dark dot as an object type; it remains an unresolved feature in a redacted still image.

Source custody and provenance

The custody record available in Release 01 is narrow: it identifies the submitting agency, the AARO submission context, a general late-2025 / Western United States incident frame, and the public PDF. It does not include the original unredacted imagery, sensor export metadata, platform details, operator log, collection geometry, adjacent frames, or mission report.

Graph context

The graph currently preserves two exact document records for this item: the Release 01 row record and the PDF asset record. The semantic layer contains 22 extracted claim records, 14 entity mentions, and 4 sensor-event records. Those entries are useful as navigation aids, but they are mostly derived from repeated manifest and CSV text rather than from a detailed mission packet.

The source-backed claim categories for this item are limited: FBI and AARO as organizations, FBI Photo B2 as document identity, Late 2025 / Western United States from the release row, the operator's statement that they could not positively identify the feature, and the fact that the public evidence is a still image derived from a military system. The sensor-event records should be read carefully: they reflect textual phrases such as still image and military system, not a separate radar track, telemetry record, or instrument readout released with this PDF.

No candidate crosslinks are recorded for this item. Related graph records include nearby FBI photo items, including B17 and B22. One manifest-derived graph quote associated with this context references row 126, while the verified B2 release record and inventory entry are row 123; if those nearby photo relationships are used later, row alignment should be checked before drawing any sequence-level conclusion.

Leads to check

  • Locate the unredacted or less-redacted source image, if it is releasable, so the redacted overlays and masked border fields can be separated from the original scene.
  • Locate the missing mission report, operator log, platform metadata, or AARO submission metadata referenced by the release description.
  • Compare adjacent FBI photo releases from the same apparent still-image series to see whether B2 is part of a sequence, while keeping any row-number mismatch as a provenance cleanup issue.
  • Check whether the unresolved dot remains fixed, moves, changes shape, or disappears in adjacent frames or original video, if such frames exist.
  • Perform prosaic checks only after collection time, location, sensor type, field of view, altitude/azimuth, and environmental context are available; this one redacted still is not enough for identification.

Lead check notes

  • Blocked — The Open Sky release-file copy exposes only the one-page redacted PDF and its embedded still-image raster; the unredacted or less-redacted source frame, mission report, operator log, platform metadata, AARO submission packet, adjacent frames, and original video are not included in this released item.
  • Partial — The rendered page and extracted raster confirm the visible overlay timestamp 12/31/99 18:11:27, but the release description says the system date/time was not set, so the timestamp remains visible image text rather than a verified incident time.
  • Partial — Current graph context links this item to nearby FBI photo records such as B17 and B22, but no candidate crosslinks are recorded. A manifest-derived quote also surfaces row 126 while the verified B2 release row is 123, so any B-series sequence comparison still needs row-aligned source review.
  • Needs external source — Ordinary image explanations and scene reconstruction require collection time, location, sensor type, field of view, platform geometry, environmental data, and adjacent-frame behavior that are not present in the public still-image PDF.

Deep investigation — graph + web reconnaissance

Source reread

The official-primary cached PDF rechecks as the same one-page file already modeled on this page: 583,544 bytes, SHA-256 e55d5cab5063153c6f2f27314c47b9e4a7f4938f2cefc6bfecf7eb6264b0a07b, title/subject FBI Photo B2, and one embedded 1280 x 960 RGB image. OCR contributes only the visible overlay timestamp 12/31/99 18:11:27; it does not add operator notes, coordinates, platform data, or sensor settings.

Visual review of both the PDF render and the extracted embedded raster supports a narrow reading: a monochrome, grainy, heavily redacted still with a centered reticle, horizontal 15 / 10 / 5 tick labels, the unreliable lower-left timestamp, and one small dark compact feature slightly above and right of reticle center. Other small speckles remain image noise or compression/scan artifacts unless adjacent frames or original video show otherwise.

Graph connections

Read-only graph review finds the expected Release 01 PDF asset record and the row-123 release record for FBI Photo B2. The semantic layer attached to the asset remains navigation material, not a finding: 22 machine-extracted claims, 14 entity mentions, and 4 sensor-event records, all marked for human review / not-a-finding. The sensor-event entries are derived from source phrases such as still image and military system; they are not a released radar return, telemetry record, track file, or separate instrument product.

The graph has no CANDIDATE_CROSSLINK records for B2. It does surface nearby B-series provenance links, especially B17 and B22, plus a derived community markdown conversion. Those are sequence/provenance leads only. One cleanup issue remains important: the verified B2 release row is 123, while graph row/URL drift can associate the B2 URL or hash with a row-126/B22 record and can leave stale B17 URL fields on the row-123 record. Exact title, URL, byte size, and SHA-256 should be preferred over row-derived neighbors until that manifest alignment is repaired.

External provenance and custody context

Direct live WAR.GOV probes for the PDF, landing page, current CSV, and thumbnail returned 403 Access Denied from this environment, so the custody basis for this page is the previously cached official-primary PDF plus its hash, the release manifest text, and the public Open Sky release-file copy. Internet Archive availability shows an archived exact-URL PDF snapshot for 20260514084738; that archived PDF renders the same visible B2 frame but is an optimized 122,637-byte PDF with a different file hash. Treat it as an availability/provenance lead, not a replacement for the cached official-primary 583,544-byte hash.

The release row itself states FBI submitted a still image derived from a U.S. military system to AARO, that the imagery had been redacted before submission, that no accompanying mission report was provided, and that the operator could not positively identify the feature. The row's video/DVIDS pairing fields are blank, so no public paired video or DVIDS record is established from this source page alone.

Prosaic checks and open questions

The source does not provide enough event geometry for ordinary correlation work. The visible 12/31/99 timestamp is explicitly unreliable, and Late 2025 / Western United States is too broad for meaningful weather, astronomy, aircraft, launch, satellite, balloon, terrain, or sensor-artifact checks. Candidate mundane lanes therefore remain blocked rather than cleared: sensor/display artifact, compression or scan artifact, dirt/debris, distant aircraft or balloon, bird/insect near the optical path, terrain/cloud contrast, and reticle/overlay masking all require the original source package.

Highest-value follow-up items are the unredacted or less-redacted frame, the missing mission report or AARO submission packet, platform and sensor metadata, field of view and collection geometry, operator notes, and adjacent frames/video showing whether the compact dark feature moves, persists, or is fixed to the sensor/display frame.

Audit note

No finding, hypothesis, or resolution decision is added from this review. The public evidence remains a redacted still-image PDF with provenance and visual-content checks, plus unresolved leads for source-custody cleanup and original-media recovery.

Limits

This page is not a finding and does not resolve the object. The public file is a redacted one-page still-image PDF with no accompanying mission report and no released sensor telemetry beyond the image overlay. The visible timestamp is explicitly unreliable as a collection date according to the release text. The background and small dark feature are too low-resolution and unresolved to support a determination of identity, size, range, speed, altitude, or behavior.

Sources

  • WAR.GOV Release 01 PDF: FBI Photo B2
  • Open Sky Release 01 file endpoint: war-gov-fbi-photo-b2-67ab3ffe
  • WAR.GOV Release 01 CSV manifest record: row 123, title FBI Photo B2, agency FBI, incident date Late 2025, incident location Western United States
  • Open Sky Release 01 graph records for the PDF asset and current release row; graph status remains graph_investigation_draft, needs_human_review, not_a_finding.