時間：2011-04-18 00:50來源：藍(lán)天飛行翻譯 作者：航空 點擊：次
|
EXAMPLE. MDW V262 BDF V10 BRL STJ SLN GCK Spelled out: from Chicago Midway Airport via Victor 262 to Bradford, Victor 10 to Burlington, Iowa, direct St. Joseph, Missouri, direct Salina, Kansas, direct Garden City, Kansas. NOTE. When route of flight is described by radio fixes, the pilot will be expected to fly a direct course between the points named. 7. Pilots are reminded that they are responsible for adhering to obstruction clearance requirements on those segments of direct routes that are outside of controlled airspace. The MEAs and other altitudes shown on low altitude IFR enroute charts pertain to those route segments within controlled airspace, and those altitudes may not meet obstruction clearance criteria when operating off those routes. d. Area Navigation (RNAV)1.Random RNAV routes can only be approved in a radar environment. Factors that will be considered by ATC in approving random RNAV routes include the capability to provide radar monitoring and compatibility with traffic volume and flow. ATC will radar monitor each flight, however, navigation on the random RNAV route is the responsibility of the pilot. 2.Pilots of aircraft equipped with approved area navigation equipment may file for RNAV routes throughout the National Airspace System and may be filed for in accordance with the following procedures. (a)File airport-to-airport flight plans. (b)File the appropriate RNAV capability certification suffix in the flight plan. (c)Plan the random route portion of the flight plan to begin and end over appropriate arrival and departure transition fixes or appropriate navigation aids for the altitude stratum within which the flight will be conducted. The use of normal preferred departure and arrival routes (DP/STAR), where established, is recommended. (d)File route structure transitions to and from the random route portion of the flight. (e)Define the random route by waypoints. File route description waypoints by using degree-distance fixes based on navigational aids which are appropriate for the altitude stratum. (f)File a minimum of one route description waypoint for each ARTCC through whose area the random route will be flown. These waypoints must be located within 200 NM of the preceding center’s boundary. (g)File an additional route description waypoint for each turnpoint in the route. 5.1.14 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 AC20.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 AIM 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. MIA1 SRQ2 3407/106153 3407/11546 TNP4 LAX 5 1 Departure airport. 2 Departure fix. 3 Intermediate fix (turning point). 4 Arrival fix. 5 Destination airport. or ORD1 IOW2 KP49G3 KD34U4 KL16O5 OAL6 MOD27 SFO8 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. |
