The very powerful cell-phone sized device you have just received, connected to your router and our powerful MADAR Server, is going to be an exciting piece of equipment for the UAP researcher and will revolutionize how we study UFOs/UAP in action, even providing us a heads-up or Early Warning System so we can be ready to gather even much more handheld scientific data.

So let's get your device up and running!

1) The MADAR-III DataProbe
2) The power supply

Note: power supplies and batteries made for charging mobile devices will also work if you live in a foreign country. The voltage requirements for this device is 5.0 volts, +/- 5% or 4.75-5.25 volts. Or obtain one of these adaptors:
from Amazon or some other supplier.

For powering this device only use the power input jack or micro-mini jack just like the one on your cell phone. DO NOT USE ANY OF THE USB PORTS for powering. These are for add-on devices only.

You need to purchase an appropriate length Ethernet cable.  (According to our tech support this device works great with wifi but a lot of us desire hard wire). Pick a location in your room that will be several feet away from electronics, computers, printers, routers, phones, radios, etc. You will need an AC outlet within 5' of the device or a small extension cord and an Ethernet cable in the neighborhood of 5-6 feet long or longer. One owner ran his 25' away! You can locate a good spot by turning a transistor radio to AM and off to the end of the dial. Walk around the room and listen to what you can pick up! You will be amazed. Pick the quietest spot you can. This will help you but we have seen devices run well even in "noisy" areas.

1) Carefully place the device flat down on the floor or shelf you selected and make sure the device can't be jogged. At some point you may want to use Velcro to make a final mounting of the device. (You can always move it, but this prevents accidentally moving it). Before you connect it up, remember that the power adapter cord AND the Ethernet cable should not be yanked or moved. The slightest movement could trigger the device and put you in alert status. Even a small earthquake can do this. But the device should return to normal  "status" (or "armed") soon after an alert.

2) Connect your Ethernet cable to your router and then to the device in the Ethernet socket on the rear of the device.

3) Towards the front of the device, on the corner near where the LED lights are located, you will notice a very small cell-phone-like female jack. Note the orientation on the device case compared to the orientation of the plug on the AC adapter before you try to force it in. When you are ready to go,  plug the very small male connector into the female jack mentioned above, then plug the adapter into the nearest 110 VAC.

The easiest way to remember this is to connect up the device in any sequence but always plug in the 110 volt power adapter LAST. If for some reason you have to move the device or shut it down or reboot, always start with and end with unplugging and plugging the power adapter. This prevents a movement which would give you a false alert.

Do not move the device from here on. At this stage don't worry about orientation. You are powering up and the device is connecting to the MADAR Server.

On a computer anywhere in the world go to the

At this time disregard the user and password prompts, and scroll down to the blue and black LIVE MADAR Display. At the upper left of the screen below the word "Home" you will see the "+" and "-" buttons. Left click on the "-" until the whole world is in view.  For 60 years MADAR was a one site system, and since 1973 at one location in Mt. Vernon, Indiana. But what you are looking at in 2018 is a network of many MADAR-III DataProbes, some in foreign countries. We hope to have a hundred all over the world by the end of 2018

While we are here take note of the "Sound on" box at the upper right. Because of alerts and constant beep every 10 seconds you may want to keep this box unchecked. If you want to check on alerts, check the box for a while and pay attention to the red dots.

Right now,  zoom in with your double-left click button or "+" to the country you live in.  You can left click and drag to move the image. In the United States where we now have the bulk of the devices running you will see clusters of light blue or red dots. These dots are "Nodes" and represent  DataProbe devices.  If you are in a cluster such as the NE sector of the U.S. you may want to zoom in and take in the whole subnetwork.  The MADAR Command Center is now located at Newburgh, Indiana, but has set up three devices near it to form a subnetwork covering SW Indiana and SE Illinois.

If you have some old XP's lying around you could monitor a wide area on one screen and a small sector on another. Or you can have two windows views and toggle in and out. 

If your device is NOT in the North American continent, the easiest way to find it is to, using the "-", minimize the display to get the entire world in view, then zoom in on your area. By now you should be online and you should see a light blue dot at your geographic coordinates. This "node" dot was put there when the programmer punched in your coords the day it was bench tested. The server automatically gave you your "Node Number" and you are online!

If you left-click on any node it will give you a "pop-up" which is a snapshot view of what the device is reading out every minute.

Node ID: is the node number
Last Event: is where you are at the moment which should be "status" and really means "armed". If you in alert status the word "alert" appears.
Field (mGa): is the raw reading from the magnetometer in milligaus
Std Dev (mGa)
Pressure (Pa) is Barometric Pressure in Pascals / this will soon be changed to inHg or inches of mercury.
Location: The city and state.
Version: 1.01e is the software the node is running on.
Updated (UTC): This is the date/time code in Universal Time (UTC)

The subsequent upgrade in the s/w should reflect any additional change and hopefully will include the sensitivity setting which we refer to as "limits".

Again, the pop-up a spot check of the live data and the screen refreshes every 60 seconds.

And at this point you are probably wondering what the numbers mean and your light blue dot may turn red at any time which is alert status.

This is the real important data that will be accessed by you and others (our team) and is logged every 500 milliseconds when on Alert Status. We'll go into that in gory detail a little later.

Getting to and staying "blue" is what you want to do and where you want to be most of time. Then when an anomalie occurs, and you are on the madar.site MAP,  the device will go to "alert status" and your blue dot will turn red and you will be alerted by an audible "beep" every 10 seconds on your computer. There may be others already on alert status and your pc audio may have to be muted during those times. Use the easily accessible "Sound On" box at the upper right of your screen. We're still working on a text alert for your cell phone but right now you can rely on the email alert which provides a documented and written printout of your anomalie. Print out and save all anomalies.

If you are on alert status very often, it could be the location or your sensitivity may have to be lowered and your "limits" may have to be raised.  We try to set the limits before shipping to a higher default setting and then help you tweak the system down until you get it right. If your limits are higher than what we would recommend we may ask you to move your device to a more suitable location. But be patient. We will get you there.

When your DataProbe goes into alert status you will receive an email documenting it. If you begin getting too many alerts they are probably false alarms and your settings will have to be changed or the device moved to a better location. Our Tech Support will be monitoring your node to make sure it is an easy transition into the world of the MADAR-III.

No other emails will be sent unless you approve, but there are two lists which you should at least consider. Neither are high volume level lists.

1) MADAR OPERATORS LIST - Only the people who have the devices are on this list.
2) MADAR PROJECT LIST - Includes discussions and news notes about detection including enthusiasts who do not have a device.

Otherwise you will be on an alert list only. Send note to

The equipment that you have in and near your room will vary depending on your lifestyle. You may have a number of devices located in and around your home, but some of them may just be plugged into a router and not be in a high RF or EM source. One or more may be near computers, monitors, printers,other appliances, maybe even near LED lights which might be turned on occasionally and produce RF. The point is, the E-M or RF loop will mask the low geomagnetic field and make detection of an anomalie next to impossible. Once you determine you have an issue, you need to move your device out of that loop. If you would place a EM meter over your device it should read between zero and 1.5 milligaus. A reading showing an RF greater than that will lessen your chance of detecting a change in the earth's geomagnetic field. Setting your limits high enough to "cover" a high EM or RF loop will lesson your signal to noise ratio and your device will be blue a lot longer than others on the network. You don't want to put duck tape on a mouse trap. As mentioned earlier, a transistor radio tuned to the far end of the AM dial will tell you alot about your E-M and FR noise level. Most E-M and RF loops are relatively small in a room and a few feet can make a big difference, sometimes even inches can make a significant reduction in EM and RF noise level.

In most cases a plug in is all one needs. But as you can see from the geomagnetic lines in the map above there is more to the device than compass deviations. The device measures the earth's geomagnetic field in milligaus as well and is TRIGGERED by a deviation in the reading, which is set at a default limit in the beginning.  This means the sensitivity is magnetudes above a mere change in the direction of a compass needle, and we have 150+ cases of those on record.The best way to tweak the system is by studying other Nodes. One of the best operators we have operates Node 110 at Concord, NH. He even picks up what he claims is earthquakes and he is now head of the Earthquake Section. His Field (mGa) is 352 with a Std Dev (mGa) of 4.05.  Further experiments and analyses are in the works.

Note: Most devices need a reboot at times but we are working on new software to have most reboots as an automatic feature when we (or you) adjust your "limits" (sensitivity) or when there is a periodic software upgrade. We mention this here because reboot now involves unplugging the power supply, waiting 15-20 seconds, then re plugging. There is a power adapter that is available at Amazon which is 6' long and has an inline rocker switch. These are a lot easier to use and can be bought for under $10.


A complete world-wide network of devices that are known to be very sensitive and reliable for the betrayal of the presence of some UAP (Unidentified Aerial Phenomena) need to be online before the next sighting wave. Researchers may not get another chance.

The beginnings of the project began with Fran Ridge who organized the first NICAP subcommittee in Indiana. Officially authorized on November 17, 1960, the Vincennes, Indiana unit was a rapid deployment team composed of seven men, with four field investigators and three special advisers. One of the advisers, Lewis Blevins, had worked as a scientific consultant to the early Air Force project “Saucer” in the late forties. At his behest, Ridge constructed a compass-needle geomagnetic field detector utilizing light beams and photo cells to act as an early warning device.

The first prototype of the detection device was no more than an alarm system. The need to collect and store scientific data made it necessary to create a more elaborate device, and by 1970 a system was constructed at Vincennes, Indiana, but not put into real use while the designer sought a suitable location for it and was involved in subsequent job transfers to Villa Grove, Illinois (1971), Hillsboro, Illinois (1972) and finally, Mt. Vernon, Indiana (1973). It was 1973, before the world-wide wave hit the news, that MADAR (Multiple Anomaly Detection and Automated Recording) was born. Besides an alarm, MADAR provided recordings of other data, including background radiation, time of actuation, and duration.. After 20 years of successful operation and 26 potential anomalies, and with a decline in good UFO reports, the project was terminated in 1990.

With renewed interest and newer technology, a new project was established and went online on February 19, 2014. The MADAR Project, with over 50 years of work in the detection field and thousands of dollars invested, now utilized a magnet variometer, a mode control panel, two computers, four surveillance cameras, five monitors, a quad video multiplexer, a surveillance camera recorder,  a geiger counter and three audio recorders covering five channels. The project recorded four events.

An idea to build a newer, smaller, and deployable system came about in early 2016. By April of that year Fran Ridge had put out a status report showing how such a system would work. The MADAR-III DataProbe would log and store geomagnetic and electromagnetic information in a database and display that data on a Map. In late August such a system was being considered and experimentation began taking place. A small and affordable sensor system and processor was to be in place at many locations in the U.S. and Canada.  The primary purpose being to detect a change in the local geomagnetic field, display the ambient readings on the Map referred to as the “MADAR Screen” and store those readings in a database spreadsheet on the server. .

In the beginning, with detection being the most important part of the detection and recording concept, it was desired to monitor magnetic compass movements since there are more than a 150 documented incidents of compass needle/UFO incidents (Herr/Ridge). The chip module we selected was well-suited for this operation. However, very soon it was decided to take advantage of the magnetometer reading for detection, and then compass movements and BMP for backup data studies. It turns out that the mGa readings from the magnetometer are magnetudes more sensitive at detecting geomagnetic anomalies, even small earthquakes! The MADAR event that coincided with the famous "WOW" Signal in August of 1977 was a major disturbance, moving the magnet variometer needle 18 times in 3 minutes and 29 seconds.  MADAR-III is therefore thousands of times more capable of betraying the presence of UAP.
1) The device reads and stores on the server, 24/7, the Node Number, the actual compass deflections, the ambient readings of the local geomagnetic field in mGa, the local BMP (barometric pressure), all time-dated in UTC (Universal Time Code).
2) The device's computer looks at the data fifteen times a second and records a series of datalines with all the above information once every sixty seconds.
3) The computer detects a change in the  geomagnetic field and puts the DataProbe into alert status (Alert Start).
4) Upon Alert Status the DataProbe's onboard computer shifts into high gear, storing a full datalines every 500 milliseconds for ten minutes, after which it returns the device to normal referred to as "status" ending the printout with the words "Alert End".
5) By noting the Alert Start and Alert End one can ascertain the duration of the disturbance.

1) The operator gets an alert email message from the server which documents the alert and provides a list of the data. More on that later.
2) An upgrade in the software, which will be updated automatically, will soon provide an alert by text message to the operator's cell phone. By this means you will be alerted anywhere when an alert takes place so that you can possibly use some of your own equipment (See Early Warning Kit) to gather additional scientific data.
3) If you are on your computer and have your MADAR Screen minimized at
you can always toggle on to the LIVE MADAR Screen. If you are on alert status it will show a red dot where your blue dot use to be. Anytime a device goes into alert status on the MADAR Map the server sends out a beep every ten seconds. Unfortunately the Nodes are not separated and any Node will cause this to occur and you will need to have your "Sound on" button unchecked most of the time. This box is located at the upper right of your MADAR Screen.  When the North American Continent is quiet and the Nodes are all blue you can check this box and monitor the entire area while you work on you pc.

One modification being sought is a switching device for a MADAR-III DataProbe where a alert activates a power strip with other selected equipment such as recorders, cameras, other devices. This is for those with more aspirations involving the MADAR capabilities.
1) This device could trigger a wireless audio alarm located anywhere on the site and may become a part of every device made at some point...
2) If the station is already equipped with a stand-alone geiger counter, the readings (clicks) can be logged on a recorder activated by the MCP or may be a later plug-in to the device and network. [Note: MADAR HQ has a geiger counter that has a screen digital readout in mR/hr (milliroentgens) recorded via video and surveillance recorder. This has nothing to do with the MADAR-III DataProbe but operators who are interested may contact us at skyking42@gmx.com] 
3) If the station has a police or aircraft scanner (or both) in operation, a recorder can record the transmissions upon activation of the MCP.
In the event that a UAP sighting takes place in the region, the operator/team may be able to provide interesting data in the form of slight changes just under the triggering threshold. We already have at least three primary sources for the latest sightings to use as support data and leads for further investigation:

1)The National UFO Reporting Center in Seattle, Washington (NUFORC)
2) Mutual UFO Network
3) UFO Stalker
UFO Stalker tracks cases reported to MUFON but there are a few cases filtered to MUFON's S.A.T. Team (Special Assignment Team) that are not in the normal C.M.S System, pending investigation by the team.

The last 24 hours, or even the last 7 days of data, could be viewed in a graph if accessed by a local computer to quickly locate reading highs and lows.  This button on the Analysis Tool Dashboard (not yet completed) would make this easier than grab and paste into a spreadsheet program.

For the operation of the MADAR System it is desired that most units/devices would be utilized as Base Units. These “robot” devices would receive and gather data at all times and without the need for an on-site operator. Base units should never be moved as they are programmed to operate at specific geographic coordinates,.

Field Units (and possibly “mobile” units) could be built in the same manner but their use would be different. Such a modified device could be made to be used for Field use which would have a display of its own and a battery pack, but it could also be placed at the base location for the bulk of the time and operated as a Temporary Base Unit.

BMP or Barometric Pressure measurements before, during and after an event would be valuable IF any correlations were noted. Most UFO investigation questionnaires and interrogations by FI's failed to ask the question about BMP because this is something you don't normally witness, but the effects of BMP can be felt. It is the clues to changes in barometric pressure (dizziness, ears popping, etc.) that have opened up a new area of study.

The Map or MADAR Screen displays the locations of the devices and the sample every 60 seconds. When on alert status the dot goes to “red”.

The Full Data Block may be useful to all operators, but especially to the analyses and tech support people. With a black DOS-like background and white readout, at one glance the status of each device listed in alpha order by state resembles an ever-changing flight and arrival display at an airport. When the CUT/UTC is not correct, the device is down. And data comparisons are very easy to notice, especially in areas where the devices are grouped. A sample of what the FDB might look like is provided below.

The Full Data Block

This map shows all the missile sites located all over the United States, and would be the perfect locations for MADAR devices during these troubled times. UFO history has shown missile shutdowns and alerts during periods of high tensions.


Go to the MAP and type in your email address, then your password. Hit Login. The Log-n block should change to Logout. This means you are in.

Go to the top left and click on Node Data. Where is says Enter Node Id put in your Node number. The Display count is defaulted to 100 lines or normally 100 one-minute readings. Just for simplicity hit the Submit button.

If you had hit 1000 it would have displayed 1000 minutes or 1.7 hours of one min data lines IF......there were no alert! When your device goes into alert status it shifts to high gear and records the data at a much higher rate (120x's faster) at 500 milliseconds. So if you are checking on an alert you need to set the Display count to 10,000 that's 83 minutes, almost the same time but 120 times as many datalines.

On future software updates we'd like to add a field to this datapage AND the pop-up. We refer to the sensitivity level as "Limits". The lower the limits the higher the sensitivity. So when comparing data from different detections we would like to know your settings to see if you might not have been triggered when a UAP was observed near you or a device near you had an event and you didn't.

It would also be important to know your settings were high and you still picked up a UAP.

For those of you who know about spreadsheet programs and graphing data you can copy and paste these columns, but we are working on a simplified dashboard that will do this at a key stroke.


The idea behind UFO detection goes back many years, at least to the early 1950's with what was known as the “Cartwright UFO Detector”. What probably spurred the concept was the famous prospector case of June 24th 1947. The incident took place 5,000 feet above sea level in the Cascade mountains. Fred M. Johnson , a Portland prospector, told authorities he noticed a strange reflection in the sky and, looking up, spotted five or six discs about 30 feet in diameter. Johnson said he grabbed his telescope and watched the discs approximately 50 seconds while they banked in the sun. He described them as being round with tails, making no noise and not flying formation. Johnson said that while the discs were in sight the hand on his compass-watch weaved wildly from side to side. This report is documented by official Air Force records is also mentioned in the SECRET Project SIGN Report.

Quote from SIGN
Declassified on October 11, 1966, Appendix "C", page 22: Method II -- Direct use of Earth's Magnetic Field:

One observer (incident 68) noticed a violent motion of a hand-held compass. If we assume from this that the objects produced a magnetic field, comparable with the Earth's field; namely, 0.1 gauss, and that the observer found that the object subtended an angle 0 at his position, then the ampere-turns of the required electromagnet is given by:

ni = 30 R

where R is the range of the object. For instance, if R is 1 Kilometer and the object is 10 meters in diameter, then ni = 1 billion ampere-turns.
Now, if the object were actually only 10 meters away and were correspondingly smaller, namely, 10 cm in diameter, it would still require 10 million ampere-turns.

These figures are a little in excess of what can be conveniently done on the ground. They make it seem unlikely that the effect was actually observed.

Now, the Earth's magnetic field would react on such a magnet to produce not only a torque but also a force. This force depends not directly on the Earth's field intensity but on its irregularity or gradient. This force is obviously minute since the change in field over a distance of 10 meters (assumed diameter of the object) is scarcely measurable, moreover, the gradient is not predictable but changes due to local ore deposits. Thus, even if the effect were large enough to use, it would still be unreliable and unpredictable.

George E. VALLEY, Member Scientific Advisory Board


When the detection project was begun in 1960 there were many indications that changes or disturbances in the local geomagnetic or electromagnetic field were somehow connected with some genuine UFO activity.

1)  By 1964, NICAP had published the UFO EVIDENCE and had listed 106 cases of E-M effects. E-M Effects are those which disrupt electrical circuits, cause engine failure in automobiles, produce radio interference, etc. The NICAP site now documents over 116 EME cases.

2)  Later, in the 1970's, Eric Herr had located and listed many compass-needle cases and we now have a total of over 151 instances.

3)  Mark Rodeghier of the Center for UFO Studies compiled a report of over 441 cases of UFO Reports Involving Vehicle Interference. (1981) The study is an examination, chiefly through statistical means, of the subclass of UFO events wherein the car, truck, or other motor vehicle in which a witness was either riding or in near proximity to, was seemingly affected by the presence of a UFO.

4) Fifty-Six Aircraft Pilot Sightings Involving E-M Effects (Dr. Richard Haines, 1992)

5) Numerous documented MADAR detections with documented UFO reports from 1970-1990

6) PAYDIRT. Stunning detection by MADAR (Aug. 1977, MADAR-15 event) of an 18-pulse, 3-min 29-sec disturbance with significant background radiation increase (doubled) at the exact time of the famous “WOW” Signal picked up by SETI 310 miles to the NE.


In early 1973, as State-Section Director for MUFON, Fran Ridge made initial in-person contacts with law enforcement people and airport control tower operators, attempting to set up a reporting system. The timing was good. The 1973 wave helped to stimulate cooperation among those who didn't want to be burdened with UFO calls and/or didn't have the time or need to follow them up. To maintain the rapport, a Monthly Status Report was sent to police, sheriff, state police and control tower people in the three county area. In 1986 this monthly report became a State Report for all UFO Field Investigators and State-Section Directors in Indiana. Every opportunity to use the news media, periodically, provided the local readers and viewers with a 24-hot-line number.

Local member and non-member personnel who helped the Center identify reported UFOs spread throughout Posey County were part of SKYNET. A UFO reported in a certain area or direction facilitated a call from the Center to this "Spotter". Kits designed for UFO Investigation were described in the MUFON Field Investigator's Manual, but special kits were created at the Center and used for a "rapid deployment group". CB radios, radiation detection equipment, optical instruments, etc., were all used in this effort.

Today, anyone could and should create a similar situation, but it is not necessary for the implementation and success of the current MADAR-III concept. All one needs is a MADAR-III device plugged into their router to be an integral and important part of the system. Being alerted then would allow at least one person to attempt to ascertain further data, readings, photos.


Cell phone
Strobe Light
K-II type meter
Voice Recorder
Video or body camera
Notepad and Pens
Transister radio w/AM


Please refer all comments and/or criticisms, suggestions, to:

Attn: Francis L. Ridge
5847 River Walk Circle
Newburgh, IN 47630
(812) 490-0094