|Someting To talk About series|
|What is the Range of the
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?).
Examples of either the directed beam or propulsion biproduct effect I have provided one local report. At the time MADAR headquarters was Mt. Vernon, Indiana. On Oct. 20, at 6:50 AM., there was a major sighting near Mt. Vernon, Indiana. The primary witness was a conductor on a L&N train that had an encounter with a UFO. The train crew had passed through Mt. Vernon and were headed east nearing the Lamont crossing, which is about 2-miles west of the outskirts of Evansville. When they neared Caborn (6-7 miles east of Mt. Vernon), the conductor told the rear conductors by intercom that they had seen a real bright light behind them. When they got near St. Phillips, the rear conductor reported that there was a train following them, on the same track, and the RR blocking system confirmed this. As they approached a steep hill at the Lamont Crossing, one of the diesel engine units had overheated and the train was immobilized. When the object behind the train started to back away, the blocking system showed the object retreating. The diesel unit was now restarted and the train, loaded down with coal, made it up the hill and on into Evansville.
Although this is a good sample of what may be a directed beam or propulsion effect it is not a direct correlation with MADAR. Howver, without any MADAR-type alerts all year, and right at the peak of a world-wide sighting wave, ten days later on Nov. 1, 1973, the Mt. Vernon, Indiana MADAR was triggered at 9:47 p.m. The background radiation level was 18 cpm, normal for the area.