UFO Intelligence Summary
Date: Tuesday, 6 June 2014, updated 3 July 2017
From: fran ridge <firstname.lastname@example.org>
Distribution: MADAR, CE, A-Team
||20140606 / 1925 hours
||0 hours 28 minutes CUT
||Mt. Vernon, Indiana
||2 mins 11 secs, and marked I/F
at 0h 45m CUT
||Reading masked by I/F
|FLIGHT CQ DATA
||Excellent. See report below.|
|LE CQ DATA
||Excellent. See report below.|
REPORT AS FOLLOWS:
MORNING DAILY DATALOG
0606 083020 13h33m CUT 3.12 5743 0.03 to 0.04 uT NoRAD (EV out)
MADAR triggered at approximately 1925 hours (0 hours 28 mins CUT), followed by a loud crashing sound. Radio interference on WWV carrier and compass movement on Cam 4 during event
Prior to this event the operator had pondered the possibility of E-M interference from the standby RADPANEL (V-700 geiger counter and relays when activated) and had moved the panel to the right and the computer monitor to the center, leaving the pc on the left. Knowing that this might have slightly changed the E-M signature in the control room the operator reset the sensor and left the room. He had just closed the door and passed by the audio alarm box when the system was activated. He was able to hear the sensor moving and turned off the audio alarm and re-entered the control room, then realized that the manual VHS upstairs needed to be set to REC ASAP and proceeded there. This took less than a minute. At the same time he hit the REC button the sound of a "crashing shelf" startled him. His wife was also upstairs and asked him if he was OK and he said, "yes", then proceeded downstairs back to the control room to hit the TES1392 datalogger record button. The 1392 was allowed it to record for 30 minutes and the VHS for the usual 2 hours. The TLC2100 time/lapse unit routinely was operating 24/7, so all 4 "cameras" were on the Quad, creating valuable data even before the event took place. After 1 hr the operator reset the equipment and replaced the datatapes. VHS was allowed to run an additional hour for the full 2 hrs and was shut down and replaced at around 2130. At 7:42 pm Camera 4 showed DCS-800 electronic fluxgate compass movement at same time of WWV carrier interference. (See also tape analysis below for detailed report) At end of event the magnetic compass on Cam 3 was still off north by a few degrees and was reset. The physical evidence from the loud crash that had been heard that had sounded like a shelf collapsed, never materialized!
Figure 1. Quad view at 7:42 PM showing spike of 0.12 uT with TES1392 meter on Cam 2
VIDEO CLIP showing I/F and fluxgate compass movement on Cam 4
254 MM MAGNET VARIOMETER
Magnetic Sensor Recording on EMREC TERS Unit
The TERS unit recorded data for 45 minutes. Audacity graph showed 2m11s heavy radio-verified disturbance and an undeterminable number of sensor pulses, followed by the system's normal "fast beep" sound.
Fig. 2. Edited version of recording of sensor movement. First half is the interference/disturbance that blocks all the sensor pulses.
TES 1392 E-M METER
Datalogger EPROM printout had 966 datapoints with 2 sec sample rate. The event started out with 14 spikes from .06 to .12 uT. Nineteen minutes into the event, beginning with sample 572, the readings, which had normally been .03 to .04 uT jumped to .06 to .07. On Fig. 1 above (Camera 2) you can see a hidden spike of 0.12 uT at the instant the disturbance began again with interference on the WWV carrier AND the marked movement on Cam 4's Fluxgate Magnetometer.
Fig 3. TES1392 EPROM printout
All 966 datapoints
FLUXGATE MAGNETOMETER, DCS 800
TLC2100 Time Lapse recorder and VHS recordings showed strong interference on the 10 MhZ WWV carrier frequency at 7:42:22 PM. VHS had audio feeds from WWV and aircraft, and WWV carrier was disturbed.along with marked movement of needle.
V-700 GEIGER COUNTER
Data fed to RAD recorder and data after the 2m11s disturbance was flawed by an audio connectivity issue. No count could be determined. The V-700 was subsequently replaced with the Model 4 so this problem has been solved.
ARTC not contacted.
TEAC W518R Left Channel - Flight data from AC scanner - Perfectly clear after the 2m11s disturbance. Audacity showed no unusual transmissions from aircraft during the event.
TEAC W518R Right Channel - Law Enforcement data from police scanner - Perfectly clear after 2m11s disturbance. No conspicuous transmissions.
SEE ATTACHED FLYOBRYT PRINTOUT
LIST OF PROCEDURES
6.6.2014Copy VHS to DVD
Label & replace SENSOR tape
Label & replace RAD tape
Label & replace dual cassette (AIRC & LE)
Label & replace VHS tape
Label & replace TLC2100 datatape
Dload EPROM TES1392 to thumb/make printout
All datatapes transferred to digital and analyzed.
VHS(CD) recording studied.
TLC2100 datatape reviewed.
From: David ESP <email@example.com>
Date: Sun, 8 Jun 2014 14:33:17 +0100
There was solar-caused geomagnetic activity late (UTC) on 6 and 7 June. From http://www.solarham.net/magnetogram.htm
Solar particles would also have trashed shortwave (ionospheric reflection) propagation.
Seems from http://www.swpc.noaa.gov/ that there was a Coronal Mass Ejection (CME) on the 4th June. Particles travel a lot slower than light, hence can typically take a day or two to reach here.
Solar and geomagnetic data
A massive formation on the sun made of super-hot magnetic plasma erupted this week in an explosive solar storm captured on video by NASA spacecraft.
The huge plasma tendril, known as a solar filament erupted on Wednesday (June 4), blowing part of itself out into space in what astronomers call a coronal mass ejection, or CME. NASA's powerful Solar Observatory recorded video of the solar filament eruption while the Solar and Heliospheric Observatory tracked the subsequent CME.
Astronomer Tony Phillips of Spaceweather.com, a website that tracks solar flare events, wrote in a post Thursday (June 5) that amateur and astronomers had watched the filament for more than a week to see how it would meet its end.
(Astronomer Tony Phillips) Phillips added that the solar eruption was not aimed directly at Earth, but could deal a "glancing blow" to the planet's magnetic field on Saturday (June 7), possibly amplifying northern lights displays. This was the day AFTER MADAR 27.
Sensor pulse recording (Fig. 2). A short, preliminary digital recording was made in lieu of a full transfer. The preliminary results show a major disturbance which lasted approximately 2 mins and 11 secs.
Inventory of VHS/DVR Recording
Sensor off several degrees
Start REC datalogger at 19:22:50
Noise level drops off at 19:23:41
Time fix at 19:25:20 = 0h28m CUT
Notable deviation with I/F of 800 electronic compass at 0h45m02sec CUT (19:42:22)
I/F only spurt at 19:51:00
I/F spurt 19:52:35
TES1392 EPROM off at approx 19:38 on cam 1
SIGHTINGS OF UAP IN REGION
MUFON Case Management & National UFO Reporting Center sources checked this late date of July 3, 2017. With 784 calls ("reports") in the U.S. in June of 2014, there was no conspicuous activity by UAP reported on this date or even close for Illinois, Indiana or Kentucky.
Massive RF/EM disturbance of undetermined origin that lasted 2 minutes and 11 seconds. Nineteen minutes into the event there was marked interference on aircraft and police frequency carriers in the 108-200 MHz range. At 19:42:22 Quad Time there was marked interference in the carrier frequencies at the same time as jerky deviations with the DCS-800 fluxgate compass were noted on the VHS recording. (See video clip). WWV is monitored at 10.0 MHz. A time fix for the latter event was established as 19:44:19 as 0h47m CUT. The entire MADAR-27 event began with automatic activation of the MADAR system.
The sky was overcast and still daylight.
We're inclined to believe that this event was connected to the Mass Coronal Ejection but the projected times of interference don't easily match. And certainly there was no noticeable or compelling connection with reports of UAP.
END OF REPORT