|
INFORMATION SERIES |
202410025 This paper will surprise you because a lot of Ops think that if they don't have a "code blue" there is something wrong with their MADAR dataProbe. When the dataProbe is set up correctly and running properly you can have a DAS (Detection Alarm Signal) or just alert emails, cell phone SMS alerts, or all of the above. If a genuine UAP passes over or near your site and is producing enough E-M it will leave data on your spreadsheet no matter where you have your shield or threshold set. If you're set at 30 milligaus and the UAP is pumping out 30 or more the alarm will sound. Again, the UAP has to be producing an E-M disturbance at the right distance. That's not as bad as it sounds. Operators should read the paper Most of the time UAPs idle down and cruise around slowly doing whatever it is their mission calls for. But when they come in to our airspace vertically or leave the region the same way, they produce a lot of E-M, and we believe that's where MADAR comes in. If you are a Level I op you may not want to do any more than be alerted to a UAP near you and run out and look. If you're at Walmart and an alert comes in on your cell phone, you might just want to know what you missed. In any case the incident is documented in an email. Most ops want a DAS, but if you have colleagues or friends or family within 30-50 miles who you set up as part of your array, they don't have to have a DAS. You'll be able to look at their data anytime. If you are Level II and you have additional equipment and trained team members, you'll want the DAS for sure. Your rapid deployment system will give you a better chance to witness a bonified UAP and get all kinds of other data, including night vision videos and sounds associated with the event. But when you get a magnetometer spike during a UAP event you are already a winner. An Op who says, "I haven't had a code blue" in 6 months or a year may just have his TH set too high. We can help on that, . A good example and a recent event is the Reef Station, CA incident on September 17 which involved an interesting report of a UAP shadowing a military B350 and tracked on radar at 3,000 mph. The MADAR site was 100 miles to the south and the flight was heading east. There were two MADAR sites there at Santa Barbara. One was not online. (Ops need to pay attention to that!) The other was site 57. Several minutes before the pilot encounter the MADAR site had a significant magnetometer spike of 19.12 milligaus. The threshold on the node was accidentally left at 200. Had it been set at 20 it still would not have triggered but the data would still be there. Most nodes are not set that low, so it just goes to show you that the MADAR was working. Where we DO get code blues (the LED turns blue and DAS goes off) the TH can be as high or higher than 30 if the UAP enters your regional airspace at a closer range. We can help all ops attain the lowest TH and get MADAR as close to optimum integrity as possible. I have devised a method that works in two ways. 1) To determine your best TH setting I had my tech support work on an idea I had called Peak Field value. The PF value or PFV represents the highest TH number in 14 days. It's not an average. It is a nudged value that tells us what your baseline should be. 2) By always staying 5 milligaus ahead of the PFV the entire system can operate with fewer false alarms. We would no longer have to guess what a TH should be so startup would be much quicker and more practical. Fran Ridge MADAR Operations CENTER skyking42@gmx.com (812) 490-0094 JEREMY HASLAM MADAR UFO Officer teamcamden@yahoo.com |