Load video
YouTube
YouTube might collect personal data. Privacy Policy
Tentative:220125
Jump to navigation
Jump to search
January 25 2022 was the fourth Tuesday of the month, and the first day of the NEET INTEL HFGCS EAM DAILY COMPILATION RECORDINGS PROJECT.[Note 1]
For the very first day of the NEET INTEL project, recording a few EAMs off the UTwente WebSDR is about as much as you could expect for coverage. However, multiple E6s were active on this date.
So that by coincidence, the monitoring project may have begun on the eve of a SKYMASTER Event,[Note 2][Note 3] but it would take just over another year for the project have any idea of what those might be (refer to 230201). It certainly took place on a day of heightened E6 activity, and so the very first day of the project (unknowingly) demonstrated a critical blindspot in using UTwente to monitor US military communications, and likewise would end up as another blindspot for the project.[Note 4]
E6 Activity
As noted above, multiple E6s were active;
- AE040D over the Atlantic,
- AE0416 over the Pacific,
- Both AE0418 and AE040F over the Gulf of America,
- AE041B flew from Tinker Air Force Base to fly touch-and-gos at Travis Air Force Base,
- AE0417 was present on ADSB at Travis Air Force Base, but did not appear to leave the ground.
Digital broadcasts
- A data signal can be heard on 4724 kHz in DCRP 220125B.
- A data signal can be heard on 11175 kHz in DCRP 220125C.
Notes
- ↑ For anyone perusing these articles in chronological order, the DAILY RECORDINGS COMPILATION PROJECT did not aspire to be comprehensive, so some of these earlier entries end up having to fall back on additional resources to fill in the gaps. Though it gradually improves, this status persists for most of 2022 into 2023. A near-comprehensive monitoring effort won't be introduced until 230621, by way of the NEET INTEL DAILY TIMECARD PROJECT.
- ↑ A SKYMASTER Event may have taken place on or around either 220126 or 220202. (To take a look at those dates of their own accord: what traffic was captured on 220126 doesn't seem terribly "SKYMASTER-y", and it's possible there's no documented monitoring for 220202.) There was also likely to have been a SKYMASTER event only a week or two earlier; i.e. possibly either 220105 or 220112. So it obliviously started off in the vicinity of major exercises.
- ↑ If you take a look at traffic across 220129, 220130, and 220131, some of the activity looks "SKYMASTER-y", providing another possibility in the immediate time period.
- ↑ This would be exacerbated by referring to eam.watch community for advice on the matter...