Appendix 5
(d) Right/left/dual FMC failure, and/or
(e) TAWS warning.
3. Flight Training. In addition to ground training, pilots must receive appropriate training in the performance of RNP AR approaches. This training must reflect any operational documentation provided by the Original Equipment Manufacturers (OEM). Operational training must include: RNP AR procedures; flight deck equipment and display setup; recognition of aural advisories, alerts, and other annunciations; and response to loss of RNP capability in a variety of scenarios embracing the breadth of RNP AR procedures the operator plans to use. Such training may be performed in FSTDs that have been approved for RNP AR training.
a. Selection of Approaches for Training. Selection of approaches for use in training shall reflect a variety of approaches in order to enable pilots to become familiar with different requirements, minimums, lateral and vertical paths, etc. Select approaches from those that pilots can expect to fly. For example, if expected approaches contain RF legs, then use approaches in training containing RF legs. Ideally, operators should use site-specific FSTD visual databases (as opposed to generic visual) for RNP AR approach training. You may give credit during initial qualification for training with site-specific FSTD visuals.
b. Flight Training Subject Matter. Address the following subjects during some portion of RNP AR flight training:
(1) RNP AR Approach Setup:
(a) FMC/control display unit (CDU) setup;
(b) FMC/CDU failure conditions and recognition;
(c) Lateral/vertical guidance information;
(d) Maximum deviations and how they are represented;
(e) Use of map displays;
(f) Required equipment and mitigations for failures;
(g) Any emergency issues; and
(h) Ground proximity warning/escape.
(2) Unplanned Issues.
(a) Loss of vertical navigation (VNAV) path and requirements to regain path; and/or
(b) Radar vector off LNAV path and restrictions to regaining path (e.g., no direct to RF legs, etc.).
(3) Approach Briefing:
Appendix 5
(a) FMC/chart crosscheck;
(b) Verify waypoint names and sequence, speed restrictions, crossing altitudes, and glide path;
(c) Glide path and lateral path issues (e.g., configuration, landing weight, performance, winds, etc.); and
(d) Missed approach requirements.
(4) Missed Approach Briefing:
(a) Immediate turn scenarios—turn radius (bank angle versus speed);
(b) Go around considerations: track hold issues, lateral steering mode during initiation of missed approach in a turn or shortly after rollout from a turn, timely re-engaging of LNAV, and the critical importance of maintaining track to within 1xRNP between the time of initiation of missed approach and re-engagement of LNAV; and/or
(c) Missed approach requiring RNP less than 1.0.
c. RNP AR Approach Requirements.
(1) RNP AR Initial Training. With no prior RNP AR approach experience, each pilot must complete at least four RNP AR approach procedures: two as pilot flying and two as pilot monitoring. These four RNP AR approaches shall employ the unique AR characteristics of the operator’s approved procedures (i.e., RF legs, RNP missed). You must fly two approaches to the DA and two approaches must result in an RNP missed approach procedure. Two of the above approaches will include interrupted approaches resulting in one approach with vectors to resume the approach and one approach resulting in a hold at an initial approach fix (IAF) or transition fix.
NOTE: Pilots with prior experience in RNP or RNAV approach operations may receive credit for all or part of this requirement provided the current operator’s procedures are similar and require no new pilot skills trained in an FSTD.
(2) RNP AR Recurrent Training. Each pilot must complete at least two RNP AR approach procedures: one as pilot flying and one as pilot monitoring. These two RNP AR approaches shall employ the unique AR characteristics of the operator’s approved procedures
(i.e., RF legs, RNP missed). You must fly one approach to the DA and one approach must result in an RNP missed approach procedure. One of the above approaches will include either an interrupted approach resulting in vectors to resume the approach or a hold at an IAF or transition fix.
NOTE: An RNP AR procedure may be substituted for any required precision or nonprecision approach.
Appendix 6
Page 1 (and 2) APPENDIX 6. RNP AR MONITORING PROGRAM
1. Program Requirements. The operator must implement an ongoing RNP AR monitoring program to ensure continued compliance with the guidance of this AC and to identify any negative trends in performance. The monitoring program should gather information from every attempted RNP AR approach and enable the operator to understand why any approaches were unsuccessful. The program should establish internal processes that provide for regular reviews of approach data by appropriate officials.
2. Reporting Requirements. As part of that monitoring program the operator must, for the duration of the interim authorization period, submit the information listed below every 30 days to the CHDO or FSDO granting the RNP AR operational approval. In the event no interim authorization period is assigned, the operator must submit the information to the CHDO/FSDO for at least 90 days following receipt of initial operational approval.
a. Total Number of RNP AR Procedures Conducted.
b. Number of Satisfactory Approaches by Aircraft/System. Satisfactory if completed as planned without any navigation or guidance system anomalies.
c. Reasons for Unsatisfactory Approaches. Examples include:
• UNABLE REQ NAV PERF, NAV ACCUR DOWNGRAD, or other RNP messages during approaches;
• Excessive lateral or vertical deviation;
• Terrain Awareness Warning Systems (TAWS) warning;
• Autopilot system disconnect;
• Navigation data errors; and/or
• Pilot report of any anomaly.
d. Any Pertinent Crew Comments.
Appendix 7
Page 1 APPENDIX 7. RNP AR APPLICATION PREPARATION AND PROCESSING
1. Application Guidelines. In general terms, the successful RNP AR application is one that addresses each requirement listed in Appendices 2 through 6 of this AC. Operators need to show that their aircraft meets the performance requirement specified in Appendix 2. Operators also need to show they have adjusted their operating procedures and training programs to take into account each of the procedural and training requirements listed in Appendices 3 through 6 as applicable. Operators are not required to submit entire flightcrew operating and training manuals, for example, but rather should provide copies of those portions of the manuals that have been updated to reflect the specific RNP AR requirements outlined in this AC. A “complete” application is one that addresses each requirement in this AC and documents that fact.
2. Application Contents. Operators seeking operational approval to conduct RNP AR approaches should provide the following information, under cover letter, to the applicable POI or FSDO:
a. Aircraft Qualification Documentation. The operator should provide documentation from the aircraft manufacturer showing the proposed aircraft equipment meets the requirements of Appendix 2. This documentation should contain any specific hardware or software equipment requirements, procedural requirements, or limitations.
b. Description of Aircraft Equipment. Provide a configuration list that details use of pertinent components and equipment for the operation. The list should include each make, model, and version of FMS software installed.
c. Operating Procedures and Practices. Revise operating manuals to reflect the requirements of Appendices 4 and 6. Operators should submit pertinent portions of manuals and checklists that include information/guidance used for specific operations requested. Part 91 operators should submit those portions of the Aircraft Flight Manual (AFM) and required supplements which specifically relate to RNP AR performance.
d. Navigation Data Validation Program. The operator should describe, in detail, the processes and procedures it has established to meet the requirements pertaining to aircraft navigation databases as prescribed in Appendix 3.
e. Pilot Training Programs. Operators should submit documentation describing their RNP AR pilot training program in accordance with Appendix 5. Operators should also submit a description of the training conducted using simulation, credit given for simulation, and flight simulation training device (FSTD) qualification (“statement of compliance”).
f. Dispatcher/Flight Follower Training. Operators should show how they intend to train dispatchers/flight followers to perform their duties relating to RNP AR, in accordance with Appendix 5.
g. Maintenance Procedures. The operator should show how they have modified their aircraft maintenance procedures to take into account any unique maintenance requirements
Appendix 7 relating to RNP AR operations. Some aircraft and equipment manufacturers have identified specific procedures to ensure the airworthiness of certain equipment required for RNP AR.
h. RNP AR Monitoring Program. The operator must describe its program for collecting data on RNP AR operations in accordance with Appendix 6.
i. Minimum Equipment List (MEL). The operator should document the revisions to the MEL to account for RNP AR approach equipment requirements. The application should include copies of those revised MEL sections.
j. Validation. The operator should submit a proposed validation test plan that would demonstrate they are capable of RNP AR approach operations. FAA Order 8900.1, Volume 3, Chapter 29 provides guidance on validation tests. The validation plan should include a demonstration of:
(1) Aircraft capability to perform RNP AR procedures;
(2) Operational and dispatch procedures;
(3) Effectiveness of training;
(4) Effectiveness of equipment maintenance procedures; and
(5) MEL procedures.
NOTE: The validation plan should take advantage of ground training devices, FSTDs, and aircraft demonstrations. If the operator chooses to conduct the validation in actual flight, the RNP AR approaches must be completed in day VMC.
NOTE: Each make, model, and version of FMS software installed may require a demonstration.
3. Proposed Operating Conditions/Limitations. Operators should submit any proposed conditions, limitations, or non-standard language for the RNP AR operational approval
(i.e., OpSpec, MSpec, or LOA).
4. Application Processing. Figure 1 provides an optional checklist for use by both the operator and FAA personnel processing the application. Figure 2 provides a flow chart describing the process, internal to the FAA, for evaluating an application for RNP AR approval.
FAA Order 8900.1, Volume 3, Chapter 18 also provides this flow. While this flow chart describes application evaluation as a sequential process, operators are encouraged to concurrently submit copies of the application to their local FAA inspector, the regional All Weather Operations Program Manager (AWOPM), and to the Performance Based Flight Systems Branch (AFS-470) at the FAA HQ in Washington, DC. This concurrent submission will ordinarily allow quicker evaluation of the application. The local inspector, AWOPM, and AFS-470 personnel will collaborate on evaluating the application.
Appendix 7
Page 3 FIGURE 1. RNP AR APPROVAL CHECKLIST (OPTIONAL)
1. Name of Operator: ___________________________________
2. Point of Contact: ____________________________________
3. Type of Aircraft: ____________________________________
4. FMS Model and Software Version: ______________________
5. Date Application Submitted: ___________________________
a. Aircraft Qualification/Equipment List
b. Navigation Data Validation Program
c. Maintenance Procedures
d. Training (e.g., Flightcrew/Dispatch)
e. MEL Revision (as required)
f. Operating Procedures and Practices
g. RNP AR Monitoring Program
h. Conditions or Limitations for Approval
i. Dispatch/Flight Following Procedures
j. Validation Successfully Completed (as required)
6. POI Action:
a. Complete review of application and provide recommendation for operational approval to headquarters, via the regional AWOPM, in accordance with Figure 2 Date:_____________
b. Interim RNP AR Approval (Issue LOA or OpSpecs/MSpecs) Date:_____________
c. Final RNP AR Approval (Issue LOA or OpSpecs/MSpecs) Date:_____________
d. Comments:
Appendix 7
Page 4 FIGURE 2. RNP AR APPLICATION FLOW