FBI Photo B17

Evidence media

• Official PDF / Open Sky release-file view: FBI Photo B17

Derived page render from the official one-page PDF. It shows the released redacted still-image sheet with a large top redaction band, side redaction blocks, central reticle, and the visible lower-left overlay timestamp 12/31/99 18:20:48; the release description says that displayed clock is incorrect because the system date/time was not set.

Extracted embedded image object from the same official PDF. The raster shows the noisy monochrome frame itself, including the central reticle and two small unresolved dark features near the reticle; it does not expose platform, sensor, range, altitude, location, or frame-sequence context.

Investigation reading

FBI Photo B17 is a one-page Release 01 PDF containing a redacted still image. The Release 01 description identifies the submitting agency as FBI and says the item was a still image derived from a U.S. military system in 2025, submitted to AARO after redactions had already been applied. The same release description says no accompanying mission report was provided and that the operator reported being unable to positively identify the UAP.

The file was reviewed as a PDF container and as a rendered image, not only as source-text metadata. The Open Sky release-file copy verifies as 435,400 bytes with SHA-256 60418c8bf9ed18d064ebb7a6e378814ca24438614855b4e626d4375855f57e8d. PDF inspection shows one encrypted/copy-restricted page, page size 640 x 480 points, metadata title/subject B17 FBI Photo, and one embedded RGB image measuring 1280 x 960 pixels. The selectable text layer is effectively empty; the OCR pass captures redaction placeholders and the visible lower-left overlay timestamp 12/31/99 18:20:48.

That displayed timestamp should not be treated as the incident time. The official release description says the date in the image is incorrect because the system date/time was not set. The release-record context available here is broader: Late 2025 and Western United States. The public image does not expose the exact collection date, platform, sensor model, range, altitude, field of view, location, or mission context.

What the file appears to contain

The rendered page shows a grainy monochrome sensor-style frame with a bright white central reticle. A vertical reticle line and a horizontal reticle line cross near the center, with small side tick marks and the number-like 3 marking visible near both ends of the horizontal line. Multiple hard-edged black redaction blocks cover the upper band and several left/right display regions. Those blocks are release/source redactions or overlays, not scene content, and they may hide labels, telemetry, or other source fields.

The lower-left overlay reads 12/31/99 18:20:48. The visible background is mostly noisy gray texture with no clear horizon, terrain, waterline, building, vehicle, person, aircraft, star field, cloud form, or landmark. A rendered high-resolution center crop shows two small unresolved dark oval or circular spots near the reticle: one below-left of the crosshair intersection and a smaller one below-right. Both are soft-edged and indistinct against the noisy background. The official narrative description says two small, dark, circular objects are visible near the center of the frame. The released still alone does not provide enough detail to infer true shape, size, distance, motion, or identity.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/fbi-photo-b17.pdf
• Open released file: war-gov-fbi-photo-b17-f8bd1f11
• Release 01 row currently associated with this page: 120
• Agency: FBI
• Source/container kind: one-page PDF still-image container
• Verified file size: 435,400 bytes
• Verified SHA-256: 60418c8bf9ed18d064ebb7a6e378814ca24438614855b4e626d4375855f57e8d
• Embedded image: one RGB image, 1280 x 960 pixels
• Release-record incident context: Late 2025, Western United States

This file preserves custody for one public, redacted still frame and the official release description. It does not include the underlying mission report, raw sensor package, adjacent frames, operator log, platform identification, collection geometry, environmental context, or unredacted display fields. The official URL remains cited; the Open Sky Release 01 file copy and verified hash identify the public-file copy reviewed for this draft.

Graph context

The graph has exact source records for the B17 PDF asset and a Release 01 record for the same title/URL. The semantic layer currently carries 23 extracted claim records, 15 entity mentions, 4 sensor-event records, and no table rows for this asset. The strongest source-backed points are narrow: this is a still image from a U.S. military system; it was redacted before submission to AARO; no accompanying mission report was provided; the operator reportedly could not positively identify the UAP; and the visible image clock is unreliable.

The sensor-event records are navigation cues triggered by phrases such as still image and military system. They are not four independent sensor tracks and do not represent released radar, telemetry, range, altitude, or multi-sensor corroboration. Related graph records point to nearby FBI B-series photo items, including B14 and B2, but those links are release-neighborhood context unless URL, row, hash, and image-level review establish a stronger relationship.

One manifest-description text chunk for this title surfaces row 123, while the selected release record and source inventory associate B17 with row 120. Treat that as a release-index provenance cleanup lead, not a content conclusion about the image.

Leads to check

• Locate any less-redacted source frame, original image export, adjacent frames, video sequence, operator log, mission report, or AARO submission metadata.
• Verify the actual collection date/time outside the invalid 12/31/99 display clock and the broad Late 2025 release field.
• Identify the platform, sensor type, reticle meaning, field of view, range scale, altitude context, and whether redactions hide telemetry or classification markings.
• Compare B17 with official thumbnails and nearby FBI B-series photo records only after checking each record's row number, URL, hash, and visible frame content item by item.
• Run ordinary image-quality and prosaic checks before escalation: sensor blemish, dust/debris, compression or display artifact, redaction artifact, distant aircraft, bird, balloon, terrain contrast, weather, illumination, and line-of-sight.
• Reconcile the row 120 / row 123 metadata mismatch before using row numbers or related-record links for cross-page analysis.

Lead check notes

• Blocked — The less-redacted source frame, original image export, adjacent frames, video sequence, operator log, mission report, and AARO submission package are not included in the released PDF or current linked release record; those sources are needed before frame-sequence or custody questions can be checked.
• Partial — The visible overlay timestamp 12/31/99 18:20:48 is present in the page render and embedded image, but the official release description says the image date/time is incorrect because the system date/time was not set. The current source-backed incident context remains the broad Late 2025 / Western United States release metadata.
• Partial — PDF inspection supports one embedded RGB image and no embedded attachments. That confirms the public file exposes a single still-image container, not raw video, adjacent frames, or a mission-report annex.
• Partial — B-series and row-number comparison remains a provenance cleanup lead: the selected source inventory associates B17 with row 120, while one manifest-description text chunk surfaces row 123, and related B14/B2 records are only release-neighborhood context until each row, URL, hash, and visible frame is checked item by item.
• Needs external source — Platform, sensor type, reticle meaning, field of view, range scale, altitude/location context, ordinary image-quality checks, weather/illumination, and line-of-sight review all require unredacted imagery, collection geometry, or another authoritative source not present in this public still-image PDF.

Deep investigation — graph + web reconnaissance

Source reread and media review

The source still verifies as a one-page, copy-restricted PDF: 435,400 bytes, SHA-256 60418c8bf9ed18d064ebb7a6e378814ca24438614855b4e626d4375855f57e8d, page size 640 x 480 points, and one embedded RGB image measuring 1280 x 960 pixels. The OCR layer remains sparse: redaction placeholders plus the visible lower-left overlay timestamp 12/31/99 18:20:48. That timestamp is not treated as collection time because the official release description says the image date/time is incorrect due to the system clock not being set.

Visual review of the released page render and embedded raster supports only a narrow description: a noisy monochrome frame with a white central reticle, multiple hard-edged black redaction blocks, number-like 3 markings near the horizontal reticle line, and two small dark unresolved marks near the reticle center. The frame shows no horizon, terrain, waterline, coordinates, range, altitude, sensor mode, platform identifier, or other scene context that would permit scale, distance, speed, or line-of-sight analysis.

Graph connections checked

Read-only graph checks find the expected official PDF asset and the Release 01 row-120 record for FBI Photo B17. The semantic layer for the asset contains 23 machine-extracted claims, 15 entity mentions, 4 sensor-event records, and no table rows. The source-backed text points are limited to the official release description: FBI submitted a still image from a U.S. military system in 2025 to AARO after redaction, no accompanying mission report was provided, the operator reportedly could not positively identify the UAP, and the release metadata gives only the broad Late 2025 / Western United States context.

The four graph SensorEvent records are still-image / military-system extraction cues marked machine_extracted_needs_human_review and not_a_finding; they are not independent radar, telemetry, range, altitude, or multi-sensor corroboration. Direct graph neighbors include the official row record, a secondary UFO-USA markdown conversion derived from the official asset, and row-neighborhood pointers around B14/B2/B17. Those B-series links remain provenance-cleanup leads because stale row/final-URL fields and a row-123 manifest-description reference can point across adjacent FBI Photo records; they do not establish a shared event or image sequence by themselves. No CANDIDATE_CROSSLINK record was returned for this asset.

External provenance and official-source checks

Direct WAR.GOV/PURSUE PDF, thumbnail, landing-page, and CSV probes returned 403 during this check, so the verified Open Sky release-file copy and exact hash remain the usable public copy for review. Internet Archive checks add useful custody context: the exact official PDF URL has a 2026-05-08 14:24:12Z archived PDF response whose raw range reports Content-Range: bytes 0-63/435400, matching the reviewed file size and original WAR.GOV ETag; a later 2026-05-15 08:52:17Z capture reports a smaller 65,683-byte PDF with a different ETag. That looks like an official-media versioning/custody lead, not a content conclusion from this still.

DVIDS returned no usable result body for an exact-title search, and AARO/Defense search probes were blocked by 403. FBI Vault and NARA catalog public search pages loaded, but no static exact-title result was exposed in the fetched page text. No separate mission report, adjacent-frame sequence, operator log, or public AARO case package surfaced in these official/archive checks.

Prosaic checks and open questions

The first prosaic lanes are image-quality and display-context checks: sensor blemish, dust or debris, compression artifact, display/reticle artifact, redaction artifact, distant aircraft, bird, balloon, terrain contrast, illumination, and weather/line-of-sight context. Those checks cannot be resolved from this release alone because the file lacks a valid timestamp, exact location, platform, sensor model, field of view, range scale, altitude, look direction, unredacted display data, and motion sequence. The visible two dark marks should therefore remain documented as unresolved features in a noisy redacted still, not escalated into object identity or performance claims.

Audit note

This section used the official release description, verified PDF bytes/hash, OCR text, rendered/extracted image review, read-only graph context, and official/archive web reconnaissance. It adds no finding, hypothesis, or resolution decision; the next useful work is source-package recovery and row/metadata cleanup before any stronger analytic claim is considered.

Limits

This page does not identify the two dark features and does not assert a finding. The public file is a single redacted still-image PDF, not a full event package. There is no released motion sequence, no platform identity, no confirmed incident timestamp from the visible clock, no raw sensor data, no range or altitude measurement, no weather or astronomy context, and no independent corroborating source in the file. The visible marks are documented only as unresolved features in a noisy, redacted image pending review and additional source material.

Sources

• WAR.GOV / PURSUE Release 01 official PDF: FBI Photo B17
• Open Sky release-file endpoint for the same PDF: war-gov-fbi-photo-b17-f8bd1f11
• Release 01 record metadata used for this page: row 120, FBI, late 2025, Western United States
• Verified file hash: 60418c8bf9ed18d064ebb7a6e378814ca24438614855b4e626d4375855f57e8d
• Source-file review: one-page PDF inspection, rendered-page visual check, center-crop visual check, and Frontier OCR timestamp check