[MilCom] MIL: 11175.0 USB - OAK CREEK event

Jeff Haverlah jehaverlah at gmail.com
Fri Aug 9 00:35:17 EDT 2024


0427z 09 Jul 24

UTC 08 Aug 24 notable message traffic activity on the HFGCS.

OAK CREEK - HFGCS callword.  All activity heard on 8992.0 USB and 11175.0
USB. The X2 strings are 30-characters in length.

0024z X2YHRW OAK CREEK
0026z X2DJL5 OAK CREEK

0127z X2T6E2 OAK CREEK
0129z X2RK2O OAK CREEK

0135z X2Z64S OAK CREEK

0219z X2RNZH OAK CREEK
0250z  X2RNZH KICKBACK (SOMAT 37 over the Pacific; TACAMO PAC; H+20/H+50)
0320z X2RNZH KICKBACK
0350z X2RNZH KICKBACK
0420z Nothing heard (normal 2 hour window)

0536z X2A4CE OAK CREEK

0600z X2DXCV OAK CREEK
0609z X2H7Q OAK CREEK
0611z X2EGIW OAK CREEK

1418z X2IJH7 OAK CREEK
1422z X2MUSP OAK CREEK
1426z X2CUJC OAK CREEK

[YALE 44 E6 launched from TINKER at 1418z and eventually flew to the Gulf
of Mexico.  Assumed ABNCP mission. There was another E6 that visited the
missile fields in northern CONUS during the local afternoon. TAPA 46
launched from OFFUTT 1746z.]

At this point there is an obvious demarcation in OAK CREEK's activity. OAK
CREEK begins h+00/h+30 restoral repeat broadcasts.

1600z X2IXLA OAK CREEK (initial transmission.)

1630z X2IXLA OAK CREEK
1633z OAK CREEK standing by for traffic (SBFT)
1700z X2IXLA OAK CREEK
1703z OAK CREEK SBFT
1730z Nothing heard.
1736z X2IXLA OAK CREEK and SBFT.
1800z X2IXLA OAK CREEK
1802z OAK CREEK SBFT

1810z CAROLINE (unknown; another E6 perhaps. Maybe TAPA 46?) calling
MAINSAIL on 11175.

1830z X2IXLA OAK CREEK.
No SBFT heard.

1833z X2VSLR; OAK CREEK

1900z X2IXLA; OAK CREEK; SBFT
1900z AUTO BODY (YALE 44 over Gulf of Mexico) calls ALL STATIONS under OAK
CREEK's restoral broadcast but nothing heard after. AUTO BODY is heard by
others with X2VSLR at h+00/h+30 over a 2 hour window.)
1930z X2IXLA; OAK CREEK; SBFT
2000z X2IXLA; OAK CREEK; SBFT
2030z X2IXLA; OAK CREEK; SBFT
2100z X2IXLA; OAK CREEK; SBFT
2130z X2IXLA; OAK CREEK; SBFT

2200z BQCYAT 46-characters; OAK CREEK.
2204z X2IXLA; OAK CREEK
2206z OAK CREEK SBFT.

2230z BQCYAT; OAK CREEK

2236z ROPPVM;OAK CREEK;186-characters. Distinctive 4/18 groups (4 element
single character group followed by 18-character alphanumeric block), ending
with a 4/9 block (4 element single character group followed by a 9
character alphanumeric block).

2300z BQCYAT; OAK CREEK.
2330z nothing heard.
2334z BQCYAT; OAK CREEK.

And it was over.

(New Day HFGCS SULFURIC was active at 0000z 09 Aug 24 with "standing by for
traffic" and quiet afterward.)

As of the 2206z transmission (the H+00 window) the X2IXLA message expired;
and, the standing by for traffic statements ended. Both began at 1600z and
ended at the 2200z transmission. That single X2 string and SBFT were active
for 6 hours.

On a day to day basis their traffic expires at 2 hours or less.

>From the outside there appeared to be two processes at work during the
event:

The HFGCS had their 6 hour restoral transmissions/"standing by for traffic"
activity.

A 30-character string for AUTO BODY's orbit over the Gulf with a "normal"
2-hour window.

OAK CREEK did not repeat the X2VSLR string; and, AUTO BODY did not repeat
the X2IXLA string.

The 46-character BQ string and the 186 character RO string were broadcast
after the end of the 6-hour window.

Jeff Haverlah
-- 
 --------------------------------------------------------------------------
Jeff Haverlah               Coastal Texas
 California, Ohio Valley and European SDRs
---------------------------------------------------------------------------


More information about the MilCom mailing list