ZNY using 128.675??

[RonR]

It looks like both East Texas 42 (127.17) and Kennedy 56 (125.32) are operating on 127.17 this morning...maybe because it's not so busy yet...

[JetScan1]

It looks like both East Texas 42 (127.17) and Kennedy 56 (125.32) are operating on 127.17 this morning...maybe because it's not so busy yet...

These 2 sectors are often combined or split at different times throughout the day depending on traffic, in the past when the sectors merged 127.17 was shutdown and they would use 125.32 as the primary for both. Now they are doing it the opposite. Maybe issues with 125.32 ? What's 128.67 doing today ?

[RonR]

It looks like both East Texas 42 (127.17) and Kennedy 56 (125.32) are operating on 127.17 this morning...maybe because it's not so busy yet...

These 2 sectors are often combined or split at different times throughout the day depending on traffic, in the past when the sectors merged 127.17 was shutdown and they would use 125.32 as the primary for both. Now they are doing it the opposite.

Maybe issues with 125.32 ? What's 128.67 doing today ?

Yes, I always thought they used 125.32 when combining the two, but not today.  I just heard two flights try to come on to 125.32 but they were told to go back to 127.17

128.675 is quiet at the moment...

[RonR]

Well, no sooner did I post that last comment, 128.675 has come alive again.  It's in place of 125.325...

[RonR]

Here's some more information regarding 125.325 and why 128.675 has been used in its place quite often lately...it seems that when ZNY uses 125.325 there's a dead spot somewhere within the sector where aircraft have difficulty receiving ATC.  In fact, one flight when asked how well he could hear ATC on 128.675, the answer was "much better".

128.675 was in use almost all day yesterday and overnight.  At around 7AM this morning they went back to 125.325 but because of these dead spots have just gone back to 128.675.

When 125.325 is used, the ground side transmits out of Matawan NJ but when 128.675 is used, the ground side comes out of Douglaston NY.  Not sure how you solve a problem like this other than trying a different frequency in Matawan or operate out of a different location entirely, which is what they're doing now...

[dave]

This also makes things difficult on our end trying to cover that sector by itself.  The current receiver site in NJ probably doesn't hear the ground side at Douglaston - but we haven't checked.

Hopefully they will just settle on something soon.  Not too much to do except monitor for now to see what happens.

[RonR]

The ground side comes in loud and clear here.  It's on my JFK#1 feed...

[dave]

The ground side comes in loud and clear here.  It's on my JFK#1 feed...

True...only issue is hard to follow because of the other freqs

I do hear them testing now.

[RonR]

Just caught the tail end of a comment by ATC...they're going to "relocate the transmitter site for this frequency".  Gotta pull the archives to hear the whole thing...

[RonR]

A Cactus flight was asked earlier to switch to 125.325...that flight could not hear ATC on that freq at all at whatever position he was at.  When he came back to 128.675, ATC was 5 x 5.  Considering that earlier comment about "relocating the transmitter", I'd say it's looking pretty good for Douglaston 

[ferraraj]

Strange that they have a problem NOW...they've been using 125.325 out of Matawan for many years! Although 127.175 is listed out of Matawan as well, but its def not there. Ron...are you scanning 127.17 as well? Maybe that was relocated to Douglaston? I think its more likely north...perhaps at SAX, though.

Maybe put a dedicated 128.67 feed at your place?...esp if 125.32 relocates.

[RonR]

Hey Jim,

128.67 has been in use all day again today and is still up now. Yes I'm scanning 127.17 also on my JFK #1 feed but that freq is definitely not coming out of Douglaston. I'm actually a little surprised how good I get the ground side of 128.67 considering it's almost 20 miles away.

And I would definitely add a dedicated feed for that freq if and when it relocates. When I heard that comment earlier today about relocating tbe transmitter site,  I tbought of you because you just set up that dexicated feed for 125.32 

[RonR]

Here's an update on 128.675...at this moment it is being used in place 0f 118.975.  For the past several weeks it was being used in place of 125.325 while ZNY worked on a solution to the problem with the 125.325 transmitter site.  I'm not sure if a solution has been found, but right now this is what's happening with 128.675.  And at the moment ZNY56 and ZNY42 are combined on 127.175...

[RonR]

ZNY56 is back on 125.325 and all the other freqs are where they should be as well.  128.675 is quiet now.  According to some information I received, ZNY was going to try swapping the transmitter sites for 125.325 and 118.975.  There were quite a few problems with 125.325 at the original site so one of the solutions was to try and swap the transmitter sites and that it could be a permanent solution if it worked out well.  Can't say for sure if that's what ZNY has done, but the swap would be my guess.

Ah well, 128.675 was good while it lasted...

[dave]

We should wait a little longer to let this settle out.  I heard handoffs last night to 125.325.  We may be able to get 125.325 coverage from our BLM site.

[RonR]

I agree...for all I know they're still testing this out and haven't yet made a final decision.

[ferraraj]

Maybe I'll dial-in 118.97 from my house and see if they are trying it from Matawan...

[RonR]

128.675 was alive again for the past 24 hours this time being used for ZNY55 Yardley (134.6).  I heard a comment that there was interference on 134.6, that's why the switch to 128.67.  In the past half hour ZNY has gone back to using 134.6...

Ron

[RonR]

ZNY must be having issues with 134.6 now...they are back to using 128.675 again; they've been using it since yesterday...it's currently on my JFK 4 feed.