Monthly Update
Multiple Anomaly Detection
& Automated Recording
==========================================================
FOR IMMEDIATE RELEASE: JANUARY 2023
ISSUE
NEWEST MADAR SITES
Node 223
is operated by Chris Harmon at Green Valley, Illinois. I am
especially content with this new Illinois site as our midwest
array needs further fortification. This makes six sites for
Illinois. Kenneth Hartung runs the new site 224 at Affton,
Missouri, giving us seven sites in Missouri. The midwest array
includes Missouri, Illinois, Indiana, Ohio, Kentucky and
Tennessee. Our Indianapolis node 21, operated by Terry Tolly,
was shut down and moved 16 miles, and is now node 221 with a new
history. The MADAR Network currently operates in the United
States, Australia, Canada, France, Germany, Ireland, Japan, the
Philippines, Switzerland, and the United Kingdom. The program
has 150 sites and presently, 50, or 34% are now DAS-equipped,
which means the site teams can be alerted by an alarm system, go
out and gather more data with selected equipment. The project
has 204 members.
HOW WE DOING?
The MADAR-III program was operational by May of 2018 and Project
MATCH, the combined effort of MUFON, NUFORC and NICAP was
launched two months later in July. Since 2023 begins a new year,
it is a good time to stop and look back at what we have
accomplished so far. Right now the Case Status database shows 39
reports of correlations with UAP Twelve (12) of these were
code blue's. That means the MADARs magnetometers went into full
alert, and those with DAS alarms alerted the ops to those
alerts. Twenty-four incidents (24) were "data" situations where
the MADARs were not triggered but showed data at the time of
potential sightings of interest. Twenty-six (26) of these two
categories had MSV or multi-sensor verification, meaning the
onboard compass also showed variations.
There were (2) correlations in our first year, 2018. The next
year, 2019, had (2) as well. There were (5) correlations in 2020
and (7) in 2021. While we are still working the 2022 incidents
we are jut finishing the month of July and already have (22)
correlations! (All this began after the war broke out in
Ukraine).
Under the original Project MATCH plan (2018), it was the job of
the MADAR Project UFO Officer, Jeremy Haslam, to go over all the
NUFORC cases looking for potential correlations with sightings
and recorded MADAR anomalies. And MUFON was responsible for
submitting their potential sighting correlations. And since
NUFORC had no investigators, MUFON became the primary agency.
The sources of these 39 incidents are as follows: MADAR
researchers found nineteen (19) compelling cases of UAP in
NUFORC's database that had variations in MADAR data in nearby
site logs. MADAR Ops had a dozen incidents and either filed
their own reports or had the state MUFON group investigate
them. Five of those incidents (5) were investigated by case
certification officers. While looking for
leads the researchers ran across six (6) additional MUFON CMS
listings. MUFON investigated (3) of these. Although MUFON has
not submitted any potential sightings of interest near their own
MADAR sites, and since the protocols have been recently updated,
this may have been changed.
The good news is we are doing exceptionally well and we still
have five months of data to go over for 2022! What we need to
do, and concentrate on, is: 1) getting more Ops to
incorporate a DAS into their system and have some extra task
they can perform during an alert. The alert and task not only
gets the Op in a position to see a UAP, but could upgrade the
incident from an uncorrelated target to a madar/visual. 2)
Getting as many Ops as possible to get their nodes in order so
they CAN be of value. Many need to address issues that are
making their chances less likely to detect a UAP. 3)
Getting the MATCH protocols out to MUFON states so that they
know what their responsibilities are. The prime duty (besides
investigating assigned cases) is to provide potential sightings
of interest to check against nearby MADAR sites.
We have learned more about UAP and detection the last four years
than all the years previous. We knew many UAP appeared in pairs
and that many exited the atmosphere vertically. What we did not
know was that UAP many times enter the atmosphere vertically,
create a tremendous EM disturbance, then idle down to a point
where instruments show little or no EM. We know that in a dozen
cases the threshold of the device had been set at under 30
milligaus. The bulk of the code blues were set at under 26
milligaus. In spite of this, our default setting of 30 has
worked out very well. In fact, our very best code blue had been
set at 30. And not surprisingly, those devices equipped with a
DAS (alarm) were the game changers. What would have been
uncorrelated targets became MADAR/visuals. We also have learned
that cell phones either work and show nothing or don't work at
all. A major surprise came in the form of the "data"
cases. Twenty-four (24) devices that did not go into alert
mode because the field readings were under the threshold, WAY
under, but showed fluxuations during a nearby sighting! Most of
these were verified by multiple sensor readings. So what will we
learn in 2023? And like I said earlier, we still have 5 months
of potential sightings of interest to go over yet this year.
Fran Ridge
MADAR OPERATIONS CENTER
Newburgh, Indiana
812-490-0094
skyking42@gmx.com
https://www.amazon.com/dp/B09GZR746V