• 热门标签

当前位置: 主页 > 航空资料 > 国外资料 > FAA >

时间:2011-04-18 01:03来源:蓝天飞行翻译 作者:航空
曝光台 注意防骗 网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

5.4.3.3 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.
5.4.3.4 Plan the route of fight 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.
5.4.3.5 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.
MIA1 SRQ2 3407/106153 3407/11546 TNP4 LAX5
1 Departure Airport 2 Departure Fix 3 Intermediate Fix (Turning Point) 4 Arrival Fix 5 Destination Airport
 or

Federal Aviation Administration Twentieth Edition
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.

5.4.3.6 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.
5.4.3.7 File at FL 390 or above for the random RNAV portion of the flight.
5.4.3.8 Fly all routes/route segments on Great Circle tracks.
5.4.3.9 Make any in.flight requests for random RNAV clearances or route amendments to an en route ATC facility.
5.5 Flight Plan Form (See FIG ENR 1.10.1.)
5.5.1 Explanation of IFR Flight Plan Items.
5.5.1.1 Block 1. Check the type flight plan. Check both the VFR and IFR blocks if composite VFR/IFR.
5.5.1.2 Block 2. Enter your complete aircraft identification including the prefix “N” if applicable.
5.5.1.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/R. Consult an FSS briefer for any unknown elements.
5.5.1.4 Block 4. Enter your computed true airspeed (TAS).
NOTE.
If the average TAS changes plus or minus 5 percent or 10 knots, whichever is greater, advise ATC.
5.5.1.5 Block 5. Enter the departure airport identifier code (or the airport name, city and state, if the identifier is unknown).
NOTE.
Use of identifier codes will expedite the processing of your flight plan.
5.5.1.6 Block 6. Enter the proposed departure time in Coordinated Universal Time (UTC) (Z). If airborne, specify the actual or proposed departure time as appropriate.
5.5.1.7 Block 7. Enter the requested en route altitude or flight level.
NOTE.
Enter only the initial requested altitude in this block. When more than one IFR altitude or flight level is desired along the route of flight, it is best to make a subsequent request direct to the controller.
5.5.1.8 Block 8. Define the route of flight by using NAVAID identifier codes (or names if the code is unknown), airways, jet routes, and waypoints (for RNAV).
NOTE.
Use NAVAIDs or waypoints to define direct routes and radials/bearing to define other unpublished routes.
5.5.1.9 Block 9. Enter the destination airport identifier code (or name if identifier is unknown).
5.5.1.10 Block 10. Enter your estimated time en route based on latest forecast winds.
5.5.1.11 Block 11. Enter only those remarks pertinent to ATC or to the clarification of other flight plan information such as the appropriate radiotele-phony (call sign) associated with the designator filed in Block 2. Items of a personal nature are not accepted. Do not assume that remarks will be automatically transmitted to every controller. Specif-ic ATC or en route requests should be made directly to the appropriate controller.
NOTE.
“DVRSN” should be placed in Block 11 only if the pilot/company is requesting priority handling to their original destination from ATC as a result of a diversion as defined in the Pilot/Controller Glossary.
5.5.1.12 Block 12. Specify the fuel on board, computed from the departure point.
5.5.1.13 Block 13. Specify an alternate airport if desired or required, but do not include routing to the alternate airport.

5.5.1.14 Block 14. Enter the complete name, address, and telephone number of pilot.in.command or, in the case of a formation flight, the formation commander. Enter sufficient information to identify home base, airport, or operator.
 
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:美国航行情报汇编 AERONAUTICAL INFORMATION PUBLICATION AIP 2(139)