Monthly NMS Report

http://www.nicap.org/match/Correlations/1-NMS/2022-Sep-DataReport.htm

The preliminary NMS is compiled for each month by the MADAR UFO Officer, Jeremy Haslam, and is then submitted to MOC for processing. The NMS lists a total of 30 potential sightings of interest from the National UFO Reporting Center.

The time of each sighting must be specific because time is of the essence in correlation cases. So a reported time of 9:30 pm is considered general as compared to 9:41 pm which shows specificity and therefore should be more accurate. For the record, though, a domed disc with landing struts on a highway and reported as occurring at 9:30 pm would certainly be used. A sighting must also be of potential interest. Lights, orbs, many black triangles are usually excluded. Technically interesting cases or other sightings with anomalistic motion are acceptable.

MADAR incidents are basically of two types. Code blues are more rare and when the MADARs go on alert the data rate increases from one line per minute to 60 lines per minute. A data case or SCRAM is much more frequent in occurrence and is a situation where a MADAR is not triggered (magnetometer doesn't reach or exceed the threshold) but the readings are still potentially interesting at the one-minute rate. To be more precise, a Specific Column Reading And Measurements is where there is a noticeable spike in the magnetometer reading (col. 4) and with an MSV (multi-sensor verification) from the onboard compass heading (col. 3). However, sometimes a compass heading change can be of interest, based on the documented evidence of 150-plus compass cases and UAP reports over the early MADAR years and even prior.

In 30 of the cases selected, there were no code blues which are full-scale alerts. Of the total 153 operational nodes 52 are DAS equipped, which means they have audible alarm systems.

There were 30 data or SCRAM incidents. Data suggests that there was electronic evidence of a correlation, a MADAR/visual so-to-speak.

MUFON or one of our Case Certification Officers are currently investigating 7 cases. Two are actually from the September group. One is from May, another from July and 3 are pending and left over from August.

So, MOC then obtains the latitude and longitude for the sighting location, which must be rather specific in order to do any correlation studies. The coords are then punched into the MADAR setup page using one of the 500-series tracer nodes so that the registration dot on the MADAR Map can show the nearest MADAR site. Keep in mind, the nearest site sometimes turns out to be in an adjacent state. If the location is not prohibitive MOC goes to the next step.

Once we know the time zone of the area, the specific date and sighting time is converted to UTC or Universal Time Code. This is what the MADAR data is based on, UTC then documents every single line of each MADAR node's spreadsheets. Going back to the sighting date and punching in the particular MADAR site node we then pull up the sighting date/time line and place it in the center of the monitor so we can see what happened before, during, and after a witness reported his sighting.

Once we have that kind of data, the MADAR Operations Director sends a Contact Information Request to NUFORC's Technical Director, Christian Stepien to see if the witness had given permission or contact information at the time of filing. Once that is obtained, the case file is forwarded to Project MATCH investigators.

The status of each case, along with sortable data, can be viewed at any time and is updated every Saturday morning at

http://www.nicap.org/match/analyses/INVESTIGATION_STATUS.htm

Finally, the report narrative and MADAR data are then placed in the annual chronological report
http://www.nicap.org/match/Annual-Project-MATCH_Reports/
for the press, researchers, or any other party interested in the MADAR Project under Project MATCH.

MADAR Operations Director

Fran Ridge