JULY 2002 SIGHTINGS IN THE SKY

AROUND WASHINGTON D.C.

Note: It all started 50 years ago, in 1952 & 1953:

JULY 13 - JULY 29, 1952 - WASHINGTON DC, USA

WASHINGTON POST: WASHINGTON DC JULY 1952 REPORT

1952, TOP SECRET MEMO: FLYING SAUCERS EXIST"

-------------------------------------

FIRST - THE PRESENT:  26 JULY 2002

Bright Blue UFO Scrambles 113th Squadron Near D.C.

"Routine" Exercise Chasing High Speed UFOs?

http://www.rense.com/general27/bblue.htm

7-26-2

Update:   F-16s Pursue Unknown Craft Over Region

By Steve Vogel, Washington Post Staff Writer
7-27-2
 

For Renny Rogers, it was strange enough that military jets were flying low over his home in Waldorf in the middle of the night. It was what he thinks he saw when he headed outside to look early yesterday that floored him.

"It was this object, this light-blue object, traveling at a phenomenal rate of speed," Rogers said. "This Air Force jet was right behind it, chasing it, but the object was just leaving him in the dust. I told my neighbor, 'I think those jets are chasing a UFO.' "

Military officials confirm that two F-16 jets from Andrews Air Force Base were scrambled early yesterday after radar detected an unknown aircraft in area airspace. But they scoff at the idea that the jets were chasing a strange and speedy, blue unidentified flying object.

"We had a track of interest, so we sent up some aircraft," said Maj. Douglas Martin, a spokesman for the North American Aerospace Defense Command in Colorado, which has responsibility for defending U.S. airspace. "Everything was fine in the sky, so they returned home."

At the same time, military officials say they do not know just what the jets were chasing, because whatever it was disappeared. "There are any number of scenarios, but we don't know what it was," said Maj. Barry Venable, another spokesman for NORAD.

Radar detected a low, slow-flying aircraft about 1 a.m. yesterday, according to a military official. Controllers were unable to establish radio communication with the unidentified aircraft, and NORAD was notified. When the F-16s carrying air-to-air missiles were launched from Andrews, the unidentified aircraft's track faded from the radar, the military official said, speaking on condition of anonymity. Pilots with the D.C. Air National Guard's 113th Air Wing, which flew the F-16s from Andrews, reported nothing out of the ordinary, NORAD officials said.

"It was a routine launch," said Lt. Col. Steve Chase, a senior officer with the wing, which keeps pilots and armed jets on 24-hour alert at Andrews to respond to incidents as part of an air defense system protecting Washington after the Sept. 11 terrorist attacks. Rogers remains convinced that what he saw was not routine. "It looked like a shooting star with no trailing mist," he said. "I've never seen anything like it."

© 2002 The Washington Post Company

---------------------
 

What was that bright light in Maryland's sky?
 

WTOP has learned that residents near Andrews Air Force base were shaken from their beds early Friday morning by some strange activity in the air.

"Incredible. Absolutely incredible" is what Renny Rogers of Waldorf calls it. Just before two in the morning, Rogers says he saw a large blue ball of light streaking across the sky. But it was the military jets that really startled him.

"(The jets) were right on its tail. As the thing would move, a jet was right behind it," Rogers recalls.

He is not the only one who saw it. Several people called WTOP Radio reporting seeing a bright blue or orange ball moving very fast, being chased by jets.

Rogers says there was no smoke coming from the object, no flashing lights, and says it was smooth, and eerily silent.

The Air National Guard confirms they scrambled the 113th squadron. Spokesman Sheldon Smith says they are investigating and in contact with NORAD.
 

WTOP Radio, 2002
http://devtoolkit.wtop.com/news/newsdetail.cfm?newsID=584517
 

--------------------------------------------------------

Comment   From Rex   7-27-2

I see that 113th will scramble Jets for UFOs but not for the Pentagon on 911. Maybe they thought bin Laden was in that UFO? Well, it is good too see our boys up and ready anyway. :)

Rex

--------------------------------------------------------

Comment   Alton Raines   7-27-02

Once again we see the classic obfuscation required of AF and Gov't officials on the UFO issue.

--------------------------------------------------------

Comment   From Walumu   7-27-2

It's about damn time... It was a UFO. I tend not to jump to conclusions but based on the evidence it was, without a doubt, a UFO. The government cannot deny this one and say it's some sort of secret military aircraft because they wouldn't chase their own. And if it was a test chase they would not do it over such a heavily populated area as DC. They cannot hide this one at all. I'm sure as you well know this is just the tip of the iceburg when it comes to the UFO Phenomena and the subsequent 50+ year govenment coverup. We must not let these stories go unheard. It's our job, the people of this country, the people of this planet, to bring attention to these events. There's no better time than now to start. I ask you to tell everyone you know and do your best to get this article out there. For the sake of freedom.

--------------------------------------------------------

All above reports at Rense.com: http://www.rense.com/general27/bblue.htm
 

------------------------------------------------------------------------------------------
 

JULY 13, 2002 :

'NEW JERSEY UFO MANEUVERS'

PARAMUS --Three unknown objects maneuver, pulse, then fade out on a clear on July 13, 2002, night over northern New Jersey. At 11:10 PM, two bright lights, which appeared to be stars, were seen moving slowly in formation on a northeast heading. The atmospheric conditions were clear with visibility unlimited. The two objects appeared high up, and were very bright. Within moments of the sighting, a third, less brilliant object, appeared from the northwest sky behind the first two objects, and flew between them.  It also appeared to be a star. This third object then changed direction to the north and faded completely.  The objects flying in formation then faded completely, and could not be seen. Several moments later one of these a brilliant white light objects pulsed brightly, then faded.  Moments later the third object pulsed brightly, then faded as it continued toward the north.  None of the objects was seen again, though the first two must have been directly overhead. Observers include a police officer and two security officers. One observer holds a private pilot license all concur that the sighting was not that of a conventional aircraft.   Thanks to Peter Davenport NUFORC
 

----------------------------------------

NOW JUMP BACK 50 YEARS TO:

JULY 1952

'ET ARMADA OVER WASHINGTON DC'

- JULY 1952 -
 

Washington Post staff writer Peter Carlson reports on Sunday that,

In the control tower at Washington National Airport, Ed Nugent saw seven pale violet blips on his radar screen. What were they? Not planes -- at least not any planes that were supposed to be there. He summoned his boss, Harry G. Barnes, the head of National's air traffic controllers. "Here's a fleet of flying saucers for you," Nugent said, half-joking. Upstairs, in the tower's glass-enclosed top floor, controller Joe Zacko saw a strange blip streaking across his radar screen. It wasn't a bird. It wasn't a plane. What was it? He looked out the window and spotted a bright light hovering in the sky.

He turned to his partner, Howard Cocklin, who was sitting three feet away. "Look at that bright light," Zacko said. "If you believe in flying saucers, that could sure be one." And then the light took off, zooming away at an incredible speed. "Did you see that?" Cocklin remembers saying. "What the hell was that?"

It was Saturday night, July 19, 1952, fifty years ago -- one of the most famous dates in the bizarre history of UFOs. Before the night was over, a pilot reported seeing unexplained objects, radar at two local Air Force bases -- Andrews and Bolling -- picked up the UFOs, and two Air Force F-94 jets streaked over Washington, searching for flying saucers. Then, a week later, it happened all over again -- more UFOs on the radar screen, more jets scrambled over Washington.
 

Across America, the story of jets chasing UFOs over the White House knocked the Korean War and the presidential campaign off the front pages of newspapers. " 'Saucer' Outran Jet, Pilot Reveals," read the banner headline in The Washington Post. "JETS CHASE D.C. SKY GHOSTS," screamed the New York Daily News. "AERIAL WHATZITS BUZZ D.C. AGAIN!" shouted the Washington Daily News. As rumors spread, President Truman demanded to know what was flying over his house. Soon the federal government was fighting the UFOs with the most powerful weapons in the Washington arsenal -- bureaucracy, obfuscation and gobbledygook. That seemed to work. The UFOs never returned. Snip.

Dr. Bruce Maccabee isn't laughing. "One thing you have to understand: This is serious business," he says. "The skeptics like to make fun of us." Maccabee, 60, is a civilian physicist for the Navy and a prominent UFO believer. Maccabee buttresses his argument with an official government report. It's called "Quantitative Aspects of Mirages" and it was issued by the Air Force in 1969.

"They proved in their own study that there wasn't enough temperature inversion to cause this effect," he says. "The Washington sightings cannot be explained as a radar mirage."

In the '70s, he filed the Freedom of Information Act request that led to the release of the FBI's file on UFOs. The file was called "Security Matter X" -- "the real X-Files," he says.

Maccabee believes there were "solid objects" in the air over Washington 50 years ago. "And I think those solid objects were not made by us," he says. "And by us, I mean human beings."

After 50 years, the debate over the Washington UFOs goes on and on. "You have dueling experts and dueling reports," says Kevin D. Randle, author of "Invasion Washington: UFOs Over the Capitol," a new book on the 1952 sightings. "One expert says it was temperature inversion. Another says it wasn't. In that situation, you have to refer back to the air traffic controllers and the pilots who actually saw the objects." Former controller Howard Cocklin is still convinced that he saw an object over National that night. "I saw it on the screen and out the window," he says. "It was a whitish-blue object. Not a light -- a solid form. An object. A saucer-shaped object."

Now 83 and retired, Cocklin says he never saw anything like that saucer -- not before, not since. "It just went away," he says, sitting in an armchair in his Fairfax living room. "Where did it go? Why don't people see these things today? Why 50 years ago?"
 

Thanks to Washington Post
http://www.washingtonpost.com/wp-dyn/articles/A31625-2002Jul19.html

-------------------------------

FULL WASHINGTON POST ARTICLE:

50 Years Ago, Unidentified Flying Objects From Way

Beyond the Beltway Seized the Capital's Imagination
http://www.washingtonpost.com/wp-dyn/articles/A31625-2002Jul19.html

By Peter Carlson
Washington Post Staff Writer
Sunday, July 21, 2002; Page F01
 

In the control tower at Washington National Airport, Ed Nugent saw seven pale violet blips on his radar screen. What were they? Not planes -- at least not any planes that were supposed to be there.

He summoned his boss, Harry G. Barnes, the head of National's air traffic controllers. "Here's a fleet of flying saucers for you," Nugent said, half-joking.

Upstairs, in the tower's glass-enclosed top floor, controller Joe Zacko saw a strange blip streaking across his radar screen. It wasn't a bird. It wasn't a plane. What was it? He looked out the window and spotted a bright light hovering in the sky. He turned to his partner, Howard Cocklin, who was sitting three feet away.

"Look at that bright light," Zacko said. "If you believe in flying saucers, that could sure be one."

And then the light took off, zooming away at an incredible speed.

"Did you see that?" Cocklin remembers saying. "What the hell was that?"

It was Saturday night, July 19, 1952 -- 50 years ago this weekend -- one of the most famous dates in the bizarre history of UFOs. Before the night was over, a pilot reported seeing unexplained objects, radar at two local Air Force bases -- Andrews and Bolling -- picked up the UFOs, and two Air Force F-94 jets streaked over Washington, searching for flying saucers.

Then, a week later, it happened all over again -- more UFOs on the radar screen, more jets scrambled over Washington. Across America, the story of jets chasing UFOs over the White House knocked the Korean War and the presidential campaign off the front pages of newspapers.
 

"'Saucer' Outran Jet, Pilot Reveals,"
read the banner headline in The Washington Post.

"JETS CHASE D.C. SKY GHOSTS,"
screamed the New York Daily News.

"AERIAL WHATZITS BUZZ D.C. AGAIN!"
shouted the Washington Daily News.
 

As rumors spread, President Truman demanded to know what was flying over his house. Soon the federal government was fighting the UFOs with the most powerful weapons in the Washington arsenal -- bureaucracy, obfuscation and gobbledygook.

That seemed to work. The UFOs never returned. At least, not that we know of.

As Big as Life

In a way, this whole strange episode began with Marilyn Monroe. The actress appeared on the cover of Life magazine's April 7, 1952, issue, looking sultry in a diaphanous, low-cut dress, her eyelids drooping seductively. It was the kind of cover that attracts attention. And just above Monroe's left shoulder was a cover line touting a different story:

"There Is a Case for Interplanetary Saucers."

The article was titled "Have We Visitors From Outer Space?" It reviewed 10 recent UFO sightings and concluded that they could not be written off as hallucinations, hoaxes or earthly aircraft. An unnamed Air Force intelligenceofficer was quoted saying, "The higher you go in the Air Force, the more seriously they take the flying saucers."

The story ended with a series of questions that sound like something Rod Serling might intone at the end of a "Twilight Zone" episode: "Who, or what, is aboard? Where do they come from? Why are they here? What are the intentions of the beings who control them?" It wasn't the first media account of UFOs -- there had been lots of publicity since several well-known sightings in 1947, including one in Roswell, N.M. -- but the Life article marked the first time that a trusted, mainstream magazine had given credence to the theory that UFOs might be alien spacecraft.

The Life story was big news, covered in more than 350 newspapers across America. Soon, the number of UFO sightings reported to the Air Force skyrocketed -- from 23 in March, before Life's article appeared, to 82 in April, 79 in May, 148 in June.

Were these increases due to saucers swarming over America? Or did Life's story make Americans more likely to report strange things they saw in the sky?

By mid-July, Capt. Edward J. Ruppelt -- the head of Project Blue Book, the Air Force's official UFO study team -- was getting 40 reports of UFO sightings a day. Many were bogus but some came from pilots and other respectable citizens, and Ruppelt took them seriously. Then -- a few days before the first sightings at National Airport -- Ruppelt interviewed a government scientist who made a startling prediction that Ruppelt recorded in his 1956 memoir, "The Report on Unidentified Flying Objects."

"Within the next few days," the unidentified scientist said, banging his hand on his desk for emphasis, "you're going to have the granddaddy of all UFO sightings. The sighting will occur in Washington or New York -- probably Washington."
 

'Falling Stars Without Tails'

The blips first appeared on radar screens at National at 11:40 that Saturday night -- seven unidentified targets about 15 miles southeast of the city.

It was a clear, hot, humid night with very little air traffic, and the controllers at National watched the strange blips amble across their screens. They'd cruise at a leisurely rate of about 100 to 130 miles per hour, then abruptly zoom off in an extraordinary burst of speed. "They acted like a bunch of small kids out playing," Barnes, the head controller, wrote a few days later in a piece for a New York newspaper. "It was helter-skelter, as if directed by some innate curiosity. At times, they moved as a group or cluster, at other times as individuals."

Barnes called his counterparts at Andrews and Bolling to ask if they saw anything unusual on their radar screens. They did. They were getting blips in the same places.

At Andrews, controller William Brady looked out the control tower window and saw what looked like "an orange ball of fire, trailing a tail." It was, he later told Air Force investigators, "unlike anything I had ever seen before."

At National, Cocklin looked out his window and saw what he recalls as a "whitish blue light" that emanated from a solid object that was "round with no distinguishing marks such as wings or a nose or a tail." It looked, he says, "like a saucer."

Sometime after 1 a.m, National's control tower radioed Capital Air Flight 807, from Washington to Detroit, and asked the pilot if he saw any unusual objects. Captain S.C. "Casey" Pierman, a pilot with 17 years of experience, radioed back: "There's one -- and there it goes."

For the next 14 minutes, as he flew between Herndon and Martinsburg, W.Va., Pierman saw six bright lights that streaked across the sky at tremendous speed. "They were," he said, "like falling stars without tails."

Watching the radar blips flying over the Capitol and the White House, Barnes called the Air Force to report unidentified aircraft in restricted air space. But it was very late on a Saturday night and the Air Force bureaucracy responded sluggishly. By the time F-94 interceptor jets left New Castle Air Force Base in Delaware -- the runways at Andrews were closed for repairs -- it was after 3 a.m.

When the F-94s soared over Washington, the strange blips disappeared from the radar screens at National. The F-94 pilots cruised around the area for a while but saw nothing. When they headed back to New Castle, the blips reappeared.

The controllers watched the UFOs flit across their screens until dawn, then disappear.
 

Trying to Clear the Air

Nobody bothered to call Ruppelt about the sightings. When he flew to Washington a couple of days later on unrelated Project Blue Book business, he learned about them by reading newspapers at the airport.

"Radar Spots Air Mystery Objects Here," read the headline on the front page of The Washington Post.

"Air Force 'Saucer' Expert Will Probe Sightings Here," said the Washington Daily News.

Ruppelt asked his colleagues who the expert was. You are, they told him.

At the Pentagon, Ruppelt found the Air Force brass deeply concerned about one particular aspect of the sightings: What should they tell the press?

Nobody had any idea what -- if anything -- had been in the air over Washington on July 19, but the newspapers were demanding answers. Reporters, Ruppelt wrote, "were now beginning to put on a squeeze by threatening to call congressmen -- and nothing chills blood faster in the military."

Ruppelt volunteered to stay overnight to interview the controllers at National and Andrews, then report what he learned to the press. But Ruppelt got entangled in the thicket of military bureaucracy. He called the Pentagon's transportation section to get a car so he could travel to the various airports. Only colonels and generals can get cars, he was told. He called two generals, but it was after 4 p.m. and they were gone for the day.

He went to the finance office to get permission to rent a car. Take a bus, the woman there told him. It takes a lot of buses to go from the Pentagon to National to Andrews, he replied. Take a cab, she said, and pay for it out of your per diem. But his per diem was $9, he said, and he had to pay for food and lodging.

The woman then informed Ruppelt that his orders were to fly back to Ohio that night, and unless he got those orders amended, he'd technically be AWOL. He asked to talk to her boss. He'd left at 4:30 to avoid traffic, she said, and now it was 5 and she was leaving, too.

Ruppelt gave up. "I decided that if flying saucers were buzzing Pennsylvania Avenue, I couldn't care less," he wrote. "I caught the next airliner to Dayton."
 

A Return Engagement

About 10 o'clock Saturday night, July 26, Ruppelt was at home in Dayton when a reporter called to say that UFOs were back in the sky over Washington.

What, the reporter asked, did the Air Force plan to do about it? "I have no idea what the Air Force is doing," Ruppelt replied. "In all probability, it's doing nothing."

He hung up, then called the Pentagon and learned that he was right: The Air Force was doing nothing. He made more calls, dispatching two officers -- Maj. Dewey Fournet and Lt. John Holcomb, a radar expert -- to National's control tower to see what was happening.

Fournet and Holcomb arrived to find National's controllers tracking a dozen unexplained blips. An Air Force B-25 happened to be passing through the area, so the controllers asked it to check out some of the radar targets. The B-25 went to one site and spotted nothing except a tourist boat cruising the Potomac.

Perhaps, the controllers surmised, a temperature inversion -- a layer of hot air between two layers of colder air in the sky -- had bent the radar beam, causing it to mistake objects on the ground for things in the air. Temperature inversions were common in Washington on hot days, and the controllers were familiar with the phenomenon.

But Fournet and Holcomb were convinced that some of the radar blips were solid metal objects, not inversion-induced mirages. Radar operators at Andrews saw them, too. And civilian planes flying into Washington reported seeing strange glowing objects in places where the radar was getting blips.

The controllers called for interceptors, and about 11 p.m. the Air Force dispatched F-94s to search the sky over Washington. When the first jets arrived, the blips disappeared from National's radar screens and the F-94 pilots saw nothing unusual. But when they returned to New Castle, the blips returned to the radar screens.
 

About 1:30 a.m., the jets soared back over Washington. This time, pilots saw several strange lights. One pilot gave chase but he couldn't catch the streaking light.

"I tried to make contact with the bogies below 1,000 feet," pilot William Patterson told investigators. "I was at my maximum speed but . . . I ceased chasing them because I saw no chance of overtaking them."
 

Trading on Hot Air

On Monday morning, the story of UFOs outrunning fighter planes was splashed across front pages all over America. In Iowa, the headline in the Cedar Rapids Gazette read like something out of a sci-fi flick: "SAUCERS SWARM OVER CAPITAL."

"We have no evidence they are flying saucers," an unidentified Air Force source told reporters. "Conversely we have no evidence they are not flying saucers. We don't know what they are."

In the absence of hard information, the Washington Daily News printed a roundup of rumors. The "most persistent rumor" was that the saucers were American aircraft secretly produced by Boeing "at some remote site." An "absolutely weird" rumor was that the saucers were alien aircraft that had crashed and then been repaired and flown by the Air Force.

That Monday, the Air Force tried to reassure the nation by promising to keep jet fighters poised to chase the saucers at a moment's notice. But that statement didn't