FOLLOW US

USA Herald - A declassified Air Force radar report from July 1952 remains one of the most technically rigorous — and most unsettling — UFO cases in American military history.

It was just past one in the morning on July 13, 1952. The duty crew of the 674th AC&W Squadron — Aircraft Control and Warning — were settled into the quiet rhythms of a night shift at their radar station in Osceola, Wisconsin. Outside, a fierce summer storm was rolling through. Heavy rain sheeted across the darkened landscape. Lightning split the sky in irregular bursts. It was not, by any measure, a night you'd expect to find anything unusual on the scopes.

And then they appeared.

Eleven of them.

What followed over the next forty-eight minutes and ten seconds would be documented in a three-page Air Intelligence Information Report — AF Form 112 — filed by Lt. Colonel Willard L. Worden, commanding officer of the 674th. The report, eventually declassified and archived in Project Blue Book files, is not a breathless account of lights in the sky. It is not the garbled testimony of frightened civilians. It is a meticulous, clinically worded military document, signed by trained radar operators with years of experience, describing objects that moved at speeds no aircraft in 1952 — or arguably since — could match.

It describes objects traveling at between 12,000 and 20,000 knots.

To put that in perspective: a modern fighter jet cruises at roughly 500 knots. The fastest aircraft ever flown by the United States military, the SR-71 Blackbird, topped out near 1,900 knots. Whatever the radar operators of the 674th were tracking that stormy July night was moving at somewhere between six and ten times the speed of the fastest jet ever built — and it wouldn't be built for another decade.

The Men Behind the Scopes

Before examining what was seen, it is worth establishing who was doing the seeing. The report is careful on this point. The sightings, it states plainly, were "made and recorded by competent personnel using Electronic Sighting equipment." This was not a case of one bleary-eyed airman misreading a smeared scope in the small hours of the morning.

Three personnel are named and identified in the report. First Lieutenant D.C. Miller of AFSC 1635, with two years and seven months of experience. Staff Sergeant A.C. Harris of AFSC 27350, with two years of experience. Airman Second Class W. Anderson, also of AFSC 27350, also with two years of experience. These were not rookies. They were trained radar operators who understood the difference between genuine returns and radar anomalies, between aircraft and atmospheric artifacts, between something real and something spurious.

The equipment they were using was equally well-documented. The AN/FPS-6B radar set, operating at a frequency between 2,725 and 3,000 megacycles per second, with a Pulse Repetition Frequency of 300 pulses per second, an antenna rotating at six revolutions per minute, and a power output of twenty-eight milliamps. The antenna was tilted at two and a half degrees. All meter readings, the report notes, were normal. The set was functioning properly at the time of the sightings.

In other words: the equipment was working. The operators were qualified. What they tracked was real.

What the Radar Showed

The objects appeared on the scope at 1:35 in the morning. The last contact was logged at 2:22. Forty-eight minutes. Ten seconds.

They came in groups and sequences, each tracked individually and assigned a point number. The report works through them methodically, one by one, like a dispatcher logging freight movements — except these objects were not freight, and nothing about their behavior resembled conventional aviation.

Point 1 appeared 182 statute miles to the east of the sighting station at 1:38 in the morning, moving westward toward the station. It was tracked at 14,000 knots to a position 81 miles east of the radar station, where it vanished into the ground clutter — the zone of radar interference that immediately surrounds a fixed radar installation. It was gone in moments.

Point 2 materialized 185 miles to the east at 1:41, also inbound, also at 14,000 knots. Same behavior. Same destination. Swallowed by the clutter.

Point 3 came from further out — 245 miles east-southeast — at 1:02, tracked at 12,000 knots to within 126 miles before disappearing.

Point 4 is perhaps the most striking single contact in the report. It appeared 220 miles east-southeast of the station, inbound at 18,000 knots — and it simply did not vanish into the clutter the way the others had. It kept going. The track continued past the station, out to 260 miles on the other side, where it finally exceeded the limits of the equipment. It had crossed the entire range of the radar — inbound and outbound — in a matter of minutes.

Point 6 was tracked at 20,000 knots. Twenty thousand. At that speed, an object crosses the full 270-nautical-mile radar range in less than a minute. The operators would have watched it sweep across the scope in perhaps forty-five seconds.

The remaining points — through Point 11 — repeat variations of the same pattern. Objects appearing at distances between 176 and 260 statute miles from the station, on bearings ranging from due east to south-southeast, tracked at speeds clustering around 14,000 knots, all eventually lost in ground clutter or at the edge of the equipment's range. No object, the report is careful to note, passed over or beyond the sighting station itself. The inbound contacts all disappeared before reaching it. The outbound contacts originated outside the clutter zone and were last seen heading to the far edge of the scope.

The Shape of the Unknowns

The objects were not simple blips. The report describes them in precise technical language: solid centers with slightly fuzzy edges. Each left a trail — a "comets tail" of one nautical mile in length. Here the report offers a telling calibration point. The operators compared this comet's tail to what a known aircraft produces under the same conditions. An F-86 Sabre — at the time, one of the most advanced jet fighters in the American arsenal — traveling at 400 knots on the same 270-nautical-mile scope scale leaves an identical one-mile comet's tail.

This comparison is significant. It means the radar operators were not simply eyeballing alien returns with no frame of reference. They had a known standard — the trace profile of a military jet — and the unknowns matched that profile exactly, at the same scale. The objects were behaving, from a radar signature standpoint, like real, solid, physical things moving through space. Not weather. Not interference. Not malfunctioning equipment.

Their size, as computed on the radar scope, was between ten and fifteen square miles. This is not a measurement of the object itself, necessarily — radar scope representations are subject to scale distortions at range — but it speaks to the intensity and consistency of the returns. These were strong, clear, confident signals.

The Weather That Shouldn't Have Helped — But Might Have

The weather section of the report is, in its own way, fascinating. At the time of the sightings, the area around the station was experiencing heavy rain and intense lightning. Immediately after the sightings ended, the report notes, the station weather cleared to scattered clouds of undetermined height, with no rain or lightning.

Heavy cloud formations were present during the sightings, evidenced by intense ground clutter on the radar scopes — the same clutter that swallowed the inbound objects. During the interval of sightings, this distant ground clutter was lessening constantly, so that by the end of the event it had almost disappeared, suggesting decreasing cloud cover in the viewing area.

One natural instinct, reading this, is to reach for a weather explanation. Could the returns have been anomalous propagation — a well-known radar phenomenon in which temperature inversions in the atmosphere cause radar waves to bend and return echoes from distant ground objects, creating false targets on the scope? It has been invoked to explain radar UFOs before and since. The Air Force itself would use it liberally throughout the 1952 wave.

But there are problems with that explanation here. Anomalous propagation typically produces stationary or very slowly drifting returns, not contacts tracking at 12,000 to 20,000 knots with clear directionality and consistent comet tails. It does not produce objects that execute defined tracks across the scope from one edge to another. And critically — the radar operators were experienced. They knew what weather interference looked like on their equipment. The report makes no mention of any such consideration by the operators themselves.

Wind conditions aloft were unknown. Radar turbulence was indicated from local cloud action. But no proposed meteorological mechanism adequately accounts for eleven discreet objects, each with a directional track and a measurable speed many times faster than any known technology.

No Scramble, No Answers

The report's section on interception action is terse, almost resigned: "None undertaken because F-51 non A-1 equipped only aircraft available and, in consideration of the weather, it was deemed inadvisable to scramble them."

The F-51 Mustang — a World War Two-era propeller aircraft — was the only plane available to the 674th that night. Even in good weather, sending a propeller-driven fighter after contacts moving at 14,000 knots would have been an exercise in futility. Whatever these things were, there was no catching them.

No routine air traffic was sighted during the same period, even though extra care was exercised. No conventional aircraft. No friendly formations. Nothing that could explain, by contamination or confusion, what had appeared on the scopes.

Under "Conditions Accounting for Sightings," the reporting officer wrote: "Nothing that has not been stated."

Under "Existence of Evidence": "None."

The report was filed on July 22nd. It was signed and passed to Air Defense Command headquarters. And then, two months later, it received a brief addendum. Captain R.L. James, writing on September 22, 1952, added a single paragraph: "The targets described in this report are believed to have been caused by an interfering radar set, possibly the same one that caused interference on 25 July 1952."

One sentence. No technical analysis. No supporting evidence. An interfering radar set — from where? Generating eleven separate, individual, directional tracks at speeds of 12,000 to 20,000 knots, each with the correct profile of a real solid contact? The explanation, offered two months after the fact with no elaboration, reads less like a conclusion than a dismissal.

The Summer of 1952

It would be a mistake to read the Osceola report in isolation. July 1952 was, by any reckoning, the most intense month of UFO activity in the early Cold War era. The famous Washington, D.C. incidents occurred just days later, on the nights of July 19-20 and July 26-27, when unknown objects were tracked on radar over the nation's capital and scrambled jets found nothing. The Air Force held a press conference — the largest since World War Two, some accounts say — to explain the Washington sightings as temperature inversions.

The explanation did not fully satisfy. Radar operators in Washington, like those in Osceola, had years of experience. They knew what inversions looked like. They said, repeatedly and on the record, that these were not inversions.

The Osceola case never attracted the public attention of the Washington incidents. There were no newspaper headlines, no congressional questions, no press conferences about a radar station in rural Wisconsin. But in some ways the Osceola report is more compelling precisely because of what it lacks. There are no civilian witnesses to question, no ambiguous visual sightings to reinterpret, no possibility of mass hysteria or misidentified stars. There is only a radar scope, trained operators, functioning equipment, and eleven objects moving at velocities that should not have been possible.

What We Are Left With

The file sits in the Project Blue Book archives, cross-referenced as case IR-1-52C. It is marked unclassified. The radar charts are attached — hand-drawn plots of the object tracks on a 270-nautical-mile scope scale, the trajectories sketched in careful loops and arrows across the semicircular grid. They look almost gentle, these lines. Small notations in pencil. Numbers in circles. The mundane paperwork of something that, seventy years on, has no satisfactory explanation.

Eleven objects. Unknown shape. Solid radar returns. Speeds between 12,000 and 20,000 knots. Forty-eight minutes. No interception. No conventional explanation that survives contact with the technical details.

Captain James's suggestion of a rogue radar set — offered without evidence, two months late — has not aged well. No interfering radar produces directional tracks at hypersonic velocities. No weather phenomenon leaves a comet's tail identical to that of a jet fighter. No known 1952 technology, American, Soviet, or otherwise, moved at ten times the speed of the fastest aircraft on earth.

The men of the 674th AC&W Squadron — Miller, Harris, Anderson, and the others on duty that stormy night — did their jobs. They tracked what appeared on their scopes, they documented it precisely, they filed their reports up the chain. They offered no dramatic interpretations. They did not claim to know what they had seen.

They only said: something was there.

Seventy years later, we are no closer to knowing what.

source: Air Intelligence Information Report IR-1-52C, 674th AC&W Squadron, Osceola, Wisconsin, filed 22 July 1952 by Lt. Col. Willard L. Worden, USAF. Archived in Project Blue Book files (MAXW-PBB12-119-123, 125, 129). Available via the National Investigation Committee on Aerial Phenomena (NICAP) document archive.