Appendix 2
g. En route, terminal, and approach procedures applicable to RNAV;
h. The information in this AC;
i. Theory of RNAV, including the differences between B-RNAV/RNAV 5 and P-RNAV;
and
j. Limitations of RNAV.
(1) Charting, database and avionics issues including:
(a) Waypoint naming concepts;
(b) RNAV Path terminator concepts and especially:
1. Use of the ‘CF’ path terminator;
2. Use of the ‘TF’ path terminator; and
3. Fly-by and fly-over waypoints.
(2) Use of the RNAV equipment including:
(a) Retrieving a procedure from the database,
(b) Verification and sensor management,
(c) Tactically modifying the flight plan,
(d) Addressing discontinuities, and
(e) Entering associated data such as:
1. Wind,
2. Altitude/Speed constraints, and
3. Vertical Profile/Vertical Speed.
(f) Flying the procedure,
(g) Use of Lateral Navigation Mode and associated lateral control techniques,
(h) Use of Vertical Navigation Mode and associated vertical control techniques,
(i) Use of automatic pilot, flight director and auto-throttle at different stages of the procedure, and Page 13
Appendix 2
(j) The implications of system malfunctions not RNAV related (e.g., hydraulic failure or engine failure).
5. FLIGHT PLANS. U.S.-registered aircraft filing flight plans into P-RNAV designated airspace are expected to meet the P-RNAV airspace requirements. Operators should indicate approval for P-RNAV operations by annotating block 10 (Equipment) of the ICAO flight plan as required in ICAO Doc 7030. If there are any other flight plan annotations required by individual States, operators should make appropriate annotations.
Appendix 3 APPENDIX 3. INTERNATIONAL CIVIL AVIATION ORGANIZATION (ICAO)
FLIGHT PLANNING ICAO Flight Plan (FPL) Item 10 (a), Area Navigation (RNAV) Equipment Information The implementation of RNAV for en route applications requires the mandatory carriage of Basic Area Navigation B-RNAV/RNAV 5 for instrument flight rules (IFR) operations. The European Civil Aviation Conference (ECAC)-agreed concept for the RNAV implementation will allow for three types of terminal area procedures, with respect to the minimum airborne Navigation (NAV) equipment fit required, namely:
a) Precision Area Navigation (P-RNAV),
b) B-RNAV/RNAV 5, or
c) Non-RNAV.
It is a fundamental requirement for air traffic control (ATC) to be able to distinguish, systematically, between the various levels of RNAV equipment fit, such that the assignment of Standard Instrument Departure (SID)/standard terminal automation replacement system (STARS) can be accomplished in a systematic, efficient and unambiguous manner, without the creation of undue additional controller workload.
The FPL is the vehicle that supports this requirement. The automated processing of the FPL Item 10 information will be fundamental to enabling the systematic display, to all relevant ATC control positions, of the individual aircraft RNAV level of equipage.
Flight planning provisions, in respect of ECAC RNAV equipment carriage requirements, were developed with the following considerations:
a) Consistency with the ICAO Required Navigation Performance (RNP) concept;
b) Consistency with the conclusions reached by ICAO in respect of filing of information with respect to B-RNAV/RNAV 5, namely:
• That B-RNAV/RNAV 5 equipment shall form part of the standard equipment fit and shall therefore be indicated through the use of the letter S in item 10.
• The requirement for the letter R to also be inserted in item 10, in conjunction with the letter S, filed in respect of B-RNAV/RNAV 5.
c) Consistency with the mandatory carriage requirements of B-RNAV/RNAV 5 for en route operations.
d) Consistency with exemptions to B-RNAV/RNAV 5 carriage requirements, granted to operators of State aircraft;
e) The fact that P-RNAV is not mandatory for en route or terminal operations;
f) The fact that an aircraft certification with respect to P-RNAV also represents certification with respect to B-RNAV/RNAV 5;
g) The fact that P-RNAV will be required for designated RNAV terminal area procedures; and
h) That P-RNAV is a transitory step to a possible eventual mandatory requirement for the carriage of RNP-RNAV.
Apply the following when filing RNAV equipment information for flights operating within ECAC airspace:
Item 10 Item 18 Aircraft not equipped with RNAV (State a/c) -- STS/NONRNAV Aircraft equipped with B-RNAV/RNAV 5 SR -- Aircraft equipped with P-RNAV PSR --
NOTE: It is expected that ICAO will agree to a dedicated letter to indicate, in Field 10 of the FPL, that an aircraft is approved for P-RNAV operations.
European plans call for the use of the letter “P” in ICAO Doc 7030.