20180930, updated 20210126When a MADAR-III DataProbe detects an anomaly it creates a dataline called an AlertStart on the server's spreadsheet. Prior to this the data is coming in at one line per minute, giving the Node (ID) number, magnetic compass heading, E-M reading in milligaus, the barometric pressure and the Universal Time Code. This is the ambient or background data. When the alert begins, the data rate jumps to once per SECOND until the alert is over.
One of the things most of my colleagues and I agree on is that most UAP reports are Insufficient Data cases and that genuine UAP reports are rare. Many of us are also convinced that when genuine events do occur, there is a reason. Just as sure as there is a reason for every aircraft flight over any place at any time over any part of the world. Several colleagues have even documented cause and effect relationships over a period of decades, even the last century. And one scientist even pointed out that we should take advantage of the fact that many times events occur on consecutive days. The activities of the UAP may at times appear to be simple flybys, but these craft are coming from one place and going to another and for some specific reason. At other times a more complex mission may be taking place. Call it what you want, alien or ultra-human behavior may mimic human activities at times.
On Nov. 14, 2004; 100 mi out in the Pacific from San Diego, a major sighting event took place. UAP had "dogged" the aircraft carrier Nimitz and a guided missile cruiser, the U.S.S. Princeton, for two weeks, FA-18's had been dispatched. The full report is available in the 2004 chrono. (See link). Many different types of events took place over those two weeks over a wide area. There was at least one distant night sighting where a radar-verified target was observed through large ship binoculars, at least one closer encounter that involved radar and FA-18 Hornets and a gun camera video(s). These events were real and not simple isolated UAP sightings. This was an operation and involved "somebody" scrutinizing an aircraft carrier, a guided missile cruiser, an atomic submarine and two destroyers. The question as to what we were doing to provoke this series of incidents could be the subject of another paper, but below is one example of how and why an outside source might interfere if threatened by some action by others.
In early August of 1990, Sadam Hussein, in a surprise invasion, took Kuwait. But earlier that year Iraq had accused Kuwait of stealing Iraqi petroleum by slant drilling, although some Iraqi sources indicated Hussein's decision to attack was made a few months before. Our activities in the region had been routine. Then U-2 spy planes were flying part of Operation Southern Watch and were patrolling "no-fly" zones over Iraqi. There had been routine carrier activity in the Gulf, etc. This soon went from routine to intense surveillance to a buildup of a major naval task force and many mobile air bases and supply ships (carriers) were soon all over the Gulf. Before it was over, it was a full-blown war, using all types of hardware, jet fighters, bombers, helicopter flights, guided missile frigates and Cruise Missiles. This was a major operation. This scenario is very probably manifested in the activities of UAP, where someone else has been watching US in a very determined and serious manner at least since WWII.
Probes or drones, unmanned craft, manned vehicles and mother ships (some with satellite objects) all have a purpose if this phenomenon is real. Close encounters and isolated cases only tell us that some UAP are real, but unless we can study all of the available incidents, we have a picture with many of puzzle pieces missing. For scientific reasons, demonstrating UAP reality must continue but after a century of activity we need to consider the reason or purpose behind the phenomenon. In order to do this we need a way of illuminating or betraying the presence of real UAP that has been unusable all these years.
First, we consider that when genuine UAP are observed, there must be a reason or purpose for its presence. It could be a mission involving a lone craft, but it could also be a mission involving a number of vehicles, over a wider area and over a period of days or even weeks. We must consider this possibility.
Up until now many distant object sightings, daylight or nighttime events, had to be set aside in favor of better evidence. Most of the data in both systems was unusable. We have been using a select few instances of good close encounters, but the bulk of the data had to be ignored. MUFON puts out a top 12 or top 20 list every year, for example. This is very useful for scientists and other researchers studying the best data, but we now have a way to use ALL of the data, tabulated by the National UFO Reporting Center (NUFORC) and the Mutual UFO Network. Introducing MADAR we now have a new way of betraying the presence of some UAP. After years of research and testing we have a growing system of MADAR Nodes located at various places in the United States and several foreign countries. The data from those devices will now be compared to sighting activity
1977, A SURPRISING CORRELATION IN TIME AND SPACE
After a lull in sightings and MADAR events, in July and August of 1977 there were 7 MADAR anomalies at my only site, Mt. Vernon, Indiana. On July 12th at 2:10 AM MADAR had gone to alert status and police reported UFOs in southern Illinois (Mt. Vernon, IL, 60 mi W) and Mayfield, KY (85 mi to the SW). But the big shocker was yet to come. On August 15, MADAR had a major event, and background radiation doubled at the very same time that Ohio State University's SETI antenna, 350 miles to the NE, picked up the famous "WOW"Signal!
MADAR-III & THE NEW SYSTEM
Each Monday I provide an updated MADAR "hit list" to the entire MADAR Team, which includes the site operators, the Project MATCH Supervisor (Rob Swiatek), and the MATCH UFO Officer (Jeremy Haslam). We use these anomaly dates and locations to attempt correlations with sighting printouts, using the National UFO Reporting Center and the MUFON Case Management System. All of the anomalies, and any sightings listed on the MUFON CMS of relevance are then listed on the NUFORC printout. Using a yellow high-lighter the MADAR lines are marked so that sightings prior to or after can be seen very quickly.
Potential sightings of interest are then flagged for investigation or more intense scrutiny. Of utmost importance is to make sure the date, times and locations are accurate and the reported details are correct. Sightings may vary in time and space where verified objects in bordering states can be seen within hours and over a hundred miles away. The key is for the sightings to be declared as representative of the real phenomena. And since MADAR does not hallucinate, this is tantamount to having two valuable pieces of data in the form of a potential correlation. And as this paper is entitled, "Betraying Their Presence", even distant objects that are exhibiting anomalistic motion can be flagged for this study.
This new system, along with cooperation from NUFORC and MUFON, went into operation in May of 2018, and the Project MATCH codename was announced at the MUFON Symposium in July of that year. MUFON's Director of Investigations at that time, Chase Kloetzke, briefed state directors on new alliance.
Monthly reports are provided to our list of over a hundred MADAR members, and if the significance of any report is high enough, it is forwarded to the NICAP list and the NICAP A-Team, then listed on the NICAP chrono by year.
The Project MATCH folder can be found on the MUFON, NICAP & NUFORC web sites and looks like this:
In addition, an article on Project MATCH was released in the MUFON Journal in November, and a monthly installment of MADAR Updates ensued until August of 2020 where the update was switched over to the MUFON web site
Anyone interested in direct participation in either Project MADAR is certainly welcome. Please contact me at:
Information on MADAR and how to order the MADAR-III DataProbe can be found at: