RNP AR Approaches Flashcards
RNP definition
RNP is a type of performance-based navigation that allows an aircraft to fly a specific path between two 3D defined points in space.
Differences between RNP and RNAV
The key difference between them is the requirement for on-board performance monitoring and alerting during RNP.
Levels of Performance
An RNP of 10 means that a navigation system must be able to calculate its position to within a circle with a radius of 10 nautical miles, an RNP of 0.3 means the aircraft navigation system must be able to calculate its position to within a circle with a radius of 3 tenths of a nautical mile.
RNP AR
The performance requirements to conduct an approach are defined, and aircraft are qualified, against the performance based National Airspace System concept. RNP AR criteria for obstacle evaluation are flexible and designed to adapt to unique operational environments. Operational requirements can include avoiding terrain and
obstacles, de-conflicting airspace or resolving environmental constraints.
RF Leg Segments
Radius Fix or curved legs. Can be located after Final Approach Fix. Denoted as RF Required.
CE-680AS Latitude Capabilities
The Latitude is capable of Lateral RNP values as low as 0.30 NM on initial, intermediate and final approach segments and 1.0 NM on missed approach segments.
Navigation Database Requirements
The aircraft’s onboard navigation database (NDB) defines the RNP AR procedure path and associated constraints, allowing for lateral and vertical guidance. The FAA requires the associated database information be validated.
Database Validation
Validation process is complex and cannot be accomplished by the pilot using the onboard FMS. RNP AR approaches that have been validated by NetJets will be communicated to crewmembers.
RNP AR Approach Requirements
1) Load approach from a current database.
2) RNP 0.3 landing minimums must be depicted on approach chart and at least RNP 1.0 for missed
approach.
3) With SBAS available, the note regarding “uncompensated baro VNAV systems” is not applicable.
4) Low bank may not be selected throughout the approach if there is an RF segment.
5) Use only local altimeter setting.
Aircraft Equipment Requirements
1) One Flight Guidance Controller (Only for procedures with RF legs. NAV and APP selection must be functional).
2) One ADC. Two are required if using Baro VNAV.
3) One GTC.
4) Two GCU-275 PFD controllers. Required only to set altimeter setting.
5) Two GDU 1400W Display Unit.
6) One FMS. A functional FMS is equivalent to a GDU and an on-side GTC.
7) One GPS receiver.
8) One FD (Only for procedures with RF legs).
9) TAWS. If a non-normal checklist refers to an inoperative function of TAWS or Ground Proximity
system, TAWS is considered inoperative for RNP AR approach.
10) RAIM prediction. Required if SBAS is not available.
Flight Release Requirements
Must have the note “Released RNP AR” to be able to conduct RNP AR approaches on the released flight segment. If the note is absent, and RNP AR approach is required at destination, alternate, or diversion airport, the approach may be executed.
Prior to the approach, verify the planned RNP AR approach is listed in the RNP AR Authorized
Procedures list, located in Comply 365, for the applicable database cycle.
Lateral Tolerances (Exceeding Requires Missed Approach)
Full scale deflection during any portion of the approach and missed approach (except for brief deviation during waypoint sequencing).
Vertical Tolerances (Exceeding Requires Missed Approach)
Full scale prior to FAF (or FAP). From FAF to MAP, within the vertical white deviation limit indicators. The deviation limit indicators change to yellow if the limit is exceeded.
Airspeed Restrictions
Comply with published airspeed restrictions. If there are no restrictions published for an RF leg, do not exceed the following 150 KIAS IAF to FAF, 120 KIAS FAF to DA, 150 KIAS DA to MAHP. These speed limits only apply sections of the approach that contain an RF Leg.
Missed Approach prior to MAP
A technique for missed approach early on in the approach is to select the activate missed approach button in the MFD GTC. This allows for waypoint sequencing to the missed approach segment without the requirement to press the TOGA button which would cause issues with speed control and trigger missed approach actions when configuration may still be required for 120 KIAS in the missed approach segment.
Altimeter Requirements
Verify local altimeter setting is set no later than FAF.
Do not use remote altimeter settings.
Prior to FAF, verify left and right primary altimeters are within 100 ft of each other.
Navigation Requirements
Do not select direct to any waypoint when: Inside the FAF, or Immediately preceding an RF leg. Do not change altitude or airspeed constraints for any waypoint between FAF and DA.
TAWS Requirements
Monitor TAWS to ensure obstacle clearance. If TAWS Caution or Warning is annunciated, discontinue the approach and execute TAWS Escape Maneuver.
RAIM Check
Only required if SBAS is unavailable.
Approach Briefing Additional Items
1) Published RNP values for approach segments
2) SBAS or RAIM availability
3) Airspeed restrictions
4) Approach requirements and restrictions
5) Missed approach criteria
Decreasing RNP Transitions
RNP for next leg becomes effective 1 nm prior to the waypoint.
UNABLE RNP Message
Displayed if the system cannot support the new RNP.
Missed Approach Required
Full scale CDI deviation.
Amber VDI and deviation limit indicators.
Amber UNABLE RNP
GPS NAV LOST
Amber GPS LOI
Amber GPS NOT USED
APR ABORT
Primary and secondary altimeters differ by more than 100 ft.
Amber GPS NOT USED Message
This indicates that both GNSS sensors are unavailable and DME/DME or DR navigation is used. DME/DME or DR navigation is acceptable for use during the missed approach, but may not be used to continue the approach.
APR ABORT Message
If SBAS fails 1 minute prior to, or after the FAF, the approach is automatically aborted at FAF. If this occurs, the APR ABORT message is displayed on the PFD, the CDI is removed, and NO GP message is acknowledged for CDI to be restored for missed approach, provided it receives GPS, DME/DME ordisplayed on the VDI. The message must be in DR mode (CDI remains for 20 min. in DR mode).
SBAS Unavailable (More than one minute before FAF)
RNP value changes to amber
APR ADVISORY message is displayed
VDI displays a magenta chevron
Acknowledging the condition (by reading the message on GTC), switches to RNP (Baro VNAV) and the VDI displays a magenta pentagon. To have vertical guidance beyond the FAF, the condition must be acknowledged; otherwise NO GP is displayed on the vertical deviation indicator.
Temperature Compensation
Is available for Baro-VNAV minimums if required when SBAS is not available.
Maximum Predicted RAIM Outage
5 Minutes if SBAS is not available prior to conducting the approach.
