Active Military frqs. in Colorado Springs

[Mick]

Colorado Springs active Military frqs. July 2007

I suspect these are part of Fort Carson and/or Peterson AFB & the SYS ID A931 TRS's in Colorado Springs. I just did not have enough time during a visit last week to get more info. They are not part any listed frqs. for the AF Academy, Peterson AFB, Schreiver AFB, or Fort Carson. I just noticed that the database does not have anything for Cheyenne Mountain. Maybe some of these could be there too.

406.0125 CC
406.9875 CC
407.6125
407.8125
407.8625
407.8875 CC
407.9000 CC
408.1250
408.4250
408.8000
409.0250
409.2750
409.3625
409.3750
409.6375
409.6875
409.7000
409.7250
409.7625
410.1500
410.1625
410.1750
410.3250
410.5500

 

[Mick]

Here's my list from 6 days of monitoring this last week. The Ft. Carson channels can be heard individually using P25, but I just cannot get the Control Channels to work properly in my BCD396T scanner. Saw this at a Radio Hawaii Yahoo Group which may be applicable at Ft. Carson: "They may be using a new STATE of the ART Motorola Equipment called Pacific Land Mobile Radio. Motorola has ADP which if used our digital scanners can't lock on to the 9600 baud datastream." I suspect the Control Channels with System ID A931 belong to Ft. Carson.

I have not determined what Schreiver AFB or Cheyenne Mountain are using for their radio systems.

Colorado Springs active 406-420 MHz Military frqs. January 2008

406.1500 P25 PAFB TRS SID 0157-0101
406.3125 CC (not Ft. Carson; can't get SID, too weak)
406.3625 USAFA TRS SID 5F10
406.5500 USAFA TRS SID 5F10 (listed at RadioReference, not active)
406.5625 P25 PAFB TRS SID 0157-0104
406.7750 CC A931-0002 (Part of the Ft. Carson TRS)
406.9625 USAFA TRS SID 5F10
406.9875 CC too weak
407.0750 CC A931-0001 (Part of the Ft. Carson TRS)
407.1375 P25 (Part of the Ft. Carson TRS)
407.1625 CC USAFA TRS SID 5F10 (not listed at RadioReference)
407.3250 USAFA TRS SID 5F10 (listed at RadioReference, not active)
407.3625 USAFA TRS SID 5F10
407.5500 USAFA TRS SID 5F10 (listed at RadioReference, not active)
407.5625 P25 PAFB TRS SID 0157-0101
407.7625 USAFA TRS SID 5F10
407.8125 P25 (Part of the Ft. Carson TRS)
407.8625 P25 (Part of the Ft. Carson TRS)
407.8875 CC P25 TRS SID 0157-0104, w/406.5625, 408.3625, 409.275 & 409.9625
407.9500 CC A931-0005 (Part of the Ft. Carson TRS)
407.9625 USAFA TRS SID 5F10 (listed at RadioReference, not heard)
408.0000 USAFA TRS SID 5F10 (listed at RadioReference, not heard)
408.0875 P25 PAFB TRS SID 0157-0101
408.1250 P25 (Part of the Ft. Carson TRS)
408.1625 P25 PAFB TRS SID 0157-0101
408.3625 USAFA TRS SID 5F10; P25 PAFB TRS SID 0157-0104
408.4250 P25 (Part of the Ft. Carson TRS)
408.5625 P25 PAFB TRS SID 0157-0101
408.7625 CC USAFA TRS SID 5F10
408.8000 P25
409.0250 P25 (Part of the Ft. Carson TRS)
409.1250 P25 (Part of the Ft. Carson TRS)
409.1625 CC USAFA TRS SID 5F10
409.2750 P25 PAFB TRS SID 0157-0104
409.3125 PAFB TRS SID 0157-0001
409.3500 PAFB TRS SID 0157-0001
409.3625 P25 (Part of the Ft. Carson TRS)
409.3750 P25 (Part of the Ft. Carson TRS)
409.5125 P25 CC PAFB TRS SID 0157-0101
409.5625 CC USAFA TRS SID 5F10
409.6375 P25 (Part of the Ft. Carson TRS)
409.6875 P25 (Part of the Ft. Carson TRS)
409.7000 P25 (Part of the Ft. Carson TRS)
409.7125 USAFA TRS SID 5F10 (listed at RadioReference, not active); (Part of the Ft. Carson TRS)
409.7625 P25 (Part of the Ft. Carson TRS)
409.9625 USAFA TRS SID 5F10; P25 PAFB TRS SID 0157-0104
410.1500 P25 (Part of the Ft. Carson TRS)
410.1625 P25 (Part of the Ft. Carson TRS)
410.1750 P25
410.3250 P25 (Part of the Ft. Carson TRS)
410.5500 P25 (Part of the Ft. Carson TRS)

 

[firescannerbob]

Fort Carson can indeed be monitored in trunking mode, but it requires some tricky programming since it does not use the typical P25 settings. I don't have the info in front of me, but I believe it's been posted here before, if you want to do a little searching.

 

[Mick]

I've done an ample amount of searching and have been unsuccessful in locating Ft. Carson TRS info. I'll be back in July to try again. Best, Mick

Fort Carson can indeed be monitored in trunking mode, but it requires some tricky programming since it does not use the typical P25 settings. I don't have the info in front of me, but I believe it's been posted here before, if you want to do a little searching.

 

[firescannerbob]

Next time you pass through post a note BEFORE you're on your way back out before determining that you can't monitor the system, and someone here will be happy to help.

 

[Mick]

The suspense will kill me while waiting until July to get back there. Is it not able to be posted at this Web site's Colorado Database? Thanks in advance.

Next time you pass through post a note BEFORE you're on your way back out before determining that you can't monitor the system, and someone here will be happy to help.

 

[firescannerbob]

I thought it WAS in the database. I'll see what I can do.

 

[sking128]

Peterson, Schreiver, and Cheyenne Mountain will eventually all be parft of the Peterson System and most channels will be encrypted per AF and DoD rules. there are still som maintenance for the 302nd TAW that I think can still be monitored. I havn't checked since SP's and the FD went encrypted. hope this helps.

Steve

 

[jleverin]

Thanks for the post, I was wondering about frequencies for Fort Carson. Anything that was at Cheyenne is now PAFB(my husband's retired military and used to work in the mountain right before they moved everything to Peterson) I am almost sure it's encrypted and not available to scanning freqs as you have to have a Top Secret clearance to work in there. They won't be letting just anyone access those freqs I suspect. Wish it were possible but I doubt it.

 

[Mick]

While there last week in Springs I was able to hear this info on Peterson with my scanner:

* = Control channel

Peterson AFB (probably covering Cheyenne too)
101 406.1500 407.5625 408.0875 408.1625 408.5625 409.3125* 409.35000 409.5125*
104 406.5625 407.8875* 408.3625 409.2750 409.9625
105 386.2750* 387.4750 387.5750 387.7000

The Security Forces were using TG's that were clear for the dispatcher, but most mobiles were encrypted:
40001 Security Forces dispatch
44001 Security Forces exercises

Also heard:
41001 Fire Dept. training exercises
41003 Fire Dept. training exercises Tac 2
41138 Fire Dept. training exercises supervisor

Undetermined users were using these TG's:
40010
40066
41005
41026
41027
41077
41102
41140
44010
44016
44020

[=sking128]Peterson, Schriever, and Cheyenne Mountain will eventually all be part of the Peterson System and most channels will be encrypted per AF and DoD rules. there are still some maintenance for the 302nd TAW that I think can still be monitored. I haven't checked since SP's and the FD went encrypted. hope this helps.

Steve[/]

 

[firescannerbob]

Here is what I have for Ft. Carson:
CC's:
406.7750
407.0750
407.7625
407.8125
407.9500
407.9625
In Win96, I have "Multi-table" selected under "MOT 9600 CC" and have these values entered:
Base Freq: 406.1125, Offset 380, Step 12.5
Base Freq: 410.1500, Offset 680, Step 12.5
I have the following TG's:
Fire: 00016
Law Enforcement: 00656
Gates: 00768
Range Control: 02240

This all worked in the past, but I'll admit to not listening to them very often.

 

[Mick]

This is tremendous, what a good list. Three of the freqs. match the System ID of A931 that I was seeing on my scanner. The trick must be the base and offset that you have. Outstanding! Thanks for the info.

Here is what I have for Ft. Carson:
CC's:
406.7750
407.0750
407.7625
407.8125
407.9500
407.9625
In Win96, I have "Multi-table" selected under "MOT 9600 CC" and have these values entered:
Base Freq: 406.1125, Offset 380, Step 12.5
Base Freq: 410.1500, Offset 680, Step 12.5
I have the following TG's:
Fire: 00016
Law Enforcement: 00656
Gates: 00768
Range Control: 02240

This all worked in the past, but I'll admit to not listening to them very often.

 

[firescannerbob]

You're welcome Mick.
The trick is indeed the base and offset. Until we had that figured out, we had a heck of time listening to them.

 

[greenthumb]

Bump...

Is the Ft. Carson site with the CC of 407.075 sending the same system ID as these sites that Mick reported?

101 406.1500 407.5625 408.0875 408.1625 408.5625 409.3125* 409.35000 409.5125*
104 406.5625 407.8875* 408.3625 409.2750 409.9625
105 386.2750* 387.4750 387.5750 387.7000

If so, which is the real site 1?

 

[GrayJeep]

How do you do that?

You're welcome Mick.
The trick is indeed the base and offset. Until we had that figured out, we had a heck of time listening to them.

How do you figure out the base and offset info? Trial and error?

 

[Liverdog]

Gents [and ladies], the info for Ft. Carson is in the database, but it does takes some calculations to create the correct splits for the Pro-96... I had to use UniTrunker and do some research on UHF trunking splits, but it's not too difficult...

The 396t/996t are fairly straight forward with the current firmware and can be programmed by hand, but the Pro-96 needs the help of Win 96 to get both splits loaded.

I can drop the info if someone wants it... Just send me a PM and which scanner you need to program.

I've also got some additions to the TGs if you need those as well.

 

[abqscan]

will you post the offsets here for everyone to see, and for us to update the DB.

 

[rfburns]

Pro-96 needs the help of Win 96 to get both splits loaded.

Does V1.55 properly load the two tables? Earlier versions (awhile back) did not. I'm still having trouble with system A73B when I use Win 96 V1.55 to load the two tables into my 96's and 2096. I'm still experimenting with that particular system to see if the issue is Win 96 related.

 

[firescannerbob]

How do you figure out the base and offset info? Trial and error?

I was not the one who came up with those numbers, so I'm not sure how they came about. I just know that they work.

 

[Liverdog]

Does V1.55 properly load the two tables? Earlier versions (awhile back) did not. I'm still having trouble with system A73B when I use Win 96 V1.55 to load the two tables into my 96's and 2096. I'm still experimenting with that particular system to see if the issue is Win 96 related.

Well, you got me on this one... I had to look at the version I had. I just downloaded and paid for Win96 in December (couple of months ago) and it is showing V01.54.

Well here's my best shot at the Pro96 config...

Type: MOT

Control channels in order with my labels

00 FT CARSN CC1 407.07500 MOT 0.0 Delay
01 FT CARSN CC2 406.77500 MOT 0.0 Delay
02 FT CARSN CC3 407.76250 MOT 0.0 Delay
03 FT CARSN CC4 407.96250 MOT 0.0 Delay
04 FT CARSN CC5 407.95000 MOT 0.0 Delay

MOT 3600 CC: Multi table

Extended Trunking Table
Standard Plans: 3600 CC: UHF

#/ CH Lo/ CH Hi/ Base Freq/ Offset/ Step
00/ 380/ 679/ 406.11250/ 380/ 12.5/
01/ 680/ 694/ 410.15000/ 680/ 12.5/


I used UniTrunker and some other methods to calculate these numbers. They work well in the Pro-96 and were compared against the 396t and UniTrunker for completeness and accuracy.

Other TGs not currently in the database (my guesses based on traffic):

ROGUE BASE/ 2576/ (basewide logistics, including janitorial, setup/teardown operations)
LE TAC 2/ 2576/ (security police TAC 2)
RGH RIDER MN/ 40048/ (Rough Rider Main- Task force operations)
WAR HRSE MN/ 39632/ (War Horse Main- Task force operations)
BULLET OPS/ 10656/ (Specific Range operations)


Note: All TGs listed here and in the database are non-encrypted (P25/Astro). The only TG I heard that was encrypted was their Base Security Operations, and that is only an inference based on units saying to switch to Security Ops and then hearing only bleep-blop-scree-cablump...