One of the best fighter planesthe YAK


yak-54.com keyword stats



Most current MSN search phrases:

Firefighters in World War II first
force planes
fsx addons freeware balloon
Used Ultralight Aircraft jellyfishes
peace fs2004 free downloads
sticky how much does it cost of flight sim 2002
flight  

UFO Sighting at Luke Afb?

UFOs, Unidentified Flying Objects - Flyingmoved the F-84 back and forth, convinced a
Saucers, whatever you care to call them, andflaw in the canopy's plexiglass was blanking
whether you believe in them or not, there areout the airplane, however, still none to be
too many sightings to be totally dismissed.seen. Whatever the object, it was darned
Here's an exceptional one extracted fromhigh, or darned small. The object was
"Project Blue Book", written by "EJR" formertraveling at approximately 300 miles an hour,
chief of the Air Force's project foras it was necessary to reduce engine power
investigating  UFO  reports.and  "S"  to  stay  under  it.
The incident took place at Luke AFB, Arizona,He was beginning to get low on fuel about
the Air Force's advanced fighter-bomberthis time so he hauled up the nose of the
school that is named after the famousjet, took about 30 feet of gun camera film,
"balloon buster" of World War I,and started down. When he landed and told his
Lieu¬tenant Frank Luke, Jr. It was astory, the film was quickly processed and
sighting that produced some veryrushed to the projection room. It showed a
inter¬esting  photographs.weird, thin, forked vapor trailbut no
airplane.
The sky was clear except for a few high
cirrus clouds, late morning of March 3, 1953,Lieutenant Olsson and Airman Futch (veterans
when the pilot took off from Luke Air Base inof the UFO campaign of 1952) worked the
an F-84 jet, to add some more hours to hisreport over thor¬oughly. The photo
flight log. He had been flying F-51s in Korealab confirmed that the trail was definitely a
and had recently started to check out in thevapor trail, not a freak cloud formation. But
jets. After take off, clearing the trafficAir Force Flight Service said, "No other
pattern, he climbed toward Blythe Radio,airplanes in the area," and so did Air
situated  about  130  miles  west  of  Luke.Defense Command, because minutes after the
F-84 pilot broke off contact, the "object"
He'd climbed for several minutes and had justhad passed into an ADIZAir Defense
picked up the coded letters BLH thatIdentification Zoneand radar had shown
identified Blythe Radio when he looked upnothing.
through the corner glass in the front part of
his canopyhigh at about two o'clock he sawThere was one last possibility: an astronomer
what he thought was an airplane anglingsaid that the photos looked exactly like a
across his course from left to right leavingmeteor's smoke trail. But there was one
a long, thin vapor trail. He glanced down athitch: the pilot was convinced that the speed
his altimeter and saw that he was at 23,000of the object at the head of the vapor trail
feet. The object that was leaving the vaporwas approximately 300 miles per hour. He was
trail must really be high, he rememberedunsure how many miles had been covered, but
thinking, because he couldn't see anyon first picking up Blythe Radio, whilst
airplane  at  the  head  of  it.flying on Green 5 airway, he was
approximately 30 miles west of his Air Base.
He altered his course a few degrees to theWhen the pilot had disengaged from the chase,
right so that he could follow the trail anda further radio bearing confirmed his
increased his rate of climb. Before long heposition as almost up to Needles Radio, 70
could tell that he was gaining on the object,miles north of Blythe. He could see a lake,
or whatever was leaving the vapor trail,Lake  Mojave,  in  the  distance.
because he was under the central part of it.
But he still couldn't see any object. ThisWas a high-altitude jet-stream wind the
was odd, he thought, because vapor trailsreason for the smoke cloud? Futch checked
don't just happen; something has to leavethisno. The winds above 20,000 feet were the
them.usual westerlies and the jet stream was far
to  the  north.
His altimeter had ticked off another 12,000
feet and he was now at 35,000. StillSeveral months later I talked to a captain
climbing, the F-84 began to mush; it was aswho had been at Luke when this sighting
high as it would go. The pilot dropped downoccurred. He knew the F-84 pilot, whose
1,000 feet and continued oneven when he wasreport he had heard in minute detail. Maybe
below the front of the trail, however, stillnot a confirmed believer, however, certainly
no sight of an airplane. This bothered himcurious. "I never thought much about these
too.reports before," he said, "but I know this
guy well. He's not nuts. What do you think he
Nothing in 1953 flew over 55,000 feet exceptsaw?"
a few experimental airplanes like the D-558
or those of the "X" series, and they don'tI don't know what he saw. Maybe he didn't
stray  far  from  Edwards  AFB in California.travel as far as he thought he did. If he
didn't, then I'd guess that he saw a meteor's
He couldn't be more than 15,000 feet from thesmoke trail. But if he did know that he'd
front of the trail, and you can recognize anycovered some 80 miles during the chase, I'd
kind of an airplane 15,000 feet away in thesay that he saw a UFOa real one. And I find
clear  air  of  the  sub  stratosphere.it hard to believe that pilots don't know
what they're doing.
He looked and he looked and he looked. He



1 A 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 65 66 67 68 69 70 71 72 73 74 75 76