Page 1 of 17

OPS BINDER SECTOR 60

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

TABLE OF CONTENTS 1 NARRATIVE 1.1 Traffic Flow 1.2 Adjacent Sector/Facility Coordination 1.3 Potential Trouble Spots 2 ASSIGNMENT OF AIRSPACE 2.1 Delegation of Approach Control Airspace 2.2 West Atlantic Route System (WATRS) Airspace 2.3 Sectors Normally Combined 2.4 Military Airspace Delegation 2.5 SUA/SAA Activation Procedures 3 SECTOR INFORMATION 3.1 Frequency Information 3.2 Indirect Access (IA) Dial Codes 3.3 Sector Equipment Configurations 3.4 Sector Description 4 SECTOR PROCEDURES 4.1 Special Consideration for Military Aircraft 4.2 Radar Procedures 4.3 Non-Radar Procedures 4.4 Sector Specific Directives 4.5 Automated Data Exchange Procedures 4.6 LOA Procedures 4.7 Interim Altitude Waivers 4.8 Angulation of Flight Progress Strips 4.9 URET Operations

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 2 of 17

5 FLIGHT DATA REQUIREMENTS 5.1 Primary and Backup Printers 5.2 Alternate Methods of Relaying/Requesting Information 5.3 Strip Postings 5.4 Sources to Obtain Weather Information 5.5 Data Requiring Expeditious Handling 5.6 Status Information Area

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 3 of 17

1 NARRATIVE 1.1 Traffic Flows 1.1.1 Sector 60 is a high and low altitude sector (SFC and above). Sector 60

transitions arrivals and departures to and from Nassau Approach Control and the out-island airports. Traffic also consists of a significant amount of overflight traffic to and from South America and the Caribbean.

1.2 Adjacent Sector/Facility Coordination 1.2.1 Sector 60 coordinates with Sectors 40, 43, 58, 59 and 61, Havana Center

(MUFH) and Nassau Centre/Approach. 1.3 Potential Trouble Spots 1.3.1 Pilots are required to use QNE in certain areas within Sector 60, creating an

altitude/flight level transition situation. Controllers need to be aware of the JO 7110.65 8-5-1 requirements for this.

1.3.2 Due to the variety of surrounding airspace and control facilities, heightened

awareness to limited data blocks is necessary. 1.3.3 Due to a potential language barrier, emphasis should be placed on monitoring

read backs from foreign pilots, and while coordinating with HAV, to ensure compliance with clearances and coordination.

1.3.4 Because of the distances involved within the sector, close attention must be

given to overtake speeds of aircraft at the same altitude. 1.3.5 Use caution when issuing non-radar clearances to aircraft requesting IFR

clearances on the frequency or through Nassau FSS. Ensure the exact position and altitude prior to issuing clearances.

1.3.6 Be aware that many of the pilots flying to and from the islands are not

veterans to the area and do not always know local procedures. 1.3.7 Frequency coverage is limited at lower altitudes to the NW of the sector. 1.3.8 Due to the close proximity of Y589, Y586 and A315 to the ZMA/HAV

Boundary, northbound aircraft that enter sector 60 from HAV pose a potential Conflict with traffic on these airways upon entering the sector.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 4 of 17

1.3.9 Caution should be exercised when weather is impacting the vicinity of BOSAR ATA/DTA and SEANN DTA, because of the proximity of the routes associated with the DTAs and ATAs.

1.3.10 During ZMA-HAV Automated Data Exchange operations, controllers must

remain aware of potential duplicate proposed flight plans (FPLs) and ensure that aircraft are flying routes that coincide with active fight plans (CPLs).

2 ASSIGNMENT OF AIRSPACE. 2.1 Delegation of Approach Control Airspace: 2.1.1 Nassau Centre’s airspace lies in the western portion of Sector 60, SFC to

6,000’ MSL. Nassau Approach Control’s airspace lies in the northwestern portion of Sector 60, SFC to 12,000’ MSL.

2.2 West Atlantic Route System (WATRS) Airspace 2.2.1 Sector 60 is classified as WATRS Plus airspace. A detailed description of this

airspace can be found in JO 7110.65, Chapter 8. 2.3 Sectors Normally Combined 2.3.1 Sector 60 is normally combined at Sector 58. 2.4 Military Airspace Delegation 2.4.1 AUTEC Range is located southwest of Nassau and parallels the east coast of

Andros Island. The AUTEC range is used for submarine, surface vessel and missile testing. A NOTAM will be issued 96 hours prior to each scheduled firing period, and Miami Center will be advised 30 minutes prior to closure of the area, either directly or by relay. Miami Center will also be advised promptly of completion of firings. Most tests are conducted during daylight hours, under VFR conditions. Sometimes, however, the area will go “hot” and we will be required to keep aircraft from entering that airspace.

2.4.2 AW023 is located east of Bimini and extends to the Northeast of Nassau.

This area is used for AWACS operations and normally operates between FL260 and FL310, as assigned by ATC.

2.4.3 (MY)D3003A MISSILE RANGE Unltd By NOTAM VFR-IFR Nassau ACC

N24°30'00.00" W77°37'12.00" to N24°30'00.00" W77°27'30.00" to N24°28'30.00" W77°25'12.00" to N24°11'00.00" W77°18'42.00" to N24°11'00.00" W77°33'12.00" to N24°18'48.00" W77°36'00.00" to N24°28'30.00" W77°37'42.00" to beginning.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 5 of 17

2.4.4 (MY)D3003B MISSILE RANGE Unltd By NOTAM VFR-IFR Nassau ACC N24°11'00.00" W77°33'12.00" to N24°11'00.00" W77°18'42.00" to N24°00'00.00" W77°15'06.00" to N24°00'00.00" W77°29'42.00" to beginning.

2.4.5 (MY)D3003C MISSILE RANGE Unltd By NOTAM VFR-IFR Nassau ACC

N24°00'00.00" W77°29'42.00" to N24°00'00.00" W77°15'06.00" to N23°49'12.00" W77°11'42.00" to N23°49'12.00" W77°26'00.00" to beginning.

2.5 SPECIAL USE AIRSPACE (SUA)/SPECIAL ACTIVITY AIRSPACE (SAA) NOTIFICATION / ACTIVATION PROCEDURES: 2.5.1 The Miami Center Mission Position (MOS) is the focal point for all SUA/SAA. 2.5.2 When specific SUA/SAA is requested, the MOS must:

A. Call the appropriate Area FLM/CIC and relay the request. B. Once the request is approved; update the NTML Log if needed with the appropriate information. C. Alert the Area FLM/CIC that the SUA/SAA is active and the updated information is in the ESIS Queue to display on the Area ESIS. D. Update information into URET/EDST. 2.5.3 The Area FLM/CIC must: A. Advise the MOS when a notification/request originates from a

pilot/using agency to Activate/Deactivate a SUA/SAA B. When called by the MOS and advised of pending SUA/SAA activation, alert the appropriate sector(s) via VSCS. C. Take the information from the ESIS Queue and display it on the Area ESIS. 2.5.4 The Sector Radar Team must: A. Advise the FLM when a notification/request originates from a

pilot/using agency to Activate/Deactivate a SUA/SAA. B. Update the Sector Status Board to reflect the information given by the Area FLM/CIC.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 6 of 17

3 SECTOR INFORMATION 3.1 Frequencies

3.1.1 BUECS – There is no BUEC at this sector. 3.1.2 There are no Special Use frequencies at this sector. 3.2 Indirect Access (IA) Dial codes

Sector/Facility IA Signal

MYNN RHO 3376 voice

MUFH (MEVA) 3502 Voice

MIA IFSS FLT DATA 3359 03/04

MIA IFSS INFLIGHT 3359 90/92

MIA IFSS SUPERVISOR 3359 02/70

MYNN TOWER/TRACON/FSS (MEVA)

3509 2701/2702/2703

ARINC 3366 Auto

3.3 Sector Equipment Configurations 3.3.1 DC View

NEXRAD Layers 000B600

NEXRAD Levels 1-2-3 On

RNG FIX Optional

WX-1/WX-2/WX-3-- Optional**

Strobe Lines-- Optional

Map 1 (Sec./Center boundaries)-- On

Map 2 (Overlying high/low sectors)-- Optional

Map 3 (Apch. Ctl. Boundaries)-- Optional

Special Areas-- Optional*

Inbound List Optional*

Frequencies Site

127.22/239.02 MYEG/FK7

121.5/243.0 (Emergency) MYEG/FK7

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 7 of 17

Departure List Optional

Hold List Optional

Full Data Block On

All Lim. Data Block Optional

Select Lim. Data Block On

Emergency Airports Optional

All Primaries On

Non Mode "C” On

Select Beacon On

CTAS List Optional

* Note: Indicates mandatory "ON" position when special area in your sector is active. (May remain “OFF” if another method is used to display Special Areas.) ** Note: One of these must be “ON” when WX is in the area. When NEXRAD is “Not” available, NAS WX-1/WX-2/WX-3, must be selected as appropriate.

3.3.2 Flight Data Block Fields Panel

A/C ID On

Assigned Alt. On

Reported Alt. On

CID Optional

ESTAB Beacon On

Non RVSM On

Leader Line On

Position Symbol Optional

Type Optional

Dest Optional

CRR RDB Optional

STA RDB Optional

Delay RDB Optional

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 8 of 17

3.3.3 Range Vector Panel Range Normally 200 NM Vector Line Optional History Optional Leader Length Optional 3.3.4 Altitude Limits 000B600 3.3.5 Altimeter Settings YNN YEG

(as a minimum) 3.4 Sector Description 3.4.1 The sector boundary description for Sector 60 contains the lateral and vertical

limits for Sector 60 and is included in this order. 4 SECTOR PROCEDURES 4.1 Special Consideration for Military Aircraft 4.1.1 For flights operating “DUE REGARD” it is the aircrews’ responsibility to

conform to approved procedures. 4.1.2 Military and “State owned” aircraft are authorized to operate VFR at any

altitude while in Oceanic airspace. 4.2 Radar Procedures: (The following subparagraphs apply to aircraft remaining

in radar coverage)

4.2.1 The Ocean Area controller who initially establishes radar control or accepts a radar handoff of an aircraft must:

4.2.1.1 Clear aircraft AOA FL240 landing the Miami Terminal area via JUNUR/FLIPR, or CAREY..DEKAL as appropriate and assign the required STAR.

4.2.1.2 Ensure traffic landing FLL/FXE/OPF will enter Sector 40 AOB FL360. 4.2.1.3 Clear aircraft inbound from ZNY airspace landing the Miami Terminal area

direct FOWEE..JUNUR/FLIPR, or CAREY..DEKAL as appropriate, and assign the required STAR

4.2.1.4 Clear aircraft via ISAAC.BR54V.PBI, CVIKK.Y585.OMN, SRQ, REMIS

(Q100) or CIGAR (Q102), as appropriate. Aircraft entering ZMA airspace through or west of Sector 43 may be cleared via ISAAC..OMN.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 9 of 17

4.2.1.5 Ensure that aircraft proceeding over OMN through Sector 01 are able to cross the 01/59 boundary AOA FL370. Assign the preferential routing via FLL..ORL if the aircraft is unable to cross the 01/59 boundary AOA FL370.

4.2.1.6 Clear aircraft transitioning LAL/CTY/SZW no further north than: AOA FL280 -

via PBI..CTY or PBI..SZW, and aircraft AOB FL270 via PBI..LAL. 4.2.1.7 Aircraft landing MCO/ORL/SFB/OCF/ISM and Orlando area airports must be

routed as follows: FILED AT OR ABOVE FL240 cleared via direct FLL then either direct PHK.GOOFY STAR if not RNAV equipped; or direct BAIRN.BAIRN STAR if RNAV equipped. Aircraft that will cross the Sector 01 boundary between 2100-0700 (LCL) may be routed direct TRV or BAIRN and the appropriate STAR. Aircraft AOB FL230 may be routed TRV and BAIRN and the appropriate STAR during all hours.

4.2.1.8 Clear aircraft landing KNIP/KJAX via: AOB FL230 direct TRV..ORL..POGIE..KNIP or TRV..ORL..KJAX as appropriate. AOA FL240 direct FLL..ORL..POGIE..KNIP or FLL..ORL..KJAX as appropriate.

4.2.1.9 Clear aircraft entering ZNY, MTEG, MUHF or MDCS no further direct than the

ZMA FIR boundary fixes in the route of flight, consistent with the applicable LOA.

4.2.1.10 Clear MUGM arrivals to BYGON as a clearance limit. 4.2.1.11 Vector non area navigation equipped aircraft that are routed over the JUNUR ATA to join the FOWEE STAR, with coordination.

4.2.2 With the exception of aircraft with destinations of MBPV, MBGT, MDPC, and

MDLR, area navigation equipped aircraft entering Sector 60, at or above FL280, may be cleared by Sector 40 direct as follows with a computer update:

A315/Y587/Y586 ACMEE..JOSES or FORST..JOSES

A554 SEKAR

A636/Y589 ALBBE

M329 GRATX

M330 MILLE

B646 GRATX

G437 MAPYL

G446 BESAS

TJSJ Overflights DDP

TJSJ Landing Traffic IDAHO RTE6

Rev. 3 Effective 9/20/12

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 10 of 17

4.3 Non-Radar Procedures

4.3.1 A fix estimate and altitude confirmation must be verbally passed to the next sector/facility for aircraft not provided radar service.

4.3.2 Unless otherwise coordinated, If both QFK and GDT or QJS and QFK are out

A555 will be used northwest bound only and BR1L will be used southeast bound only.

4.3.3 Provo Approach arrivals that enter R58 from R60 must be routed

DUKKY.BR2L.SOLEI when Provo is on an east operation. Provo Approach arrivals entering R58 from R60 must be routed DUKKY.A555.BTLER when Provo is on a west operation.

4.3.4 When GTK radar OTS Y587 closed in sector 62. 4.3.5 When GTK radar OTS L463 closed BTLER to JUELE. 4.4 Sector Specific Directives 4.4.1 Monitors 121.5/243.0 MHz for emergency transmissions. 4.4.2 Clear SE bound traffic AOB FL120 no further direct than ACMEE A315,

ROSEA A756 or INDEE A555. 4.4.3 Clear aircraft landing within Provo Approach airspace to the outer fixes as

specified in the PROVO LOA, “no delay expected”. 4.4.4 Aircraft landing within the PBI terminal must cross the sector 40 boundary

AOB FL280.

4.4.5 After handoff, aircraft transitioning from Sector 40 to Sector 60 are released by Sector 40 for turns, provided the newly assigned headings remain between 090 and 180 degrees magnetic.

4.4.6 For traffic from Havana Center airspace that will transition to the Atlantic

Area, Sector 60 must feed Sector 59 even altitudes. 4.4.7 For traffic from the Atlantic Area that will proceed into Havana Center’s

airspace, Sector 59 must feed Sector 60 odd altitudes. 4.4.8 Each hour between 05 and 15 minutes after the hour, Sector 60 must

ensure that a current altimeter setting for YEG has been entered in the computer.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 11 of 17

4.4.9 The procedures contained in this Directive may be modified on a case-by-

case basis with prior verbal coordination. 4.5 Automated Data Exchange Procedures

4.5.1 Abbreviations:

ADE Automated Data Exchange CFL Coordinated Flight Level CPL Active Flight Plan FPL Proposed Flight Plan UTM Unsuccessful Transmission Message

4.5.2 ADE will be the primary method of flight plan coordination with Havana Center.

4.5.3 When ADE is being utilized, FPLs must be posted in the proposal bay until a CPL has been received and any inconsistency has been addressed.

4.5.3.1 Verify flight plan information on all CPLs received that do not have a corresponding FPL.

4.5.4 Controllers may make a remove strip computer input on FPLs, and physically remove corresponding strip, once the CPL is received and any discrepancy between the CPL and FPL have been resolved.

4.5.5 Controllers must issue full route clearances to aircraft that have FRC in remarks section of FPL.

4.5.6 When appropriate, controllers must verify routing for CPL that has corresponding multiple/duplicate FPL(s).

4.5.7 The use of interim altitudes, within the ADE time parameter, may be used for aircraft entering HAV ACC airspace to prevent a UTM from occurring. Controllers must coordinate revised altitudes with Havana ACC if the altitude is not the CFL (CPL coordinated altitude).

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 12 of 17

4.6 LOA Procedures 4.6.1 All LOAs pertaining to Sector 60 are:

San Juan CERAP New York Center

U.S. Customs Nassau Centre/IFSS Aeronautical Radio, Inc.

Miami AIFSS Havana Center Air Defense MBPV

4.7 Interim Altitude Waivers 4.7.1 A waiver of the computer entry of assigned altitude when aircraft are

transitioning to a higher altitude stratum has been issued to Sector 61. 4.8 Angulation of Flight Progress Strips 4.8.1 The flight progress strip must be angulated and remain angulated until no

further action is required when any of the following situations occur: 4.8.1.1 When coordination is required. 4.8.1.2 Required control actions not covered by a directive or letter of agreement. 4.8.1.3 The flight progress strip must be angulated for conflictions. 4.8.2 Normally used holding fixes:

Fix Direction Length Turns Altitude

BOSAR SE Assigned Right Assigned

HODGY As Needed As Needed As Needed As Needed

ZQA As Needed As Needed As Needed As Needed

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 13 of 17

4.9 URET Operations 4.9.1 URET Operations must conform to all applicable national and local directives. 4.9.2 Where automated coordination with a facility/sector is not available (e.g., an

international facility or VFR tower), use a flight progress strip to annotate manual coordination status.

4.9.3 The sector must keep the appropriate strips posted until one of the following

conditions is met: 4.9.3.1 The pilot of the aircraft cancels IFR. 4.9.3.2 A radar handoff has been accomplished, all known and potential conflictions

have been resolved, and the appropriate communications instructions have been issued.

4.9.3.3 The strip is no longer needed for control purposes. 5 FLIGHT DATA REQUIREMENTS 5.1 PRIMARY PRINTER: 60, backup 62 5.2 Alternate Methods of Relaying/Requesting Information: 5.2.1 Relay through other aircraft. 5.2.2 ARINC (HF, SEL Call, or ACARS) 5.2.3 Emergency Frequencies 5.2.4 VOR voice through FSS. 5.2.5 Nassau or Miami FSS. 5.2.6 Alternate means of landline communication: 5.2.6.1 Relay through adjacent facilities via available landlines. 5.2.6.2 Autovon

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 14 of 17

5.2.6.3 Commercial Telephone 5.2.6.4 AFTN 5.2.6.5 Clear aircraft to a boundary fix and have them pass their own estimate to the

next facility and receive clearance beyond the fix. 5.3 Strip Postings (Active traffic is normally sequenced by estimate times with the

earliest time at the bottom of the bay Traffic is normally sequenced using ZQA, HODGY, or HODGY FRD strips.)

5.4 Sources to Obtain Weather Information 5.4.1 Weather information is obtained via the sector printer from the Center

Weather Service Unit (CWSU) and can be observed on the WARP located in the Area.

5.4.2 Center Weather Service Unit (CWSU), by dialing IA 42370 or Traffic

Management Unit (TMU), IA 42300, 42310 or 42320. 5.4.3 Miami IFSS, via IA 3358-03, for present and forecasted weather for the entire

world. 5.4.4 Upper Wind forecast available for MIA, ELJ, EYW, MLB, HARDE, NBW,

LETON, and PIE. (UR-facility ID). 5.4.5 Upper Wind display is available in URET. (“UU W ddd” will display/raise wind

grid with specific altitude, where ddd is a three digit altitude) 5.5 Data Requiring Expeditious Handling 5.5.1 SIGMETs/CWAs/HIWAS/PIREP Alerts are normally disseminated by the

CWSU utilizing the Center GI message. 5.5.2 After issuance, the time of broadcast must be indicated on the GI strip and

the information must be posted at the affected sectors until no longer valid. 5.5.3 Post and keep radar controller informed of any flow control restrictions

applicable to the sector.

06/29/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 15 of 17

5.6 Status Information Area 5.6.1 The following information is required for display in the Status Information

Area: Review Status Information Area Airspace Equipment Weather Flow Traffic Radar Non-Radar Required Altitude Changes Fix Estimates Verified/Coordinated Automated Data Exchange

Page 16 of 17 Chg. 1 Effective 5/31/2012

 

4/27/2012

ZMA 7220.8I

APPENDIX-OCEAN 60

Page 17 of 17 Chg. 1 Effective 5/31/2012

GEORGETOWN

R60 BOUNDARY DESCRIPTION Beginning D 24-51-52N/76-00-00W Direct E 24-08-15N/74-50-08W Direct F 23-55-29N/74-32-43W Direct G 22-57-50N/75-10-37W Direct H 22-18-49N/75-35-21W Direct I 23-50-00N/77-45-00W Direct O 24-24-30N/77-16-40W Direct N 24-45-00N/77-00-00W Direct M 24-54-00N/77-00-00W Direct P 24-48-30N/76-00-00W Direct to point of beginning

from surface to FL239.

Except for the following airspace beginning at A 25-38-00N/77-48-50W Direct B 25-35-40N/77-18-30W Direct C 25-05-49N/76-24-45W Direct D 24-51-52N/76-00-00W Direct E 24-08-15N/74-50-08W Direct F 23-55-29N/74-32-43W Direct G 22-57-50N/75-10-37W Direct H 22-18-49N/75-35-21W Direct I 23-50-00N/77-45-00W Direct J 24-00-00N/78-00-00W Direct K 24-00-00N/78-10-00W Direct L 24-53-00N/77-44-30W Direct to point of beginning from FL240 and above.