fleet talk systems

[usnasa]

does anyone know what freq are fleet talk systems , and is there anything good to hear

http://www.radioreference.com/modules.php?name=TRSDB&sid=4312

thanks all

 

[Al42]

The frequencies are listed on the link you posted.

 

[usnasa]

i know that lol i want to know what they are and what will you hear is it worth programing them into the scanner ? thanks

 

[SCANdal]

Gentlemen,

I love questions like this. You'll see different versions of this type of question pop up once in awhile and I'm always amazed that they get asked. Since it's been a while since I went on this rant, I am overdue...

usnasa, how about if you program in the frequencies yourself and make your own determination if it's "worth programing them into the scanner?" I can't tell you, and I don't think anyone really, truely can tell you what's worth programming into a scanner. There is a thread going on a board somewhere else about what frequency WaWa uses at it's filling stations. Me? I could careless. But there is somebody out there who does and somebody else out there who knew the answer and provided it. Needless to say, some hack popped up on the thread and asked why anybody would care to monitor WaWa's channels. Hell, why would anybody want to listen to NYPD's SOD? Everybody has there own tastes and interests (mine are focused on exotic women from Pacific Rim countries, but I digress...).

NASA, how about this? Find some empty channels in your scanner, program in the frequencies to the trunked system in question, and listen in for a day or two (if it's a weekend, the use level on most business systems tends to slow, so you may have to give it an extra day or so). After YOU hear what there is to hear, then YOU can make a determination if it's worth keeping the system programmed into YOUR scanner or if you end up clearing out the channels and dumping in something else. Going on somebody else's advice could result in one of two bad things happening:

(a) Some one says don't bother. You end up missing out finding something worthwhile to you (say, the one talkgroup on that system that a federal agency uses under contract with the system owner), or

(b) Some one else says don't bother and you end up missing out on the opportunity of learning how, in this specific case, to program in 900 MHz trunked systems into your scanner.

This hobby is all about learning. And the best learning is from direct experience.

SCANdal

 

[usnasa]

OK thanks i will just asked sorry to bother you

 

[maalox]

Gentlemen,

I love questions like this. You'll see different versions of this type of question pop up once in awhile and I'm always amazed that they get asked. Since it's been a while since I went on this rant, I am overdue...

usnasa, how about if you program in the frequencies yourself and make your own determination if it's "worth programing them into the scanner?" I can't tell you, and I don't think anyone really, truely can tell you what's worth programming into a scanner. There is a thread going on a board somewhere else about what frequency WaWa uses at it's filling stations. Me? I could careless. But there is somebody out there who does and somebody else out there who knew the answer and provided it. Needless to say, some hack popped up on the thread and asked why anybody would care to monitor WaWa's channels. Hell, why would anybody want to listen to NYPD's SOD? Everybody has there own tastes and interests (mine are focused on exotic women from Pacific Rim countries, but I digress...).

NASA, how about this? Find some empty channels in your scanner, program in the frequencies to the trunked system in question, and listen in for a day or two (if it's a weekend, the use level on most business systems tends to slow, so you may have to give it an extra day or so). After YOU hear what there is to hear, then YOU can make a determination if it's worth keeping the system programmed into YOUR scanner or if you end up clearing out the channels and dumping in something else. Going on somebody else's advice could result in one of two bad things happening:

(a) Some one says don't bother. You end up missing out finding something worthwhile to you (say, the one talkgroup on that system that a federal agency uses under contract with the system owner), or

(b) Some one else says don't bother and you end up missing out on the opportunity of learning how, in this specific case, to program in 900 MHz trunked systems into your scanner.

This hobby is all about learning. And the best learning is from direct experience.

SCANdal

well duh ? lol

 

[SCANdal]

Maalox,

I remember now why it’s been so long since I posted a message like the one above. It’s was misunderstood the first time around and I come out looking like an upperclassman bully beating up on a freshman. Let me try to put it another way before I put my tail between my legs and scoot away from this topic…

Scannists in general are very curious people. While most people see an ambulance traveling down the road lights and siren and might think to themselves “hmm, I wonder where they are going?” scannists not only know where they are going but will know who else is going too, what hospital any aideds will be removed to, and when the ambulance will be ready for it’s next assignment after it’s all over. It seems natural to me that the same level of curiosity should extend to the systems we try to monitor.

It's too easy to fall into a rut in this (or any) hobby and end up, in some extreme cases, expecting to be spoon fed information about what to try to listen to. Ask yourself when was the last time you picked up your scanner, dropped in a low frequency, a high frequency, and started a random search? The other day I did that in the UHF federal band and found a user using a frequency of another agency that I wasn’t expecting. In other words, I learned something.

I guess, in a wordy way, what I was hoping to say to usnasa was don’t be afraid to try something new.

SCANdal

 

[usnasa]

its kool thanks for the help no harm done peace

 

[michaelsbus]

Well, I got something for usnasa to do: monitor the system and submit any and all info about it. I find it quite interesting that 14 freqs are listed on rr database, but FCC ULS reports only 4 of those . Class of the 900 band freqs is FB4C - community repeater interconnect. 150W?
Probably something along the lines of building security, neighborhood watch, etc. Map it out and submit it to the database.

 

[maalox]

Maalox,

I remember now why it’s been so long since I posted a message like the one above. It’s was misunderstood the first time around and I come out looking like an upperclassman bully beating up on a freshman. Let me try to put it another way before I put my tail between my legs and scoot away from this topic…

Scannists in general are very curious people. While most people see an ambulance traveling down the road lights and siren and might think to themselves “hmm, I wonder where they are going?” scannists not only know where they are going but will know who else is going too, what hospital any aideds will be removed to, and when the ambulance will be ready for it’s next assignment after it’s all over. It seems natural to me that the same level of curiosity should extend to the systems we try to monitor.

It's too easy to fall into a rut in this (or any) hobby and end up, in some extreme cases, expecting to be spoon fed information about what to try to listen to. Ask yourself when was the last time you picked up your scanner, dropped in a low frequency, a high frequency, and started a random search? The other day I did that in the UHF federal band and found a user using a frequency of another agency that I wasn’t expecting. In other words, I learned something.

I guess, in a wordy way, what I was hoping to say to usnasa was don’t be afraid to try something new.

SCANdal

very well put. you sure know your freqs and others.

 

[michaelsbus]

You can find some interesting things digging around the RR database and the FCC ULS. Looks like that site is run by FleetTalk Partners Ltd and subsidiary FleetTalk Services, Inc. Previously, that site was licensed to a bunch of seperate companies (like Ajomar Transportation and Merrick Car Service) in addition to (partnership?) Motorola. Now, the little guys' licenses are expired and FleetTalk is current. (buyout?) FleetTalk also has numerous sites across the country, including Nassau and Suffolk counties. You'll probably hear lots of car services (like Merrick), ambulettes (Ajomar), buses, trucks, the works.
The FleetTalk system in the database is comprised of the Site-1 license WPYH777 and also WQDZ312 with some differences in freqs covered; some older (expired) licenses listed all 14 freqs on one license, some listed 15 freqs. All from the Empire State Building site.
Interestingly, Motorola is listed as a current license holder for the same set of freqs but at the UN building! Don't know if it's a second site for that system or maybe backup.

I find it real interesting the multiple licensing on the same site.Guess I'm too used to seeing the SMR licensed and the users as customers renting airtime.