Multiple Anomaly Detection  &  Automated Recording
Address:      MADAR,  618 Davis Drive,  Mt. Vernon, Indiana  47620
Telephone:  (812) 838-3120                      Email: skyking42@gmx.com
Director:     Francis L. Ridge

MADAR-III DataProbe

               
  
                                                                                        MADAR-III DataProbe                    

       

Data Archives
MADAR-I
1970-1992
MADAR-II
2014-2016

MADAR-III
2017




MADAR Screen

Updated 19 June 2017

PURPOSE & SCOPE
A network of devices that are known to be very sensitive and reliable for the betrayal of the presence of some Unidentified Aerial Phenomena.

WHO IS BEHIND MADAR?
The beginnings of the MADAR Project began with Fran Ridge in 1960 but the idea for MADAR-III came about in April of 2016.  Work on the new Project began in September.


MADAR-III
The idea to build a newer, smaller, and deployable system came about in early 2016. Others had been working on such an idea but were having technical issues. By April of 2016  Fran Ridge had put out a status report to the MADAR Team mentioning a system that was already being used extensively in the U. S. and other parts of the world for radiation that could be devised and used to log and store geomagnetic and electromagnetic information. Data could be stored in a database and displayed on a Map.  Within months a working model was created and about a dozen devices were online.

WHAT WILL MADAR-III DO?
A small and affordable sensor system and processor will be in place at many locations in the U.S. and Canada, and soon in other parts of the world. These devices transmit data to a dedicated server and without the need for a computer, although a pc offers many advantages. The primary purpose of the MADAR-III DataProbe is to detect a change in the local geomagnetic field and display live readings on a Map or "MADAR Screen" and also listed with other devices by State on a "data screen" known as the "MADAR Full Data Block".

A beginning threshold (referred to as "limits") set by the electronics engineers that can then be adjusted by the operator based on the local geomagnetic field signature, determines the sensitivity or when the system will be triggered.


Utilizing the latest electronic technology:
  1. The device will read and store 24/7 the actual compass deflections, detect a change in the ambient reading, and activate the system. On the MADAR Screen the device icon goes into a "red" alert status.

  2. The device also displays 24/7 and records the ambient and anomalous readings of the geomagnetic field in milligaus.

  3. The sensor module will also display and record ambient and anomalistic BMP or Barometric Pressure. (This feature when available will be in the automatic software updates).

  4. All data is stored both on the device's hard drive and time-stamped in UTC (Universal Time Code).

  5. If desired, at the instrumentation site, a modified device can activate a mode control panel (MCP) or power strip which powers up other devices, all depending on the level chosen by the operator. (All models may soon have this feature built in).

  6. Upon alert status the device sends out a text message AND email to the designated operator who has filled out an application upon startup, which can be modified at any time by said operator.

  7. The device could trigger a wireless audio alarm located anywhere on the site. (Not yet available).  Plans are to have this little item plug into an outlet for power and transmission.

  8. If the station is equipped with a geiger counter, the readings are logged on a recorder activated by the MCP or could be a plug-in to the device and network. (Latter not yet available).

  9. If the station has a police and/or aircraft scanner in operation, a recorder can record the transmissions upon activation of the MCP.

  10. Upon alert, the operator takes a special kit to a nearby observation point. *

  11. If the operator is away from the location the text message and TM alert will at least notify him of an event and file a basic report memo.


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 several sources for the latest sightings to use as support data and leads for further investigation:
  1. The National UFO Reporting Center in Seattle, Washington

  2. Mutual UFO Network

  3. UFO Stalker


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.


BASE UNITS
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.

FIELD UNITS
Field Units (and possibly “mobile” units) would 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 Base Unit.

SAMPLE RATES
The sensor looks at the data 15 times a second but logs data routinely at 60 sec intervals until activated by an anomaly. Upon detection the device goes into alert mode and begins recording data at a higher rate of 500 millisecond for 30 minutes or longer.

WHAT CAN BE GATHERED

  1. Detection - There are at least 151 documented incidents of compass needle/UFO incidents (Herr/Ridge). The module we selected has several sensors built in and is well-suited for this operation and gives baseline and anomalistic readings of azimuth.

  2. Data – The module also provides baseline and anomalistic EME data in milligaus.

  3. Event Time is provided with a Universal Time Code stamp.

  4. Duration is automatically provided.

  5. BMP - Baseline and anomalistic Barometric Pressure measurements would be valuable IF any correlations were noted. Up until now there has been little precedent since the witness(es) in past events have little if any notification being possible. But recent data searches have turned up numerous potential BMP correlations.


NEEDS IN THE SYSTEM

  1. Device need to be a simple plug and play.

  2. All devices and models need to have the same and constantly updated software.

  3. Software updates need to be automatic.

  4. Access to the device and readings should be primarily by website server AND local computer.

  5. A MAP displaying the locations and device status available to anyone.

  6. A DATA page or MADAR Full Data Block showing all device data in single lines listed by State order: State, City, Device # ("Node Number"), readings, Universal Time Code.

  7. Text files of data for each sampling device



MADAR Full Data Block

A lot of information can be displayed on the DATA page which (in our case) would be listed by State and by “Node” number rather than '1,2,3” As an example in which Node numbers are assigned as devices are created, Indiana could have three devices numbered 1,22,33, etc.


Missile Sites


The map above illustrates the locations of some very important sightings, the ones near missile sites. Hopefully these will be the key locations of many MADAR-III devices.


SUGGESTED SKYWATCH OR RAPID DEPLOYMENT KIT

Binoculars
Cell phone and important numbers to call
Flashlight
Strobe Light (for signalling UAP)
Compass
K-II type meter
Voice Recorder
Video or body camera
Polarized sun glasses (for observation of possible "Faraday rings")
Notepad and Pens

MADAR NET CONTROL CENTER
Attn: Francis L. Ridge
618 Davis Drive
Mt. Vernon, IN 47620
(812) 838-3120
skyking42@gmx.com
franridge42@gmail.com