Project,Blue,Book,and,the,Luke education Project Blue Book and the Luke AFB UFO Sighting

Some forms of parent involvement with the school such as communications with school, volunteering, attending school events and parent--parent connections appeared to have little effect on student achievement, especially in high school. Helpi Translation jobs are undertaken by professional translators who are well versed with at least two languages.Translation can work at two levels: inter-state or regional language translation and inter-national or foreign language translation.

Whether you believe in them or not, there have been too many sightings of UFOs, Unidentified Flying Objects, Flying Saucers, or however you refer to them, to be totally ignored. This curious article was extracted from "Project Blue Book", written by "EJR" former chief of the Air Force's project for investigating reports of UFOs.The incident took place at Luke AFB, Arizona, the Air Force's advanced fighter-bomber school that is named after the famous "balloon buster" of World War I, Lieu¬tenant Frank Luke, Jr. It was a sighting that produced some very inter¬esting photographs.The sky was clear except for a few high cirrus clouds, late morning of March 3, 1953, when the pilot took off from Luke Air Base in an F-84 jet, to add some more hours to his flight log. He had been flying F-51s in Korea and had recently started to check out in the jets. After take off, clearing the traffic pattern, he climbed toward Blythe Radio, situated about 130 miles west of Luke.He'd climbed for several minutes and had just picked up the coded letters BLH that identified Blythe Radio when he looked up through the corner glass in the front part of his canopyhigh at about two o'clock he saw what he thought was an airplane angling across his course from left to right leaving a long, thin vapor trail. He glanced down at his altimeter and saw that he was at 23,000 feet. The object that was leaving the vapor trail must really be high, he remembered thinking, because he couldn't see any airplane at the head of it.He altered his course a few degrees to the right so that he could follow the trail and increased his rate of climb. It soon became clear to the pilot that he was gaining on the source of the vapor trail, as he was right under the middle of it. But he still couldn't see any object. This was odd, he thought, because vapor trails don't just happen; something has to leave them.His altimeter had ticked off another 12,000 feet and he was now at 35,000. Still climbing, the F-84 began to mush; it was as high as it would go. The pilot dropped down 1,000 feet and continued onnow he was below the front of the trail, but still no airplane. This bothered him too.Nothing in 1953 flew over 55,000 feet except a few experimental airplanes like the D-558 or those of the "X" series, and they don't stray far from Edwards AFB in California.He couldn't be more than 15,000 feet from the front of the trail, and you can recognize any kind of an airplane 15,000 feet away in the clear air of the sub stratosphere.He looked and he looked and he looked. He rocked the F-84 back and forth thinking maybe he had a flaw in the plexiglass of the canopy that was blinking out the airplane, but still no airplane. Whatever it was, it was darn high or darn small. The object was traveling at approximately 300 miles an hour, as it was necessary to reduce engine power and "S" to stay under it.He was beginning to get low on fuel about this time so he hauled up the nose of the jet, took about 30 feet of gun camera film, and started down. When he landed and told his story, the film was quickly processed and rushed to the projection room. It showed a weird, thin, forked vapor trailbut no airplane.Lieutenant Olsson and Airman Futch (veterans of the UFO campaign of 1952) worked the report over thor¬oughly. Confirmation from the photo lab proved this was definitely a vapor trail, rather than a freak cloud formation. But Air Force Flight Service said, "No other airplanes in the area," and so did Air Defense Command, because minutes after the F-84 pilot broke off contact, the "object" had passed into an ADIZAir Defense Identification Zoneand radar had shown nothing.There was one last possibility: an astronomer said that the photos looked exactly like a meteor's smoke trail. But there was one hitch: the pilot was positive that the head of the vapor trail was moving at about 300 miles an hour. He was unsure how many miles had been covered, but on first picking up Blythe Radio, whilst flying on Green 5 airway, he was approximately 30 miles west of his Air Base. When the pilot had disengaged from the chase, a further radio bearing confirmed his position as almost up to Needles Radio, 70 miles north of Blythe. He could see a lake, Lake Mojave, in the distance.Could a high-altitude jet-stream wind have been blowing the smoke cloud? Futch checked thisno. The winds above 20,000 feet were the usual westerlies and the jet stream was far to the north.Several months later I talked to a captain who had been at Luke when this sighting occurred. He knew the F-84 pilot and he'd heard him tell his story in great detail. I won't say that he was a confirmed believer, but he was interested. "I never thought much about these reports before," he said, "but I know this guy well. He's not nuts. What do you think he saw?"I don't know what he saw. Maybe he didn't travel as far as he thought he did. Maybe, it could have been the smoke trail from a meteor that he saw. But if he did know that he'd covered some 80 miles during the chase, I'd say that he saw a UFOa real one. And I find it hard to believe that pilots don't know what they're doing.