What is a 'fly-by' waypoint versus a 'fly-over' waypoint in RNAV procedures?

1-2-1. General
a. Introduction to PBN. As air travel has evolved, methods of navigation have improved to give operators
more flexibility. PBN exists under the umbrella of area navigation (RNA V). The term RNA V in this context, as
in procedure titles, just means "area navigation," regardless of the equipment capability of the aircraft. (See
FIG 1-2-1.) Many operators have upgraded their systems to obtain the benefits of PBN. Within PBN there are
two main categories of navigation methods or specifications: area navigation (RNA V) and required navigation
performance (RNP). In this context, the term RNA V x means a specific navigation specification with a specified
lateral accuracy value. For an aircraft to meet the requirements of PBN, a specified RNA V or RNP accuracy must
be met 95 percent of the flight time. RNP is a PBN system that includes onboard performance monitoring and
alerting capability (for example, Receiver Autonomous Integrity Monitoring (RAIM)). PBN also introduces the
concept of navigation specifications (NavSpecs) which are a set of aircraft and aircrew requirements needed to
support a navigation application within a defined airspace concept. For both RNP and RNA V NavSpecs, the
numerical designation refers to the lateral navigation accuracy in nautical miles which is expected to be achieved
at least 95 percent of the flight time by the population of aircraft operating within the airspace, route, or
procedure. This information is detailed in International Civil Aviation Organization's (ICAO) Doc 9613,
Performance-based Navigation (PBN) Manual and the latest FAA AC 90 -105, Approval Guidance for RNP
Operations and Barometric Vertical Navigation in the U.S. National Airspace System and in Remote and Oceanic
Airspace.
FIG 1-2-1
Navigation Specifications
b. Area Navigation (RNA V)
1. General. RNAV is a method of navigation that permits aircraft operation on any desired flight path within
the coverage of ground- or space-based navigation aids or within the limits of the capability of self-contained
aids, or a combination of these. In the future, there will be an increased dependence on the use of RNA V in lieu
of routes defined by ground-based navigation aids. RNA V routes and terminal procedures, including departure
procedures (DPs) and standard terminal arrivals (STARs), are designed with RNA V systems in mind. There are
several potential advantages of RNA V routes and procedures:
Performance-Based Navigation (PBN) and Area Navigation (RNA V) 1-2-1

AIM 2/20/25
(a) Time and fuel savings;
(b) Reduced dependence on radar vectoring, altitude, and speed assignments allowing a reduction in
required ATC radio transmissions; and
(c) More efficient use of airspace.
In addition to information found in this manual, guidance for domestic RNA V DPs, STARs, and routes may also
be found in AC 90-100, U.S. Terminal and En Route Area Navigation (RNA V) Operations.
2. RNA V Operations. RNA V procedures, such as DPs and STARs, demand strict pilot awareness and
maintenance of the procedure centerline. Pilots should possess a working knowledge of their aircraft navigation
system to ensure RNA V procedures are flown in an appropriate manner. In addition, pilots should have an
understanding of the various waypoint and leg types used in RNAV procedures; these are discussed in more detail
below.
(a) Waypoints. A waypoint is a predetermined geographical position that is defined in terms of
latitude/longitude coordinates. Waypoints may be a simple named point in space or associated with existing
navaids, intersections, or fixes. A waypoint is most often used to indicate a change in direction, speed, or altitude
along the desired path. RNA V procedures make use of both fly-over and fly-by waypoints.
(1) Fly-by waypoints. Fly-by waypoints are used when an aircraft should begin a turn to the next
course prior to reaching the waypoint separating the two route segments. This is known as turn anticipation.
(2) Fly-over waypoints. Fly-over waypoints are used when the aircraft must fly over the point prior
to starting a turn.
NOTE-
FIG 1-2-2 illustrates several differences between a fly-by and a fly-over waypoint.
FIG 1-2-2
Fly-by and Fly-over Waypoints
(b) RNA V Leg Types. A leg type describes the desired path proceeding, following, or between
waypoints on an RNA V procedure. Leg types are identified by a two-letter code that describes the path (e.g.,
heading, course, track, etc.) and the termination point (e.g., the path terminates at an altitude, distance, fix, etc.).
Leg types used for procedure design are included in the aircraft navigation database, but not normally provided
on the procedure chart. The narrative depiction of the RNAV chart describes how a procedure is flown. The "path
and terminator concept" defines that every leg of a procedure has a termination point and some kind of path into
that termination point. Some of the available leg types are described below.
1-2-2 Performance-Based Navigation (PBN) and Area Navigation (RNA V)

2/20/25 AIM
(1) Track to Fix. A Track to Fix (TF) leg is intercepted and acquired as the flight track to the following
waypoint. Track to a Fix legs are sometimes called point -to-point legs for this reason. Narrative: "direct
ALPHA, then on course to BRAVO WP ." See FIG 1-2-3.
(2) Direct to Fix. A Direct to Fix (DF) leg is a path described by an aircraft's track from an initial area
direct to the next waypoint. Narrative: "turn right direct BRAVO WP ." See FIG 1-2-4.
FIG 1-2-3
Track to Fix Leg Type
FIG 1-2-4
Direct to Fix Leg Type
(3) Course to Fix. A Course to Fix (CF) leg is a path that terminates at a fix with a specified course
at that fix. Narrative: "on course 150 to ALPHA WP ." See FIG 1-2-5.
Performance-Based Navigation (PBN) and Area Navigation (RNA V) 1-2-3

AIM 2/20/25
FIG 1-2-5
Course to Fix Leg Type
(4) Radius to Fix. A Radius to Fix (RF) leg is defined as a constant radius circular path around a
defined turn center that terminates at a fix. See FIG 1-2-6.
FIG 1-2-6
Radius to Fix Leg Type
(5) Heading. A Heading leg may be defined as, but not limited to, a Heading to Altitude (V A),
Heading to DME range (VD), and Heading to Manual Termination, i.e., Vector (VM). Narrative: "climb
heading 350 to 1500", "heading 265, at 9 DME west of PXR VORTAC, right turn heading 360", "fly heading
090, expect radar vectors to DRYHT INT."
(c) Navigation Issues. Pilots should be aware of their navigation system inputs, alerts, and
annunciations in order to make better -informed decisions. In addition, the availability and suitability of
particular sensors/systems should be considered.
(1) GPS/WAAS. Operators using TSO-C129(), TSO-C196(), TSO-C145() or TSO-C146() systems
should ensure departure and arrival airports are entered to ensure proper RAIM availability and CDI sensitivity.
(2) DME/DME. Operators should be aware that DME/DME position updating is dependent on
navigation system logic and DME facility proximity, availability, geometry, and signal masking.
1-2-4 Performance-Based Navigation (PBN) and Area Navigation (RNA V)

2/20/25 AIM
(3) VOR/DME. Unique VOR characteristics may result in less accurate values from VOR/DME
position updating than from GPS or DME/DME position updating.
(4) Inertial Navigation. Inertial reference units and inertial navigation systems are often coupled
with other types of navigation inputs, e.g., DME/D ME or GPS, to improve overall navigation system
performance.
NOTE-
Specific inertial position updating requirements may apply.
(d) Flight Management System (FMS). An FMS is an integrated suite of sensors, receivers, and
computers, coupled with a navigation database. These systems generally provide performance and RNA V
guidance to displays and automatic flight control systems.
Inputs can be accepted from multiple sources such as GPS, DME, VOR, LOC and IRU. These inputs may be
applied to a navigation solution one at a time or in combination. Some FMSs provide for the detection and
isolation of faulty navigation information.
When appropriate navigation signals are available, FMSs will normally rely on GPS and/or DME/DME (that
is, the use of distance information from two or more DME stations) for position updates. Other inputs may also
be incorporated based on FMS system architecture and navigation source geometry.
NOTE-
DME/DME inputs coupled with one or more IRU(s) are often abbreviated as DME/DME/IRU or D/D/I.
(e) RNA V Navigation Specifications (Nav Specs)
Nav Specs are a set of aircraft and aircrew requirements needed to support a navigation application within a
defined airspace concept. For both RNP and RNA V designations, the numerical designation refers to the lateral
navigation accuracy in nautical miles which is expected to be achieved at least 95 percent of the flight time by
the population of aircraft operating within the airspace, route, or procedure. (See FIG 1-2-1.)
(1) RNA V 1. Typically RNA V 1 is used for DPs and STARs and appears on the charts. Aircraft must
maintain a total system error of not more than 1 NM for 95 percent of the total flight time.
(2) RNA V 2. Typically RNA V 2 is used for en route operations unless otherwise specified. T-routes
and Q-routes are examples of this Nav Spec. Aircraft must maintain a total system error of not more than 2 NM
for 95 percent of the total flight time.
(3) RNA V 10. Typically RNA V 10 is used in oceanic operations. See paragraph 4-7-1 for specifics
and explanation of the relationship between RNP 10 and RNA V 10 terminology.