DOW-UAP-D095, Joint U.S.-Canadian Aviation Projects and UFO Sighting Reports, 1954-1955
This file contains reports, memoranda, and correspondence concerning various then-developmental vertical take-off and landing (VTOL) aircraft. The file includes assessments of the experimental potential of the “Avro Project Y2,” a joint U.S.-Canadian near-circular VTOL aircraft that is similar in appearance to contemporary popular descriptions of unidentified flying objects (UFO). A 1954 memorandum opines that VTOL aircraft with a circular planform may be mistaken for UFOs to observers unfamiliar with such technologies. It also recommends that UFO reports in the vicinity of Soviet military operations or assets be re-examined to assess whether they may be attributable to previously unknown advanced VTOL aircraft of foreign design. The file also contains correspondence relating to a UFO incident involving a U.S. Air Force (USAF) KC-97 flying near Newfoundland, Canada in July 1955. A USAF committee found that the characteristics described in the report were inconsistent with those of known Soviet, American, or Canadian military systems. The committee was also “unable to explain the simultaneous ground radar returns and aircrew visual sightings.” It also contains correspondence relating to the potential value of data from incidental radar collection of meteors entering the atmosphere. USAF Air Research and Development Command recommended using that data to improve the performance of the AN/FPS-17 radar system. Finally, the file contains correspondence indicating support for the Communications Instructions for Reporting Vital Intelligence Sightings (CIRVIS) program, a joint U.S.-Canadian civil-military program to standardize reporting methods for unusual or unidentified airborne and maritime hazards and threats.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Where this file fits in the PURSUE archive
This file is one of DoD's 171 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #124 of 171 by Anomalousness Index. Across the entire 334-file archive it ranks #234 of 334.
That places it in the lower-scoring band of the archive (234 of 334 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.
Reported by a witness with no instrumented record. The lowest tier in the rubric's sensor axis. Eyewitness perception in field conditions, even when the witness is highly credentialed, scores below capture by any instrumented modality. This report reached the federal record through the Department of War.
Trained U.S. military personnel reporting from an operational mission context. The second-highest credibility tier in the rubric. This is the witness profile shared by the entire AARO-submitted infrared-capture cluster that anchors the 66-point score band.
Single-witness or single-instrument capture. This is the corroboration tier for the overwhelming majority of the PURSUE archive on the released metadata - the rubric records the honest limit of the underlying record rather than inferring multi-witness corroboration that the released summaries do not establish. A small number of files with an independent second witness or instrument score on the multi-witness/multi-instrument tier above this one.
No kinematic measurements - speed, acceleration, vector - are published in the released file with sufficient precision to score on the kinematic axis. The rubric does not infer kinematic anomaly from narrative observer estimates. Every file in the archive carries this value, which is itself an observation about the disclosure: kinematic-grade telemetry was not part of what was released.
A conventional candidate explanation has been considered but is not dispositive. Every file in the archive scores this way - reflecting that the underlying release metadata systematically caveats strong determinations in either direction. The released summaries warn against reading them as conclusive analytical judgments, and the rubric respects that.
Released as open after formal review by the originating agency. The file passed through a review process and was published in that posture - a stronger disposition signal than 'unresolved with no review,' because review has occurred and the open status is the agency's published conclusion.
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 →