INFORMATION SERIES
 

SETTING THE TRIPWIRE





Dated: 10 July 2019

PRIMARY GOAL
Acquisition of scientifically valuable UAP sightings with MADAR-III DataProbe technical corroboration each documented with close time and location support.

DEVIATION OR TRIGGER SETTINGS
Under the current plan the program will operate with a nominal amount of "false targets". The earlier system "threw out the baby with the bathwater." All legitamate deviation reports listed in the weekly Unevaluated MADAR Anomalies printout will be retained in the database. However, only those reports that conform to current protocols will be initially submitted to the NUFORC.


PLAN 61
A major improvement to the MADAR system operation was incorporated in both plans 60 and 61, released in April.  The earlier software for the MADAR operation released in December still used the positive and negative numbers coming off the triple-axis magnetometer, and consequently was not working properly. Plan 60 was to be the new default software and attempted to overcome those issues. Because the project was running about a month late we opted to go to Plan 61, which used any change from any one of the axes on the triple-axis magnetometer and offered the best solution, so it was quickly adopted after a 30 day test with Plan 60, getting the system in place for the projected busy summer months.

The MATCH database lists 365 "hits" since May of 2018 when MADAR-III went operational. The last two months (May and June) indicate
that the system was saturated with "hits" and it became necessary to make some "trigger" setting adjustments very quickly. It is our opinion that getting false targets with good hits is better than getting fewer hits with some valid ones lost due to "filtering" with a higher "trip wire". The majority of the nodes are now regulated and the last check showed no nodes needing change at this juncture.

There were 32 hits listed in the last week, covering the period of 7/1 through 7/8, and
all 32 will be checked for possible sighting correlations. Under the new guidelines, however, only 10 qualified for the NUFORC database. In this manner all detections of anomalies will be checked against all the available sighting databases. And any sighting found to be a potential correlation, even if only an indication of valid UAP in the region, will be sent to NUFORC if not already listed there.

One thing was obvious once more: MADAR-III DataProbes with the Q and H chip ARE NOT WORKING.  A number off issue had been found during the first year, which was the reason why the project had created its own sensor board in the first place. If an operator declines the upgrade, at some point soon the registration dot on the MADAR Site Map will come down and the device will be purged from the system.  With our actual cost of the I-board at $40 the device can upgraded, and includes a new hard drive and new enclosure. 


Fran Ridge
skyking42@gmx.com

Information on MADAR and how to order the MADAR-III DataProbe can be found at:
http://www.nicap.org/madar.htm