Skip to content

Myth versus document · 100 entries

Claim ledger

Not cases — individual sentences. Each with its origin, source tier, verification status, and what exactly would settle it.

This page cuts both ways. It dismantles legends grown around strong cases — and defends cases that were discarded along with the legends.

RefutedT5Common framing; put to Fravor in 2023 as “this floating Tic Tac video that you engaged with on November 14th, 2004” (printed hearing, p. 41)

“The FLIR1 video shows Fravor’s encounter with the Tic Tac.”

Fravor’s own testimony puts the video on a later flight. After the encounter, “We returned to Nimitz. We were taking off our gear. We were talking to one of my crews, who was getting ready to launch. We mentioned it to him, and they went out and luckily got the video that you see, that 90-second video.” (printed hearing, p. 14) No document we can open establishes that the object on FLIR1 is the one Fravor saw; the Navy slides that set video frames beside the case do not say when the frames were recorded or what the camera was pointed at. See the case.

What would settle it

Nothing for the claim itself: the pilot’s own testimony puts the video on a later sortie. Whether it shows the same object would take the time-stamped records of both sorties.

RefutedT5Internet narrative and popular science media

“The Tic Tac entered the ocean.”

Under oath in 2023, Fravor said they saw whitewater, not an object in the water. Asked by Rep. Burchett, “do you believe that you witnessed an additional object under the water in relation to your encounter?”, he answered: “I will say we did not see an object. There was something there to cause the whitewater and when we turned around it was gone. So, there was something there that obviously moved.” (printed hearing, p. 21) The object he did see, by his account, “began to climb” and then “rapidly accelerated in front of us and disappeared” (p. 13). See the case.

What would settle it

Nothing: the only witness whose account can be opened describes whitewater, not an object entering the water.

RefutedT4COMETA, “UFOs and Defense: What Should We Prepare For?” (1999), section 2.2, p. 18: “Utah and the onboard radar that had just detected the object”

“The RB-47 tracked the object on three independent radars at once.”

The 1957 records do not bear it out. The aircraft commander’s data sheet of 10 September 1957 asks “Was an attempt to detect the object on airborne radar made?”; he circled “Yes” and wrote “UNSUCCESSFUL” (Project Blue Book, NAID 28970538, image 45). What followed the signal was ECM operator No. 2’s direction finder; as McDonald put it in 1971, “the DF receivers are not radars” (image 15). On the ground, the wing’s message has site “Utah” confirm the object on its scopes (image 43), while the message of the radar squadron at Duncanville, sent the same day, reports “NEGATIVE CONTACT WITH OBJECT” (image 4), and Blue Book’s card says the object “could not be seen by ground radar” (image 1). The same card says it “was picked up by B-47 radar”, against the commander’s own answer. COMETA builds its account on what the crew told McDonald twelve years later: “The six officers were questioned by MacDonald in 1969.” (p. 18) See the case.

What would settle it

The records of site “Utah” for that night; they are not in the Blue Book file.

RefutedT4Claims by those who submitted the material for analysis

“The magnesium-bismuth sample is a fragment of extraterrestrial technology.”

The material was tested. Results indicated a terrestrial alloy, and subsequent laboratory analysis assessed it as consistent with ordinary alloy used in industrial applications. No properties beyond known metallurgy were found.

What would settle it

Nothing — the matter was investigated and closed.

RefutedT5Interpretation of released programme documents

“The KONA BLUE programme held biological material of non-human origin.”

KONA BLUE existed as a *proposed* programme. It was never formally approved, never funded, and never received any material. The existence of a document describing a proposed programme is not evidence that the programme operated.

What would settle it

Nothing — the decision record is unambiguous.

RefutedT2AARO’s case resolution of 2025, quoting the report: “Object Altitude (reported): Near ocean’s surface”

“GOFAST shows an object racing just above the ocean surface.”

AARO assessed in February 2025 that the object flew about 13,000 feet above the sea and showed “no anomalous performance characteristics”. The altitude follows from the numbers on the display alone, the sensor angles and the range to the target; AARO calls it a high-confidence result. The speed does not: AARO gives 72 to 161 mph depending on the object’s heading relative to the wind, because “The aircraft’s exact location and heading (compass direction) during the recording are unknown.”, while NASA’s study team, neglecting the wind, found about 40 mph, “a typical wind speed at 13,000 feet” (p. 28). Both attribute the impression of speed to parallax, and AARO adds that it “cannot definitively identify the object”. See the case.

What would settle it

Nothing for the altitude, which AARO derives from the display alone. A single speed and heading would need the aircraft’s position and heading, which AARO says are unknown, or the original file, whose metadata it says are “no longer available”.

Cases

GOFAST

RefutedT5The standard reading of the Customs and Border Protection IR video

“The Aguadilla video shows an object entering the ocean and splitting in two.”

A 3D trajectory reconstruction established that the objects did not enter the water and did not split, and that they moved at roughly wind speed. The ‘water entry’ is an object passing behind a shoreline viewed at a shallow angle; the ‘split’ is two objects present throughout, momentarily unresolvable at the sensor’s resolution.

What would settle it

Nothing — the analysis has been performed and published.

RefutedT5The standard reading of the night-vision recording

“The USS Russell video shows pyramid-shaped craft.”

In 2022 the Deputy Director of Naval Intelligence showed a House intelligence subcommittee a Navy video of “what appears to be triangles, some flashing” and said: “The triangular appearance is a result of light passing through the night vision goggles and then being recorded by an SLR camera.” (transcript, p. 16) Asked whether the triangles were drones seen through the goggles, he answered: “Some type of drone, some type of unmanned aerial system, and it is simply that that light source resolves itself through the night vision goggles onto the SLR camera as a triangle.” (p. 29) He named neither the ship nor the date, and no document we can open ties his video to USS Russell. This base no longer holds the case the claim belonged to (see the withdrawn entry).

What would settle it

Nothing for the shape. Asked whether the effect had been reproduced by flying a drone and observing it with the same equipment, Bray answered: “The UAP Task Force is aware of studies that have done that.” (p. 29) Which ship and which night the video comes from would take a Navy record that names them.

RefutedT5The Tacoma press and anonymous telephone calls, August 1947, as the FBI recorded them (FBI file 62-HQ-83894: Portland teletype of 5 August, Section 1, p. 141; Seattle letter of 18–19 August, Section 3, pp. 36–40)

“The B-25 that crashed near Kelso was carrying flying-disc fragments from Maury Island and was brought down so they could not be examined.”

Intelligence officers at McChord Field told the FBI that “THERE IS NO QUESTION OF THE CRASH OF THE B- TWENTYFIVE AT KELSO … HAVING BEEN CAUSED BY ANY SABOTAGE” and gave the cause: “THE LEFT ENGINE BURNED OUT AN EXHAUST STACK WHICH CAUSED THE WING TO BURN AND BREAK OFF” (Seattle teletype of 6 August 1947). D. M. Ladd reported to the Director on 14 August: “Investigation by the Bureau has reflected that this plane was definitely not carrying parts of a disc and there appears to be no substantiation of a sabotage charge.” Whether the heavy cardboard carton that the crew chief placed in the B-25 held the fragments is not known: he “did not look in the box” (Fourth Air Force A-2 report, 12 August). And by their own signed statement to the FBI of 7 August, what Dahl and Crisman had handed on as fragments was “strange rock formations from a gravel pit on Maury Island”.

What would settle it

The report of the investigation of the wreck, which is not in the release, and an analysis of the material the two men handed over; no analysis is in the release either.

RefutedT5Radio Tupi, Rio de Janeiro, 8 November 1963, as taken down by FBIS (EOP-UAP-D001), and a local newspaper report paraphrased by the American embassy (DOS-UAP-D001)

“A large metal sphere with a human body inside fell in the centre of Conde, Bahia, in November 1963.”

Asked by the embassy, the consul in Salvador replied on 14 November 1963: “Story of strange object descending in region of Conde Bahia apparently fabricated in Rio no such objects seen by anyone in the area according to newspaper reporters and others who rushed there before investigation reports were received” (telegram 157, quoted in airgram A-628, DOS-UAP-D002). The Diario de Noticias of 9 November, as the airgram summarises it, “states that the Ministry of Aeronautics categorically denies that there was any ‘strange object’ in Conde”, and the embassy had recorded that “no repeat no such object had been found aground” (DOS-UAP-D001). All of this reaches us through the embassy: the consul’s telegram and the clippings are not in the release.

What would settle it

The consul’s telegram 157 and the two clippings he sent by pouch on 14 November, which are not in the release; the Rio newspaper report; any record of the Ministry of Aeronautics or of the Secretary of Public Security on the episode.

RefutedT4Witness accounts and early Soviet reporting

“The Petrozavodsk ‘jellyfish’ phenomenon was inexplicable.”

The phenomenon matches a Soyuz launch from Plesetsk — a propellant release in the upper atmosphere, lit by a Sun already below the horizon. Thousands of witnesses and total failure to recognise the phenomenon were not evidence of anything unusual; they were evidence that the programme was secret.

What would settle it

Nothing — the temporal and directional match to the launch is unambiguous.

RefutedT5Contemporary presentations in popular media

“The 1561 Nuremberg woodcut documents an aerial UFO battle.”

The broadsheet is authentic; the interpretation is not. Publications of this kind were a sixteenth-century blend of sensational press and religious commentary, in which ‘signs in the sky’ were a generically expected element. Observation cannot be separated from iconography.

What would settle it

Nothing — the limit follows from the nature of pre-instrumental sources.

RefutedT5The standard ‘British Roswell’ narrative

“Radar confirmed an object over Rendlesham Forest.”

The UK Ministry of Defence file is unambiguous on this point: no radar confirmation of an unidentified object in that area and timeframe was found. This matters, because the events unfold between two NATO air bases in a densely covered radar environment.

What would settle it

Nothing — the MOD files have been released.

RefutedT1Infrared footage released by the Mexican Secretariat of National Defence

“The Mexican Air Force filmed eleven objects surrounding its aircraft.”

The heat sources were real and the sensor worked correctly. They were also stationary, on the surface, roughly 200 km away — gas flares at the Cantarell offshore oil field. The apparent motion and encirclement came from the aircraft’s own turn. Third instance of the same failure mode as GoFast and Aguadilla: competent operators, working sensor, assumed range.

What would settle it

Nothing — the geometry was reconstructed and matches the platform positions.

RefutedT1The CIA’s own 1955 file: memoranda headed “Flying Saucers or Unconventional Aircraft”, and the handwritten note “Sen. Russell UFO file” on the information report

“The CIA confirmed that Senator Russell saw a flying saucer.”

The CIA recorded that Senator Russell said he had seen a flying saucer; it did not confirm that he had. Its October memorandum refers to “Senator Russell’s remarks that he had seen a flying saucer”, and its memoranda are headed “Flying Saucers or Unconventional Aircraft”. What the memorandum of 31 October records him describing is less: “a small greenish-yellow glowing ball rising quite rapidly”; he “never saw the form of the object only the luminescent ball”, and thought it “could have been as small as a rocket”. The same memorandum concludes that “the only testimony which would support the existence of flying saucers or radically unconventional aircraft is that of Colonel Hathaway”, and that “All other observations can probably be explained as steep climbing aircraft or missiles.” The senator’s is among them. The note “Sen. Russell UFO file” on the information report is handwritten and unsigned, and it names a file, not a finding.

What would settle it

Nothing further is needed for what the CIA concluded: its memorandum of 31 October states it. The file does lack the senator’s own debriefing and Prague dispatch C-103, which would show exactly what he said and when.

MisrepresentedT3Cdr. David Fravor under oath (2023), relaying the controller aboard USS Princeton (printed hearing, p. 13)

“The object dropped from 80,000 ft to sea level in a fraction of a second.”

The version that can be opened says something else. Fravor, relaying the controller: “these objects had been observed for over 2 weeks coming down from over 80,000 feet, rapidly descending to 20,000 feet, hanging out for hours and then going straight back up.” (printed hearing, p. 13) His written statement: “They had been descending from above 80,000ft and coming rapidly down to 20,000ft”. Neither gives a time, and both end at 20,000 feet, not at sea level. No radar record of those descents can be opened. See the case.

What would settle it

The SPY-1 records of USS Princeton for the two weeks before 14 November 2004.

MisrepresentedT1Air Intelligence Information Report 52-1 of 22 July 1952, whose source is given as “Control Tower Operators”; a handwritten “(7300 mph)” on one copy; the later FTD summary (Project Blue Book, NAID 28945857, images 150, 152, 120)

“Targets over Washington moved at up to 7,000 mph.”

The figure goes back to one trace on one night. Report 52-1 of Headquarters Command says of 19/20 July that “one (1) target left a trace from West of Andrews to Riverdale a distance of seven (7) miles in four (4) seconds” (Project Blue Book, NAID 28945857, image 152). Seven miles in four seconds is 6,300 miles per hour (our calculation). On that copy someone has written “(7300 mph)” by hand; the other typing of the page has no such note (image 98). The undated FTD summary has the objects “reported to have speeds on the order of 7500 miles per hour” (image 120). The report describes a single trace, not a series of returns measured one after another; of other targets that night the CAA’s senior controller wrote that they “indicated a very rapid movement if they were the same ones” (image 85), and he put the movement of the targets he checked at “about 100 to 130mph” (image 84). The Blue Book files hold no weather data for that night. See the case.

What would settle it

Scope photographs, if any were made: a Tenth Air Force officer wrote that “there is a possibility that scope photographs were made providing the equipment was available” (Project Blue Book, NAID 28945857, image 138). Also the tower operators’ own reports, on which report 52-1 rests.

MisrepresentedT1The memorandum of SAC Guy Hottel to the FBI Director, 22 March 1950 (FBI file 62-HQ-83894, Section 5, p. 68)

“An FBI memo confirms that three flying saucers and their occupants were recovered in New Mexico.”

The memorandum exists and says this, but only as hearsay passed along a chain: “An investigator for the Air Forces”, unnamed, through “Mr. HOWE'S informant”, to Karl Howe of the Metropolitan Police Department, to FBI Special Agent Kurtzman, to Hottel. It ends: “No further evaluation was attempted by SA KURTZMAN concerning the above.” It is not a confirmation by the FBI. Searching the text of the released parts of the file, we found no follow-up to it; the result is negative, not absolute. Our own observation from the dates, not a connection the documents make: in the same weeks the file records other second-hand stories of crashed saucers with crews three feet tall, in an Air Force message of 16 January 1950 (p. 44) and a New Orleans memorandum of 31 March 1950 (p. 77), whose margin carries a handwritten note of which we can read “4/12/50 OSI adv. […] who adv. they checked this out negatively”; the words in between, which would say who checked it, are illegible.

What would settle it

The identity of the Air Force investigator, and any record of the three objects with established provenance.

MisrepresentedT1Film footage and Wellington ATC radar records

“Kaikoura is a confirmed radar–film correlation.”

The temporal correlation exists, but analysis indicated that part of the lights match squid-fishing boats seen through an inversion layer, and part match bright planets. The radar returns may have been independent echoes from anomalous propagation. One night, two independent error mechanisms.

What would settle it

Fishing fleet positions for that night, matched frame by frame against the footage.

MisrepresentedT5UPI photo caption, Anchorage Daily News, 1 January 1987, p. B3: “The Federal Aviation Administration and the U.S. Air Force have confirmed that a UFO appeared on their radar.” (FAA file, NAID 40587537, image 29)

“FAA radar confirmed an object alongside JAL 1628.”

Returns were seen at the time. The Anchorage Center’s chronology has the military control centre at Elmendorf reporting “a primary radar return in JL1628’s 10 o’clock position at 8 miles” and later “a ‘flight of two’ in JL1628’s position” (FAA file, NAID 40587180, image 3), and the controllers wrote of primary returns where the pilot reported traffic (NAID 40587240). The recorded data does not show them: “Radar data recorded by Anchorage Center does not confirm the presence of the traffic reported by Flight 1628” (NAID 40587180, image 2). The FAA’s Technical Center found that the second target “was not another aircraft but rather a split radar return from the JAL Boeing 747” (NAID 40587486, image 3), and a review of 61 minutes of data found no “abnormalities that could be associated with any type of target as indicated by the pilot” (NAID 40587480, image 4). The Air Force “INTERPRETED INCIDENT AS SPURIOUS SIGNALS ON A.F. RADAR” (NAID 40587497, image 3). The controller who said the traffic stayed with the 747 through its turns later wrote: “this information was what I received from JL 1628” (NAID 40587240, image 2). The caption was printed before the FAA released its file.

What would settle it

The Air Force’s radar data of that evening, which FAA notes of 2 January 1987 record as gone: “TAPES HAVE BEEN REUSED” (NAID 40587497, image 3). The Anchorage Center’s printout of its recorded radar data is public (NAID 40587258) and can be read again against the Technical Center’s analysis.

MisrepresentedT5Associated Press, 27 June 1947: “nine saucer-shaped, shiny objects dipping and skimming” (Project Blue Book, NAID 28929152, image 61)

“Kenneth Arnold saw saucer-shaped objects.”

Partly. In the account he wrote for the Air Force in July 1947 Arnold calls the objects “saucer like objects” and says that in the sun’s reflection “they appeared to be completely round” (NAID 28929152, images 38–39). The drawing in the same account shows another outline: “They seemed longer than wide, their thickness was about 1/20th of their width” (image 41). The words about a saucer skipping on water are not in his account; they appear only in an undated Blue Book summary, which cites a “subsequent interview” the file does not hold (image 13), and in the proofs of a book that gives no source (image 47).

What would settle it

The “subsequent interview” that the Blue Book summary cites, which is not in the file; what the files hold is set out in the case.

MisrepresentedT1National Guard exercise documentation, March 1997

“The Phoenix Lights were flares from a military exercise.”

True of the ~22:00 episode — and only of that one. That episode produced most of the footage. The ~21:00 episode is a separate event an hour earlier and is not explained by flares. Conflating the two is the source of most confusion around the case.

What would settle it

Nothing for 22:00. The 21:00 episode requires radar data.

MisrepresentedT1Recordings of interviews conducted within days of the event

“Sixty children independently confirmed the same event.”

The accounts are not independent: the children spoke to one another before the interviews, and some of the recorded questions are leading. It is no longer possible to separate what they saw from what was suggested during questioning. This is a case for witness psychology, not for physics.

What would settle it

Nothing — the interview material is what it is.

MisrepresentedT5TASS news agency dispatch, September 1989

“The USSR officially confirmed a UFO landing at Voronezh.”

A press agency dispatch is not an investigative document. The state character of the publisher does not raise the source tier — what matters is whether an investigation stands behind the statement. None did.

What would settle it

Nothing — this is a question of source classification, not of fact.

MisrepresentedT5The standard reading of the USAF statistic

“Project Blue Book left 701 cases unexplained — meaning 701 unknown craft.”

The number 701 is correct: of 12,618 reports investigated, that many remained in the ‘unidentified’ category. But ‘unidentified’ means ‘it could not be determined from the available information what this was’ — not ‘it was proven to be non-terrestrial’. In the great majority of those cases the constraint was data quality, not the nature of the object. The project was describing the same limitation early on. In a recording of a project briefing, dated by the publisher to March 1952 (DOW-UAP-D154), Ruppelt puts the files at about 800 cases and says about 20 per cent are “very good reports offered by very reliable people” from which “absolutely no conclusions can be drawn”. The trouble is that “the details aren’t the kind that we want”, and “we’ve got no real proof that anything even exists.” Good witnesses, details that cannot be measured: that is the point of this entry, in the project’s own words. The publisher’s 2026 summary says those cases “remained unexplained after technical analysis”; those words are not in the recording. About 20 per cent in 1952 and 701 of 12,618 at the end of the programme are far apart, but the first is an estimate spoken at a briefing and the second a formal category at the programme’s close, so they need not measure the same thing. The release also holds the formal count at an intermediate date: a memorandum of 28 September 1965 from the Air Force’s Director of Information (DOW-UAP-D092) gives 9,267 reports investigated by 30 June 1965 and says “Of these 9267 reports, 663 cannot be explained”, about 7 per cent, so the category was already close to its final size by then. The documents do not explain the difference, and neither does this entry.

What would settle it

Nothing — this is a matter of reading the category definition correctly.

MisrepresentedT4A paper attached to a May 1971 minute of the Australian Joint Intelligence Organization, paragraph 12 (CIA-UAP-019, held by the National Archives of Australia as NAA: A13693, 3092/2/000)

“Project Blue Book’s consultants tested the unknowns against the identified objects and found the probability that they were alike was less than one in 10²⁸.”

The tests are real and the result went that way, but the figure is not in the report. Project Blue Book Special Report No. 14 (CIA-UAP-015) compared 434 unknown sightings with the identified ones by a chi-square test on six characteristics: colour, number, shape, duration, speed and light brightness. For each it gives the chi-square, the degrees of freedom and the values for 5 and 1 per cent, but no exact probability, and nowhere does it combine the tests into one figure. Its own reading: “In five of the six cases, the probability is less than 1 per cent that the distributions are the same.” It then says what that does not show: “these tests do not necessarily mean that the UNKNOWNS are primarily ‘flying saucers’ and not aircraft, balloons, or other known objects or natural phenomena”, because the unknowns “may be known objects in different proportions than the group identified as KNOWNS”, which it calls the more probable case. With astronomical sightings removed from the knowns, the colour test no longer reached the 5 per cent value, shape, duration and brightness fell between the 5 and 1 per cent values, and number and speed stayed beyond the 1 per cent value. The report calls these results “inconclusive since they neither confirm nor deny that the UNKNOWNS are primarily unidentified KNOWNS”, and says why it went no further: fitting a combination of knowns to the unknowns would, it felt, give “a distorted and meaningless result” because of the inaccuracies in the reports. The 1971 paper calls this irrational without answering that reason, and says the same report “showed mathematically that the evidence favoured an explanation that was scientifically unknown”, while the report concludes it is “highly improbable that any of the reports of unidentified aerial objects examined in this study represent observations of technological developments outside the range of present-day scientific knowledge.” The paper does not say how it arrived at 10²⁸. Because the report prints the chi-square and the degrees of freedom for every test, the exact probability of each can be worked out from its tables. Our own calculation from those tables, which the report does not contain, puts the six probabilities multiplied together at about 1 in 2 × 10²⁹ for the full set, which fits the paper’s “less than one in 10²⁸”, and at about 1 in 4 × 10¹⁷ without the astronomical sightings, which is far from its “ten trillion trillion to one”, 10²⁵. The paper does not say it multiplied anything, and multiplying treats six characteristics of the same 434 reports as independent tests, which the report nowhere does.

What would settle it

The calculation behind the paper’s figure: which probabilities were combined, where they came from and on what assumption. The report itself prints only the chi-square, the degrees of freedom and the 5 and 1 per cent values for each test.

MisrepresentedT1The public database of the French agency GEIPAN

“A substantial share of UAP reports remains unexplained.”

The French database — the best-structured public collection in the world — shows a different picture: roughly two thirds identified or probably identified, roughly thirty per cent unresolvable for lack of data, and roughly three per cent unexplained after full investigation. Three per cent is not ‘a substantial share’ — but it is not zero either.

What would settle it

Nothing — the data is published and kept current.

MisrepresentedT1Recommendations of the CIA scientific advisory panel (Robertson Panel), January 1953 (CIA-UAP-002)

“The CIA ordered the truth about UFOs to be concealed.”

The panel did recommend acting on public interest, and the CIA folder that holds its report (CIA-UAP-002) shows it went further than reducing it. The report recommends that the national security agencies “take immediate steps to strip the Unidentified Flying Objects of the special status they have been given and the aura of mystery they have unfortunately acquired”. F. C. Durant’s report of the panel’s meetings gives the educational programme “two major aims: training and ‘debunking’”, to be carried out through “mass media such as television, motion pictures, and popular articles”, and records that civilian groups studying the subject “should be watched”, with “the possible use of such groups for subversive purposes” to be “kept in mind”. That is a documented instance of narrative management. The motive the folder gives is defence, in its own words: “the clogging of channels of communication by irrelevant reports, the danger of being led by continued false alarms to ignore real indications of hostile action”, and a public in which “skillful hostile propaganda could induce hysterical behavior”; Durant’s report adds “greater vulnerability to possible enemy psychological warfare”. The panel’s report does not name the USSR. The Soviet framing belongs to a CIA memorandum of 13 October 1952 to the Deputy Director (Intelligence), written before the panel met, which calls “the scientific capabilities of the USSR to create and control Flying Saucers as a weapon against the United States” “a primary concern of the CIA/OSI”. Nothing in the folder suggests knowledge of a non-terrestrial origin: the report finds “no residuum of cases which indicates phenomena which are attributable to foreign artifacts capable of hostile acts, and … no evidence that the phenomena indicate a need for the revision of current scientific concepts”, and Durant writes of the members that “What they did not find was any evidence that related the objects sighted to space travelers.” As for “ordered”: the panel recommended. Part I of Durant’s report, the history of the meetings, survives in an unclassified version of 1967 with the names removed (DOW-UAP-D092). It records that someone who joined the meeting on 15 January, whose name has been removed, stated three personal opinions, among them “That vigorous effort should be made to declassify as many of the reports as possible”, and that on Saturday 17 January the panel was told a copy of the initial rough draft had been shown to the Director of Intelligence, USAF, “whose reaction was favorable.” At the request of the Director of Central Intelligence the report went to the Secretary of Defense, the Federal Civil Defense Administration and the National Security Resources Board, with letters saying that “this Agency does not consider problems arising from sightings of ‘flying saucers’ primarily its concern”, and concluded that “no National Security Council Intelligence Directive on this subject is warranted.” The Secretary of Defense’s copy survives as well (DOW-UAP-D085): his office received it on 17 March 1953, a handwritten note on its routing slip reads “This report appears to warrant action”, and copies of the letter and the report went on to the Secretary of the Air Force by memorandum. A CIA memorandum of 17 December 1953 (CIA-UAP-007), under the heading “Results of OSI Panel Recommendations”, reads: “The definite drop in the number of ‘sightings’ reported during 1953 over 1952 could be attributed to actions following these recommendations.” The concern is older than the panel. In a recording of an Air Force project briefing, dated by the publisher to March 1952, the year before the panel and with no mention of the CIA (DOW-UAP-D154), a speaker from the project explains the hesitation over alerting the Ground Observer Corps: “we’re afraid maybe if we alert that number of people, then everybody in the United States will get excited again. That’s the thing we’re trying to keep out of this thing is this excitement business.” The motive given there differs from the panel’s: the quality of reports and relations with the press. The project wants reports from “people with good common sense instead of all these nut letters”, and is trying to lower the classification because answering reporters with “it’s classified” produced stories that “The Air Force just picked up a spaceship somewhere and they won’t tell us about it.” The same aim existed inside the Air Force’s own programme a year earlier, and it protected no finding either: in the same recording Ruppelt says “we’ve got no real proof that anything even exists.” It also outlasted the panel, again inside the Air Force. In a memorandum to General Samford of 13 January 1955, two years after the panel, Lt Col Joseph A. Bloomer of the Air Force’s Directorate of Intelligence (DOW-UAP-D095) records how he answered a request for a statement of position on UFOs: “I stated our position regarding UFO’s and indicated that our best efforts in this field were constantly directed to discouraging, minimizing, and playing down any and all attempts at publicity, not excluding classified vehicles such as AID.” That is the Air Force’s position, in the words of its own intelligence directorate; the CIA does not appear in the memorandum.

What would settle it

The names removed from Part I of F. C. Durant’s report of the meetings, “History of Meetings of Panel”, which the folder lacks and which survives in an unclassified version of 1967 (DOW-UAP-D092), and the item withdrawn from the folder as a 25-page report with attached memoranda dated 17 January 1953. The folder’s other withdrawn item, a 6-page memorandum dated 16 February 1953, is probably that Part I: Durant’s report carries the same date, its purpose and Part I fill pages 1 to 6, and the folder’s copy starts at page 7. That is an inference from the date, the page count and the gap in the pagination; no document says so.

MisrepresentedT1A memorandum for record by Maj. Harold A. Steiner, Assistant Secretary of the USAF Scientific Advisory Board, “Some SAFOI Thoughts for the SAB Ad Hoc Committee on UFOs”, 21 January 1966, recording what he was told that day at SAFOI (DOW-UAP-D092, pp. 42–43)

“The Air Force set up its 1966 scientific review of UFOs to get itself off the hook.”

The words are in the file, but they record what SAFOI wanted, as an officer of the Scientific Advisory Board wrote it down, not the task the review was given or what it did. The review began with a request of 28 September 1965 from Maj. Gen. E. B. LeBailly, Director of Information, whose memorandum the Board’s papers file as “SAFOI Memo” (DOW-UAP-D092). It asked for “a working scientific panel composed of both physical and social scientists” to review Project Blue Book, “its resources, methods, and findings”, and “to advise the Air Force as to any improvements that should be made in the program”, and said that “many of the reports that cannot be explained have come from intelligent and technically well qualified individuals whose integrity cannot be doubted.” On 5 October 1965 the Board’s secretary reported that the request had just arrived, that Dr. Stever’s “initial reaction was lukewarm”, and that Stever wanted the Military Director’s views first, “to see if perhaps there is some additional information or facts which would give a clue on why the request was made.” On 21 January 1966, thirteen days before the committee first met, the Board’s assistant secretary, Harold A. Steiner, visited SAFOI and recorded: “SAFOI wants some prestigious scientific group to look at the UFO problem in depth and come up with a position that will help get the Air Force off the hook.” The same memorandum says SAFOI expected a report that would let it “stand before the most renown critics and say that the AF position on UFOs is sound or action is being taken to make it sound”, and that it was “very emphatic that they do not want a ‘for motherhood and against sin’ type of committee report”, because it could not “get to the heart of the public relations problem until they get some scientific evidence upon which to base their opinion.” The committee met on 3 February 1966 under Dr. Brian O’Brien. The file gives its conclusion as that the programme “can be improved by conducting a more thorough scientific investigation of questionable sightings”, and on 5 April 1966 Harold Brown wrote to the Chief of Staff that its recommendations “should be accepted and arrangements made to contract for a scientific team to investigate in depth certain selected reported sightings of UFO’s.” The public relations motive runs through the rest of the file: a memorandum of 20 April 1966 on putting the recommendation into effect lists among its open questions that “the problem is 99% public relations”, and in February 1969 Steiner wrote that the University of Colorado study, for which the O’Brien committee had served “as a springboard”, “puts the Air Force in an excellent position to counter criticism.” The documents show that SAFOI, the office that asked for the review, wanted it to get the Air Force off the hook, and that those involved later judged the result would help against criticism. They do not show that the committee was asked for a conclusion settled in advance, or that it gave one.

What would settle it

SAFOI’s own papers from September 1965 to January 1966, which would show whether the aim Steiner recorded was the office’s position or his summary of one conversation, and whether it reached the committee’s terms of reference.

MisrepresentedT1The conclusion of the 1984 field report, “whatever it is, can be measured”, which the project’s website quotes today

“The Hessdalen phenomenon is repeatable and measurable with instruments.”

The 1984 report does conclude that “the phenomenon, whatever it is, can be measured”, “by radar and laser” besides the light measurements. What stands behind it: of 36 radar recordings, “Three of those were probably also seen as lights. All the others were not observed visually.” The usable spectra were either of a light that “might be a known light” or “too weak to say what kind of spectrum it is”, and the report says: “We have not found out what this phenomenon is.” Lights are reported in the valley again and again, “At the most … about four times a day” by the report and seldom in summer, but not on demand: in September 2026 the project wrote that “For the first time since the 2024 camera upgrade, a witness report could be verified through camera footage.” Nor is the valley unique: a geophysical paper of 2024 names Marfa, Silver Cliff, Paasselkä and Queensland among the “Areas where luminous phenomena have repeatedly been reported”. See the case.

What would settle it

Radar and camera records of the same light at the same time, published with the times of the sightings, from the station or from a campaign.

MisrepresentedT5Interpretation of material presented publicly by AARO

“The Mosul footage shows an object with extraordinary properties.”

AARO presented the footage with an explicit caveat: there is too little data to state anything, and absence of resolution does not imply anomaly. This is exemplary institutional conduct — the category ‘unresolved for lack of data’ must exist separately, or every blurry pixel becomes evidence.

What would settle it

Platform metadata: range to target, viewing angle, navigation data.

MisrepresentedT4Frank Edwards, talk to Civilian Saucer Intelligence of New York, 28 April 1956: “eleven people rushed from a farmhouse” (Project Blue Book, NAID 28963358, image 68)

“Eleven witnesses fired on small non-human figures for four hours.”

The shooting, the drive to the police and a hole in a window screen are on record. The Kentucky New Era of 22 August 1955 names the guns, “a shotgun for Sutton and a .22 caliber target pistol for Taylor”, and reports that officers found “no tracks of ‘little men’” and “a hole in the screen at the window through which occupants said a shot had been fired”; at the station the household said: “We’ve been fighting them for nearly four hours” (Blue Book file NAID 28963358, images 51, 52). The number is not. The same paper put “some 10 or 12 persons at the house, including several children”, and “investigating officers were not able to determine exactly how many of those present actually claimed to have seen any of the little men”; a statement written on 22 August lists seven adults (image 53). “Eleven” first appears in Frank Edwards’ talk of April 1956 (image 68). What they fired at, no document establishes: the woman’s statement says it “looked like a monkey” (image 53).

What would settle it

The Kentucky State Police report and sketches, which a memo of 10 September 1956 places “on file with Trooper Riley’s case report at Frankfort, Kentucky” (image 57); the report of Isabel Davis and Arthur Ledwith of Civilian Saucer Intelligence, “The Landing at Kelly - August 21-22, 1955”, with sketches made from the witnesses’ descriptions the day after (image 113); and the account and pictures of Pfc Hodson of Fort Campbell, published in the Clarksville Leaf-Chronicle (image 57). None of them is in the releases.

MisrepresentedT5A circulating version of the case, with no document behind it: the Blue Book file gives 38 as the number present and 27 as the number who signed (NAID 28983630, images 5, 6, 11)

“Thirty-eight witnesses signed a contemporaneous account of the Boianai sighting.”

Thirty-eight is the number of people present, not the number who signed. Gill’s report of 14 July 1959: “38 witnesses were brought together into a well-lighted room”, and after he had addressed them, “27 observers of a total of 38 voluntarily signed” (Project Blue Book, NAID 28983630, images 5, 6). The sketch of the object says “by 38 witnesses” (image 11). The data sheets were kept during the observation, but the file holds copies: “a copy of the original recorded during the actual time of observation by the reporter” (image 6). Gill himself warned of “undue influence by suggestion of a European observer” (image 5).

What would settle it

The original signature list and Gill’s original notes, of which the Blue Book file holds copies; and the findings of the RAAF officer who investigated the report, of which the RAAF letter of 22 February 1960 says “such reports are not releasable to the public” (The A.P.R.O. Bulletin, March 1960, p. 2).

Cases

Boianai

MisrepresentedT1The first report, as the Foreign Technology Division’s memo of 24 October 1968 records it: “the crew of a B-52 had sighted and photographed an UFO” (Project Blue Book, NAID 302580672, image 3)

“A B-52's own radar painted a return correlated with a visual sighting from the same aircraft.”

The radar return is on record; the visual correlation is not. The crew described the return on the RAPCON tape, and the base reported that “RADAR SCOPE PHOTOS WERE OBTAINED AND CLEARLY SHOW THE RADAR ECHO”. The same message says: “WHATEVER CAUSED THE ECHO WAS NOT VISUALLY SIGHTED BY THE AIRCRAFT CREW MEMBERS” (Project Blue Book, NAID 302580672, image 14). The light the instructor pilot saw later was, in his words, “either on the ground or just slightly above the ground”, and the Foreign Technology Division wrote that a simultaneous sighting from the ground and the air “was not substantiated by the pilot’s form 117” (image 104). Two handwritten notes in the file question the pilot’s time, and the base’s investigator said on the telephone “They had it visually all the way down” without saying whether he meant the scope. The photographs are not in the published file. See the case.

What would settle it

The 13 scope photographs and the RAPCON tapes, with the times of the radar return and of the pilot’s sighting.

MisrepresentedT4Chris Rutkowski in the Library and Archives Canada podcast “UFOs at LAC: The Falcon Lake incident, part 1”, 15 May 2019: “the checkerboard pattern of chemical burns or thermal burns was on his abdomen”

“The Falcon Lake witness bore a burn in a regular grid pattern.”

The burns are on record; a grid on the skin is not. His doctor recorded “first degree burns to the upper abdominal wall” (Dr. R. D. Oatway, 19 September 1967). The RCMP officers who saw them on 23 May described “a large burn that covers an area approximately 1 foot in diameter”, “blotchy and with unburned areas inside the burned perimeter area” (RCMP report of 26 May 1967, p. 2). The only pattern in the files is on his undershirt: S. E. Hunt saw photographs of “the burns on his abdomen and the scorced grid pattern on his undershirt” (memorandum of 13 September 1967, p. 2), and S/L Bissky, examining the undershirt, found burns “in a square pattern, or perhaps slightly oblong, not too similar to the abdominal burn” (report, p. 3). What caused the burns, no document establishes.

What would settle it

The Misericordia Hospital’s record of 20 May 1967; Annex B to Bissky’s report, the “preliminary medical report from Mr. Michalak’s doctor”, which we did not find in the file of the National Research Council; and the photographs taken for Life magazine of the burns and the undershirt.

MisrepresentedT1MOD UFO desk internal assessment, The National Archives

“The MOD judged the Cosford object to exceed anything in the UK inventory.”

The internal assessment says this, and it is a genuine documented instance of a defence ministry taking a UAP report seriously in writing. But the same file, and later analysis, identified a Russian rocket stage re-entering over the UK that night, producing widely observed fireballs along the reported corridor. Institutional concern and a prosaic cause are both real and not in conflict.

What would settle it

Nothing — the re-entry is independently documented.

MisrepresentedT5Media and social coverage of the Department of War releases from May 2026 onward

“The 2026 file releases are Disclosure.”

The releases are real, continuous and larger than anything since Blue Book was digitised: six tranches by 21 September 2026, when we last harvested the releases, alongside a statutory transfer of federal records into the National Archives collection. What is being released is documentation — files agencies already held. That is not the same as a finding. No released record asserts a non-human origin, and the office publishing the video states in each caption what was reported rather than what was established. Two different things are being called by one name.

What would settle it

A released record whose own text states a non-human origin, or physical material an outside laboratory can re-analyse. Neither has appeared.

MisrepresentedT5Public discussion of AAWSAP

“AAWSAP was a contract to study UFOs.”

Not on paper. Across the seven contract documents the Department of War released in PURSUE release 06 (the Statement of Objectives, the solicitation and order, and modifications P00001 to P00005) the words UFO, UAP, unidentified, anomalous and paranormal do not appear once. The stated object is the foreign threat: “to understand the physics and engineering of these applications as they apply to the foreign threat out to the far term, i.e., from now through the year 2050”, in twelve technical areas from lift and propulsion to spatial/temporal translation and human effects. That is what the contract says. It is not evidence that the programme had nothing to do with the subject. The same release published 37 technical reports under the AAWSAP name, the DIRDs listed in our records registry as DOW-UAP-D117 to D153, and a contract records what was ordered, not what was produced. The claim misstates what the contract is on paper; these documents cannot be asked what the programme made.

What would settle it

The deliverables the contract names: the monthly status reports, the research reports for the twelve technical areas and the final Integrated Threat Assessment, together with the BAASS proposal of 3 September 2008 that the order incorporates by reference.

MisrepresentedT2Air Force memorandum for the press room, 1 June 1956

“The Air Force determined that the Tremonton film shows seagulls.”

The Air Force did say so, but it was its third answer, and the Blue Book file shows what it rests on. The ATIC worksheet of 1952 marks the final evaluation “Unknown”. A teleconference message of 3 February 1953, supplying text for the press, calls sea gulls soaring in thermals a “strong possibility”. Only the memorandum written for the Air Force press room on 1 June 1956 finds “little reasonable doubt” that the objects were “indeed seagulls”. It credits the Photo Reconnaissance Laboratory with the gull hypothesis, says it was “undoubtedly supported by the presence of identifiable seagulls in some of the frames”, and rests its verdict on the “unanimity of opinion present in all evaluations”. The laboratory analysis in the same file says the opposite: it is “reasonably certain” that the brightness of the objects exceeds that of “white birds against the sky”, and a memorandum for the record of February 1953 summarises it the same way. The file holds no frame with an identifiable gull. An ATIC memorandum of 21 May 1956 repeats that the original shows gulls “on a number of frames”, but names none and reproduces none. In the Blue Book file the gull films said to have strengthened the conclusion appear twice, one sentence each time, with neither the films nor any measurements. The CIA folder on its scientific panel (CIA-UAP-002) records that a film of seagulls in bright sunlight was shown to the panel in January 1953, again without distances or measurements, and the February 1953 memorandum still lists filming gulls in Florida, with the distance of each shot known, as a step to be taken. None of this shows the objects were not gulls; the file cannot settle that. It shows a press line that cites an analysis saying something else, and supporting material the file does not contain.

What would settle it

The frames the 1956 memoranda rely on, identified by number on the earliest surviving copy of the film, or the gull test films with the distance of each shot, which the February 1953 memorandum itself said the test would require.

UnverifiedT3Cdr. David Fravor under oath, 26 July 2023 (printed hearing, p. 14), relaying the ship’s controller

“The Tic Tac covered 60 nautical miles in under a minute.”

Both the distance and the time are the controller’s words as Fravor recalled them in 2023: “the controller came up and said, ‘sir, you are not going to believe this, but that thing is at your CAP point roughly 60 miles away in less than a minute.’” (printed hearing, p. 14). His written statement adds that the object “had reappeared on the Princeton’s Aegis SPY 1 radar at our CAP point”. No radar record from USS Princeton can be opened, and the Navy task force slide on the case speaks of “very limited data to support technical analysis”. To read the figure as a speed you must assume that both radar indications were the same object and that the track was not lost and picked up again; neither can be checked. See the case.

What would settle it

The raw SPY-1 track file from USS Princeton, with continuity of track and timestamps.

UnverifiedT3Cdr. David Fravor under oath (2023), relaying the crew of the next sortie (printed hearing, pp. 14, 21, 41)

“The object actively jammed the aircraft’s APG-73 radar.”

Fravor did not fly that sortie; he relays its crew: “My crew that launched after we landed experienced significant jamming to the APG–73 radar” (printed hearing, p. 21); “The other airplane that took the video did get it on a radar. As soon as it tried to lock it, it jammed the radar” (p. 41). He also said that the record is missing: “What you do not see is the radar tape that was never released, and we do not know where it is at” (p. 14). No radar data from the sortie can be opened. See the case.

What would settle it

The APG-73 recording from the sortie, analysed by electronic warfare specialists.

UnverifiedT5Harry G. Barnes, senior controller at the air route traffic control centre at Washington National Airport, in a newspaper account of 29 July 1952 (Project Blue Book, NAID 28946178, image 22)

“Each sighting coincided with a pip on the radar near the pilot’s plane.”

Barnes wrote of Capt. Pierman’s flight on the morning of 20 July: “Each sighting coincided with a pip we could see near his plane.” (Project Blue Book, NAID 28946178, image 22) The papers of 1952 support a correlation, but at the level of time and place. Headquarters USAF passed on the centre’s report that “WASHINGTON CENTER RADAR SUBSTANTIATED ELECTRONICALLY THAT OBJECT WAS FOLLOWING AS PILOT OBSERVED.” (NAID 28945857, image 47), and the CAA’s senior controller wrote that a light which followed another flight in “was substantiated by Tower and Center radar” (image 84). A Department of State memorandum of 28 July 1952 reports General Samford as saying: “The radar observation may have elements of ‘electronic fluke,’ but is sufficiently tied in with pilot observation so that it cannot be attributed entirely to this.” It names neither Washington nor any date of a sighting; only its own date ties it to the wave. The FBI file, Section 6 records an Air Force briefing on reports by pilots “for which there is additional corroboration, such as recording by radar or sighting from the ground”, without naming a sighting. Against it: asked at the press conference of 29 July whether Andrews and National had triangulated anything, Capt. James answered that “the records made and kept aren't accurate enough to tie that in that close” (NAID 461459117, image 12). On 19/20 July Andrews’ radar found nothing in the first hour, and the light its officer watched he took for a star (NAID 28945857, image 68). When the centre gave Pierman the position of the objects at ten o’clock, he saw “a DC-4 type aircraft” there (image 137). Gordon Thayer, in the Condon report, found the radar tracks “generally not correlated with each other, with airborne radar/visual observations, or with ground visual reports, except in a very general way”. See the case.

What would settle it

Scope photographs and the F-94 crews’ reports, set against the centre’s log, which gives times to the minute (Project Blue Book, NAID 28945857, image 261).

UnverifiedT1RAF Lakenheath’s teletype report BOI-485 of 16 August 1956, as transcribed in the Condon report (Case 2)

“The object moved into position behind the intercepting fighter.”

Reported, but by the ground radar at Lakenheath, not by the crew. Lakenheath’s message: “LAKENHEATH RATCC REPORTS THAT AS THE VENOM PASSED THE TARGET ON RADAR, THE TARGET BEGAN A TAIL CHASE OF THE FRIENDLY FIGHTER. RATCC REQUESTED PILOT ACKNOWLEDGE THIS CHASE. PILOT ACKNOWLEDGED AND STATED HE WOULD TRY TO CIRCLE AND GET BEHIND THE TARGET.” (Project Blue Book, NAID 28966873, image 38) In the Condon report’s transcription the next page, illegible on the scan, has the pilot say he “was unable to ‘shake’ the target off his tail”. No statement by the crew and no radar record is in the file; the record card does not mark “Air-Intercept Radar”, and an analysis in the same file reads: “From the incomplete information submitted, it is impossible to make a definite determination of the sources of these sightings.” (image 33) See the case.

What would settle it

The Lakenheath radar centre’s logs for the night and the RAF’s own record of the Venom sortie; neither is in the Blue Book file.

UnverifiedT4Accounts by people connected to the programme, written down later

“Project SIGN produced a document concluding UFOs were interplanetary.”

The document does not survive in the archives and its existence has never been independently confirmed. A paper attached to a May 1971 minute of the Australian Joint Intelligence Organization (CIA-UAP-019, also held by the National Archives of Australia as NAA: A13693, 3092/2/000) states that “The Top Secret Estimate was forwarded to the Pentagon” but cites no source for it, so it retells the story twenty-three years later rather than confirming it. The two official analyses of 1948 in this release, the initial Project SIGN report of 23 April (DOW-UAP-D097) and Air Intelligence Division Study No. 203 of 10 December (DOW-UAP-D093 and DOW-UAP-D094), do not mention an Estimate: the first thinks a low aspect ratio aircraft could reproduce much of what was reported, and the second sees “two reasonable possibilities”, domestic devices or objects “from a Soviet source”, which neither confirms nor rules out that an Estimate existed. An interesting historical thread; not evidence of concealed knowledge, nor of its absence.

What would settle it

Locating the document in archival holdings, or a registry entry confirming it was created.

UnverifiedT4Accounts collected from the late 1970s, three decades after the event

“A craft of non-terrestrial origin was recovered at Roswell.”

The entire dramatic structure of the case comes from testimony written down more than thirty years later. Documents from 1947 confirm a press release and its retraction the same day, and a third document of those days, an FBI teletype from Dallas of 8 July 1947, relays what a major of the Eighth Air Force told the FBI by telephone: the object “RESEMBLES A HIGH ALTITUDE WEATHER BALLOON WITH A RADAR REFLECTOR”, a belief that, the teletype adds, a call with Wright Field had not borne out (FBI file 62-HQ-83894, Section 1, p. 70). That is the military's account passed on by the FBI, not a finding of the FBI. Nothing more.

What would settle it

Material with a documented chain of custody back to 1947, independently analysed in several laboratories.

Cases

Roswell

UnverifiedT4Witness accounts from the 1980s and 1990s

“Non-human bodies were recovered at Roswell.”

No publicly verified material of any kind. USAF investigations in the 1990s pointed to anthropomorphic test dummies used in parachute programmes as a possible source for part of the testimony, though their chronology does not fully overlap with 1947.

What would settle it

Medical documentation or biological material with established provenance.

Cases

Roswell

UnverifiedT4The A.P.R.O. Bulletin, March 1960: the object “was made of 100% magnesium, which is not within the technology of our times” (Project Blue Book, NAID 28976909, image 29)

“The Ubatuba samples are extraterrestrial metal.”

No laboratory report can be opened today. The analyses are known only from APRO’s account: a spectrographic report of 24 September 1957, quoted as finding “magnesium (Mg) of a high degree of purity”, a second spectrograph run and an X-ray diffraction, whose reports, the bulletin says, “are on file at APRO’s headquarters” (Project Blue Book, NAID 28976909, image 29). The Brazilian Army took a sample on 4 November 1957, and by APRO’s own account “Dr. Fontes was not informed of the results of the test” (image 29). In May 1960 the Air Force’s Aerospace Technical Intelligence Center asked for “a sample of the material and the technical report concerning the Ubatuba Beach case” (NAID 28956049, image 37); no analysis of its own is in the files. The fragments came with a letter whose “signature was not legible” (NAID 28976909, image 27).

What would settle it

The papers APRO said were “on file at APRO’s headquarters”, Dr. Barbosa’s report and the films among them; the result of the Brazilian Army’s test; and Ibrahim Sued’s column in “O Globo” of 14 September 1957, with the letter (The A.P.R.O. Bulletin, March 1960, pp. 1, 3).

UnverifiedT4Claims by individuals presenting themselves as informants

“The US government holds a dozen or more recovered non-human craft.”

AARO’s historical review found no empirical evidence supporting these claims. Critically, several of those relaying the information held second- or third-hand knowledge rather than direct access to the programmes described.

What would settle it

Physical material with a chain of custody and independent analysis, or programme documentation with a registry entry.

UnverifiedT1Report of the US Defense Attaché Office in Tehran to DIA, 23 September 1976 (IR 6 846 0139 76)

“The F-4’s weapons systems failed as the pilot attempted to fire on the object.”

The attaché’s message does report it: “THE PILOT ATTEMPTED TO FIRE AN AIM-9 MISSILE AT THE OBJECT BUT AT THAT INSTANT HIS WEAPONS CONTROL PANEL WENT OFF AND HE LOST ALL COMMUNICATIONS (UHF AND INTERPHONE).” It also says where the account came from: “ACTUAL INFORMATION CONTAINED IN THIS REPORT WAS OBTAINED FROM SOURCE IN CONVERSATION WITH A SUB-SOURCE, AND IIAF PILOT OF ONE OF THE F-4S.” The document confirms that the failure was reported, not that it happened, and nothing else in the file checks it: no system log or maintenance record can be opened. Reprinting an account of the incident in October 1978, the US Air Force Security Service wrote: “Although this incident is incomplete and cannot be substantiated, it contains food for thought.” See the case.

What would settle it

F-4 system logs and the maintenance record for the airframe after the sortie.

Cases

Tehran

UnverifiedT4Testimony of duty officers, given publicly from the 1990s onwards

“UAP caused Minuteman missiles to go offline at Malmstrom AFB.”

If this were documented the way it is narrated, it would be the single most important claim in the field. We have consistent officer testimony and we have the fact of the faults. We do not have a publicly available document joining the two on one timeline. Remembered correlation is not recorded correlation.

What would settle it

Maintenance logs and system records from the launch facilities for 16 and 24 March 1967, set against the security force logs.

UnverifiedT4A letter from Donald Menzel and Lyle Boyd of 19 February 1965; not in the file, known from Hynek’s reply and his trip report (Project Blue Book, NAID 302532129, images 33, 46)

“Socorro was a hoax by Socorro high school students.”

The files know the hypothesis from Menzel and Boyd’s letter of 19 February 1965, which is not among them. Hynek sums it up in his report on a trip of March 1965: the speeding car was “a deliberate decoy”, and hoaxers released “a balloon with a cardboard or aluminum flying saucer attached thereto” (Project Blue Book, NAID 302532129, image 46). In April 1964 the Air Force’s investigation had found “no indication that a hoax was being perpetrated” (image 13). Against the balloon Hynek wrote that “the wind was from the south, and the object went west” (image 46); that “both Chavez and FBI agent Byrnes must have been in on the hoax if we adopt the hoax hypothesis” (image 34); and that “No paraphernalia of a hoax were ever found” (image 46). The hoaxers the hypothesis needs are, in his papers, the town’s high school students: “I do not believe that the Socorro high school students could have kept a secret this long.” (image 47) One point runs the other way: as the object flew off, Zamora told the sheriff’s radio operator “It looks like a balloon.” (FBI file 62-HQ-83894, Serial 438, p. 15), while Chavez told Hynek “that Zamora never described the thing as looking like a balloon” (image 46). Within the files there is no apparatus, no admission and no reconstruction. See the case.

What would settle it

A documented admission, or a reconstruction that reproduces the marks, the flame and the sound. Hynek in 1965: “Sometimes confessions come years afterwards.” (Project Blue Book, NAID 302532129, image 38)

Cases

Socorro

UnverifiedT4DIRD of 11 March 2010 (DOW-UAP-D128), p. 23: “one assumes the cells DNA damage was secondary to ionizing radiation”; it rests on a MUFON UFO Journal article of November 1981 and “unpublished findings”

“The Cash–Landrum witnesses suffered radiation injuries from the object.”

The only document on the case that can be opened is a Defense Intelligence Reference Document of 11 March 2010 on injuries from field effects. It discusses the case as an example of injury: “Thus, in the Cash-Landrum case...one must assume that the RF and tissue heating, clearly responsible for the erythema and burns, did not cause the cell dyscrasia and subsequent gastrointestinal and malignant transformations; one assumes the cells DNA damage was secondary to ionizing radiation” (DOW-UAP-D128, p. 23). It sets the case beside one of three antenna engineers: “There are no significant differences in either the reported acute effects (symptoms) or the physician-observed (signs) between the case of three antenna engineers and the Cash-Landrum cases.” (p. 19) For the case itself it cites a MUFON UFO Journal article of November 1981 (p. 26) and “Unpublished HIPPA files” (p. 28), and it calls its clinical data “HIPAA - protected” (p. 15). It gives no date, place, object or helicopters, and this database no longer holds the case the claim belonged to (see the withdrawn entry). No medical record or other document that would let the injuries or their cause be checked can be opened.

What would settle it

The clinical data the DIRD relied on: “Unpublished HIPPA files” (DOW-UAP-D128, p. 28), which it calls “HIPAA - protected” (p. 15).

UnverifiedT4Accounts from the Operação Prato period and later interviews

“Residents of Colares suffered injuries caused by UAP.”

The most heavily exploited and most poorly documented element of the case. No publicly available medical record permits the described symptoms to be attributed to any specific cause.

What would settle it

Medical records from clinics on the island for September 1977 – January 1978.

UnverifiedT5The standard reading of the Navy video

“The object in the GIMBAL video performs a 90-degree rotation.”

Ryan Graves, a pilot of the squadron, testified under oath in 2023: “The recording on the AT FLIR system shows a single object that rotates.” (printed hearing, p. 38) The Department of Defense, which released the recording in 2020, says the phenomena in it “remain characterized as ‘unidentified’”, and AARO lists it as an “Unresolved Case”. No document we can open measures the rotation or explains it, and none gives 90 degrees. See the case.

What would settle it

The full recording, which Graves says is classified, with the sensor pod’s data for each frame, and the radar data he saw at the debrief (p. 38).

Cases

GIMBAL

UnverifiedT5Narrative accompanying the footage circulated under the ship’s name

“The objects around USS Omaha entered the ocean.”

No document we can open names USS Omaha, and none says that any object entered the water. Release 05 of the Department of War has five recordings titled “Unresolved UAP Report, Pacific Ocean, 2019”, with no ship and no date beyond the year; for one of them, DOW-UAP-PR124, the description says only: “The area of contrast loses distinctiveness against the background.” Nothing ties these recordings to USS Omaha. This base no longer holds the case the claim belonged to (see the withdrawn entry).

What would settle it

A Navy record naming the ship, the time and the sensor, with the sensor data from the moment the object stops being visible.

UnverifiedT4An analytical hypothesis based on the character of the events

“The activity around USS Omaha was a drone swarm launched from a surface vessel.”

The logs and reports of other ships off San Diego in July 2019 do record drones: USS Rafael Peralta’s CIC log on 15 and 16 July, USS Paul Hamilton’s brief of 17 July and an incident in the Navy’s database dated 29 July (see Off San Diego, July 2019). That they were launched from a surface vessel has no source: the database says “Point of origin of all UASs is unknown.” No document we can open names USS Omaha (see the withdrawn entry).

What would settle it

Surface traffic data for the area on those nights.

UnverifiedT4Witness accounts of the ~21:00 episode

“A single enormous triangular craft passed over Phoenix.”

The decisive question is whether witnesses saw lights joined by one hull, or saw a formation of lights and closed a dark shape between them. The brain does this automatically. Without radar, or footage showing stars being occulted, it cannot be settled.

What would settle it

Radar data for the Phoenix area, 13 March 1997, 20:30–21:30.

UnverifiedT4Participant accounts collected mainly from the 2000s onwards

“The military secured the Westall site and ordered pupils to stay silent.”

Not confirmed by any document. An element of the narrative that appeared in testimony gathered more than thirty years after the event.

What would settle it

Unit logs for military formations in the Melbourne area, 6 April 1966.

UnverifiedT5A narrative built around the accounts of three primary witnesses

“The military captured a living non-human being at Varginha.”

The primary account is short and modest: three people saw something unusual. Everything else — the military, the hospital, the body, the covert transport — comes from layers added later by people who saw nothing themselves.

What would settle it

Hospital records and unit logs from Minas Gerais, January 1996.

UnverifiedT5The Scandinavian press from late May 1946, and Swedish Defense Staff spokesmen talking to the US Military Attaché, as the US Intelligence Review of 9 January 1947 reports (DOW-UAP-D099, pp. 18–19)

“The Ghost Rockets were Soviet missile tests.”

The press “openly attributed them to missiles fired by the U. S. S. R.”, and Defense Staff spokesmen told the US Military Attaché that “they definitely believed there were rockets over Sweden, and that they were launched by the Soviets from Peenemünde”; “However, they have not been able to produce any evidence to support these statements” (DOW-UAP-D099, pp. 18–19). The Defense Staff’s own communiqué of 10 October 1946, known only from that review, put “the great majority of the reported incidents” down to “celestial origin” (p. 19). The US analysts concluded: “The best evidence, at present, is that there have been only 2 or 3 real incidents, perhaps as many as 5 or 10, of low-flying missiles of the V-1 type. The high-altitude missiles reported seem definitely to have been meteors or fireworks.” (p. 20) A G-2 paper of 1950 says: “Careful investigation by the US MA and by an independent British team, failed to uncover any evidence to support the theory of Soviet missiles” (FBI file 62-HQ-83894, Section 5, pp. 156–157). No Swedish document is in the release.

What would settle it

The file “Swedish Incidents”, which Air Materiel Command understood in January 1948 to be held at Air Force headquarters (DOW-UAP-D100, p. 152); the findings of the US Military Attaché and of the British team (FBI file 62-HQ-83894, Section 5, p. 157); the Swedish Government’s report of 1947 and the Defense Staff’s files and communiqués; the evidence behind the review’s “2 or 3 real incidents”; an analysis of the “nonmetallic slag”; Soviet test records for 1946. None of them is in the release.

UnverifiedT1Allied air intelligence at the time: A.D.I.(K) of the Air Ministry, 17 February 1945 (“Flak Bombe”), and the Air Ministry, 13 March 1945 (Me 262s and flak rockets), in SHAEF file 37153 (RG 331, pp. 10, 2)

“Foo fighters were an enemy weapon.”

No document in the releases shows what the lights were. The Air Ministry wrote on 13 March 1945: “A few of the alleged aircraft may have been Me. 262 and for the rest, flak rockets are suggested as the most likely explanation”, and in the same letter: “The whole affair is still something of a mystery and the evidence is very sketchy and varied so that no definite and satisfactory explanation can yet be given.” A.D.I.(K) thought on 17 February that a CX report SHAEF had sent “probably refers to ‘Flak Bombe’”; neither that report nor the A.D.I.(K) report it cites is in the file. SHAEF passed the Air Ministry’s view on with: “It is regretted that no further, or more definite, information can be given.” In 1953 the CIA’s scientific panel heard that the exact cause or nature of foo fighters “was never defined” (CIA-UAP-002, PDF p. 18). That “It became clearly apparent at the end of the war that it was nothing of the sort”, and that German pilots took the lights for a US weapon, rests only on the COMETA report of 1999, which gives no source (pp. 75–76 of the file).

What would settle it

Documents not in the release: A.D.I.(K) Report No. 562/1944, paragraphs 128–129, and the CX report SHAEF sent on 14 February 1945; the squadron’s full sortie reports and any record of the crews’ calls to GCI control; the Bomber Command crews’ reports the Air Ministry mentions; and the findings, if any, of SHAEF’s Scientific Investigation Division (“Mr. Robertson”: the documents do not say whether he is the H. P. Robertson who chaired the CIA panel in 1953).

UnverifiedT4A CIA History Staff study by Gregory W. Pedlow and Donald E. Welzenbach, The Central Intelligence Agency and Overhead Reconnaissance: The U-2 and OXCART Programs, 1954–1974 (1992), pp. 72–73 (CIA-UAP-003)

“U-2 and OXCART flights accounted for more than half of all UFO reports in the late 1950s and the 1960s.”

The sentence is in the CIA’s own history of the two programmes, with a qualifier the circulating version drops: “U-2 and later OXCART flights accounted for more than one-half of all UFO reports during the late 1950s and most of the 1960s.” The history was written by the CIA History Staff between 1983 and 1992, and the only support it gives is footnote 49: “Information supplied by James Cunningham to Donald E. Welzenbach (U).” Cunningham was the U-2 project’s administrative officer from May 1955; Welzenbach is one of the two authors. It cites no number of reports, no breakdown by year and no document. The text does name a mechanism, that “BLUE BOOK investigators regularly called on the Agency’s Project Staff in Washington to check reported UFO sightings against U-2 flight logs”, but no record of those checks is cited either. The same paragraph says the letters about such sightings “in turn, led to the Air Force’s Operation BLUE BOOK”, and this release puts Blue Book first: the CIA’s scientific panel received “Project BLUE BOOK” status reports in January 1953 (CIA-UAP-002), a CIA memorandum of December 1953 refers to “ATIC’s project (Bluebook No. 10073)” (CIA-UAP-007), and Blue Book’s Special Report No. 14 is dated 5 May 1955 (CIA-UAP-015), while the history itself dates the first planned U-2 flight to 4 August 1955. That error does not disprove the figure, but the figure rests on one participant’s account set down decades later, in a paragraph whose only statement that can be checked in this release is wrong.

What would settle it

Blue Book’s case files for the late 1950s and the 1960s matched against U-2 and OXCART flight logs, or any record of the checks the text says Blue Book asked the Agency’s Project Staff to make.

UnverifiedT3Ryan Graves under oath (2023, printed hearing, pp. 11, 17) and in his written statement

“East Coast pilots were seeing UAP almost daily.”

Graves speaks of briefings, not of a count of sightings: “Soon these encounters became so frequent that aircrew would discuss the risk of UAP as part of their regular preflight briefs.” (printed hearing, p. 11); his written statement: “The sightings were so frequent that they became part of daily briefs.” The Office of Naval Intelligence wrote of “near daily incursions” in briefings of February and March 2020, without naming a region or a year. The Navy reading room holds seven hazard reports from W-72 between June 2013 and April 2014; on 27 April 2014 the commander of VFA-11 wrote of “the third occurrence in five days, and the fourth in the last ten months observed by the squadron”. No count of reports for those years can be opened. See the case.

What would settle it

Report statistics from East Coast squadrons for 2014–2015.

UnverifiedT4Participant accounts given over subsequent decades

“USAF personnel touched a landed craft and saw symbols on its hull.”

Lt Col Halt’s memorandum of 13 January 1981 — the primary document — describes lights, ground indentations and elevated radiation readings. It does not describe a landed craft, touching a hull, or symbols. All of those appear in the later layer.

What would settle it

Nothing — the primary document exists and is public. The gap between it and later accounts is itself data.

UnverifiedT4MOD correspondence and accounts of how the material was handed over

“The Ministry of Defence lost six negatives from Calvine.”

The negatives went to a state institution and have not been located. That much is established. What is not established is whether they were lost by accident or destroyed under routine records disposal. The effect is the same: the case is open because the evidence disappeared into an administration.

What would settle it

Locating the negatives. Without them, grain and depth-of-field analysis cannot be performed.

Cases

Calvine

UnverifiedT4A narrative developed around the documented search operation

“An underwater recovery operation was conducted at Shag Harbour.”

Canadian government documents confirm the report, the multiple sightings, the rescue operation, the absence of any missing aircraft, and the formal closure without identification. They confirm nothing from the narrative about a recovery, a military operation, or submarines.

What would settle it

Royal Canadian Navy operational logs for October 1967.

UnverifiedT4Airport staff accounts

“The object over O’Hare punched through the cloud layer, leaving a hole.”

Fallstreak holes are a known phenomenon, produced when an aircraft passes through a layer of supercooled droplets. That explains the hole; it explains the object seen beforehand less well. The case was never investigated: nobody checked the radar record of one of the world’s most closely monitored airports.

What would settle it

O'Hare radar data for 7 November 2006 — if it still exists.

Cases

O'Hare

UnverifiedT4Observations reported over subsequent years

“The lavender at Valensole failed to grow normally for years afterwards.”

Ground marks were documented by the gendarmerie the same day and are solid. The multi-year growth anomaly was observed and reported but never studied under controls, with sampling and comparison plots. That gap is precisely what GEPAN closed sixteen years later at Trans-en-Provence.

What would settle it

A controlled agronomic study at the time. It is no longer possible.

UnverifiedT3Public statements by the pilot, given decades later

“A Peruvian Su-22 fired cannon at a UAP without effect.”

One of very few documented instances anywhere of a military aircraft firing on a UAP, which is significant as state behaviour. But nothing instrumental was published — no radar record, no gun camera footage, no unit documentation. A large high-altitude balloon accounts for the shape, the station-keeping, the ineffective fire at long range and the eventual climb beyond the aircraft’s performance.

What would settle it

Peruvian Air Force unit records and any gun camera film from the sortie.

UnverifiedT5Boston Traveler, 25 October 1965: the story of an abduction “has been related by a New Hampshire couple under clinical hypnosis” (Project Blue Book, NAID 28994718, image 30)

“Hypnosis recovered the Hills' memory of being taken aboard a craft.”

No record of the sessions can be opened today, and the Air Force’s file on the case holds the story only in the press. Look printed parts of the tapes in 1966; in its editors’ note the psychiatrist, Dr. Benjamin Simon, says: “Nothing is absolutely proved to me regarding the alleged ‘abduction.’” (Look, 4 October 1966, p. 45; NAID 28994718, image 13), and a page of the second instalment is headed “Dr. Simon accepted a sighting, but found the abduction improbable” (Look, 18 October 1966, p. 118; images 9 and 8). The Air Force’s report of 21 September 1961, taken by telephone, describes a sighting and nothing of an abduction (images 39–41).

What would settle it

The recordings of the sessions and Dr. Simon’s notes, if an archive holds them. The University of New Hampshire’s Betty and Barney Hill Collection (MC 197) is the place to check; what the files hold is set out in the case.

UnverifiedT1Analyses under the Soviet Academy of Sciences UAP programme

“Soviet academy laboratories found anomalous residue at Dalnegorsk.”

Sampling and analysis did take place under a state programme, which puts the case structurally close to Trans-en-Provence. The critical difference is publication: the analytical reports have never been comprehensively released in a form outside researchers can examine. Dalnegorsk also sits in one of Russia’s most intensively mined regions, which weakens the prior on unusual metallic residue considerably.

What would settle it

Publication of the original laboratory reports with sample provenance, and independent re-analysis.

UnverifiedT1AAWSAP Statement of Objectives, 18 July 2008: the term “is anticipated to be 5 years”

“AAWSAP was a five-year programme.”

The phrase is real, and it is a forecast: “a base year of 12 months from date of award plus four (4) 12 month option years.” What the released documents show is two funded years. The base year ran from 22 September 2008; the first option year was exercised in September 2009 and funded in February 2010; the last released modification, P00005, extends the period of performance to 21 December 2010 and says “No funding is required for this extension.” No document in the set exercises a second option year. Our records registry does list two DIRD reports from the same release dated January 2011, after that end date, so either the set of modifications is incomplete or reports were dated after the period closed. The documents do not say which.

What would settle it

Any modification after P00005, or the contract’s close-out record.

UnverifiedT5Public discussion of AAWSAP

“AAWSAP was handed to Bigelow without competition.”

The documents show a solicitation, not a sole-source award. Solicitation HHM402-08-R-0211 was issued on 1 September 2008 as a request for proposals, marked “unrestricted”, with offers due at 2:00 pm on 10 September; the award to Bigelow Aerospace Advanced Space Studies followed on 22 September. Nine days is short, and the objectives asked for prime-contractor experience within the past seven years in the “analysis, design, construction, and flight testing of high performance aircraft and/or satellites”, which narrows the field. How many offers arrived is not in these documents, and that is the number the claim turns on.

What would settle it

The contract file’s record of offers received and the source-selection decision.

UnverifiedT5Public discussion of AAWSAP

“AAWSAP funded research at Skinwalker Ranch.”

The contract does not say so. The Statement of Objectives says “the work under this contract shall be performed at the Contractor’s facility” and names no property; the contractor’s addresses in the documents are 1899 W Brooks Ave in North Las Vegas and 4640 S Eastern Ave in Las Vegas. Nothing in the seven documents mentions a ranch or any field site. That does not refute the claim, because where a contractor chose to work is not something an order form records. It means the claim cannot rest on the contract.

What would settle it

The research reports and the BAASS proposal, which would show where the work was done.

UnverifiedT5Public discussion of AAWSAP

“AAWSAP was shut down because of what it found.”

The documents show a cut, not a closure, and give no reason for either. P00001 priced the first option year at $25,000,000; P00002 funded it at $11,948,810 and directs that the “impacts to deliverables as a result of reduced funding” and the “technical risks of reduced funding” be identified. The attachment that sets those out was not released, and no document states why the funding was reduced. The last released modification extends the work to 21 December 2010 at no cost; nothing in the set terminates the contract or declines a further option. Whatever ended the programme is not in these papers.

What would settle it

The P00002 attachment, any later modification or close-out record, and the DIA’s funding decision on the second option year.

Open problemT4James E. McDonald, “Astronautics & Aeronautics”, July 1971, built on the 1957 file and on interviews with the crew in 1969

“The 2.8 GHz signal proves the object emitted its own radar.”

Open, and the figure is not the one from 1957. The wing’s message of 1957 gives “FREQUENCY 2995 MC TO 3000 MC; PULSE WIDTH OF 2.0 MICRO-SECONDS; PULSE REPETITION FREQUENCY OF 600 CPS” and reads the signal’s movement up the direction-finding scope as “AN AIRBORNE SOURCE” (Project Blue Book, NAID 28970538, images 41–42). 2,800 is the operator’s memory, as McDonald reports it: “his recollection was that the frequency was near 2800 mcs” (image 15). In 1957 the Air Technical Intelligence Center’s AFCIN-4E1 wrote that the signals “have all the characteristics of ground radar equipment, and in fact are similar to CPS-6B. This office knows of no S-band airborne equipment having the characteristics outlined.” (image 7) In 1971 Philip J. Klass attributed them to ground radars near Biloxi and at Duncanville (images 21–38) and quoted the operator: “I do not believe any UFO was emitting these signals.” (image 36) In 1972 the Chief of the Historical Research Division wrote to Klass that his explanation “provides a reasonable explanation”, after “I lack the technical background for full appreciation of your detailed account of the RB-47 UFO case” (image 39). Whether the source was airborne can be settled only against the aircraft’s positions and the ground radars’ records, and neither is in the file. See the case.

What would settle it

The ELINT records of the flight and the aircraft’s position minute by minute, set against the ground radars of the region.

Open problemT4A pattern recurring across cases over several decades

“UAP cause electromagnetic interference in onboard systems.”

One of the few motifs that recurs independently in Tehran 1976, at Nimitz in 2004 and at Levelland in 1957. For Nimitz the only account that can be opened is Fravor’s, relaying the crew of the sortie after his: “My crew that launched after we landed experienced significant jamming to the APG–73 radar” (2023 hearing, printed record, p. 21). None of them, however, supplies a machine record documenting the effect. We have observed system behaviour and operator interpretation, not a causal recording. For Tehran 1976, DIA’s evaluation of the US attaché’s report notes: “Similar electromagnetic effects (EME) were reported by three separate aircraft.” The report it rates was, by its own account, “OBTAINED FROM SOURCE IN CONVERSATION WITH A SUB-SOURCE, AND IIAF PILOT OF ONE OF THE F-4S”, and in its “MIJI Quarterly” of October 1978 the US Air Force Security Service wrote: “Although this incident is incomplete and cannot be substantiated, it contains food for thought.” At Levelland, on the night of 2/3 November 1957, a student told the Air Force that “the ampmeter on SOURCE's automobile registered discharge for a moment”, after which the engine cut out and the lights and radio went out; no vehicle was examined (see the claim about engines).

What would settle it

Even one case with a preserved system log correlated in time with range to the target.

Open problemT1Parts One and Two of the Air Force’s field report AISS-UFOB-386-57 of 8 November 1957, and the 686th ACWRON’s message of 4 November 1957 (Project Blue Book, NAID 28972840, images 62, 65 and 7–9)

“UAP stop vehicle engines.”

The Air Force’s field report on Levelland has two drivers whose engines stopped. In Part One a student on Texas highway 116 saw his ammeter register a discharge, then “the engine of the automobile began cutting out as if it were not getting any gas. After it had quit running, the lights and car radio went out.” When the object left, “the lights and radio of the car came on and the motor started with no difficulty.” (NAID 28972840, image 62) In Part Two a barber’s truck engine and lights went out as an object passed over him and came back when it was gone (image 65); the preparing officer wrote: “This observer's account of the sighting cannot be relied upon.” (image 78) A message of the 686th ACWRON has the same sequence: “THREE PEOPLE OBSERVED THE OBJECT FROM AUTOMOBILES AND WHEN THE OBJECT ROSE ABOUT 200 FEET THE ENGINE AND LIGHTS WOULD AGAIN WORK.” (image 8) In the material that can be opened nobody examined a vehicle from Levelland: the report’s list of checks has none (image 75). Two summaries speak of a faulty distributor and of faulty ignition systems but name no vehicle (images 2 and 36); the only truck the files examine is at Kearney, Nebraska, and we read those sentences as carried over from there (image 18; NAID 28972949, image 11). See the case.

What would settle it

A record of a stalled vehicle examined soon after the event, as the Air Force did at Kearney; for Levelland the files hold none, and the vehicles can no longer be examined.

Open problemT4A pattern running from the 1948 green fireball wave to AARO reporting

“UAP cluster around nuclear installations.”

The pattern is real in the reporting data. Its interpretation is not settled: nuclear installations are simultaneously the places with the densest observer coverage, the best sensors and the lowest threshold for reporting an anomaly. The effect may be a property of the phenomenon or a property of the observation system. The FBI's file on Oak Ridge shows both sides. In 1949 Colonel C. D. Gasser, the Air Force engineering officer at the site, said that insofar as was known to him “there was absolutely no connection between these missiles and the fact that they were observed close to Oak Ridge, Tennessee. He stated that this was perhaps, and probably, a matter of coincidence and they were seen in this area merely as they were seen in forty-six of the forty-eight states” (FBI file 62-HQ-83894, Section 4, p. 88). Against that, an Air Force radar tracked eleven objects over the plant on 12 October 1950, and the report ends: “NO REASONABLE EXPLANATION FOR RADAR READINGS YET DEVELOPED ALTHOUGH OPERATORS ARE EXPERIENCED RELIABLE PERSONNEL AND RADAR SET IS IN PERFECT OPERATING CONDITION” (Section 6, p. 92); the follow-up is not in the release. Our own reading of the rest of that file: a dense net of watchers, the plant's patrol, ground observers, a radar station and fighters on call, produced reports that on checking came back as a star, a reflection or an unreliable set.

What would settle it

Comparing report density at nuclear installations against comparably staffed non-nuclear sites, controlling for observer count and sensor class.

Open problemT3Ryan Graves under oath (2023, printed hearing, pp. 10, 17), who speaks of a radar upgrade without naming the radar

“The rise in reports followed the radar upgrade to AESA.”

“AESA” appears in no document we can open. Graves testified: “After upgrades were made to our jet’s radar systems, we began detecting unknown objects operating in our airspace. At first, we assumed they were radar errors” (printed hearing, p. 10), and “in the 2014 to 2015 time period, anyone that had upgraded their radar systems were seeing these objects” (p. 17). The Naval Intelligence Activity wrote in 2021: “Airspace increasingly cluttered, sensors increasingly sensitive = Increased UAP encounters”; the ODNI the same year, of sightings clustered around training grounds: “this may result from a collection bias as a result of focused attention, greater numbers of latest-generation sensors operating in those areas, unit expectations, and guidance to report anomalies.” A better sensor may detect what was always there, or new artefacts and prosaic objects; both readings predict the same rise, and no document gives report rates before and after the upgrade. See the case.

What would settle it

Comparing report rates in squadrons before and after the upgrade, controlling for flight hours.

Open problemT1Photometric analyses, including within the Condon Committee

“The McMinnville photographs are authentic and show a large, distant object.”

Photometric analysis is consistent with a large distant object — and does not exclude a model suspended on a line. The same frame fits an object 30 cm across at 5 metres and a 20-metre object at a kilometre. Photometry narrows the range; it does not close it.

What would settle it

Re-analysis of the original negatives by contemporary methods.

Open problemT4Vargemezis et al., Journal of Applied Geophysics 226 (2024) 105398, which suggests “a provisional mechanism” with a geological basis

“The Hessdalen lights are a plasma phenomenon with a geological basis.”

The geological part has a source. A VLF survey of the valley found conductive zones “mainly related to mineral deposits (mainly sulfides)”, which trace a ring along a gabbro intrusion; its authors propose that strong electric fields rising from them, with gas such as radon, could produce lights by ionisation. They call it “a provisional mechanism” and write that “Further statistical examination of long-term geophysical records will be necessary for assuming a further accurate interpretation.” The paper records no light. That the lights are a plasma is established by nothing we have read: the 1984 report quotes an NDRE radar expert only conditionally, “If this isn’t a reflection of a solid object, but only gas in the air, the gas has to be locally and strongly ionised”, and its campaign found no connection between the lights and movements in the ground. See the case.

What would settle it

Long-term geophysical records matched against recorded lights, as the 2024 paper itself calls for, and spectra of a light that cannot be explained.

Open problemT4The 1896–97 airship wave and later waves

“Thousands of consistent witness descriptions indicate a real object.”

In 1896 thousands of people consistently described a cigar-shaped airship with a searchlight and propellers — a machine that did not exist; powered flight was seven years away. Consistency within a wave tracks the technology the culture is currently anticipating. It is weak evidence for an object and strong evidence for a shared expectation.

What would settle it

Nothing — the 1896 wave is itself the control experiment.

Open problemT1Brazilian Navy examination of the negatives, endorsed by the President

“The Trindade photographs were authenticated by the Brazilian Navy.”

The Navy examined the negatives and stated it had no reason to doubt them — a meaningfully stronger position than “unidentified”, and a head of state backed the release. But the photographer had a background in trick photography, and the fundamental limit applies: without a known range, the image fits a small nearby object and a large distant one equally.

What would settle it

Modern re-analysis of the original negatives, if they can be located.

Open problemT1Verbatim transcript of the radio exchange, 21 October 1978

“Valentich disappeared while describing an object above his aircraft.”

The transcript is a primary document and immune to memory drift — we know exactly what he said. The aircraft was never found and the investigation closed with cause unknown. The leading hypothesis is spatial disorientation with the pilot inverted, seeing his own lights reflected in the sea; it fits parts of the transcript well and others poorly.

What would settle it

Recovery of the wreck, which would establish the aircraft’s attitude and condition.

Open problemT1Colorado multi-agency task force report, January 2020

“Large drones flew nightly grid patterns over Colorado and nobody identified the operator.”

The task force found most reports were misidentified aircraft, planets and stars, amplified by media coverage — well supported, and matching the Ladakh pattern. It did not identify what produced the initial cluster of credible law-enforcement reports before the media wave began. Strip out the exotic vocabulary and this is the shape of the modern problem: unattributed aircraft, a lot of noise, a small unresolved core, and no agency with both the authority and the sensors to settle it.

What would settle it

FAA registration and flight data for the region during the reporting window.

Open problemT2AARO consolidated annual report on UAP for fiscal year 2025

“Around a hundred objects and two surface craft were tracked together off Virginia.”

The report describes it as reported by US Navy assets: roughly a hundred airborne objects and two probably uncrewed surface systems, and records the case as under active investigation with the reporting unit. It is the single maritime-domain report in a year of 319, which is why it stands out. Note what the report does not say. It does not call the objects anomalous, and a coordinated group of drones and unmanned surface vessels in a busy naval operating area is the ordinary reading. The case is worth following because it is open in an official document, not because it is unexplained in the popular sense.

What would settle it

The sensor record behind the report: track files with continuity and timestamps, and whatever the investigation concludes about attribution.

EstablishedT1The FBI’s file (Serial 438 and Section 9) and the Blue Book case file (Holder’s plans, Moody’s report, the soil analysis)

“Physical landing traces remained at Socorro.”

Established as marks in the ground, not as their cause. The FBI agent who reached the site that evening described four depressions “approximately sixteen by six inches rectangular” and three circular marks “as if a jar lid had gently been pushed into the sand” (FBI file 62-HQ-83894, Serial 438, p. 3). Capt. R. T. Holder measured the marks while the agent was “placing rocks around the four earth indentations and around one other mark at the site” (Section 9, p. 237); his plans are in the Blue Book file (Project Blue Book, NAID 302532129, images 50–58). The measuring and the marking were done together, by the two men, so the FBI’s sketches and the Blue Book’s plans are not independent records. The only photographers the files name are from the state police, Sgt. Chavez with his polaroids and a trooper with his slides (images 63–64), and neither file holds those photographs. The Air Force’s soil analysis found “no significant differences in elemental composition between the different samples” (image 73). What is established is that the marks existed and what their dimensions were, not what made them. See the FBI report of 8 May 1964, the teletypes and airtels of April 1964 and the case.

What would settle it

Hynek’s condition of 1964: that “the device finally selected as the culprit, be indeed capable of producing the marks observed” (Project Blue Book, NAID 302532129, image 71). Also the original photographs, and the samples, among them the charred material the FBI kept in Albuquerque.

Cases

Socorro

EstablishedT1GEPAN technical note no. 16 (CNES, March 1983), section 7, written by Dr M. Bounias of INRA Avignon-Montfavet

“Graded biochemical changes were found in plants at Trans-en-Provence.”

Confirmed as a laboratory finding. In GEPAN’s technical note no. 16 (March 1983; the list of GEPAN’s notes in COMETA gives it as the Trans-en-Provence case), Dr M. Bounias of INRA reports that wild alfalfa taken 1.5 m from the centre of the trace the day after the sighting had, against plants taken 20 m away, chlorophyll A down 33%, β-carotene down 50 to 57% and, in young leaves, violaxanthin down 80%. In the series taken from the centre outwards, most of the changes varied with distance; that full series was taken 40 days after the sighting, after heavy rain. The note establishes changes graded with distance, not their cause or their link to the sighting: knowledge of plant damage was “trop parcellaires pour que l’on puisse fournir dès à présent une interprétation précise et unique” (too fragmentary to give, for now, a precise and single interpretation), and “Reste à savoir si cela correspond bien à la description fournie par le témoin” (it remains to be seen whether this matches the description the witness gave). See the case.

What would settle it

The samples, if they were kept (the note does not say), analysed again, and the further plant analyses Bounias described as under way in March 1983.

EstablishedT1FOIA request for FAA radar data, 2008

“Independent researchers obtained the state’s raw radar data and ran their own analysis.”

Confirmed, and important as a precedent. The result was mixed and valuable precisely for that reason: the data overturned the base’s first official position, while also explaining a substantial share of the sightings as F-16 flights and flares. This is the working model the whole field should aim at.

What would settle it

Nothing — the data is public.

EstablishedT2Base statements before and after the radar data was released

“The air base initially denied its own aircraft were flying.”

Confirmed. The base denied it, then corrected its position once the FAA data was presented. Relevant to how much weight first official denials deserve in other cases — but equally proof that correction follows when someone produces data.

What would settle it

Nothing — both versions of the statement are documented.

EstablishedT2Press conference by Brazil’s Air Minister, May 1986

“Brazil scrambled fighters against multiple unidentified targets in one night.”

Confirmed publicly at ministerial level within days of the event — internationally almost unprecedented. Paradoxically this made the case far less famous than Rendlesham, about which the government said nothing.

What would settle it

Nothing as to the intercepts. The nature of the targets remains undetermined.

EstablishedT1AARO annual report listing the case as active

“Around 100 aerial objects and two surface systems were observed off Virginia.”

Confirmed as the content of an official report. The case remains under analysis. The surface-system category deserves separate attention — until 2024 practically all UAP discussion concerned aerial objects, and for that category neither procedures nor a historical corpus yet exist.

What would settle it

Completion of the AARO analysis and publication of the result.

EstablishedT1Laboratory tests in Ottawa reported in the RCMP Commissioner’s telex of 24 July 1967, and the survey of the site by S. E. Hunt of the Radiation Protection Division (memorandum of 13 September 1967)

“Soil at the Falcon Lake site was radioactive.”

Established, with limits the files spell out. The samples first found radioactive, soil, a steel tape and pieces of his shirt, were collected and taken from the site by Michalak and Gerald Hart in June 1967, though the RCMP had asked him not to remove evidence (RCMP report of 10 August 1967, p. 1); their activity was “up to approximately 0.54 µCi of Ra226 or its equivalent” (Hunt, p. 1). At the site, with the RCMP and the RCAF present, Hunt found a smear of contamination “about 0.5 x 8.0 inches” by a crack in the rock: “The whole contaminated area was no larger than 100 squaree inches” (p. 3); the RCMP recorded it as radium 226 (p. 7). In May his skin, undershirt and cap had been checked and “no radio-active material was found” (RCMP report of 26 May 1967, p. 4). Hunt left the origin “yet to be determined”; Peter M. Millman of the National Research Council judged in 1969 that “all the radioactivity observed could well have been produced by finely crushed uranium ore”, and that it was “highly probable” for all of it.

What would settle it

The final analysis of the Radiation Protection Division in Ottawa, which Hunt and the RCMP were still waiting for; the second analysis at the Winnipeg General Hospital, “to try and determine the isotope by its rate of decay” (Hunt, p. 4); and the samples Barry Thompson sent to APRO in Tucson. None of them is in the files.

EstablishedT4Admissions and interviews with the pilots who flew the formations

“Thousands of witnesses reported a single huge craft that was actually a formation of light aircraft.”

The pilots admitted flying light aircraft in close formation with modified lighting on those nights. Thousands of people, police officers included, reported a single enormous silent craft occulting the stars. This is the closest thing the field has to a calibration measurement for mass sightings, and it shows the intuition “so many people cannot all be wrong about a solid craft” is simply false.

What would settle it

Nothing — the participants confirmed it. A residual set of nights without formations was never separately resolved.

EstablishedT2Airport and civil aviation statements, July 2010

“A major Chinese airport suspended operations over an unidentified object.”

The operational disruption is confirmed: flights were diverted and delayed. Everything about the object is not. Authorities appeared to indicate a military explanation without providing one — the Petrozavodsk pattern, where a state’s own classified activity generates an unexplained phenomenon and the explanation is withheld for unrelated reasons.

What would settle it

Release of the radar record, or an explicit official determination.

EstablishedT2Indian Institute of Astrophysics / DRDO investigation findings

“Several hundred military sightings in Ladakh were Jupiter and Venus.”

Confirmed, with an elegant check: the sightings stopped when the planets moved out of that part of the sky. Two military organisations on alert along a contested nuclear frontier logged several hundred sightings over six months and suspected adversary drones. The Blue Book explanation everyone sneers at is sometimes simply correct.

What would settle it

Nothing — the correlation with planetary positions closes it.

Cases

Ladakh

EstablishedT2NORAD statements on radar filter adjustment, February 2023

“The three objects shot down in 2023 became visible because radar filters were loosened.”

Confirmed and, for this field, decisive. Air defence radar had long been tuned to discard exactly the signature most UAP reports describe: slow, small, high, non-manoeuvring. When the filters came off the sky immediately filled with objects nobody had been seeing. The same fact supports a deflationary reading of the modern UAP surge and the claim that the sky was never properly monitored — anyone citing it should say which they mean.

What would settle it

Nothing — NORAD stated it directly.

EstablishedT1The default reading of night-sky reports, from witnesses and from aggregators alike

“A bright, brief flash high in the sky, moving with no sound, is unexplained.”

Sunlight reflecting off a satellite produces exactly this signature. AARO distinguishes two mechanisms: specular reflection off mirror-like panels and antennas, giving an intense flash of a second or two, and diffuse reflection off many satellites launched together, giving the trains seen after a Starlink deployment. In the year to 30 May 2025 this single mechanism accounted for 238 resolutions, more than twice the 114 cases AARO closed by every other means combined. It is now the largest identified source of UAP reports on record.

What would settle it

Nothing further: the mechanism is established. What it does not do is settle any individual report, which still needs the observer’s time, bearing and elevation checked against the catalogue of orbits and the sun angle.

EstablishedT1Obligations recorded in contract HHM402-08-C-0072 and its modifications, 2008–2010

“AAWSAP cost $22 million.”

Established, to the dollar: $21,948,810. The base year was $10,000,000 in six line items, 22 September 2008 to 21 September 2009. Modification P00002 of 2 February 2010 funded the first option year at $11,948,810 and states that “the total obligated amount for this contract is $21,948,810.00.” One refinement matters. P00001 had priced that option year at $25,000,000, so the second year received less than half of its price, and P00002 asks for the “impacts to deliverables as a result of reduced funding”. Twenty-two million is what was obligated, not what was planned.

What would settle it

Nothing further for the obligation. Payment records would show what was actually disbursed, which the contract documents do not.