AIM 5-5-16

Pilot. If unable to comply with the requirements of an RNAV or RNP procedure, pilots must advise air traffic control as soon as possible. For example, “N1234, failure of GPS system, unable RNAV, request amended clearance.”

Pilots are not authorized to fly a published RNAV or RNP procedure (instrument approach, departure, or arrival procedure) unless it is retrievable by the procedure name from the current aircraft navigation database and conforms to the charted procedure. The system must be able to retrieve the procedure by name from the aircraft navigation database, not just as a manually entered series of waypoints.

Whenever possible, RNAV routes (Q- or T-route) should be extracted from the database in their entirety, rather than loading RNAV route waypoints from the database into the flight plan individually. However, selecting and inserting individual, named fixes from the database is permitted, provided all fixes along the published route to be flown are inserted.

Pilots must not change any database waypoint type from a fly-by to fly-over, or vice versa. No other modification of database waypoints or the creation of user-defined waypoints on published RNAV or RNP procedures is permitted, except to: Change altitude and/or airspeed waypoint constraints to comply with an ATC clearance/instruction.

Insert a waypoint along the published route to assist in complying with ATC instruction, example, “Descend via the WILMS arrival except cross 30 north of BRUCE at/or below FL 210.” This is limited only to systems that allow along-track waypoint construction.

Pilots of FMS-equipped aircraft, who are assigned an RNAV DP or STAR procedure and subsequently receive a change of runway, transition or procedure, must verify that the appropriate changes are loaded and available for navigation.

For RNAV 1 DPs and STARs, pilots must use a CDI, flight director and/or autopilot, in lateral navigation mode. Other methods providing an equivalent level of performance may also be acceptable.

For RNAV 1 DPs and STARs, pilots of aircraft without GPS, using DME/DME/IRU, must ensure the aircraft navigation system position is confirmed, within 1,000 feet, at the start point of take-off roll. The use of an automatic or manual runway update is an acceptable means of compliance with this requirement. Other methods providing an equivalent level of performance may also be acceptable.

For procedures or routes requiring the use of GPS, if the navigation system does not automatically alert the flight crew of a loss of GPS, the operator must develop procedures to verify correct GPS operation.

RNAV terminal procedures (DP and STAR) may be amended by ATC issuing radar vectors and/or clearances direct to a waypoint. Pilots should avoid premature manual deletion of waypoints from their active “legs” page to allow for rejoining procedures.

RAIM Prediction: If TSO-C129 equipment is used to solely satisfy the RNAV and RNP requirement, GPS RAIM availability must be confirmed for the intended route of flight (route and time). If RAIM is not available, pilots need an approved alternate means of navigation. REFERENCE-

AIM, Para 5-1-16 , RNAV and RNP Operations.

Definition of “established” for RNAV and RNP operations. An aircraft is considered to be established on-course during RNAV and RNP operations anytime it is within 1 times the required accuracy for the segment being flown. For example, while operating on a Q-Route (RNAV 2), the aircraft is considered to be established on-course when it is within 2 NM of the course centerline. NOTE-

Pilots must be aware of how their navigation system operates, along with any AFM limitations, and confirm that the aircraft's lateral deviation display (or map display if being used as an allowed alternate means) is suitable for the accuracy of the segment being flown. Automatic scaling and alerting changes are appropriate for some operations. For example, TSO-C129 systems change within 30 miles of destination and within 2 miles of FAF to support approach operations. For some navigation systems and operations, manual selection of scaling will be necessary.

Pilots flying FMS equipped aircraft with barometric vertical navigation (Baro-VNAV) may descend when the aircraft is established on-course following FMS leg transition to the next segment. Leg transition normally occurs at the turn bisector for a fly-by waypoint (reference paragraph 1-2-1 for more on waypoints). When using full automation, pilots should monitor the aircraft to ensure the aircraft is turning at appropriate lead times and descending once established on-course.

Pilots flying TSO-C129 navigation system equipped aircraft without full automation should use normal lead points to begin the turn. Pilots may descend when established on-course on the next segment of the approach.

Previous | Top | Next AIM |

ATPUBS |

FAA |

Send your comments regarding this website.

Chapter 5. Air Traffic Procedures AIM

AIM by Chapter Number Chapter 0. General Information Chapter 1. Air Navigation Chapter 2. Aeronautical Lighting and Other Airport Visual Aids Chapter 3. Airspace Chapter 4. Air Traffic Control Chapter 5. Air Traffic Procedures Chapter 6. Emergency Procedures Chapter 7. Safety of Flight Chapter 8. Medical Facts for Pilots Chapter 9. Aeronautical Charts and Related Publications Chapter 10. Helicopter Operations Chapter 11. Unmanned Aircraft Systems (UAS) Appendix 1 Appendix 2 Appendix 3 Appendix 4 Appendix 5

ATPUBS

AIM by Topic

General Information Explanation of Changes

Air Navigation Navigation Aids

Performance-Based Navigation (PBN) and Area Navigation (RNAV)

Aeronautical Lighting and Other Airport Visual Aids Airport Lighting Aids

Air Navigation and Obstruction Lighting

Airport Marking Aids and Signs

Airspace General

Controlled Airspace

Class G Airspace

Special Use Airspace

Other Airspace Areas

Air Traffic Control Services Available to Pilots

Radio Communications Phraseology and Techniques

Airport Operations

ATC Clearances and Aircraft Separation

Surveillance Systems

Operational Policy/Procedures for Reduced Vertical Separation Minimum (RVSM) in the Domestic U.S., Alaska, Offshore Airspace and the San Juan FIR

Operational Policy/Procedures for the Gulf of America 50 NM Lateral Separation Initiative

Air Traffic Procedures Preflight

Departure Procedures

En Route Procedures

Arrival Procedures

Pilot/Controller Roles and Responsibilities

National Security and Interception Procedures

Emergency Procedures General

Emergency Services Available to Pilots

Distress and Urgency Procedures

Two‐way Radio Communications Failure

Aircraft Rescue and Fire Fighting Communications

Safety of Flight Meteorology

Barometric Altimeter Errors and Setting Procedures

Cold Temperature Barometric Altimeter Errors, Setting Procedures and Cold Temperature Airports (CTA)

Wake Turbulence

Bird Hazards and Flight Over National Refuges, Parks, and Forests

Potential Flight Hazards

Safety, Accident, and Hazard Reports

Medical Facts for Pilots Fitness for Flight

Aeronautical Charts and Related Publications Types of Charts Available

Helicopter Operations Helicopter IFR Operations

Special Operations

Unmanned Aircraft Systems (UAS) General

Small Unmanned Aircraft System (sUAS)

Large UAS (MGOW 55 Pounds or More)

Airspace Access for UAS

UAS Pilot Testing, Certification and Responsibilities

Advanced Air Mobility

UAS Operations on Airports

Other Information and Best Practices

Appendix 1

Appendix 2

Appendix 3

Appendix 4

Appendix 5

Air Traffic Procedures

National Security and Interception Procedures

Chapter 5. Air Traffic Procedures

Section 6. National Security and Interception Procedures