INFORMATION SERIES
 

TECHNICAL ANALYST SPECIALISTS
MADAR / UAP Sighting Correlations


Updated 24 October 2023


The purpose of this short paper is two-fold:
1) To list the sequence and procedures used to properly evaluate selected UAP reports.
2) To assist in the training of prospective Technical Analysis Specialists.

The first step needed in the investigation and analysis of a selected UAP report is the filter process used by the MADAR UFO OFFICER, Jeremy Haslam. It is his job to go over the monthly batch of sightings from NUFORC (National UFO Reporting Center) and select  cases worthy of follow-up. NUFORC cases are logged by Peter Davenport in Seattle, Washington, and must be investigated by outside sources..
Those reports should not only warrant the MADAR data be checked, but be of the type a scientist or dedicated researcher would want to showcase. A list of those cases by Haslam, all NMS (non-MADAR sightings at this stage) is provided to MADAR Operations on a monthly basis.

MUFON reports, on the otherhand, are usually already investigated and should be of the proper quality, and are provided by the MUFON MATCH Coordinator, Michael Panacello.

Once the analyst gets a prospective case, the latitude and longitude of the sighting area are checked to see where the nearest MADAR site is located on the MADAR MAP. *.
madar/site
The display will then show where and approximately how far the nearby nodes are.  Usually within 50 miles would be appropriate, but the value and type of the case might require some additional miles.

Now that there appears to be some possibilities, the analyst looks up the node's time zones. Keeping in mind that months probably have already passed the time zone will probably be different than the current one. 

Using the UTC Time Conversion Chart the TAS looks up the time in the 24-hour format and proper column. Nine-twenty pm being 2120 hours if the time zone were EST the UTC would then be determined to be 0220. It gets a little complicated here because as you can see the UTC is actually the DAY AFTER. So if the sighting date were October 10th, the MADAR UTC time would actually be October 11th.

I suggest everyone print out a UTC Time Conversion Chart, take a yellow highlighter and highlight all the "0000" on the left side of the page. Anything above the yellow line is the following day.

Taking the nearest node, go into the data spreadsheet for that node the date and the time, selecting 10000 records, and hit submit. Then go to the exact time and center that dataline on the page on your monitor. Then look at the magnetometer field reading first and see if there are any spikes. Then try the compass heading to see what was going on during this sighting. If one gets spikes in both columns this is a pretty good correlation. If the compass heading varies 3 degrees or more we refer to this as Multiple Sensor Verification (MSV). You want to save any single sensor spike, however.

It becomes even more interesting when you have multiple MADAR nodes showing spikes.

* There are several ways to determine the distance from sighting to node.

Fran Ridge
MADAR OPERATIONS