Showing posts with label AISS. Show all posts
Showing posts with label AISS. Show all posts

Monday, April 23, 2018

Moon Dust and the 4602nd AISS

AISS Patch/Logo
Credit: CUFON

      For years, decades really, there has been this idea that Project Moon Dust began with the creation of the 4602nd Air Intelligence Squadron (AISS) in early 1953. Ed Ruppelt, one time chief of Project Blue Book, had complained to his superiors after the massive UFO sighting wave of the summer 1952, that he needed help in the investigations. He was surprised when it was suggested, and later put into an Air Force regulation, that the investigation of UFO sightings would be accomplished by the 4602nd.

By Kevin Randle
A Different Perspective
4-16-18

If you go back and read what Ruppelt wrote, and if you look at the unit history of the 4602nd along with an examination of the Project Blue Book administrative files, you’ll see what was going on. The 4602nd was created at the time of the Korean War and during the Cold War in which military, governmental and strategic planners were worried about an aerial assault on the continental United States. This means, naturally, they worried about a Soviet bombing campaign which would see bombers shot out of the sky and Soviet airmen trying to escape and evade inside the US borders.

The thought was they needed trained teams who could search for these downed crewmen, who had lots of skills that normal service members didn’t need such as riding horses, Russian language skills, the ability to question civilians who might have seen something in the sky, and other similar skills. The 4602nd was designed with this in mind and to gain experience in interrogating civilian witnesses, they would be investigating UFO sightings. This put them in contact with untrained, sometimes uneducated, and often nervous civilians who had seen something strange. They would become experienced investigators.

Regulations written dictated this and it was, in fact, implemented. Going through the Blue Book files, there are sighting reports that were written by members of the 4602nd about their investigations of UFO sightings. There is correspondence from the commanders of the 4602nd to ATIC and other offices about UFOs. There is no dispute that this happened, and it interesting if only because it wasn’t until much later that this connection was made.

But, that does not give us the date of the beginning of Moon Dust. Others, and me among them, have suggested it and run with that idea that the 4602nd was the beginning of Moon Dust. It seemed to be a logical conclusion, but it wasn’t actually supported by the documentation.

This idea was reinforced when New Mexico Senator Jeff Bingaman, working with Cliff Stone of Roswell, requested information about Project Moon Dust from the Air Force. Lieutenant Colonel John E. Madison, of the Congressional Inquiry Division, Office of Legislative Liaison wrote, “There is no agency, nor has there ever been, at Fort Belvoir, Virginia, which would deal with UFOs or have any information about the incident in Roswell. In addition, there is no Project Moon Dust or Operation Blue Fly.”

Documentation obtained through the Freedom of Information Act, first by Robert Todd, later by Stone, and also by me, proved the statement to be untrue. I found, in the Project Blue Book files four cases that had been marked as “Moon Dust.” Clearly, the project existed.

When that documentation was presented to the Air Force, they changed their response. Colonel George M. Mattingley, Jr., wrote that they wanted to amend their response, suggesting that Moon Dust did exist. Mattingley wrote:
In 1953, during the Korean War, the Air Defense Command organized intelligence teams to deploy, recover, or exploit at the scene of downed enemy personnel, equipment, and aircraft. The unit with responsibility for maintaining these teams was located at Fort Belvoir, Virginia. As the occasion never arose to use these air defense teams, the mission was assigned to Headquarters, United States Air Force in 1957 and expanded to include the following peace-time functions: a) Unidentified Flying Objects (UFOs); b) Project MOON DUST; to recover objects and debris from space vehicles that had survived re-entry from space to earth; c) Operation BLUE FLY, to expeditiously retrieve downed Soviet Bloc equipment.
This is the earliest reference that I have found to Moon Dust. We also know that it had a UFO component based on other documents that define several terms including UFO and that there are reports in the Blue Book file that refer to Moon Dust.

Note also that Mattingley mentions that the mission was given to Headquarters, USAF in 1957, which corresponds with the launch of Sputnik, and the message issued by that Headquarters in 1957. The creation of the 4602nd, then, was not the beginning of Moon Dust.

The upshot of all this is that Moon Dust did not begin in 1953, but late in 1957. It was in operation until 1985, and contrary to Mattingley’s claim, it was deployed and was not shut down. When the name was compromised in 1985, the code name was changed. In a letter to Robert Todd, dated July 1, 1987, he was told the “nickname Project Moon Dust no longer exists.” The new name was not releasable because even the code name was classified.

In the years that followed, we have not been able to learn the new name, and we don’t know if it is still in operation today. All I can say for certain is that we know, based on other information, that the Pentagon did engage in UFO research not all that long ago and though they say that project ended, we don’t know if that is true. After all, they told us that Project Sign, the first official UFO project had ended, but the name was merely changed to Grudge. We were told that Grudge had ended, but the name was changed to Blue Book. We were told that Blue Book had ended, but we know that Project Moon Dust survived the end of Blue Book and was still in operation in 1987 when the name was changed.

What we really see here, and what we can document, is a long history of Air Force investigation of UFOs, Air Force saying one thing and doing another, and that UFO investigation continued beyond the end of Blue Book, and that other studies of UFOs have been conducted into the 21st century. What this tells us that there are many aspects of the UFO problem that have not been revealed to us and that there are still secrets being kept.

Friday, November 27, 2015

Air Force Pilot Reports UFOs Landing | UFO CHRONICLE – 1957

Bookmark and Share

AISS UFO Report of Joseph Long (A)
AISS UFO Report of Joseph Long (B)
AISS UFO Report of Joseph Long (C)- click on image(s) to enlarge -

By 1006th AISS
United States Air force
11-23-1957


See Also:

UFOs, the AISS, and Air Force Interest After Blue Book

Pilot Recalls Seeing Discs

J. Allen Hynek Reports On a UFO Landing Near Nuclear Missile Site; An Air Force 'Strike Team' was Ordered To Intercept




REPORT YOUR UFO EXPERIENCE


Monday, May 05, 2014

Car Engines Stalled by UFOs (Pt 2)


Bookmark and Share

Car Engines Stalled by UFOs

By Kevin Randle
A Different Perspective
4-26-14

     I have long been under the impression that in many UFO EM cases in which car engines stalled, the car spontaneously started when the UFO departed. I then noticed in a couple of cases that it was reported that the car was restarted, which is not the same as it just restarting up on its own. I had suggested that we might want to revisit these cases of EM effects to see what we might learn from them.

Using various sources including my files, Project Blue Book, Dick Hall’s The UFO Evidence, Mark Rodeghier’s UFO Reports Involving Vehicle Interference (because, frankly, I wasn’t all that interested in UFO interference with radio stations, TV sets, and other such manifestations of EM effects) and The Scientific Study of Unidentified Flying Objects (known as the Condon Committee), I was able to learn some interesting things.

The first reported instance of a UFO (described as a globular light) causing any sort of EM effect was on May 19, 1909. A motorcyclist said that his headlight failed as the light passed overhead. When it was gone, the motorcycle light came back on.

The first case in which an engine was stalled was from California in the spring of 1944 or 1945. According to the APRO Bulletin of Jan/Feb 1968, two school teachers were driving in the mountains when their car engine stalled. They spotted a cigar-shaped craft hanging motionless in the air. After watching it for a while, the driver turned the key to start the engine, but it wouldn’t start. When the object left, the driver tried again, but the car still would not start. After several minutes a tow truck driver stopped to help but could find no reason for the engine to quit or why it wouldn’t start when it started by itself.

The first case in which the car had to be started after the UFO disappeared was reported on September 13, 1952 from Frametown, West Virginia, which is part of the Flatwoods Monster case. A couple said they were traveling with their daughter when they saw a bright light and their car stalled. They did see a creature, which is irrelevant to us here. When the UFO took off, apparently after recovering the creature, the car could then be restarted.

From then on, it seemed that the rule was that the car, if stalled, had to be restarted. According to an analysis of the cases, it seems that in only five to six percent of the reports that involved a stalled engine did the car start without an action taken by the driver.

I will note here that there were a number of cases in which it wasn’t clear if the car had to be restarted or if it restarted on its own. In those reports, it was noted only that once the UFO was gone, the “car acted normally.” That could mean almost anything, including that the engine started spontaneously or that the driver started it.

The other thing to be noted is that I found many cases in which the radios filled with static and the headlights dimmed or faded out completely, but the engine didn’t stall. In some of them the engine began to run roughly or sputtered, but never stopped. In these reports once the UFO was gone, the engine smoothed out and the lights and the radio began to operate properly as well.

Rodeghier reported that for a long time that it was only the gasoline engines that stalled but diesel engines seemed to be immune. Rodeghier wrote, “For example, a UFO passed over two tractors in Forli, Italy, on November 14, 1954, one tractor with a diesel engine the other with an internal combustion engine. The engine of the diesel tractor continued to operate, but the other tractor’s engine stopped and could not be started until the UFO had vanished.”

The Condon Committee, without much apparent enthusiasm, attempted to study EM effects. They looked at one case that had happened while their investigation was in progress. They found discrepancies in the witness story, didn’t like that it was single witness, and found no evidence that the car had been subjected to a powerful magnetic field. They concluded that, “Because of the vagueness of the witness’ description of the ‘object,’ the wide inconsistencies in his estimates of its size and distance, the fact that no one else observed the alleged event, and the fact that the car body did not show evidence of exposure to strong magnetic fields, more detailed investigation of this event as a source of evidence related to electro-magnetic effect on automobiles did not seem warranted.”

They eventually concluded the claims of interference with engines were the most puzzling. “The claim is frequently made, sometimes in reports that are impressive because they involve multiple independent witnesses. Witnesses seem certain that the function of their cars was affected by the unidentified object, which sometimes reportedly was not seen until after the malfunction was noted. No satisfactory explanation for such effects, if indeed they occurred, is apparent.”

Or, in other words, this is truly puzzling, but we’re just not sure that such things happen. We investigated one case of a single witness, and we just don’t like it because he was unable to estimate the size and distance to the UFO with any sort of reliability. And while we know about Levelland (as noted in their index with but a single reference to it), we just don’t think these things happen and therefore we reject them.

What I learned here is that very few of the cases in which the car stalled, did the engine seem to restart spontaneously. The number of so low, that I wonder if, as has been suggested by others elsewhere, that those reports are in error. That the driver, without realizing it, did something to cause the car to restart. There seems to be no mechanical, chemical, or electrical reason for the engine to start without an action by the driver. Nearly everyone agrees with this from the scientists of the Condon Committee to mechanics and automobile engineers. Once the circuit is interrupted, the car will not start unless someone does something.

Thursday, May 01, 2014

Electromagnetic Effects, Car Engines & UFOs


Bookmark and Share

Electromagnetic Effects, Car Engines & UFOs

By Kevin Randle
A Different Perspective
4-22-14

     I was doing some work for my book, The Government UFO Files, which is a cheap way to give it a plug and I noticed that I had included a sighting from November 23, 1957 made by an Air Force officer that included electro-magnetic effects. Given the discussions from the past several days, this case becomes relevant.

According to the story told by First Lieutenant Joseph F. Long, a pilot with the 321st Fighter-Inceptor Squadron, he was near Tonopah, Nevada when his car engine stalled. He reported:
… Attempts to restart the engine were unsuccessful, and SOURCE [Long] got out of his car to investigate the trouble. Outside the car he heard a steady high-pitched whining noise which drew his attention to four (4) disc-shaped objects that were sitting on the ground about 300 – 400 yards to the right of the highway. These objects were totally unlike anything he had ever seen, and he attempted to get closer for a better look at them. He walked for several minutes until he was to within approximately fifty (50) feet from the nearest object. The objects appeared identical and about fifty (50) feet in diameter. They were disc-shaped, emitting their own source of light which caused them to blow brightly. They were equipped with a translucent dome in the center of the top which was obviously not of the same material as the rest of the craft. The entire body of the objects emitted the light, they did not seem to be dark on the underside. They were equipped with three (3) landing gears each that appeared hemispherical in shape, about two (2) feet in diameter, and some dark material. Source estimated the height of the objects from the ground level to the top of the dome to be about ten (10) to fifteen (15) feet. The objects were equipped with a ring around the outside that was darker than the rest of the craft and was apparently rotating. When SOURCE got to within fifty (50) feet of the nearest object, the hum, which had been steady the air over since he first observed the objects, increased in pitch to a degree where it almost hurt his ears, and the objects lifted off the ground. The protruding gears were retracted immediately after take-off, the objects rose about fifty (50) feet into the air and proceeded slowly (about ten mph) to the north, across the highway, contoured over some small hills about half (½) mile away, and disappeared behind those hills. As the object passed directly over SOURCE, he observed no evidence of any smoke, exhaust, trail, heat, disturbance of the ground or terrain, or any visible outlines of landing gear doors, or any other outlines or openings on the bottom. The total time of the sighting lasted about (20) minutes. After the objects disappeared, SOURCE examined the place where he had first seen them on the ground. There was no evidence that any heat had been present, or that the ground had been disturbed in any other way than several very small impressions were very shallow and bowl-shaped, triangular in pattern (in equally sided triangles). SOURCE did not measure the distances between the impressions, but estimated it to be about eight (8) to ten (10) feet. After his investigation of the impressions, SOURCE returned to his car, and the engine started immediately and ran perfectly.
This is important simply because it was another example of someone reporting that the car stalled when the UFO was near, but that Long was able to restart it when the UFO was gone. Or, in other words, it didn’t spontaneously start. Long had to turn the key.

Yes, there is much more to this story, including a rather annoying assessment by Captain G. T. Gregory who was the chief of Project Blue Book at the time. He made the normal condescending statements about the witness because Long was a member of the Air Force Reserve. All that is laid out in The Government UFO Files.

As I say, I found this interesting because the car didn’t spontaneously start when the UFO disappeared. Long had to start it… which, of course, was the point of the post about Levelland.

Saturday, October 18, 2008

UFOs, the AISS, and Air Force Interest After Blue Book

By Francis Ridge
NICAP
© 1964 - 2008

Francis Ridge     In 1963, I was living in Vincennes, Indiana. That September I was contacted by an Air Force reserve captain, the CO for the local 1127th Air Reserve Squadron, requesting a briefing concerning our NICAP team's investigations of UFOs. This briefing was scheduled to be given at the Robert Green Auditorium on the 16th of that month. I was flattered and simply thought that this interest was due to the increased UFO activity in the region, particularly the 1963 UFO concentration or "mini-flap" in southern Illinois. But it now appears there was more to it than that

My briefing covered the UFO subject in general, but highlighted the 1963 mini-flap, especially the part about Blue Book sending a special team from Dayton to investigate the S. Illinois sightings. Preliminary investigations are usually carried out by the UFO officer at a nearby Air Force base. In this case it would have been an intelligence officer from Scott Air Force Base at Belleville, Illinois, near St. Louis. However, this time Blue Book had sent a TEAM of investigators, including no less than the Project Blue Book chief, Lt. Col. Robert J. Friend.

The front page of the August 12th issue of the Wayne County Press had the photo and caption: "A TEAM OF AIR FORCE PHYSICISTS were in Fairfield over the week end checking last week's light-in-the-sky stories. Here they are reading about it all in the press...Lt. Col. Robert J. Friend (center), Capt. Hector Quintinalla, right and Sgt. Charles R. Sharp." This team TEAM had checked the Austin boy's automobile for radiation in the Wayne City Car Chase and investigated a few of the 60-70 reported incidents in the area that week.

My briefing covered the key points of the concern about serious UFO reports, including the possibility of accidental war from misinformed air defense radar men mistaking UFOs for Soviet missiles during dangerous alert periods. But many years later, researchers located a document that mentioned a mysterious government project known as Project "Moon Dust" (Just Caus report). They discovered that the retrieval of downed space objects, including UFOs, was the responsibility of a "special unit" at Fort Belvoir, NJ., the 4602d Air Intelligence Service Squadron.

Team of Air Force Physicists in S. Illinois, 1963
Team of Air Force Physicists in S. Illinois, 1963

I was aware of the 4602d's participation for two reasons: Ruppelt had mentioned it in his book and Air Force Regulation 200-2 had also mentioned it. The latter was an Intelligence regulation titled "Unidentified Flying Objects Reporting". It dealt only with UFO-related questions: "The Air Defense Command has a direct interest in the facts pertaining to UFOB's reported within the ZI and has, in the 4602d Air Intelligence Service Squadron (AISS), the capability to investigate these reports. The 4602d AISS is composed of specialists trained for field collection and investigation of matters of air intelligence interest which occur within the zone of the ZI." I had assumed, however, that the "collection" part probably always referred to just reports and sometimes items that turned out to be IFOs, and that anything else was wishful-thinking. As it turns out, there was more to it.

On January 3, 1953, the 4602d (AISS) was created by Air Defense Command regulation 24-4. The designation of the "special unit" at Fort Belvoir changed a number of times. The 4602d became the 1006th AISS in July 1957. In April 1960 it became the 1127th USAF Activities Group. That designation became important when tracking the Project Moon Dust (Kevin Randle's full report) and Operation Blue Fly documents. Project Moon Dust was set up by the U.S. Air Force to locate, recover, and deliver descended foreign space vehicles (including UFOs). Operation Blue Fly was established to facilitate expeditious delivery to the Foreign Technology Division (FTD) of Moon Dust and other items of great technical intelligence interest (once again including UFOs).

We had always suspected that Project Blue Book (the official AF UFO project) was merely a PR front, and there was evidence that some types of UFO project teams were active even after Blue Book closed down in December of 1969. But now we knew who some of these people were, and we had it from a reliable source: The Bolender Memo of 20 October 1969. Brigadier General C. H. Bolender wrote, "Moreover; reports of unidentified flying objects which could affect national security are made in accordance with JANAP 146 or Air Force Manual 55-11 , and are not part of the Blue Book system." The real responsibility for UFO reports was located in Langley, Virginia and not Dayton, Ohio. This also explained why some important case files were not found in the Blue Book archives.
Kevin Randle:
"On January 3, 1953, the 4602d Air Intelligence Service Squadron (AISS) was created by Air Defense Command regulation 24-4 in what might be considered an amazing coincidence. The Robertson Panel convened about two weeks later. They reviewed the information, suggested answers for the previously listed unidentifieds, and recommended that the myth be taken from the UFO sighting reports. They suggested that the media be used to "educate" the public about flying saucers. They believed that if they could teach the public about the nature of UFOs, then the number of sighting reports would drop off."

Captain Edward J. Ruppelt:

"The panel didn't recommend that the activities of Blue Boot be cut back, and they didn't recommend that it be dropped. They recommended that it be expanded. Too many of the reports had been made by credible observers, the report said, people who should know what they're looking at-people who think things out carefully. Data that was out of the circumstantial evidence class was badly needed. And the panel must have been at least partially convinced that an expanded effort would prove something interesting because the expansion they recommended would require a considerable sum of money. The investigative force of Project Blue Book should be quadrupled in size, they wrote, and it should be staffed by specially trained experts in the fields of electronics, meteorology, photography, physics, and other fields of science pertinent to UFO investigations."

Kevin Randle:
"Then, just after the conclusion of the Robertson Panel, Blue Book was stripped of its investigative function. Sighting reports were no longer to be sent to Blue Book and ATIC at Wright-Patterson, but to the 4602d at Fort Belvoir, Virginia. A series of new regulations and special units was created that carefully spelled out who had the responsibility for UFO investigation, and it was not Blue Book. Seven months later, on August 26, 1953, the 4602d was tasked with the official investigation of UFOs under Air Force Regulation 200-2. The regulation required that all UFO reports from inside the United States be transmitted to the 4602d before they were sent on to Project Blue....an organization other than Blue Book and ATIC (would) be alerted first in a UFO report. Then the 4602d would determine if it was to be forwarded to ATIC at Wright-Patterson Air Force Base. Primary responsibility for UFO-related reports was held at Fort Belvoir, Virginia."

Randle continues:
"Project Blue Book was nothing more than a public relations outfit designed to identify objects and to convince the public that something was being done. In November 1961 another policy was established by the air force in a document sent to various air force intelligence functions. It outlined the establishment of the "AFCIN Intelligence Team Personnel." It was more proof that the air force was interested in UFOs and that it has continued its investigation of them. There is a portion of the document deleted, but in paragraph 2, subparagraph c, it says, "In addition to staff duty assignments, intelligence team personnel have peacetime duty functions in support of such Air Force projects as Moondust, Bluefly, and UFO, and other AFCIN directed quick reaction projects which require intelligence team operational capabilities."
One of my experiences that indicated there was somebody in the government officially still in charge of UFO reports occurred in 1983. For some time now we have known that something very strange and important was going on in October and November of 1975. We have proof that there were incidents that, to quote from released documents, "prompted the implementations of a Security Option 3 at our northern tier bases since 27 October." Sightings occurred at Loring AFB, Wurtsmith AFB, and then at Malmstrom AFB. In late 1983, an informant reported to me that there had been a major incident at NORAD during that same period which prompted a Security Option 5 alert and total "lock down" at "the Mountain" which houses NORAD. And some official UFO team from the Air Force investigated that incident.

The mystery of who they were is probably solved. Although it could have been Air Force OSI agents, the informant told me that the men who interrogated his group were from "the Air Force UFO division", six years after Blue Book shut down. It was very probably some offshoot of the 4602d AISS. But back in 1963 an Air Force reserve squadron which was a descendant of the 4602d was very interested in what we in NICAP knew about UFOs. But more importantly, we found that UFO investigations continued and in direct proportion to the events which may have, or was determined to have, an effect on national security.