Preferred Route Database: Difference between revisions

Latest revision as of 21:43, 6 July 2025

Introduction

The Preferred Route Database (PRD) is a method of standardizing routes and expediting the flow of traffic. The PRD is a database of suggested or required routings between airport pairs. The data is intended to remove uncertainty regarding efficient routes to exit or transition the N90/PHL TRACONs and ZNY airspaces.

Usage

The PRD is a web-based tool available on the NYARTCC website, at https://nyartcc.org/prd.

The PRD interface loads with a default/sample route request, KJFK to KBOS (a very common route on the VATSIM network).

Enter an airport pair to view available routes from both the FAA Preferred Route database, and those routes administered on the VATSIM network in accordance with the Letters of Agreement between NYARTCC and neighboring facilities.

Understanding the Results

Origin: The departure airport.; 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.
Route: This column is the route portion to check against the airplane your clearing.
Destination: The arrival airport.
Type: Types commonly found in the ZNY PRD include the following:

H: high altitude (i.e., in the flight levels)
L: low altitude (i.e., no higher than 17,000')
TEC: tower enroute control: lower altitude routes through busy airspace that avoid Center airspace.

Area: Indicates which airports are affected by this routing. For instance, Routes may apply to multiple nearby origin and/or destination airports.; Note: 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.; 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.
Altitude: This column contains the approved altitudes for this route of flight. Restrictions may be issued as a range of valid altitudes, or a highest or lowest valid altitude. Assigned altitudes must comply with direction-of-flight altitude rules while fitting into the restrictions listed in the PRD results.; Taking the first checked route for example, this is read as "11,000 to FL210." This means that no flight should be assigned this routing below 11,000 or above FL210.
Aircraft: This field describes 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"). In the event of multiple valid choices of route differentiated only by aircraft type, assign the most restrictive option. For instance, RNAV always overrules non-RNAV. In majority of situations, those who file RNAV capable can also fly Non-RNAV routes, but Non-RNAV capable aircraft can almost never fly RNAV routes.
CTR FROM: The ARTCC covering the departure airport.
CTR TO: The ARTCC covering the arrival airport. This assists in determining whether or not the arrival field is within ZNY or within one of ZNY's Tier 1 Neighbors.
ZNY PREF: 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

Observe this procedure for determining whether to issue a route to a flight:

NOTE: "Tier 1 Facility" is defined as ZOB, ZBW, and ZDC or flights to CYYZ.

Updates

The PRD includes data from the FAA's real-world Preferred Routings, as well as additional routes that are added in accordance with NYARTCC Letters of Agreement with neighboring facilities. The entries in the PRD are updated from time to time as real-world operations change, Letters of Agreement with other facilities on VATSIM are updated, or as required.

@@ Line 1: / Line 1: @@
-==Preferred Use Database Usage==
+== Introduction ==
-=== Introduction ===
+The Preferred Route Database (PRD) is a method of standardizing routes and expediting the flow of traffic. The PRD is a database of suggested or required routings between airport pairs. The data is intended to remove uncertainty regarding efficient routes to exit or transition the N90/PHL TRACONs and ZNY airspaces.
-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 controllers 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 [https://www.fly.faa.gov/ois/tier/zny.htm Tier 1 ARTCCs], or Toronto Pearson Airport (CYYZ).'''
+== Usage ==
+The PRD is a web-based tool available on the NYARTCC website, at https://nyartcc.org/prd.
-=== Ok yes, it's amazing we know, but how does it work? ===
+The PRD interface loads with a default/sample route request, KJFK to KBOS (a very common route on the VATSIM network).
-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 [https://nyartcc.org Home Page] or by clicking [https://nyartcc.org/prd 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).
+Enter an airport pair to view available routes from both the FAA Preferred Route database, and those routes administered on the VATSIM network in accordance with the [[Letters of Agreement]] between NYARTCC and neighboring facilities.
-[[File:PRD-Example.png|900px]]
+== Understanding the Results ==
-The table headers represent:
+[[File:PRD-Example.png|900px|Example PRD Search Results]]
-# ''Origin'': the departure airport
-## '''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.
-# ''Route'': the route the aircraft should follow
-## Routes are often subject to restrictions based on aircraft type. Keep reading to learn how to select among them.
-# ''Destination'': the arrival airport
-## As with the departure airport, the leading "K" is omitted in the PRD but must be present in the aircraft's flight plan.
-# ''Type'': the type of route
-## Types commonly found in the ZNY PRD include the following.
-### H: high altitude (i.e., in the flight levels)
-### L: low altitude (i.e., no higher than 17,000')
-### TEC: tower enroute control: lower altitude routes through busy airspace that avoid Center airspace.
-# ''Area'': which airports the route applies to.
-## Routes may apply to multiple nearby origin and/or destination airports.
-## 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.
-### Example: there is no preferred route from MMU to BWI. However, searching for a preferred route from [https://nyartcc.org/prd?from=teb&to=bwi 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.
-### Example: there is no preferred route from TEB to DTW. However, searching for a preferred route from [https://nyartcc.org/prd?from=ewr&to=dtw EWR to DTW] returns a route with "FROM NEWARK & SATS" that should be used for a TEB departure.
-# ''Altitude'': the required altitude or altitude range
-## This column may be empty. If so, any altitude that is valid for direction of flight (i.e., follows NEODD/SWEVEN) may be assigned.
-## 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.
-## 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.
-## If a range of altitudes is listed, an altitude that is both within that range and follows NEODD/SWEVEN should be assigned.
-# ''Aircraft'': the applicable aircraft type(s)
-## 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").
-## 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.
-# ''CTR FROM'': which ARTCC the aircraft is departing from
-## In our PRD, this will always be ZNY.
-# ''CTR TO'': which ARTCC the aircraft is arriving in
-## This column makes it possible to check if the arrival airport is within 1 ARTCC or is arriving within ZNY.
-# ''ZNY PREF'': whether this is a preferred route
-## 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 ===
+; Origin
-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.
+: The departure airport.
+:''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.
+; Route
+: This column is the route portion to check against the airplane your clearing.
+; Destination
+: The arrival airport.
+; Type
+: Types commonly found in the ZNY PRD include the following:
+* '''H:''' high altitude (i.e., in the flight levels)
+* '''L:''' low altitude (i.e., no higher than 17,000')
+* '''TEC:''' tower enroute control: lower altitude routes through busy airspace that avoid Center airspace.
+; Area
+: Indicates which airports are affected by this routing. For instance, Routes may apply to multiple nearby origin and/or destination airports.
+: ''Note:'' 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.
+: ''Example:'' there is no preferred route from MMU to BWI. However, searching for a preferred route from [https://nyartcc.org/prd?from=teb&to=bwi 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.
+; Altitude
+: This column contains the approved altitudes for this route of flight. Restrictions may be issued as a range of valid altitudes, or a highest or lowest valid altitude. Assigned altitudes must comply with direction-of-flight altitude rules while fitting into the restrictions listed in the PRD results.
+: Taking the first checked route for example, this is read as "11,000 to FL210." This means that no flight should be assigned this routing below 11,000 or above FL210.
+; Aircraft
+: This field describes 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"). In the event of multiple valid choices of route differentiated only by aircraft type, assign the most restrictive option. For instance, RNAV always overrules non-RNAV. In majority of situations, those who file RNAV capable can also fly Non-RNAV routes, but Non-RNAV capable aircraft can almost never fly RNAV routes.
+; CTR FROM
+: The ARTCC covering the departure airport.
+; CTR TO
+: The ARTCC covering the arrival airport. This assists in determining whether or not the arrival field is within ZNY or within one of ZNY's [[#PRD Decision Making|Tier 1 Neighbors]].
+; ZNY PREF
+: 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.'''
-[[File:PRD-FlowChart.png|700px]]
+== PRD Decision Making ==
-"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.
+Observe this procedure for determining whether to issue a route to a flight:
-The PRD is periodically updated as real world operations change, LOAs are updated, etc. Our routing comes [https://www.fly.faa.gov/rmt/nfdc_preferred_routes_database.jsp straight from the FAA].
+[[File:PRD-FlowChart.png|900px|PRD Assignment Decision Flow Chart]]
-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.
+'''NOTE:''' "Tier 1 Facility" is defined as ZOB, ZBW, and ZDC or flights to CYYZ.
-See you on the scopes!
+== Updates ==
+The PRD includes data from the FAA's real-world Preferred Routings, as well as additional routes that are added in accordance with NYARTCC Letters of Agreement with neighboring facilities. The entries in the PRD are updated from time to time as real-world operations change, Letters of Agreement with other facilities on VATSIM are updated, or as required.