DOC

13 March 2008

By Jason Alexander,2014-05-06 11:38
26 views 0
13 March 2008

    19 June 08

    Emphasis Item: ICAO Flight Plan, FP Addressing and Field 18 Entries

    Introduction. Paragraph 7 is extracted from the 19 June 08 update of the FAA WATRS Plus Operational Policy/Procedures Notice” posted on this Webpage under “Operating Policy”. Paragraph 7b was updated on 19 June 08. Paragraphs 7f and 7g were posted to the Notice on 13 March 08.

7. Flight Planning Requirements. Not later than 5 May 2008, operators should begin making ICAO

    flight plan annotations in accordance with this paragraph and paragraph 4, if applicable. On/after 5 June 2008, operators shall follow the practices detailed in this paragraph and

    paragraph 4, if applicable.

a. ICAO Flight Plan Requirement. ICAO flight plans shall be filed for operation on oceanic routes and

    areas in the WATRS Plus CTAs.

    b. ICAO Flight Plan AFTN Addressing For Operations in the New York Oceanic CTA/FIR (including WATRS). All flights entering the New York Oceanic CTA/FIR shall address flight plans to

    KZWYZOZX. All flights entering the New York Oceanic CTA/FIR and a U.S. ARTCC and/or Bermuda airspace shall address flight plans to both KZWYZOZX and the appropriate U.S. ARTCC, except Boston.

    (See table below) If operators do not address flight plans to KZWYZOZX, 50 NM lateral separation cannot be applied to them.

    Airspace To Be Entered:

    New York Oceanic CTA/FIR and Required AFTN addresses

    U.S. ARTCCs

    New York (NY) Oceanic CTA/FIR KZWYZOZX

    Boston & NY Oceanic KZWYZOZX only. (This change confirmed 19 June 08). NY domestic and/or Bermuda & NY Oceanic KZNYZQZX & KZWYZOZX Washington (KZDC) & NY Oceanic KZDCZQZX & KZWYZOZX Jacksonville (KZJX) & NY Oceanic KZJXZQZX & KZWYZOZX Miami (KZMA) & NY Oceanic KZMAZQZX & KZWYZOZX San Juan & NY Oceanic TZSUZRZX & KZWYZOZX

c. To inform ATC and to key Ocean21 automation that they have obtained RNP 10 or RNP 4

    authorization and are eligible for 50 NM lateral separation, operators shall:

    (1) annotate ICAO Flight Plan Item 10 (Equipment) with the letters “R” and “Z” and…

    (2) annotate Item 18 (Other Information) with, as appropriate, “NAV/RNP10” or “NAV/RNP4” (no

    space between letters and numbers).

Note: see paragraphs 7f and 7g below! They provide recommended filing practices for domestic U.S.

    RNAV operations and filing with Eurocontrol.

d. 50 NM lateral separation will only be applied to operators/aircraft that annotate the ICAO flight plan in

    accordance with this policy.

    e. Operators that have not obtained RNP 10 or RNP 4 authorization shall not annotate ICAO flight plan Item 18 (Other information) with “NAV/RNP10” or “NAV/RNP4”.

Note: on the ICAO Flight Plan, letter “R” indicates that the aircraft will maintain the appropriate RNP

    navigation specification for the entire flight through airspace where RNP is prescribed. Letter “Z” indicates that information explaining aircraft navigation and/or communication capability is found in Item 18.

f. Recommendation For Filing To Show Domestic U.S. RNAV and Oceanic RNP Capabilities.

    (1) Explanation. On 5 June 2008, the FAA is implementing a program to enhance operators’ capability to communicate their domestic US RNAV capabilities to ATC by requiring an entry following the

    NAV/ indicator in item 18 of the ICAO flight plan. The initiative has provisions for showing RNAV

    capabilities for departure (“D”), enroute (“E”) and arrival (“A”) with RNAV accuracy values. An example

    item 18 entry is: NAV/RNVD1E2A1. The numerals in the example indicate RNAV 1 and RNAV 2

    accuracy. The website for this initiative is at:

    http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/enroute/flight_plan_filing/

     (2) Recommendation. It is recommended that operators show their RNAV capability for domestic

    U.S. and capabilities for oceanic operations (RNP 10 or RNP 4) by filing: “NAV/”, then the domestic US

    alphanumeric sequence, then a mandatory space and then “RNP10” or “RNP4”, as appropriate. The

    following is an example: “NAV/RNVD1E2A1 RNP10”

g. Caution For Westbound Flights From Europe.

     (1) Alphanumeric Character Limitation. Operators should be aware that, until 27 May 08, for

    flight plans filed with Eurocontrol, only 20 alphanumeric characters should be entered after the “NAV/” indicator in flight plan item 18. Operators entering more than 20 characters may have their flight plans

    processed manually. On 27 May 2008, operators will be able to enter up to 50 characters after the

    “NAV/” indicator in flight plan item 18.

    (2) Multiple NAV/ Entries. In addition, operators should be aware that if they make multiple

    “NAV/” entries in a flight plan filed with Eurocontrol, only the last “NAV/” entry will be forwarded. For example, if “NAV/D1E2A1” and “NAV/RNP10” are entered, only “NAV/RNP10” will be forwarded.

    (3) Recommendation. Item 18 entries made in accordance with paragraph 7f (2) above will limit

    the number of characters needed to show domestic U.S. RNAV and oceanic RNP capabilities and mitigate

    the chance that one or the other will not be forwarded for use by FAA domestic and oceanic automation

    systems.

Report this document

For any questions or suggestions please email
cust-service@docsford.com