Federal Freq Identification Thread (Consolidated)

[riveter]

Question for any and all:

I can't remember if it used to be in the DB, but I can't find any reference- does anyone know what site/AO/location DOD 1B5C8-001 Site 0101 is, reporting CC 381.1875? It's showing as a peer to Fort Meade.



And another thing - JNCR always, always shows patches for TG 501 and 593 being patched to 8437. Has anyone ever heard any one of these? I have no reference to any of them or anything close.

 

[BM82557]

DB - United States Department of Defense (1B5C8-001) Trunking System, Multiple, Maryland - Scanner Frequencies has 381.1875 as site 8-08 Kent Island. Maybe DB is incorrect??

 

[riveter]

Sorry, yes, it's also that. Site 0202 is reporting two different peers, 0101 and 0808, with 381.1875 as the current CC. So, they're definitely well spread apart, geographically.

 

[LeSueurC]

ICE Nets

Was the all traffic encrypted?

 

[riveter]

No, they have had a surprising amount in the clear on and off over the last few months.

 

[LeSueurC]

Interesting, down here its always encrypted

 

[ThePhotoGuy]

On 167.75 NAC 68F Balt Fed IO LE 3 listed in database:

FBI Baltimore Conducted the Roll Call on "Baltimore Federal Interop Channel"
ATF Baltimore
MEMA
ATF Wilmington
DEA
FPS
CBP
ICE
US Park Police
US Postal Inspectors
Secret Service
USCG
Baltimore City Police
MD State Police
US Marshals
NSA Police

MEMA was the only person that responded to the roll call. I will have to listen in next week to see if more agencies will call in (Since it is Veterans Day and the Fed’s have off).

 

[riveter]

Oh didn't even know that was going on, that's a really really good moment to tie RID ranges to agencies that I can then use elsewhere for ID'ing TGs and freqs.

Also, semi-related note:

I recently had some opportunity to monitor actual activity (wow) on the IWN NCR system. The cool thing about that system is, being VHF, there's no reason for agencies to want to use different IDs or ID ranges than they usually do. So, I'm still seeing 305xxxx, 356xxxx, and 222xxxx RIDs on there. Even better, I've realized that their talkgroup numbering matches the agency RID ranges, minus two digits. So, 222xxxx radios show up on 222xx talkgroups, etc.

Might be old news for some, but I live just at the edge of the IWN's coverage area and haven't heard any sustained traffic on it before last weekend. So, exciting discovery for little old me.

 

[ThePhotoGuy]

Oh didn't even know that was going on, that's a really really good moment to tie RID ranges to agencies that I can then use elsewhere for ID'ing TGs and freqs.

Very true. I guess they do it on Wednesdays at 1030AM. I had my BCD436hp on so no radio ids but I will leave my PRO-668 on next week to get the radio ids.

Just started to listen/search the federal range after seeing this thread. I always assumed these frequencies would be fully encrypted but I have found some transmissions in the clear. Some interesting transmissions when they are in the clear.

 

[riveter]

And that's why I'm sniffing around. On a related note, one COMPLETELY new conventional system (new agency RID sequence unseen before by me at least):

-------------------------------------------------------------------------------------------------------------------

173.6 - Only DB history is one use as federal IO
NAC 293 - makes it harder
RID 886xxxx
ID - No clue.

 

[ecps92]

http://forums.radioreference.com/fe...-your-mystery-frequencies-45.html#post2475571 No Real ID yet

And that's why I'm sniffing around. On a related note, one COMPLETELY new conventional system (new agency RID sequence unseen before by me at least):

-------------------------------------------------------------------------------------------------------------------

173.6 - Only DB history is one use as federal IO
NAC 293 - makes it harder
RID 886xxxx
ID - No clue.

 

[LeSueurC]

173.78750 NAC 167, FBI down here, wonder if it's the same up there

 

[ecps92]

All depends on where and the Tones.
I've seen/heard in use - ATF, BP, USAF, USFS and yes FBI

Freq's alone are only a start, PL, DPL and NAC added to that equation begin to help make the identification, however with some Common NAC's and use of ODD NAC's, the only other ways are listen (months, not days) and now with the ability to see the Radio ID's that all help in the process

173.78750 NAC 167, FBI down here, wonder if it's the same up there

 

[ThePhotoGuy]

168.8375
NAC 293
RID: 13297xx

168.9625
NAC 293
RID: 52003xx

170.75
NAC 293
RID: 82070xx

 

[kennyblues]

168.8375
NAC 293
RID: 13297xx
US DHS Air 1

168.9625
NAC 293
RID: 52003xx
US DHS Air 2

170.75
NAC 293
RID: 82070xx

US Marshals Courthouse security

 

[riveter]

Yep Yep, though I haven't heard Air 2 on at all, and I've never seen a 132xxxx.

 

[guyiv]

Ocean City Area

170.9125
NAC 167
TG 1
RID 848xxxx
AES
KeyID 38421

 

[riveter]

Ocean City Area

170.9125
NAC 167
TG 1
RID 848xxxx
AES
KeyID 38421

I think my initial submission of that frequency/nac/area was incorrect, reviewing this.

848xxxx I have on USMS channels all over BA/AA, and that Key ID is what shows up on their local BA net too. Think that might be part of the USMS Baltimore office's coverage out that way.

 

[ecps92]

$167 pretty much ID's this as FBI
However keep in mind that the FBI took over some of the Dispatch Services for the USM
according to documents/stories seen on the NET

So the Freq/NAC = FBI
but the user at the time could be... USMS

The Fed Files Blog: US Marshals Service

Ocean City Area

170.9125
NAC 167
TG 1
RID 848xxxx
AES
KeyID 38421

 

[ClayD]

Ocean City Area

170.9125
NAC 167
TG 1
RID 848xxxx
AES
KeyID 38421

What program do you have running to grab this information, especially KeyID?