TBL ENR 1.1.3
Pilot/Controller Phraseology
Message  Phraseology 
For a controller to ascertain the RVSM approval status of an aircraft:  (call sign) confirm RVSM approved 
Pilot indication that flight is RVSM approved  Affirm RVSM 
Pilot report of lack of RVSM approval (non.RVSM status). Pilot will report non.RVSM status, as follows: a. On the initial call on any frequency in the RVSM airspace and . . . b. In all requests for flight level changes pertaining to flight levels within the RVSM airspace and . . . c. In all read backs to flight level clearances pertaining to flight levels within the RVSM airspace and . . . d. In read back of flight level clearances involving climb and descent through RVSM airspace (FL 290 . 410)  Negative RVSM, (supplementary information, e.g., “Certification flight”). 
Pilot report of one of the following after entry into RVSM airspace: all primary altimeters, automatic altitude control systems or altitude alerters have failed. (See paragraph 38.9, Contingency Actions: Weather Encounters and Aircraft System Failures). NOTE.
This phrase is to be used to convey both the initial indication of RVSM aircraft system failure and on initial contact on all frequencies in RVSM airspace until the problem ceases to exist or the aircraft has exited RVSM airspace.  Unable RVSM Due Equipment 
ATC denial of clearance into RVSM airspace  Unable issue clearance into RVSM airspace, maintain FL 
*Pilot reporting inability to maintain cleared flight level due to weather encounter. (See paragraph 38.9, Contingency Actions: Weather Encounters and Aircraft System Failures).  *Unable RVSM due (state reason) (e.g., turbulence, mountain wave) 
ATC requesting pilot to confirm that an aircraft has regained RVSM.approved status or a pilot is ready to resume RVSM  Confirm able to resume RVSM 
Pilot ready to resume RVSM after aircraft system or weather contingency  Ready to resume RVSM 

Federal Aviation Administration Twentieth Edition
38.9 Contingency Actions: Weather Encoun-ters and Aircraft System Failures
TBL ENR 1.1.4 provides pilot guidance on actions to take under certain conditions of aircraft system failure and weather encounters. It also describes the expected ATC controller actions in these situations. It is recognized that the pilot and controller will use judgment to determine the action most appropriate to any given situation.

TBL ENR 1.1.4
Contingency Actions:  Weather Encounters and Aircraft System Failures
Initial Pilot Actions in Contingency Situations 
Initial pilot actions when unable to maintain flight level (FL) or unsure of aircraft altitude.keeping capability:  Notify ATC and request assistance as detailed below.  Maintain cleared flight level, to the extent possible, while evaluating the situation.  Watch for conflicting traffic both visually and by reference to TCAS, if equipped.  Alert nearby aircraft by illuminating exterior lights (commensurate with aircraft limitations). 

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 38.6, Guidance on Severe Turbulence  Paragraph 38.6 explains “traffic permitting.” 
and Mountain Wave Activity (MWA), for detailed 
guidance. 

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 38.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 38.6 explains “traffic permitting.” 
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：美國航行情報匯編 AERONAUTICAL INFORMATION PUBLICATION AIP 2(53)