25 Oct 2020Fran Ridge
Once we eliminate the false alarms and other problematic codes, and then the Multi Sensor Verification * filter is applied to the balance of anomalies, we are left with processed data, which still represent "uncorrelated targets". The anomalies that didn't pass the MSV muster remain in the system. Nothing is deleted and can be used for any future experiment or study. Once we have a verified or qualitative potential sighting of interest that aligns itself in time and space with an anomaly on file, then we have a potential or actual correlation.
When an operator has an obvious false alarm, he/she files a report to MADAR OPERATIONS in the form of short email. In the email the op sometimes pastes a copy of the one-line alert that they received right after the alert, but the important thing is we are advised that somebody accidentally set off their device at a certain time on a certain day. That email is put in the "blue folder". Every Sunday I get a report from Eric Calkins referred to as the MADAR Weekly Alerts. An example of what this contains is Oct 19th which showed 102 hits prior to that date. Only 14 of those hits passed the test. Eighty-eight we're disqualified for the following reasons;
1) Any site that had 3 or more hits that week has a device set to low on threshold. One unit had 35 hits!
2) Any site that has an average Ambient above 1,000 is also disqualified.
3) Any anomaly in the field column that does not have at least a 3 degree deviation in compass heading (*MSV)
4) Any anomaly occurring at UTC "10:25".
The remaining 14 hits are then presented to the entire MADAR Team later that day or the next (monday or tuesday). A copy is sent to the MATCH Team ASAP so that they can check those anomalies (which have been converted to local time) against the CMS (MUFON Case Management System). On Wednesdays I punch those entries into the NUFORC database. It is my job to check the NUFORC data once the MADAR is integrated in the printout. So I'm basically a week behind on that procedure, which is no real issue. (BTW, any report we find of significance in the CMS I send a synopsis to NUFORC for chronological inclusion in the printout, even if it had no obvious MADAR correlation).
If the MATCH Team finds a correlation in the CMS while doing a weekly search, this needs to be reported to us ASAP, as it would be important to get MUFON to investigate right away. Most of the CMS listings are reported events but not investigated by actual field investigators. The same goes with potential sightings of interest with MADAR correlations on the NUFORC printouts. Peter Davenport may have contact information for MUFON follow-up.
If the MATCH Team finds a good case while routinely looking at any particular CMS file they can convert the local time to UTC and enter that case date in the Sighting Search Tool, along with the state, anbd it will show what MADAR nodes had anomalies. Further data can then be accessed, so we should be advised of this.
WHAT ARE DUTIES FOR OPS AND THE MATCH TEAM?
1) Ops operate and maintain their MADAR nodes, and if possible, on alert should go out and look and try to obtain additional scientific data.
2) The MATCH Team takes the weekly list of processed hits and checks them against the MUFON CMS.
WHAT SHOULD THE MATCH TEAM LOOK FOR?
1) Orbs and lights only if they correlate precisely in date, time, and location. These could be "probes" or alien "drones".
2) Closer encounters with structured objects within two days if not over a hundred miles, even if in an adjoining state. We have hundreds, if not thousands, of UFOs over a two-day period. The Nimitz encounters were scattered over a two week period and many miles.
3) Better safe than sorry, report anything that seems potentially important.
If you haven't read the Foul Eagle case, see the MUFON UFO Jourmal, Nov and Dec 2020, or go to
Portion of "sorted" MATCH Database
Information on MADAR and how to order the MADAR-III DataProbe can be found at: