10.07.2015 Views

Order 7110.65P, Air Traffic Control, with changes

Order 7110.65P, Air Traffic Control, with changes

Order 7110.65P, Air Traffic Control, with changes

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>7110.65P</strong> CHG 2 2/17/052. Distance verification shall be obtained fromeach aircraft at least every 24 minutes to verify thatseparation is maintained.3. If an aircraft fails to report its position <strong>with</strong>in3 minutes after the expected time, the controller shalltake action to establish communication. If communicationis not established <strong>with</strong>in 8 minutes after thetime the report should have been received, thecontroller shall take action to apply another form ofseparation.NOTE−When same track aircraft are at, or are expected to reduceto, the minima, speed control techniques should be appliedin order to maintain the required separation.d. Minima based on DME/RNAV:Apply the following DME/RNAV minima in<strong>Control</strong> 1234H, <strong>Control</strong> 1487H and the NortonSound High <strong>Control</strong> areas to turbojet aircraftestablished on or transitioning to the North Pacific(NOPAC) Route System.1. 30 NM between aircraft when DME reports orradar observations are used to verify the distance,otherwise at least 40 NM based on RNAV must beapplied; and2. Both aircraft must provide DME/RNAVdistance reports via direct voice that indicates theappropriate separation exists; and3. Application of DME/RNAV separation <strong>with</strong>outdirect voice communications may not continuefor more than 90 minutes; and4. The preceding aircraft is assigned the sameor greater Mach number than the following aircraft;and5. Both aircraft shall be advised of the otheraircraft involved, including the distance relative tothe flights.EXAMPLE−“Maintain Mach point eight four, same direction traffic,twelve o’clock, three five miles.”REFERENCE−FAAO 7110.65, <strong>Traffic</strong> Advisories, Para 2−1−21.8−9−4. LATERAL SEPARATIONIn accordance <strong>with</strong> Chapter 8, Offshore/OceanicProcedures, Section 4, Lateral Separation, apply thefollowing:a. Within areas where Required NavigationPerformance 10 (RNP−10) separation and proceduresare authorized, apply 50 NM to RNP−10approved aircraft.b. Apply 30 NM to RNP−4 approved aircraftoperating <strong>with</strong>in airspace designated for RNP−4when direct controller/pilot communications, viavoice or <strong>Control</strong>ler Pilot Data Link Communications(CPDLC), and the required ADS−C contracts aremaintained and monitored by an automated flightdata processor (e.g., Ocean21).c. When aircraft operate <strong>with</strong>in airspace wherecomposite separation and procedures are authorized,apply the minimum specified in para 8−9−5,Composite Separation Minima.d. Apply 100 NM to aircraft not covered bysubparas a, b or c.8−9−5. COMPOSITE SEPARATION MINIMAProvide composite separation <strong>with</strong>in the Central EastPacific (CEP) and North Pacific (NOPAC) compositeroute systems and where designated by facilitydirective in the Pacific Organized Track System(PACOTS) at and above FL 290 as follows:a. 1,000 feet vertical separation; andb. 50 NM lateral separation.8−9−6. COMPOSITE SEPARATION ALTITUDEASSIGNMENTa. <strong>Air</strong>craft operating at or above FL 300 in acomposite route system may be cleared at even flightlevels. Additionally, aircraft may be cleared at evenflight levels while joining, crossing, or leaving acomposite route system provided such aircraftleaving the system are cleared to an appropriate oddcardinal flight level when noncomposite vertical orlateral separation is achieved.b. <strong>Air</strong>craft (operating at or above FL 300) leavinga composite route system at an even cardinal flightlevel do not have to be assigned an odd cardinal flightlevel provided:1. The aircraft is being provided radar service;and2. The aircraft will be cleared for descent andapproach to an airport <strong>with</strong>in the facility’s domesticFIR; and8−9−2Pacific ICAO Region

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!