AC 90-91D

Historical

Advisory circular · North American Route Program

A newer version is currentThis is a historical version. AC 90-91K is the version in force, approved December 11, 2008.

Approved: March 1, 2000
Last reviewed: March 2, 2001
Cancelled by: AC90-91E
Family: AC 90-91 · 6 versions
Revision: D
14 CFR parts: Unknown Part

Guidance, not mandatory unless a rule or AD requires it. DRS record last changed March 2, 2001.

U.S. Department of Transportation Federal Aviation Administration Advisory Circular AC 90-91D DATE: 8/23/1999 AC No: 90-91D Date: 8/23/99 Change:

Initiated by: ATO-200 Subject: NORTH AMERICAN ROUTE PROGRAM (NRP)

1. PURPOSE. This Advisory Circular provides guidance to users of the airspace system for participation in the North American Route Program (NRP).

2. CANCELLATION. Advisory Circular 90-91C, dated November 23, 1998, National Route Program, is cancelled.

3. BACKGROUND. The North American Route Program is a joint Federal Aviation Administration (FAA) and NAV CANADA program, which harmonizes procedures between the FAA National Route Program and the Canadian Domestic Random Route Program. The objective of the NRP is to harmonize and adopt common procedures, to the extent possible, applicable to random route flight operations at and above Flight Level 290 (FL290) within the conterminous United States and Canada. Additionally, North Atlantic international flights operating within the North American Route (NAR) system, are eligible to participate in the NRP within specific guidelines and filing requirements, outlined in the Canadian Aeronautical Information Regulations and Control (AIRAC). The NRP has been implemented through various phases with the end result of allowing all international and domestic flight operations to participate in the NRP throughout the conterminous United States, Alaska, and Canada. This program allows aircraft operators to select operationally advantageous routings. These route selections could be based on factors such as minimum time, cost, fuel, weather avoidance, aircraft limitations and/or other factors.

4. REQUIREMENTS. Flights may participate in the NRP under

Page 2Open in PDF

specific guidelines and filing requirements provided the flight originates and terminates within the conterminous United States and Canada, or for North Atlantic international flights operating within the NAR system. NRP aircraft are not subject to route limiting restrictions (e.g., published preferred instrument flight rules (IFR) routes) beyond a 200 NM radius of their point of departure (egress) or outside a 200 NM radius of their destination (ingress). Operators should refer to the Canadian AIRAC procedures for specific requirements while operating within Canadian airspace.

5. PROCEDURES.

a. Flights should be filed and flown via Departure Procedures (DP's), Standard Terminal Arrival Routes (STAR), or published preferred IFR routes for at least that portion of flight which is within 200NM from the point of departure (egress) or destination (ingress), (except as stated in paragraph 5b below). If the procedure(s) above are less than 200 NM, published airways may be used for the remainder of the 200 NM.

If published procedure(s) do not exist, published airways may be used for the entire 200NM.

b. Flights may be filed and flown on the complete transition of DP's and/or STAR's for the airport areas listed in Appendix 1, Departure Procedures, and Appendix 2, Standard Terminal Arrival Routes, in lieu of the 200 NM ingress/egress filing requirements described in paragraph 5a above.

c. Flights should not be filed via DP/NRP/STAR transitions within offshore transition areas (12 miles or more off the United States shoreline).

d. Operators should ensure that the route of flight contains no less than one navigational aid (NAVAID), or waypoint (in the fix radial distance (FRD) format) in each delegated area of airspace jurisdiction for each FAA Air Route Traffic Control Center (ARTCC) in which a direct route segment traverses. These NAVAID's, or waypoints must be located within 200 NM of the preceding FAA ARTCC's boundary. Additional route description fixes for each turn point should be defined. Within Canadian airspace, a significant point (NAVAID/waypoint) may also be identified by a coordinate in degrees and minutes of latitude and longitude.

e. For routes that cross the United States/Canadian border west of Sault St. Marie (SSM), a significant point within 30 nautical miles of either side of the border should be filed.

For those flights filed east of SSM file on one of these eight fixes: Sault St. Marie (SSM), London, Ontario (YXU) or QUBIS, TAFFY, TOPPS, EBONY, ALLEX, TUSKY.

f. Operators within the United States should ensure that the route avoids active restricted areas and prohibited areas by at least 3 NM unless permission has been obtained from the using agency to operate in that airspace and the appropriate air traffic control facility has been advised.

Page 3Open in PDF

h. Operators should ensure that "NRP" is entered in the remarks section of each flight plan.

NOTE: "NRP" will be retained in the remarks section of the flight plan if the aircraft is moved due to weather, traffic, or other tactical reasons. In these situations, every effort will be made to ensure the aircraft is returned to the original filed flight plan/ altitude as soon as conditions permit. If the route of flight is altered due to pilot requested or controller initiated direct route, "NRP" will be removed from the remarks section of the flight plan, and the flight will be considered as a non-participant of the NRP.

i. Flight plans should be filed at least one hour prior to departure.

j. Operators should not file a NRP route that conforms to published preferred IFR route(s).

m. Flights not meeting the FAA guidelines contained within this Advisory Circular are to be requested through the FAA nonpreferred route programs. Those requests will be approved or disapproved on a workload-permitting basis.

Page 4Open in PDF

Page 5Open in PDF

Page 6Open in PDF

Page 7Open in PDF

Page 8Open in PDF

Page 9Open in PDF

Page 10Open in PDF

Page 11Open in PDF

Page 12Open in PDF

| |(FREES5) | | | County | | | |Scaggs Island (SGD) |Pilot Nav| Sonoma | | | | | | County | | | |Point Reyes (PYE) |Pilot Nav| Sonoma | | | | | | County | | | |Mendocino (ENI) |Pilot Nav| Sonoma | | | | | | County | |_____|_____________|____________________|_________|____________| | ZOA |Gongs One |Maxwell (MXW) |Pilot Nav| Chico | | |(GONGS1) |Point Reyes (PYE) |Pilot Nav| Chico | | | |Red Bluff (RBL) |Pilot Nav| Chico | | | |Sacramento (SAC) |Pilot Nav| Chico | | | |Williams (ILA) |Pilot Nav| Chico | |_____|_____________|____________________|_________|____________| | ZOA |Homan Two |Red Bluff (RBL) |Pilot Nav| Redding | | |(HOMAN2) |Chico (CIC) |Pilot Nav| Redding | |_____|_____________|____________________|_________|____________| | ZOA |Kendl One |Red Bluff (RBL) |Pilot Nav| Redding | | |(KENDL1) |Tomad (TOMAD) |Pilot Nav| Redding | |_____|_____________|____________________|_________|____________| | ZOA |Krest Three |Itmor (ITMOR) |Pilot Nav| Redding | | |(KREST3) |Shata (SHATA) |Pilot Nav| Redding | | | |Tomad (TOMAD) |Pilot Nav| Redding | |_____|_____________|____________________|_________|____________| | ZOA |Lizrd Two |Oakland (OAK) |Pilot Nav| Napa County| | |(LIZRD2) |Santa Rosa (STS) |Pilot Nav| Napa County| |_____|_____________|____________________|_________|____________| | ZOA |Loupe Nine |Red Bluff (RBL) |Pilot Nav| San Jose | | |(LOUPE9) | | | | |_____|_____________|____________________|_________|____________| | ZOA |Marina Four |Scaggs Island (SGD) |Pilot Nav| Oakland | | |(MARI4) | | | | |_____|_____________|____________________|_________|____________| | ZOA |Molen Three |Mendocino (ENI) |Pilot Nav| San | | |(MOLEN3) | | | Francisco | |_____|_____________|____________________|_________|____________| | ZOA |Porte Three |Panoche (PXN) |Pilot Nav| San | | |(PORTE3) | | | Francisco | |_____|_____________|____________________|_________|____________| | ZOA |Quiet Two |Chico (CIC) |Pilot Nav| San | | |(CUIT2) | | | Francisco | | | |Linden (LIN) |Pilot Nav| San | | | | | | Francisco | | | |Mendocino (ENI) |Pilot Nav| San | | | | | | Francisco | | | |Red Bluff (RBL) |Pilot Nav| San | | | | | | Francisco | | | |Sacramento (SAC) |Pilot Nav| San | | | | | | Francisco | |_____|_____________|____________________|_________|____________| | ZOA |Rebas Three |Chico (CIC) |Pilot Nav| San | | |(REBAS3) | | | Francisco | | | |Mendocino (ENI) |Pilot Nav| San | | | | | | Francisco | | | |Red Bluff (RBL) |Pilot Nav| San | | | | | | Francisco | |_____|_____________|____________________|_________|____________|

Page 13

Load pages 13–23 of 23

Versions of AC 90-91

AC 90-91KNorth American Route ProgramApproved Dec 11, 2008 · 2 pages AC 90-91HHistoricalNorth American Route Program (NRP)Approved Jul 30, 2004 · 2 pages AC 90-91GHistoricalNorth American Route Program (NRP)Approved Jul 30, 2003 · 31 pages AC 90-91FHistoricalNorth American Route Program (NRP)Approved Jul 30, 2002 · 2 pages AC 90-91EHistoricalNorth American Route ProgramApproved Mar 1, 2000 · 28 pages

AC 90-91DHistoricalNorth American Route ProgramApproved Mar 1, 2000 · 23 pages · This page

ADs that cite this AC · 0

No AD in this release cites this AC

Source file

PDF mirrored from FAA DRS32,770 bytesSHA-256 64afa80dc1d7297aa40aba34ce31f1bd2b2db98a3eef8ca0e1ecf25f44cc7050