================================================================================ GLITCHY MATRIX EVALUATION FILE Project Blue Book - Incident #1436 ================================================================================ PDF SOURCE: 1952-07-7274433-Kirksville-Missouri-1436-.pdf EVAL GENERATED BY: Claude Sonnet 4.6 for GlitchyMatrix.com/bluebook/ ================================================================================ IMPORTANT NOTE ON FILE CONTENTS: This PDF contains only two document types: a cover sheet and seven radar scope photographs. No witness statements, no ATIC narrative form, no investigator's report, and no Project Blue Book conclusion form appear in this file. The cover sheet explicitly labels the file as "7 photos." Associated narrative documentation, if it exists, is not present in this PDF. All analysis in this eval is therefore based on: (a) physical examination of the seven radar photographs, (b) contextual information about the date, time, and location, and (c) the fact that this case earned an UNIDENTIFIED designation sufficient to be included in the five highest-priority cases in the archive (both UNIDENTIFIED and carrying an official USAF incident number). ================================================================================ SECTION 1: TRANSCRIPTION OF SOURCE DOCUMENTS ================================================================================ --- DOCUMENT 1: COVER SHEET --- File: 1436 Date: July 13, 1952 Location: Kirksville, Missouri Contents: 7 photos --- DOCUMENTS 2-8: SEVEN RADAR SCOPE PHOTOGRAPHS --- FORMAT: All seven images are photographs of a PPI (Plan Position Indicator) radar scope display. PPI format is the standard 360-degree sweep radar presentation: the radar antenna is at the center of the display, range rings radiate outward as concentric circles, and azimuth lines radiate from center like spokes. The rotating antenna sweep causes returns to paint and then fade as the scan continues; photographs capture the phosphor persistence of those returns. All images show a radar scope with what appears to be 8-10 range rings and multiple azimuth/bearing lines. Physical hole-punches appear at the top corners of most frames, indicating these were filed in a binder. VISUAL ASSESSMENT OF THE SEVEN FRAMES: FRAME 1 (top-left, page 1 of photos): Central return: Bright, large white central mass -- typical PPI ground clutter or center lobe return from the radar station itself. Secondary return(s): A distinct, clearly separate bright patch/blob is visible at approximately the 10-11 o'clock azimuth position (NNW bearing), at roughly 3-4 range rings out from center. Several smaller satellite dots are near this return. The return is compact and relatively well-defined -- more consistent with a hard point target than diffuse weather clutter. FRAME 2 (top-right, page 1 of photos): Central return: Bright central mass, similar to Frame 1. Secondary return(s): A return is again visible in the upper-left quadrant, approximately 10 o'clock azimuth, similar range to Frame 1. Appearance slightly less intense than Frame 1, possibly due to scanning angle at moment of photo capture. FRAME 3 (bottom-left, page 1 of photos): Central return: Bright central mass, but notably larger/more diffuse in this frame, with what appears to be a tail or smear extending to the left. Secondary return(s): The secondary target has shifted position -- now visible at approximately 9-10 o'clock, and appears to have multiple components or sub-returns scattered nearby. The smearing of the central return in this frame may indicate antenna motion artifact or possible anomalous propagation bleed-through. FRAME 4 (bottom-right, page 1 of photos): Central return: Bright central mass, smaller and more contained than Frame 3. Secondary return(s): A well-defined bright return at approximately 11 o'clock, farther out from center (approximately 4-5 range rings). The scope overall appears cleaner in this frame with less scatter. FRAME 5 (top-left, page 2 of photos): Central return: Moderate central mass. Secondary return(s): Target appears to have migrated toward 8-9 o'clock (WSW bearing) and is now relatively close to the central area (2-3 rings). Multiple bright spots visible in this quadrant suggesting possible fragmented return or multiple objects in formation. FRAME 6 (top-right, page 2 of photos): Central return: Moderate central mass. Secondary return(s): Return appears again at upper-left (10-11 o'clock), at close range (2-3 rings). This frame shows what appear to be 3-4 distinct bright spots grouped in the upper-left quadrant. FRAME 7 (bottom-center, page 2 of photos -- wider/different aspect ratio): This frame appears to be either from a different scope image or a differently cropped photograph. The PPI grid appears at a slightly different scale. Central return: Bright central mass. Secondary return(s): Returns visible at approximately 11-12 o'clock (N-NNW bearing), at 3-4 range rings. One or two distinct bright spots with some scatter. SUMMARY OF RADAR IMAGE SEQUENCE: The seven frames, taken sequentially, show one or more distinct radar returns that are clearly separate from the central ground clutter mass. Across the frames, the secondary return(s) appear at different azimuth positions and ranges from the center, suggesting: (a) one or more objects moving relative to the radar station, (b) the radar antenna completing multiple sweeps between frames and the target position changing with each sweep, or (c) some combination of target motion and scan artifacts. The returns do not present the typical diffuse blobbing pattern of anomalous propagation (weather-related radar clutter) which tends to cover large arcs of the scope rather than appearing as compact distinct targets. The secondary returns in most frames are compact, bright, and relatively well-defined. Without range-ring calibration data (miles per ring) or bearing calibration it is not possible to determine the exact position, altitude, or speed of the tracked object(s) from photograph examination alone. The companion narrative documentation would contain those specifics. ================================================================================ SECTION 2: SEARCH INDEX TERMS ================================================================================ INCIDENT DATA: incident-1436, project-blue-book, project-sign, project-grudge, unidentified, radar-case, photographic-evidence, radar-photographs, PPI-scope, radar-return, anomalous-radar-return LOCATION: Kirksville, Missouri, northeast-Missouri, Kirksville-Regional-Airport, Adair-County, Missouri DATE / TIME: July-1952, 13-July-1952, 1952, 1952-UFO-flap, summer-1952, July-flap EVIDENCE TYPE: radar-scope-photographs, PPI-photographs, photographic-evidence, 7-photos, physical-evidence, instrument-record, non-visual-case RADAR CHARACTERISTICS: PPI-scope, ground-clutter, anomalous-return, moving-target, hard-return, multiple-frames, sequential-photography, point-target, compact-return, not-anomalous-propagation CONTEXT: 1952-UFO-wave, 1952-flap, Washington-DC-radar-1952, summer-flap, Ruppelt-era, radar-visual-correlation, Cold-War-air-defense, US-air-defense-radar-network, temperature-inversion OUTCOME: officially-unidentified, radar-only-case, no-narrative-in-file, physical-instrument-evidence, photographic-documentation ================================================================================ SECTION 3: GM ANALYSIS ================================================================================ -- Glitch N. Matrix | GlitchyMatrix.com | AI Assessment -- -- Claude Sonnet 4.6 | Project Blue Book Archive Evaluation -- ================================================================================ CASE OVERVIEW: On 13 July 1952, at an unspecified time of day (narrative documentation not present in this file), a radar installation in or near Kirksville, Missouri tracked one or more anomalous returns and photographed the radar scope. Seven photographs survive. That is the complete documentary record available in this PDF. Kirksville is a small city in northeastern Missouri, home to Kirksville Regional Airport (KIKV). In 1952 it was also in the coverage zone of the expanding US military air defense radar network. The precise identity of the radar installation depicted in the seven photographs is not stated in this file. The case sits at the intersection of two facts: it has a formal USAF incident number, and it was classified UNIDENTIFIED. Of the 10,808 cases in the archive, only a small handful carry both designations. This one does. It arrived in the Blue Book files with no accompanying visual sighting report -- just seven photographs of a radar scope catching something it could not identify. THE 1952 CONTEXT -- CRITICAL TO UNDERSTANDING THIS CASE: July 1952 is not a random month. It is the peak of the most intense and well-documented UFO flap in American history. July 19-20, 1952: Unknown returns appeared on radar at Washington National Airport and Andrews AFB simultaneously. Air Defense Command scrambled F-94 interceptors. The returns disappeared when jets approached and reappeared when jets left. July 26-27, 1952: The Washington DC incidents repeated, with even stronger radar confirmation. Multiple radar operators at National Airport, Andrews AFB, and Bolling AFB all tracked the same returns simultaneously. Additional visual observations from airline pilots confirmed lights in the same locations as the radar targets. Air Force Chief of Staff General Hoyt Vandenberg received a personal briefing. The incident triggered the largest peacetime press conference at the Pentagon since World War II. The Kirksville, Missouri incident on July 13, 1952 occurs six days before the first Washington DC radar event -- in the same building wave of activity. This is not coincidence of date; this is the documented national context in which radar operators across the country were encountering, photographing, and reporting anomalous returns. Edward Ruppelt, who commanded Project Blue Book during this period, described the summer of 1952 as the period when "the Air Force was publicly worried." The volume of credible reports -- many from military radar operators and trained airline pilots -- was creating serious analytical difficulty. The Kirksville photographs were taken and preserved as physical evidence during exactly this national crisis period. WHAT RADAR EVIDENCE MEANS: Visual sightings are subject to human perceptual error, atmospheric optical effects, misidentification of known objects, and psychological factors. Radar returns are not. A PPI radar return represents a physical echo: a transmitted radio-frequency pulse that left the antenna, struck a solid or semi-solid object, and returned to the receiver. The object has a measurable radar cross-section (RCS). The physics are documented and calibrated. The scope does not hallucinate. The scope does not get excited by newspaper stories. If a return is on the scope, something is physically there. The debate is always about what it is -- but the reality of a return is not in question. This is why radar cases are epistemically different from visual-only cases. WHAT THE PHOTOGRAPHS SHOW: Seven sequential frames of a PPI scope, each showing: 1. Normal central ground-clutter return (bright white mass at center) 2. One or more secondary returns clearly separated from the central mass The secondary returns in these frames are relatively compact and bright -- characteristics more consistent with a hard target (aircraft, large metallic object) than with weather phenomena. Anomalous propagation (temperature inversion ducting) typically presents as large diffuse clutter that covers substantial arcs of the scope. The Kirksville returns appear more point-like than clutter-like, though this assessment is limited by the resolution of 70-year-old photographic copies. Across the seven frames, the position of the secondary return(s) relative to center changes -- appearing at different azimuths and ranges. This is consistent with a moving target being captured at different points in the antenna rotation cycle. The movement also appears to place the target at different azimuths in different frames, suggesting either significant speed or direction change between frames. THE ANOMALOUS PROPAGATION QUESTION: Summer 1952 was also characterized by strong temperature inversions across the central United States, and anomalous propagation (AP) was the standard debunk offered for the Washington DC radar incidents. Under AP conditions, radar beams that normally propagate in a straight line bend back toward the ground due to temperature/humidity inversions, causing ground returns to appear on scope at distances and azimuths that would normally be beyond radar horizon. AP returns can appear, disappear, and move. However, AP typically produces: - Large diffuse areas of clutter covering many degrees of azimuth - Returns that track at ground level (apparent speeds follow terrain) - Enhancement of known ground targets (buildings, highways, terrain features) - Gradual appearance and dissipation correlated with inversion layer changes What the Kirksville frames show does not appear to be classic AP. The returns are compact and discrete. Without the narrative documentation we cannot know whether the radar operators observed any characteristics (apparent speed, altitude data from height-finder radar, simultaneous visual confirmation, or correlation with atmospheric sounding data) that would confirm or deny AP. The Washington DC events of July 19-20 and 26-27 were ultimately attributed by the Air Force to AP -- a conclusion that many radar experts then and since have disputed as physically implausible given the specific tracking behavior observed. The Kirksville case may be subject to the same debate, but that debate cannot be resolved from photographs alone. WHAT THE MISSING DOCUMENTATION PROBABLY CONTAINED: For a case to receive a formal USAF incident number and UNIDENTIFIED classification, some level of investigation and documentation was required beyond the radar photographs themselves. The companion narrative -- which is not in this PDF -- almost certainly contained: 1. Radar operator statements (who was on duty, what they observed) 2. The specific radar type and range calibration (miles per ring) 3. The time and duration of the tracked returns 4. Whether ground observers were alerted 5. Whether interceptors were scrambled or contacted 6. Whether weather radar or atmospheric soundings were checked for AP conditions 7. The formal ATIC analysis and final conclusion language The fact that after all that documentation and analysis, the case retained UNIDENTIFIED status is the most important single fact this file contains. If AP had explained it, the conclusion would read "ASTRONOMICAL" or "OTHER" or simply a weather cause. If a conventional aircraft had been identified, the case would have closed. UNIDENTIFIED means the physical record -- seven photographs of an anomalous radar return -- was examined by trained analysts and found to have no satisfactory explanation. WHAT THE OFFICIAL CONCLUSION GOT RIGHT AND WHAT WAS MISSED: Without the narrative, it is not possible to assess the full investigation. However, the UNIDENTIFIED classification in a radar case during the summer 1952 flap represents a particularly significant determination -- precisely because this was the period when the Air Force was under enormous pressure to explain anomalous radar returns as AP. The fact that this case survived that pressure and remained UNIDENTIFIED suggests the returns were sufficiently anomalous to resist the AP explanation. The missing narrative is a genuine gap. The photographs alone cannot tell us speed, altitude, track, or duration. They can tell us that something real was on the scope, that it was distinct from ground clutter, that it appeared to move across multiple frames, and that seven photographs were taken as evidence -- indicating the radar operators took what they were seeing seriously enough to document it photographically. WHAT MAKES THIS CASE NOTABLE: 1. INSTRUMENT-ONLY EVIDENCE: No visual sighting in the available documentation. No witness to discredit. No perceptual ambiguity. Just a radar scope and seven photographs of an anomalous return. 2. JULY 1952 CONTEXT: This case occurs during the most documented UFO flap in American history, six days before the first Washington DC radar incident, in the same midwestern air corridor. It is part of a national pattern of anomalous radar activity in the summer of 1952. 3. PHOTOGRAPHIC DOCUMENTATION: Seven sequential photographs represent active tracking, not a single momentary anomaly. Someone at the radar site was watching this return long enough to photograph it seven times. That implies a sustained, trackable anomaly -- not a scan artifact. 4. RETAINED UNIDENTIFIED STATUS: During an era when the Air Force was actively trying to reduce the UNIDENTIFIED count and was under both internal and public pressure to explain the 1952 flap, this case held its UNIDENTIFIED classification through final analysis. Whatever the Air Force analysts saw in these photographs and the associated narrative, they could not explain it. 5. PHYSICAL EVIDENCE THAT SURVIVES: These seven photographs are physical evidence of an anomalous radar return. The scope does not lie. In a field dominated by eyewitness accounts, this case offers something different: instrument data, preserved, on file, still unanswered. BOTTOM LINE: Incident #1436 is a radar-only case -- the most physically grounded category of UFO evidence. Something real appeared on a radar scope in Kirksville, Missouri on 13 July 1952. It appeared for long enough that seven photographs were taken. It appeared during the peak of the 1952 UFO flap, six days before the Washington DC radar incidents that would trigger a Pentagon press conference. It was analyzed by Project Blue Book at the height of the Ruppelt era, when the program was arguably at its most rigorous. And it was classified UNIDENTIFIED. The absence of the companion narrative is a genuine limitation on what this evaluation can determine. But the photographs themselves carry a simple message: the object was physically real, it was tracked on calibrated instruments, and nobody could tell you what it was. That is, and remains, the definition of unidentified. ================================================================================ END OF EVALUATION GlitchyMatrix.com/bluebook/ | Project Blue Book Archive ================================================================================