NS Kings Bay TRS Site 1 Search and Store

Location: Kingsland, GA

While I was sleeping last night, I let the BC396 run a Search and Store on the NSB Kings Bay TRS Site 1 (386.050 CC). Only three talkgroups came up that I haven't logged on the site previously, but they are very interesting ones; I wish I had been awake to hear what traffic was on them (if they weren't encrypted):

2016
2048
8410

I have not seen any 4 digit talkgroups come up on the SE DOD TRS sites I've monitored thus far. Additionally, I've not seen any 4 digit talkgroups listed on the Radio Reference website either. For that reason, I'm not convinced that these are legitimate talkgroup IDs. It will take more monitoring to determine if these were actual talkgroups or errors in the Search and Store

Mac McCormick III, KF4LMT

NSB Kings Bay Sites of the Southeast DOD TRS

Location: Kingsland, GA

This afternoon and evening have found me spending time in Kingsland, GA. In my down time, I've been monitoring the NSB Kings Bay site of the Southeast DOD TRS and a site that I believed is a second NSB Kings Bay site.

The site I thought to be the second Kings Bay site, using the control channel 386.1875 is definitely at or near NSB Kings Bay. The signals from the site are extremely strong on and around NSB Kings Bay and the talkgroup activity practically mirrors the already known NSB Kings Bay site. It is pretty safe identifying the site as NSB Kings Bay.

This being a Friday afternoon/evening, there has not been a great deal of talkgroup activity. Here is an overview of the talkgroup activity I've heard (it seems that the two have been simulcasting the same activity):

28053 - encrypted
28058 - encrypted/clear
28081 - encrypted
28087 - encrypted/clear
28563 - encrypted
28050 - Waterfront Security, encrypted
28562 - Police, encrypted/clear
28557 - Fire, encrypted/clear

Throughout the evening and afternoon I have heard nothing on the NSB Kings Bay 406 MHz TRS. I have heard some traffic on it during the daytime on weekdays before but it has almost always sounded civilian in nature.

Tomorrow I hope to have some more time to monitor the Kings Bay sites and some time to monitor the NS Mayport site. I doubt I'll be close enough to hear the NAS Jax site, but I'll definitely take some notes if I'm lucky enough.

Mac McCormick III, KF4LMT

SE DOD Trunked System

As promised, here are the notes from my monitoring of the SE DOD TRS Kings Bay sites on 10 November. Talkgroup IDs are from RadioReference.

386.050 NSB Kings Bay Site
386.1875 Unknown Site

Note: 386.1875 slightly weaker than 386.050 but audible in Kingsland and south end of Brunswick

TG 28027 unknown
-KINGS BAY wkg KEY WEST for radio check (sounded civilian)
TG 28050 NSBKB Waterfront Security; encrypted
TG 28052 unknown; encrypted
TG 28053 unknown; encrypted
TG 28056 NSBKB Security
-E3W clg 19 for radio check
TG 28057 unknown; encrypted/clear
-E3H wkg ????? (encrypted) "send it for E3H"
-unid ref personnel pickup
TG 28059
TG 28064 unknown; encrypted
TG 28081 unknown; encrypted
TG 28082 unknown; encrypted
TG 28087 unknown; encrypted
TG 28562 unknown; encrypted/clear
-unid ref escort
TG 28567 unknown; encrypted


Mac McCormick III, KF4LMT

US DOD Southeastern Region TRS

Yesterday (14 July 2008) I was traveled down I-95 to the Jacksonville area for a short trip into downtown Jacksonivlle. I used the opportunity to do some very brief monitoring of the US Department of Defense Southeastern Region TRS. Due to the nature of the trip, I wasn't able to listen closely and take notes, but I did put the BC-396 into search and store mode. The 396 picked up on the 386.050 Control Channel for NSB Kings Bay and the 385.5625 Control Channel for NAS Jacksonville.

This afternoon I was able to fully review the contents of the BC-396's talkgroup search and store bank:

19457
28050
28051
28053
28056
28057
28058
28061
28064
28081
62036

The 28### series talkgroups all seemed to be from NAS Kings Bay. From what little time I was able to listen, it seemed there was a lot of encrypted traffic. Some talkgroups seemed to be a mix of encrypted and unencrypted stations, i.e. the base station would be in the clear and the mobile would be encrypted. Likewise, during that short listening time, I did not hear any voice traffic (encrypted or clear) on the NAS Jacksonville Control Channel.

As far as 19457 and 62036 go, I did not note which Control Channel they were found on.

Mac McCormick, KF4LMT
kf4lmt@comcast.net

Road Trip Report: Fort Frederica National Monument and Kingsland, GA

Earlier today I took a trip to St. Simon's Island to visit the Fort Frederica National Monument. After visiting Fort Frederica, I went down to Kingsland, GA to try listening to the Department of Defense (DOD) Southeast Regional TRS (a 380-400 Mhz P25 system). While I was at Fort Frederica, I put my BC 396 into Close Call mode in an attempt to find any frequencies the Park Service might be using there. Close Call found nothing, but it appears that the park does use VHF, as there was a VHF quarterwave on top of a park vehicle in the parking lot.

Along the way I did some mobile Public Safety, Federal, and Military monitoring. This report covers the part of the trip outside of the immediate Savannah area (Chatham and Bryan counties). As usual, I didn't monitor very much law enforcement activity.


Military Aviation
BLADE 23/24 (F/A-18A+, VMFA-115) were up on SEALORD's North Primary 284.500 checking in with SEALORD and pushed to W-157 Discrete frequency 385.300 for air combat training. They were using 225.675 for air-to-air, which very well might be their new Tac 2 frequency. 225.675 was first noted in use while the BLADEs were at Avon Park last week; usage there and since the returned to Beaufort seem to indicate that it has replaced 320.200 as their Tac 2 frequency.

CD 1## flights (T-45, VT-7) were working with an unknown aircraft carrier for carrier landing training. They were on SEALORD's South Primary frequency 267.500 and were working each other and unknown station on 233.750 (referred to as Button 15). They mentioned a Button 1, but I was driving and couldn't run a search while driving.

US Coast Guard
There was activity from Sector Charleston's area on Marine VHF Ch. 21, 157.050 and from Sector Jacksonville on Marine VHF Ch. 23, 157.150. On 157.050, Sector Charleston was in communication with USCGC Tarpon and COAST GUARD 41354 was in communication with Station Brunswick.

Liberty County Public Safety
As usual, Liberty County Fire Dispatch on 154.205 (PL 136.5) and Liberty County EMS Dispatch on 155.160 (PL 103.500) were active. I never can get over how good the signal from that 154.205 repeater is and how good it's coverage area is.

FLETC TRS
The Federal Law Enforcement Training Center VHF TRS was pretty much quiet this morning except for occasional radio traffic from Security on TG 64000. For more information on the FLETC System, check the out the system profile on RadioReference.

Glynn County Public Safety
Glynn County Fire Department and Brunswick Fire Departments were very active this morning. The Glynn County FD 1 talkgroup (TG 2000) and Brunswick FD 1 talkgroup (TG 1488) were busy along with 154.385, which was simulcasting dispatches from the Glynn County FD 1 talkgroup. The SEGRMC 1 talkgroup (TG 2960) was active throughout the morning with Ambulance to ER traffic. For more info on the Glynn County TRS, check out the system profile on RadioReference.

Camden County Public Safety
Camden County Fire/EMS Dispatch on 155.880 (PL 118.800) was active with a few dispatches, but the Fire/EMS side of things seemed to be pretty quiet in Camden County this morning.

When I came down the offramp from I-95 southbound to Exit 3 in Kingsland, I was jolted by the sight of what I thought was a Savannah Chatham Metropolitan PD car sitting in the grass at the bottom of the ramp. As I came closer, however I noticed that the car was Kingsland PD car. It was practically identical to an SCMPD car except the lettering (identical in font) read Kingsland Police Department instead of Savannah Chatham Metropolitan Police Department. Otherwise, the striping and lettering style was identical.

Kings Bay NSB TRS
As expected on a weekend, the Kings Bay NSB TRS was pretty quiet except for the Police and Fire Department. I was able to monitor an interesting incident that arose from someone attempting to grill (yes, a food grill...) in one of the bathrooms of a barracks building. Police 1 (TG 368) was busy with 2## and 4## units working 200 (Dispatch) and Fire 1 (TG 1104) was busy with ENGINE # and PORTABLE #. For more info on the Kings Bay NSB TRS, check out the system profile on RadioReference.

DOD Southeastern Region TRS
The main reason I went down to Kingsland after visiting Fort Frederica was to see if there was any activity on the DOD Southeastern Region TRS site at Kings Bay. 386.275 was active with a 9600 baud control channel, but I never heard any talkgroup activity on it. All of the Kings Bay activity I heard was on the Kings Bay TRS. For more info on this system, including the other sites, check out the system profile on RadioReference.

Mac McCormick, KF4LMT
kf4lmt@comcast.net