時(shí)間：2011-04-18 00:50來源：藍(lán)天飛行翻譯 作者：航空 點(diǎn)擊：次
|
Pilot/Controller Roles and Responsibilities 5.5.5 5.5.13. VFR-on-top a. Pilot. 1. This clearance must be requested by the pilot on an IFR flight plan, and if approved, allows the pilot the choice (subject to any ATC restrictions) to select an altitude or flight level in lieu of an assigned altitude. NOTE. VFR.on.top is not permitted in certain airspace areas, such as Class A airspace, certain restricted areas, etc. Consequently, IFR flights operating VFR.on.top will avoid such airspace. REFERENCE. AIM, IFR Clearance VFR.on.top, Paragraph 4.4.8. AIM, IFR Separation Standards, Paragraph 4.4.11. AIM, Position Reporting, Paragraph 5.3.2. AIM, Additional Reports, Paragraph 5.3.3. 2. By requesting a VFR-on-top clearance, the pilot assumes the sole responsibility to be vigilant so as to see and avoid other aircraft and to: (a)Fly at the appropriate VFR altitude as prescribed in 14 CFR Section 91.159. (b)Comply with the VFR visibility and distance from clouds criteria in 14 CFR Sec-tion 91.155, Basic VFR weather minimums. (c)Comply with instrument flight rules that are applicable to this flight; i.e., minimum IFR altitudes, position reporting, radio communications, course to be flown, adherence to ATC clearance, etc. 3. Should advise ATC prior to any altitude change to ensure the exchange of accurate traffic information. b. Controller. 1.May clear an aircraft to maintain VFR-on-top if the pilot of an aircraft on an IFR flight plan requests the clearance. 2.Informs the pilot of an aircraft cleared to climb to VFR-on-top the reported height of the tops or that no top report is available; issues an alternate clearance if necessary; and once the aircraft reports reaching VFR-on-top, reclears the aircraft to maintain VFR-on-top. 3.Before issuing clearance, ascertain that the aircraft is not in or will not enter Class A airspace. 5.5.14. Instrument Departures a. Pilot. 1.Prior to departure considers the type of terrain and other obstructions on or in the vicinity of the departure airport. 2.Determines if obstruction avoidance can be maintained visually or that the departure procedure should be followed. 3.Determines whether a departure procedure and/or DP is available for obstruction avoidance. 4.At airports where IAPs have not been published, hence no published departure procedure, determines what action will be necessary and takes such action that will assure a safe departure. b. Controller. 1.At locations with airport traffic control service, when necessary, specifies direction of takeoff, turn, or initial heading to be flown after takeoff. 2.At locations without airport traffic control service but within Class E surface area when necessary to specify direction of takeoff, turn, or 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.5.6 Pilot/Controller Roles and Responsibilities 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 aircraft navigation database and conforms to the charted procedure. 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. AIM (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, shall verify that the appropriate changes are loaded and available for navigation. |
