Operational Policies and Procedures For Pacific Oceanic and Offshore Airspace

航空发表于 2010-9-27 11:32:01

**** Hidden Message *****

航空发表于 2010-9-27 11:33:15

<?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:date Year="2006" Month="2" Day="16" w:st="on">2/16/06</st1:date>                                                   <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
Operational Policies and Procedures   <o:p></o:p>
For Pacific Oceanic and Offshore Airspace <o:p></o:p>
<o:p> </o:p>
OBJECTIVE.  The objective of this Notice is to document operational policies and procedures applicable in Pacific Oceanic and Offshore airspace.  <o:p></o:p>
<o:p> </o:p>
PARAGRAPH CHANGES (<st1:date Year="2006" Month="2" Day="16" w:st="on">2/16/06</st1:date> version).  See paragraph e (Special Procedures for In-flight Contingencies In Oceanic Airspace).<o:p></o:p>
<o:p> </o:p>
CONTENT.  The following are the major paragraphs of this document:<o:p></o:p>
<o:p> </o:p>
a.    Areas Where RVSM Is Applied   <o:p></o:p>
<o:p> </o:p>
b.    Boundaries of RVSM In the <st1:City w:st="on">Oakland</st1:City> and <st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City></st1:place> FIRs<o:p></o:p>
<o:p> </o:p>
c.    RVSM Airworthiness and Operational Approval and Monitoring<o:p></o:p>
<o:p> </o:p>
d.    In-flight Procedures in RVSM Airspace
<o:p> </o:p>
e.         Update:  Special Procedures for In-flight Contingencies In Oceanic Airspace<o:p></o:p>
<o:p> </o:p>
f.     Weather Deviation Procedures for Oceanic Controlled Airspace<o:p></o:p>
<o:p> </o:p>
g.    Strategic Lateral Offsets In Oceanic Airspace to Mitigate Wake <o:p></o:p>
Turbulence and to Mitigate Collision Risk<o:p></o:p>
<o:p> </o:p>
h.    Flight Planning in RVSM Airspace<o:p></o:p>
<o:p> </o:p>
i.     State Aircraft That Are Not RVSM Compliant<o:p></o:p>
<o:p> </o:p>
j.     Operation of Non-RVSM Aircraft Within RVSM Airspace<o:p></o:p>
<o:p> </o:p>
k.    Procedures For Suspension of RVSM With <st1:City w:st="on">Oakland</st1:City> or <st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City></st1:place> <o:p></o:p>
Airspace<o:p></o:p>
<o:p> </o:p>
OPERATIONAL POLICIES AND PROCEDURES:<o:p></o:p>
<o:p> </o:p>
a.  Areas Where RVSM Is Applied.  <st1:country-region w:st="on">Australia</st1:country-region>, <st1:country-region w:st="on">Fiji</st1:country-region>, <st1:country-region w:st="on">New Zealand</st1:country-region>, Tahiti, the <st1:country-region w:st="on">United States</st1:country-region>, <st1:country-region w:st="on">Japan</st1:country-region>, <st1:country-region w:st="on">Philippines</st1:country-region>, <st1:country-region w:st="on">Indonesia</st1:country-region>, and <st1:place w:st="on"><st1:country-region w:st="on">Papua New Guinea</st1:country-region></st1:place> have implemented RVSM within specified areas of their Flight Information Regions (FIR) at specified levels.
b. Boundaries of RVSM In the <st1:City w:st="on">Oakland</st1:City> and <st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City></st1:place> FIRs.  RVSM airspace is prescribed within the Oakland Oceanic FIR and Anchorage Oceanic FIR within controlled airspace between FL290 and FL410 inclusive. The flight level orientation scheme (FLOS) is single alternate, per ICAO Annex 2, Appendix 3a.
c. RVSM Airworthiness and Operational Approval and Monitoring
1. Operators must obtain operational approval from the State of <st1:place w:st="on"><st1:State w:st="on">Registry</st1:State></st1:place> or State of the Operator, as appropriate, to conduct RVSM operations. On behalf of the Pacific Air Traffic Service Providers, the FAA is maintaining a website containing documents and policy for RVSM approval.
The address is: www.faa.gov/ats/ato/rvsm1.htm. In the Pacific RVSM Documentation section, "Documents and Process for Pacific RVSM Aircraft and Operator Approval" provides an outline of approval process events with references to related documents.
2.   Airborne Collision Avoidance System II (ACAS II).  (TCAS II, Version 7.0 meets the ICAO ACAS II standard).   <o:p></o:p>
<o:p> </o:p>
(a)  <st1:place w:st="on"><st1:country-region w:st="on">U.S.</st1:country-region></st1:place> operators flying in airspace where RVSM is applied must comply with Part 91 Appendix G (Operations in RVSM Airspace).  Appendix G states that unless otherwise authorized by the FAA, aircraft equipped with TCAS II and used in RVSM operations must incorporate Version 7.0 or a later version.  For operations within other countries,  <o:p></o:p>
Part 91 Section 91.703 requires <st1:place w:st="on"><st1:country-region w:st="on">U.S.</st1:country-region></st1:place> operators to “…comply with  the regulations relating to flight and maneuver of aircraft there in force”.<o:p></o:p>
(b)  Non-U.S. Operators should confirm ACAS II equipage requirements applicable to them with the responsible State authority.  Many countries have adopted the ICAO Annex 6, Part I (International Commercial Air Transport Airplanes) standard:    from 1 January 2005, turbine-engined airplanes with a maximum certificated take-off mass in excess of  5,700 kg or authorized to carry more than 19 passengers shall be equipped with ACAS II. <o:p></o:p>
3. An essential part of the implementation of RVSM is the ability to monitor aircraft height to ensure that the aircraft height-keeping performance standard is being met. The Asia Pacific Approvals Registry and Monitoring Organization (APARMO) will process the results of monitoring. For further information on RVSM monitoring, the APARMO web site is: www.tc.faa.gov/act500/rvsm/aparmo_intro.html.
d. In-flight Procedures Within RVSM Airspace
1. Before entering RVSM airspace, the pilot should review the status of required equipment. (See Appendix 4 of FAA Guidance 91-RVSM for pilot RVSM procedures). The following equipment should be operating normally:
(a) Two primary altimetry systems.
(b) One automatic altitude-keeping device.
(c) One altitude-alerting device.
2. The pilot must notify ATC whenever the aircraft:
(a) Is no longer RVSM compliant due to equipment failure.
(b) Experiences loss of redundancy of altimetry systems.
(c) Encounters turbulence that affects the capability to maintain flight level.
(See Appendix 5 of FAA Guidance 91-RVSM for pilot and controller actions in such contingencies).
3. During cleared transition between levels, the aircraft should not overshoot or undershoot the assigned FL by more than 150 ft. (45 m).
4. Pilot Level Call. Except in an ADS or radar environment, pilots shall report reaching any altitude assigned within RVSM airspace.
e. Update:  Special Procedures for In-flight Contingencies In Oceanic Airspace. This paragraph contains procedures for in-flight contingencies in oceanic airspace that are now published in Section 15.2.2 of ICAO Document 4444 (Procedures for Air Navigation Services  - Air Traffic Management).  Effective <st1:date Year="2006" Month="2" Day="16" w:st="on">February 16, 2006</st1:date>, operators are expected to follow the procedures printed below.  The effective date for the guidance has been coordinated with the Air Traffic Services providers in the <st1:place w:st="on">Atlantic</st1:place> and Pacific.  The guidance will, therefore, be applicable in all Pacific and Atlantic oceanic FIRs including <st1:City w:st="on">Oakland</st1:City>, <st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City>, <st1:State w:st="on">New York</st1:State></st1:place> and San Juan Oceanic.  
<o:p> </o:p>
NOTE 1.  The only significant procedural change from in-flight contingency procedures previously published in ICAO Regional Supplementary Procedures (Doc 7030) is to the track offset.   The track offset has been changed to 15nm for contingencies requiring the aircraft to depart cleared altitude and/or track prior to obtaining a revised clearance.   In the “General Procedures” section below, see paragraphs 3b and 4.  <o:p></o:p>
 <o:p></o:p>
NOTE 2:  Prior to this harmonization, the track offset for in-flight contingencies was 30nm in the North Atlantic (NAT) and 25nm in Pacific airspace.  <o:p></o:p>
<o:p> </o:p>
<H1 style="MARGIN: 0cm 0cm 0pt 72pt">SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE:   INTRODUCTION<o:p></o:p></H1>
<o:p> </o:p>
1.  Although all possible contingencies cannot be covered, these procedures provide for the more frequent cases such as:<o:p></o:p>
<o:p> </o:p>
(a) Inability to maintain assigned flight level due to meteorological conditions, aircraft performance or pressurization failure;<o:p></o:p>
<o:p> </o:p>
(b) En route diversion across the prevailing traffic flow; and<o:p></o:p>
<o:p> </o:p>
(c) Loss of, or significant reduction in, the required navigation capability when operating in an airspace where the navigation performance accuracy is a prerequisite to the safe conduct of flight operations.<o:p></o:p>
<o:p> </o:p>
2.  These procedures are applicable primarily when rapid descent and/or turn-back or diversion is required. The pilot’s judgement shall determine the sequence of actions to be taken, having regard to the prevailing circumstances.  Air traffic control shall render all possible assistance.<o:p></o:p>
<o:p> </o:p>
<H1 style="MARGIN: 0cm 0cm 0pt 72pt; TEXT-INDENT: 36pt">SPECIAL PROCEDURES FOR IN-FLIGHT <o:p></o:p></H1>
<H1 style="MARGIN: 0cm 0cm 0pt 108pt">CONTINGENCIES IN OCEANIC AIRSPACE:<o:p></o:p></H1>
<H1 style="MARGIN: 0cm 0cm 0pt 108pt">GENERAL PROCEDURES<o:p></o:p></H1>
<o:p> </o:p>
1. If an aircraft is unable to continue the flight in accordance with its ATC clearance, and/or an aircraft is unable to maintain the navigation performance accuracy specified for the airspace, a revised clearance shall be obtained, whenever possible, prior to initiating any action.<o:p></o:p>
<o:p> </o:p>
2. The radiotelephony distress signal (MAYDAY) or urgency signal (PAN PAN) preferably spoken three times shall be used as appropriate. Subsequent ATC action with respect to that aircraft shall be based on the intentions of the pilot and the overall air traffic situation.<o:p></o:p>
<o:p> </o:p>
3. If prior clearance cannot be obtained, an ATC clearance shall be obtained at the earliest possible time and, until a revised clearance is received, the pilot shall:<o:p></o:p>
<o:p> </o:p>
(a) Leave the assigned route or track by initially turning *90 degrees to the right or to the left. When possible, the direction of the turn should be determined by the position of the aircraft relative to any organized route or track system.  Other factors which may affect the direction of the turn are:<o:p></o:p>
<o:p> </o:p>
(1) The direction to an alternate airport, terrain clearance;<o:p></o:p>
<o:p> </o:p>
(2) Any lateral offset being flown, and the flight levels allocated on adjacent routes or tracks.
<o:p> </o:p>
*FAA EXPLANATORY NOTE:  a turn of less than or greater than 90 degrees may be required, depending on the type of contingency and whether the pilot intends to continue in the same direction or reverse course. <o:p></o:p>
<o:p> </o:p>
(b) Following the turn, the pilot should:<o:p></o:p>
<o:p> </o:p>
(1) If unable to maintain the assigned flight level, initially minimize the rate of descent to the extent that is operationally feasible;<o:p></o:p>
<o:p> </o:p>
(2) Take account of other aircraft being laterally offset from its track;<o:p></o:p>
<o:p> </o:p>
(3) Acquire and maintain in either direction a track laterally separated by 28 km (15 NM) from the assigned route; and <o:p></o:p>
<o:p> </o:p>
(4) Once established on the offset track, climb or descend to select a flight level which differs from those normally used by 150 m (500 ft);<o:p></o:p>
<o:p> </o:p>
(c) Establish communications with and alert nearby aircraft by broadcasting, at suitable intervals: aircraft identification, flight level, position (including the ATS route designator or the track code, as appropriate) and intentions on the frequency in use and on 121.5 MHz (or, as a back-up, on the inter‑pilot air-to-air frequency 123.45 MHz);<o:p></o:p>
<o:p> </o:p>
(d) Maintain a watch for conflicting traffic both visually and by reference to ACAS (TCAS) (if equipped);<o:p></o:p>
<o:p> </o:p>
(e) Turn on all aircraft exterior lights (commensurate with appropriate operating limitations);<o:p></o:p>
<o:p> </o:p>
(f) Keep the SSR transponder on at all times; and<o:p></o:p>
<o:p> </o:p>
(g) Take action as necessary to ensure the safety of the aircraft.<o:p></o:p>
<o:p> </o:p>
4. When leaving the assigned track to acquire and maintain the track laterally separated by 28 km (15 NM), the flight crew, should, where practicable, avoid overshooting the track to be acquired, particularly in airspace where a 55.5 km (30 NM) lateral separation minimum is applied.<o:p></o:p>
<o:p> </o:p>
SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE:   ETOPS AIRCRAFT <o:p></o:p>
(ETOPS:  EXTENDED RANGE OPERATIONS BY AIRCRAFT WITH <o:p></o:p>
TWO-TURBINE POWER-UNITS) <o:p></o:p>
<o:p> </o:p>
1. If the contingency procedures are employed by a twin-engine aircraft as a result of an engine shutdown or failure of an ETOPS critical system, the pilot should advise ATC as soon as practicable of the situation, reminding ATC of the type of aircraft involved, and request expeditious handling.<o:p></o:p>
f. Weather Deviation Procedures for Oceanic-Controlled Airspace
General
1. The following procedures are intended to provide guidance. All possible circumstances cannot be covered. The pilot's judgment shall ultimately determine the sequence of actions taken and ATC shall render all possible assistance.
2. If the aircraft is required to deviate from track to avoid weather and prior clearance cannot be obtained, an air traffic control clearance shall be obtained at the earliest possible time. In the meantime, the aircraft shall follow the procedures detailed in paragraph g.8 below.
3. The pilot shall advise ATC when weather deviation is no longer required, or when a weather deviation has been completed and the aircraft has returned to the centerline of its cleared route.
Obtaining Priority from ATC when Weather Deviation Is Required
4. When the pilot initiates communications with ATC, rapid response may be obtained by stating "WEATHER DEVIATION REQUIRED" to indicate that priority is desired on the frequency and for ATC response.
5. The pilot still retains the option of initiating the communications using the urgency call "PAN PAN PAN" (preferably spoken three times) to alert all listening parties to a special handling condition which will receive ATC priority for issuance of a clearance or assistance.
Actions To Be Taken when Controller-Pilot Communications Are Established
6. The pilot notifies ATC and requests clearance to deviate from track, advising, when possible, the extent of the deviation expected. ATC will take one of the following actions:
(a) If there is no conflicting traffic in the horizontal dimension, ATC will issue clearance to deviate from track, or
(b) If there is conflicting traffic in the horizontal dimension, ATC will separate aircraft by establishing vertical separation, or
(c) If there is conflicting traffic in the horizontal dimension and ATC is unable to establish vertical separation, ATC shall:
(1) Advise the pilot unable to issue clearance for requested deviation.
(2) Advise pilot of conflicting traffic.
(3) Request pilot's intentions.
PHRASEOLOGY- "Unable (requested deviation), traffic is (call sign, position, altitude, direction), advise intentions."
7. The pilot will take the following actions:
(a) Advise ATC of intentions by the most expeditious means available.
(b) Comply with air traffic control clearance issued, or
(c) Execute the procedures detailed in para 8(a) below. (ATC will issue essential traffic information to all affected aircraft.)
(d) If necessary, establish voice communications with ATC to expedite dialogue on the situation.
Actions To Be Taken if a Revised Air Traffic Control Clearance Cannot Be Obtained:
8. The pilot shall take the actions listed below under the provision that the pilot may deviate from rules of the air (e.g., the requirement to operate on route or track centerline unless otherwise directed by ATC), when it is absolutely necessary in the interests of safety to do so.
(a) If a revised air traffic control clearance cannot be obtained and deviation from track is required to avoid weather, the pilot shall take the following actions:
(1) If possible, deviate away from an organized track or route system.
<DIV align=center>
<TABLE class=MsoNormalTable style="BORDER-RIGHT: black 1pt outset; BORDER-TOP: black 1pt outset; BACKGROUND: white; BORDER-LEFT: black 1pt outset; WIDTH: 336pt; BORDER-BOTTOM: black 1pt outset; mso-padding-alt: 2.25pt 2.25pt 2.25pt 2.25pt; mso-border-alt: outset black .75pt; mso-cellspacing: 0cm" cellSpacing=0 cellPadding=0 width=448 border=1>
<TBODY>
<TR style="mso-yfti-irow: 0; mso-yfti-firstrow: yes">
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 125.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=167>
Route center line track<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 96pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=128>
Deviations >10 NM<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 95.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=127>
Level change<o:p></o:p></TD></TR>
<TR style="mso-yfti-irow: 1">
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 125.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=167>
EAST (000-179 magnetic)<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 96pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=128>
LEFT RIGHT<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 95.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=127>
DESCEND 300 ft CLIMB 300 ft<o:p></o:p></TD></TR>
<TR style="mso-yfti-irow: 2; mso-yfti-lastrow: yes">
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 125.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=167>
WEST (180-359 magnetic)<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 96pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=128>
LEFT RIGHT<o:p></o:p></TD>
<TD style="BORDER-RIGHT: black 1pt inset; PADDING-RIGHT: 2.25pt; BORDER-TOP: black 1pt inset; PADDING-LEFT: 2.25pt; PADDING-BOTTOM: 2.25pt; BORDER-LEFT: black 1pt inset; WIDTH: 95.25pt; PADDING-TOP: 2.25pt; BORDER-BOTTOM: black 1pt inset; BACKGROUND-COLOR: transparent; mso-border-alt: inset black .75pt" vAlign=top width=127>
CLIMB 300 ft DESCEND 300 ft<o:p></o:p></TD></TR></TBODY></TABLE></DIV>
NOTE- Subparagraphs 8(a)(2) and 8(a)(3) below call for the pilot to: broadcast aircraft position and pilot's intentions, identify conflicting traffic and communicate air-to-air with near-by aircraft. If the pilot determines that there is another aircraft at or near the same FL with which his aircraft might conflict, then the pilot is expected to adjust the path of the aircraft, as necessary, to avoid conflict.
(2) Establish communication with and alert nearby aircraft by broadcasting, at suitable intervals: flight identification, flight level, aircraft position (including the ATS route designator or the track code), and intentions (including the magnitude of the deviation expected) on the frequency in use, as well as on frequency 121.5 MHz (or, as a back-up, the VHF inter-pilot air-to-air frequency 123.45).
(3) Watch for conflicting traffic both visually and by reference to ACAS (if equipped).
(4) Turn on all aircraft exterior lights (commensurate with appropriate operating limitations).
(5) For deviations of less than 10 NM, aircraft should remain at the level assigned by ATC.
(6) For deviations of greater than 10 NM, when the aircraft is approximately 10 NM from track, initiate a level change based on the criteria in the table below.
(7) If contact was not established prior to deviating, continue to attempt to contact ATC to obtain a clearance. If contact was established, continue to keep ATC advised of intentions and obtain essential traffic information.
(8) When returning to track, be at its assigned flight level, when the aircraft is within approximately 10 NM of centerline.
<H1 style="MARGIN: 0cm 0cm 0pt">g.  Strategic Lateral Offsets In Oceanic Airspace To Mitigate Collision Risk And To Mitigate Wake Turbulence<o:p></o:p></H1>
1. Pilots should use the Strategic Lateral Offset Procedure as standard operating practice in the course of normal oceanic operations to mitigate collision risk and wake turbulence.  The Strategic Lateral Offset Procedure will be applied throughout the <st1:City w:st="on">Oakland</st1:City> and <st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City></st1:place> oceanic FIRs. This procedure is to be used for both wake vortex encounters, and to mitigate the heightened risk of collision when non-normal events such as operational altitude deviation errors and turbulence induced altitude deviations occur.  
2.  Strategic Lateral Offset Procedures will be applied using the following guidelines: 
  (a) Strategic lateral offsets executed to mitigate collision risk and those executed to mitigate the effects of wake turbulence are to be made to the right of a route or track; 
  (b) In relation to a route or track, there are three positions that an aircraft may fly: centerline, 1 NM or 2 NM right; and, 
  (c) Offsets are not to exceed 2 NM right of centerline. 
3. The intent of this procedure is to reduce risk (increase the safety margin) by distributing aircraft laterally and equally across the three available positions. In this connection, pilots must take account of the following: 
  (a) Aircraft without automatic offset programming capability must fly the centerline; 
  (b) Aircraft capable of being programmed with automatic offsets may fly the centerline or offset 1 NM or 2 NM right of centerline to obtain lateral spacing from nearby   aircraft; 
  (c) Pilots should use whatever means are available (e.g. communications, visual acquisition, GPWS or TCAS/ACAS) to determine the best flight path to fly; 
  (d) Any aircraft overtaking another aircraft is to offset within the confines of this procedure, if capable, so as to create the least amount of wake turbulence for the aircraft being overtaken; 
  (e) For wake turbulence purposes, pilots are also to fly one of the three positions at 2b above and never offset to the left of centerline nor offset more than 2 NM right of centerline; 
NOTE.   It is recognized that the pilot will use his/her judgment to determine the action most appropriate to any given situation and has the final authority and responsibility for the safe operation of the aeroplane. The use of air-to-air channel, 123.45, may be used to co-ordinate the best wake turbulence offset option. 
  (f) Pilots may apply an offset outbound at the oceanic entry point but must return to centerline at the oceanic exit point.
  (g) Aircraft transiting radar-controlled airspace (e.g. Guam or <st1:place w:st="on"><st1:PlaceName w:st="on">Vancouver</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place>) may    remain on their established offset positions but must advise the radar controller on initial contact of their offset status; <o:p></o:p>
  (h) There is no ATC clearance required for this procedure and, except as stated in paragraph (g), above it is not necessary that ATC be advised; and, 
  (i) Voice position reports are to be based on the current ATC route/course clearance and not the exact co-ordinates of the offset position. 
h. Flight Planning in RVSM Airspace
1. RVSM approval is required for aircraft to operate within RVSM airspace. The operator must determine that the appropriate State authority has approved the aircraft and will meet the RVSM requirements for the filed route of flight and any planned alternate routes. The letter "W" shall be inserted in item 10 (Equipment) of the ICAO standard flight plan to indicate RVSM approved aircraft.
2. Non-RVSM Aircraft.  Non-RVSM civil aircraft unable to fly to an appropriate destination at or below FL280 and unable to fly at or above FL430 may flight plan at RVSM flight levels provided one of the following conditions exists: <o:p></o:p>
 (1) The aircraft is being initially delivered to the State of <st1:place w:st="on"><st1:State w:st="on">Registry</st1:State></st1:place> or Operator.
(2) The aircraft was formerly RVSM approved but has experienced an equipment failure and is being flown to a maintenance facility for repair in order to meet RVSM requirements and/or obtain approval.
(3) The aircraft is being utilized for mercy or humanitarian purposes.
(4) The aircraft is transporting a spare engine mounted under the wing.
<o:p> </o:p> 
3. Aircraft operators requesting approval as above shall:
(a) If departing within Oakland FIR or Anchorage FIR, obtain approval from the appropriate Oceanic Control Center normally not more than 12 hrs. and not less than 4 hrs. prior to the intended departure time.
(b) If transiting Oakland FIR or Anchorage FIR, notify the appropriate <st1:place w:st="on"><st1:PlaceName w:st="on">Oceanic</st1:PlaceName> <st1:PlaceName w:st="on">Control</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place> after approval is received from the first affected Center and prior to departure. (Note that filing of the flight plan is not appropriate notification).
(c) Include the remarks "APVD non-RVSM" in Field 18 of the ICAO Flight Plan.
4. Contact details for approval request or notification are as follows:
<st1:place w:st="on"><st1:City w:st="on">Oakland</st1:City></st1:place> ARTCC Telephone: 1-510-745-3342 AFTN: KZOAZRZX FAX: 1-510-745-3411
<st1:place w:st="on"><st1:City w:st="on">Anchorage</st1:City></st1:place> ARTCC Telephone: 1-907-269-1108 AFTN: PAZAZQZX FAX: 1-907-269-1343
5. Non-RVSM aircraft operating in the RVSM stratum will be separated from all other aircraft by a minimum 2,000 ft vertical separation.
6. This approval process is intended exclusively for the purposes indicated above and not as a means to circumvent the normal RVSM approval process.
i. State Aircraft That Are Not RVSM Compliant
<st1:PlaceName w:st="on">Non-RVSM</st1:PlaceName> <st1:PlaceType w:st="on">State</st1:PlaceType> aircraft may flight plan within <st1:City w:st="on">Oakland</st1:City>, <st1:City w:st="on">Anchorage</st1:City>, <st1:City w:st="on">Tokyo</st1:City> or <st1:place w:st="on"><st1:City w:st="on">Naha</st1:City></st1:place> airspace without prior coordination. State aircraft should include in field 18 of the ICAO Flight Plan (remarks):  “STS/Military NON-RVSM" should be added to the remarks section of the flight plan. 
j. Operation of Non-RVSM Aircraft Within RVSM Airspace
1.      Vertical separation applied. It should be noted that RVSM approved aircraft will be given priority for level allocation over non-RVSM approved aircraft. The vertical separation minimum between non-RVSM aircraft operating in the RVSM stratum and all other aircraft is 2,000 ft. 
<o:p> </o:p>
2.      Climb and descent through RVSM airspace. Non-RVSM compliant aircraft may be cleared to climb to and operate at or above FL430 or descend to and operate at or below FL280 provided that they:
(a) Do not climb or descend at less than standard rate.
(b) Do not level off at an intermediate level while passing through the RVSM stratum.
k. Procedures for Suspension of RVSM
Air traffic services will consider suspending RVSM procedures within affected areas of the Oakland FIR or Anchorage FIR when there are pilot reports of greater than moderate turbulence. Within areas where RVSM procedures are suspended, the vertical separation minimum between all aircraft will be 2,000 ft.
<o:p> </o:p>
(Oceanic Operations Standards Group, <st1:date Year="2006" Month="2" Day="16" w:st="on">2/16/06</st1:date>)<o:p></o:p>

bocome 发表于 2011-7-31 10:35:43

庞巴迪挑战者动力装置

页: [1]

航空论坛_航空翻译_民航英语翻译_飞行翻译's Archiver

Operational Policies and Procedures For Pacific Oceanic and Offshore Airspace