By Fran Ridge


      The network of MADAR DataProbes is improving and continues to grow. We have placed 111 MADAR DataProbes around the world, with 98 actually in the system and 89 running. Nine are in the process of going online. The latest additions to the network are as follows:
     Node 98 is operated by Thomas Czeizinger at Hamilton Township, New Jersey. This makes four MADAR sites in that state. Since our server tech support/op from Estes Park, Colorado (Eric Calkins) moved with his family to Washington, he has a new node number there. That device previously had a Colorado history, so Eric has the unit at Whidbey Island and we reprogrammed the unit to node number 58.  Node 61 is operated by David Gordon of Edmonds, Washington, so we now have four sites in Washington. Node 60 is operated by Michael Cimino at St. Peter, Minnesota, our first MADAR DataProbe in the state of Minnesota. Node 59 is operated by Warren Westall at Deep River, ON, Canada

Spikes and Anomalies Short of Trigger
I know we have touched on this topic where there is a sighting near a MADAR site, we can look at the data to see if there are any spikes that are under the trigger shield. This is very promising and we already have several candidates. But I am now conferring with my software team to see if we can produce a daily printout of these spikes, provided  that they exceed half of the shield value. For example, most nodes have a 30 milligaus threshold. If the field readings would exceed 15 milligaus the software would catch it and a notification would go out to my team, very similar to the Nodes Offline report and the Daily MADAR Alert. Keep in mind that readings UNDER alert threshold are scanning at one minute intervals, where alerts have a ramped-up scan rate of one line per second. This would be a tremendous help because if there were a sighting in a state that has four MADAR sites, we would have to pull up four sets of data. And even more important, this would also flag spikes in nearby states.

Analyses and PSOI (potential sightings of interest)
Since we went operational in May of 2018 we have had several interesting correlations or potential correlations. Most notable in 2018 were two events, one in May and one in July, and we are just now going over the data for August of that year, so we have some catch-up to do for the last four months of 2018, plus work on most of 2019. The last discoveries, also under analysis, are the two more recent events. One occurred on November 19, 2019 at Sandy, Georgia, and the other on December 7th at Elizabeth, Colorado.To view the files go to:

INTERCOM: A New Idea for Extending the Alert Signal
Those that have a DAS (Delayed Alarm Signal) box (to get the observer quickly outside with other equipment) can now use an intercom to extend that feature. All you have to do is hook up an intercom, place it near the DAS, and lock the send button down. Take the other intercom and turn it on and place it where you want it to be, bedroom, man cave or garage. Make sure both are on the same channel. Make sure you get an FM unit with a long range so that it isn't just a same-circuit unit. These are about $50 on Amazon and you can place them up to a mile apart, a great early warning system.

     To see MADAR "hits" and potential monthly correlations one can go to the Project MATCH site at
Check out the full MADAR site or order a MADAR-III DataProbe or MADAR cap at