Meant to say heard more up Senator using my magmount.
I'm in the Groom Creek area just past the northern edge of the evacuated areas, and 2-4 miles north of the fires, most of the tankers/helis are flying directly overhead within a few thousand feet of me. Antenna is an external discone mounted about 20' up. Just about perfect conditions and location for listening, though I'd prefer to not be in the "set" stage for evacuating. Scanners are Uniden BCD996P2 and BCD996T.
I don't think anyone who's not in the immediate area will be able to hear the NIRSC Tac channels, but anyone in Prescott/Prescott Valley should be able to hear the Air frequencies.
Also, I'm not hearing it very well, but I'm picking up retardant load/refuel traffic (presumably at Prescott airport) on 163.1 MHz, it's probably a lot easier to hear in Prescott proper nearer to the airport.
Also… I heard the Sheriff dispatch say that VTAC 36 is activated. Are you hearing anything on that? Would that be a repeated freq or direct? Thx.
It's a good idea to have all of these channels in your scanner, if possible. You never know what you might hear on any of them.
![]()
National Interoperability (United States) Scanner Frequencies and Radio Frequency Reference
Scanner Frequencies and Radio Frequency Reference for National Interoperability (United States)www.radioreference.com
John
Peoria
Also… I heard the Sheriff dispatch say that VTAC 36 is activated. Are you hearing anything on that? Would that be a repeated freq or direct? Thx.
Picking up quite a bit of crew traffic on 171.0625, this looks like it may be a repeater output with the interoperability IR-2 frequency of 170.4125 as an input - the signal is much stronger than the IR-2 signals I'm hearing and consistent, so it might be a good target for those further away from the fire.
I've looked but haven't found 171.0625 or nearby frequencies on any list associated with NIFC/NIRSC/interoperability; in any case it's a new frequency to me.
170.4125 would be paired with 165.9625 not 171.0625
I've not seen 171.0625 in many years [here in New England] it was a link for the UHF USPS network
are they both showing the same PL ??
I mentioned this specifically because it seems to be violating the pairing in the document posted and I can't find any references to a 171.0625 (or any 171.0xxx) frequency in any docs I've seen, which makes it new to me. I didn't expect to see it either.
They're both showing the same PL, 131.8, but that PL is being used on many channels here.
The input channel might be a mis-identification because NIRSC Cmd 3 is 170.425, just 12.5 KHz away and I'm seeing traffic on that as well, so maybe it's really 170.425 and not 170.4125 being repeated on 171.0625.
The signal strength on 170.425 is very high so it's possible it's getting captured on the adjacent channel. Unfortunately being so close to the action means the frequencies can be off a bit and still work.
I'm going to set up yet another scanner and try to see where exactly 171.0625's input really is coming from, but there's little doubt it (or something within a few KHz) is in use.
Generally [my knowledge of reading 205's and some monitoring] that the PL is assigned per fire based on the Crews.
So each Fire may have a different PL
Could be they got it assigned to use as a link between Repeater [Wild Guess] - keep listening
I've been able to directly confirm by listening to both simultaneously that 170.4125 is the input and 171.0625 is the output as I was able to listen to the same traffic (ground crews on the Tango line of the fire) on both, and also that 170.4125 is a being identified differently than the traffic on 170.425 (which is correctly ID'ing as Command 3, per the NIRSC band plan.)
What PL, so if I find an IAP (205) I can compare the info
PL is 131.8
That's being used on all of the NIRSC of frequencies here, not only the 170.4125(IR2)/171.0625 pair but also:
166.725 (NIRSC Tac 4)
166.775 (NIRSC Tac 5)
168.050 (NIRSC Tac 1)
168.075 (NIRSC Cmd 3 Simplex)
168.200 (NIRSC Tac 2)
168.250 (NIRSC Tac 6)
170.425 (NIRSC Cmd 3)
I haven't seen any other PLs on these frequencies, however I did see these:
107.2 on VFIRE22 (154.265)
110.9 on NIFC flight following (168.65)
123.0 and 203.5 on Federal common 2 (168.6125)
156.7 on VTAC13/38 (158.7375)
173.8 on Federal common national (163.7125)
They brought in the incident team from California because AZ's was handling the NM fire.
I just met a crew from Nevada that was scouting my neighborhood.
Keep in-mind VFIRE 22 would be using 156.7, so the user with 107.2 is likely a local user, not the Interop.
So far the only IAP for AZ, I've seen so far is using 146.2 for their tones
I've been able to directly confirm by listening to both simultaneously that 170.4125 is the input and 171.0625 is the output as I was able to listen to the same traffic (ground crews on the Tango line of the fire) on both, and also that 170.4125 is a being identified differently than the traffic on 170.425 (which is correctly ID'ing as Command 3, per the NIRSC band plan.)
Quite likely. There's activity on VTAC11/36 as well that I know is the sheriff, but they were clear they were using the incident frequencies and announce that often on the channel.
VFIRE24 is also active now with 107.2. It probably doesn't help that the local departments use 156.7 on their main dispatch frequencies as well.
The situation with 170.4125 and 170.425 is really driving me bonkers. At this point I think what's happening is due to poor coordination, the repeater with the 171.0625 output is re-transmitting either of those frequencies if they have the 131.8 PL tone due to FM capture effect.
.For the PL tones, maybe one of the California IAPs is using 131.8 and perhaps that plan came over with the California crews.
Do remember that on large incidents such as this one that all the command repeaters are linked and you will hear the same traffic simultaneously on as many repeaters as they have. If you hear 170.4125 as the weaker signal, it may cause you to think it is an input, when in fact, it is another output on a distant peak you are not picking up as well. Remember that command traffic is the only traffic on repeaters and tactical is always simplex. So you don't hear "crews" on the command channel, only division supervisors, operations, branch directors, the IC.
It is NIFC policy that every fire pick one CTCSS tone from the National Standardized Tone List and use it on all frequencies, command and tactical. Tacs are not used on air to air and air to ground frequencies. This fire obviously used Tone 3 (131.8) for all it's frequency outputs. Since each repeater uses a different pair of frequencies Tone 3 can also be used as in input as well.
Also this is confusing "maybe one of the California IAP's is using 131.8." There is one Incident Action Plan that includes one communications plan for each incident. I don't know what you mean by saying a "California IAP." Someone from California does not bring their own IAP to an incident. The IAP is written by the Incident Command Teams' planning section after getting input from all the other sections on the incident. The Communications Unit Leader is responsible for the ICS form 205 (Communications Plan) and is using frequencies assigned by both the Geographical Area Command Center (Southwest Area in this case) with the approval of the communications function at NIFC in Boise, Idaho. They are the coordinators of what frequencies are being used on each incident when national frequencies are needed. There is a lot to this and I don't think you understand the big picture yet.