By Fran Ridge



Some of you may have noticed the lower number (2-digit) nodes. The test nodes originally were 2-digit. We are now using the numbers available from 50 on up. We have built and used 123 devices so far. When a node is moved to another state or another city in the same state, because of the history of that latitude/longitude we Z-out that device and reprogram it with a new node number.

Peter Gise is running node 52 at Los Altos, California, making 4 in CA.
 Donald Cline has node 53 at Star Valley, Arizona, making 4 in AZ. Last month I mentioned the new node in Kentucky but didn't give the op's name. Barry Gaunt, runs node 54 at Franklin. Kentucky needed this and we hope to have others in the northern and eastern portion of the state. CK Haun had a site at Boise, Idaho (116) which we renumbered and is running at Stateline, Nevada as node 160. Boise still has a node 111 so we are OK there. Jeramy Walker is running node 51 at Beulah, Michigan, making that one the second MADAR site in that state. Al Larsen is at the helm of Node 50 at Lacy, Washington, and John Shuster is running a node at Port Angeles, making 6 nodes in Washington state
Currently we are feverishly working on several projects at once. For those that want to go a step farther than just detecting anomalies and recording the data, and being alerted, we have MADAR-CAM and MAVERIC.  Fran Ridge at the MADAR Operations Center has built and is testing a 4-camera system that runs 24/7. At this point the system is manually operated, especially during alerts. Two more cam sites are being set up and operated by Eric Calkins at Whidbey Island, WA and Paul Browning at Clarksville, TN. These are high-definition RLC-511W cameras but anyone can buy them for about $100 each at Amazon. Tests conducted on April 19th showed images of the belt of Orion! We have a MADAR-CAM Team and each is working on some other similar ideas all over the world.

MAVERIC stands for MADAR Audio/Video Environment Recording Integrated Console. Paul Browning is spearheading this project and has the Lenix software almost completed. The system uses an Arduino and a dedicated computer with camera views and FlightRadar 24 running 24/7, including aircraft and law enforcement sound tracks. The console is a computer screen input form that allows the op to set parameters, such as recording time, etc. The device uses the relay contacts on the MADAR DataProbe to AUTOMATICALLY record all the data, even if the op is out of town!

* Credited "hits" are those that were obtained by the device and uploaded to the server that were not documented as a false alarm, or had no problematic data.
     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