**Special Area Navigation (RNAV) Routes** **Between Florida and Puerto
Rico: Change From "T-routes" to "Y-routes" On 5 June 2008**

**[Introduction.]{.underline}** Effective 05 June 2008 at 0900Z, the
Special Area Navigation (RNAV) routes in the airspace between Florida
and Puerto Rico, previously identified as

"T-routes", will be designated as "Y-routes". The letter "Y" will be
followed by the numerical route number.

**[Background:]{.underline}**

The airspace between the State of Florida and the Commonwealth of Puerto
Rico is designated Class A airspace in Title 14 of the Code of Federal
Regulations (14 CFR).

The applicable sections are Part 71, Section 71.1, which incorporates
FAA Order 7400.9 by reference, and Section 71.33. Historically, air
traffic capacity within this area is constrained by a route structure
based on traditional ground-based navigation aids (NAVAIDs) and
non-mosaic radar facilities.

In 1999, the FAA's Southern Region developed a Special RNAV route
structure to better serve the user community that flies between Florida
and Puerto Rico. Those routes are currently designated "T-routes." They
are being re-designated as "Y-routes" because the "T" designation is now
being used to identify terminal RNAV routes in the National Airspace
System (NAS).

The objective of the Y-routes does not change from that of the original
Special RNAV

T-routes. The objective is to capture the benefits that Global
Navigation Satellite Systems (GNSS) and other approved RNAV systems
provide by enabling aircraft to navigate on direct point-to-point
routes. These special routes augment the existing conventional airway
system and stand as the foundation toward increased efficiency in air
traffic management and decreased operating costs for users.

The FAA has noted that many aircraft, both new and in-service, are being
equipped with GNSS navigation systems. Based on this improved navigation
capability, the FAA is considering future plans to publish and chart
public routes in this area that conform to

AC 90-100, as amended (U.S. Terminal and En Route Area Navigation (RNAV)
Operations) with the intent of further enhancing the safety and
efficiency of the Atlantic High Offshore airspace.

**[Operational Policy and Procedures:]{.underline}**

**[1. Route and fix publication.]{.underline}** On 10 April 2008, the
waypoints that define the Y-routes will be published in the National
Flight Data Digest (NFDD). Y-routes will remain "special" routes and
will not be charted on U.S. government aeronautical charts. The

Y-routes will generally follow the location and orientation of the
T-routes, however, some waypoints will change slightly to accommodate
crossing points with West Atlantic Route System (WATRS) Plus "Lima" and
"Mike" routes.

**[2. Date/time for transition to Y-routes.]{.underline}** Y-routes will
replace T-routes at 0900Z on

5 June 2008. At/after 0900Z on 5 June 2008, aircraft planning to operate
on special RNAV routes between Florida and Puerto Rico will file and fly
Y-routes.

**[3. Operation when ATC radar temporarily OTS.]{.underline}** Normally
these routes operate under radar surveillance. However, under the
conditions detailed below, the routes may continue to operate using
non-radar procedures during periods of temporary air traffic control
(ATC) radar outage. The decision to continue RNAV route operation in
non-radar situation is based on an evaluation of the following
communications, navigation and surveillance (CNS) factors:

A.  Communications: Direct controller-pilot communications via VHF radio
    is available on the routes.

B.  Navigation: Aircraft RNAV systems are approved for Instrument Flight
    Rules (IFR) operation in accordance with existing FAA regulations
    and Advisory Circulars (ACs).

C.  Safety Net: In a non-radar environment, an operational Traffic Alert
    and Collision Avoidance System (TCAS) is required in accordance with
    paragraph 6 below.

D.  Operational environment: Pilot requests for track deviations to
    avoid convective weather and for aircraft contingencies or
    emergencies will be managed in accordance with existing ATC
    procedures.

**[4. Operational approval]{.underline}**

A.  [Class I Navigation:]{.underline} operations on the Y-routes will
    continue to be categorized as Class I navigation, as defined in FAA
    Order 8900.1, Vol. 4, Chapter 1, Section 3, Class I Navigation.

> **Note**: FAA Order 8900.1, Vol. 4, Chap. 1, Sect. 3, Paragraph 4-56
> states that area navigation is an approved type of IFR Class I
> navigation.

B.  [Operations Specifications:]{.underline} operators are considered
    eligible to conduct operations on the Y-routes provided that
    aircraft are equipped with the appropriate equipment in accordance
    with paragraph 5 and 6 below and operations are conducted in
    accordance with paragraph 7 below. Title 14 CFR Parts 121, 125, 135
    operators are authorized to operate on the Y-routes when they are
    issued Operations Specifications (OpSpecs) paragraph B034 (Class I
    Navigation Using Area Navigation Systems). In addition, OpSpecs B034
    must be annotated in OpSpecs paragraph B050 (Enroute Authorizations,
    Limitations and Procedures), for the Caribbean Sea area of
    operations.

C.  [Title 14 CFR Part 91 Operators:]{.underline} Title 14 CFR Part 91
    operators are considered eligible to conduct operation on the
    Y-routes provided aircraft are equipped with approved equipment in
    accordance with paragraphs 5 and 6 and operations are conducted in
    accordance with paragraph 7. Title 14 CFR Part 91 operators must
    review their Airplane Flight Manual (AFM) and verify that the
    aircraft RNAV system has been approved and installed in accordance
    with one of the FAA Advisory Circulars listed in paragraph 5. If the
    operator is unable to verify that the AFM shows that the aircraft
    RNAV system is appropriately approved, then it should contact the
    local Flight Standards District Office (FSDO) for help in
    determining eligibility. The FSDO may contact the Flight
    Technologies and Procedures Division (AFS-400) if further assistance
    is required. (See paragraph 8 for contacts). **A specific Letter of
    Authorization is not required.**

**[5. Operator determination of RNAV equipment
eligibility.]{.underline}** Operators will not flight plan nor operate
on Y-routes unless their aircraft is equipped with RNAV systems that are
approved for IFR navigation. Aircraft may be considered eligible to
operate on

Y-routes if the AFM shows that the navigation system installation has
received airworthiness approval in accordance with one of the following
ACs:

A.  AC 90-45A (Approval of Area Navigation Systems for use in the U.S
    National Airspace System)

B.  AC 20-121A (Airworthiness Approval of LORAN-C Navigation Systems for
    use in U.S. National & Airspace System (NAS) and Alaska)

C.  AC 20-130, as amended (Airworthiness Approval of Navigation or
    Flight Management Systems Integrating Multiple Navigation Sensors)

D.  AC 20-138, as amended (Airworthiness Approval of Global Navigation
    Satellite System (GNSS) Equipment); or

E.  AC 25-15 (Approval of Flight Management Systems in Transport
    Category Aircraft)

> Note: for Inertial Navigation System (INS) limitation, see paragraph
> 7D.

**[6. TCAS equipage when ATC radar temporarily out of
service.]{.underline}** An operational TCAS is required for commercial
operators to dispatch for flight on Y-routes when the Y-routes are
**not** operating under radar surveillance. For general aviation
operators, this requirement will be applied when the flight plan is
filed. Air Traffic Control will notify operators that applicable ATC
radar is inoperative as soon as possible.

**[7. Operational requirements and procedures.]{.underline}**

A.  Pilots in command (PIC) filing a Y-route are certifying that the
    crew is qualified and the aircraft equipment meets the requirements
    to conduct RNAV operations.

B.  Pilots in command are responsible for navigating along the
    centerline (as defined by the aircraft navigation systems) in
    accordance with the requirements of

> 14 CFR Part 91.181 (course to be flown) and ICAO Annex 2, Paragraph
> 3.6.2.1.1. (Annex 2, paragraph 3.6.2.1.1 states that flights shall "in
> so far as practicable, when on an established ATS route, operate along
> the defined centerline of that route.")

C.  The PIC shall notify the Miami Air Route Traffic Control Center
    (ARTCC) or San Juan Combined Center Radar Approach Control (CERAP)
    of any loss of navigation capability that affects the aircraft's
    ability to navigate within the lateral limits of the route.

D.  For the purpose of Y-route operation, on routes where Inertial
    Navigation Systems (INS) or Inertial Reference Systems(IRS) cannot
    receive automatic position updates (e.g., DME/DME update) for the
    entire length of the route, aircraft are limited to 1.5 consecutive
    hours of un-updated operation. In preparation for take-off, this
    time starts when the INS or IRS is placed in the navigation mode. En
    route, the maximum time allowed between automatic position updates
    is 1.5 hours. Systems that perform position updating after the pilot
    has manually selected the navigation aid are considered to have
    "automatic update" capability.

E.  Radar monitoring will normally be provided. In the event of a loss
    of radar, the flight crew will be advised. Air traffic control (ATC)
    will ensure that the appropriate non-radar separation is applied
    during these time periods.

F.  Pilots must have and use an en route chart that identifies the
    Y-routes and their waypoints.

G.  Waypoints shall be identified as compulsory or non-compulsory
    reporting points. When the ARTCC/CERAP is providing radar service,
    the operator shall report compulsory points only when requested. In
    accordance with ICAO documents, routes are identified as Y-routes
    and all waypoints/fixes are pronounceable five letter names.

**[8. Contacts for questions.]{.underline}** If there are questions or
request, you may contact one of the following:

A.  Jim McGrath (Miami Air Route Traffic Control Center).

> Phone: +1 305-716-1592; Email: <Jim.McGrath@faa.gov>

B.  Madison Walton (Flight Standards Service, Flight Technologies and
    Procedures Division (AFS-400)). Phone: +1-202-385-4596;

> Email: <Madison.Walton@faa.gov>

C.  Roy Grimes (FAA Separation Standards Program Support, CSSI, Inc).

> Phone: +1-202-863-3692; Email: <RGrimes@cssiinc.com>

**(AJE-32, 3/13/08)**