AIM
4/3/14
5−1−15
Preflight
(h)
Plan additional route description way-
points as required to ensure accurate navigation via
the filed route of flight. Navigation is the pilot’s
responsibility unless ATC assistance is requested.
(i)
Plan the route of flight so as to avoid
prohibited and restricted airspace by 3 NM unless
permission has been obtained to operate in that
airspace and the appropriate ATC facilities are
advised.
NOTE
−
To be approved for use in the National Airspace System,
RNAV equipment must meet the appropriate system
availability, accuracy, and airworthiness standards. For
additional guidance on equipment requirements see
AC 20
−130, Airworthiness Approval of Vertical Naviga-
tion (VNAV) Systems for use in the U.S. NAS and Alaska,
or AC 20
−138, Airworthiness Approval of Global
Positioning System (GPS) Navigation Equipment for Use
as a VFR and IFR Supplemental Navigation System. For
airborne navigation database, see AC 90
−94, Guidelines
for Using GPS Equipment for IFR En Route and Terminal
Operations and for Nonprecision Instrument Approaches
in the U.S. National Airspace System, Section 2.
3.
Pilots of aircraft equipped with latitude/
longitude coordinate navigation capability,
independent of VOR/TACAN references, may file
for random RNAV routes at and above FL 390 within
the conterminous U.S. using the following
procedures.
(a)
File airport-to-airport flight plans prior to
departure.
(b)
File the appropriate RNAV capability
certification suffix in the flight plan.
(c)
Plan the random route portion of the flight
to begin and end over published departure/arrival
transition fixes or appropriate navigation aids for
airports without published transition procedures. The
use of preferred departure and arrival routes, such as
DP and STAR where established, is recommended.
(d)
Plan the route of flight so as to avoid
prohibited and restricted airspace by 3 NM unless
permission has been obtained to operate in that
airspace and the appropriate ATC facility is advised.
(e)
Define the route of flight after the
departure fix, including each intermediate fix
(turnpoint) and the arrival fix for the destination
airport in terms of latitude/longitude coordinates
plotted to the nearest minute or in terms of Navigation
Reference System (NRS) waypoints. For latitude/
longitude filing the arrival fix must be identified by
both the latitude/longitude coordinates and a fix
identifier.
EXAMPLE
−
MIA
1
SRQ
2
3407/10615
3
3407/11546 TNP
4
LAX
5
1
Departure airport.
2
Departure fix.
3
Intermediate fix (turning point).
4
Arrival fix.
5
Destination airport.
or
ORD
1
IOW
2
KP49G
3
KD34U
4
KL16O
5
OAL
6
MOD2
7
SFO
8
1
Departure airport.
2
Transition fix (pitch point).
3
Minneapolis ARTCC waypoint.
4
Denver ARTCC Waypoint.
5
Los Angeles ARTCC waypoint (catch point).
6
Transition fix.
7
Arrival.
8
Destination airport.
(f)
Record latitude/longitude coordinates by
four figures describing latitude in degrees and
minutes followed by a solidus and five figures
describing longitude in degrees and minutes.
(g)
File at FL 390 or above for the random
RNAV portion of the flight.
(h)
Fly all routes/route segments on Great
Circle tracks.
(i)
Make any inflight requests for random
RNAV clearances or route amendments to an en route
ATC facility.
e. Flight Plan Form
− See FIG 5−1−2.
f. Explanation of IFR Flight Plan Items.
1. Block 1.
Check the type flight plan. Check
both the VFR and IFR blocks if composite VFR/IFR.
2. Block 2.
Enter your complete aircraft
identification including the prefix “N” if applicable.
3. Block 3.
Enter the designator for the aircraft,
followed by a slant(/), and the transponder or DME
equipment code letter; e.g., C−182/U. Heavy aircraft,
add prefix “H” to aircraft type; example: H/DC10/U.
Consult an FSS briefer for any unknown elements.