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

FBI Photo B12

Official PDF: Open Sky release file copy

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

FBI Photo B12

Evidence media

Official FBI Photo B12 PDF page render

Derived page render from the official one-page PDF. The page shows the redacted monochrome still-image frame with the central reticle, horizontal scale numbers, lower-left timestamp 12/31/99 18:11:12, and the low-contrast background described in the release record.

Embedded image extracted from FBI Photo B12 PDF

Extracted embedded image object from the same official PDF. This view removes the PDF page boundary but preserves the actual frame content: black redaction blocks, reticle/symbology, the unreliable displayed timestamp, dark lower terrain-like background, and the tiny unresolved dark speck above and right of center.

Investigation reading

This draft reads FBI Photo B12 as a one-page still-image PDF, not as a mission report. The Release 01 record says the FBI submitted a report to AARO consisting of a still image derived from a U.S. military system in 2025. The same release text says the original imagery was altered with redactions before submission, that no accompanying mission report was provided, and that the operator reported being unable to positively identify the object.

The Open Sky release-file copy verifies as a 574,722 byte PDF with SHA-256 c440872bb730cae896ce618a3b9d4c4d57553e1910ad218b41c0be01f8801694. The PDF has one page, metadata title/subject B12 FBI Photo, and one embedded RGB image measuring 1280 x 960 pixels. Selectable text is effectively absent; the OCR pass captures only redaction labels, the reticle scale numbers, and the visible timestamp 12/31/99 18:11:12.

What the file appears to contain

The released page is a single monochrome, grainy still frame with no separate caption sheet, report text, map, diagram, table, or attachment visible outside the image itself. The frame contains a bright white central reticle: a vertical line, a horizontal tick-marked scale, and horizontal labels reading approximately 15, 10, 5, 5, 10, and 15 across the center. Several hard-edged black rectangular redactions obscure the upper band and side display areas.

The lower-left overlay shows 12/31/99 18:11:12. That date should not be treated as the incident date: the official release description says the image date is incorrect because the system date/time was not set.

The background is low-contrast and hazy. The lower portion shows darker, uneven terrain- or ridgeline-like shapes, but the public image is too redacted and low-detail to identify exact terrain or location from the frame alone. A tiny dark unresolved feature appears in the upper-right quadrant, above the horizontal reticle and right of the vertical reticle. Visually it is only a small speck or compact blob against the lighter gray background, with no readable structure, motion trail, surface markings, scale, altitude, or range information in the released still.

Source custody and provenance

The source record is best treated as custody for a redacted still frame. It does not include the underlying mission report, platform identity, sensor export, adjacent frames, operator log, range/altitude readout, or original unredacted imagery.

Graph context

The graph has two exact custody records for this item: the B12 PDF asset and the current Release 01 row-115 record. The semantic layer currently carries 23 extracted claim records, 15 entity mentions, 4 sensor-event records, and no table rows. The useful source-backed points are narrow: the file is a still image from a U.S. military system; the operator reportedly could not positively identify the object; the image was redacted before AARO received it; and the visible frame date is unreliable.

The still image and military system sensor-event records are navigation cues from the source language, not four independent sensor tracks or four separate observations. Related graph records point to nearby FBI Photo items such as B1 and B15, but there are no candidate crosslinks on this B12 draft. One semantic description chunk appears to associate B12 text with row 118; the current release metadata and release record place B12 at row 115, while row 118 is FBI Photo B15. Treat that as an indexing cleanup lead, not a content conclusion.

Leads to check

  • Locate the actual collection date/time and any reliable metadata outside the bad 12/31/99 display clock.
  • Determine the platform, sensor type, field of view, reticle meaning, range, altitude, and whether redactions hide telemetry or display fields.
  • Look for an unredacted or less-redacted source frame, adjacent frames, a video sequence, operator log, or mission report.
  • Compare B12 with the official thumbnail and nearby FBI Photo records only as custody/navigation context until source rows and imagery are reviewed item by item.
  • Run ordinary image-quality checks before escalation: sensor blemish, dust/debris, compression/noise, distant aircraft/bird/balloon, terrain contrast, display artifact, or redaction/scan artifact.
  • Clean up the row-number inconsistency between the current B12 row 115 record and the stale row 118 semantic chunk.

Lead check notes

  • Blocked — The actual collection date/time and platform/sensor details are not present in the released PDF. The only visible clock value is 12/31/99 18:11:12, and the release description says that displayed date is incorrect because the system date/time was not set.
  • Blocked — The Open Sky release-file copy exposes one still-image PDF with one embedded image and no embedded attachments; the release description says no accompanying mission report was provided. A less-redacted frame, adjacent frames, video sequence, operator log, sensor export, range, altitude, and reticle/FOV explanation would need an external source.
  • Partial — Nearby FBI Photo records are useful custody context only. Current linked records place B12 among adjacent still-image FBI photo items, and B11/B12 share the same general release-description pattern, but item-by-item source-row and image comparison is still required before treating the series as a sequence or corroborating context.
  • Needs external source — Ordinary image-quality/prosaic checks cannot be completed from the public still alone. Sensor blemish, dust/debris, compression/noise, distant aircraft/bird/balloon, terrain contrast, display artifact, and redaction/scan artifact checks need unredacted imagery, frame sequence, platform geometry, and environment data.
  • Partial — The current Release 01 record places B12 at row 115; one semantic description chunk still associates B12 text with row 118, which corresponds to FBI Photo B15 in the current linked records. That is a provenance/indexing cleanup lead, not a content conclusion.

Deep investigation — graph + web reconnaissance

Source reread

The deep reread confirms B12 as a single still-image PDF, not a mission report or raw sensor package. The official release text says the FBI supplied AARO with a still image derived from a U.S. military system in 2025, that the imagery was redacted before submission, that no accompanying mission report was provided, and that the operator reported being unable to positively identify the UAP. The verified Open Sky release-file copy is 574,722 bytes with SHA-256 c440872bb730cae896ce618a3b9d4c4d57553e1910ad218b41c0be01f8801694.

File-level review matches the existing page summary: the PDF is one encrypted/copy-disabled page with metadata title/subject B12 FBI Photo, one embedded RGB image at 1280 × 960, and no useful selectable text. OCR preserves only redaction labels, the horizontal reticle scale values, and the lower-left timestamp 12/31/99 18:11:12; that displayed date remains unreliable because the release description says the system date/time was not set.

Visual review of the embedded image supports only a cautious scene description: a noisy grayscale frame, a central white reticle and tick-marked horizontal scale, large black redaction bars, a lower-left timestamp overlay, darker low-contrast terrain-like background in the lower frame, and a tiny unresolved dark dot or compact blot slightly right of the vertical reticle and above the horizontal reticle. The redactions, reticle, scale, and timestamp are overlays or release-handling features, not physical scene content.

Graph connections

Neo4j has an exact B12 PDF asset node at the official URL with the matching hash and 574,722 byte length, plus a current Release 01 row 115 record titled FBI Photo B12. It also exposes a custody/indexing drift lead: a nearby current row 118 record titled FBI Photo B15 carries the B12 final URL/body hash through stale manifest-file fields, while the exact B12 asset node remains the stable identifier. That row drift should be treated as graph hygiene, not as a second B12 source or corroborating record.

The semantic layer remains machine-review material: 23 extracted claims, 15 entity mentions, and 4 sensor-event records. The useful claim categories are narrow—document identity, FBI/AARO agency mentions, Late 2025 / Western United States, still-image platform wording, redaction, and the operator's inability to identify the UAP. The four sensor-event records are triggered by source phrases such as still image and military system; they are not four independent tracks, not radar confirmation, and not a released telemetry set. No CANDIDATE_CROSSLINK relationship was returned for the B12 asset during this read-only graph check.

External provenance and web reconnaissance

Direct official WAR.GOV fetches for the B12 PDF, thumbnail, Release 01 CSV, and Release 01 landing page returned Akamai 403 responses during this check. That access result does not invalidate the verified official-primary file already preserved in Open Sky, but it means this page should cite the exact official URL, verified hash/size, and Open Sky release-file endpoint rather than implying a fresh live official download succeeded.

The Internet Archive availability API returned an exact-URL snapshot for the B12 PDF at 20260514084723 with status 200: http://web.archive.org/web/20260514084723/https://www.war.gov/medialink/ufo/release_1/fbi-photo-b12.pdf. That is useful provenance redundancy for the official URL, while the official PDF and Open Sky verified copy remain the source of record. The graph-linked UFO-USA GitHub Markdown conversion is derivative and can help spot OCR/markdown drift, but it should not override the official PDF, release record, page render, or embedded-image review.

Prosaic checks and open questions

The best current ordinary-check lane is image provenance and image quality: single-frame ambiguity, sensor noise, compression, tiny scene specks, display symbology, redaction edges, terrain/background contrast, and possible sensor/display/scan artifacts. Aircraft, balloon, bird, debris, weather, illumination, line-of-sight, satellite, or launch checks cannot be responsibly narrowed from this page alone because the released record gives only Late 2025, Western United States, an unspecified military system, and an unreliable displayed timestamp.

The next source checks are therefore straightforward: recover the true collection date/time, exact location or route, platform and sensor mode, reticle/FOV meaning, range/altitude/look geometry, adjacent frames or video sequence, operator log, and any less-redacted source frame. Until those fields are released, B12 remains a source-backed still-image record with an unresolved visible mark, not an analytical finding.

Audit note

This review used the public wiki page, verified file/OCR/image evidence, read-only graph queries, and official/archive web reconnaissance. No graph writes were made, and this section does not create or imply a Finding, Hypothesis, or ResolutionDecision.

Limits

This page does not identify the unresolved feature and does not assert a finding. The released evidence is one redacted still-image PDF with a visible reticle and timestamp, not a raw sensor package. There is no released motion sequence, no triangulation, no sensor calibration details, no confirmed range/altitude/speed, no weather or astronomy context, and no mission report in the public file. The tiny dark feature is therefore described only as visible but unresolved in the released image.

Sources

  • WAR.GOV / PURSUE Release 01 official file: fbi-photo-b12.pdf
  • Open Sky Release 01 file endpoint: war-gov-fbi-photo-b12-2b947223
  • Release 01 CSV/source record for row 115: FBI Photo B12
  • Verified SHA-256: c440872bb730cae896ce618a3b9d4c4d57553e1910ad218b41c0be01f8801694
  • Frontier OCR page text: redaction labels, reticle scale numbers, and timestamp 12/31/99 18:11:12