Global UFO Archive
English中文日本語PortuguêsFrançaisEspañol

United States / 1953 / DISPUTED

1953 Ellsworth AFB radar-visual report

The public Air Force file identifies this as a 5-6 August 1953 chain of reports around Black Hawk, Rapid City and Ellsworth Air Force Base, South Dakota. A Ground Observer Corps report prompted radar searches and two F-84 responses; pilots and ground witnesses described bright, changing lights, while controllers logged numerous returns. The file also preserves important limits: radar-scope photographs failed, gun-camera film was blank, positions were not continuously matched, and one pilot wrote that a principal light could have been a star or planet affected by refraction. Project Blue Book investigated and a status report left the case unsolved pending further study. Edward Ruppelt later called it his best unknown, but his 1956 memoir shifted the same story to 12-13 August and dramatized some correlations beyond the surviving statements. A 1968 Colorado Project analysis instead attributed the sequence to stars viewed through inversion layers, at least one meteor, anomalous-propagation echoes, a possible ghost echo and a malfunctioning airborne gunsight. That later explanation is substantial but inferential. The safest conclusion is a documented radar-visual investigation with disputed interpretation—not proof of an extraordinary craft.

Archive cover for the 1953 Ellsworth AFB radar-visual report
This locally authored archive cover identifies the dossier only. It is not an event photograph, a reconstruction, a radar plot or evidence of the reported lights.Global UFO Archive editorial
CredibilityC
StatusDISPUTED
Evidence types8
Official sources3
Last reviewed2026
Archive assessment

This case is disputed. The archive preserves the claims while separating evidence from interpretation.

Documentation
High documentation
Primary location
Black Hawk and Rapid City near Ellsworth AFB, South Dakota
Source base
7 linked records
Research use
Comparison case

What the Ellsworth file establishes

Identity
Ellsworth AFB, South Dakota—not Ellington AFB, Texas. The canonical ID is a legacy mismatch.[1][5][6]
Date
Signed records establish 5-6 August 1953. Ruppelt's later 12-13 August dating conflicts with them.[1][3][4]
Confirmed
Blue Book investigated reports involving ground observers, two F-84 responses and radar personnel.[1][2]
Media limit
Radar photographs failed and gun-camera film was blank; no authenticated event image survives in the reviewed file.[1]
Assessment
A later stars-meteor-propagation explanation is plausible but inferential; the case remains disputed, not extraordinary.[1][4]

Case dossier

Ellsworth, not Ellington

The place-name issue is not ambiguous in the primary record. The 740th Aircraft Control and Warning Squadron report names Rapid City, Black Hawk and Ellsworth AFB in South Dakota. Air Force installation history says Rapid City AFB received the Ellsworth name in June 1953, before the August reports. Ellington AFB was a separate navigator-training base near Houston, Texas. [1] · [5] · [6]

The Black Hawk reports

At about 20:05 MST on 5 August, Ground Observer Corps volunteer Phyllis Killian reported a bright red light near Black Hawk. Her signed statement says it changed toward green while moving, returned near its starting area and later reappeared. Other local observers described star-like, multicoloured lights that appeared, vanished and seemed to move when jets approached. These are witness estimates made without measured range; they do not by themselves establish one solid object or one continuous path. [1]

Two F-84 responses

Controllers searched the 740th squadron radar after the visual call and reported many blips, some lost in ground clutter. One airborne F-84 was directed toward reported positions and briefly saw a bright white light pulling away. A second F-84, flown by 1st Lt. David K. Needham, reported a white-to-green light and an A-4 gunsight lock indication while climbing. Needham also wrote that the lock light blinked after he turned away, giving him the impression of a malfunction. [1] · [2]

A lock light without a measured range

The Blue Book interview extract distinguishes the illuminated gunsight indicator from an actual distance reading. It says no range was obtained: the sight began measuring at about 4,000 yards, and the indication could at most suggest something beyond that range. The same account records intermittent indications on the return flight and says maintenance had not checked the sight at the time of the investigation. Needham’s signed statement likewise describes removing the flashing bulb. A reported lock is therefore neither a measured separation from the light nor a technically verified radar detection; the suspected malfunction was not established by a documented bench test. [2] · [1] · [7]

Why the photographs cannot settle it

The surviving media record is negative. The report says thirteen radar-scope photographs did not develop because the camera mechanism failed. Needham exposed about forty feet of gun-camera film, but it was blank. No authenticated event photograph, usable radar plot or motion-picture evidence is therefore available in the reviewed public file. Later illustrations and UFO imagery cannot be substituted for the missing 1953 records. [1]

The investigation remained open

Project Blue Book sent an investigator because the report combined ground visual, airborne visual, ground radar and airborne radar claims. The available Status Report No. 12 extract describes those interviews; the contemporary trip report explicitly reached no definite conclusion and recommended further study. That uncertainty does not certify that every return and light was the same physical target or that conventional causes were excluded permanently. [2] · [7]

The 1953 trip report and its limits

An annotated trip report headed 17 August 1953 provides a contemporary counterweight to the memoir. It records departure from Dayton on 10 August and a meeting at Ellsworth on 11 August. The Navy balloon checks found no matching Navy flight, but the report also mentions untraced or lost balloons; this was not an exclusion of every balloon. It explicitly says the investigator did not visit Bismarck or personally interview the Black Hawk observers on that trip. Its conclusion remained uncertain and recommended further study by Hynek and Futch. These documented limits matter when reading the memoir’s claim to have interviewed everyone. [7] PDF 18–21 · [3]

The memoir’s conflicting date

Ruppelt's 1956 book is a participant memoir, not the contemporaneous case form. Its Ellsworth sequence closely matches the base, Black Hawk observer, radar controller and two F-84 responses, but it dates the event to the night of 12 August and his call to 13 August. The signed Air Force statements repeatedly say 5 August, the report was dated 8 August, and the later Colorado analysis also uses 5-6 August. The page therefore treats 5-6 August as established and Ruppelt's shifted date as an unresolved retrospective discrepancy. [1] · [3] · [7]

The Colorado Project explanation

The Colorado Project revisited the sequence in 1968 using astronomical positions and refractivity profiles. Gordon Thayer proposed Pollux for one chase, Mirfak for another, a meteor for a fast ground sighting, anomalous-propagation echoes on the GCI radar and a possible ghost echo that paced the fighter. He also cited Needham's own malfunction impression. The analysis concluded that this combination could account for the Rapid City-Bismarck sequence. It is the strongest developed conventional explanation, but it reconstructs conditions fifteen years later and cannot convert every uncertain observation into a separately proved identification. [4]

What the weather profiles show

Thayer’s weather argument uses profiles from different times, not a continuous measurement along either fighter’s path. At Rapid City, the 20:00 profile showed only a weak inversion; the much stronger elevated duct came from the 08:00 profile the following morning. His explanation inferred overnight formation and lifting after sunrise. Bismarck had its own evening surface inversion. These observations support considering unusual propagation, but the morning profile cannot directly establish the conditions at every earlier radar contact, and the Bismarck sounding does not measure conditions over Ellsworth. [4]

Related checks and records

Timeline

  • Rapid City AFB is renamed Ellsworth AFB before the reported event.
  • Phyllis Killian reports a bright changing light near Black Hawk; the Rapid City filter center relays the call.
  • Radar personnel search reported positions; an airborne F-84 is vectored and briefly sees a bright light.
  • David K. Needham takes off in a second F-84, reports a changing light and later judges the gunsight indication may have malfunctioned.
  • Additional airmen and Bismarck observers report lights; the record does not establish one continuous target across all locations.
  • The 740th AC&W Squadron dates its Air Intelligence Information Report; Blue Book later summarizes the case as unsolved pending study.
  • Ruppelt publishes the same recognizable sequence but dates it 12-13 August, creating a retrospective conflict with the signed file.
  • The Colorado Project publishes a multi-cause conventional analysis involving stars, a meteor, anomalous propagation and equipment effects.

Questions about the 1953 Ellsworth report

Was this at Ellington or Ellsworth Air Force Base?

Ellsworth AFB near Rapid City, South Dakota. The official file repeatedly names Ellsworth and Black Hawk; Ellington was a separate Texas base.

What date did the incident occur?

The signed Air Force statements establish the evening of 5 August into early 6 August 1953. Ruppelt's later 12-13 August date is treated as a memoir discrepancy.

Did radar and pilots confirm the same craft?

They reported overlapping activity, but the public file lacks a continuous calibrated plot. Clutter, failed photographs, shifting positions and a possible gunsight malfunction prevent proof of one target.

Are there authentic photographs?

No usable event image was found. The official report says radar photographs failed and the F-84 gun-camera film was blank.

What did Project Blue Book conclude?

A status report carried it as unsolved pending further study. That is an investigative disposition, not confirmation of extraterrestrial or extraordinary origin.

What is the leading conventional explanation?

The Colorado Project proposed a combination of bright stars seen through inversion layers, a meteor, anomalous-propagation radar echoes, a possible ghost echo and equipment malfunction. It is plausible, though not a separate proof for every observation.

Sources

No authenticated event image or usable radar photograph was found. The official file says the radar camera failed and the gun-camera film was blank.