N90 Callsign Changes

For close to 20 years, ZNY has been using NY_XXX_APP and NY_XXX_DEP for our N90 logon callsigns to the VATSIM network and it has been a staple in how we are shown on the VATSIM network. However; for just about the same amount of time, our controllers and staff have been frustrated by the fact that pilots, especially pilots who have never flown to the New York area before, do not know who to contact in what situation. Additionally, when connected as NY_XXX_APP, users of VATSPY and other tools that display who is online on the VATSIM network, only see a ring centered on JFK, not LGA, EWR or ISP when they are connected.

Today, we're announcing that we are changing the N90 connection callsigns! 

Note: These changes will take effect on April 15th, 06:00z.

Individual Airports

From April 15th, we're moving to a callsign pattern for each individual airport that clearly indicates what airport they are covering. For example, Newark Approach will be known as EWR_APP and LaGuardia as LGA_APP etc. Subsectors will be using the middle identifier to indicate what subsector they are covering, i.e. LGA EMPYR will connect as LGA_E_APP, Kennedy final as JFK_F_APP etc.

The approach sectors will still use the radio callsign “New York Approach” as always, and when coordinating, will still be known as their individual sectors, i.e. the primary sector for the field EWR_APP = Yardley, JFK_APP = Camrn, LGA_APP = Haarp etc.

There are some situations where sub-sectors start with the same identifier, or clashes with reserved callsigns (Mentor) EWR MUGZY and EWR METRO are good examples. In these situations, we use the second letter in the identifier to indicate which sector it is. MUGZY becomes EWR_G_APP and METRO becomes EWR_E_APP.

N90 Combined

When combining two or more fields, for example when one controller is covering both EWR and LGA from the same frequency, the controller shall use NY_APP as their callsign and must keep their controller information update at all times. The controller is required to use their controller info to indicate what airports they are covering. 

If a controller is connected as NY_APP and someone wants to open up a facility already covered by NY_APP, the NY_APP controller may remain connected as NY_APP as long as their controller info is updated, even if they are just covering a single facility.

Example: NY_APP is connected covering EWR, and JFK and JFK_APP connects. NY_APP may remain connected as NY_APP as long as they update their controller info. 

Complete list of callsign changes: