By Fran Ridge


Last month we touched on Day Two, our normal Tuesdays here at MADAR HQ. On Wednesdays (Day Three), two types of data are submitted to Peter Davenport at NUFORC: 1) The latest anomalies by date, time, location and node number; 2) Any potential sightings of interest (PSOI) from the MUFON CMS. By Wednesday, if there are no false alert notifications reported by MADAR Ops, the reports are submitted to NUFORC  in Seattle. By the weekend, Peter Davenport punches this information into his database so we can compare the new data the following Tuesdays. By highlighting the MADAR anomalies one can look above and below and see if an potential correlations can be observed.

MADAR now has 60 devices, with eight in foreign countries. The latest being two in Swittzerland, both of these sites to be operated by researcher Roger Spinner. Thirty-three MADAR-III's utilize the new I-board which is a major upgrade and a number of "A" models are being either returned for upgrade or their SD Card replaced.

Last month I mentioned we had gained our third Florida site at North Port, operated by Chris Goodman, but the Node number (Node 147) was not available at the time.

Node 148 is up and running at Northbrook, Illinois operated by Tim Aines. There is a special web page for Illinois at
showing the regional coverage of MADAR at this time. You'll note the four sites in the S. Illinois and SW Indiana array, three of which have been upgraded. We're getting ready for a busy summer.

The "A" Model as a datalogger has been very successful but the white paper required us to have an alert capability in the form of a beeper, buzzer or siren so that ops could go out and observe, take additional equipment, record extra data onsite such as background radiation, communications from police, sheriff, state police, and aircraft. The I-board ("B" Model) made this possible, with or without an ADT panel. For those that have this feature we have a basic alert device or siren module ($20) available. When the alert sounds, the op turns off the siren but lets the MADAR gather data until the alert is over.

May 11 and July 2 had some very important potential sightings of interest involving MADAR and the data can be seen at
There are others being studied, the latest of which occurred in March of this year, but we're still working on them. I just want to make it clear that we are primarily looking for local cause and effect relationships and getting ops out observing and recording. But the data we are also looking at are potential events over time and distance that suggests UAP operations or at least two or more UAP, one triggering the MADAR; the other being scrutinized by a regional observer. In these cases it is imperative that only sightings representing the real phenomena be used.

Help support the MADAR Project by buying and wearing our MADAR cap
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 at