On the evening of 9 August 1952, a Marine pilot near K-3 airfield in southeastern Korea reported an unfamiliar object with a fiery head and a long trail. A ground controller had noticed unusual radar blips shortly beforehand. Their apparent agreement became an intelligence report, but the surviving papers also record uncertainty over whether those blips belonged to one target, several aircraft or interference.
The eight-page Project Blue Book packet is unusually useful because it preserves more than its final index card. The card classifies the object as a meteor. The detailed cover describes that identification as tentative, while the controller’s statement explains how an initially disconnected set of radar indications became associated with the pilot’s sighting. UKPX assesses the encounter as Possibly Explained: a meteor was the contemporary officers’ preferred explanation, with important limits to the claimed radar corroboration.
A pilot’s brief view near K-3
The geographical anchor is K-3, identified as Pohang in the National Institute of Korean History’s account of wartime airfields. The intelligence cover’s country field says Japan, reflecting the reporting organisation; its area-of-report field explicitly says southeastern Korea. The incident should therefore remain located in South Korea rather than be moved to Japan by a catalogue field.
The pilot’s account reaches us through relayed messages and summaries, rather than a signed statement by the pilot. One summary places the aircraft near K-3, on a course of 005 degrees, flying at 9,400 feet and 240 knots. It says the pilot reported a long flame streamer with a fiery ball at its front, passing roughly 500 yards off his starboard wing and about 1,000 feet higher. The observation was brief and the closing speed was described as very high.
Another relay described a dark object with fire at its rear, unlike the exhaust the pilot recognised. These descriptions should not be silently combined into a detailed, stable silhouette. The daily summary uses the call sign Richman 18; the controller’s own statement repeatedly uses Richmond 18. The packet concerns the same encounter, but its wording passed through several people and documents.
What the radar controller actually recorded
Second Lieutenant Leo N. Nagrodsky’s statement is dated 11 August. He had been senior watch controller at Marine Ground Control Intercept Squadron 3 from 20:00 to midnight on the ninth. At about 20:47 he was adjusting the tuning of his controller’s radar display while following an inbound aircraft subsequently identified as Richmond 18.
At approximately 20:50, with the known aircraft about 20 miles away, he saw a weak target at a bearing of 205 degrees and a range of 15 miles. It did not return on the next sweep. He initially attributed it to interference. On the third sweep a target appeared at the same bearing but at 27 miles, and on the fourth at 32 miles. He did not initially connect these widely separated returns.
On the fifth sweep, about fifty seconds after the first faint indication, he saw a stronger, peculiar blip at 206 degrees and 38 miles. He described it as roughly two miles long and curved away from the appearance of an ordinary target. No further unusual blips appeared. At that stage he thought the indications had probably been interference.
These were recollections written down several minutes later, with an estimated accuracy of two miles and five degrees. The radar teller’s display was tuned less sensitively and its operator did not see the unusual returns. Nagrodsky had not drawn that operator’s attention to them because he was already reporting the normal aircraft accurately and the extra marks seemed unconvincing. This is a documented radar report, but it is not two operators independently tracking a continuous object.
How the two accounts became connected
At about 20:57, the pilot checked in and asked whether the controller had seen plots in his vicinity seven to nine minutes earlier. Nagrodsky replied that he had seen what might have been several aircraft or noise. The pilot’s description prompted him to reconsider whether the disconnected marks could instead represent a single fast track.
He discussed the matter with Captain Vernor, the assistant operations officer, then wrote down the remembered times, ranges and bearings before sending a report to the control station Devastate Able. The telephone circuit was weak. His statement says he repeated the message three times before it was correctly read back, with that exchange ending at about 21:23. The communication difficulty is part of the source trail, rather than proof that any particular detail was corrupted.
Nagrodsky calculated that a single track through the recalled positions would imply about 1,200–1,400 knots. Finding that excessive, he considered whether two aircraft following each other might account for the marks at lower speeds. Different portions of the packet use different ranges and speed units: its daily summary gives grid positions and ranges that do not exactly match his fuller narrative. The figures are contemporary estimates, not a modern reconstruction from original radar film.
Why officers favoured a meteor
At about 23:00, members of the incoming watch discussed a meteor they had seen while at a film showing. They described a long, brilliant trail and placed it at approximately the time of the radar indications. Nagrodsky reported this further information to Devastate Able, whose controller agreed that the meteor was probably what had appeared on his display.
The squadron commander endorsed the meteor interpretation and suggested that the earlier effort to explain the observations conservatively had underestimated the speed if they represented one track. The preparing officer also argued that the nearly constant bearings in the written statement suited a meteor better than the slightly erratic course suggested by the plotted drawing. The acknowledged position errors weakened any argument for a precisely manoeuvring trajectory.
The cover report, dated 25 August, retained the qualification that the object had been tentatively identified. The later record card compressed the result into an astronomical classification. The packet contains neither a recovered meteorite nor an independently determined meteor trajectory matching the pilot, radar and ground witnesses. Its physical arguments remain the reporting officers’ interpretation of the available accounts.
Assessment and location
The meteor proposal has specific contemporary support: the reported fiery trail, the approximate timing of another group’s observation and the broadly constant radar bearings. Its weakness is the unproven association between those observations. Several faint returns, reconstructed after the event, need not establish the position or speed of the briefly seen light. A useful assessment preserves both the proposed ordinary explanation and that evidential gap.
The map pin is an approximate K-3/Pohang airfield-area reference, rounded to 35.99, 129.42 from the Republic of Korea aeronautical publication’s airport reference coordinates. It does not locate the historic radar room, the aircraft at the moment of observation or a point on the object’s flight path. No access to operational areas is implied, and no case-specific public visitor site has been verified.
Sources and reading the original
Read the complete eight-page government packet, especially the controller’s opening statement on scan page 4 and its continuation on page 3. The commander’s discussion begins on page 6 and continues through the preparing officer’s comments on page 5; pages 7–8 contain a radar plot and area sketch. The scan order is not the narrative order. The documentary image above reproduces the intelligence cover, rather than a photograph of the reported object.