Preferred Route Database

Preferred Use Database Usage

Introduction

The Preferred Route Database (PRD) is our way of standardizing route and efficiently expediting the flow of traffic. The PRD is a database of combinations of flights with either suggested or required routing. The PRD removes a lot of uncertainty for new and old controllers alike regarding most efficient ways to get out of, or travel around, the N90/PHL TRACONs and ZNY airspaces.

The PRD should be checked for ALL flights within ZNY, to Tier 1 ARTCCs, or Toronto Pearson Airport (CYYZ).

Ok yes, it's amazing we know, but how does it work?

The PRD is really quite simple. The first step is to locate it on the website. This can be accomplished by scrolling down to the bottom of the Home Page or by clicking here.

Clicking on the last link brings you to the PRD with a sample route put in, KJFK to KBOS (a common route on the VATSIM network).

The table headers represent:

1. Origin: the departure airport
   1. Note: because most departure airports in the PRD are in the Contiguous United States (exception: Bermuda - TXKF), the prefix K is omitted from the departure airport code. However, this K will exist in the flight plan of the aircraft you are clearing. You must ensure there is a K in both the departure and arrival airport of the flight plan in the controlling client.
2. Route: the route the aircraft should follow
   1. Routes are often subject to restrictions based on aircraft type. Keep reading to learn how to select among them.
3. Destination: the arrival airport
   1. As with the departure airport, the leading "K" is omitted in the PRD but must be present in the aircraft's flight plan.
4. Type: the type of route
   1. Types commonly found in the ZNY PRD include the following.
      1. H: high altitude (i.e., in the flight levels)
      2. L: low altitude (i.e., no higher than 17,000')
      3. TEC: tower enroute control: lower altitude routes through busy airspace that avoid Center airspace.
5. Area: which airports the route applies to.
   1. Routes may apply to multiple nearby origin and/or destination airports.
   2. Not every minor airport has all of its PRD routings in the database. Therefore, when issuing clearances for aircraft departing from or landing at minor airports, controllers should always search to see if there is a PRD route from the nearest major airport that indicates that applies to the satellite airport.
      1. Example: there is no preferred route from MMU to BWI. However, searching for a preferred route from TEB to BWI returns a route with "FROM TETERBORO(TEB.MMU.CDW)" in this column. That route should therefore be issued to a MMU departure.
      2. Example: there is no preferred route from TEB to DTW. However, searching for a preferred route from EWR to DTW returns a route with "FROM NEWARK & SATS" that should be used for a TEB departure.
6. Altitude: the required altitude or altitude range
   1. This column may be empty. If so, any altitude that is valid for direction of flight (i.e., follows NEODD/SWEVEN) may be assigned.
   2. If a single altitude is listed, the aircraft must be assigned that altitude. Note that these altitudes do not necessarily follow NEODD/SWEVEN; it is ok to issue such altitudes in this case.
   3. If a single altitude with "AOA" (at or above) or "AOB" (at or below) is listed, then a corresponding valid altitude that also follows NEODD/SWEVEN should be assigned.
   4. If a range of altitudes is listed, an altitude that is both within that range and follows NEODD/SWEVEN should be assigned.
7. Aircraft: the applicable aircraft type(s)
   1. This is potentially one of the most important columns for most clearances you will issue. This column determines what type of aircraft can fly this route. This can range from more broader restrictions (like "TURBOJET RNAV ONLY") to very specific restrictions (such as "/E,/F,/G, PROPS ONLY").
   2. If your routing assignment comes down to the aircraft, always select the most restrictive option. For instance, RNAV always overrules non-RNAV. Usually, those who file RNAV-capable can also fly non-RNAV routes, but non-RNAV-capable aircraft can almost never fly RNAV routes. The flowchart below helps make this decision process clear.
8. CTR FROM: which ARTCC the aircraft is departing from
   1. In our PRD, this will always be ZNY.
9. CTR TO: which ARTCC the aircraft is arriving in
   1. This column makes it possible to check if the arrival airport is within 1 ARTCC or is arriving within ZNY.
10. ZNY PREF: whether this is a preferred route
    1. Routes where a checkmark is present, are higher priority than the other routes. When at all possible, you must assign one of these routes to the pilot.

PRD Decision Making

The following flow chart is usable for any clearance you issue while a controller here at ZNY. We highly recommend studying it and referring to it as needed when issuing clearances.

"1 ARTCC away" (or "Tier 1 Facility") is defined at ZNY as ZOB, ZBW, and ZDC or flights to CYYZ. These routes are always highlighted in green in the PRD.

The PRD is periodically updated as real world operations change, LOAs are updated, etc. Our routing comes straight from the FAA.

Obviously, every single situation you will experience while on the network can't be addressed in one document. However, do not hesitate to ask questions in the #ask-staff channel in Discord or by submitting a ticket through the website.

See you on the scopes!