38_143685_box7_Incident_Summaries_1-100

Evidence media

• Official PDF: Open the verified Release 01 PDF. The Open Sky release-file copy is the 209-page official PDF represented by the SHA-256 value in the provenance section.
• Derived page renders: The images below are page renders from the official PDF for inspection. They are not separate standalone photographs or film frames.

Page 1 render: declassified cover/classification sheet for the incident-summary packet.

Page 50 render: Harmon Field/Newfoundland checklist for Incident #25. The form references Kodachrome film, but this rendered page is a typed checklist, not the film itself.

Page 88 render: Phoenix/Rhodes checklist for Incident #40. The form lists Photos (2), but the page render does not show the photo plates.

Page 101 render: Wilmington continuation page with cone/triangle sketches and green-mist annotations. These are documentary sketches preserved in the packet, not photographs.

Page 156 render: Las Vegas trail/path note with side-view and top-view diagrams.

Page 162 render: Snake River/Twin Falls narrative page with object sketches and witness-note text.

Page 178 render: Boise/Meridian page stating the observer exposed about ten seconds of 8 mm motion-picture film, with a movement diagram. The film itself is not shown in this page render.

Investigation reading

This file is a large packet of early official incident-summary worksheets, not a single sighting case. The PDF reports 209 pages, and the available OCR resolves 209 page markers with text on every page. The pages are raster scans: the direct PDF text layer is effectively empty, while the OCR and rendered page images provide the readable record.

A full packet pass identified 109 checklist or incident-start anchors across the 209 pages. Most entries use a repeated CHECK-LIST - UNIDENTIFIED FLYING OBJECTS form with fields for date, time, location, observer, number of objects, altitude, speed, direction, sound, shape, weather, sketches or photographs, disappearance, and remarks. Many entries are two-page packets: a checklist page followed by a narrative continuation, reliability note, source note, or witness statement. Some incident numbers are duplicated, sublettered, or out of strict page order, so the packet should be treated as a source bundle until child case pages are split out.

Representative rendered-page checks confirm that the file is primarily typed forms and narrative pages. The cover page is a declassified classification/stamp sheet. Pages that mention visual attachments usually contain text references, not the underlying images. Examples: the Harmon Field/Newfoundland checklist cites Kodachrome film; the Phoenix/Rhodes checklist cites Photos (2); and the Boise/Meridian entry says the observer exposed about ten seconds of 8 mm motion-picture film. In the rendered pages checked, those film frames or photographs are not present as standalone image plates. The packet does include visible sketches/diagrams on some pages, including the Wilmington triangular/cone-like light sketches, a Las Vegas side-view/top-view trail diagram, a Snake River/Twin Falls object sketch, and a small Boise/Meridian movement diagram.

What the file appears to contain

The source is a compilation of short sighting summaries and supporting notes from the early flying-disc reporting period, mostly 1947 with several January 1948 entries. It includes ground witnesses, police officers, pilots, aircraft crews, control-tower personnel, military officers, press reports, foreign-source notes, and administrative summaries. The repeated forms preserve reported observations; they do not, by themselves, resolve the nature of the objects or lights described.

Approximate packet map:

Targeted full-document searches found no OCR hit for radar in this PDF. Sensor-like context is therefore mainly visual observation, aircraft/platform context, control towers, field glasses, telescope/binocular references, theodolite/pibal language, and camera/film references. The text does preserve ordinary-sky and prosaic comparison leads throughout: weather balloons, aircraft, stars, meteors, comets, rockets or jet trails, clouds, smoke, reflections, canopies, and atmospheric visibility limits. Those comparisons belong in per-incident follow-up work, not as packet-level conclusions.

High-value anchors for later case splitting include Muroc/Rogers Dry Lake, Portland police reports, United Air Lines/Captain E. J. Smith near Boise/Emmett, Kenneth Arnold/Mt. Rainier, Frank Ryman/Lake City, William Rhodes/Phoenix, Lockbourne, Godman/Mantell, Hamilton Field, Lake Mead, Richmond pibal/theodolite, David Johnson near Boise/Meridian, the White Sands/Las Cruces road report, and the late-December California/Nevada/Oregon luminous-object chain.

Source custody and provenance

• Official/source URL: https://www.war.gov/medialink/ufo/release_1/38_143685_box7_incident_summaries_1-100.pdf
• Open Sky release-file route: war-gov-38-143685-box7-incident-summaries-1-100-b60b84a6
• SHA-256: 13d1805bd1725b38174a328ddf34db564228163768a9082ddd59bca3780fc10e
• File size verified from the release copy: 247,087,612 bytes.
• PDF metadata reports 209 pages; image inventory shows one raster page image per page.
• OCR coverage: 209 pages with text, 231,817 OCR characters, 135 OCR chunks.
• Official CSV row: 28.
• Agency: Department of War.
• Review status: graph_investigation_draft; investigation status: needs_human_review; finding status: not_a_finding.

The official PDF URL is the canonical citation for this page. The Open Sky release-file route is the verified explorer copy, tied back to the same official URL, byte count, and SHA-256 hash.

Graph context

Open Sky currently models this item with two exact document records: the Release 01 CSV/source record and the PDF asset record. The PDF asset is connected to the official Release 01 source and to the text/OCR layer used for packet indexing.

The semantic graph carries this file as a dense source packet, not as one adjudicated event:

• Source-text claim records: 2,412.
• Entity mentions: 525.
• Sensor-event-style records: 44.
• Table-row records: 0.
• OCR chunks: 135; OCR pages: 209.
• Candidate crosslinks currently surfaced for this asset: 0.

The graph records are navigation cues for human review. Many sensor-event extractions are ordinary source references to aircraft, control towers, field glasses, film/camera use, pibal/theodolite observation, or reporting channels. They should not be read as confirmed instrument data, and no radar plot or radar return is visible from this PDF's OCR/source pass.

Leads to check

• Split the bundle into incident-level child pages before using it as evidence for any single case. The PDF contains geographically distinct entries, continuation pages, subreports, and duplicated or sublettered incident numbers.
• Reconcile the incident numbering, especially the Godman/Mantell subreports, Lockbourne/Wilmington cross-references, the duplicated internal numbers, and late-packet incidents that appear out of sequence.
• Locate or rule out the underlying visual attachments referenced in text: Frank Ryman's Lake City/Seattle photograph, Harmon Field/Newfoundland Kodachrome film, William Rhodes/Phoenix photos, David Johnson's 8 mm motion-picture film, the Lakeland photograph, and any Maxwell Field transmittal photo. In the representative rendered pages reviewed here, those referenced photos/films are not present as standalone image evidence.
• Treat visible sketches and diagrams as documentary exhibits to review separately from photographs: Wilmington triangular/cone sketches, Las Vegas trail/path diagrams, Snake River/Twin Falls object sketch, and Boise/Meridian movement diagram.
• Compare named anchors against existing canonical case pages and source collections, including Kenneth Arnold, Mantell/Godman Field, William Rhodes, United Air Lines/Captain E. J. Smith, Muroc/Rogers Dry Lake, Portland-area reports, and early green-fireball/luminous-object chains.
• Run incident-by-incident prosaic checks before escalation: weather-balloon and pibal records, aircraft traffic and base activity, star/planet/meteor possibilities, cloud/smoke/flare/rocket explanations, camera/film artifacts, local weather, and line-of-sight/geography for each date and location.
• Preserve redactions, OCR uncertainties, and missing fields as uncertainty. Several reports have redacted observer details, missing distances, uncertain altitudes, rough coordinates, and narrative-only source channels.

Lead check notes

• Partial — incident-level split: The current wiki has dedicated pages for Kenneth Arnold sighting and Mantell Incident, plus this source-packet page. Dedicated child pages are still needed for several high-value anchors in this packet, including Muroc/Rogers Dry Lake, Portland/United Airlines, Rhodes/Phoenix, Lockbourne/Wilmington, Richmond pibal/theodolite, Snake River/Twin Falls, and Boise/Meridian.
• Partial — numbering/sublettering: The PDF confirms sublettered and continuation-style entries, including Incident #1/#1a/#1c material near the opening pages and cross-reference notes around the Wilmington continuation page. Treat page ranges as working anchors until each incident is reconciled against original enclosures.
• Checked — media references: The rendered pages above verify in-packet references to Kodachrome film, Photos (2), diagrams/sketches, and an 8 mm motion picture camera report. No standalone film strip, photo plate, or separate original enclosure was found in the selected page renders; those remain external/source-file leads.
• Checked — scan/text-layer caution: The packet is a scanned PDF with copy-disabled or sparse text behavior. Page renders are required for sketches, handwritten marks, and form annotations; text extraction alone misses important context.
• Partial — case-context cross-check: The linked Release 01 OCR corpus contains separate references to names and anchors such as Frank Ryman, William Albert Rhodes, Kenneth Arnold, Godman Field/Mantell, and Richmond pibal/theodolite material. This confirms cross-corpus leads, but it does not by itself settle chronology, duplication, or source custody.
• Checked — radar/sensor wording: The packet text reviewed here did not surface radar. Sensor-like leads in the packet are instead form/checklist references such as pibal/theodolite, control-tower observations, aircraft observations, camera/film, and sketches. Broader Release 01 radar mentions belong to other packets and should not be merged into this page without a specific source link.
• Needs external source — prosaic checks: Weather, astronomy, balloon launches, aircraft traffic, local press, and original photo/film custody still require outside-source review on an incident-by-incident basis.

Limits

This is a graph investigation draft, not a human-reviewed finding. The source is a scan-heavy archive packet with copy-disabled/limited text extraction, so OCR can misread names, coordinates, handwritten marks, incident numbers, and marginal notes. The page-range inventory above is a guide to the packet, not a replacement for direct reading of each embedded incident.

Many entries are short summaries, second-hand reporting channels, press items, or condensed military worksheets. Some accounts reference photographs, film, drawings, or other attachments that are not visibly present as standalone artifacts in the reviewed page images. The lack of radar in this PDF's OCR should not be treated as proof that no related radar or sensor records exist elsewhere; it only describes this released PDF packet.

No conclusion is made here about the nature of any object, light, trail, or photograph mentioned in the packet. Each embedded report needs source-custody checking, witness/source comparison, and prosaic-correlation work before promotion beyond needs_human_review.

Deep investigation — graph + web reconnaissance

Source reread

• The verified Release 01 file remains a 209-page scanned PDF packet, not one incident case: 247,087,612 bytes, SHA-256 13d1805bd1725b38174a328ddf34db564228163768a9082ddd59bca3780fc10e, PDF metadata title 38_143685_box7_Incident_Summaries_1-100, and copy-disabled raster-page behavior.
• The available frontier OCR covers 209 page markers and about 231,817 OCR characters. A fresh keyword pass found no radar hit in this packet, while preserving many packet-level prosaic and evidence-custody cues: theodolite, pibal, weather balloon, meteor, star, comet, rocket, aircraft, cloud, smoke, photograph, Kodachrome, film, 8 mm, sketch, control tower, and pilot.
• Representative image rereads confirmed the media posture: page 101 is a typed Wilmington continuation page with embedded triangle/cone sketches and green-mist/red annotations; page 178 is a typed Boise/Meridian narrative with a small movement diagram and a statement that about ten seconds of 8 mm motion-picture film was exposed. Neither checked render is a standalone photograph or film frame.

Graph connections

• Read-only graph checks found the expected official pair for this asset: the Release 01 CSV/source record for row 28 and the PDF asset record for the exact official URL/hash. The asset is linked to the official Release 01 source, 137 text chunks, and one derived secondary Markdown-conversion record; no separate exact-title/hash duplicate was promoted as another case.
• Semantic graph material remains machine-extracted and not_a_finding: 2,412 Claim nodes, 525 EntityMention nodes, and 44 SensorEvent nodes are all marked machine_extracted_needs_human_review. Claim kinds are dominated by observation/witness-testimony, motion, object descriptors, dates, platform text, and prosaic leads.
• The 44 sensor-event-style nodes should be treated as extraction leads, not confirmed instrumentation. Sampled records came from source phrases such as aircraft in a traffic pattern, known-aircraft comparisons, control-tower context, or field/checklist wording. The source reread still found no radar plot or radar-return text in this PDF.
• Existing wiki context already has dedicated pages for Kenneth Arnold sighting and Mantell Incident. This packet also points toward child-page candidates for Muroc/Rogers Dry Lake, Portland/United Air Lines, Frank Ryman/Lake City, William Rhodes/Phoenix, Lockbourne/Wilmington, Richmond pibal/theodolite, Snake River/Twin Falls, White Sands/Las Cruces, and Boise/Meridian.

External provenance and archive context

• Direct WAR.GOV checks for the official PDF, landing page, and CSV returned 403 Forbidden from this environment, which is an access/custody note rather than a contradiction of the verified release copy.
• Internet Archive CDX checks for the exact official PDF URL showed 200 application/pdf captures on 20260508133753 and 20260516080442; the later archived capture had a much smaller recorded length, so it is a versioning/custody lead, not a replacement for the verified 247,087,612-byte release copy.
• An archived WAR.GOV CSV snapshot from 20260512032210 contained the matching row: title 38_143685_box7_Incident_Summaries_1-100, type PDF, agency Department of War, incident date/location N/A, and the same official PDF and thumbnail URLs. The CSV body was served as compressed application/octet-stream, so decompression/parsing is required before row comparison.
• National Archives context page Project BLUE BOOK - Unidentified Flying Objects confirms the broader custody lane for retired Air Force UFO-investigation records, but it does not by itself identify this exact PDF/box/page. FBI Vault's UFO collection is a useful overlap lane for 1947-1954 reporting, especially where packet anchors touch FBI-correspondence cases, but it should be used only after exact page/part matching.
• The graph-linked UFO-USA GitHub Markdown conversion is a derived/secondary OCR lead only. It can help locate text spans, but the official WAR.GOV PDF/CSV and page renders remain the source of record.

Prosaic checks and unresolved work

• Packet-level astronomy, weather, balloon, aircraft, launch, or satellite correlation would be misleading because the file bundles many dates and locations. Those checks need to run incident by incident after child-page splitting and page-number reconciliation.
• Priority follow-ups are to map each incident start/continuation page, reconcile duplicated or sublettered incident numbers, locate any original photo/film enclosures named in the summaries, and pin exact NARA/Project Blue Book/FBI Vault counterpart pages before creating source-backed child cases.
• Until that work is done, this page should stay at source-packet level: it preserves official custody, OCR/search leads, graph extraction coverage, and unresolved evidence-custody questions without resolving any embedded object, light, trail, sketch, photograph, or film reference.

Audit note

This section uses the wiki page, verified release-file metadata, OCR text, representative page renders, read-only graph queries, and official/archive web checks. No graph writes were made, and no finding, hypothesis, or resolution decision is created here.

Sources

• Department of War, PURSUE Release 01, CSV row 28, 38_143685_box7_Incident_Summaries_1-100.
• Official PDF: 38_143685_box7_incident_summaries_1-100.pdf.
• Open Sky verified release-file copy: war-gov-38-143685-box7-incident-summaries-1-100-b60b84a6.
• National Archives: Project BLUE BOOK - Unidentified Flying Objects.
• FBI Vault: UFO.
• Open Sky graph records: Release 01 source record official:doc:war-pursue-uap-release:record:b71585299de962e8 and PDF asset record official:doc:war-pursue-uap-release:asset:38-143685-box7-incident-summaries-1-100-pd:b60b84a66715.