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 massive database of combinations of flights with either suggested or required routing in it. The PRD removes a lot of uncertainty from new and old controllers alike regarding most efficient ways to get out of, or travel around, the N90/PHL TRACONs and ZNY airspaces. This is a fabulous tool that, when utilized properly, makes ZNY a highly efficient ARTCC. From S1 to I3, the PRD is one of the most useful flight verification tools we have.  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).
-=== Ok yes, it's amazing we know, but how does it work? ===
+== Usage ==
-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].
+The PRD is a web-based tool available on the NYARTCC website, at https://nyartcc.org/prd.
-Clicking on the last link brings you to the PRD with a sample route put in, KJFK to KBOS (a very common route on the VATSIM network).
+The PRD interface loads with a default/sample route request, KJFK to KBOS (a very common route on the VATSIM network).
-[[File:PRD-Example.png|900px]]
+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.
-First and foremost, let's discuss what each of the table headers means.
+== Understanding the Results ==
-# From
+[[File:PRD-Example.png|900px|Example PRD Search Results]]
-## This column is the departure airport in question.
-### <u>NOTE</u> 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.
-## There is something very interesting about the JFK-BOS PRD routing. Notice how the first four routes all have checkmarks. This indicates that these routes are '''higher priority''' than the other routes. This essentially means that these routes are agreed upon by multiple facilities in the form of an LOA, SOP, or some other facility directive. '''When at all possible, you must assign one of these routes to the pilot.'''
-### <u>NOTE</u> Each of these routes is subject to restrictions based on aircraft type. Make sure to keep reading on to learn more about how to determine between them.
-# To
-## This column is the arrival airport in question.
-# Area
-## This column indicates which airports are affected by this routing. For instance, the fourth routing published has the content "AND SATS," indicating that all JFK Satellite airports would also be subject to this routing if applicable.
-### <u>NOTE</u> Not every minor airport in ZNY has every PRD routing attached to it when searched. Due to this reality, those issuing clearances at minor airports should '''ALWAYS''' attempt to search for a PRD route from the major airport which indicates that it should be applied to the satellite airports as well.
-# Altitude
-## This column contains the approved altitudes for this route of flight. This column may not always have something in it, but when it does it's for good reason. Make sure to always ensure that airplanes filed on these routing are issued altitudes between the two numbers. 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.
-## Notice how the fourth routing does not assign a top altitude. This means you can clear airplanes as high as they want to fly that route in compliance with direction-of-flight altitude rules.
-# Aircraft
-## 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 assign the most restrictive restriction. 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. Keep reading for a nice flow chart later on regarding all of this
-# CTR FROM
-## This column indicates which ARTCC the PRD applies to. For now, this will always be ZNY
-# CTR TO
-## This column indicates which ARTCC the PRD applies to. This is what column you look at to determine whether or not the airport the aircraft is within 1 ARTCC or is arriving within ZNY. This column is another one that determines whether or not a PRD routing will be required
-=== PRD Decision Making ===
+; Origin
-All of us here at ZNY understand that this can be a lot to take in. Air Traffic Control is an incredibly complex system, and there are things that sometimes just take practice to let sink in. However, we have some extra resources we'd like to provide to ease that transition for all of you new guys and ensure proper utilization of the resources you're already familiar with for you more... senior... fellas.
+: 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.'''
-The following flow chart is usable for any clearance you issue while a controller here at ZNY. We <u>highly</u> recommend giving this a good glance, and maybe even practice with it up on your screen for as long as you need.
+== PRD Decision Making ==
-[[File:PRD-FlowChart.png|700px]]
+Observe this procedure for determining whether to issue a route to a flight:
-'''*NOTE*''' "1 ARTCC away" (or "Tier 1 Facility") is defined at ZNY as ZOB, ZBW, and ZDC or flights to CYYZ. These routes should always be highlighted in green, whether manually added or pulled from the FAA.
+[[File:PRD-FlowChart.png|900px|PRD Assignment Decision Flow Chart]]
-The PRD is manually updated by our staff as we notice inconsistencies with real world operations, changes in LOAs, etc. We pull our routing straight from the FAA [https://www.fly.faa.gov/rmt/nfdc_preferred_routes_database.jsp here]. Additionally, [https://flightaware.com/statistics/ifr-route FlightAware] is a great resource to find routes used in the real world.
+'''NOTE:''' "Tier 1 Facility" is defined as ZOB, ZBW, and ZDC or flights to CYYZ.
-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.
+== Updates ==
-See you on the scopes!
+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.