ENR 7.11 Atlantic High Offshore Airspace Offshore Routes Supporting Florida Airspace Optimization

  1. Introduction
    1. On 27 October 2005, nine new directional offshore Class I area navigation (RNAV) Atlantic Routes (ARs) were established between Florida and northeastern US airport pairs. These routes support the Florida Airspace Optimization project and are designed to relieve traffic congestion and reduce in-trail delays. The nine new offshore RNAV routes, designated AR15, AR16, AR17, AR18, AR19, AR21, AR22, AR23 and AR24, were established between FL240 and FL600 inclusive.
    2. None of the waypoints will be compulsory reporting points since the new and revised routes are entirely within radar coverage.
    3. Southbound routes include AR15, AR17, AR19, and AR22, while northbound routes include AR16 and AR18. AR23, AR24 are bidirectional.
    4. Air traffic control services for these routes in offshore airspace is provided by Washington, Jacksonville and Miami ARTCCs.
  2. Filing Routes
    1. Flights departing from and landing at airports within the domestic U.S. should file to conform with the appropriate Preferred IFR Routes listed in the Chart Supplements. International traffic southbound from the Wilmington VORTAC/Dixon NDB (ILM/DIW) area filing over MCLAW, FUNDI, Fish Hook NDB (FIS), or CANOA should file AR17. International traffic southbound from the ILM/DIW area filing over Freeport VOR (ZFP) or URSUS should file AR23 or AR24. Traffic originating south of Miami, Florida, filing over the ILM/DIW area should file AR16, AR18, AR23 or AR24.
  3. Operational Requirements
    1. Operations on these AR routes requires the use of area navigation (RNAV) systems approved for IFR enroute operations and which incorporate GPS and/or inertial system inputs. For U.S. commercial operators, i.e., those operating under 14 CFR part 91 Subpart K, 121, 125, and 135, use of RNAV systems must be authorized by their Operations Specifications, Management Specifications, or Letters of Authorization. For operators flying under part 91, their Airplane Flight Manual, Pilot Operating Handbook, or other manufacturer-provided documentation should indicate that the RNAV system meets the requirements for IFR enroute RNAV operations in Advisory Circular (AC) 20-138 or AC 90-100, or meets the requirements for inertial navigation systems in 14 CFR part 121 appendix G.
    2. Pilots should fly the route centerlines at all times and must notify Air Traffic Control (ATC) of any loss of navigation capability that affects the aircraft's ability to track the route centerline.
    3. ATC will provide radar separation for these routes. In the event of loss of radar, ATC will advise the aircraft and apply appropriate separation.
    4. Pilots of aircraft without GPS and who therefore must rely on inertial RNAV systems to fly on these AR routes, are limited to one hour of operation between position updates, e.g., DME/DME update of the position in their RNAV system. This one-hour time period starts when the inertial system is placed in the navigation mode and applies en route between position updates. Pilots unable to obtain a position update for their RNAV system must inform ATC prior to one hour from the last update.
    5. Some AR routes are co-designated Y routes, e.g., AR19/Y291. The route filed in the flight plan governs the navigation equipment and performance requirements. Filing for Y291 on a route designated AR19/Y291 for example, requires the aircraft to be equipped with GNSS and flown with RNAV 2 performance on that route, in accordance with section ENR 7.10.