132.175 is being scanned on the #2 JFK area feed, for some reason it hasn't made its way into the list yet. What you see in the list is handled by someone else. But, I can tell you that 132.175 is being scanned.

A second opinion. The radio is already overloaded with too many frequencies as it is. I'm curious how much you would expect to actually hear on these additional frequencies if they were added on, given all the other frequencies that are already being scanned ?

Sorry Jim, I have to agree with Jet on this. It would be too many on one feed. In fact, I think it's almost too many freqs as it is. But it is a good reason to add another feed. I would consider that, I have the radio for it. Just would need to gather a few other things. A few other freqs could be added too, like ZNY128.575 and ZNY 132.875. Interesting idea tho...

Ron...yes agreed...lots of freqs. Maybe rearrange the feeds so that JFK Arrivals sectors were on one feed and departure sectors on the other. Right now it looks like its more geographic. Easier to follow when the inbounds and outbounds are each bunched all together, etc. Maybe take out a few that are duplicated by Dave's Atl/Mil feed from NH?

BTW...did you re-tighten the squelch on the IGN20 feed (125.575?)...yes it was noisy...but when you opened it up a bit you could still hear a bit of the ground side...I liked that! Your feed...your call... Just my 2 cents...

BTW Ron...my vote would be to use that other radio and split your Clipr feed into two feeds...that's super busy with the 4 ground-side freqs and often too busy to "follow" flights/comms. Specifically...135.8 is often stepped on by 134.0 or 124.52... Again...my 2 cents!

Actually that is also part of the plan. at some point those feeds will also be split up. The one feed 134.0 was added because I could get a decent signal there.for some reason I cannot receive 125.575 there even though it comes from the same transmitter as 134.0. by the way that feed originates out in Ridge New York which is a lot further east from North Babylon. I agree with you that those feeds should be split up you are right they are very busy. I actually have more than one scanner radio I could put into service, the problem is I don't have the raspberry pi's and I also don't have proper antennas.once I have the necessary equipment I would be happy to expand the feeds I have now.the JFK one feed and the JFK to feet are both operating from a single Raspberry Pi. This system is working actually quite well. So maybe that could be done to the single feed out in Ridge. hmm, you've given me something to think about, I'll have to look into this idea.

Heck...I'll send you the $$ for a rasp pi to split the feed!... Thats what we are using at my feed I set up at my dad's near Rome, NY... ZBW-RKA & UCA/ART feeds. I knew they were busy...so set out w/two feeds. working out great.

BTW...can you retweek the feed squelch to hear the "noisy" IGN20 sector?

Oh, what a coincidence! The feed I have out in Ridge New York is also at my dads place. he's very close to Calverton where the signal originates from. right now I'm not home. But when I get back home tomorrow I will look into the IGN 20 signal and see what I can do to improve it. I'm actually in Stamford New York right now and will be going back home tomorrow morning.

by the way, I appreciate the offer for the Raspberry Pi. I might take you up on that! I even have a couple of Griffin iMics lying around so all that's really need is the Raspberry Pi. I'll let u know! Thanks for the offer!

Thanks Jet, I appreciate the offer. Right now I'm experimenting with splitting a single antenna signal to supply two radios. I might go out to my parents place today and see what happens when I split the signal there. The problem there is that they live in a gated community and they have their rules about antennas being visible to others. There's really no room for play there as far as placing the antenna in a higher location (oh, if only I could place it higher ). So, basically, I'd have to work with what's out there right now. I'll PM you when I have a better handle on what can be done there.

And Jim, yes the two JFK area feeds are split somewhat geographically because a lot of the traffic through this area goes north/south. So I tried to arrange the feeds to follow that idea. For example, on JFK2 you can hear northbound overflights getting handed off from 126.875 to 125.45 and then I believe to 125.325 and then to 125.575. There's also departures from KLGA that come on to 134.6 and get handed off to 134.325. From there they get handed off to 133.475 (covered by someone else's feed) and then to 133.975. KBOS arrivals start their descent on 125.325 and get handed off to 134.0. So, there is some method to the madness

BTW, I've been listening to 133.15 for the past hour now and thus far haven't heard anything. Maybe they only use that (and 121.325) when things get busy...

It's always tough when you've got a bunch or frequencies where you only get the airborne side. If I am not mistaken, Ron feeds one from his pop's out east and the other from home in Nassau. The gem in his collection is 134.0, where he can get the ground from his dad's, and if it were me I think I would at the very least have a dedicated radio for that one, run the feed out there in stereo, put that freq on one side and the kettle of fish on the other. At least that way you could get full QSO for one of these many channels, in fact if I had to choose between streaming either a dozen one-sided channels of mostly very brief acknowledgements of instructions or a full air/ground channel that occasionally is dead for hours at a time, I would still choose the latter. Even if you didn't want to run stereo, I would still use two radios, one scanning and the other on 134, and brew up a simple audio priority switch to pad down (not fully mute) the scanning radio whenever the squelch on the fixed radio is opened.

Even without an active device you can make a simple three-way mixer with a handful of resistors and a small chunk of perf-board that will give left, right and center audio with a stereo feed, which is what I use on the HF feed. We're not talking about hard left and right, more like 45 degrees either side, which makes things less disorienting. Using three HF receivers I feed 5550 left, 6577 right 24/7 and 8846 from 9AM to 8PM in the center, and it is rare that two frequencies are in use at the same time, let alone all three, and only when they are switching over as the bands go up and down.

Even with a mono, single channel feed using blended audio, if you group frequencies between two or three radios such that all the channels associated with certain arrivals or departures are allocated to one receiver, with different receivers becoming more active at different times, you will still be far better off than with a single radio scanning a dozen channels.

The feed out at my parents place in Ridge is the one with 134.0, 135.8, 132.3 and 124.525. You can hear both sides of the conversation on all of these frequencies. 132.3 is the odd one...it is only used occasionally. So if this feed were split up, I would probably put 134.0 and 132.3 on one and 135.8 and 124.525 on the other. The only issue is the antenna. I can't put up a second antenna so the signal would have to be split. It would be nice if 134.0 had it's very own feed but then at the same time 135.8 should also have its own feed IMO

So, what about the other feeds here at home? I fully agree that there's a lot happening on both feeds. So, hypothetically speaking, if they were to be split up, what do you guys think of this arrangement:

#1132.525, 126.875, 125.45, 125.325, 125.575

#2120.75, 121.375, 120.975, 133.125, 118.975

#3128.3, 133.5, 127.7

#4134.6, 134.325, 121.025, 133.975

This takes into account as much as possible the routes that flights take through each sector. #1 for example is mostly northbound overflights and descending flights into KLGA and KEWR, #2 has north and southbound flights and also flights descending into JFK. #3 is mostly JFK departing flights going south and #4 seems to be mostly departing flights out of KLGA (and EWR??).

This set up doesn't even consider western approaches and departures from the NY area. 132.875 handles mostly westbound flights and 128.575 handles mostly inbound flights from the west and hands off to 124.625.

So out east, put a splitter in so you can feed your antenna to both radios, add another sound card & stream to your PC. Then, if they both tend to be busy at the same time, put 134.0 on one radio and 135.8 on the other. Then put 124.525 on whichever radio it doubles the least with and 132.3 on the other. If you can set delay by channel, put 2s delay on 134 and 135.8 and no delay on the others.

Same schema at home... group frequencies that either have a common progression (so you hear a flight transitioning between channels) OR that have operations at different times. For example, if you only had one feed you could group JFK CAMRN and ROBER together because they are not always active at the same time. First and foremost are any channels where you get both sides of the conversation... try to have a radio for each of them, turn on their delay so they hold the two-way and keep the other shit from breaking up the QSOs, and then pile in the rest of them according to conflict schedules (when two-way "A" is active, shit "B" usually is not).

If you don't get the ground side, I would probably just pile all the departure stuff, 3 & 4, on one radio, then split 1 & 2 among the other two or three radios. Ideally it would end up in three groups, something like NY area Departures, Arrivals & Overflights.

All I know is when I try to listen to feeds where the guy loads up the scanner, I never hear both sides of the conversation and half the airborne transmissions are partial due to scanning... it is largely incomprehensible and gets boring pretty quickly.

North Mountain is a great site. I had to go up there decades ago to fix a repeater nobody could get figured out. That feed, which I assume is on high ground, will probably be picking up 5-10% of all the flights in the country when you consider the bulk of the flights between the PHL/BOS corridor and the middle/upper mid-west pass overhead on their way to or from Slate Run.