1957·North-eastern Saudi Arabia, in flight at 39,000 ft
Saudi Arabia.Saudi Arabia · something only a B-52's tail radar picked up
One night in January 1957, during the first nonstop round-the-world flight by jet bombers, the tail-turret fire-control radar of B-52 "Lucky Lady III", leading the formation at 39,000 feet over north-eastern Saudi Arabia, held a return at the 6,000-yard marker, directly behind the bomber, for five to seven minutes, smaller than that of another B-52 in the cell. The return vanished when the bomber banked left, and the next day's intelligence report allows that the turn may have caused the loss; nobody reports seeing anything.
Tier S · SolidWhat do they mean? →
Strong evidence: a contemporary instrumental record (radar, sensor, film or photo of known provenance) that corroborates several independent witnesses.
What it was
63%natural or human cause
Most likely an ordinary cause that no one has identified
See the split across the six explanations
Natural or human cause
No known cause
Read the full reasoning
The absence of a published analysis is not evidence against an ordinary cause: AARO's FY2024 report finalized "all 174 cases" as "resolved to prosaic objects", while "many other cases remain unresolved".What happened
Between January 16 and 18, 1957, three B-52B bombers of Strategic Air Command's 93rd Bombardment Wing made the first nonstop round-the-world flight by jet aircraft, Operation Power Flite (the report spells it "Operation Powerflight"). Five took off from Castle Air Force Base, California, on January 16 at 1 p.m. Pacific time. One could not refuel and diverted to Goose Bay, Labrador; another, a spare, left the flight over North Africa for England as planned, and the remaining three landed at March Air Force Base, also in California, 45 hours and 19 minutes later, after four in-flight refuellings from piston-engined KC-97 tankers. One of those refuellings took place over Saudi Arabia. The lead aircraft was B-52B 53-0394, "Lucky Lady III", commanded by Lieutenant Colonel James H. Morris, with Major General Archie J. Old Jr., commander of Fifteenth Air Force, on board.
According to the intelligence report written afterwards, aircraft 394, of the 328th Bombardment Squadron, was leading its group, call sign "Runner 11", at 39,000 feet and 642 knots. The report's drawing labels that figure as true airspeed, but it exceeds the B-52B's maximum (547 knots at about 20,000 feet, according to This Day in Aviation); most likely it is ground speed with a tailwind (our own reasoning). It was night and the aircraft was at about 27° N 47° E, coordinates the report itself gives as approximate and which fall in north-eastern Saudi Arabia.
Just before the rendezvous with the tanker, the tail gunner, Master Sergeant C. H. Ballew, saw on his screen what the report calls an unidentified aircraft. It was the screen of the A-3A, the radar that aimed the tail turret: it looks backwards, shows anything that reflects its waves as a dot of light, a "blip", and has markers for range. The blip stayed at the 6,000-yard marker (about 5.5 km), in the center of the screen (the middle column of the drawing): directly behind the bomber, for about five to seven minutes. The B-52 then banked left and the blip went off the screen to the left.
The report adds three points. First, that the disappearance "may have been caused by the change in direction of the B-52", that is, by the turn itself. Second, that the blip nevertheless seemed to vanish in the direction of the Baghdad Flight Identification Region. Third, that it was smaller than the blip of a second B-52 in the group, showing at the same time at the 3,000-yard marker. The second page is a drawing of the screen showing both blips: the unidentified aircraft's, on the 6,000 marker, annotated "Smaller return than that produced by B-52", and the second bomber's, on the 3,000 marker. In the drawing the exit arrow points to the right-hand edge, while the text says the blip went off to the left; the report does not explain the difference, which could be because the tail radar's screen is read looking aft, so that the aircraft's left appears on the right (our own reasoning). In the paragraph on significance, the report says the unidentified aircraft "appeared on the scope where no aircraft were expected".
The report was written on January 19, the day after the landing, by Captain Alva Smith of the 22d Bombardment Wing, based at March, under the title "Report of Unidentified Aircraft Sighting". It is an Air Intelligence Information Report (AF Form 112, report number IR-1-57) on Saudi Arabia, with January 18 as the date of information and the crew of B-52 number 394 as source. It is signed by Major Robert Sullivan, assistant chief of the intelligence division; it went to Fifteenth Air Force, Strategic Air Command headquarters, the 93rd Wing and Air Force headquarters, and carries the evaluation "B-2": usually reliable source, information probably true.
The report does not say whether anyone on board saw anything, whether the second B-52's radar or any ground radar recorded the same blip, where the third bomber was flying, or at what time the contact occurred. The January 18 it gives as the date of information, which the document's official description uses to date the event, is the day the formation landed; from the flight's schedule, the pass over Saudi Arabia must have been on the afternoon or night of the 17th (our own calculation). The digitized Blue Book collection on archive.org, which holds 25 files for January 1957, has none on this event.
Why it matters
The contact was recorded by a military radar during a record flight, with the crew identified and an intelligence report written the next day giving the aircraft, its commander, the gunner, altitude, speed, coordinates and a drawing of the screen. The report itself does not exaggerate: it attributes no maneuvere to the blip, allows that the loss of contact may have been caused by the bomber's turn, and only notes that it appeared where no aircraft were expected.
What the record does not allow is to say what it was. A blip that stays on the same range marker for five to seven minutes, while the bomber is flying at cruise speed, is something that kept that distance; the report gives neither the blip's altitude nor its heading. By our own calculation, that rules out a KC-97 tanker: the radar looked aft, and a piston-engined aircraft a hundred knots or more slower than the B-52 would have dropped back about 3,000 yards a minute and left the scale within one or two; at the rendezvous, moreover, the tanker sits ahead of the aircraft taking on fuel, not behind it. No source examines the other possibilities, among them another aircraft of the operation itself, traffic the crew did not know about, or a false signal from the equipment.
That the blip was smaller than the second B-52's does not mean the object was: it was twice as far away, and the energy returning to a radar falls with the fourth power of range, so at twice the distance about sixteen times less comes back (our own calculation). Over Saudi Arabia the group had three bombers and the report does not say where the third was flying, though it does say the blip appeared where no aircraft were expected.
There are no visual witnesses either. The report does not mention anyone seeing a light or an aircraft, and it was night, so the radar is the only evidence and the drawing is an illustration of the screen, not an image of the object. The official description accompanying the document warns that the report's descriptive language reflects the reporter's subjective interpretation at the time and should not be read as a conclusive indication of the object's characteristics.
Documents and sources
Primary documents
DOW-UAP-D155 — Air Intelligence Information Report on the return seen by B-52 number 394
Air Intelligence Information Report IR-1-57 (AF Form 112) from the 22d Bombardment Wing, dated January 19, 1957, on the blip seen by the tail radar of B-52 number 394 over Saudi Arabia during the Operation Power Flite round-the-world flight: position, altitude, speed, duration of contact, the gunner's name and the report's own sentence about the turn.
Read more
The second page draws the screen of the A-3A tail-turret fire-control radar with the unidentified blip at the 6,000-yard marker and the second B-52's at 3,000. The document, published in the seventh PURSUE release (DOW-UAP-D155, October 23, 2026), has five pages. The first two are the report, classified "Secret" (the marking is struck through), with the handwritten number 1071367 and a NARA declassification stamp with authority NW 78452 and the date "3/19/26". Pages 3 and 4 are a second, fainter copy that carries the purple stamps "957 00161" and "M1 21360" but not the file number or the declassification stamp, and page 5 is the back of the page 4 sheet, with the drawing showing through in reverse and the handwritten number 34635867.
Fuerza Aérea de EE. UU., 22.º Ala de Bombardeo (PURSUE Release 07) · Public domain · US Government work · open original
Documented evidence
- Air Intelligence Information Report IR-1-57 (AF Form 112), 22d Bombardment Wing, March AFB: prepared by Captain Alva Smith on January 19, 1957, signed by Major Robert Sullivan, area Saudi Arabia, date of information January 18, source the crew of B-52 number 394, evaluation "B-2"
- Same report: B-52 394 of the 328th Bombardment Squadron, 93rd Wing, commanded by Lt Col J. H. Morris, leading its group, call sign "Runner 11", 39,000 ft, 642 knots (labelled true airspeed, though above the B-52B's maximum), night, at about 27° N 47° E; tail gunner, M/Sgt C. H. Ballew
- Same report: just before the tanker rendezvous, the screen of the A-3A tail-turret fire-control radar held the blip at the 6,000-yard marker, in the center, for five to seven minutes; when the bomber banked left the blip went off the screen, and the report says the disappearance "may have been caused by the change in direction of the B-52"
- Same report: the blip was smaller than that of a second B-52 in the group, received at the same time at the 3,000-yard marker, and seemed to vanish in the direction of the Baghdad Flight Identification Region; its significance, that it "appeared on the scope where no aircraft were expected"
- Page 2 of the report: drawing of the tail radar screen with both blips; the exit arrow points to the right-hand edge, while the text says the blip went off to the left
- Operation Power Flite: five B-52Bs took off from Castle on January 16, 1957 and three landed at March 45 hours 19 minutes later, after four refuellings from KC-97 tankers, one of them over Saudi Arabia; 53-0394, "Lucky Lady III", led the formation with General Archie J. Old Jr. on board
Sources
- war.gov/UFO — DOW-UAP-D155, 'Air Intelligence Information Report, Saudi Arabia, 1957' (PURSUE Release 07) — Primary document, embedded in this case's viewer: the January 19, 1957 intelligence report with the drawing of the scope.
- Official war.gov/UFO description of DOW-UAP-D155 (verbatim copy on the probed.space mirror; war.gov is not reachable from here) — Declared substitute: it reproduces the official description, which summarizes the report and warns that its descriptive language reflects the reporter's subjective interpretation and is not a conclusive indication of the object's characteristics.
- This Day in Aviation — '16–18 January 1957' (Operation Power Flite) — Secondary context source: the five B-52Bs, 53-0394 "Lucky Lady III" under Morris with General Old on board, the four KC-97 refuellings and the B-52B's speeds: 453 knots cruise at 35,000 ft and 547 knots maximum at 19,900 ft.
- Flight Journal — '16 to 18 January 1957' — Secondary context source: places one of the refuellings over Saudi Arabia, before the flight followed the coast of India to Sri Lanka.
- GlobalSecurity.org — 'B-52C Stratofortress' (tail-turret fire-control systems) — Secondary source: describes the A-3 as the tail turret's radar fire-control system, "capable of both optical and automatic tracking and search", replaced by the MD-5 in most B-52Bs and reinstated in the last ones.
- EarthSky — article on AARO's 2024 annual report — Base rate: AARO finalized 174 cases, all resolved to prosaic objects, and leaves many others unresolved.
Related cases