3 ms·
Not the parent, but how do you explain something like this? https://en.wikipedia.org/wiki/1952_Washington,_D.C.,_UFO_incident https://en.wikipedia.org/wiki/1952
by z7 3y ago
Not the parent, but how do you explain something like this?
https://en.wikipedia.org/wiki/1952_Washington,_D.C.,_UFO_incident https://en.wikipedia.org/wiki/1952_Washington,_D.C.,_UFO_inc...
- nobody9999 3y ago>Not the parent, but how do you explain something like this? https://en.wikipedia.org/wiki/1952_Washington,_D.C.,_UFO_inc https://en.wikipedia.org/wiki/1952_Washington,_D.C.,_UFO_inc... I don't have to. Your link did so for me: "At the request of the Air Force, the CAA's Technical Development and Evaluation Center did an analysis of the radar sightings. Their conclusion was that "a temperature inversion had been indicated in almost every instance when the unidentified radar targets or visual objects had been reported."[29] Project Blue Book would eventually label the unknown Washington radar blips as false images caused by temperature inversion, and the visual sightings as misidentified meteors, stars, and city lights.[30] In later years two prominent UFO skeptics, Donald Menzel, an astronomer at Harvard University, and Philip Klass, a senior editor for Aviation Week magazine, would also argue in favor of the temperature inversion/mirage hypothesis.[31] In 2002 Klass told a reporter that "radar technology in 1952 wasn't sophisticated enough to filter out many ordinary objects, such as flocks of birds, weather balloons, or temperature inversions."[7] The reporter added that "UFO proponents argue that even then seasoned controllers could differentiate between spurious targets and solid, metallic objects. Klass disagrees. It may be that 'we had two dumb controllers at National Airport on those nights'...[Klass] added that the introduction of digital filters in the 1970s led to a steep decline in UFO sightings on radar."[7]"
- z7 3y agoHow does that explain the eyewitness accounts? >Staff Sgt. Charles Davenport observed an orange-red light to the south; the light "would appear to stand still, then make an abrupt change in direction and altitude ... this happened several times." >Nugent's superior, Harry Barnes, a senior air-traffic controller at the airport, watched the objects on Nugent's radarscope. He later wrote: We knew immediately that a very strange situation existed ... their movements were completely radical compared to those of ordinary aircraft. >Barnes then called National Airport's radar-equipped control tower; the controllers there, Howard Cocklin and Joe Zacko, said that they also had unidentified blips on their radar screen, and saw a hovering "bright light" in the sky, which departed with incredible speed. >Airman William Brady, who was in the tower, then saw an "object which appeared to be like an orange ball of fire, trailing a tail ... [it was] unlike anything I had ever seen before."[3][5] As Brady tried to alert the other personnel in the tower, the strange object "took off at an unbelievable speed. >On one of National Airport's runways, S.C. Pierman, a Capital Airlines pilot, was waiting in the cockpit of his DC-4 for permission to take off. After spotting what he believed to be a meteor, he was told that the control tower's radar had detected unknown objects closing in on his position. Pierman observed six objects — "white, tailless, fast-moving lights" — over a 14-minute period. >At one point both radar centers at National Airport and the radar at Andrews Air Force Base were tracking an object hovering over a radio beacon. The object vanished in all three radar centers at the same time.
- mjan22640 3y agoA temperature inversion or another atmospheric phenomena would move at wind speed, not at an "unbelievable" speed.