航行情報(bào)手冊(cè) Aeronautical Information Manual (AIM) 2

時(shí)間：2011-04-18 00:50來(lái)源：藍(lán)天飛行翻譯 作者：航空 點(diǎn)擊：次

Severe Turbulence and/or Mountain Wave Activity (MWA) Induced Altitude Deviations of Approximately 200 feet
Pilot will: Controller will:
.When experiencing severe turbulence and/or .Vector aircraft to avoid merging target with
MWA induced altitude deviations of traffic at adjacent flight levels, traffic permitting
approximately 200 feet or greater, pilot will
contact ATC and state “Unable RVSM Due (state .Advise pilot of conflicting traffic
reason)” (e.g., turbulence, mountain wave) .Issue FL change or re.route, traffic permitting
.If not issued by the controller, request vector
clear of traffic at adjacent FLs .Issue PIREP to other aircraft
.If desired, request FL change or re.route
.Report location and magnitude of turbulence or
MWA to ATC
See paragraph 4.6.6, Guidance on Severe Paragraph 4.6.6 explains “traffic permitting.”
Turbulence and Mountain Wave Activity (MWA) for
detailed guidance.
Operational Policy/Procedures for Reduced Vertical Separation Minimum (RVSM) in the Domestic U.S., Alaska, Offshore Airspace and the San Juan FIR 4.6.8 Operational Policy/Procedures for Reduced Vertical Separation Minimum (RVSM) in the
Mountain Wave Activity (MWA) Encounters . General
Pilot actions: .Contact ATC and report experiencing MWA .If so desired, pilot may request a FL change or re.route .Report location and magnitude of MWA to ATC See paragraph 4.6.6 for guidance on MWA. Controller actions: .Advise pilot of conflicting traffic at adjacent FL .If pilot requests, vector aircraft to avoid merging target with traffic at adjacent RVSM flight levels, traffic permitting .Issue FL change or re.route, traffic permitting .Issue PIREP to other aircraft Paragraph 4.6.6 explains “traffic permitting.”
NOTE. MWA encounters do not necessarily result in altitude deviations on the order of 200 feet. The guidance below is intended to address less significant MWA encounters.
Wake Turbulence Encounters
Pilot should: .Contact ATC and request vector, FL change or, if capable, a lateral offset See paragraph 4.6.7, Guidance on Wake Turbulence. Controller should: .Issue vector, FL change or lateral offset clearance, traffic permitting Paragraph 4.6.6 explains “traffic permitting.”
“Unable RVSM Due Equipment” Failure of Automatic Altitude Control System, Altitude Alerter or All Primary Altimeters
Pilot will: .Contact ATC and state “Unable RVSM Due Equipment” .Request clearance out of RVSM airspace unless operational situation dictates otherwise Controller will: .Provide 2,000 feet vertical separation or appropriate horizontal separation .Clear aircraft out of RVSM airspace unless operational situation dictates otherwise
One Primary Altimeter Remains Operational
Pilot will: .Cross check stand.by altimeter .Notify ATC of operation with single primary altimeter .If unable to confirm primary altimeter accuracy, follow actions for failure of all primary altimeters Controller will: .Acknowledge operation with single primary altimeter
4.6.9
Transponder Failure
Pilot will: .Contact ATC and request authority to continue to operate at cleared flight level .Comply with revised ATC clearance, if issued NOTE. 14 CFR Section 91.215 (ATC transponder and altitude reporting equipment and use) regulates operation with the transponder inoperative. Controller will: .Consider request to continue to operate at cleared flight level .Issue revised clearance, if necessary
4.6.10. Procedures for Accommodation of b. Categories of Non.RVSM Aircraft that may Non.RVSM Aircraft be Accommodated
a. General Policies for Accommodation of Non.RVSM Aircraft
1.The RVSM mandate calls for only RVSM authorized aircraft/operators to fly in designated RVSM airspace with limited exceptions. The policies detailed below are intended exclusively for use by aircraft that the FAA has agreed to accommodate. They are not intended to provide other operators a means to circumvent the normal RVSM approval process.
2.If either the operator or aircraft or both have not been authorized to conduct RVSM operations, the aircraft will be referred to as a “non.RVSM” aircraft. 14 CFR Section 91.180 and Part 91 Appendix G enable the FAA to authorize a deviation to operate a non.RVSM aircraft in RVSM airspace.
3.Non.RVSM aircraft flights will be handled on a workload permitting basis. The vertical separation standard applied between aircraft not approved for RVSM and all other aircraft shall be 2,000 feet.
4.Required Pilot Calls. The pilot of non. RVSM aircraft will inform the controller of the lack of RVSM approval in accordance with the direction provided in paragraph 4.6.8, Pilot/Controller Phraseology.
Subject to FAA approval and clearance, the following categories of non.RVSM aircraft may operate in domestic U.S. RVSM airspace provided they have an operational transponder.
1.Department of Defense (DOD) aircraft.
2.Flights conducted for aircraft certification and development purposes.
3.Active air ambulance flights utilizing a “Lifeguard” call sign.
4.Aircraft climbing/descending through RVSM flight levels (without intermediate level off) to/from FLs above RVSM airspace (Policies for these flights are detailed in paragraph 4.6.11, Non.RVSM Aircraft Requesting Climb to and Descent from Flight Levels Above RVSM Airspace Without Intermediate Level Off.
5.Foreign State (government) aircraft.
c. Methods for operators of non.RVSM aircraft to request access to RVSM Airspace. Operators may:
1. LOA/MOU. Enter into a Letter of Agree-ment (LOA)/Memorandum of Understanding (MOU) with the RVSM facility (the Air Traffic facility that provides air traffic services in RVSM airspace). Operators must comply with LOA/MOU.

航空翻譯 m.jdhsafaris.com
本文鏈接地址：航行情報(bào)手冊(cè) Aeronautical Information Manual (AIM) 2