Messages

1

Utility / Re: HFGCS General Log

« on: May 17, 2024, 2147 UTC »

Partial log of messages highly likely to have been broadcast by E4 ADFEB4 on May 17 2024;

Code: [Select]

NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
THREE NINE
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
THREE NINE
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
THREE NINE
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
THREE NINE
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
THREE NINE
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNCHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANN

//////// CUT ////////

 HANCEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE KKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
ONE NINE
FIVE SIX
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNCHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CH

//////// CUT ////////

AL ONE
CHANAL OKE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
KKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHTIEIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
SIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOVEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNKKKKKKZCZCZCZXLLXLLXLL
ZZ
BT
EIGHT EIGHT
EIGHT EIGHT
ZERO ZERO
ONE SEVEN
TWO ZERO
TWO ZERO
ALFA ALFA
ECHO ECHO
GOLF GOLF
KILO KILO
NOVEMBER NOEMBER
XRAY XRAY
ZULU ZULU
EIGHT EIGHT
EIGHT EIGHT
BT
NNN
NNN
NNNNCHANNEL ONE
CHANNEL ONE
CHANNEL ONE
CHANNEL ONE
888800171939AAEEGGKKNNXXZZ8888 [repeated at least 5 times]
888800171956AAEEGGKKNNXXZZ8888 [repeated 6 times]
888800172020AAEEGGKKNNXXZZ8888 [repeated 6 times]

Broadcast was FSK signal on 31.7 kHz (50/50). Captured using KiwiSDR in Wisconsin. [Sample recording]

(SIGINT/all, I am not sure if you consider VLF 8888 messages suited for the EAM/FDM log, this HFGCS general log, or should be in its own thread. Let me know if it does not fit here)

2

Utility / Re: HFGCS General Log

« on: May 16, 2024, 0512 UTC »

160836Z MAY 2024 11175.0 kHz USB
08:32 "ANDREWS GLOBAL, ANDREWS GLOBAL, this is V9Z. Exercising Esteem Highly Alpha. Request phone patch to J1X. Over."
08:34 "MAINSAIL, MAINSAIL, this is V9Z. Request if your station has phone patch capabilities? Over."

MUNICIPAL (NCS callsign for May 16) eventually responds; QSY is arranged to 8047 kHz.

{Was not available to change frequency to continue monitoring.}

3

Utility / Re: HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: May 07, 2024, 2028 UTC »

Daily call sign for 07 May 2024: TRANSLATE (ground NCS), (airborne CP), (other)

071303Z MAY 2024
TO: ALL STATIONS
FROM: TRANSLATE
FOR: BID LOW
6VCL6D // TI55G 4K7IZ C7M67 F7UEG 4PBO

071315Z MAY 2024
TO: ALL STATIONS
FROM: TRANSLATE
FOR: BID LOW
6VWHXZ // KPGPD FHJUG 5KKCI FCHWI KSKP

071957Z MAY 2024
TO: ALL STATIONS
FROM: TRANSLATE
FOR: BID LOW
6V64Q3 // YONZ5 GZCOP 5XXXS YMJRS NSOV

4

Utility / Re: US STRATCOM SKYMASTER Traffic Log

« on: April 28, 2024, 0005 UTC »

Some additional messages broadcast on April 18;

For SKYMASTER (CULINARY/BACHELOR/BACKBENCH);

Code: [Select]

04:05 KIVA 43 FOR SKYMASTER VO1S
04:14 TAVA 44* FOR CULINARY 6F9V
04:27 DARE 06 FOR BACHELOR 3O4W
04:29 DARE 05 FOR BACHELOR WGO9
04:35 WOOD 32 FOR BACHELOR ENEI
04:36 WOOD 32 FOR BACHELOR ENEI
04:45 WOOD 42 FOR BACHELOR A36P
04:54 WOOD 31 FOR BACKBENCH UG84
04:57 WOOD 41 FOR BACHELOR 6ARI
05:16 FEAR 32 FOR SKYMASTER DH1O
05:27 SARGE 11 FOR ? SR44
05:36 FEAR 31 FOR BACHELOR 9Y83
05:47 RICO 12 FOR ? 6XLE
06:04 KIVA 43 FOR CULINARY BVQL
06:08 KIVA 42 FOR BACHELOR FRSD
06:15 KIVA 44 FOR CULINARY VXWG
06:23 DARE 05 FOR BACHELOR NUHV
06:28 DARE 06 FOR BACHELOR T5J9
06:48 WOOD 42 FOR CULINARY PPM3
06:53 WOOD 31 FOR CULINARY FNUI
07:06 SARGE 12 FOR CULINARY 005R
07:07 WOOD 41 FOR CULINARY WIMU
07:17 FEAR 32 FOR CULINARY ASRH
07:28 SARGE 11 FOR CULINARY USBL
07:29 RIKA 12 FOR BACHELOR ????
07:37 RIKA 12 FOR BACHELOR MPSG
07:49 RIKA 11 FOR SKYMASTER Z7BQ
07:53 KIVA 41 FOR CULINARY 6BCK
07:59 KIVA 42 FOR BACHELOR 64S6
08:00 KIVA 42 FOR BACHELOR 64S6
08:04 KIVA 43 FOR CULINARY UV4H
08:15 KIVA 44 FOR BACHELOR C4I4
08:36 WOOD 32 FOR CULINARY ZI16
08:44 WOOD 42 FOR CULINARY 84V4
08:53 WOOD 31 FOR CULINARY 2QUU
08:57 WOOD 41 FOR BACHELOR W1NL
09:05 SARGE 12 FOR CULINARY 092J

* TAVA 44 originally misidentified itself as FIAT 32 to deliver message and amended itself twice.
** Suspect all KIVA/RIKA/RICO were actually PLICA – "PLICA" confirmed via phonetic spelling in contact with Gander radio; [link].
*** As observed during the January 11 event, it is almost like there are "3 SKYMASTERS" – one for the US east coast, one for the US west coast, and one for the US central region. My impression is that E6s were serving this role under callsigns BACKBENCH, BACHELOR, and CULINARY, respectively.
**** It is quite likely that some of my transcriptions have mixed up BACHELOR/BACKBENCH. Reception wildly varied per SDR and all were affected by a great deal of background noise for the duration of this event.

274 message;

Code: [Select]

04:07 CULINARY PIL UQY BIK WPD XKD TAJ

Aside; there were also 274 messages broadcast April 10 and 11. It is not obvious if those messages automatically 'connect' with the SKYMASTER traffic on April 12, but it does not seem horribly unreasonable to connect the dots there.

Additional messages;
Additional messages were broadcast under 3 character callsigns on 5074 kHz, 6778 kHz, 6807 kHz, 7594 kHz, 7703 kHz, 9883 kHz, and 10674 kHz. Many of the messages were identical to message traffic on primary HFGCS frequencies (but did not follow the typical "ALL STATIONS" format or have an addressee. The 'format'/delivery was not consistent; e.g. in at least one case, what had been broadcast as a 'standard' 30 character message on a primary HFGCS frequency was read off in groups of 3 characters to comprise a message of "3-0 characters". (There were some messages delivered using what I thought was an intentionally comic tone of voice, and others an overly slow delivery. While in at least one instance I thought I recognized the voice of an HFGCS operator, from context, this is probably unlikely.)


Unlike my previous post in this thread where I felt like it was reasonable to expect more SKYMASTER messages 'sometime in April', I feel I do not have enough information to correctly anticipate the next one. Around late August/early September I am expecting another event like this one to occur, but for May – July I am going to have to look through the past documentation of SKYMASTER events on www.radioscanner.ru to see what activity has typically been like during this time of the year. (I have seen some 'reputable' people in the SWL community incorrectly reporting there has been an increase in the frequency of these events since early 2023 – there is more than enough evidence to the contrary for those who are interested in looking for it.)

5

Utility / Re: HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: April 09, 2024, 1824 UTC »

Transcriptions of all the ALL STATIONS messages I've heard broadcast today so far (April 9 2024). At the moment don't have time to convert to the usual format/style of this thread but may find time later today.

00:44   FLY FISH
ZZZBSQ ARWGDJT33YAOGVNWGDG5IACJ

00:52   FLY FISH
Q57OCT KP4WID7ZUPTBFWYIVV35YN6C

01:08   FLY FISH
Q5FSWX SULTH5JNPUETT6I6EIYVDZCW

05:08   FLY FISH
Q5KA4E 4H4OO2B4QBTYUIESLS37IHSJ

05:11   FLY FISH
Q5OXFC W6XKXKUXDAZPOWZTWBAWDCQ4

05:13   FLY FISH
Q5N5JB JJ2CLNZBZ3FXQ7ROJICN7YXH

05:29   FLY FISH
Q5N5JB JJ2CLNZBZ3FXQ7ROJICN7YXH

05:47   FLY FISH
MESSAGE OF 164 CHARACRERS FOLLOWS
BWIWBF75NOTW72QGKXB2HC6P3NXCZ6IDLWXU7X4XK
NNNNKCWSFV5T4J4WZIAQWA
NNNN7TB6LJFFZONO2DPGFA
IIII67BLZNEYEYSPTJYV5Y
MMMMIETGHQT7L3CUOD4H6T
CCCC7OMELIVLLSXWSMQSFC
IIII5W4URXCX6

05:59   FLY FISH
Q5UC3X 3VTI7TEGQ6R4YMVEKDKO7GQY

06:03   FLY FISH
Q5N5JBJ J2CLNZBZ3FXQ7ROJICN7YXH
MORE TO FOLLOW, STAND BY
Q5OXFC W6XKXKUXDAZPOWZTWBAWDCQ4

12:25   FLY FISH
FOR TONAL, FOR CARO
ZZ2BK2 U2EZM3TDWM7PBXEUZ2Y5FOCW

12:44   FLY FISH
FOR TONAL, FOR CARO
ZZE5F4 YZEARQGVF75HPJIVQESCN6TK

14:09   FLY FISH
ZZ72BS EJ4IFTUSUREQLNXBWYWJCNX5

15:15   FLY FISH
Q56YRR IDBSBKF4ZRC42PQVUETUACQR

17:29   FLY FISH
FOR TONAL, FOR CARO
ZZRZW3 6KNRWCCWVFDPNDNWA5VG63UW

17:38   FLY FISH
ZZNWC7 AYBAZF7HRCVIBSEPWKDMDIXU

18:33   FLY FISH
Q5ZSOT GVNMNC6YKK2Q6Y5RDCQZME3B

There have also been a number of STANDING BY FOR TRAFFICs during the day, I don't usually log these. There was one STANDING BY which I found peculiar because it was disregarded, while the ones a half hour prior and half an hour after were not. (Off memory, this was the ~16:00 STANDING BY.)

6

Utility / Re: HFGCS General Log

« on: March 31, 2024, 0042 UTC »

302312Z MAR 2024 11175.0 kHz USB
23:12 KANSAS 68 requests radio check from MAINSAIL; no answer.
23:13 KANSAS 68 requests radio check from MAINSAIL. From MAINSAIL; "please say again."
23:13 KANSAS 68 has MAINSAIL weak and unreadable. MAINSAIL has KANSAS 68 loud and distorted. KANSAS 68 requests current message traffic.
23:14 MAINSAIL; "[...] at this time."
23:15 KANSAS 68 does not understand what MAINSAIL just said, asks to confirm if they said no messages at this time?
23:15 MAINSAIL; "[message traffic is none at this time?]"
23:15 KANSAS 68 asks MAINSAIL which station they are calling from; MAINSAIL indicates they are broadcasting from Puerto Rico at this time.

7

Utility / Re: HFGCS General Log

« on: March 29, 2024, 2050 UTC »

291820Z MAR 2024 15016.0 kHz USB
18:20 BATHROOM attempts to contact CANDLEWAX. (A few more attempts over the next ~30 minutes ensue.)

291849Z MAR 2024 15016.0 kHz USB
18:49 CANDLEWAX finally answers, has BATHROOM readable but weak. From BATHROOM; "I have you the same. Will try again in a little bit."

291907Z MAR 2024 11175.0 kHz USB
19:07 YUMA[?] MAINTENANCE requests radio check from MAINSAIL; no answer heard on my end.


291913Z MAR 2024 13907.0 kHz USB
At some point, I heard BATHROOM "copy" CANDLEWAX, without confirming what, exactly, was copied. After some searching, finally find CANDLEWAX and BATHROOM have moved to 13907 kHz. They remain on the frequency until about 19:48. At some point they also use 9031 kHz for voice traffic, when voice traffic on 9031 kHz is accompanied by RTTY signals on 13907 kHz. Communications end because CANDLEWAX is landing soon. (My impression is that whatever it is that they were attempting to do, it was not particularly successful.)

8

Utility / Re: HFGCS General Log

« on: March 17, 2024, 0552 UTC »

Phone patch very similar to the one I logged on March 13; could not hear the individual calling at any point in the conversation (despite trying myriad SDRs), and the exact same number was requested.

2024 MAR 17 11175.0 kHz
04:53 ELMENDORF requests for 2SE to QSY to 11056 kHz.

(Time gap here is my fault, did not immediately change freq.)

2024 MAR 17 11056.0 kHz
04:58 ELMENDORF copies 757 836 ----.^{[note 1]}
04:59 ELMENDORF requests 2SE stand by for phone patch.
05:02 ELMENDORF advises 2SE that ground party is on the line. (Afterwards, can only faintly hear a voice, but too weak to make anything out.)
05:03 ELMENDORF; "2SE, 2SE."
05:04 ELMENDORF; "Please stand by at this time. Re-initiating phone patch."
05:13 ELMENDORF; "We are having issues with phone patch software. Do you wish us to relay information to uh... phone patch recipient?"
05:14 ELMENDORF; "We are having software issues at the moment. Do you wish us to relay any information to the phone patch recipient?"

Note: Like last time, this seems to have simply concluded. While waiting to hear if there was any follow up, subsequent traffic occurred which seems to line up with the use of 11056 kHz as a discrete[?] HFGCS frequency. (It has previously been documented as such, but by whom and when this was, not sure.)



2024 MAR 17 11056.0 kHz
05:18 ?; "JOHN BULL, JOHN BULL, this is DRAGON 22 with a radio check. How copy? Over."
05:19 ?; "MAINSAIL, MAINSAIL [...] how copy? Over."
05:35 MAINSAIL with a test count. (Twice.)
05:39 JOHN BULL with a test count.
05:39 JOHN BULL with a test count.


^{[note 1]} Last four digits omitted. Per personal record, the number was identical to the second requested during the March 13 phone patch log. A cursory web search finds it in logs of phone patches as far back as 2013 {1} {2}.

9

Utility / Re: HFGCS General Log

« on: March 13, 2024, 2116 UTC »

I tried several SDRs and was unable to hear 4HA.

132038Z MARCH 2024 11175.0 kHz
c.20:38 4HA requests phone patch from MAINSAIL. MAINSAIL asks 4HA to QSY to 11159.0 kHz.

132040Z MARCH 2024 11159.0 kHz
20:41 MAINSAIL; "Ready to copy DSN or commercial number, over."
20:41 MAINSAIL; "I copy figures 312 836 ----.*^{[note 1], [note 2]}
20:44 MAINSAIL; "Be advised ground party is on the line at this time.."
20:45 MAINSAIL; "Be advised ground party has disconnected."
20:45 MAINSAIL; "Ground party has disconnected at this time."
20:46 MAINSAIL; "Ground party has disconnected. I say again, disconnected at this time."
20:46 MAINSAIL; "Do you have another number to contact, or do you require any further assistance?"
20:47 MAINSAIL; "Ready to copy commercial phone number."
20:47 MAINSAIL; "I copy figures 757 836 ----".^{[note 3]}
20:49 MAINSAIL; "Be advised ground party is on the line."
20:50 GROUND PARTY; "4HA, roger. Esteem Highly Alpha."
20:51 GROUND PARTY; "4HA, this is 1YG. Roger. Esteem Highly Alpha."
20:51 GROUND PARTY; "4HA, this is 1YG. Roger. Esteem Highly Alpha. [My cell?] 2051, over."

Did not hear anything afterward. Stayed tune to 11159 kHz until 21:15.



^{[note 1]} Seems to be commercial number, I have omitted last 4 digits. I can remove more digits if out of line with forum policy or decorum.
^{[note 2]} Voice in background could be heard reading a portion of message beginning TDQ6VO. (See EAM/FDM Log.)
^{[note 3]} Again, digits have been omitted. If this number was a DSN, appeared to correspond to numbers associated with Naval Support Activity Hampton Roads.

10

Utility / HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: March 13, 2024, 1928 UTC »

Daily call sign for 13 March 2024: MUSCULAR (ground NCS), CONFRONT, DOC LUCKY, OVERLORD (airborne CP), (other)

131452Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
TDMY4G // PTCQN TFCK7 OZA35 2JJ4V WGEE

131459Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
TD3GFP // EDZPV 4ZA7D O5VDB WOTS3 ZUN4

131502Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
TD3GFP // EDZPV 4ZA7D O5VDB WOTS3 ZUN4
THIS IS MUSCULAR, MORE TO FOLLOW, STANDBY

131504Z MAR 2024
TDMY4G // PTCQN TFCK7 OZA35 2JJ4V WGEE

131646Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
FOR: MALCOLM
MGXCDT // VDLWM YBJDI I3KIG DUC3X I4RA

131732Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
FOR: MALCOLM
MG64IP // 4FYSO 5WZIN VIQKG EABAU BKQV

131758Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
FOR: SWIRL 73
MGQ4SP // N3SZO OI6UW LNSZV IM5BC EO35

131816Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
FOR: MALCOLM
MGL6CS // T47JY XQDDN DTSC2 46LZX IZ47

131828Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
TDJDXT // ZMXE7 IYYTH J2TSN 2OIXC Q7AU

131850Z MAR 2024
TO: ALL STATIONS
FROM: CONFRONT
TDJDXT // ZMXE7 IYYTH J2TSN 2OIXC Q7AU

131920Z MAR 2024
TO: ALL STATIONS
FROM: CONFRONT
TDJDXT // ZMXE7 IYYTH J2TSN 2OIXC Q7AU

131950Z MAR 2024
TO: ALL STATIONS
FROM: CONFRONT
TDJDXT // ZMXE7 IYYTH J2TSN 2OIXC Q7AU

131828Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
8888
DISREGARD THIS MESSAGE, THIS IS MUSCULAR OUT.

Note: There were 8888 messages broadcast March 13 of 2019, and March 12 of 2023. If we feel comfortable assuming there were 8888 messages broadcast March 2020, 2021, and/or 2022 (but not captured or transcribed by anyone), are these routine?

132020Z MAR 2024
TO: ALL STATIONS
FROM: CONFRONT
TDJDXT // ZMXE7 IYYTH J2TSN 2OIXC Q7AU

132020Z MAR 2024
TO: ALL STATIONS
FROM: MUSCULAR
TDQ6VO // SG2QA ZHARC B6GFS HKLYR ZQIW

Note: This message could be heard being read off in the background during a phone patch request. (See General Log.)

132130Z MAR 2024
TO: ALL STATIONS
FROM: DOC LUCKY
TDQ6VO // SG2QA ZHARC B6GFS HKLYR ZQIW

132200Z MAR 2024
TO: ALL STATIONS
FROM: DOC LUCKY
TDQ6VO // SG2QA ZHARC B6GFS HKLYR ZQIW

132210Z MAR 2024
TO: ALL STATIONS
FROM: OVERLORD
TDQ6VO // SG2QA ZHARC B6GFS HKLYR ZQIW

Note: Transmission had awful metal squelching sound overtop throughout transmission. I suspect this is coming from E6 AE041C, which I've previously pointed to as a possible source of transmissions with this noise.

132230Z MAR 2024
TO: ALL STATIONS
FROM: DOC LUCKY
TDQ6VO // SG2QA ZHARC B6GFS HKLYR ZQIW

Note: Transmission quality poor on 11175 kHz; bandpass exceeded 3 kHz filter and had a tinny noise. No such issue with its simulcast on 8992 kHz.

11

Utility / Re: HFGCS General Log

« on: March 11, 2024, 1745 UTC »

Transcribed from this livestream^{[note 1]};

111621Z MAR 2024 11175.0 kHz USB
16:21 ROMAN LAD requests radio check from NEON LAMP; I didn't hear response.
16:23Z NEON LAMP requests radio check from ROMAN LAD; L/C. ROMAN LAD requests NEON LAMP meet on CE WINDOW.


111624Z MAR 2024 9031.0 kHz USB [CE WINDOW]
16:24 ROMAN LAD requests radio check from NEON LAMP; L/C.
16:24 ROMAN LAD; "at this time we're gonna try to coordinate some HF data, if you guys are able to, at this moment."
16:24 NEON LAMP; "[...] let us get set up for that."
16:25 ROMAN LAD; "[...] while we're at it, would you guys be able to set up [point to point?]?"
16:26 ROMAN LAD; "were gonna be ahead with Harrises."

16:29 NEON LAMP; "are you guys setting up the point to point?"
16:29 ROMAN LAD; "uh yeah, we should be setting up the point to point. I believe they already did."
16:29 NEON LAMP; "okay, copy. We're doing HF data right now. We had a minor [tasking?] to handle and now we're moving along."

16:35 ROMAN LAD; "at this time my station is ready to transmit. just keep [...] how everything's going on your end."
16:36 NEON LAMP; "we are almost there. we have recently been tasked with a lot of stuff to do so, uh, we're almost there."
16:36 ROMAN LAD; "take your time."
16:39 NEON LAMP; "we are ready for your data, if you guys wanna transmit first."
16:40 ROMAN LAD; "yeah, just give us two seconds."
16:41 ROMAN LAD; "as far as transmission goes, would you guys like to keep 90310 open for communications, and use Z150 as the actual transmit and receive data frequency?"
16:41 NEON LAMP; "copy, Z150. let me dial it in real quick."
16:42 ROMAN LAD; "if everything's set up on your end, we will transmit."
16:42 NEON LAMP; "we are ready to receive."

[Sound can be heard on 9016 kHz USB, probably confirming a list of Z freqs someone provided to me a few months ago. Recording not on livestream.]


111643Z MAR 2024 9031.0 kHz USB
16:44 ROMAN LAD; "we should be done with the transmission. I thought [.. receive?]"
16:44 NEON LAMP; "I did not hear data tones. Are you guys sure you were on Z150?"

16:46 NEON LAMP; "we did not hear any data tones over Z150. request you move to Z120."
16:46 ROMAN LAD; "moving to Z120."
16:46 NEON LAMP; "we are on Z120. ready to receive again."

[Sound can be heard on 13245 kHz USB.]


111647Z MAR 2024 9031.0 kHz USB [Z120]
16:48 NEON LAMP; "are you guys sending data, or what?"
16:48 ROMAN LAD; "give us three more seconds. I'm gonna swap radio and see if everything will come up."

[Sound can be heard on 13245 kHz USB. As described by NEON LAMP momentarily, "one solid tone".] (Livestream does swap over to this frequency and sound is recorded.)


111651Z MAR 2024 9031.0 kHz USB
16:51 NEON LAMP; "be advised we did receive sound from you, but it only sounded like one solid tone. it did not sound like data."
16:52 ROMAN LAD; "alright. I'm gonna have my other panel operators recheck all their [...] clear up anything that may have [...]
16:52 NEON LAMP; "okay, sounds good. we're chilling."

16:56 ROMAN LAD; "at this time, if you guys don't mind, we would like to switch over to secure to see if we can work out some of the [...]"
16:56 NEON LAMP; "let me get loaded up here. should I stay on the CE?"
16:57 NEON LAMP; "request we move HF secure to Z155."
16:57 ROMAN LAD; "copy all, we will go secure to 155. it's gonna take a couple more minutes on our side to just get set up [...] we'll let you know."
16:57 NEON LAMP; "uh, let's go ahead and move to Z155 and do a radio check first." ^{[note 2]}
16:57 ROMAN LAD; "copy all. moving to Z155."


111658Z MAR 2023 18387 kHz USB [Z155]
16:58 ROMAN LAD requests radio check; NEON LAMP has ROMAN LAD L/C, but NEON LAMP's audio sounds distorted.
16:59 ROMAN LAD requests radio check again.
16:59 NEON LAMP's audio still sounds distorted; "request you move to Z210, Z210."

(I do not know which frequency is Z210. Returned to 9031 kHz in case they returned to CE Window and waited.)


111705Z MAR 2023 9031 kHz USB
17:05Z NEON LAMP; "request we move to Z100."
17:05 ROMAN LAD: "moving to Z100."


111705Z MAR 2023 13907 kHz USB [Z100]
17:05 NEON LAMP and ROMAN LAD request radio check at the same time, broadcasting over each other.
17:06 NEON LAMP requests radio check; L/C.
17:06 NEON LAMP; "I'm gonna go ahead and finish setting up for secure, and then I will let you know when I'm ready to go."

17:13 (Signal can be heard on 13907 kHz; lasts under a minute, not sure if related to comms between NEON LAMP and ROMAN LAD.)

17:15 ROMAN LAD; "let me know whenever you're ready."
17:15 NEON LAMP; "stand by, I'm having trouble loading this real quick, I'm trying to find the right setting."

17:31 NEON LAMP; "we are ready to go secure. over."
17:31 ROMAN LAD; "alright, perfect. moving to secure."
17:32 (Digital modem signal can be heard on 13907 kHz. Sounds similar to what I have heard in previous contexts – ANDVT and/or "ANDVT-like". Three additional instances from 17:33 to 17:36.)
17:37 ROMAN LAD; "NEON LAMP, NEON LAMP, this is ROMAN LAD, ROMAN LAD, on 13907 in the clear."
17:39 (Three additional instances of ANDVT/ANDVT-like digital sound from 17:39 to 17:41.)
17:42 ROMAN LAD requests radio check from NEON LAMP; L/C.
17:42 ROMAN LAD; "alright, perfect. we were going out, we believe we heard a garbled transmission coming from you. can you confirm it was coming through and/or if you could hear the status of our voice coming through in the green?"
17:42 NEON LAMP; "I can confirm that - it sounded like you guys were trying to go out as well but for some reason it's not taking up."
17:43 ROMAN LAD; "please say again your last."
17:43 NEON LAMP; "yeah, we could hear you too. sounded like it was garbled. I'm not 100% sure what's going on."
17:45 ROMAN LAD; "can you guys ensure that your [...] net HF is displayed, that you're using HF net secure crypto?"
17:45 NEON LAMP; "it is displayed and I am using the crypto designated in the [cog?]"
17:46 ROMAN LAD; "I could switch to a different radio and hopefully that will play out a little different. not very optimistic in that approach but, you know, [...]"
17:46 NEON LAMP; "repeat your last on that one. I got [stepped on?]"
17:46 ROMAN LAD; "I could go ahead and switch radios using the same frequencies and hopefully it might clear up something. not very optimistic that it will but, you know, anything's worth a shot at this point."
17:46 NEON LAMP; "ok yeah go ahead change radios. I know I had to change a radio because the [..] wasn't working. if you wanna go ahead and do that, let me know, we could try it again."
17:47 ROMAN LAD requests 2 radio checks; L/C.
17:48 ROMAN LAD; "we're gonna go ahead and retry HF secure again using this new radio configuration. I'm gonna say if you don't hear anything coming through by 1751Z if you'd wanna just meet back up on the [clear-fi?]"
17:51 NEON LAMP; "moving to secure now."
17:51 (ANDVT/ANDVT-like digital sound on 13907 kHz; followed by 3 more.)
17:51 NEON LAMP; "hey, does your first line read 1TTB2.4?"^{[note 3]}
17:52 ROMAN LAD; "your last transmission came in a little weak [...] volume. can you please say again your last?"
17:52 NEON LAMP; "does the first line on your display show 1TTB2.4?"
17:53 ROMAN LAD; "that is a negative. mine is reading 1 TTA and then 2.4K."
17:53 NEON LAMP; "say again. I got [stepped on by the PA?]"
17:53 ROMAN LAD; "it is a negative. ours is showing 1 TTA and then 2.4K."
17:53 NEON LAMP; "okay, stand by. let me see if I can get that B to an A. that might be our problem."

(Unrelated comms on 13907 kHz at 18:20. Not familiar, may in fact have also been US military, but at any rate not a part of comms between NEON LAMP and ROMAN LAD.)

18:21 NEON LAMP; "ROMAN LAD, NEON LAMP, onnnn [..] are you there?"^{[note 4]}
18:21 ROMAN LAD; "NEON LAMP, this is ROMAN LAD, on the uh, same. yeah."
18:21 NEON LAMP; "we're having equipment issues with another system so we're gonna go ahead and shift our focus to that. we're about to start [descending?] anyways. whenever we make contact [person?] we'll go over everything."
18:22 ROMAN LAD; "alright, yeah, absolutely. we'll have a debrief then. till then, ROMAN LAD out, bye."
18:23 NEON LAMP; "thank you." 



^{[note 1]} Any ALE signals – a staple on 13907 kHz – are omitted from this transcription. Some radio checks are also omitted.
^{[note 2]} I do not normally comment on operator tone of voice because I think this train of thought can lend to wild speculation, so please take this with a grain of salt. Save for this point, he entire conversation between NEON LAMP and ROMAN LAD is very casual – both are happy to take cues from each other insofar as the progress of this data transmission attempt, with no apparent problem on either side if there are interruptions due to workload, technical difficulties, etc. on either end and even the apparent lack of success at the end is taken in stride on both sides. However, here, NEON LAMP is rather stern – "let go ahead and move to Z155 and do a radio check first." These frequency changes are apparently important. This strikes me as odd, though, as there's no readily obvious reason they switched away from 9031 kHz, and after they did jump frequencies several times ended up on a frequency with regular ALE bursts, other potential US comms, and by the end even forgot what frequency it was that they had ended up on anyways.
^{[note 3]} NEON LAMP and ROMAN LAD both describe how their display reads a little differently. ROMAN LAD mentions spaces between "1" and "TT" and "2.4K" and NEON LAMP does not. I have transcribed this bit according to how they describe it - spaces omitted if not mentioned.
^{[note 4]} NEON LAMP has forgotten which frequency they are on, as has ROMAN LAD. This is still on 13907 kHz.

12

Utility / HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: March 03, 2024, 2359 UTC »

Messages for March 3rd;
031246Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR GOLF FORCE, MIKE FORCE, ERNIE
DISREGARD THIS MESSAGE, THIS IS STEERSMAN, OUT.

Note: Used previous day's callsign.


031247Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR GOLF FORCE, MIKE FORCE, ERNIE
MGBEAX // 3JPDS FID3Q SSGNJ UROGZ KY3S

Note: Used previous day's callsign.


031258Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR GOLF FORCE, MIKE FORCE, ERNIE
MGLPCL // W67C4 GDRHD RHKV6 IRKV6 SYFJ

031547Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR ALPHA FORCE, ERNIE
MGAJ7K // 53US3 7L5WR

Note: Signal was lost during transmission (did not appear to be a problem on receiving end). No disregard was announced.


031550Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR ALPHA FORCE, ERNIE
MGAJ7K // 53US3 7L5WR EQDFG GMCSG 2Y2H

031603Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR ALPHA FORCE, ERNIE
MG5OA5
DISREGARD THIS MESSAGE, THIS IS DOORSILL, OUT.

031604Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR ALPHA FORCE, ERNIE
MG5OA5 // H23JB WTQ5B IFPVR EA5YW LUI3

031743Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE, GOLF FORCE, ERNIE
MGYW7Z // 6SX5F DY4WH MRJR7 7EOBW 6XIE

031751Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE, GOLF FORCE, ERNIE
MG7CWM // 65YNU 46GAL BNRKQ WUKHY WCCS

031902Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE, ERNIE
MGD4WD // XRFIC 3I44B IL4HZ N54O7 VW35

031920Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE, ERNIE
MGCODR // TKQJN ZWX2Y CCFK3 USOJT ZSQU

032032Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE
MG7V3T // QTW6H DIHTK MHEOV WHPEM OPHA

032046Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
FOR BRAVO FORCE
MGONKF // ZQHSB 5DQLG Y66Z5 YGJSX ANV6

032242Z MAR 2024
TO: ALL STATIONS
FROM: DOORSILL
TD3ZZG // S55V2 SX4KF 7ZWC4 B4ZUI E6QP

13

Utility / HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: March 02, 2024, 2350 UTC »

In case you are too busy to monitor this afternoon*;


n.b. Today's callsign sounds more like STEERSMAN to me which is why I have it in my notes as such, but perhaps it is SPEARMAN.

021928Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR ALPHA FORCE
MGYYAZ // 742QG LFC33 MVDXB KZ3MO TJL3

021940Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR ALPHA FORCE
MGJU6X // MWSEP P3XE4 QQGTA MQRUY TTRI

022133Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR ALPHA FORCE
MGRDKT // 6RKRR 634RZ O267N P4DIV GK4P
(This message exhibited broken, "glitchy" audio when received with an SDR in Kansas. No broken audio observed when received with an SDR in Europe. I note this not because I believe the individual receiving SDR is fault, but because I imagine select HFGCS broadcasting antenna(s) or stations might be at fault here.)

022317Z MAR 2024
TO: ALL STATIONS
FROM: STEERSMAN
FOR BRAVO FORCE, MIKE FORCE
MGB6WQ // ZKA2H Q5OMJ VH3SH Q5GBD 2ENF
(This standby exhibited broken, "glitchy" audio.)


082329Z FEB 2024 8992.0 kHz USB
23:29Z This is STEERSMAN standing by for traffic.
(This standby exhibited broken, "glitchy" audio.)



* If you did/do log these yourself, SIGINT, can delete this post so that the thread is easier to follow for readers.

14

Utility / Re: HFGCS General Log

« on: February 23, 2024, 2015 UTC »

232002Z FEB 2024 11175.0 kHz USB
20:02Z NO ID?: "[unintelligible*] We are ready to terminate digital and analog at this time."
20:02Z NO ID?: "3, 2, 1."

* I cannot tell what is being said at the beginning. A recording is available at the relevant timestamp (you'll have to jump to it manually for now); https://www.youtube.com/watch?v=4ssFMSe3wQE

15

Utility / Re: HFGCS Force Directional Message (FDM) and Emergency Action Message (EAM) Log

« on: February 15, 2024, 2027 UTC »

Note: I am missing something here ... the character count does not match the msg content.

It's not "FOR MIKE," it's "4M". You can tell it is part of the EAM because they repeat it as the preamble 3 times; if it was an addressee of a direct EAM they'd only be repeating it twice. This will give you 43 characters for both messages.

They're quite interesting messages, I think. This is possibly how to break them apart;

Code: [Select]

4M4G3SX FCFTR7VS ADDWHX ADDWGE ATEOW ATEDW ATEQS2
4MVDICD FOFMDZGS EYUMJW EYT255 JJBUU TTTPB TPTXIE
Edit:
The 37 character message seems to fit this pattern fine, dropping one of the possible 5 character sections. I am less sure of the 33 character message;

Code: [Select]

4MVA5FW Q2DSAC42 ZSVF47        4PIDZ 4PI4Z 4PIW4G
4MGWWV2 DWBNHVMT OUUP3G        OOEUU              2227O3P