 |
 |
 |
and the National UFO
Reporting Center
present the
2018 PROJECT MATCH REPORT
present the
2018 PROJECT MATCH REPORT
|
|
|
This report deals exclusively with bonified MADAR anomalies and Potential Sightings of Interest, those that we feel are representative of the UAP phenomena. There were a number of interesting sightings that either had too distant connections or had no obvious correlations-in-time to be used in this report. There were also cases that were not used because certain data couldn't be confirmed. So this is an effort to show accurate results, many times using Multi-Server Verification. This report will be subject to updating. Appropriate explanetory links are provided at the end of this summary. The current INVESTIGATION_STATUS database report showing all these cases and others can be accessed at any time. Finally, any terms used in this report you are not familiar with are explained at the end of this report. - Fran Ridge, MADAR Operations Center. Updated: 6/13/2024 May 11, 2018; Marysville, Washington At 1:44 pm CDT, on May 13, 2018, the MADAR Operations Center (MOC) at Newburgh, Indiana received an email marked "RE: FW: Alert -sighting correlation". It was from Jim klotz, the operator of MADAR site 100 at Mountlake Terrace, Washington. The somewhat urgent message stated: "I think I have a very good correlation for the most recent alarm to a report from the MUFON Case Management System." He had gotten an alert email stating "A magnetic anomaly has occurred on node: 100 Mag: 134.1, Compass: 234.1; Pressure: 29.70, Time 2018-5-12, 04:59:27 GMT " This was documented evidence from the MADAR server that an anomaly had occurred at 10:59:27 pm PDT., a full-blown "code blue". Site 100 was not yet DAS equipped so there was no audio alarm, but the alert message had gone out from the server and was received at the MADAR site at 10:00 pm on May 11th, just seconds after the alert. A couple of days later, Klotz submitted a request for any UAPs in the MUFON Case Management System, and someone had indeed filed a report on 5/13. On May 11, 2018, there had been a sighting at Marysville, Washington, about 22 miles NE of the MADAR site as the crow flies. The MUFON report stated: that on 5/11/2018, at 9:58 pm (cak) Light as bright as a normal star/satellite. Appeared and disappeared as it traveled northward." Witnesses also filed a report with NUFORC the same day as the filing with MUFON. The more detailed description stated, "We observed an object at high altitude proceed from south to north +/- traveling at a speed similar to observed satellites this object appeared to vary its course from left to right and back. Perhaps a meteor skipping off the atmosphere? There were no other lights on the object. Thought it was a satellite at first except that it appeared to vary its course left and right and would "go out" and come back on later on its generally northward trajectory. It went out at about a 35 degree azimuth to the north and did not reappear. It originally appeared at about a 20 degree azimuth to the south. It did not exhibit normal aircraft lighting characteristics." Case CMS # 91974 - Sphere - AN1 - Cat 1 .This object was a self or reflectively lit craft at high altitude (no sound) flying in a direction that could be expected from a polar orbiting satellite. The one minute (3 min?) duration eliminates any possible meteor as an explanation. Not being listed in a satellite database would suggest a possible secret satellite. However such a satellite would probably not be deliberately lit up, and would be painted a dark color so that the sun would not expose it. This object apparently exhibited anomalistic motion. It looks like a polar orbit but the tracking angle from Earth's rotation would not be that exaggerated. [Problem associated with this report: A few days after these knowledgeable witnesses filed an unsolicited online report clearly documenting 9:58 pm as the sighting time, someone changed the time to 11:22 pm. To this date, no one has explained how this could have happened. The NUFORC report retains the original entry]. . August 6, 2018; Norwich, Connecticut At 1:05 pm EDT. The witness reportedly saw, what appeared to be a helicopter, free-fall to hover over the trees about a quarter mile from his building less than 1000 feet up. It moved side to side as if troubled with control. He thought it was going to crash, then it turned sideways and the sun shone off it brightly. At this point he realized that It was not a helicopter and seemed possibly bullet shaped, and a bright chrome. It continued to attempt control then steadied itself for a few seconds before flying straight up above the clouds. He could still see it through a hole in the clouds and watched until it shot off to his right, traveling fast enough that he only observed it again because the sun struck the chrome once more, before it was out of view. 5 mins. (NUFORC). Six minutes later at 1:11 pm, and 40 miles away to the NW, the Newington MADAR site 106 had a verified anomaly. The data in 2018 was not yet calibrated but the magnetomter field increase was indicative of an actual geomagnetic change which is what triggered the MADAR. The MSV (multi sensor verification) protocol, which went into effect in June of 2020 was utilized recently in the case above, and showed a significant compass heading change during this event. Interesting case of another vertical ascent, which provides more solid ground for a bonified UAP and support of Operation Foal Eagle findings. END OF REPORT Terms and acronyms used in this report: nuforc = National UFO Reporting Center at Seattle, Washington CCO = Case Certification Officer. Used when MUFON is not available. MADAR dataprobe = official term for MADAR unit. Operation Foal Eagle |