The RB-47 Incident: Triple-Sensor UAP Chase Over the American South

On 17 July 1957, a USAF RB-47 reconnaissance aircraft on a training mission over the American South tracked an unidentified object for approximately ninety minutes across multiple states. Three independent sensor systems — the aircraft's electronic intelligence receiver, its own airborne radar, and a ground-based Air Defense Command radar — all registered the object simultaneously. The crew also observed it visually. The University of Colorado's Condon Report, prepared for the Air Force, rated the case 'unidentified.' Atmospheric physicist Dr. James McDonald called it one of the most significant in the entire history of UAP sightings. No explanation consistent with all sensor data has been formally established.

On the morning of 17 July 1957, six United States Air Force officers aboard an RB-47H strategic reconnaissance aircraft tracked an unidentified aerial object for approximately ninety minutes as it appeared to intercept, shadow, and evade their aircraft over Louisiana, Texas, and Oklahoma. The object was simultaneously detected by three independent sensor systems: the aircraft’s own electronic intelligence (ELINT) receiver, its airborne fire-control radar, and a ground-based Air Defense Command radar installation near Dallas.

The case is unusual not because the witnesses were credible — though military aviators constitute strong witnesses by any standard — but because no single equipment anomaly can account for three simultaneous, correlated contacts on different sensor platforms. It was logged as Project Blue Book Case 4703 and rated unidentified. The University of Colorado’s official Air Force-sponsored study, the Condon Report, concluded in 1969 that conventional explanations had low probability and that the case must be listed as unidentified. Atmospheric physicist Dr. James E. McDonald, who examined the original documentation, wrote that it stood as “one of the most significant in the entire history of UAP sightings.”

What Was Reported

The RB-47H was a long-range electronic intelligence variant of the B-47 Stratojet strategic bomber, operated by the 55th Strategic Reconnaissance Wing. On 16–17 July 1957, the aircraft was conducting a multi-leg training mission that took it south from Forbes Air Force Base in Topeka, Kansas, through the Gulf Coast states and back.

The anomalous encounter began at approximately 0400 Zulu (roughly 11 PM Central Daylight Time on the night of July 16) while the aircraft was over the Gulf Coast region near Gulfport, Mississippi. 1st Lieutenant Frank McClure, the Electronic Warfare Officer stationed in the rear of the aircraft and responsible for the APD-4 ELINT receiver, picked up a signal on the S-band (approximately 2,800 MHz) that he initially took for a ground-based radar installation. What troubled him was directional: the signal’s bearing should have been fixed relative to the ground, but it appeared to rotate in a manner inconsistent with a stationary emitter as the aircraft moved. The source appeared to be ahead of the aircraft, moving.

McClure alerted the crew. Moments later, Major Lewis D. Chase, the pilot and aircraft commander, observed a brilliant blue-white light closing rapidly on the aircraft from the right. He initially estimated it as an oncoming aircraft. It was not: the light reached a position dead ahead of the RB-47, matched the aircraft’s speed — approximately 500 miles per hour — held position briefly, and then executed what Chase described as a sharp left turn.

The aircraft’s APQ-56 airborne radar then acquired the contact. The target return was consistent in bearing and distance with the light Chase and at least one other crew member observed visually. All three data streams — McClure’s ELINT receiver, the APQ-56 airborne radar scope, and the visual report from the flight deck — were tracking the same position simultaneously.

Ground radar became part of the story when the crew radioed Duncanville Air Defense Control Center, a Ground Control Intercept station located southwest of Dallas, Texas. Duncanville’s radar confirmed a single unknown target in the area the crew reported, and ground controllers tracked it for a portion of the event’s duration, observing it as a skin-paint return that moved and maneuvered in ways inconsistent with any filed flight plan.

Over the following ninety minutes, the object was observed to accelerate, decelerate, disappear from all sensors simultaneously, reappear in a different position, and at one point appeared to descend rapidly toward the ground before halting. The ELINT signal dropped off and came back in correlation with the visual and radar disappearances, suggesting the three contact types were detecting a single phenomenon rather than three unrelated events. The encounter ended somewhere over Oklahoma or southern Kansas as the object’s contact faded and the RB-47 returned toward Forbes AFB.

Witnesses

All six crew members are commissioned Air Force officers; all held security clearances appropriate to a strategic reconnaissance mission.

Major Lewis D. Chase (Pilot / Aircraft Commander) — Chase was the pilot flying and the primary visual witness from the flight deck. He described the initial contact as a blue-white light of exceptional intensity closing from ahead and to the right, then pulling into position ahead of the aircraft. His visual report and the ELINT and radar readings were consistent in azimuth and timing. Chase was formally interviewed during the Project Blue Book investigation.

1st Lieutenant Frank B. McClure (Electronic Warfare Officer, Position 1) — McClure was the first crew member to detect the anomaly, via the APD-4 ELINT receiver. His detection preceded the visual contact, which means the electronic signature was present before the crew had any reason to be looking for something unusual. McDonald considered this sequencing particularly significant: McClure was not primed by a visual report to interpret his instruments as anomalous.

The remaining four crew members — Captain James H. McCoid (co-pilot), Captain Thomas H. Hanley (navigator), Captain John J. Provenzino (navigator), and 1st Lieutenant Walter A. Tuchscherer (Electronic Warfare Officer, Position 2) — were also aboard and gave consistent accounts to investigators. McDonald’s 1969 AAAS paper notes that the navigator Hanley independently confirmed multiple aspects of the event’s timeline.

Duncanville Air Defense Control Center operators — Ground radar controllers at Duncanville confirmed the target on their radar scope when queried by the aircraft. Their contact was independent of the crew’s sensor readings and constitutes a fourth observation modality (ground-based radar) corroborating the others.

Official Response

Project Blue Book investigators took the case seriously by their own standards. The file was assigned number 4703. Interviews were conducted with the crew, and the Air Defense Command ground radar data was obtained. After review, the case was stamped unidentified — one of the few hundred cases in the Blue Book database to receive that designation rather than being attributed to a known natural or man-made phenomenon.

The case attracted renewed attention when Dr. James McDonald, a senior atmospheric physicist at the University of Arizona and a member of the American Meteorological Society, obtained access to the Blue Book files in the late 1960s. McDonald’s working assumption was that many UFO cases would resolve to mundane explanations on close examination; the RB-47 case was one of a handful he concluded did not. He presented a detailed analysis to the American Association for the Advancement of Science in December 1969, characterizing it as “perhaps the most significant” instrumental UFO case on record and noting that the official Blue Book investigation had left the sensor-correlation question unresolved.

The Condon Report, published in 1969 as the Air Force’s commissioned scientific review of UAP evidence, examined the case in detail as Case 5. The report’s investigator (Dr. Roy Craig is believed to have handled this case, though the report lists no individual attribution for every case) wrote: “In conclusion, although conventional or natural explanations certainly cannot be ruled out, the probability of such seems low in this case and the case must be listed as unidentified.” The report noted specifically that the simultaneous triple-sensor correlation was the factor most resistant to routine explanation.

NICAP documented the case independently through its investigator network and has maintained the most comprehensive public case archive. Researcher Brad Sparks conducted a detailed reconstruction of the flight path and sensor-contact timeline, which is available through NICAP and addresses several specific claims made by skeptics.

The Air Force closed Project Blue Book in 1969 without revisiting the case. AARO has not publicly addressed the RB-47 incident in any of its historical review disclosures as of August 2026.

Mundane Explanations Considered

Radar anomalies / atmospheric ducting — Under certain atmospheric temperature inversion conditions, ground-based radar signals can be ducted over long distances and appear to interrogating receivers as aerial contacts. This could theoretically explain an anomalous ELINT return from a ground-based emitter appearing to move. However, ducting would not explain the APQ-56 skin-paint radar contact on the aircraft, and it would not explain the correlated visual observation by the flight crew. Three independent anomalies of three different physical types occurring simultaneously at the same azimuth and distance over a ninety-minute window is not a parsimonious account.

Another aircraft, unreported — The simplest aerial explanation is that an unidentified conventional aircraft operated in the same airspace without a flight plan. However, the object’s reported behavior — including apparent stationary hover, extremely rapid acceleration, and descent from altitude to ground level followed by halt — is inconsistent with any jet or propeller aircraft available in July 1957. The Duncanville radar contact also remained unexplained; Air Defense Command would have been able to correlate any tracked military flight against the return.

Electronic countermeasures (ECM) testing — Skeptic Donald Menzel proposed that the ELINT receiver contact was the result of a classified ground-based electronic countermeasures or radar-jamming test that could produce an apparent moving signal on the APD-4. This is theoretically possible, but it requires assuming that a classified program of which the Air Force chose not to inform its own Blue Book investigation existed, was operating at the right frequency, and coincided with the crew’s simultaneous visual and radar contacts. No classified ECM program operating on that night in that area has subsequently been acknowledged.

Ball lightning or plasma phenomenon — Luminous atmospheric plasma phenomena have been proposed as explanations for some UAP cases, and some researchers have applied such models to the RB-47 case given the description of a brilliant blue-white light. However, ball lightning does not emit coherent S-band electromagnetic signals, does not produce skin-paint radar returns on military fire-control radars, and does not travel at speeds comparable to a B-47 Stratojet for ninety minutes across multiple states. The plasma explanation does not survive contact with the full sensor dataset.

Meteor or re-entry event — Single visual UAP sightings are frequently misidentified meteors. The RB-47 encounter lasted ninety minutes, involved multiple crew members observing a sustained phenomenon that matched their aircraft’s speed, and generated electronic contacts on multiple systems. Meteors do not produce sustained S-band ELINT signals; they do not match aircraft speeds for extended periods.

Instrument malfunction — For the case to be explained as instrumentation error, the APD-4, the APQ-56, the Duncanville ground radar, and the eyes of two or more pilots would all have to malfunction or be misread simultaneously, with the malfunctions correlating across independent systems in real time. The probability of correlated failure of this type is low; the crew and ground controllers were operating under standard military procedures and had no prior expectation of a UAP event.

Open Questions

• The precise frequency of the ELINT signal was noted in the APD-4 data. Brad Sparks’ reconstruction identifies it as a recognized radar band used by both US Air Force ground radars and Soviet intelligence collection assets of the era. Whether the signal characteristics more closely match a specific known system has not been definitively resolved in publicly available literature.
• The Duncanville GCI radar track data appears in the Condon Report description but the raw track records have not been publicly released in detail. The disposition of those records in the National Archives has not been confirmed.
• Whether any classified Air Defense Command logs from Duncanville for the date in question exist and have been reviewed by AARO’s historical case program is not known. The AARO FY2025 report (Case #00471) does not address the 1957 RB-47 incident.
• McDonald repeatedly requested that the Air Force release the full unredacted Blue Book file. The degree to which his published analysis reflects complete access to the original documentation is unclear; some researchers believe the file held in Project Blue Book Case 4703 is not the complete record of the inquiry.
• The behavior described — object holding position ahead of a strategic reconnaissance aircraft, then moving at will — raises the question of whether similar ELINT contacts were recorded by other 55th SRW crews during this period. No comparable adjacent case from the same wing has been publicly identified.

The Council’s Verdict

Inconclusive.

The RB-47 incident’s evidentiary value lies in what it is, not what it implies. Three independent sensor types — an ELINT receiver, an airborne radar, and a ground radar — all logged contact with the same position at the same time. The crew observed the phenomenon visually. The event lasted ninety minutes. Project Blue Book rated it unidentified. The Condon Report, a study commissioned specifically to find conventional explanations, could not find one and said so in print.

What this establishes is that something physically real was present in that airspace and was detectable by the instruments of the day. What it does not establish is what that something was. The multi-sensor correlation rules out most single-cause mundane explanations, but it does not, in itself, confirm a conclusion about origin or nature. The Council will not reach beyond the data.

The strongest conventional candidate — an untracked military aircraft — fails on the behavioral evidence. The strongest non-conventional candidates remain unverified. “Inconclusive” in this case is not a diplomatic hedging but an honest statement about the evidence ceiling: the data is better than almost any contemporaneous UAP report, and it still does not close the question.

The comparison to Case #00029 (the 1976 Tehran F-4 incident) is instructive. Both involve military aircrews, radar confirmation, and a phenomenon that responded to the pursuit aircraft’s behavior. Tehran added attempted weapons-system engagement and avionics interference. The RB-47 case adds ELINT data Tehran lacks. Neither case resolves. Together they define a pattern of highly credentialed, multi-sensor military encounters that Project Blue Book and the Condon Report could not explain — and that AARO has not yet revisited in public reporting.

For the pattern of UAP operating near military assets in the 1950s, see also Case #00006 (Levelland vehicle-interference reports, November 1957, the same calendar year) and Case #00072 (Lakenheath-Bentwaters radar-visual, 1956, the year prior). The cluster of credible, documented cases in this period is not consistent with a hypothesis of mass fabrication.

Sources

1. Scientific Study of Unidentified Flying Objects (Condon Report), Case 5. University of Colorado, 1969. Commissioned by the U.S. Air Force; examined by Dr. Edward U. Condon and staff. Case 5 is available at the National Center for Atmospheric Research (NCAS) online archive.
2. Dr. James E. McDonald, “Science in Default: 22 Years of Inadequate UFO Investigations,” presented to the American Association for the Advancement of Science, December 1969. Reprinted in UFOs: A Scientific Debate (Cornell University Press, 1972), eds. Carl Sagan and Thornton Page.
3. NICAP Case File: RB-47 Incident, 17 July 1957. nicap.org/570717dir.htm. Includes crew accounts and investigative notes.
4. Brad Sparks, “RB-47 Case: The Best UFO Radar Case Ever?” Reconstruction of flight path and sensor-contact chronology. NICAP, nicap.org/570717sparksdir.htm.
5. Project Blue Book, Case 4703. U.S. Air Force / National Archives. Available via Fold3 USAF records database.