It is fairly easy to catch a potential sighting of interest that is aligned with a MADAR correlation. It is a little more difficult to find data in a node's spreadsheet that demonstrates interesting spikes short of trigger. A good example of this is illustrated above where there are 7 nodes. In the NUFORC printout below one can see three sightings that were reported in Washington, one of which was an interesting event on March 26th.
The immediate questions we had were, where is Battle Ground and where is the closest MADAR site in relation to the sighting location. The easiest way for us to do this was to establish the latitude and longitude of Battle Ground, punch those coords into a test node, and see where it popped up. 502 popped up in the extreme southwest corner of Washington and nowhere near any of the 7 Washington MADAR sites. However, the Portland, Oregon MADAR site was only 20 miles away!
The next thing we had to do was to convert the local time at Battle Ground to UTC (Universal Time Code). In March, Portland, Oregon was on Pacific Daylight Time and 12:00 AM is the same as 0000 (right after midnight) converted to UTC is 0700. Two minutes prior to the reported time of the sighting node 66 had a recalibration, which we believe is a good sign for the next datapoints. Four minutes prior to the "reported" time (actual time of 6:56:19 or 11:56 PM 3/25) the field readings in column 4 were as high as 9 milligauas. This indicates that the magnetometer 20 miles to the SW may have detected an anomaly about 3 minutes before the sighting or the sighting may have been closer to 11:56 pm. Since the MADAR was not in alert mode (60X's a minute) and running at status mode, the data is restricted to one-minute readings, but the compass readings in column 3 do suggest Multi Sensor Verification of at least 3 degrees.
This example of how we analyze each potential sighting of interest may have turned up another secondary correlation.
MADAR Operations Director