AIM
4/3/14
5−5−7
Pilot/Controller Roles and Responsibilities
initial heading to be flown, obtains pilot’s concur-
rence that the procedure will allow the pilot to comply
with local traffic patterns, terrain, and obstruction
avoidance.
3.
Includes established departure procedures as
part of the ATC clearance when pilot compliance is
necessary to ensure separation.
5
−
5
−
15. Minimum Fuel Advisory
a. Pilot.
1.
Advise ATC of your minimum fuel status
when your fuel supply has reached a state where,
upon reaching destination, you cannot accept any
undue delay.
2.
Be aware this is not an emergency situation,
but merely an advisory that indicates an emergency
situation is possible should any undue delay occur.
3.
On initial contact the term “minimum fuel”
should be used after stating call sign.
EXAMPLE
−
Salt Lake Approach, United 621, “minimum fuel.”
4.
Be aware a minimum fuel advisory does not
imply a need for traffic priority.
5.
If the remaining usable fuel supply suggests
the need for traffic priority to ensure a safe landing,
you should declare an emergency due to low fuel and
report fuel remaining in minutes.
REFERENCE
−
Pilot/Controller Glossary Item
− Fuel Remaining.
b. Controller.
1.
When an aircraft declares a state of minimum
fuel, relay this information to the facility to whom
control jurisdiction is transferred.
2.
Be alert for any occurrence which might
delay the aircraft.
5
−
5
−
16. RNAV and RNP Operations
a. Pilot.
1.
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.”
2.
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.
3.
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.
4.
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:
(a)
Change altitude and/or airspeed waypoint
constraints to comply with an ATC clearance/
instruction.
(b)
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.
5.
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.
6.
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.
7.
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