What this disclosure says.

The Unresolved Residue

The pattern starts before the phrase UAP had any official life. In January 1947, War Department intelligence reviewed the 1946 Scandinavian "Ghost Rockets" wave and did something more careful than either dismissal or belief. It separated noise from residue. Reports began over southern Sweden in late May 1946, spread to Finland and Denmark in June, and increased sharply over Sweden by July, with additional reports from Norway. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.3]

The reports were not internally tidy. The two most common descriptions were "a ball of fire with a tail" and a "shiny cigar-shaped object." [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.3] Reported altitudes ran from treetop height to 160,000 feet, and reported speeds ran from 65 miles per hour to lightning fast. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.3] That spread matters. It is the kind of spread official reviewers often use to sort witness reports into buckets: misread sky events, bad estimates, rumor, and the smaller set that keeps its shape after review.

The Ghost Rocket review did not treat Swedish military concern as proof. Swedish Defense Staff spokesmen privately told the U.S. Military Attache that they definitely believed rockets were flying over Sweden and that the Soviets were launching them from Peenemunde, but the Swedish side produced no supporting evidence. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.5] No U.S. military or naval personnel in Sweden had seen fragments, impact points, or other direct evidence proving guided missiles had appeared over Sweden. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.5] The file is blunt about the problem: "To arrive at any definite conclusion from the conflicting evidence available on these reported missiles is impossible." [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.5]

Then comes the residue. The same review judged the high-altitude missile reports to have been meteors or fireworks. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.6] But it did not erase the whole wave. Its final assessment was that the best evidence supported only 2 or 3 real incidents, perhaps 5 or 10, involving low-flying V-1 type missiles. [DOW-UAP-D099, Intelligence Review of “Ghost Rocket” Incidents, 1947 p.6] That is the key move. Most of the wave collapses. A small remainder does not.

Project SIGN shows the same habit one year later, now inside the Air Materiel Command inquiry into unidentified flying objects in the United States. Headquarters USAF said Project SIGN had been established after a December 30, 1947 letter from the Director of Research and Development. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.1] Headquarters also stated that some type of flying object appeared to have been observed, while its identification and origin were not discernible to Headquarters. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.1]

This was not framed as folklore collection. USAF tied the investigation to national defense needs and possible countermeasures if the objects proved domestic or foreign in origin. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.1] It also warned that press pressure would soon make silence unacceptable and asked AMC what the Air Force should tell the press. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.1]

AMC reported that it had studied approximately 180 unidentified flying object incidents through initial reports, mailed checklists, field-agency interrogations, and personal investigations. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.7] The reported objects fell into categories: flat discs, cigar-shaped aircraft, spherical or balloon-shaped objects, and balls of light. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.7] AMC identified some reports as weather or upper-air scientific balloons and others as astro-physical phenomena, including Venus. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.7]

Again, the sorting did not close the file. AMC said some reports still had no reasonable everyday explanation, but no physical evidence had been obtained. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.8] It also said the reported discs, cigar-shaped objects, and balls of light did not appear to be of domestic origin based on information available to Headquarters. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.8] The same page includes the sentence that later debates tend to isolate from its caution: "The possibility that the reported objects are vehicles from another planet has not been ignored." [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.8] In context, that is not a verdict. It is an admission that the ordinary bins had not captured everything.

AMC's proposed public posture was cautious. It recommended withholding detailed press information about unidentified cases and, if forced to comment, stressing weather balloons, astral bodies, and continued investigation. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.9] It also stated that there was not yet conclusive proof that unidentified flying objects, other than known balloons, were real aircraft. [DOW-UAP-D100, Air Materiel Command Report on Unidentified Flying Objects, 1947-1948 p.9] That is not the same as saying there was nothing there. It is the bureaucratic shape of uncertainty: identify what can be identified, refuse the leap, preserve the unresolved set.

The 1953 film analysis sharpens the pattern because the evidence was not only testimony. The Officer in Charge of the U.S. Naval Photographic Interpretation Center sent the Director of Naval Intelligence a progress report on movies of unidentified objects. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3] The Utah material consisted of approximately 30 feet of processed 16mm color motion picture film taken on July 2, 1952. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3] The Utah film was in very poor condition, so the center duplicated it before analysis to preserve the original material. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3]

The analysts did not merely watch the footage and speculate. They divided the Utah film into three parts based on camera settings and motion, then plotted three definite groups of lights across the film. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.4] They used densitometric readings to compare luminosity, size, distance, and object density, while acknowledging limits caused by film duplication and equipment constraints. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.5] The majority opinion was that the images were light sources, but that did not account for the velocity or acceleration factors. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.6]

Under stated assumptions, the Utah film produced maximum and minimum velocities from 55 measurements of 2,457 miles per hour and 378 miles per hour, with acceleration values reaching 965 g and deceleration values reaching 1,479 g. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.8] For the Montana film, terrestrial objects provided control points, making velocity and acceleration determinations more reliable than the Utah calculations. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.8] Consulted astronomy and physics experts could not explain the objects as natural phenomena under the reported filming conditions and could not recognize them as man-made. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.9]

Worth sitting with: across these files, the unresolved category is not created by enthusiasm. It is what remains after reviewers subtract meteors, fireworks, Venus, balloons, poor evidence, bad film, weak controls, and public pressure. The residue is smaller than the story that surrounds it. But it is still there.

The useful part of the 1953 Navy film report is not that it solves the Utah and Montana cases. It does not. The useful part is that it shows an early government photo lab trying to measure the phenomenon in public-facing technical terms: camera footage, film condition, duplication loss, density readings, plotted tracks, velocity, acceleration, and the limits of the work itself. The report was a May 4, 1953 progress report from the Officer in Charge of the U.S. Naval Photographic Interpretation Center to the Director of Naval Intelligence, and it concerned motion pictures of unidentified objects. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3]

The Utah material was not a clean original handed to analysts in ideal lab condition. It was about 30 feet of processed 16mm color motion picture film shot on July 2, 1952. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3] The center said the film was in very poor condition, so it made a duplicate before analysis to preserve the original. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3] That matters because the report did not pretend the imagery had arrived as perfect evidence. It put the weakness near the front of the record.

The analysts then treated the Utah film as something that could be measured, not just described. They divided the film into three parts based on camera settings and camera motion, then plotted three definite groups of lights through the sequence. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.4] The digest preserves one of the report's plain technical observations: "Three det'inite groups of l i ghts were observed through out the film and plots were recorded as fol l ows:" [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.4] The spelling is damaged by the source text, but the method is legible. The center was not only asking what the lights looked like. It was asking where they moved, how their apparent positions changed, and what could be inferred from that track.

The report also tried to separate brightness from shape and motion. The center used densitometric readings to compare luminosity, size, distance, and object density, while acknowledging limits caused by film duplication and equipment constraints. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.5] The report's own working caveat is blunt: "Because of this situation only the largest readings obtained b scanning the objects were used." [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.5] That sentence is not a flourish. It is the kind of limitation that makes the document more useful, because it tells the reader where the measurement may be weak.

The majority reading was conservative in one sense and strange in another. The report said, "It is the majority opinion of the group conducting this analysis that these images a.re light sources." [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.6] But that conclusion did not close the case inside the report. The same page says the light-source explanation did not account for the velocity or acceleration factors. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.6] The same page also says, "There is no indication of' what kind of objects could have caused the images except that they must be of a construction, design, a nd material not commonly known ." [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.6]

That is the core tension. The images read as lights, but the motion math pushed the analysts past easy identification. The report described the Utah objects as apparently oblate or disk shaped and blue-white, with size estimates built on an assumed five-mile distance. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.7] Its preserved phrasing is more direct: "The shape of the objects appears to be oblate or disk shaped, c o~or; blue-white, and maximum and minimum size; 98 a nd 16 f eet ." [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.7] Those numbers depend on the assumed distance. They are not free-standing proof of 98-foot craft. They are a record of what the analysts calculated if that distance assumption held.

The velocity figures are more striking, and also assumption-bound. For the Utah film, the report computed maximum and minimum velocities from 55 measurements at 2457 mph and 378 mph, with acceleration values reaching 965 g and deceleration values reaching 1479 g under its stated assumptions. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.8] Those are not casual witness adjectives. They are measured outputs from a government photo interpretation center working from a degraded duplicate film. The correct reading is not that the numbers settle the identity of the objects. The correct reading is that the numbers explain why the analysts did not treat the case as ordinary lights moving across ordinary sky.

The Montana film gave the center something the Utah film lacked: better external anchors. The report said terrestrial objects in the Montana footage provided control points, which made velocity and acceleration determinations more reliable than the Utah calculations. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.8] That distinction matters. The report itself ranked its own evidence. Utah had dramatic measurements but weaker controls. Montana had reference points that made the motion analysis firmer. This is what disciplined UAP reading looks like before the modern acronym era: not one big claim, but a stack of unequal measurements.

The outside expert check did not identify the objects either. The report said consulted astronomy and physics experts could not explain the objects as natural phenomena under the reported filming conditions and could not recognize them as man-made. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.9] That is a narrow claim, but it is a real one. The experts were not declaring origin. They were saying the available explanations did not fit the reported conditions.

The final note is almost as important as the analysis. The center said the results were produced by the Photogrammetry Division of the Evaluation Department and did not necessarily represent the official attitude of the Navy or the center. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.3] The report also said the investigation was limited by a lack of proper equipment, money, and personnel. [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.9] Its own words are stark: "Because of the lack of proper equipment, mone y and personnel, the investigation was limited." [DOW-UAP-D098, Film Analysis of Unidentified Objects, 1953 p.9]

Worth sitting with: the 1953 record does not show a government lab waving away bad film. It shows a Navy photo interpretation center preserving a damaged 16mm source, plotting lights, measuring density, calculating speeds, consulting experts, and then naming the limits of its own tools. The institutional record supports a careful reading: before the modern UAP era, at least some official analysts treated photographic cases as measurable technical problems, not only as stories to be believed or dismissed.

Puerto Rico and the Intelligence Problem

The Puerto Rico file matters because it is not just a sighting report. It is an intelligence problem moving through controlled channels, with a pilot observation, Navy radar photography, a classified aircraft hypothesis, and a scientific review that did not make the easy explanation fit. The control sheet placed the file under BYEMAN controls for OXCART and marked it TOP SECRET, which means this was handled inside the security world built around CIA's own high-speed aircraft program. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.2]

That matters before the object even enters the story. OXCART was not a public UFO desk. It was the compartment around CIA's A-12 reconnaissance program, the same family of secrecy that made confusion with advanced Lockheed aircraft a live possibility. The document says access was restricted to people cleared for the specific projects, including OXCART. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.2]

The initiating memo went to the Assistant Director for Scientific Intelligence under the subject line "Unidentified Flying Object." [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.6] CIA Special Activities said OSI and OSA had received similar information about a UFO near Puerto Rico during November 18-24, 1964. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.6] The memo also says CINCLANTFLT had been told that CO Ramey identified the UFO as a YF-12A, but CIA believed ONI had been convinced it was not a YF-12A or a similar Lockheed aircraft. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.6]

That is the hinge. The first explanation was not swamp gas, Venus, or nervous pilots. It was one of America's own black aircraft. Then the compartment that knew those aircraft asked for a scientific review because the identification still did not hold. Special Activities asked OSI, possibly with OEL, to evaluate original Navy radar film and prints for any further information about a high-speed, high-altitude UFO. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.6]

The resulting review narrowed the case. Scientific Intelligence reported that a detailed OSI review found no high-altitude, high-speed UFOs northeast of Puerto Rico during November 18-24, 1964, but did find two valid radar or observation cases near the Atlantic Fleet Weapons Range on November 18, 19, 22, and 24. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.3] In other words, the review did not endorse every report in the packet. It separated weaker location framing from cases the analysts still considered valid.

The strongest event was November 19. CIA's response says a Navy F-8C pilot described a delta-shaped object about the size of a jet fighter and estimated its speed above Mach 3. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.3] The briefing notes say the Crusader pilot observed the object in full moonlight, with good weather and good visibility. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.1] The same notes say the pilot identified it as delta-shaped and about the size of a jet fighter. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.1]

The radar side is just as important. The briefing notes say USS Gyatt held radar contact with an object for 21 minutes near a fighter aircraft on November 19. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.1] They describe USS Gyatt as a Navy surface-to-air missile destroyer equipped with accurate tracking radar. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.2] The OSI response says analysis of USS Gyatt radar photography found a good track for the object and estimated its relative speed at about 3,800 knots. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.3]

Worth sitting with: this is the same incident being seen two ways. A Crusader pilot sees a delta-shaped object in good visibility and full moonlight. A Navy destroyer obtains radar-scope presentation pictures and tracks an object long enough for analysts to talk about a good track and a relative speed near 3,800 knots. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.2] [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.3]

The scientific conclusion did not identify the object. It said the object was probably a delta-wing type with performance significantly higher than the F-8C at roughly 20,000 feet. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.4] That language is careful. It does not say alien craft. It does not say Soviet aircraft. It says the object's apparent performance exceeded the observing aircraft by a meaningful margin.

The location sharpened the intelligence concern. The response described scheduled missile test firings in the Atlantic Fleet Weapons Range as a possible reason the area could have been attractive for reconnaissance. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.4] The same response noted that the USSR had a MiG-21 reconnaissance configuration, but said there was no evidence of MiG-21 reconnaissance activity based in Cuba. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.4]

The November 24 event kept the problem open. The briefing notes say the Atlantic Fleet Weapons Range again held a high-speed, high-altitude target that pulled away from a Crusader flying Mach .99 at 45,000 feet. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.1] ONI had no further information at the time and was asked to notify CIA of similar future incidents. [CIA-UAP-D023, Briefing Notes for Mr. Walter Elder p.2]

The chapter's lesson is not that Puerto Rico proves one grand answer. The documents do not support that. The lesson is narrower and stronger: in November 1964, U.S. military sensors and aircrew reported high-speed objects near a weapons range; CIA reviewed original Navy radar material under OXCART-linked controls; and the attempted YF-12A explanation failed inside the very system best positioned to know whether a Lockheed aircraft was responsible. [CIA-UAP-D022, Unidentified Flying Object Reported near Puerto Rico, 1965 p.6]

The Conde, Bahia file is useful because it gives the archive a control case. A sensational claim entered the U.S. record. Then the record tested it. The result was not amplification. It was rejection.

The first version came through an FBIS monitoring report from Rio de Janeiro Radio Tupi in Portuguese at 2330 on November 8, 1963. [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1] The reported location was Conde, a municipality in Bahia, Brazil. [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1] The broadcast said, "REPORTS FROM THE MUNICIPALITY OF CONDE, IN ' BAIA, SAY A LARGE METAL SPHERE FELL IN THE CENTER OF THE CITY, GOUGING A HOLE FOUR METERS DEEP." [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1] It added that "THE MYSTERIOUS SPHERE HAS WINDOW SHAPED OPENINGS COVERED WITH THICK GLASS." [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1] The most dramatic claim was the body: "INSIDE IS A HUMAN BODY DRESSED IN HEAVY CLQTHING BEARING INSCRIPTIONS WHICH CANNOT BE DECIPHERED." [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1]

That is the kind of report a bad archive would let sit as a mystery. Metal sphere. Glass openings. A body. Undeciphered markings. Local alarm. The broadcast also said the population of Conde was intrigued and that authorities had been informed. [EOP-UAP-D001, NASC Inquiry into Bahia, Brazil Incident, November 13, 1963 p.1] On the surface, it has all the old ingredients: impact, machine, occupant, official attention.

But the next documents show the institutional reflex that matters. The story was not left as folklore. It was routed for verification.

A November 14, 1963 Department of State cable, marked UNCLASSIFIED, went from the U.S. Embassy in Rio de Janeiro to the Secretary of State in Washington. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1] The cable referred to a poor radiotelephone connection the previous night and asked Washington to confirm or correct the embassy's understanding of the discussion. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1] The version in that cable had already shifted from Radio Tupi's metal sphere to a local press account of a large metal manned balloon found near Salvador around November 8, 1963, with a dead crewman aboard. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1] The crewman was described as wearing a uniform or spacesuit with strange markings. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1]

That mutation matters. In one channel, the object is a metal sphere in the center of Conde. In the next, it is a large metal manned balloon near Salvador. In both, the dead occupant remains. The stable element is not the machine. It is the sensational hook.

The embassy cable did not endorse it. It asked for confirmation. The embassy said it understood that an object had been sighted in the same vicinity around that date and tentatively identified as a weather-type balloon. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1] It also emphasized that no such object had been found on the ground. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1] The cable was passed to Defense and NASA at 2:20 PM on November 14, 1963. [DOS-UAP-D001, Diplomatic Cable, Brazil, November 14, 1963 p.1]

Five days later, the record gets cleaner.

A November 20, 1963 Department of State cable from the U.S. Embassy in Rio de Janeiro went to the Department as a negative report on a UFO reportedly sighted near Salvador, Bahia. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] The embassy asked the Department to pass information copies of the earlier cable to Defense for the Air Force and to NASA. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] Consul Harold Midkiff in Salvador reported that the story of a strange object descending in Conde, Bahia, was "apparently fabricated in Rio" and that no such objects had been seen by anyone in the area. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] Newspaper reporters and others had rushed to the area before investigation reports were received, and no verified sighting emerged. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1]

The weather-balloon explanation also stayed in the record, but with restraint. A local public security official speculated that the reported object might have been a weather balloon. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] The same cable says no such sighting was verified. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] That is not a debunking flourish. It is a chain of custody for uncertainty: speculation named, verification absent.

The supporting local press record points the same way. The cable cites Salvador newspaper clippings from Diario de Noticias and Jornal da Bahia as supporting the negative report. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] One clipping reported that the Ministry of Aeronautics categorically denied that there was any strange object in Conde. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] The other was titled "The Airship that wasn't there". [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.1] The cable was signed for the Ambassador by Andre C. Simonpietri, Scientific Attache. [DOS-UAP-D002, Diplomatic Cable, Brazil, November 20, 1963 p.2]

Worth sitting with: this is what a healthy disclosure corpus should preserve. Not only the strange reports that survive scrutiny, but the strange reports that do not. The Conde story was extraordinary at entry and weak at verification. The file does not require the reader to sneer at the claim. It requires the reader to notice the sequence. A monitored broadcast carried a crashed object and a body. NASA and State channels sought embassy verification. Local inquiry, press follow-up, and an Aeronautics denial produced a negative report.

The documents support reading the Conde case as a hoax-control case, not as a hidden retrieval case. The claim entered the archive because officials checked it. It stayed in the archive because the checking itself mattered.

Triangles in the FBI Record

The FBI triangle records in this tranche do not describe one clean event. They describe three separate witness accounts, collected in three separate FD-302 interviews, plus four later image files the FBI prepared in 2026 as PURSUE visual aids. That split matters. The FD-302s are interview records. The renderings are artistic interpretations of those interviews, not photographs, sensor captures, or original testimony. [FBI-UAP-D025, Digital Rendering, “Airborne Triangle,” 2002 p.1]

The oldest triangle account sits inside FBI-UAP-D024, a March 2024 FD-302 from a former U.S. military pilot. [FBI-UAP-D024, FD-302, “Airborne Lights and Triangle,” 2002, 2023-2024 p.1] Most of that interview concerns later white-light sightings from airline routes in 2023 and 2024, but the last page reaches back to June 2002 at Bagram Air Force Base in Afghanistan. [FBI-UAP-D024, FD-302, “Airborne Lights and Triangle,” 2002, 2023-2024 p.3] The witness described stars being blocked out by something huge passing overhead from west to east in an equilateral triangle shape. [FBI-UAP-D024, FD-302, “Airborne Lights and Triangle,” 2002, 2023-2024 p.3] A second pilot also saw the triangle, and the witness later found no data that explained what he saw in Afghanistan. [FBI-UAP-D024, FD-302, “Airborne Lights and Triangle,” 2002, 2023-2024 p.3]

That 2002 account is stark because it is almost all silhouette. No color pattern anchors it. No reported sound anchors it. The detail that carries the weight is occlusion: stars disappeared behind the shape. The record says it appeared as if something huge went overhead, from west to east, in an equilateral triangle shape. [FBI-UAP-D024, FD-302, “Airborne Lights and Triangle,” 2002, 2023-2024 p.3]

The 2011 account in FBI-UAP-D028 has a different texture. The FBI form records an April 2025 interview with two former U.S. military service members about an evening in June or July 2011. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.1] One witness first saw three lights in the sky from a vehicle near an intersection, then got out and saw a large black triangular object. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.1] The object was reported moving north, low to the ground, with a white light in each of its three corners. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.2] One witness estimated it at about 800 feet above ground and about 200 feet long by 100 feet wide. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.2]

Here the triangle is not only a shape. It has scale, corner lights, motion, and sound. The witnesses remembered a pulsing sound and reported no contrails behind the object. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.2] The attempted phone video failed because the object moved over the tree line and out of sight before the phone was ready. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.2] The FD-302 also notes a limitation: the witnesses did not clearly remember the object's vertical profile because they were initially underneath it and were distracted while trying to record it. [FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011 p.2]

The 2023 Colorado Springs records add two more triangle reports, but they should not be collapsed into one case. FBI-UAP-D026 records a January 2026 interview about an October 2023 event in Colorado Springs. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.1] The witness and his wife were on their back porch around 10:50 PM when the object came from behind the house and moved toward the southwest. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.1] He estimated it was possibly as low as 300 feet and roughly the size of a large SUV. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.2]

This is the most physically strange of the three descriptions, but it is also the briefest. The witness said the object appeared almost see-through, with haze, distortion, and ripple-like visual effects around it. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.2] He described a triangular form with possible rounded edges and a silverish blue band along the trailing flat edge. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.2] The object moved quickly in a straight path, stayed at a consistent elevation, and made no sound or physical effect he could feel. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.2] The whole sighting lasted four seconds, leaving no time to take a photo or video. [FBI-UAP-D026, FD-302, “Dark Translucent Triangle,” 2023 p.2]

FBI-UAP-D030, also from Colorado Springs in October 2023, is a separate FD-302 entered after an October 2025 FBI interview. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.1] The reported incident occurred between 8 and 9:30 PM while the witness was watching the sky in the Colorado Springs area. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.1] The first unusual feature was a dark-gray cloud that appeared pixelated or distorted and was stationary in the sky. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2] The witness then described a solid black triangular object emerging from the cloud with a diffuse red light at each of its three corners. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2]

This second Colorado Springs triangle is larger and higher in the witness estimate than the porch sighting in FBI-UAP-D026. The witness estimated the object could have been as large as the parking lot where he stood, 3 to 5 stories thick, and 3,000 to 5,000 feet high. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2] He reported no noise, no visible propulsion, and no unusual smell, but described waves around the object like a mirage on a hot road. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2] He said the object accelerated almost instantaneously to possibly Mach 1 or 2, then turned south or slightly southwest. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2] About 60 seconds after the sighting, he called his wife, who said his voice sounded robotic, as if there was electronic interference. [FBI-UAP-D030, FD-302, “Large Triangle with Red Lights,” 2023 p.2]

The later renderings are useful, but only if kept in their lane. FBI-UAP-D025 is an artistic interpretation tied to the June 2002 Bagram account, prepared by the FBI in 2026 for PURSUE. [FBI-UAP-D025, Digital Rendering, “Airborne Triangle,” 2002 p.1] FBI-UAP-D029 is a 2026 rendering based on the June or July 2011 first-hand description from two former U.S. military service members described in FBI-UAP-D028. [FBI-UAP-D029, Digital Rendering, “Dark Triangle with Lights,” 2011 p.1] FBI-UAP-D027 is a 2026 rendering of the October 2023 dark translucent triangle near Colorado Springs, based on the former Department of War employee's account in FBI-UAP-D026. [FBI-UAP-D027, Digital Rendering, “Dark Translucent Triangle,” 2023 p.1] FBI-UAP-D031 is a 2026 rendering of the large triangle with red lights near Colorado Springs, based on the U.S. Person's description in FBI-UAP-D030. [FBI-UAP-D031, Digital Rendering, “Large Triangle with Red Lights,” 2023 p.1]

Read together, the FBI record does not prove a single triangle phenomenon. It does something narrower and more durable. It preserves repeated first-hand reports of triangular objects across 2002, 2011, and 2023, with different witnesses, different locations, different light patterns, and different collection dates. The pattern is not a verdict. The pattern is a filing fact: triangles keep appearing in the interview record, and the FBI considered the descriptions concrete enough to turn four of them into PURSUE visual aids in 2026. [FBI-UAP-D031, Digital Rendering, “Large Triangle with Red Lights,” 2023 p.1]

The strongest part of the Gulf of Oman record is also the part the public cannot inspect directly.

The core report is DOW-UAP-D101, an Intelligence Information Report for a September 8, 2021 live-fire training event in the Gulf of Oman involving a U.S. Special Operations Forces AC-130 Gunship. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.1] The aircraft first saw the reported UAP after it dropped a water-activated flare to use as a mock target, then scanned near the flare with the EO/IR sensor. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The first two objects were described as roughly four-foot cold orbs, 0 to 20 feet above the water, stationary for about 15 seconds. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2]

That is a precise claim. It has a date, a platform, a location, a sensor type, a target context, an altitude band, and an estimated object size. The report then adds the behavior that makes the case harder to file away: the pair moved rapidly out of the sensor feed immediately after the Combat Systems Officer pulled the trigger to fire the aircraft's 105mm cannon. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] During the sortie, the crew reported roughly 25 UAP instances, viewed in infrared as cold orbs in both white-hot and black-hot modes. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The report describes formation behavior, including two UAP moving in a coordinated loose formation and a separate formation of three. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The Combat Systems Officer estimated observed maneuvering speeds from 250 to 1,300 miles per hour using the aircraft's TACTOOL. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The report also states that no means of propulsion were observed. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.5]

Those are the load-bearing details. They are why this incident matters. But the evidentiary center has a hole in it.

DOW-UAP-D101 says the AC-130 crew attempted to save the EO/IR footage, but the aircraft's Digital Video Recorder failed and the video data became corrupted. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The same report's attachment line identifies a PowerPoint containing six embedded videos related to the September 8, 2021 observations. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.6] What the public release gives readers, however, is not the native sensor file that would normally carry the most forensic value. It gives secondary recordings of an infrared sensor display, filmed with a cellular device. [DOW-UAP-PR117, Unresolved UAP Report, Gulf of Oman, 2021 p.1]

That distinction is not technical trivia. It is the case.

PR117 is 16 seconds of UAP video footage submitted by United States Central Command to AARO, and the file says the footage is a secondary cellular recording of an infrared sensor display aboard a U.S. Special Operations Forces AC-130J Gunship, not native primary sensor data. [DOW-UAP-PR117, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR118 is 30 seconds of video footage, also described as a secondary cellular-device recording of an infrared sensor display aboard the same class of aircraft, not native primary sensor data. [DOW-UAP-PR118, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR119 is only two seconds of footage captured by a cellular device from an infrared sensor display aboard a U.S. Special Operations Forces AC-130J Gunship. [DOW-UAP-PR119, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR120 is 13 seconds of secondary cellphone footage from the infrared display. [DOW-UAP-PR120, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR121 is 34 seconds of secondary cell-phone recording from the infrared display. [DOW-UAP-PR121, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR122 is 26 seconds of video footage from the AC-130J infrared sensor display, again described as a secondary cellular-device recording rather than native primary sensor data. [DOW-UAP-PR122, Unresolved UAP Report, Gulf of Oman, 2021 p.1]

AARO and the Department of War do not hide the limitation. PR118 warns that filming a screen can introduce fidelity, resolution, blur, and flicker limitations. [DOW-UAP-PR118, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR119 says the footage is not native primary sensor data and that secondary recording limits fidelity, resolution, and overall visual quality. [DOW-UAP-PR119, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR121 says the secondary recording method introduces limits in fidelity, resolution, and visual quality, including possible screen-filming artifacts such as blur or flicker. [DOW-UAP-PR121, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR122 says the same recording method can introduce limits in fidelity, resolution, and visual quality, including possible screen-filming artifacts such as blurring or flickering. [DOW-UAP-PR122, Unresolved UAP Report, Gulf of Oman, 2021 p.1]

So the public record splits in two. On one side is the crew report: roughly 25 infrared UAP instances, cold orb descriptions, apparent formation behavior, no observed propulsion, and speed estimates reaching 1,300 miles per hour. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] On the other side are the released clips: short, secondary cellphone recordings of a sensor display, with the native DVR file unavailable because the attempted saved footage was corrupted. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2]

The video-release language is careful, almost defensive. PR117 says the video description is limited to an area of contrast remaining generally within the center of the sensor field of view, with no stated analytical conclusion. [DOW-UAP-PR117, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR119 explicitly says readers should not treat the video description as an analytical judgment, investigative conclusion, or factual determination. [DOW-UAP-PR119, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR120 says the description is informational only and should not be treated as an analytical judgment or investigative conclusion. [DOW-UAP-PR120, Unresolved UAP Report, Gulf of Oman, 2021 p.1] PR121 says AARO's description is informational only and should not be read as an analytical judgment, investigative conclusion, or factual determination. [DOW-UAP-PR121, Unresolved UAP Report, Gulf of Oman, 2021 p.1]

That caution is warranted. A cellphone recording of a screen is not the same evidentiary object as native EO/IR data. The screen recording may show what a crew member or another onboard observer saw on a display, but it strips away the original sensor stream, metadata, frame integrity, and clean image quality that would help outside reviewers test range, motion, contrast, artifact, and tracking claims. That limitation follows directly from the releases' own repeated warning that the public clips are not native primary sensor data and that the recording method limits fidelity, resolution, and visual quality. [DOW-UAP-PR120, Unresolved UAP Report, Gulf of Oman, 2021 p.1]

Worth sitting with: this is not a weak case because nothing was recorded. It is a frustrating case because the report says the crew tried to save the EO/IR footage, then the DVR failed and the video data became corrupted. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The surviving public evidence is not nothing. PR117 through PR122 were captured contemporaneously with the September 8, 2021 event. [DOW-UAP-PR122, Unresolved UAP Report, Gulf of Oman, 2021 p.1] The accompanying DOW-UAP-D101 report describes the phenomena in those contemporaneous clips as cold orbs approximately four feet in diameter. [DOW-UAP-PR121, Unresolved UAP Report, Gulf of Oman, 2021 p.1] But the released files do not let the public test the strongest claims at the native-data level.

The Gulf of Oman record therefore supports a narrow reading, not a grand one. A trained AC-130 crew reported repeated infrared contacts during a live-fire sortie, including low-altitude cold orbs, formation-like behavior, rapid movement, and no observed propulsion. [DOW-UAP-D101, Intelligence Information Report, Unresolved UAP Report, Gulf of Oman, 2021 p.2] The public release preserves secondary screen recordings from that event, while acknowledging that those recordings are degraded substitutes for the native sensor data. [DOW-UAP-PR118, Unresolved UAP Report, Gulf of Oman, 2021 p.1] The unresolved part is not only the object. It is the missing instrument record beneath the object.

Secondary Media and the Limits of Public Proof

The Pacific Ocean set starts with a warning about evidence type. DOW-UAP-PR123 is not described as native sensor data. It is a 1 minute, 4 second hand-held recording of an infrared sensor display aboard a U.S. military platform, from a 2019 incident over the Pacific Ocean. [DOW-UAP-PR123, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The Department of War says that method limits fidelity, resolution, and visual quality. [DOW-UAP-PR123, Unresolved UAP Report, Pacific Ocean, 2019 p.1] It also says the media was digitally altered before it was reported to AARO, and that AARO is presenting it as received. [DOW-UAP-PR123, Unresolved UAP Report, Pacific Ocean, 2019 p.1]

That matters because the release still gives the public a time-coded description. In PR123, the description tracks an area of contrast near the center of the frame across several time ranges, including sensor panning and zooming from 00:08 to 00:25. [DOW-UAP-PR123, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The sentence does not say object, craft, vehicle, or aircraft. It says area of contrast. That phrase is doing real work. It names what can be seen in the released media without claiming what the thing is.

The next file repeats the same evidentiary posture. DOW-UAP-PR124 concerns a 2019 Pacific Ocean UAP incident recorded from an infrared sensor display aboard a U.S. military platform. [DOW-UAP-PR124, Unresolved UAP Report, Pacific Ocean, 2019 p.1] It is a secondary capture made with a hand-held recording device, not native primary sensor data. [DOW-UAP-PR124, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The Department of War says PR123 through PR127 were captured contemporaneously, which makes them a grouped public record rather than five free-floating clips. [DOW-UAP-PR124, Unresolved UAP Report, Pacific Ocean, 2019 p.1] But the agency also says PR124 was digitally altered before it was reported to AARO and is presented as AARO received it. [DOW-UAP-PR124, Unresolved UAP Report, Pacific Ocean, 2019 p.1]

PR125 narrows the public record even further. It contains 28 seconds of footage from an infrared sensor display aboard a U.S. military platform. [DOW-UAP-PR125, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The file is a secondary capture made with a hand-held recording device, not native primary sensor data. [DOW-UAP-PR125, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The recording method introduces limits in fidelity, resolution, and visual quality, including possible blurring or flickering from filming a screen. [DOW-UAP-PR125, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The time-coded description reports an area of contrast moving within the infrared sensor field of view between 00:00 and 00:28. [DOW-UAP-PR125, Unresolved UAP Report, Pacific Ocean, 2019 p.1]

PR126 and PR127 shift from infrared-display recordings to low-light hand-held footage, but the same pattern holds. PR126 is described as 2 minutes and 32 seconds of footage captured in 2019 by a U.S. military service member using a hand-held recording device during a Pacific Ocean incident. [DOW-UAP-PR126, Unresolved UAP Report, Pacific Ocean, 2019 p.1] Low-light conditions affected the visual quality. [DOW-UAP-PR126, Unresolved UAP Report, Pacific Ocean, 2019 p.1] The visual description tracks apparent light sources entering, leaving, and being centered in frame as the camera pans and zooms. [DOW-UAP-PR126, Unresolved UAP Report, Pacific Ocean, 2019 p.1] PR127 is described as 2 minutes and 29 seconds of handheld footage captured by a U.S. military service member in 2019, with low-light conditions affecting the overall visual quality. [DOW-UAP-PR127, Unresolved UAP Report, Pacific Ocean, 2019 p.1] Its description repeatedly frames the visible content as camera pans tracking an apparent light source, separated by intervals with no content. [DOW-UAP-PR127, Unresolved UAP Report, Pacific Ocean, 2019 p.1]

The Middle East files show a cleaner sensor chain in some cases, but not a stronger public conclusion. PR134 says CENTCOM submitted a UAP report to AARO after a 2025 Middle East incident. [DOW-UAP-PR134, Unresolved UAP Report, Middle East, 2025 p.1] The supporting footage was recorded by an electro-optical and infrared sensor aboard a U.S. military platform. [DOW-UAP-PR134, Unresolved UAP Report, Middle East, 2025 p.1] The video runs 1 minute and 39 seconds and shows the sensor tracking an area of contrast from left to right while changing collection mode and magnification. [DOW-UAP-PR134, Unresolved UAP Report, Middle East, 2025 p.1] Again, the public phrase is area of contrast, not identification.

PR136, PR142, and PR149 are even more compressed. PR136 consists of 30 seconds of infrared video from a U.S. military platform during a 2023 Middle East incident reported by CENTCOM to AARO. [DOW-UAP-PR136, Unresolved UAP Report, Middle East, 2023 p.1] From 00:00 to 00:08, the sensor panned to track an area of contrast and kept it generally centered. [DOW-UAP-PR136, Unresolved UAP Report, Middle East, 2023 p.1] From 00:09 to 00:33, the sensor zoomed in on the area of contrast, with a reticle briefly surrounding it. [DOW-UAP-PR136, Unresolved UAP Report, Middle East, 2023 p.1] PR142 is 14 seconds of infrared sensor video from a U.S. military platform in a 2025 Middle East incident, and the described visible activity lasts only from 00:05 to 00:08 as an area of contrast crosses from left to right. [DOW-UAP-PR142, Unresolved UAP Report, Middle East, 2025 p.1] PR149 is 51 seconds of infrared video from a U.S. military platform in a 2023 Middle East event, with an area of contrast first moving from the bottom right edge toward the lower left edge, then remaining generally near center as the sensor pans to track it. [DOW-UAP-PR149, Unresolved UAP Report, Middle East, 2023 p.1]

What is striking is the consistency of the boundary language. PR123 says the description is informational only and should not be read as an analytical judgment, investigative conclusion, or factual determination. [DOW-UAP-PR123, Unresolved UAP Report, Pacific Ocean, 2019 p.1] PR124 gives the same caution for its time-coded description. [DOW-UAP-PR124, Unresolved UAP Report, Pacific Ocean, 2019 p.1] PR125 warns that the description should not be read as a finding about validity, nature, or significance. [DOW-UAP-PR125, Unresolved UAP Report, Pacific Ocean, 2019 p.1] PR126 and PR127 repeat that the release language is not an analytical judgment, investigative conclusion, or factual determination. [DOW-UAP-PR126, Unresolved UAP Report, Pacific Ocean, 2019 p.1] [DOW-UAP-PR127, Unresolved UAP Report, Pacific Ocean, 2019 p.1] PR134, PR136, PR142, and PR149 carry the same limit into the Middle East cases. [DOW-UAP-PR134, Unresolved UAP Report, Middle East, 2025 p.1] [DOW-UAP-PR136, Unresolved UAP Report, Middle East, 2023 p.1] [DOW-UAP-PR142, Unresolved UAP Report, Middle East, 2025 p.1] [DOW-UAP-PR149, Unresolved UAP Report, Middle East, 2023 p.1]

The public record therefore supports a narrow reading. These releases document that U.S. military systems or service members recorded visual anomalies, that AARO received the reports, and that the released descriptions track contrast areas or apparent light sources through specific time windows. [DOW-UAP-PR134, Unresolved UAP Report, Middle East, 2025 p.1] [DOW-UAP-PR149, Unresolved UAP Report, Middle East, 2023 p.1] They do not publicly prove what the recorded things were. That restraint is not a defect in the chapter. It is the central fact of the chapter.

The western U.S. cluster reads less like a conclusion than a stack of interview records and visual aids. That matters. FBI-UAP-D032 is an FD-302 interview record, and the form states that it contains neither FBI recommendations nor FBI conclusions. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] FBI-UAP-D040 carries the same boundary: the document says it contains neither recommendations nor conclusions of the FBI. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.1] The Bureau is preserving statements, reported sensor context, and supporting imagery. It is not, in these pages, telling the reader what the objects were.

The thermal case in FBI-UAP-D032 begins with a precise trigger. A U.S. Government Special Agent reported being alerted at approximately 1604 local time to an RF detection at 10K MSL for 5 to 10 seconds, then being asked to observe at a bearing of 58 degrees. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] Using a thermal optical device, the agent saw a black object in the sky that was not moving fast. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] While watching the first object, the agent saw a second object to its right and captured more photos or videos. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1]

The reported behavior is narrow but concrete. The two objects moved together at the same speed, and the witness described them as black hot. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] The observation lasted approximately 5 to 10 minutes. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] The agent could not estimate altitude or speed, and said the objects were above the mountain line. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] Page 2 says the photos were provided to an FBI Special Agent. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.2] The linked media record, FBI-UAP-PR007, says the footage was captured by a U.S. Government Special Agent with a hand-held optical thermal imaging device during a 2026 western U.S. incident. [FBI-UAP-PR007, “Slow-moving Objects,” 2026 p.1] It describes the visible content as two slow-moving black-hot areas of contrast in infrared imaging, and it links that footage back to FBI-UAP-D032 for incident context. [FBI-UAP-PR007, “Slow-moving Objects,” 2026 p.1]

FBI-UAP-D033 gives a second thermal record, again carefully limited. The FD-302 attaches and reproduces a Special Agent's written statement for readability. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1] The reported observation occurred in 2026 at approximately 2100 hours while the agent was positioned in the same general observation area referenced in a prior statement. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1] The object appeared thermally elevated, in the same general western sector, and on a similar heading as the prior night's observed object. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1] The agent could not identify specific physical characteristics or determine the object's exact configuration because it was farther west with terrain separation. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1]

The useful part of D033 is the comparison method. The agent recorded video of a U.S. Army Black Hawk helicopter in the same general area to create a visual and thermal comparison point. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1] The unidentified object was estimated at approximately half the size of the Black Hawk helicopter, with the statement labeling that comparison as an estimate only. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.1] The agent still could not determine whether the object was fixed-wing, rotary-wing, or another unmanned aerial system. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.2] The object continued southbound and was eventually lost from observation because of terrain and distance. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.2]

The red-light interviews shift the evidence from thermal contrast to human observation under poor weather and night-optical conditions. FBI-UAP-D037 records an FBI interview with a U.S. person about events in the western United States in 2026. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.1] The first observation occurred after the witness and another person had been driving in rainy weather with significant cloud cover, roughly between 8:00pm and 8:30pm. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.1] The witness described two dull red dash-shaped lights moving along a western mountain ridgeline, then said the same lights appeared orb-like or circular through night optical devices. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.1] After about 20 minutes, the two lights disappeared, and another similar light appeared directly above the observers for about 10 minutes. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2]

The later D037 details are stranger because they move closer to the observers and closer to the ground. Between 10:00pm and 11:00pm, the witness reported another similar light about 600 meters east of their position and about 500 feet above the vehicle. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2] A second eastern light reportedly moved toward the first and appeared to be about 6 feet off the ground. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2] The witness also reported a glow moving through a dry wash about 100 meters behind the observers, although he could not directly see the light source. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2] The same witness reported that his analog watch showed a time 25 minutes ahead of his phone and the vehicle clock, despite having been accurate around 10:00pm. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2]

FBI-UAP-D040 overlaps the red-light theme but adds a second witness account and a different geometry. The telephonic interview says the first observation began after the observers drove roughly 25 miles north following heavy rain and stopped when a red light appeared near the crest of a mountain range to their west. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.1] The interviewee estimated the first light was between 5,000 and 7,000 feet above ground level, based on mountain-range and cloud-cover heights. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.1] After about 15 minutes, approximately 6 to 10 additional lights appeared directly over the observers and moved east or southeast with the original light. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.1] One light reportedly descended rapidly by an estimated 1,000 feet before disappearing. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.1]

On closer observation in D040, each light cluster appeared to contain three lights in a triangular or diamond-shaped pattern. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] The clusters moved together and did not separate, as if the three lights were attached to the same object. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] Around 2350, the observers saw two lights on or near the ground to the east that were only visible through Night Optical Devices and stopped about 200 to 300 meters away. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] The interviewee also reported a rapidly moving light streak with a visible light tail, followed by a hue of light moving north along a defilade before fading out or disappearing. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] Afterward, one analog watch was reportedly 25 minutes fast while a digital watch, cell phones, and the vehicle clock displayed the same time. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] The interviewee stated that he had no physiological reactions or effects during or after the events. [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2]

The renderings should be read as aids, not evidence on their own. FBI-UAP-D038 and FBI-UAP-D039 are digital renderings tied to the D037 account, prepared by the FBI in 2026 as PURSUE visual aids from a first-hand description by two U.S. persons. [FBI-UAP-D038, Digital Rendering 1, “Multiple Red Lights,” 2026 p.1] [FBI-UAP-D039, Digital Rendering 2, “Multiple Red Lights,” 2026 p.1] FBI-UAP-D041 and FBI-UAP-D042 perform the same function for the D040 account, again as FBI-prepared digital renderings based on a first-hand description from two U.S. persons. [FBI-UAP-D041, Digital Rendering 1, “Multiple Red Lights,” 2026 p.1] [FBI-UAP-D042, Digital Rendering 2, “Multiple Red Lights,” 2026 p.1] They help reconstruct what the witnesses said they saw. They do not replace the FD-302s, and they are not sensor records. [FBI-UAP-D038, Digital Rendering 1, “Multiple Red Lights,” 2026 p.1]

Worth sitting with: these files do not prove a single cause. They do preserve a pattern of disciplined uncertainty. Thermal observers recorded black-hot slow movers but could not estimate altitude or speed. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1] A second thermal observer made a helicopter comparison, then still declined to classify the object as fixed-wing, rotary-wing, or unmanned. [FBI-UAP-D033, FD-302, “Thermally Elevated Aerial Object,” 2026 p.2] Red-light witnesses described low-elevation lights, NOD-only lights, and 25-minute analog watch discrepancies, while also reporting no physiological effects. [FBI-UAP-D037, FD-302, “Multiple Red Lights,” 2026 p.2] [FBI-UAP-D040, FD-302, “Multiple Red Lights,” 2026 p.2] The documents support a restrained reading: the FBI collected credible interview material and supporting visual references around western U.S. UAP reports, but these pages do not identify the objects, certify an anomaly, or close the case. [FBI-UAP-D032, FD-302, “Slow-moving Objects,” 2026 p.1]