Listings in bold are compelling
correlations
and more
information on
those
incidents can
be found by
clicking on
the 8-digit
date at
http://www.nicap.org/match/Correlations/
Line 3 - Las Vegas, NV. Only one MADAR in service, node 160 right near the California border at Stateline, but was not online that date. The Las Vegas node 126 has been offline for years.
Line 4 - Harwinton sighting shows field readings.
Line 5 - Kirkwood, CA. Four sites in the state, (52,56,57,105) but none close enough to the sighting.
Line 6 - Vista, CA. Photos, look like a blimp. In any case there are four nodes in California, none close to the sighting which took place far south of all four MADAR sites.
Line 7 - Kettering, OH. Seven sites with no obvious anomalies. The nearest two sites had no appreciable data. Node 89 had a very high Average Ambient and was for all practical purposes out of business with 1499 milligaus. 107 had no data of interest.
Line 8 - Madison, ??, no state information.
Line 9 - NE of Louisville. No nodes at Louisville until June.
Line 10 - Just north of node 165 (Pinebush) which was offline at that time.
Line 11 - Ashville, NC. 80 miles east of nearest node, Maryville, TN. No data of interest with a rough time given.
Line 12 - Dover, Delaware. No nodes in Delaware.
Line 13 - Sacramento. Nearest node 52 is 28 mi SW. Data not compelling and time is a rough estimate.
Line 14 - Battle Ground, WA. Closest node was Portland, OR, node 66 about 20 miles, field reading spikes. UI (Under Investigation by MUFON).
Line 15 - Node 56 at Littlerock is 120 miles from Palm Desert.
Line 16 - Slight variations in numbers at node 182 at Goshen but sighting value is low due to lack of details.
Line 17 - Littleton - amazing sighting and great field numbers, including accelerometer at closest node. UI (Under Investigation by MUFON)
Line 18 - Denver. The data is not as compelling for the earlier daylight sighting at Littleton.
http://www.nicap.org/match/
Line 3 - Las Vegas, NV. Only one MADAR in service, node 160 right near the California border at Stateline, but was not online that date. The Las Vegas node 126 has been offline for years.
Line 4 - Harwinton sighting shows field readings.
Line 5 - Kirkwood, CA. Four sites in the state, (52,56,57,105) but none close enough to the sighting.
Line 6 - Vista, CA. Photos, look like a blimp. In any case there are four nodes in California, none close to the sighting which took place far south of all four MADAR sites.
Line 7 - Kettering, OH. Seven sites with no obvious anomalies. The nearest two sites had no appreciable data. Node 89 had a very high Average Ambient and was for all practical purposes out of business with 1499 milligaus. 107 had no data of interest.
Line 8 - Madison, ??, no state information.
Line 9 - NE of Louisville. No nodes at Louisville until June.
Line 10 - Just north of node 165 (Pinebush) which was offline at that time.
Line 11 - Ashville, NC. 80 miles east of nearest node, Maryville, TN. No data of interest with a rough time given.
Line 12 - Dover, Delaware. No nodes in Delaware.
Line 13 - Sacramento. Nearest node 52 is 28 mi SW. Data not compelling and time is a rough estimate.
Line 14 - Battle Ground, WA. Closest node was Portland, OR, node 66 about 20 miles, field reading spikes. UI (Under Investigation by MUFON).
Line 15 - Node 56 at Littlerock is 120 miles from Palm Desert.
Line 16 - Slight variations in numbers at node 182 at Goshen but sighting value is low due to lack of details.
Line 17 - Littleton - amazing sighting and great field numbers, including accelerometer at closest node. UI (Under Investigation by MUFON)
Line 18 - Denver. The data is not as compelling for the earlier daylight sighting at Littleton.