INFORMATION SERIES

 
SUCCESSIVE NODE PENETRATION 
ARRAYS

25 June 2020; updated 24 Aug 2024 This paper deals with what Level-II operators can do. This is not to complicate or discourage Level-I operations. To be honest, about 70% of our operators are Level-I.   SUCCESSIVE NODE PENETRATION One of the very first things considered when MADAR-III was released in 2018 was the idea to track UAP as they moved over the MADAR Map from one node area to another. The first thing we did was have the light-blue registration dot change to red when an alert occurred. And if the box at the top of the MADAR Map was checked, a siren could be heard. But with all the start-up things that had to be done and early lessons to be learned, the feature wasn't taken advantage of by the ops. Common sense, science fiction, NASA history, and even Project Blue Book documents of actual sightings, told  us that even if UAPs did not originate from outer space, one of best and fastest and safest ways to navigate the earth was to enter vertically, moved laterally to a point of interest, then leave in a vertical ascent. Maybe a specific craft used this method. All we know is the evidence was there. But another method, possible used by a different craft (or the same craft under different circumstances) could just move from one place to another as if it were transported. We're new kids on the block, so we just had to open our shields as low as possible without having excessive false alarms, and see what showed up, when, and why. When an informant told us about what had happened at Operation Foal Eagle in South Korea in the summer of 2020, one concept about how UAPs entered and exited a region was confirmed. It also gave us insight as to what occurred AFTER a UAP entered our regional airspace. But more important than that, it explained the strange readings we had been getting from our magnetometer on our MADAR dataProbes. But this short paper deals with what to do with this knowledge. There are two ways to deal with sightings where UAPs penetrate an area populated with MADAR nodes. One is the conventional way of node ops comparing notes and data as part of a rapid response team. Then there is a possible new way of tracking UAP by using FR24 methods to create a loop from the MADAR Map. This paper we'll discuss the first option, what we can do now. I originally drafted this idea in 2020 but this is an updated version. Nearby MADAR sites, especially a group of nodes, should compare notes on code blues and data cases. This is not a new idea and I have always recommended it. It is up to the ops. We just lower the TH for them, assuming and hoping the local environs are the same or close to same. * Ops should strive to have their dataProbes online 24/7. * Ops should be at Level-II No one knows what the best settings are for certain types of UAP. We are in year 7 of the MADAR-III program and Project MATCH, and we are learning as we go. Nodes should run on a shield or threshold as low as possible, then observe what types of UAPs are documented to be involved. Of course both levels of operations should require TH levels be set at the lowest value. One of the tools that I feel could help tremendously is the night vision equipment now available at affordable prices. Our first documented correlation occurred at Fishers, Indiana in 2019, and it was a night vision case. ARRAYS There are different types of arrays: Circular, horizontal, vertical, or irregular. They are something you don't just plan or build. Ops set up MADARs and they begin to form into one or the other over time. New York now has 20 sites. You simply take advantage of the volunteer effort. When operators do their best to maintain their node status and stay online, and operate on the lowest threshold possible, you can't ask for more in a Level-I operation. And it is a bonus to have an op interested enough to take it to Level-II, add a DAS and geiger counter, have additional equipment at the ready, and have the ability to move outside during an alert, either with or without other team members.   Recently, while working on our new software I came upon an idea that might help ops AND tech support. When we have new software that is at a test stage almost ready to deploy, I suggest that interested nodes in these arrays purchase an additional unit (at a special low price) and have them scanning along with their normal units. Another suggestion would be to have everyone in a loop receive a cell phone SMS alert at the same time. Each node would the same phone numbers of the others in the loop. I'm not sure we can do this, but it would be similar to a yellow alert.. MADAR-III has 170 plus sites and 30% are DAS equipped. Many sites are in various stages of operation. Most are in the United States but we are starting to see some clustering of nodes in a lot of places. Successive Node Penetration could be of great scientific value to the MADAR program. Anyone interested in participation in either Project MADAR or Project t MATCH is  certainly welcome. Please contact me at: Fran Ridge MADAR Operations Director skyking42@gmx.com madar.site/