X INTELLIGENCE · OCTOBER 24, 2026

An October 23 post from DOW Rapid Response spotlights a B-52 crew's report of an unidentified radar contact over Saudi Arabia in 1957. The brief announcement accurately directs attention to the gunnery scope. The underlying document adds a consequential qualification: loss of the return may have resulted from the B-52's own change of direction.

The post refers to DOW-UAP-D155, an Air Intelligence Information Report included in PURSUE Release 07. The file is a historical report newly highlighted by the department, not a contemporary encounter or a newly recorded radar track.

What the crew reported

The report, dated January 19, 1957, lists January 18 as the date of information and identifies the crew of B-52 aircraft number 394 as its source. It describes an encounter on an A-3A gunnery scope shortly before a tanker rendezvous during the mission it calls Operation Powerflight.

According to the narrative, the unidentified return remained near the 6,000-yard marker for approximately five to seven minutes. A second B-52 was also present on the scope, with a return at approximately 5,000 yards. The report says the unidentified return appeared smaller. That comparison describes the radar presentation; it is not a direct measurement of the object's physical dimensions.

When the observing B-52 banked left, the unidentified return left the scope to the left. The report explicitly allows that the bomber's turn may have caused the disappearance. It also records an apparent direction toward the Baghdad Flight Identification Region, without establishing the contact's identity.

The mission context is independently documented

The Air Force's history of Operation POWER FLITE describes B-52s departing Castle Air Force Base on January 16, 1957 and completing a nonstop global flight on January 18, with repeated aerial refueling. It identifies Lt. Col. Jim Morris as commander of the lead aircraft. This independently supports the mission context and names in the intelligence report. It does not identify or independently confirm the unexplained radar return.

What the X post leaves for readers to check

The official post makes a specific, restrained claim about a recorded detection. Expanding that into an assertion of extraordinary acceleration would require evidence beyond this file. A contact leaving a directional sensor's coverage after the observing aircraft turns is not, on its own, proof that the target accelerated away.

The document preserves a narrative and scope presentations. It does not supply a complete calibrated time series from which this article can reconstruct a trajectory, diagnose radar behavior or rule out all ordinary explanations. The crew considered the contact worth reporting because no aircraft was expected in that position; that operational concern deserves to be preserved without treating uncertainty as a technological identification.

Assessment: The strongest contribution of the post is renewed access to a specific Cold War report. Its own caveat about platform motion belongs beside its description of the unidentified return.

Source note: the exact public X post was read directly. The five-page PDF was retrieved through its Internet Archive copy, with the first-page narrative visually checked against OCR. No independent reanalysis of original radar data was possible.

Hero image: original AI-generated editorial illustration; it does not depict evidence or reconstruct the reported event.