28 August 2020, updated 28 March 2022

Unlike RADAR, MADAR doesn't have a "range" nor does it send out a signal that bounces off UAPs. MADAR is an intricate device with a powerful computer that looks for and reports on anomalistic variations in the geomagnetic field measured in milligaus, unusual variations in magnetic compass heading, and perturbations in the accelerometer reading (formerly barometric pressure). When a variation occurs in the milligaus field measurement, which is controlled by a "limits" setting, the device goes into alert mode (AlertStart) and the data registration ramps up to once per second, 60 times faster than the normal rate listed on the printout as "alert". The datalines register at this alert rate until the anomaly is no longer affecting the device, plus an additional 180 seconds, and the final line is labelled "AlertEnd" at which time the rate reverts back to once per minute and is tagged as normal or "status" once again. A typical day has 1440 (status) datalines or once every minute, Therefore, if an alert occurs, a 9 sec disturbance would create 189 seconds of additional lines that day.

How far a MADAR may pick up a UAP, therefore, is determined by the UAP, not the DataProbe. The size and power output of the UAP, and what the phenomena is doing are probably the factor at work here. Consider the following UAP examples that may produce disturbances or geomagnetic anomalies:

1) Small, probe-like objects, reported throughout UFO history, that operate similar to today's "drones". One would think that the EMF from one of these would be quite small.
2) Then we have the more common-sized objects, many of which were described as "flying saucers" for half a century, about 30' in diameter. The E-M field generated to power a craft of this size is probably the same as the object that Project SIGN studied.
Large objects, possible mother ships or transports. These would seem to require either much more power and E-M or a different power source altogether.

How could UAP's affect MADAR?  UAPs either produce a field that is
a) omnidirectional with intensity varying by the inverse cube of the distance,
b) omnidirectional with intensity linked to the application of and rated to applied power,
c) directional (propulsion) or a directed beam (stalking phase in an abduction attempt?).
d) powerful enough to distort the earth's geomagnetic field in such a way as to create anomalies for many, many miles.

Any of these could represent the activity of more than one object in a small area or even a larger region!  MADAR was designed to filter out any and all natural E-M sources so that it would be looking at the normal, ambient geomagnetic field and be able to discriminate between that data and distortions of the field by UAP.
The key to analyzing and understanding any anomaly is in the data provided, which shows variation, intensity and duration.
Item "a", above, would probably best describe the source of the anomaly we would desire. Items "b" thru "d" would probably give us local alerts without visuals. In other words, "uncorrelated targets". In 1977, MADAR  detected anomalies at the Mt. Vernon, Indiana site while police were getting reports of objects being sighted up to 85 miles away and in southern Illinois and northern Kentucky. Since the visuals were NW and SE of the MADAR site, this implies multiple sightings in a region, but anything is possible. By that we infer that other UFOs were active in the region. Discoveries such as made by members of Operation Foal Eagle in 2002 in South Korea suggest that the burst of energy from a UAP entering the atmosphere or exiting the atmosphere has been documented, and that subsequently the readings are significantly reduced during an idling period. It is also possible that if an object was coming out of hyperspace or another  dimension, a great deal of energy would be expended.

The important thing to keep in mind is that UAP's can, and have, produced anomalies in the geomagnetic field at least 150 times that we have documentation for. This fact is the basis for detection of UAP, and more importantly, our ultimate goal of an Early Warning System
. This we hope will alert the operator(s) and the local team so that they can go out and observe the sky and be able to take additional equipment and gather scientific data, videos, night vision shots, etc. Everything we experience, all the anomalies we detect without verification, all the "uncorrelated targets", are necessary training missions, dress-rehearsals if you will, to qualify and tweak the system and the procedures as we prepare for that ultimate goal. The evidence suggests that many of the "uncorrelated targets" are indeed vertical maneuvers but there were no witnesses to report the observations. There seems to be no differences between the signatures of correlated and uncorrelated events once we have processed the raw hits each week and these occur at an average rate of about 6-10 times a week!

In April of 2020 we had a major breakthrough: A MADAR/visual. Two witnesses observed a UAP at close range after being alerted by a MADAR anomaly!  This tells us the system is working and that the most important thing an Op can do is to GO OUTSIDE AND LOOK! If an Op has a cellphone cam or a night vision camera it should be grabbed on the way out the door.

It gets even better. New evidence (see Operation Foal eagle) suggests UAP can be in the area a lot longer than the initial alert time. We would suggest an Op be outside on skywatch for a minimum of 10 minutes. The data suggests UAP produce very high E-M fields while slowing down prior to enter to atmosphere, trigger nearby nodes, then produce little to no detectable E-M for extended periods of time. The same thing is suspected upon departure, but could occur at a different location.

All the nodes had to be upgraded to the new I-board, so everyone has this upgrade which has the green relay contacts on the top. For those who have the opportunity to go to the next step (other than getting email notices AFTER an event) they can add other equipment to the system. Recently we updated our software so that anyone can afford and utilize the newer
DAS the system.

Level One, the detection of anomalies and finding correlations with UAP is the main thrust of the MADAR Project and Project MATCH. Level Two is where the op and his team are alerted by the DAS and take additional equipment outside. Currently we have over 30% running at that level.

Anyone interested in direct participation in either Project MADAR or Project MATCH is  certainly welcome. Please contact me at:

Fran Ridge
MADAR Director
(812) 490-0094