Air Traffic Control Fully Certified
Communication Breakdown; Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Procedure
These are 'WAVEY Shuffle' departures originating from KHPN..CMK..BETHA..HTO..BEADS..SWL.J174./. When these flight plans populate the URET as proposals; this is the routing depicted. When the hand off is accepted by ZBW Sector 32; the routing changes to KHPN..BEADS..SWL.J174. Sector 32 Controllers have been briefed on a mutual understanding that these aircraft will be DIRECT BEADS on initial contact after hand off from N90. These two particular aircraft were never given direct BEADS by the previous controller and were preceding DIRECT HTO when queried. The difference between HTO and BEADS can be as much as a 40 degrees depending on the angle the aircraft enters our airspace. If aircraft are left DIRECT HTO (ESE bound); they are climbing head on with descending JFK arrivals on the PARCH1. We expect them SE bound DIRECT BEADS. Recommendation; 1) Fix the automation. N90 Controllers do not see the update that Sector 32 gets via DIRECT BEADS in the computer. I queried the delivering Controller and he said his routing showed HTO..BEADS. I told him we are expecting them DIRECT BEADS. This is a made up route forced upon ZBW with no LOA or briefing. N90 controllers are unsure; we are unsure. 2) Put into writing; the procedure (DIRECT BEADS); and make sure each individual controller at both N90 and ZBW sign off on the procedure.
ZBW Controller described a confused routing event initiated by N90 noting the procedure in question should be formalized and contained in an LOA.