DOW-UAP-D159, Air Intelligence Information Report, Germany, 1953
This document is an Air Intelligence Information Report (AIIR), a standardized U.S. Air Force reporting form used to record raw information of potential intelligence value for later analysis. The form served as a primary vehicle for U.S. Air Force field intelligence collection throughout the early Cold War, until defense-wide reporting standards were established in the early 1960s. This AIIR records a series of entries extracted from Tempelhof Airport air traffic control logs dated 10–11 August 1953 concerning aerial reports in the Soviet-occupied zone of Germany. The report states that a British European Airways DC-3 aircraft reported observing what the pilot described as red-colored rockets being fired approximately one mile in front of the aircraft while inbound to Tempelhof via the Center Corridor. It further states that the pilot of a second British European Airways DC-3 later reported a stationary, red-colored light approximately 20 nautical miles west of Genthin at an altitude of approximately 5,000 feet. The report also notes that British Berlin Air Safety Center stated that Soviet authorities had investigated the reported red light and could not account for it. A later Pan American pilot reported no corresponding light or activity when passing through the same area. All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 415 words from pages 1, 2 of 2.
PAGE 1
AIR INTELLIGENCE INF
EXTRACTS FROII AIR TIW'FIC CaffROL LOGS
AREA REPORTED ON FROM (A9'/>cr)
SOVIE!' ZOIE GERWY 73501'H BASE ICOMPLU!N'r SQOlDROI
DATEOF REPORT
PREPARED BY (O}ftctr)
FRED L. ALLEN C.AFT. USAF
AIR TBAn'IC COlfTROLLER
SUMMARY: (lrnler ..,,,;,. •umm•r11 ofr PAGE 2 AF FORM 112-PART II 3
AIR INTELLIGENCE INFORMATION REPORT
FROM (;lgrncv) REFORT NO.
B<1l'E; .A.a of thie report, thie office has been
unable to contact Pan American Airlines Pilot Lesser
to gain any further inforaation.
Capt. USAF
Air Intelligence Officer
LIBRARY SUBJECT -AREA CODES
NOTE: TH IS DOCUMENT CONTAINS INFORMATION AFFECTING THE NATIONAL DEFENSE,OF THE UNITED STATES WITHIN THE MEANING OFTHE ESPIONAGE ACT. SOU. S. C.-
31 AND 32. AS AMENDED. ITS TRANSMISSION OR THE REVELATION OF ITS CONTENTS IN ANY MANNER TO AN UNAUTHORIZED PERSON IS PROHIBITED BY LAW.
IT MAY NOT BE REPRODUCED IN WHOLE OR IN PART. BY OTHER THAN UNITED STATES. AIR F'ORCE AGENCIES, EXCEPT BY PERMISSION OFlHE DIRECTOR OF
INTELLIGENCE, USAF.
Where this file fits in the PURSUE archive
This file is one of DoD's 282 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #165 of 282 by Anomalousness Index. Across the entire 478-file archive it ranks #289 of 478.
That places it in the lower-scoring band of the archive (289 of 478 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 56/100
Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.
🤖 AI-ASSISTED SCORING · methodology
The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.
No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.
Reported by trained U.S. military personnel during an operational mission (8/10/1953) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.
On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.
The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.
Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.
This file was released as open by the Department of War after a formal review process concluded - not simply logged and left pending. That's a stronger disposition signal than 'unresolved, no review': a review actually happened, and remaining open is the Department of War's own published conclusion from it, not an absence of one.
Bottom line on the score: the Anomalousness Index of 56/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.
Related files in DoD
Other PURSUE files in the same category, ranked by Anomalousness Index.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →