In May of 2018 Montana became part of the World wide project to detect UFO activity by scientific means. I installed a Multiple Anomaly Detection & Automated Recording (MADAR)-III data probe at my home in Helena, MT. (See photo below.)
I also installed a Geiger counter at my home in Helena, MT which continuously monitors gamma rays, x-rays and beta rays. The Geiger counter continuously loads data to a website and data are stored for several weeks. Elevated radiation readings have been noted in the vicinity of UFO activity. Readers can view a live map of radiation readings at the following link:
http://www.gmcmap.com/ (The stations take awhile to load on the map.)
I also have four security cameras which continuously monitor a portion of the sky in about 75% of the directions.
The MADAR unit measures magnetic flux in units of milligaus, magnetic declination and barometric pressure. UFO’s have been known to generate magnetic anomalies and can even cause power outages and vehicles to turn off. If a significant deviation in magnetic and/or pressure readings occur, the unit generates an alert. At the time we pore over UFO reports to see if any occurred in the area. The threshold for alerts is set by the team who manage the units at NICAP (National Committee for Investigation of Aerial Phenomena). The units have been used since the 1960’s and have been gradually improved.
A detailed description of the MADAR data probe follows.
First of all, unlike RADAR, MADAR doesn’t send out a signal that bounces off UFOs. MADAR is an intricate device that looks for and reports on anomalistic variations in the geomagnetic field measured in milligaus, unusual variations in magnetic compass heading, and perturbations in ambient barometric pressure. The device looks at the data 15x’s a second and reports a full dataline beginning with the MADAR “Node Number” (device ID#), “Status”, then the data mentioned above, followed by the date/time in UTC once every 60 seconds. “Status” is the normal mode or “armed” mode, and “Alert” is self-explanatory. When a variation occurs in the 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, for up to five minutes, 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 datalines. If an alert occurs a 5 min disturbance would have about 300 lines of data.
Range of MADAR is determined by the UAP, possibly what it is doing and why, and the “limits” on the device are set by the operator. Let me make it clear that the “limits” setting isn’t a “sensitivity” setting, since the sensitivity is always there. The threshold of the mGa setting is based on the local “noise level”. If the device triggers too often, the “cry wold syndrome” sets in and the operator is unable to discriminate between a real anomaly and a local natural or man made disturbance. The operator uses an E-M meter or or an AM radio tuned to the far left of the band to check on E-M noise levels in the selected room. If all else fails, the default settings for limits must be increased slightly until the device reports anomalies only a few times a month or less. Even then, the alleged anomaly must meet certain criteria before it is reported to NUFORC as a potential anomaly.
How do 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 by applied power, c) directional (propulsion) or a directed beam (stalking phase in an abduction attempt?).
Users can access the MADAR map for the U.S. at the following link:
The Montana MADAR unit is in my home in Helena, MT and has a node id of 128.